Compliance and records

NDIS Training Register: What It Must Contain and How to Keep One

Published 28 July 2026 · about an 8-minute read

Most providers can produce a certificate for a worker if you give them long enough to find it. Far fewer can produce one document showing, across the whole workforce, who was assigned what, who finished it, and when. That document is the training register, and it is usually the first thing asked for when training comes up in an audit.

Taieri Walsh, founder of CORA Workforce

Taieri WalshFounder of CORA.

There is a version of training records most providers will recognise. Certificates land in an inbox, someone saves them into a folder named after the worker, and the folder structure becomes the record. It works, in the sense that the evidence exists somewhere. It stops working the moment anyone asks a question about the workforce rather than about one person.

A training register is the answer to that second kind of question. It is one document, covering everyone, built to be read across rather than down.

What a training register actually is

In short: a training register is a single named record of what training every worker was assigned and what they completed, with dates. It is a workforce-wide document, not a folder of certificates, and it is the format that answers a question about coverage rather than about one individual.

The distinction matters more than it sounds. A folder of certificates can tell you that one worker completed manual handling in March. A register tells you that of the fourteen workers rostered to a house where manual handling applies, twelve have completed it, one is overdue, and one started last week and has not been assigned it yet.

The first is evidence. The second is a management tool that also happens to be evidence, and it is the one that shows a provider is running its training rather than collecting the paperwork afterwards.

What it has to contain

In short: for every worker, their name and role, the training name, who delivered it, the completion date, a certificate or record reference, an expiry or renewal date where one applies, and the delivery method. Miss the role and you cannot show the training suited the job. Miss the delivery method and an online module looks identical to an observed practical session.

There is no official template, so what follows is the working set most providers converge on and most auditors expect to see.

Field Why it is there
Worker name and role or position Training has to be appropriate to the job. Without the role on the same line, nobody can judge whether it was.
Training or course name Specific enough to identify what was covered. "Induction" on its own tells a reader almost nothing.
Training provider Who delivered it, whether that is your own team, an RTO, or a platform. Establishes where the evidence originates.
Date completed The anchor for everything else, including whether the training predates the person's current role.
Certificate or record reference The link from the row to the underlying evidence. A register nobody can trace back to a document is an assertion.
Expiry or renewal date Only some training carries one, but where it does, its absence from the register is where the gaps form.
Delivery method Online, in person, or external. Distinguishes a module a worker read from a session someone watched them do.

The two fields most often missing are role and delivery method, and they are missing for the same reason: a system that exports course completions does not necessarily know either. It knows a person finished a module. Whether that person is a team leader or a new casual, and whether the training was a video or a practical, sits outside what a completion record captures on its own.

Training register or credential register

In short: a training register records what you assigned and delivered. A credential register records what you hold but did not deliver, like worker screening, first aid or a licence, each on its own expiry clock. They answer different questions and a provider needs both.

These get conflated constantly, usually because one system produces one of them and the provider assumes that is the whole obligation.

The test is simple. If your organisation decided what training a worker would do and then delivered it, that belongs in the training register. If a third party issued something the worker brought with them, or that you sent them out to obtain, that is a credential and it belongs in a credential register with its own expiry tracking.

A worker can be perfectly current on one and lapsed on the other. That is exactly the scenario a provider wants to catch before an auditor does, and it is why keeping the two records in the same place, attached to the same person, is worth more than keeping either one well on its own.

Where the spreadsheet version breaks

In short: the format is not the problem. The problem is that a spreadsheet is accurate on the day it is updated and drifts every day after, and it holds the row separately from the evidence the row refers to.

Plenty of providers run a perfectly good spreadsheet register, and for a small stable team it can be the right tool. Three things tend to break it.

It drifts. Every new starter, every role change and every completion is a manual edit, and the register is only as current as the last time someone remembered. Nothing tells you it has gone stale, so you find out when you look.

It separates the row from the evidence. The register says a worker completed something on a date. The certificate proving it lives in a folder, in an inbox, or with a manager who has since left. At audit you are reconciling two systems under time pressure.

It does not chase anything. A register records what happened. It does not tell anyone what has not happened yet, which is the more useful half of the job and the half that keeps the register accurate in the first place.

What an auditor does with it

In short: they sample it. The register is rarely the end of the conversation, it is the starting point for picking a few workers and asking to see the evidence behind their rows.

This is worth understanding because it changes what a good register looks like. A register that is comprehensive but cannot produce the underlying certificate quickly is worse than a smaller one where every row traces to something in a couple of clicks.

The pattern is usually: read the register, choose workers who look interesting, which often means recent starters, people in higher-risk roles, or anyone whose row has a gap, then ask for the evidence behind those specific entries. What is being tested is not whether the document exists. It is whether the document is true.

That means the register and the evidence want to live together. It also means a register with visible holes is not necessarily a problem, as long as the provider can say what the holes are and what is being done about them. A register that looks perfect and does not survive sampling is a considerably worse position to be in.

What it does not prove

