Staff Competency Tracking for Care and NDIS Providers: A Practical Guide

What is staff competency tracking, and how is it different from qualification tracking?

Staff competency tracking is the record of which of your workers can safely and capably perform which tasks or support types, connected to the decision about who actually gets assigned to a shift. Qualification tracking is a narrower thing: a register of certificates and credentials on file, with expiry dates. Qualification tracking asks whether a worker holds a document. Competency tracking asks whether that worker is the right one for this specific client and this specific task, today.

The two are related, not identical. A current qualification is usually a precondition for competency, but competency adds two things a qualification register does not capture on its own: what a specific client requires from anyone who works with them, and whether a specific carer should or should not be sent to a specific client for reasons that have nothing to do with certificates, such as a prior incident or a client's own preference. A worker can hold every certificate your organisation lists and still be the wrong person to send to a particular client tomorrow.

How do I track the competencies of my staff?

Set up a single catalogue of the competencies that matter to your organisation, record what each worker currently holds against it, set which competencies each client requires, and enforce the match at the point a shift is assigned rather than checking it separately afterwards. Each step depends on the one before it, and skipping the last one is why most competency systems fail in practice.

1. 1.Build a catalogue. List every competency you need to track: First Aid, CPR, NDIS Worker Screening, Manual Handling, Medication Administration, and anything specific to your organisation, such as PEG feeding or catheter management. Decide, for each one, whether it expires, how far ahead to alert before it lapses, and whether it needs evidence or a sign-off to count as held.
2. 2.Record what each worker holds. Against the catalogue, log each worker's current competencies with an attainment date and, where relevant, an expiry date. Attach evidence or a sign-off where the competency type requires it. This is the register everything else checks against.
3. 3.Set what each client requires. Some clients need a specific competency from anyone who works with them, regardless of which service is booked. Record that requirement once, on the client's own record, rather than trying to remember it shift by shift.
4. 4.Enforce it at the point of assignment. This is the step most spreadsheet-based systems skip. A catalogue and a register are only useful if something actually checks a worker against a client's requirements at the moment a coordinator is deciding who to send, not in a monthly audit after the fact.

What competencies should a care or NDIS provider track?

The specific list depends on the supports you deliver, but most disability, aged care, and community health providers track a similar core set, then add competencies specific to their client group.

Standard competencies, tracked by nearly every provider:

Complex or high-intensity competencies, relevant where your client group includes clinical or behavioural needs:

Our companion guide on clinical competency management for NDIS providers covers the regulatory detail behind the high-intensity list, including what a competency assessment record needs to contain to survive an audit.

Building a competency matrix without a spreadsheet

A competency matrix is the classic way to visualise this data: workers down one side, competencies across the top, and a cell for each combination showing whether that worker currently holds that competency and when it was assessed. As a concept, it is exactly right. As a spreadsheet, it breaks down fast.

The failure is not that spreadsheets are ugly. It is that a spreadsheet has no relationship to your roster. It does not know that Client A requires a specific competency from every carer who visits them. It does not know that a worker's competency needs to be checked against the date of a specific future shift, not against today. And it does not stop a coordinator, under time pressure covering a last-minute call-in, from assigning whoever answers the phone first.

A working competency matrix needs to live inside the same system as your roster: one catalogue, one register of what each worker holds, one place to set what each client requires, all checked automatically at the point someone is assigned. That is what competency tracking software is built to do, rather than being a document you update once a quarter and hope stays accurate.

Why competency tracking has to connect to your roster, not sit beside it

The value of competency tracking is entirely in the moment of assignment. A perfectly accurate register that a coordinator has to remember to check manually protects you no better than no register at all, because the check gets skipped exactly when you can least afford it: a sick call an hour before a shift, a new coordinator covering someone else's clients, a busy Friday afternoon.

A properly connected system does three things at that moment. First, it checks the worker's held competencies against what the client requires, and against the shift date the support is actually being delivered on, not against today's date. A carer whose First Aid lapses next Tuesday should not be shown as eligible for a Wednesday visit, even if the roster is being built today while the certificate is still current. Second, it applies any carer-specific rules attached to that client: a soft preference, which still allows the carer to be selected but flags them, or a safeguarding exclusion, which is a hard block that removes the carer from the list entirely and cannot be overridden by a coordinator in the moment. Third, it shows the coordinator why, splitting the assignment list into who is eligible, who is missing a requirement, and who is not available, rather than silently hiding people with no explanation.

This is the difference between competency tracking as a document exercise and competency tracking as an operational control. See how this connects to qualification-matched rostering on the scheduling board, and how the underlying register ties into compliance and expiry tracking more broadly.

Competency tracking and the NDIS Practice Standards

