An assessor asks for your training register. Not a summary of it, the actual thing: who did what, when they did it, and when it needs doing again. Most providers know it by a longer name: the Staff Learning, Training and Professional Development Register.
What is an auditor actually asking for?
The requirement sits under Human Resource Management, part of Provider Governance and Operational Management in the Core Module. It asks a provider to keep a record of the learning, training and professional development each worker has undertaken, current enough that it reflects what's actually happened rather than what was planned at the start of the year.
In short: it's not a training calendar and it's not a course catalogue. It's a per-worker record of what was actually completed, with dates.
What information should an NDIS training register contain?
A register that satisfies the indicator needs, at minimum, a worker's name, the course or training activity they completed, the date they completed it, who delivered it if it was run in person, and where relevant, the date the training needs refreshing.
Professional development counts too, not only mandatory compliance courses. A register that only shows Compliance Foundations completions is showing half the picture. This is the working set CORA's own register exports as one row per completion:
| Column | What it shows |
|---|---|
| Worker name and role | So the training can be judged against the job, not read in isolation |
| Course or training activity | The specific course completed, not a category |
| Date completed | Written the moment the course is finished, not typed in later |
| Delivered by | CORA, or named where training was run in person or externally |
| Knowledge check result | Recorded against the completion, not a separate document |
| Mapped NDIS Practice Standards | Shown on the certificate and carried into the register row |
| Refresher or expiry date | Where a course carries one, so it sits with the name rather than a separate spreadsheet |
How does CORA build the register automatically?
Every course completion writes its own row. Nothing gets typed in twice, because the register is generated from the same data as the certificate, not compiled separately from it. Where a course carries a refresher period, like infection control, the expiry date sits against that worker's name in the same register, not in a separate spreadsheet someone has to remember to update.
The whole register, or a filtered slice of it, exports as a PDF or a CSV, ready to hand to an assessor.
The training register is one record inside CORA's wider HR software for NDIS providers, alongside the credential register, policy acknowledgements and supervision, all on the same worker file.
Where do the register's entries come from?
Every course in CORA's library of 90+, from Compliance Foundations through to Leadership & Workforce Sustainability, feeds a completion straight into this register the moment a worker finishes it. Infection Control & Hygiene is a good example: its completion record carries its own refresher date, so the register shows exactly when a worker's infection control training expires, not just that they once did the course.
Existing training history doesn't get left behind either. Credentials and in-person training records import in bulk, and they land in the same register, so a provider with four years of history in a spreadsheet doesn't have to choose between abandoning it and retyping it. Day one looks like year four, not like an empty system.
Does a training register prove a worker is competent?
No. The training register answers "did this happen, and when." That's a real and necessary artefact, and it's the one an assessor names by name. It does not establish that a worker can apply the training on shift. A different question, whether the training actually changed what a worker does on shift, is answered by the Workforce Capability Report, built from scored decisions rather than completion dates. Where observed assessment applies, for complex and higher-risk supports, that call stays with the provider's own qualified assessor. The two records are related but not the same claim, and it's worth knowing which one you're holding.
Common questions
What is the NDIS training register called?
Auditors usually ask for it as the Staff Learning, Training and Professional Development Register. CORA generates it automatically from every course completion recorded in the system.
Does the training register update automatically?
Yes. Every time a worker completes a course, CORA adds the record to the register, including the refresher date where one applies. Nothing needs to be entered twice.
Can I export the training register for an audit?
Yes. The register exports as a one-click, audit-ready PDF or CSV, ready to hand to an assessor.
Does a training register prove a worker is competent?
No. It 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.
Is a training register the same as a credential register?
No. A training register records what your organisation assigned and delivered. A credential register records tickets, checks and licences issued by someone else, like NDIS worker screening or first aid, each with its own expiry date. See the NDIS credential register for what that one holds.