In short: a training register evidences what was assigned and completed. It does not establish that a worker can apply any of it on shift. Where observed assessment applies, a qualified assessor makes that call.

This is the honest limit of the document, and it is worth stating because the opposite gets implied so often.

A completed module means a worker went through the content and, if there was a knowledge check, answered questions about it. That is genuinely useful and it is genuinely required. It is not the same as knowing they will read a situation correctly at 6am in someone's home with nobody else there.

For complex and higher-risk supports, that gap is closed by observed assessment, where a qualified assessor watches the work and signs it off. That is your assessor's call and your organisation's process. Keep the scope honest in both directions though: observed assessment applies to those higher-risk supports, not to every course a worker completes, and implying otherwise overstates what any provider is expected to do.

What a register can do, if the underlying system captures more than a completion tick, is show something about whether the training landed. That is a different record answering a different question, covered in how to prove workforce capability at an audit.

How CORA handles it

In short: a training register by name is one of four records CORA produces, alongside a completion summary with timestamps, a credential and evidence register, and completion certificates. All of it exports as PDF or CSV, and all of it is included on both plans.

CORA's training register lists every worker by name with their assigned pathway, what they have completed, what is outstanding and the dates, so the workforce view and the individual view come from the same record rather than being assembled separately.

It sits alongside three other named records. A completion summary across the workforce with timestamps. A credential and evidence register covering screening, first aid, tickets and in-person training with expiry status and the evidence file attached. And completion certificates carrying the worker's name, the course, the date, the knowledge check result and the mapped NDIS Practice Standards.

Naming them is deliberate. Every platform in this category says it makes you ready for an audit, which is easy to say and impossible for a buyer to check. A list of exactly which records you get is something you can hold up against what your auditor actually asks for. What an audit outcome looks like still depends on a provider's whole quality system, not on training records alone.

All of that is included on both plans, along with course delivery, role and site pathways, per-course due dates and automatic due, overdue and renewal reminders. None of that is the differentiator, and it is worth saying so plainly. Keeping records current is the minimum a system should do. 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 register and the records

If your training register currently lives in a spreadsheet, the quickest way to see the difference is to look at the four exportable records side by side with what your auditor asks for.

See how it works Request a demo

Frequently asked questions about the NDIS training register

What is a training register for an NDIS provider?

A training register is a single named record of what training every worker was assigned and what they completed, with the dates. It answers one question for a provider and its auditor: for this worker, in this role, what training have they actually done. It is a workforce-wide record rather than a folder of individual certificates, and it is the document most often asked for first when training comes up in an audit.

What information should an NDIS training register contain?

For every worker: their name and their role or position, the name of the training, who delivered it, the date it was completed, a certificate or record reference, an expiry or renewal date where the training has one, and the delivery method, meaning whether it was online, in person, or an external course. A register missing the role makes it impossible to show training was appropriate to the job. A register missing the delivery method cannot distinguish an online module from an observed practical session.

Do the NDIS Practice Standards require a training register?

The Practice Standards do not prescribe a register template or a fixed list of fields. What they require is that a provider can demonstrate its workers are appropriately skilled and trained for the roles they perform, and that this is documented. In practice a register is how most providers evidence it, because it is the format that answers the question across the whole workforce rather than one worker at a time. Providers should confirm the specific expectations that apply to their registration groups with the NDIS Quality and Safeguards Commission.

What is the difference between a training register and a credential register?

A training register records the training a provider assigned and the worker completed. A credential register records the clearances, certificates and tickets a provider holds but did not deliver, such as an NDIS Worker Screening Check, a first aid certificate from an RTO, or a driver's licence, each with its own expiry date. They answer different questions and a provider needs both. A worker can have completed every assigned module and still hold a lapsed clearance.

Can a spreadsheet be used as a training register?

It can, and plenty of providers run one. The difficulty is not the format, it is that a spreadsheet is accurate on the day someone updates it and drifts every day after. It also separates the record from the evidence, so at audit you are matching a row in a file against certificates saved somewhere else. That is workable for a small team and gets progressively harder as the workforce grows or as staff turn over.

Does a training register prove a worker is competent?

No. A training register evidences what training was assigned and completed, and when. It does not establish that a worker can apply it on shift. Where observed assessment applies, for complex and higher-risk supports, a qualified assessor watches the work and makes that call. Treating a register as a competence record is the most common way providers overstate what their training evidence shows.

How long should NDIS training records be kept?

Retention periods come from the NDIS rules and a provider's own registration conditions rather than from the training system, and providers should confirm what applies to them with the NDIS Quality and Safeguards Commission. The practical point for choosing a system is that records need to survive staff turnover and platform changes, so being able to export the full register as PDF or CSV matters more than where it happens to be stored today.

Does CORA produce a training register?

Yes. A training register by name is one of four records CORA produces, alongside a completion summary with timestamps, a credential and evidence register, and completion certificates carrying the worker's name, the course, the date, the knowledge check result and the mapped NDIS Practice Standards. All of it exports as PDF or CSV and is included on both plans.

Sources and further reading

← Back to all guides