This page sets out what the indicator actually asks for, what a completed review needs to carry, and how CORA turns individual reviews into one cycle view across a whole team.
What the indicator asks for
The requirement sits among the Human Resource Management indicators a Certification audit adds on top of Verification, part of Provider Governance and Operational Management in the Core Module. In the Commission's own words:
"Worker performance is managed, developed and documented, including feedback and development opportunities."
The artefact that satisfies it: completed performance reviews on a regular cycle. Not one review, ever, for each person. A cycle, repeating, with a record left behind each time.
Three separate asks in one sentence
Read the indicator slowly and it's actually three requirements, not one.
Managed means ongoing, not a single event early in someone's employment and then nothing again. Developed means the review has to produce something forward-looking, an actual opportunity or a next step, not just a look back at the last few months. Documented means written down, on a worker's own record, not held in a manager's memory or a private notebook that leaves the building when they do.
A conversation that ticks all three from memory, once, doesn't satisfy this. A written cycle does.
What a completed review has to carry
Every completed performance review in CORA carries two things by design: an agreed development plan, the actual opportunities or next steps discussed and agreed with the worker, and a next-review date, so the cycle keeps going rather than ending the moment one review is filed.
Those two pieces are what turn a conversation into a record. A next-review date on its own is a diary entry. A development plan on its own is a note with no follow-up attached. Together, they're the artefact the indicator is actually asking for, evidence that performance is managed and developed, not just discussed once and left.
No rating, and that's deliberate
CORA's performance reviews don't produce a score or a pass mark for a worker. What they conclude in is the plan and the date, the same two things every time, for every worker, on every cycle.
That's a deliberate design choice. The indicator asks that performance be managed, developed and documented. It doesn't ask for a verdict, and a rating attached to every worker on file is the kind of thing that becomes a dispute waiting to happen rather than evidence that helps anyone. Keeping the review's conclusion to an agreed plan and a date keeps it about what happens next for that person, which is the part an auditor is actually checking for.
The cycle view: overdue, never reviewed, unscheduled
One screen shows the whole workforce against its review cycle, and it separates three genuinely different facts rather than folding them into one number. Overdue: a review was due and hasn't happened yet. Never reviewed: nobody has ever run one for this person. Unscheduled: a review's happened, but no next date has been set to keep the cycle going.
Those are three different problems with three different fixes, and a manager working down that list knows exactly which one they're looking at instead of a single count that hides which is which.
Where reviews sit inside supervision
A performance review is one of the combinable parts a supervision session can be built from, alongside a conversation and a Support Observation of practice actually watched on shift. Run a review on its own on its usual cycle, or fold it into a session that covers all three, and it still lands on the same worker record either way, ready for the same evidence pack.
Building the development side of the plan
The agreed development plan is only as good as what's actually available to put in it. Addressing Performance Issues in Support Work and Coaching and Feedback for Support Workers, both inside Leadership and Workforce Sustainability, are built for the team leads running these conversations: everyday accountability and useful feedback, not a scripted conversation nobody enjoys.
Every claim on this page is about a record CORA already holds and structures, checkable in a demo. See the standard we hold every claim on the site to.
Common questions
What has to be in an NDIS performance review record?
A completed review, on a regular cycle, carrying an agreed development plan and a next-review date. The indicator asks that performance be managed, developed and documented, and those two pieces are what document the second and third parts.
Does a performance review need a rating or score?
No. The indicator asks for performance to be managed, developed and documented, not rated. A CORA review concludes in an agreed plan and a next date, the same for every worker, every cycle.
Does this apply to a Verification audit or only Certification?
It sits among the requirements a Certification audit adds. Verification's fourteen requirements work from worker files and training records.
How do I find out who's overdue for a review?
One cycle view shows the whole workforce, split into overdue, never reviewed, and unscheduled, so you can see which problem you're looking at before you go and fix it.