Most support workers dread incident reports. They’re stressful to write, they take time, and the stakes feel high. But here’s the thing: a well-written incident report doesn’t get you in trouble. It protects you. It shows you followed the right steps, notified the right people, and documented what happened while it was fresh.
A poorly written one — or worse, no report at all — leaves gaps that can be filled by assumptions, complaints, or audit findings. Your record is your defence. Make it count.
The 6 reportable incident categories
Under the NDIS (Incident Management and Reportable Incidents) Rules 2018, there are six categories of incidents that must be reported to the NDIS Quality and Safeguards Commissioner.
What your incident record must include
Section 12(2) of the Incident Management Rules sets out the minimum fields for every incident record. This isn’t optional — it’s a legal requirement.
Required fields
The mistakes that leave you exposed
The most common mistake is documenting that something happened without documenting what you did about it. “Participant fell in the bathroom” is not an incident report — it’s a sentence. Where are the actions taken? Who was notified? Was there an injury? Was a physical check done? Did you call an ambulance or decide it wasn’t needed, and why?
The second most common mistake is waiting. Incident records should be made as soon as possible after the event. Details fade. If you write the report two days later, you’ll forget the exact time, the exact sequence, what was said. Write it while it’s fresh — even rough notes that you clean up later are better than a delayed report from memory.
The third mistake is not classifying the incident. Every incident should be assessed against the six RI categories. Even if you’re not sure whether it meets the threshold, document your reasoning. “Provider to assess whether this meets RI2 threshold” is far better than no classification at all.
Your record is your protection
When an incident is investigated — whether by your provider, the NDIS Commission, or in a complaint — the first thing they look at is the documentation. If you wrote a thorough record at the time showing what happened, what you did, and who you told, you’re protected. If the record is thin, vague, or missing, the narrative gets written by someone else.
Good incident documentation isn’t about covering yourself. It’s about showing that you responded appropriately to a difficult situation and that the participant’s safety was your priority. The paperwork is just the proof.
Clio detects and documents incidents automatically
Describe your shift in plain English. If an incident occurred, Clio flags it, classifies it against the 6 NDIS categories, generates the required documentation fields, and adds follow-up actions — all from your description.
Try Clio for free →