A provider can be doing everything right and still fail this. The courses are bought, the workers are willing, the induction set goes out on day one. Then a first aid certificate expires in April, a refresher falls due in June, and both facts live in a spreadsheet that was accurate in March.
The gap between having training and having current training is almost entirely a tracking gap. It is worth separating out, because the fix is a different kind of fix.
Why mandatory training goes overdue
In short: it is a tracking failure, not a willingness failure. Training gets assigned once at induction, renewals fall due months later on dates nobody is watching, and turnover means new starters inherit a role without the training set that goes with it.
Almost nobody sets out to let training lapse. What happens is quieter than that. A worker completes their induction set in their first fortnight, the certificates land, and the record looks healthy. Eleven months later a refresher falls due on a date that exists only inside a system nobody opens, and the person who would have noticed is three houses away sorting a roster gap.
Turnover does the rest. A worker leaves, a replacement starts, and the replacement inherits the shift but not the training set attached to the role. Six weeks in, they are working alongside colleagues who did modules they have never been assigned. Nothing failed loudly. The gap just appeared and stayed.
This matters for how a provider fixes it. If overdue training were a willingness problem, more reminding by a person would work. It is a tracking problem, so it responds to a system that watches the dates and tells someone before they pass.
What a provider actually needs to track
In short: assigned, complete, due, overdue and expiring, for every worker, and readable by team and by role. Most systems show the first two well. The last three are what decide whether anyone acts in time.
Assigned and complete is the easy half, and it is the half most systems display prominently, because it is the half that looks good. A dashboard showing 94 per cent completion is a comfortable thing to look at. It is also the number least likely to tell a quality manager what to do this week.
The useful columns are the other three. What is due, what is already overdue, and what is expiring soon. Those are the ones that generate an action, and they are the ones a provider is asked about when training comes up in an audit.
It also has to be readable by team and by role, not just by worker. The question a provider needs answered is rarely about one person. It is closer to: of the workers rostered to this house, who is not current on the training this house needs. A per-worker list cannot answer that without someone sitting down and cross-referencing a roster.
What an automated reminder has to do to work
In short: fire before the due date, use a warning window the provider sets, and go to someone other than the worker. A reminder that only reaches the person already not doing the training changes nothing.
Automated reminders are common. Automated reminders that change an outcome are less common, and the difference comes down to three things.
They have to fire early. A reminder on the due date is a notification, not a prompt. It tells someone they are late. Firing ahead of the date is what leaves room to actually book the training.
The window has to be adjustable. A seven-day warning is fine for an online refresher a worker can finish on a break. It is close to useless for a worker screening clearance or an external first aid course, where the provider does not control the turnaround and weeks can pass. A single fixed window across everything will always be wrong at one end.
Someone other than the worker has to see it. This is the one most often missed. If the only reminder goes to the person who has not done the training, the system has automated the nagging and nothing else. A weekly summary to a team leader or quality manager is what turns a reminder into a follow-up.
Is automating the chasing the point?
In short: no. Delivering training, tracking due dates and sending reminders is the minimum a compliance system should do, and several platforms do it well. It is table stakes. The question worth asking is what a system can tell you once the chasing is handled.
It is worth being direct here, because a lot of marketing in this category is not.
Getting mandatory training delivered, tracked, chased and recorded is the baseline. It is what a compliance system is for, several platforms do it competently, and a provider should expect it rather than be sold it. Naming it as a headline feature is a bit like a car being advertised as having wheels.
The more useful question for a provider comparing systems is what happens after that. Once the chasing is handled and the dashboard is green, what does the system actually know about the workforce? A team where every worker is marked complete is not the same as a team that is capable, and completion data on its own cannot tell the difference between the two.
Both things matter. Chasing the admin is the minimum. Seeing the decisions a team makes on shift is the part that nothing else in this category does.
What an auditor makes of an overdue list
In short: having overdue items is not automatically a finding. Whether the provider knew about them, and can show the list is being worked rather than discovered, is what carries weight.
There is a fear that showing an auditor anything overdue is an admission. In practice the opposite tends to be true, and providers who understand this present better.
A workforce of any size will have training in flight at any moment. Someone started last week. Someone is on leave. A clearance is with the screening unit. An auditor is not surprised by that. What they are testing is whether the provider has visibility of it, can name which workers and which training, and can show the list is being actively worked.
The uncomfortable version is the opposite one: a report showing everything complete, with no tracking visible behind it and no record of anything ever having been overdue. That invites the question of whether the system is measuring anything at all. An honest list with dates and follow-up against it is a stronger position than a clean one nobody can explain.
What tracking and reminders do not tell you
In short: they evidence what was assigned, when it was due and when it was completed. They say nothing about whether a worker can apply it on shift. Where observed assessment applies, a qualified assessor makes that call.
This is the boundary worth holding, because it is the one most easily blurred.
A tracking system produces a defensible record of process: this training was assigned to this worker, it was due on this date, it was completed on that one, here is the certificate. That is a genuinely useful record and it is what a great deal of compliance evidence consists of.
It is not a competence record. Completing a module on de-escalation on time evidences that the module was completed on time. Whether the worker can de-escalate a situation in a shared house at 2am is a different question, and no completion date answers it. Where observed assessment applies, for complex and higher-risk supports, the provider's own qualified assessor watches the work and makes that judgement. CORA does not make it, and no training platform can.
How CORA handles it
In short: automatic due, overdue and renewal reminders, with the warning window set by the provider from 7, 14, 30, 60 or 90 days, a weekly summary to whoever should receive it, and pathways carrying per-course due dates so a new starter inherits the right set. Included on both plans.
Automatic due, overdue and renewal reminder emails go out on their own, so keeping training on track stops being a standing item on someone's list.
The provider sets how far ahead a renewal counts as due, choosing from 7, 14, 30, 60 or 90 days, and chooses who receives the weekly summary. That covers both ends of the problem described above: a short window for the things a worker can finish quickly, a long one for the clearances that are out of the provider's hands.
Role and site pathways carry per-course due dates, so a new starter inherits the right training set with the right deadlines automatically rather than by someone remembering. Workers can be invited in bulk by CSV, grouped into teams, and exempted individually from a course that does not apply to them. The credential and evidence register runs the same way for the things CORA did not deliver: worker screening, first aid, licences and tickets, each with its own expiry and warning band.
All of it exports. The training register, a completion summary with timestamps, the credential register and completion certificates all come out as PDF or CSV, and all of it is included on both plans.
None of that is the differentiator, and this page has already said why. Keeping records current is the minimum. The part CORA adds on the Capability plan is the Workforce Capability Report, which shows whether the training your workers finished actually landed, worker by worker and team by team.
See the tracking and the records
The quickest way to judge a tracking system is to look at what it produces when someone asks. CORA's four exportable records are the same ones an auditor tends to ask for.
See how it works Request a demoFrequently asked questions about tracking overdue NDIS training
Why does mandatory NDIS training go overdue?
Rarely because a worker refuses. It goes overdue because nobody owns the chase. Training is assigned once at induction, renewals fall due months later on dates nobody is watching, and the person who would notice is doing a roster. Turnover compounds it: a new starter inherits a role but not the training set that goes with it. The failure is almost always a tracking failure rather than a willingness failure, which is why it responds to a system rather than to more reminding by a person.
What should an NDIS provider track for training compliance?
For each worker: what was assigned, what is complete, what is due, what is overdue, and what is expiring. Assigned and complete is what most systems show. Due, overdue and expiring is the part that decides whether anyone acts in time. Tracking has to work by team and by role as well as by worker, because the question a provider needs answered is usually about a house or a shift rather than about one person.
What makes an automated training reminder actually work?
Three things. It has to fire before the due date rather than on it, so there is time to act. The warning window has to be something the provider sets, because a 7-day warning suits an online module and is useless for a clearance that takes weeks to renew. And someone other than the worker has to see the summary, because a reminder that only goes to the person who is already not doing the training changes nothing.
Is automating the chasing what makes a training platform worth buying?
No, and it is worth being direct about that. Delivering training, tracking due dates and sending reminders is the minimum a compliance system should do, and several platforms do it well. It is table stakes, not a differentiator. The question worth asking a vendor is what the system can tell you once the chasing is handled, because a workforce where everyone is marked complete is not the same as a workforce that is capable.
What does an auditor make of an overdue training list?
Having overdue items is not automatically a finding. What matters is whether a provider knows about them, can say which workers and which training, and can show the overdue list is being worked rather than discovered. A clean report with no visible tracking behind it tends to invite more questions than an honest list with dates and follow-up against it.
Do automated reminders prove a worker is competent?
No. Reminders and tracking evidence that training was assigned, when it was due and when it was completed. They say nothing about whether a worker can apply any of it on shift. Where observed assessment applies, for complex and higher-risk supports, the provider's own qualified assessor watches the work and makes that call.
How far ahead should a renewal reminder be set?
It depends what is renewing. An online refresher can be handled in a week. A worker screening clearance or an external first aid course needs far longer, because the provider does not control the turnaround. That is why a single fixed reminder window across everything tends to fail at one end or the other, and why the window is worth setting deliberately rather than left at a default.
How does CORA handle due, overdue and renewal tracking?
Automatic due, overdue and renewal reminder emails go out on their own. The provider sets how far ahead a renewal counts as due, choosing from 7, 14, 30, 60 or 90 days, and chooses who receives the weekly summary. Role and site pathways carry per-course due dates so a new starter inherits the right set automatically, and a worker can be exempted from a course that does not apply to them. It is included on both plans.
Sources and further reading
- NDIS Practice Standards, NDIS Quality and Safeguards Commission
- Provider obligations and requirements, NDIS Quality and Safeguards Commission
- NDIS Worker Screening, NDIS Quality and Safeguards Commission
- What an NDIS training register must contain, CORA
- NDIS credential tracking: worker screening, first aid and expiry dates, CORA
- NDIS audit preparation: a training checklist for quality managers, CORA
- NDIS staff training requirements: the 2026 provider's guide, CORA
- Common questions from providers, CORA