How to Write an NDIS Incident Report (With Examples)

Last updated 2026 · SupportNotes · Made in Australia

What is an NDIS incident report (and why does it matter for you)?

An incident report is the written record of something that went wrong — or nearly went wrong — during a shift. A fall, a medication error, a participant getting hurt, two participants in conflict, an allegation, or even a near miss where nothing happened but easily could have.

Here is the part that matters most for you personally: that report is also your protection. If anyone ever asks "what happened and what did the worker do?", your words are the answer. A clear, factual, calm report shows you acted professionally. A vague, emotional, or blame-filled one can do the opposite — even when you did everything right.

So the goal is simple. Write down exactly what happened, in plain language, as if you are describing it to someone who wasn't there. Nothing more, nothing less. You are not deciding fault. You are recording facts.

• Protects the participant — gives the team what they need to keep them safe.
• Protects you — documents that you responded appropriately.
• Meets your legal obligations — the NDIS expects accurate records of incidents.
• Feeds improvement — patterns in incidents reveal risks before they get worse.

Reportable vs non-reportable: which incidents must go to the NDIS Commission?

This is the question that causes the most anxiety, so let's make it clear. Almost every incident gets written up internally. Only a specific group — called reportable incidents — must also be notified to the NDIS Quality and Safeguards Commission. The rest stay in your provider's internal incident register and are managed in-house.

You usually don't make the Commission notification yourself — your provider or registered manager does. Your job is to recognise when an incident might be reportable and escalate it to your supervisor straight away, so the clock doesn't run out. When in doubt, escalate. It is always safer to flag something that turns out to be minor than to stay silent on something serious.

• REPORTABLE (notify the Commission via your provider): the death of a participant; serious injury; abuse or neglect of a participant; unlawful physical or sexual contact; sexual misconduct toward a participant; and the use of a restrictive practice that wasn't authorised in the participant's plan.
• NON-REPORTABLE (internal register + incident management only): a fall with no serious injury, a minor medication error caught early, a participant becoming upset and then settling, property damage, or a near miss where no one was harmed.
• ALWAYS write it up regardless: even non-reportable events belong in your internal incident register — "non-reportable" does not mean "don't document it."
• If you are not sure which side it falls on: treat it as potentially reportable and escalate to your supervisor immediately.

The timeframes: the 24-hour rule and the 5-business-day rule

For reportable incidents, time is not on your side, and the most serious categories carry the tightest deadlines. As a rule of thumb that NDIS providers work to:

The exact deadline depends on the category of the incident and is set by the NDIS Commission, so always follow your provider's incident management procedure — but the practical takeaway is the same for you on the floor: tell your supervisor the moment you become aware of a serious incident. A report that sits in your head, or in a notebook, until the end of a long shift can quietly blow past the 24-hour window. Escalating immediately is what keeps your provider compliant and keeps you in the clear.

• Immediate / within 24 hours: the most serious reportable incidents (such as a death, serious injury, abuse or neglect, or unauthorised use of a restrictive practice) must be notified to the Commission within 24 hours of the provider becoming aware.
• Within 5 business days: a fuller written report is then provided to the Commission for the relevant categories, following the initial notification.
• Your part: report to your supervisor as soon as you become aware — the provider's clock often starts when the first staff member knows.
• If you missed a deadline: still report as soon as you can and note honestly why the delay happened. A late report is better than no report.

How to write the report: 7 sections that protect everyone

A strong incident report follows a predictable shape. You don't need fancy words — you need a clear, ordered account. Work through these seven parts and you will capture everything an investigator, manager, or auditor needs.

The golden rule running through all of them: describe what you observed, not what you assumed. "The participant raised their voice and pushed the chair away from the table" is an observation. "The participant was aggressive" is a judgement. Observations protect you; judgements can be argued with.

• 1. Incident summary — one sentence: what happened and when (use only the time you actually know).
• 2. Antecedents / context — what was happening right before, in plain terms. Don't guess why.
• 3. The incident — only what you saw and heard. Replace labels like "aggressive" or "meltdown" with the specific behaviour.
• 4. Worker response — the concrete actions you took, step by step. This is where you show you acted well.
• 5. Outcome — the participant's state and the environment afterward.
• 6. Notifications / escalation — who was told (supervisor, family, nurse, doctor, Commission if reportable).
• 7. Follow-up recommendations — practical next steps based only on what happened.

Objective language: the words that keep you safe

Most workers — especially if English is your second language — don't get into trouble for what they did. They get into trouble for how the note reads. A few habits make all the difference.

Cut three things entirely: your feelings ("I felt terrible"), your hindsight blame ("I should have noticed sooner"), and your guesses about the participant's mind ("he was angry because…"). None of these are facts, and all of them create liability. Replace labels with descriptions, and replace opinions with observations.

• Say what you saw, not what you concluded: "cried for several minutes" not "had a meltdown."
• Drop self-blame: "the incident was identified at 2:00 pm" not "I should have caught it earlier."
• Don't read minds: delete "because she was upset about…" — you cannot know motive.
• Use the participant's name or "the participant," never "client," "patient," or "resident."
• Keep your emotions out: an incident report records events, not how you felt about them.
• If a duty-of-care question exists, state the facts and the timing plainly — do not add words that argue fault either way.

Before and after: real incident report examples

Here is how a rough, honest first draft becomes an NDIS-aligned report — same facts, safer wording. Notice nothing is invented. We only fix the language.

These mirror the structure our free notes tool produces in its worker-protective Incident Report mode. The point is not to make the event sound better than it was — it's to record it accurately and professionally so it reads the way you actually behaved: like a careful worker.

A 60-second checklist before you submit

Run through this quick list before the report leaves your hands. It catches the mistakes that cause the most grief later.

• Did I write only what I saw and heard — no guesses about why?
• Did I remove my feelings and any "I should have…" sentences?
• Did I record the time accurately (and not invent a clock time I don't actually know)?
• Did I describe behaviour specifically instead of using labels like "aggressive" or "good day"?
• Did I clearly note what I did in response?
• Did I flag whether this might be a reportable incident and tell my supervisor?
• Would this report read well if a stranger — or an auditor — picked it up in two years?

Try the free worker-protective incident report tool

You don't have to get the wording perfect on your own. Our free notes tool has a dedicated Incident Report mode built specifically to protect support workers: paste your rough notes in plain or broken English, and it rewrites them into the seven-section, objective-language structure above — without inventing a single fact, time, or quote you didn't write.

It fixes the grammar, swaps labels for observed behaviour, strips out self-blame and emotion, and reminds you where escalation belongs. It's genuinely free, and it's designed for workers whose first language isn't English. Try it, then bring the polished report to your supervisor.

If you run or manage a SIL house or NDIS service, the same care needs to exist at the policy level — your incident management policy, incident register, and reporting workflow all need to be audit-ready. The $297 SIL Rescue Kit from our sister site NDISCompliant gives you 74 audit-ready, plain-English documents (including a ready-to-use Incident Report Form and Incident Register) mapped to the NDIS Practice Standards, with a 30-day refund. It turns "we should fix our paperwork" into "done."

• Free notes tool (Incident Report mode): on our homepage — paste rough notes, get an NDIS-aligned report.
• Never fabricates: keeps your facts, fixes only the wording.
• Built for ESL workers: plain English in, professional report out.
• Going further? The $297 SIL Rescue Kit covers the policies and forms behind the report.

Frequently asked questions