CORA's Pathway Builder produces the same artefact, and keeps it current without anyone having to remember to touch it.
What the indicator asks for
The requirement sits under Human Resource Management, part of Provider Governance and Operational Management in the Core Module. It asks a provider to show a plan, or a matrix, that maps who needs which training and by when.
In short: a spreadsheet can technically satisfy this on the day it's built. What most providers can't produce is one that still matches reality six months later.
What a plan or matrix needs to show
At minimum: who a course applies to, when it's due, and whether it's been completed. A matrix format usually lays this out as a grid, courses against people or roles, so gaps are visible at a glance. A plan format usually lists it as a named set of courses with dates attached. CORA's Pathway Builder produces both properties in one object: a named, ordered plan, with a due window on every course, which is exactly what a matrix maps.
How CORA builds one that doesn't drift
A pathway is a named, ordered list of courses. Each course carries its own due window, expressed in days from when a person was put on the pathway, so a new starter in August gets the same plan on the same clock as one who started in March, with no dates to work out by hand.
Order the courses so foundational material genuinely comes first, rather than sitting first by accident of when someone added it. Mark specific courses for team leads only, so one pathway can serve a whole team while a handful of its courses apply only to supervisors, instead of maintaining a general plan and a separate leaders' plan that drifts out of step with it.
Assign the finished pathway to a person directly, or to a whole team. This is the part worth understanding properly:
Assign a pathway to a team and it keeps applying. Someone who joins the team in November is on the pathway in November, with their own due dates.
Nobody has to remember to add the new starter to the plan. Membership is resolved live, so the moment someone joins the team, they're on the pathway, with their own clock already running.
The plan and the evidence agree, because they're the same object
The NDIS training indicator asks for a training plan. In CORA the plan and the evidence of following it are the same object, so they agree by construction.
Most providers keep the plan in one place, a spreadsheet, and the evidence of whether anyone actually did the training somewhere else, a folder of certificates. The two drift apart because they're never the same record. In CORA, progress against the pathway feeds directly into the training register and the completion summary, so there's nothing to reconcile between what was planned and what happened.
Start from a CORA pathway, or build your own
CORA publishes ready-made pathways covering common combinations of support needs, and any provider can start from one rather than building a plan from a blank page. A published pathway can't be edited by any one provider, so a provider tidying their own copy of it can never accidentally change what every other provider using it sees.
Finished with a pathway, or replacing it with a newer one? Archiving takes it off the list of pathways a provider can newly assign, and nothing else changes.
Archiving a pathway takes it off the picker. Everyone already on it keeps it, because training history is the one thing a provider cannot reconstruct.
Tidying a list should never be able to destroy a record. Archiving in CORA can't.
Common questions
What is an NDIS training matrix?
A training matrix maps who needs which training and by when, usually as a grid of courses against people or roles. The gazetted indicator accepts a matrix or a plan as the same requirement.
Do I need a training plan or a training matrix?
The indicator accepts either. CORA's Pathway Builder satisfies it either way: a named, ordered plan per pathway, with a due window on every course, which is exactly what a matrix maps.
What happens to training history if I stop using a pathway?
Archiving a pathway takes it off the picker. Everyone already on it keeps it, because training history is the one thing a provider cannot reconstruct.
Does a training matrix have to be a spreadsheet?
No. The indicator accepts any plan or matrix that maps who needs which training and by when. A spreadsheet satisfies it on the day it is built. CORA's Pathway Builder produces the same artefact and updates it automatically as people join or leave a team.