Most NDIS providers document incidents one at a time. An incident happens, a report is filed, the right people are notified, and the file moves on. But nobody is looking at the incidents together. Nobody is asking: is this the same type of incident happening every two weeks? Are they always at the same time of day? Is the frequency going up or down?

That’s what an incident summary report does. It pulls every incident from a reporting period into one document and looks for the patterns that individual reports can’t show.

Why patterns matter more than events

A single head-hitting incident is concerning. Two head-hitting incidents in a month is a pattern. Two head-hitting incidents that both happened in the morning after poor sleep — that’s actionable intelligence. The BSP review should consider scheduling sessions for afternoons. The team should be briefed about the sleep correlation.

Without a summary report, these patterns stay invisible. The incidents exist in separate files, written by different workers, filed on different dates. Nobody reads them side by side. The pattern is only visible when someone compiles them — and most providers don’t have time to do that manually.

What this looks like

Here’s an incident summary report generated from 24 sessions of signed progress notes:

Incident Summary — Misa Tanaka
1 Jan 2026 — 7 Mar 2026 · 3 reportable incidents · Generated by Clio
Incident Overview
RI2 — Serious Injury × 2Restrictive Practice Used × 1Elopement × 1
Incident 1 — 7 February 2026
Category: RI2 — Serious Injury
Description: Head hitting episode during morning transition. De-escalation attempted with weighted blanket, chew necklace, quiet space. Physical restraint used per BSP (seated hold, 3 minutes). Participant bit worker’s arm during restraint.
Actions taken: First aid applied. Supervisor notified same day. Incident form submitted.
Incident 2 — 21 February 2026
Category: RI2 — Serious Injury
Description: Head hitting in swimming pool change room. Triggered by loud hand dryer and echoing noise. Small abrasion on forehead.
Actions taken: Guided to quiet area. Weighted blanket applied. Episode resolved without restraint. Parent notified.
Incident 3 — 5 March 2026
Category: Elopement
Description: Ran toward car park after seeing water fountain. Wrist link prevented reaching road. No injury.
Pattern Analysis
Head hitting frequency has decreased from weekly (Jan) to fortnightly (Feb–Mar). Both head hitting incidents occurred in the morning after poor sleep. No head hitting incidents during afternoon sessions. Swimming pool change room identified as a high-risk sensory environment. Elopement continues to be triggered by water.
Recommendations
Schedule sessions for afternoons where possible. Pre-visit change rooms before swimming sessions. Continue wrist link for all community outings near roads or water. Update BSP with swimming pool change room as a known trigger.

That summary took seconds to generate. A coordinator doing this manually would need to read through every note from the period, find the incident entries, cross-reference them, identify the patterns, and write the analysis. That’s hours of work for one participant — and most providers have dozens.

When you need an incident summary

Plan review meetings — the NDIA wants to know about incidents and safety during the reporting period. BSP reviews — the behaviour support practitioner needs incident data to assess whether current strategies are working. Provider audits — auditors check that incidents are being tracked and patterns are being identified. Team handovers — incoming workers need to understand the safety landscape.

In all of these situations, having a compiled summary report is infinitely more useful than asking someone to read through three months of individual notes.

Generate incident summary reports with one click

Clio pulls every incident from your signed progress notes, categorises them, identifies patterns, and generates a structured summary with recommendations — ready in seconds.

Try Clio for free →