This page sets out what the Human Resource Management indicators covering supervision actually ask for, and how CORA turns cadence, sessions and evidence into one register instead of a set of calendar reminders nobody's tracking against anything.
What does the NDIS supervision indicator ask for?
The Practice Standards' Human Resource Management requirements, part of Provider Governance and Operational Management in the Core Module, ask for:
"Timely supervision, support and resources are available, relevant to the scope and complexity of supports delivered."
The artefact that satisfies it: a supervision schedule, and records that supervision did occur. Two things, not one. A schedule alone is a plan. Records alone are a history with no way to see who's missing. Together, they're the register an assessor is actually asking for.
This one sits among the requirements a Certification audit adds on top of Verification, alongside position descriptions and performance reviews.
A second indicator lives inside the same record
"Worker performance is managed, developed and documented, including feedback and development opportunities."
That's the second Human Resource Management indicator this page touches, and it shares a register with the first because a performance review is one of the things a supervision session can be built from. See the full artefact this indicator needs, an agreed development plan and a next-review date on every completed review. Here, it's enough to know it lives in the same place: one worker, one supervision history, not two systems to keep in step.
Who decides how often supervision happens?
Supervision that's genuinely timely for a new starter in their first month looks different from what's timely for a casual who's worked the same three shifts for two years, and different again for a team lead running their own roster. CORA lets you set the cadence per employment type, new starter, casual, lead, or a default for everyone else, or set it explicitly to none for a category that doesn't need one.
Every register reading after that measures against the cadence you decided, not a generic interval CORA invented. Weekly, monthly, quarterly, whatever fits how your service actually runs. The record that comes out the other end is a plain fact: this worker was due on this date, and here's what happened.
How do I track overdue supervision across a workforce?
One screen shows who's overdue, measured against those settings, not a fixed number applied to everyone regardless of role. A new starter three weeks without their first session shows up differently from a long-serving lead who's a week past a quarterly check-in, because the cadence behind each of them is different too. See the whole roster at once, or narrow to one employment type to check how a specific cadence is tracking.
What is in a supervision session record?
A supervision session isn't one fixed form. It's built from parts you choose to include: a conversation, a Support Observation, watched on shift rather than reported after the fact, or a performance review. Combine what a particular session actually needs. A quick check-in might be a conversation alone. A quarterly session might carry all three. The record reflects what actually happened rather than forcing every session into the same template.
Feedback reaches the worker only when it's deliberately sent, so a supervisor's working notes and what a worker actually sees stay two different, intentional things.
What goes in a supervision evidence pack?
Pick a date range and print the lot, every session, every note, every observation and review that fell inside it, as one pack ready to hand to an assessor. That answers the register question in one document: not "do we do supervision" but "here's exactly what happened, for this person, across this period."
| Field | Why it is there |
|---|---|
| Worker name and employment type | Names the cadence the sessions inside the pack are measured against |
| Session dates in the chosen range | Shows the actual pattern, not a single sample session |
| Session type per entry | Conversation, Support Observation, performance review, or a combination |
| Topics or observations recorded | What the session actually covered, as topics rather than participant details |
| Development plan and next review date | Where a performance review sits inside the pack |
| Who ran each session | Named against every entry, not assumed |
How providers actually use this
Set cadence once, when a worker's employment type is confirmed, and the register starts measuring from their first day. Run the overdue view on the same weekly rhythm most services already use for rostering, so a missed session gets caught inside weeks, not discovered the month before an audit. Pull the evidence pack for a specific quarter before a mock audit, and you'll see exactly what a real one would ask for.
Team leads running supervision for the first time often pair it with Coaching and Feedback for Support Workers, built for exactly this conversation.
Every claim on this page is about a record CORA already holds, checkable in a demo against your own settings. See the standard we hold every claim on the site to.
Supervision sits alongside credentials, policies and the worker file inside CORA's HR software for NDIS providers, on one record rather than a separate system. Running supervision on paper for now? Grab the free supervision agenda template, no email required.
Common questions
What counts as an NDIS supervision record?
A schedule showing how often supervision is due for each worker, and records showing it actually happened, who ran it, when, and what it covered. Both halves are needed. A schedule alone or notes alone don't satisfy the requirement on their own.
Who decides how often supervision happens?
The provider. CORA holds the cadence you set for each employment type and measures every session against it.
Does the supervision indicator apply to a Verification audit?
It sits among the requirements a Certification audit adds. Verification's fourteen requirements work from your worker files and training records.
Can a supervision record include a performance review?
Yes. A supervision session is built from combinable parts, a conversation, a Support Observation or a performance review, so a worker's whole supervision history sits in one place rather than split across separate systems.