Software Comparison
Health and NDIS CRMs with competency tracking, compared
“Competency tracking” means different things depending on which vendor you ask. For most platforms in this category, it means a place to store credentials with expiry reminders. That is useful, but it is not the whole job.
This page sets out what competency tracking should mean for a care or NDIS provider, gives you a checklist to test any vendor against, and compares Teiro honestly against ShiftCare, Lumary, Brevity, CareMaster, and GoodHuman on it. Where we have not been able to verify a competitor’s capability from public documentation, we say so rather than guess.
What “competency tracking” should actually mean
A document store that reminds you a certificate is expiring in 30 days is qualification tracking. It is a real and useful capability, and most care software has it in some form. Competency tracking is a step further: it connects that register to who a specific client actually needs, and to who should or should not be sent there for reasons that have nothing to do with a certificate.
The part that separates a document-management feature from an operational control is enforcement. A register that a coordinator has to remember to check manually protects you no better than no register, because the check gets skipped under exactly the pressure it exists for: a last-minute sick call, a coordinator covering someone else’s clients, a busy afternoon. Real competency tracking runs the check automatically, at the moment a worker is assigned, and makes the hard exclusions genuinely un-skippable.
The buyer’s checklist
Seven capabilities worth testing in a demo, whichever vendor you are evaluating. Where a competitor’s public documentation does not describe a capability one way or the other, this table says so rather than assuming the answer.
| Capability | ShiftCare | Lumary | Brevity | CareMaster | GoodHuman | Teiro |
|---|---|---|---|---|---|---|
| Credential document storage with expiry alerts | Yes | Not publicly documented | Yes | Not publicly documented | Not publicly documented | Yes |
| Required competencies set per client, not just per worker | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Yes, set once on the client record |
| Distinct soft preference vs hard safeguarding exclusion | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Yes, two severities, safeguarding cannot be overridden |
| Enforced at the point of assignment, not a separate review | Documented as alerting, not assignment-time gating | Not publicly documented | Documented as alerting, not assignment-time gating | Not publicly documented | Documented as alerting, not assignment-time gating | Yes, in the assignment picker itself |
| Checked against the shift date, not just today | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Yes |
| Configurable enforcement mode (warn vs hard block) | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Yes, flexible by default, strict optional |
| Audit trail on exclusion changes and overrides | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Not publicly documented | Yes |
Based on publicly available product documentation as of August 2026. “Not publicly documented” means we could not confirm the capability either way, not that the vendor lacks it. Features change, verify directly with each vendor before deciding. Teiro’s enforcement runs in a flexible mode by default; missing requirements are grouped and flagged rather than always hard-blocked, and safeguarding exclusions are a hard block regardless of mode. Required competencies are set at the client level today; per-service-type requirements are on our roadmap, not yet shipped.
Where each platform fits
Competency tracking is one capability among many you are weighing. Here is a short, honest read on where each of these platforms tends to fit, with a link through to a fuller head-to-head where one exists.
ShiftCare
A mature, widely used platform with a strong shift offer and bid workflow, and mature Xero and MYOB integrations. Its credential tracking covers document storage and expiry alerts for key credentials. See the full Teiro vs ShiftCare comparison.
Lumary
An enterprise platform built on Salesforce, generally suited to larger organisations with dedicated implementation resources and complex configuration needs. Its credentialing capabilities are not fully documented publicly, and would need to be confirmed directly with Lumary during a demo. See the full Teiro vs Lumary comparison.
Brevity
Priced and positioned for smaller providers, with credential storage and expiry tracking covering key NDIS and workforce credentials. See the full Teiro vs Brevity comparison.
CareMaster
An Australian-built platform, also priced for smaller providers. Its competency-tracking depth beyond general credential storage is not something we have been able to verify from public documentation. See the full Teiro vs CareMaster comparison.
GoodHuman
A care and disability-focused platform. Its document storage and credential-tracking capabilities are not something we have been able to verify from public documentation. See the full Teiro vs GoodHuman comparison.
Teiro
Built around competency tracking as an enforcement layer, not just a document store: a credential catalogue, worker-held competencies, competencies required per client, and safeguarding exclusions that lock a carer out of the assignment picker entirely. Checked against the shift date, not today’s date, and run in a flexible warn-first mode by default with a strict mode available. See the full competency tracking software page for how it works.
Frequently asked questions
What should competency tracking actually mean in care software?
More than a document store with expiry reminders. A competency tracking system should let you set what a specific client requires from anyone who works with them, hold a soft preference and a hard safeguarding exclusion as distinct severities, and check all of it automatically at the point a worker is assigned to a shift, not in a separate compliance review after the roster is built.
Which health or NDIS CRMs have competency tracking?
Most care workforce platforms, including ShiftCare, Brevity, and GoodHuman, offer credential document storage with expiry alerts. Teiro is built around a fuller definition: a credential catalogue, worker-held competencies, competencies required per client, and safeguarding exclusions that are enforced automatically at the point of assignment. Whether a given competitor supports per-client requirements or assignment-time enforcement specifically is not always clear from public documentation, which is why this page compares vendors capability by capability rather than by a single yes or no.
What is the best software for tracking staff competencies?
The best fit depends on which capabilities matter most to your organisation. If you only need document storage with expiry reminders, most platforms in this category cover that. If you need required competencies enforced per client and un-skippable safeguarding exclusions at the point a shift is assigned, fewer platforms document that specifically. Teiro is built around the second definition. Use the checklist on this page to test any vendor you are evaluating, including us.
Why does this page mark most competitor capabilities as “not publicly documented” instead of no?
Because we have not verified it either way. Several platforms in this category are strong, established products, and it is possible some support per-client requirements or assignment-time gating without describing it in public materials. We would rather say a capability is not publicly documented than claim a competitor lacks something we cannot confirm. If you use one of these platforms and can tell us how it handles a specific row on this table, we will update the page.
Is a safeguarding exclusion the same as a compliance flag?
No. A compliance flag typically relates to a missing or expired credential and can usually be overridden with a note. A safeguarding exclusion is a carer-specific restriction, often following a prior incident, that should remove that carer from the assignment picker entirely and never be overridable by a coordinator in the moment. Conflating the two, or only supporting one, is one of the gaps this checklist is designed to surface.
See competency tracking and the assignment gate live
Bring your own checklist, including this one. We will walk through the catalogue, client requirements, safeguarding exclusions, and how the assignment picker enforces all of it in a live roster.
Running a small team? Free for under 5 users - no credit card, no time limit.