HelpAlong e-Brochure 
In the NDIS, incident reports are not just another task on your shift. They are one of the most important ways we keep participants safe, protect staff from allegations, and make sure the organisation is meeting its responsibilities. But many support workers still feel unsure about writing them. Some fear that reporting an incident will get them in trouble. Some think an incident must be “serious” before it deserves a report. Others feel embarrassed about their English skills and worry their writing won’t be perfect.
The truth is simple: you never get in trouble for reporting an incident. You can get into trouble for not reporting one. An incident report is there to protect you, not blame you. It shows what you saw, what you did, and how you responded. If someone later asks what happened, your report becomes your evidence. Without it, you are left with no written record to support you.
Across the disability sector, we know that many events never get reported. Audits and reviews show that 25% to 40% of incidents go unreported. This includes early signs of behavioural changes, refusals of medication, missed medications, sleep issues, changes in routine, WHS hazards, sensory triggers, refusals to engage with therapy or appointments, incontinence events, medical concerns, and maintenance issues. When these moments are not written down, the NDIA only sees a calm, safe, incident-free picture of the participant. But that picture is not real. Because the NDIA relies on written evidence, missing reports often lead to reduced funding, fewer support hours, and reduced staffing ratios. When funding drops, the participant loses the supports they truly need. And workers lose shifts because the house no longer has enough funded hours.
Writing an incident report does not require perfect English. It does not require long paragraphs. What matters most is that the report is factual, clear, and truthful. This means you should write only what you saw, heard, or did. Do not add assumptions about why the participant behaved a certain way. Do not include opinions about what you think they were feeling or what you believe caused the behaviour. If you did not see it, do not claim it happened. If you are unsure, say you are unsure. Factual reporting protects you. Opinions create risk.
For example, instead of writing, “He was angry because staff upset him,” a factual report would say, “Participant raised his voice, paced around the lounge room, and hit the table with his hand after being reminded that it was time for his shower.” The first version is an opinion. The second is a fact. The NDIA, managers, and behaviour practitioners can only trust reports when they are factual, not emotional or personal.
One of the most important parts of any incident report is explaining what was happening before the incident. These details help identify patterns and triggers. Maybe the participant refused medication earlier in the day. Maybe they had no sleep the night before. Maybe their routine changed. Maybe they encountered a loud noise, bright lights, or a stressful phone call. Maybe the house had a maintenance issue that affected them. These small details help behaviour practitioners create better strategies and help the NDIA understand the true level of need. Without these details, the picture is incomplete, and the participant’s support can suffer.
Incident reports also protect staff. If a complaint or allegation is made later, the very first thing supervisors, auditors, or investigators will ask for is documentation. When you submit a clear, factual report, you protect yourself from blame. When you do not report, you leave yourself vulnerable. A simple, honest record is your strongest defence.
A common question support workers ask is, “How do I know if something is an incident?” The answer is straightforward: if you are unsure, report it. It is always better to have a report than to realise later that something important was missed. No one ever gets into trouble for reporting too much. But many people have faced consequences because something was never written down.
Incident reporting makes everything safer. It helps ensure that the participant continues to receive the right funding and support. It allows organisations to meet NDIS quality and safety standards. It helps behaviour support practitioners do their jobs properly. And most importantly, it protects the support worker by creating a written record of what really happened.
Support work is challenging and meaningful. Incident reports are not there to punish you; they are tools that help you, your participants, and your coworkers. When you write clear, factual reports, you protect everyone involved and strengthen the quality of care the participant receives.
So when something happens — big or small — take a moment to write the incident report. Keep it simple. Keep it factual. Keep it honest. Your participant needs it. Your team needs it. And you will be grateful later that you took the time to put the truth on paper.
