Why incident reporting is different for independent workers
If you’ve worked for a registered provider, you’ve probably experienced their incident reporting process. Something happens, you tell your supervisor, they fill out the incident form, and the provider handles the notification to the Commission if required. The documentation burden falls mostly on the provider’s systems.
On a platform, you don’t have that safety net. You’re the one who was there. You’re the one who needs to document what happened. And after mandatory registration, that documentation needs to meet the same standard that registered providers are held to under the NDIS Incident Management Rules.
The platform will have its own incident reporting process, but the initial documentation — the case note that captures what happened during the session — is yours to write. If that documentation is incomplete, vague, or missing key details, it creates a compliance problem that starts with you.
The six categories of reportable incidents
Not every incident is a reportable incident. The NDIS defines six specific categories that trigger mandatory notification to the Commission. Understanding these categories helps you recognise when something that happened during your session crosses the threshold from “something to document” to “something that must be reported.”
1. Death of a participant
Any death of a participant during or connected to the delivery of supports. Notification must be made within 24 hours.
2. Serious injury
Serious injury during or connected to the delivery of supports. This includes injuries requiring hospitalisation, fractures, head injuries, burns, or any injury with lasting impact. Notification within 24 hours.
3. Abuse or neglect
Any form of abuse or neglect of a participant. This includes physical, emotional, financial abuse, and neglect such as failing to provide required supports, withholding medication, or leaving someone unsupervised when supervision is required. Notification within 24 hours.
4. Unlawful sexual or physical contact
Any unlawful sexual or physical contact with a participant, or assault of a participant. Notification within 24 hours. Note that unlawful physical contact with negligible impact may be excepted.
5. Sexual misconduct
Sexual misconduct committed against or in the presence of a participant, including grooming for sexual activity. Notification within 24 hours.
6. Unauthorised restrictive practice
Use of a restrictive practice that isn’t authorised under a behaviour support plan or State/Territory authorisation, or use that doesn’t comply with the conditions of the authorisation. Notification within 5 business days.
Your legal obligation: under Section 19 of the Incident Management Rules, workers must notify key personnel, their supervisor, or the designated person as soon as possible when they become aware of a reportable incident. On a platform, this means notifying the platform immediately — but your case note is the primary record of what happened.
What incident documentation needs to contain
Section 12(2) of the Incident Management Rules sets out the minimum information that must be recorded for every incident. Your case note should capture as many of these as possible from the session: a description of the incident including impact on or harm caused to the participant, whether the incident is or may be a reportable incident, the time, date, and place of the incident, names and contact details of persons involved, names and contact details of any witnesses, immediate actions taken including support to affected persons, and the name and contact details of the person making the record.
You won’t always have all of this information at the time of writing. That’s okay — document what you know and flag what needs to be completed. An incomplete record with clear gaps identified is far better than no record at all.
The difference between an incident and a behavioural moment
Not everything that goes wrong during a session is an incident in the NDIS sense. A participant getting upset, refusing an activity, having a meltdown, or damaging property are behavioural moments that should be documented plainly in your notes — but they don’t automatically trigger the formal incident reporting process.
The key question is: was someone harmed or at genuine risk of harm? A child throwing a toy is a behavioural observation. A child throwing a toy that hits another person and causes injury is a potential reportable incident. The same action can fall on either side of the line depending on the outcome.
Document behavioural moments in your notes so there’s a record. But reserve the formal incident classification and reporting for situations where actual harm occurred or there was genuine risk of harm to a person.
Restrictive practice documentation
If you used a restrictive practice during a session — and many workers don’t realise when they have — the documentation requirements are particularly detailed. Section 15(2) of the NDIS Restrictive Practices Rules requires a record that includes the type of practice used, who authorised it, the date and time it started and ended, the duration, the behaviour that led to it, less restrictive alternatives that were tried first, whether it was in accordance with the participant’s behaviour support plan, the impact on the participant, and who was notified.
Physical restraint, environmental restraint, seclusion, chemical restraint, and mechanical restraint are the five regulated types. Holding someone’s hands to stop self-harm, blocking a doorway, removing objects to control behaviour, and administering PRN medication for behavioural purposes can all constitute restrictive practices requiring this documentation.
Clio detects incidents and restrictive practices automatically. When you describe a session that involves an incident or a restrictive practice, Clio flags it, classifies it against the reportable incident categories, and generates the required documentation — including a full Section 15(2) restrictive practice record when needed. You describe what happened. Clio handles the compliance.
Build the habit before July
Most incidents are stressful. You’re managing a crisis, keeping someone safe, and trying to do the right thing in the moment. The last thing you’re thinking about is Section 12(2) minimum record-keeping fields. That’s exactly why you need a documentation system that handles the compliance structure for you — so when something happens, you describe it in plain language and the system ensures the right fields are captured.
Incident documentation, handled automatically
Clio Care detects incidents in your session description, classifies them against reportable categories, and generates the required documentation. You describe what happened. Clio handles the rest.
Start for free →