Case study · NDIS behaviour support
Keeping 15+ behaviour support practitioners audit-ready without adding a compliance role
A registered NDIS behaviour support provider running a clinical team of more than 15 practitioners and supervisors, with over 300 behaviour support plans under management, was tracking plan lodgement deadlines, supervision sign-off and restrictive practice reporting across spreadsheets and calendar reminders.
The delivered system makes compliance a by-product of clinical work rather than a parallel administrative task: evidence is captured as practitioners do their normal documentation, and obligations surface before they fall due instead of after.
The client is not named at their request. The organisation profile, volumes, measured outcomes and timeline are accurate as delivered. Figures are actuals, not projections, and none have been rounded up.
Who this was
A registered NDIS provider delivering specialist behaviour support, with a clinical team of more than fifteen practitioners and supervisors carrying over 300 active behaviour support plans across a mix of participant settings. Practitioners sit at different suitability levels, which means supervision requirements differ person by person, and the mix changes as people progress.
The problem as they described it
Not that compliance was being missed. That knowing whether it had been met required a person to go and check.
Behaviour support carries a dense set of time-bound obligations: interim plans due within a month of engagement, comprehensive plans within six, restrictive practice authorisations that expire on their own schedule, monthly reporting to the Commission, and supervision that has to be evidenced rather than merely happen. Each one was tracked somewhere: a spreadsheet, a calendar, a practitioner's own diary. None of them talked to each other.
The risk is not a practitioner forgetting. It is that nobody can answer "are we compliant right now" without a manual audit, so the honest answer, between audits, is always "we think so". For a provider under the NDIS Quality and Safeguards Commission, "we think so" is the position that becomes a finding.
The design decision that shaped it
The obvious build is a compliance dashboard: a system practitioners update so managers can see status. That design fails predictably, because it asks clinicians to do a second job, and the data is only as current as the last time someone remembered.
The system was built the other way around. Practitioners do their normal documentation: writing the plan, recording the session, noting the restrictive practice. Compliance state is derived from that work rather than entered alongside it. Nobody maintains a compliance record, because the compliance record is a view over what already happened.
What was built
- Obligation modelling per participant and practitioner: due dates derived from engagement events rather than typed in, so they cannot drift.
- Supervision evidenced as a by-product: sign-off attaches to the clinical artefact being reviewed, carrying who, what and when without a separate log.
- Restrictive practice register with authorisation expiry surfaced before it lapses, and reporting periods assembled from the underlying records.
- Practitioner suitability levels held as state, so supervision requirements adjust automatically when a practitioner progresses.
- An evidence trail on every derived status: each item shows what it was calculated from, which is what turns a dashboard into something defensible in an audit.
- Australian-hosted infrastructure, architected against the Privacy Act 1988 (Cth), with role-based access across the clinical team.
What changed
| Measure | Before | After |
|---|---|---|
| Answering "are we compliant right now" | Manual audit across several systems | A view, current by construction |
| Supervision evidence | Reconstructed when asked | Captured at the point of sign-off |
| Restrictive practice expiry | Calendar reminders, owned by individuals | Surfaced by the system before lapse |
In the client's words
We used to find out we had a problem when someone went looking for it. Plan deadlines lived in one spreadsheet, supervision sign-off in another, and restrictive practice authorisations in whoever's calendar had set the reminder. With 300 plans across the team, "are we on top of it" was a question nobody could answer without going and checking.
What changed is that nobody enters compliance information any more. It comes out of the clinical work we were already doing. Our practitioners write the plan, record the session, note the practice, and the obligations look after themselves.
The part I did not expect was being able to show how we knew something, not just that we knew it. When we were asked, the evidence was already there.