Guide
Behaviour support supervision: what has to be on the record, and who confirms it
Search for behaviour support supervision and every result on the first page is someone selling the sessions themselves — a consultancy offering clinical supervision to practitioners who need it. That is a real service and a fair number of practices and sole traders need to buy it. It is also not the question this note answers.
This is about the record: what has to exist once the session happens, who has to confirm it, and why a practice that runs supervision well can still fail this on paper.
Not legal advice; the Commission's own documents are the authority on everything below.
Supervision is not a courtesy. It is a capability domain.
The Positive Behaviour Support Capability Framework organises what a practitioner has to demonstrate into seven domains, and the seventh is Continuing Professional Development and Supervision. That placement is deliberate: supervision is not administrative overhead sitting next to a practitioner's practice, it is one of the things being assessed as part of it.
The same requirement surfaces again inside Module 2A of the Practice Standards, under the outcome covering behaviour support plan review — implementation is monitored "through formal and informal means", and supervision is named explicitly among them, alongside participant feedback and data collection. Two separate parts of the framework independently land on the same record.
What "the record" actually has to contain
A supervision session that happened and was never written down is, for audit purposes, indistinguishable from a session that never happened. What makes a record usable is not that a session occurred — it's that four things are attached to it:
- Who supervised, and their own standing to do so. A supervisor's own capability level matters; a practitioner cannot be meaningfully supervised by someone with less standing than the framework expects for the domain in question.
- When, and how often. A single session eleven months ago is not "regular supervision" by any reading of the standards, and a gap is exactly what an auditor is trying to find.
- What was actually discussed, attributed to the case or the domain it touched — not a generic "supervision occurred" entry.
- A confirmation, separate from the practitioner's own note. The seventh domain, like the other six, distinguishes between what a practitioner reports about themselves and what someone else has confirmed. A self-written note is a diary. A supervisor's sign-off is evidence.
Where this fails in practice
Not from a lack of supervision — most practices that fail this genuinely run the sessions. It fails on the record, in one of three predictable ways.
It lives somewhere that isn't attached to anything. A calendar entry, a shared notes doc, a supervisor's own private file — none of these produce a record that can be pulled per practitioner, per domain, on demand. When it's requested, someone has to go and reconstruct it.
It records that supervision happened, not what changed because of it. "Session held 14 March" answers a different question from "capability in Functional Assessment reviewed and confirmed, 14 March, by [supervisor]". Only the second is the kind of evidence Module 2A's plan-review outcome is actually asking for.
Nobody notices when someone falls behind. Supervision that runs on individual memory rather than a visible schedule tends to go to whoever is loudest about needing it, not whoever is actually overdue — and a practitioner who has quietly gone three months without a session is invisible until someone asks.
The sharper version of this problem: going solo
If you are a sole trader, or applying through the Commission's new entry-level pathway, supervision stops being something a practice arranges around you and becomes something you have to arrange and evidence yourself — including, for some applicants, a specific requirement to engage a proficient-level practitioner for clinical oversight before the Commission will consider you suitable at all. That condition, and the twelve-month reconsideration clock that follows it, is its own topic: see going solo as a behaviour support practitioner.
The portfolio of evidence, and what a supervisor is actually signing
There is a second, more formal place this same record gets used, and it is worth naming precisely rather than folding into "supervision" generally.
Under the Commission's self-assessment pathway, a practitioner rates themselves against the framework using the Self-Assessment Tool and builds a Portfolio of Evidence to support that rating. Their supervisor then reviews the ratings and the portfolio, the two of them discuss whether they agree on the level being claimed, and — if the supervisor decides the practitioner meets it — the supervisor completes the Supervisor Endorsement Tool. That endorsement is what turns a self-assessment into something the Commission will act on.
None of that works without exactly the record described above. A supervisor endorsing a level they have not actually observed evidence for is not a formality, it is the one failure mode the whole two-step design exists to prevent — self-assessment plus independent endorsement, not self-assessment alone. Which means the ongoing discipline of dated, attributed, supervisor-confirmed sessions is not separate from the portfolio: it is the portfolio, assembled as it happens rather than reconstructed the week the endorsement is due. A practice that has been keeping the record this guide describes is not doing extra work when a self-assessment comes around — it is handing a supervisor evidence that already exists.
Where NDPRO fits, and where it does not
Treat this section as interested rather than neutral: this is what NDPRO's supervision record is built to do.
Every session is logged against the practitioner and the domain it touched, with a named supervisor attached to the confirmation — not a self-report standing alone. The practice sees who is overdue, sorted by how long it has been since their last session, rather than relying on anyone remembering. A practitioner sees that a session happened and what was covered; a supervisor's own private note stays private, because a record a practitioner can edit is not independent confirmation of anything.
What it does not do: it does not decide who is fit to supervise, and it does not make a supervision session happen. That part is still a person, in a room or on a call, doing the work. The record is downstream of that, not a substitute for it.
Related: keeping a PBS capability record current · what Module 2A asks for, outcome by outcome · behaviour support as a sole trader.
Sources: NDIS Quality and Safeguards Commission — the Positive Behaviour Support Capability Framework, the Supplementary module: Implementing behaviour support plans, and the Self-assessment resource guide for the Positive Behaviour Support Capability Framework. Read 01/09/2026, portfolio/endorsement section added 02/09/2026. All three are revised from time to time; check the current versions rather than relying on any summary, including this one.