How to write an NDIS incident report (with examples)

Incident reporting is one of those things every provider knows they need and many do inconsistently. A good report is fast to write, sticks to facts, and gives you a clear record if anyone ever asks what happened. Here's how to do it well.

Incident vs reportable incident

An incident is any event that caused or could have caused harm to a participant in connection with your supports. A reportable incident is a specific subset that must be notified to the NDIS Quality and Safeguards Commission within set timeframes.

Reportable incidents generally include things like the death of a participant, serious injury, abuse or neglect, unlawful sexual or physical contact, sexual misconduct, and the use of a restrictive practice that isn't authorised. The exact definitions and timeframes are set by the Commission — keep their current guidance handy, because this is the category where getting it wrong matters most.

What a good report contains

• ✓Who was involved (participant, workers, witnesses) and their roles.
• ✓When and where it happened — date, time and location.
• ✓What happened, in plain factual language — what you observed, not what you assume.
• ✓What immediate action was taken (first aid, made safe, who was contacted).
• ✓Any injury or harm, and follow-up required.
• ✓Who was notified and when (participant's representative, your manager, the Commission if reportable).

Write facts, not interpretations

The single biggest improvement most reports need: separate what you saw from what you concluded. Compare these two.

"John was aggressive and refused to cooperate."

That's interpretation. Here's the same moment as fact:

"At 2:15pm John raised his voice, pushed his chair back and walked out of the room. He declined the offered support and said he wanted to be left alone."

The factual version is more useful, more respectful, and far stronger if the record is ever reviewed.

A worked example

Incident: Participant slipped in the bathroom during a morning support shift.

1. Observation: "At approximately 7:40am, while being supported with morning routine, [participant] slipped on a wet floor near the basin and fell onto their left side."
2. Immediate action: "I checked for injury, helped them to a seated position, and observed redness on the left elbow. No loss of consciousness. Applied a cold pack."
3. Notification: "Contacted [participant]'s sister and my coordinator at 8:05am. Recommended GP review for the elbow."
4. Follow-up: "Placed a non-slip mat in the bathroom and noted the wet-floor risk in the support plan for review."

Notice there's no blame and no guessing — just a clear sequence anyone could follow.

Close the loop

A report isn't finished when it's written. Good incident management includes reviewing what happened, identifying anything that could prevent a repeat, and recording that follow-up. That review step is exactly what distinguishes a provider who learns from one who just files paperwork.

For the definitive list of reportable incidents and notification timeframes, always check the current NDIS Quality and Safeguards Commission guidance.