Guide
Behaviour support supervision records for practitioners and directors
In short: NDPRO helps behaviour support teams keep dated supervision records and review progress against the cadence agreed for each supervision relationship. Records can identify the practitioner, supervisor, session date and optional notes or cases. Directors can review supervision activity alongside the practice’s wider capability records.
The operational questions are specific: when did supervision last occur, what schedule was agreed, and which relationships need attention? A calendar booking and a record of a completed session answer different questions.
NDPRO works standalone. Practices already using Splose can add an optional read-only connection; supervision recordkeeping does not depend on that connection.
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.
Specialist clinical supervision is addressed separately in section 38(4) of the Quality Indicators Guidelines. Module 2A plan review concerns monitoring a participant's plan implementation through several formal and informal approaches, which can include supervision. A session may contribute to either evidence trail when its content is relevant; its label or a domain tag alone does not establish either outcome.
A practical supervision record
The following is a suggested practice process, not a universal statutory format or a rule that every session must be separately countersigned. Keep records proportionate to your supervision agreement, applicable conditions and assessment pathway:
- People and purpose. Identify the practitioner, supervisor and the relevant supervision arrangement. Check the supervisor meets the requirements applicable to that arrangement.
- Date and agreed cadence. Record when the session occurred and review gaps against the agreed schedule. There is no single frequency asserted here for all practitioners or states.
- Relevant discussion and actions. Capture development areas, appropriate evidence references, owners and review points, with confidentiality controls.
- Review or confirmation where needed. Distinguish the practitioner's notes, a supervisor's feedback and formal endorsement. A self-authored note can contribute evidence; it is not by itself independent agreement with a capability rating.
Formal supervisor endorsement requirements for an applicable assessment pathway remain separate from routine session notes.
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]". The second adds information relevant to capability review. Neither statement alone demonstrates the participant's plan implementation was monitored under Module 2A; that needs evidence about implementation and its review.
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 reconsideration on the date specified by the Commission for a new-entry practitioner, 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 practitioner and supervisor complete the Endorsement Tool to document that agreement. The required tools go to the Commission with the application. The full portfolio is not routinely submitted, but the Commission may request supporting examples.
Supervision records can form part of a broader portfolio across the capability domains. The portfolio can also include relevant work samples, reflection and professional development. A supervisor reviews the ratings and supporting evidence as a whole; a set of attended sessions or domain tags is not the portfolio by itself.
Keeping dated records as work occurs makes evidence easier to retrieve. It does not remove the need to judge its relevance, sufficiency or suitability for the assessment pathway.
Separate oversight from confidential supervision content
A Director may need to know that supervision occurred and that an agreed action has an owner. That does not mean every Director should receive every confidential supervision note. Define visibility with the practitioner and supervisor, your policies and the applicable obligations; then test access in the actual product.
Synthetic example: a NSW practitioner and supervisor agree a fortnightly cadence. A session on 6 October identifies an assessment skill to develop. The agreed action is to review a de-identified work example at the next session. The operational record needs the session date, the two roles, the agreed action, its owner and review point. Confidential discussion can stay in its approved restricted location. A fortnightly cadence is the choice in this example, not a universal Commission requirement.
| Director review | Supporting evidence | Boundary to preserve |
|---|---|---|
| Was the agreed session held? | Dated record and responsible supervisor | A calendar invitation alone does not prove attendance |
| What agreed follow-up remains? | Action, owner and review point | Share only the information needed for oversight |
| Has the action been reviewed? | Review date and outcome | Completion is not a formal endorsement of capability |
| Can the appropriate reviewer retrieve the evidence? | Approved reference and access check | Do not expose identifiable case material in a sales demo or public checklist |
Use the supervision evidence worksheet for an internal review. It is an administrative aid; it does not replace a supervision agreement, professional judgement or the formal suitability process. See also how evidence links support capability review.
How NDPRO supports supervision oversight
The supervision workspace includes team views, review information and a session log. A session record can identify the supervised practitioner, the supervisor, the date, session type and optional cases or notes.
Weekly, fortnightly, monthly and ad hoc labels describe the recorded session. The cadence agreed for the relationship is tracked separately. Your practice can review the last recorded session and progress against that agreement.
Ask for a walkthrough using synthetic records: open the team view, inspect a supervision relationship and show which information belongs in the session log. Confirm visibility with the practitioner and supervisor; operational oversight does not require unrestricted access to confidential discussion.
Does recording supervision endorse a practitioner’s capability level? No. A dated session record can contribute to the evidence considered during review. It does not by itself endorse a capability level or establish practitioner suitability.
Core, Proficient, Advanced and Specialist are levels in the PBS Capability Framework. The NDIS Commission makes suitability decisions; it does not endorse capability levels. NDPRO helps organise the records for assessment and review.
See capability assessment and review records, PBSP-QA plan quality reviews and NDPRO for practice directors.
Related: PBSP-QA plan quality reviews in NDPRO · 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. Reviewed 20/10/2026. The self-assessment resource guide identifies itself as updated May 2021; the later upload path is not its issue date. All three are revised from time to time; check the current versions rather than relying on any summary, including this one.