Build a learning pathway for your team.
The Pathway Builder is a free, no-sign-up tool that maps CORA's courses to your actual team from a short support profile. Tell us about who you support and your team. We'll map it to the CORA courses your workers and team leaders need. No identifying information required.
The Pathway Builder is free to try here, and free on every CORA plan. Inside the provider portal it becomes the real thing: pathways assigned by role or site with per-course due dates, automatic due, overdue and renewal reminders, a credential and evidence register alongside them, and the records you export for audit.
Your learning pathway
What the Learning Pathway Builder does
Most training plans in disability support are built the wrong way round. A provider chooses a set of courses once, assigns the same set to everyone, and then finds on shift that the worker supporting a person with dysphagia and a behaviour support plan completed exactly the same induction as the worker doing two community access shifts a week. The gap is not effort. It is that nothing connects the person being supported to the training the worker in front of them actually needs.
The Pathway Builder starts from the person. You describe the participant's diagnoses and presentations, how they communicate, which behaviours and health needs are present, the setting the support happens in, and what is going on in the team around them. Eleven questions across three sections, four of them required. The builder maps that profile against CORA's library of 90+ scenario-based NDIS courses and returns a course list with a reason attached to every course, so the recommendation can be argued with rather than taken on trust.
Who builds a pathway
Usually the service manager, team leader or practice lead, or whoever holds the training register. It takes a few minutes, needs no sign-up, and asks for no identifying information about the participant. Support coordinators and behaviour support practitioners use it a second way: to show a provider what a team would need to hold before a new participant starts, rather than after the first incident report.
What a finished pathway contains
- A profile summary restating what was described, so the reasoning behind the list is visible.
- A frontline foundation list. The courses every worker supporting this participant should hold.
- A tailored list. The courses that exist only because of something specific in this profile, each with a one-line rationale.
- A team leader list, shown when the continuity and staffing answers call for it and kept separate so supervisor content is never pushed at frontline workers.
- The baseline stated in writing. CORA's Compliance Foundations, covering rights, safety, documentation and professional conduct, are treated as already completed by every worker, and the pathway sits on top of them rather than repeating them.
The whole thing prints to a clean A4 sheet with the reference you typed at the top, so it can go straight into a planning meeting, a handover pack or a service agreement conversation.
How a pathway gets assigned
Nothing is assigned automatically, on this page or inside the portal. The list is a recommendation, and a questionnaire will always know less about a participant and a team than the person filling it in, so the expected next step is to add, remove or reorder before anything reaches a worker.
For providers with a CORA portal, Add to my CORA portal carries the course codes across and creates a named pathway waiting for confirmation. Only the course codes and the reference you typed travel in that link. The answers, the diagnoses and the setting stay on this device. From there the pathway behaves like any other in CORA: assign it by role, by site or to an individual worker, set per-course due dates, and let due, overdue and renewal reminders run without anyone chasing them. Completions land on the same worker record as the credential register, the policy acknowledgements and the supervision history, and export together as a training register.
Where a pathway stops
The builder recommends training. It does not assess anyone, and completing a pathway is not a statement that a worker is competent to deliver a support. That sign-off stays with your own qualified assessor, and for high intensity supports it is generally clinician-led. Where a participant has a behaviour support plan or a mealtime management plan, the plan-specific training that goes with it sits alongside a pathway, not inside it.
Learning Pathway Builder FAQ
Yes. It is free to use on this page with no sign-up and no email required, and it is included on every CORA plan at no extra cost. The generated pathway can be printed or saved whether or not you are a CORA customer.
No. The builder asks about presentations, needs and setting, never about a name, address or NDIS number. The optional reference field stays on your device, prints on the pathway, and is not sent anywhere. Follow your own data-handling policy and participant consent as you would for any planning document.
A few minutes. There are eleven questions across three sections, covering the participant, the support and the team, and only four of them are required. The more you answer, the more specific the tailored list becomes.
Yes, and you are expected to. Nothing is assigned automatically. Courses can be added, removed or reordered here and again inside the portal before anything is sent to a worker.
No. A pathway builds the underlying knowledge a worker brings to a plan. Training in a particular behaviour support plan, mealtime management plan or high intensity support procedure is separate, is specific to that person, and sits alongside the pathway rather than inside it.
Inside the portal, each course completion is dated and timestamped on the worker's record and appears in the training register, which exports as PDF or CSV alongside the credential register and the policy acknowledgement trail. CORA does not guarantee an audit outcome, which depends on your whole quality system.