Guide
The PBS Capability Framework: keeping a practitioner's level current, not reconstructing it
The Positive Behaviour Support Capability Framework is published by the NDIS Quality and Safeguards Commission, and it is not hard to find. What is hard is the part nobody publishes: keeping a practitioner's capability current between the day they self-assess and the day somebody asks for the evidence.
This is a working note on how to do that. It is not legal advice, and the Commission's own documents are the authority on every requirement described here.
What the framework actually is
The framework describes four levels of practitioner — Core, Proficient, Advanced and Specialist — and, for each level, the capabilities expected across seven domains of behaviour support practice:
- Interim Response
- Functional Assessment
- Planning
- Implementation
- Know It Works
- Restrictive Practice
- Continuing Professional Development and Supervision
The knowledge and skills in each domain are split in two: a first section covering what is considered core to being a behaviour support practitioner at all, and a second covering what is expected of a practitioner rated proficient or above.
Two things follow from that structure, and they are the ones most practices get wrong.
A level is not a qualification. It is a description of demonstrated capability across seven areas at once. A practitioner does not become Proficient by finishing a course; they are Proficient when there is evidence across the domains that says so.
The seventh domain is about the other six. Continuing professional development and supervision is itself a capability domain — which means the record of how a practitioner is developing is not administrative overhead sitting beside their practice. It is part of the practice being assessed.
What the self-assessment asks you to hold
The Commission publishes a self-assessment tool and a resource guide for it. Practitioners work through the domains at their level and rate themselves, with evidence.
Filling it in takes an afternoon. That afternoon is not the problem.
The problem arrives eleven months later. The self-assessment is a photograph of one day. Everything it asserted keeps moving: supervision sessions happen or do not happen, professional development is completed, a practitioner starts working with restrictive practices for the first time, someone moves from writing interim plans to writing comprehensive ones. By the time the evidence is requested, the document on file describes a practitioner who no longer exists — usually a more junior one than the person now doing the work.
So the practice does what practices do: it reconstructs. Somebody goes through a year of calendars, inboxes and certificates to rebuild a picture of what was already true. That week is expensive, and nobody pays for it.
The distinction that matters
A self-assessment is a record of what you decided about a practitioner. What gets asked for at audit is what happened.
Those are not the same document, and a spreadsheet cannot hold the second one. A spreadsheet holds a field. It can tell you that a practitioner is rated Proficient in Functional Assessment. It cannot tell you that the rating was reviewed after supervision on a particular date, by a named supervisor, against a particular piece of work — because that is not a field, it is a sequence of events with people attached.
This is why capability records decay in a way that other records do not. A credential has an expiry date, so a calendar reminder is enough. A capability has no expiry date. It just quietly stops being true.
What "current" means in practice
For a practitioner's level to be defensible on any given day, five things need to be true, and each needs to be evidenced rather than asserted:
- The self-assessment exists and has a date on it. An undated assessment cannot be shown to be current.
- Supervision is recorded, not remembered. Who supervised, when, and what was discussed. The seventh domain is not satisfied by a supervisor's recollection.
- Professional development is tied to a domain. "Twelve hours of CPD" answers a different question from "what has this practitioner developed in Functional Assessment this year". The framework is organised by domain, so the evidence should be too.
- A change in scope changes the record. The first time a practitioner works on a plan involving a regulated restrictive practice, their Restrictive Practice domain evidence changes that day — not at the next annual review.
- Someone other than the practitioner has confirmed it. A self-assessment is, by definition, self-reported. What makes it hold up is the supervisory confirmation sitting beside it.
A method that survives a year
None of this requires software. It requires that the record is produced by the work rather than compiled from it. Whatever you use, the test is the same: when a practitioner completes supervision, does the capability record change by itself, or does someone have to remember to update it?
If the answer is "someone has to remember", the record will be wrong within a quarter. Not because the team is careless — because that update has no natural moment. It is a second job, done after the first one, for a document nobody reads until an auditor does.
The practices that stay current do one of two things. Either they run a fixed cadence and treat capability review as an agenda item in supervision itself, so the update happens while the evidence is fresh and the person is in the room. Or they use a system where completing the work is the update, and there is nothing separate to remember.
The first costs discipline. The second costs money. Both work; doing neither does not.
Where a system earns its place
This is what NDPRO is built to do for the seventh domain, so treat the rest of this section as interested rather than neutral.
In NDPRO, a practitioner's capability against the framework is a live record rather than a filed document. Supervision sessions and professional development are logged as they happen, against the domain they belong to, and a practitioner's CPD record builds itself out of work the practice is already capturing — which matters mostly because it means the practitioner has a reason to keep it current that has nothing to do with compliance. A supervisor confirms capability against a domain, and that confirmation carries the date and the person, because an unattributed confirmation is not evidence of anything.
What it deliberately does not do is give you a score. There is no percentage, no green tick and no certificate saying a practitioner is compliant. It shows what is outstanding and who it belongs to. A number would be a judgement the Commission makes, not a judgement software gets to make on its behalf — and a dashboard that grades you is a dashboard your team stops opening.
What this does not cover
Capability is one part of a much larger obligation. This note says nothing about behaviour support plan quality, about the authorisation of regulated restrictive practices — which is governed state by state and is a separate problem — or about the Commission's reporting requirements. Those each deserve their own treatment.
And the framework itself is revised. Check the version on the Commission's site against the one your practice assessed against, because a self-assessment against a superseded version is a document that looks current and is not.
Related: behaviour support supervision, and what has to be on the record · the state-by-state restrictive practice authorisation problem · what an auditor asks for under Module 2A · behaviour support as a sole trader.
Source: NDIS Quality and Safeguards Commission, the Positive Behaviour Support Capability Framework. Read 28/08/2026. The framework is revised from time to time; check the current version before relying on any summary, including this one.