Under the NDIS Practice Standards, most requirements concern organisational process and participant outcomes. The High Intensity Daily Activities module is different: it is specifically about clinical governance, and it is where the certificate-versus-competency distinction matters most to an auditor.

For each high-intensity activity a provider delivers, such as PEG feeding, tracheostomy management, or complex bowel care, the Practice Standards expect evidence that a worker has been assessed as competent by a qualified assessor, not just trained. That means a record of who assessed the worker, when, by what method, and with what outcome, linked to the specific worker and the specific activity. A certificate that a course was completed is not, on its own, treated as sufficient evidence for these supports.

The practical implication for tracking is that a certificate on file is not, by itself, a complete record. In Teiro, a held competency can carry an attached evidence document, a manager sign-off with a name, date, and notes, a certificate number, and the attainment and expiry dates, so the register reflects a reviewed record rather than just a course completion. What Teiro does not currently capture as separate structured fields is the assessor's identity, the assessment method, or the assessment outcome. If your high-intensity supports need that level of detail recorded formally, keep it in the evidence document itself or in a dedicated assessment record alongside the held competency.

Where Teiro's register earns its keep is at the point a worker is assigned: the assignment gate checks held competencies against what is required using the actual shift date, not today's date, so a competency that will have lapsed by the day the support is delivered is caught before the roster is finalised, not after. That is an assignment-time check, and it is a different thing from a retrospective audit report. Teiro does not currently produce a report showing whether a worker held a given competency on an arbitrary past shift date after the fact. This is why competency tracking needs to be tied to your roster as a live check, not treated as a static list refreshed periodically.

How to move from a spreadsheet to a competency tracking system

Moving off a spreadsheet does not need to happen all at once. A practical sequence:

1. 1.Audit what you actually track today. Pull together whatever spreadsheets, HR folders, or sticky notes currently hold competency information, and consolidate them into a single list of competencies your organisation cares about.
2. 2.Build the catalogue first. Set up each competency type with its expiry rule and evidence requirement before you start entering worker data, so you are not re-doing the structure halfway through.
3. 3.Backfill your current workforce. Enter what each existing worker holds. This is the most time-consuming step and the one worth doing properly, since everything downstream depends on it being accurate.
4. 4.Start with your highest-risk clients. Rather than trying to set required competencies for every client on day one, begin with the clients whose needs are most complex, where a mismatch carries the most risk, and expand from there.
5. 5.Run in a flexible enforcement mode first. Most organisations are better served starting with a mode that flags gaps and groups ineligible workers, rather than hard-blocking every assignment, while the underlying data is still being cleaned up. Move to stricter enforcement once you trust the register.
6. 6.Keep safeguarding exclusions separate from preferences from the start. Decide early which client-carer restrictions are genuine duty-of-care exclusions that must never be overridden, and which are softer preferences, so the distinction is built into your data rather than retrofitted later.

Frequently Asked Questions

How do I track the competencies of my staff?

Keep one catalogue of the competencies that matter, record what each worker holds against it with attainment and expiry dates, and check that register automatically whenever a worker is assigned a shift. The tracking only holds up if the check happens at assignment, not as a separate task someone has to remember to run.

What is the difference between a qualification and a competency?

A qualification is a certificate: evidence a worker completed a course or holds a screening check. A competency is broader: it includes the qualification, but also whether that worker is the right fit for a specific client, factoring in what that client requires and any carer-specific preferences or safeguarding exclusions attached to their record.

Do I need special software to track competencies, or is a spreadsheet enough?

A spreadsheet can hold the data, but it cannot enforce it. It has no connection to your roster, no way to check a worker's competency against a specific future shift date, and no way to stop an assignment happening when a requirement is missing. Purpose-built competency tracking software keeps the catalogue, the register, and the roster in the same system, so the check runs automatically rather than depending on someone remembering to look.

How is competency tracking different from a safeguarding exclusion?

Competency tracking covers whether a worker can perform a task. A safeguarding exclusion is a separate, carer-specific restriction, typically following a prior incident, that blocks a particular carer from being assigned to a particular client regardless of their competencies. A well-built system tracks both, and treats a safeguarding exclusion as a hard block that cannot be overridden by a coordinator, unlike a general preference, which is a softer steer.

Can competency requirements be set for a specific service type rather than the whole client?

In most systems today, including Teiro, required competencies are set at the client level: a competency a carer must hold to work with that client at all, regardless of which specific service is booked. Requiring a competency only for certain service types, so a client's general community access visits are treated differently from their clinical supports, is a finer level of control some platforms are still building toward.

Teiro keeps the competency catalogue, worker register, client requirements, and carer safeguarding rules in one system, and checks all of it automatically in the assignment picker. Book a demo to see the full competency tracking software in action, or sign up to explore the platform.