NDIS
NDIS Reportable Incident Register
How NDIS providers should structure incident and reportable incident records from intake through notification, investigation, corrective action and closure.
9 min read | 2026-05-14
Separate incident capture from reportable incident decisions
Every incident should be recorded, assessed and managed. Some incidents also require reportable incident handling. A strong register separates initial incident capture from the decision about whether regulator notification is required.
That distinction matters because staff need a clear way to escalate concerns quickly while the provider still records investigation, participant communication and corrective action.
Fields for an NDIS incident register
The register should capture the full lifecycle, not just the incident description.
- Incident ID, date, time, location, participant and workers involved.
- Incident category, severity and immediate action taken.
- Reportable incident status, notification due date and notification record.
- Participant, family, nominee or representative communication.
- Investigation owner, findings, root cause and evidence.
- Corrective actions, responsible person, due dates and closure status.
- Management review, lessons learned and improvement links.
Evidence that supports the register
An incident register is only audit-ready when it links to supporting proof. That may include statements, photos, clinical notes, correspondence, notification confirmations, staff debriefs and corrective action evidence.
- Incident report forms.
- Investigation records and witness notes.
- Commission notification receipts where applicable.
- Participant communication records.
- Corrective action evidence.
- Trend analysis and management review notes.
Next step
Want to see this inside an NDIS provider workspace?
Book a short walkthrough and we will map the guide to provider profile, Practice Standards, participant files, worker screening, incidents, complaints and audit-ready exports.