Restrictive practices documentation: what software needs to handle

Restrictive practices — defined under the NDIS as any practice that restricts the rights or freedom of movement of an NDIS participant — represent one of the most legally and ethically complex areas in disability support. The NDIS regulatory framework requires that any use of a regulated restrictive practice must be authorised under the relevant state or territory law, implemented as part of a behaviour support plan developed by a qualified behaviour support practitioner, and reported to the NDIS Quality and Safeguards Commission. Software that supports providers delivering supports to participants with behaviours of concern must be capable of managing this entire compliance chain, not merely storing a document that says a plan exists.

The behaviour support plan is the foundation of lawful restrictive practice use. It must be developed by a registered NDIS behaviour support practitioner, must include a functional behaviour assessment, must identify the behaviours of concern, must specify the regulated restrictive practices that are authorised for use, and must include a clear pathway for reducing or eliminating restrictive practice use over time. The plan is not static — it must be reviewed at least annually, and more frequently when there is a change in the participant's circumstances or when an incident involving a restrictive practice occurs. Software must track plan version history, review due dates, and the approval status of each version.

State and territory authorisation requirements create a compliance complexity that software must navigate carefully. Each jurisdiction has its own authorisation pathway — in some states, a guardian or tribunal must authorise the use of regulated restrictive practices; in others, the consent of the participant or their nominated representative may be sufficient depending on the category of restriction. Software serving providers across multiple jurisdictions must be capable of recording the jurisdiction-specific authorisation status for each participant and alerting staff when a restrictive practice is being implemented without current authorisation. The use of a regulated restrictive practice that is not currently authorised is a reportable incident under the NDIS rules.

Implementation monitoring is an area where compliance failures commonly occur. A behaviour support plan may be impeccably documented, but if frontline staff are not implementing it as written — or are implementing restraints that are not included in the plan — the provider is exposed to serious regulatory risk. Software supports implementation monitoring through progress notes that are linked to the behaviour support plan, prompts for staff to record restrictive practice use in structured formats, and exception reporting that flags when recorded practice use differs from what the plan authorises. This is not a feature for large providers only; it is a requirement for any provider whose participants have a behaviour support plan in place.

Reporting obligations to the Commission require providers to submit monthly reports on the use of regulated restrictive practices for each participant. These reports must specify the type of restrictive practice used, the frequency of use, the duration of each episode, and the circumstances in which it was used. Generating these reports manually — by reviewing progress notes and tallying instances — is error-prone and time-consuming. Software that captures restrictive practice use in structured fields at the point of recording can generate monthly reports automatically, with the additional benefit that the underlying data is available for the internal audit and review processes that good governance requires. Providers who manage this data in free-text notes will find the reporting burden unsustainable at any meaningful scale.