Reportable Incident Record Example for NDIS

What Is a Reportable Incident Record?

Under the National Disability Insurance Scheme Act 2013 and the associated NDIS (Incident Management and Reportable Incidents) Rules 2018, registered NDIS providers are legally required to maintain an incident management system. Within that system, every reportable incident must be documented in a structured record that demonstrates the provider identified the incident, notified the NDIS Quality and Safeguards Commission within the required timeframes, and followed through with an appropriate investigation and response.

For SIL and other disability-support providers, these records are among the highest-scrutiny documents examined during an NDIS audit. A poorly completed record — or one that is missing entirely — is a straightforward non-conformance against the NDIS Practice Standards, Core Module 2 (Incident Management).

What Counts as a Reportable Incident?

Not every untoward event is a reportable incident. The NDIS Commission defines the following as reportable incidents when they occur in connection with the delivery of NDIS supports:

• The death of an NDIS participant
• Serious injury of a participant
• Abuse or neglect of a participant
• Unlawful sexual or physical contact with, or assault of, a participant
• Sexual misconduct by a person carrying out work for the provider
• The use of a restrictive practice that is not in accordance with a behaviour support plan or that is used without authorisation

SIL providers in particular should note that the use of an unauthorised restrictive practice is itself a reportable incident, even when no physical harm occurs. This is one of the most commonly missed triggers at audit.

Notification Timeframes

Providers must notify the NDIS Commission as soon as practicable, and no later than:

• 24 hours — for incidents involving the death of a participant or incidents that are currently under police investigation
• 5 days — for all other reportable incidents

Initial notification can be made through the myNDIS provider portal or by telephone. A follow-up written report must then be submitted within the required window.

Mandatory Fields in a Compliant Record

A compliant reportable incident record must capture, at minimum, the following information. Missing any of these fields is grounds for an auditor finding:

1. Unique incident reference number
2. Date and time the incident occurred
3. Date and time the incident was identified or reported to management
4. Location of the incident (address or site name)
5. Category of reportable incident (from the list defined in the Rules)
6. Full name of the participant(s) involved
7. NDIS participant number
8. Name(s) of support worker(s) or other persons involved or present
9. Factual description of what occurred — written in plain, objective language
10. Immediate actions taken (first aid, emergency services contacted, participant removed from risk)
11. Who was notified and when (participant, substitute decision-maker, family/guardian where applicable, NDIS Commission, police)
12. NDIS Commission notification reference number and date submitted
13. Investigation status and assigned investigator
14. Outcome of investigation and findings
15. Corrective or preventive actions implemented
16. Date record was closed and approved by designated manager

Realistic Filled-In Example

The following is a realistic sample record. All names, dates, and details are illustrative only and do not represent real individuals or events.

What Auditors Check — and Common Non-Conformances

When an approved quality auditor reviews your incident management system against the NDIS Practice Standards, they are looking for evidence that your system is functional, not just documented. Common non-conformances identified at SIL audits include:

• Notification timeframes not met — the Commission submission date on the record shows a gap longer than permitted. Even by one day, this is a non-conformance.
• No participant reference number recorded — particularly common when incidents are entered by support workers who do not have system access to participant files.
• Corrective actions listed but not verified — the record states an action was taken, but there is no evidence of completion (no sign-off date, no photograph, no follow-up check).
• Subjective or emotive language in the description — phrases like "the participant was being difficult" or "nothing bad happened" are red flags. Descriptions must be factual and objective.
• Unauthorised restrictive practice not recognised as reportable — providers sometimes log a restrictive practice incident as an internal incident only and fail to notify the Commission.
• Records not retained in accessible format — paper records in unsorted filing, or records stored in a system the provider can no longer access.

Strengthened Practice Standards — What Changes in 2026

The strengthened NDIS Practice Standards, which the Commission has been progressively implementing, place greater emphasis on a provider's ability to demonstrate systemic learning from incidents — not simply recording that they occurred. For SIL providers, this means your records should show a clear line from incident description through to investigation findings and, most importantly, to measurable corrective actions with verified completion dates. An auditor reviewing your system under the strengthened framework will ask: did this provider learn from this incident, and can they prove it?

Providers preparing for registration or re-registration in 2026 should ensure their incident register can be filtered by incident type, date range, location, and staff member to enable trend analysis. This is now an expected capability, not a bonus feature.

Practical Tips for SIL Providers

• Use a digital incident register with mandatory fields — this prevents incomplete records being saved.
• Build the NDIS Commission notification step directly into your incident response flowchart so it cannot be skipped.
• Review your incident register monthly for patterns — repeated falls at the same address, or incidents involving the same staff member, warrant a deeper review before an auditor finds them first.
• Debrief participants (with appropriate communication support) after incidents wherever safe and appropriate to do so — and document that you did.
• Store closed records for at least five years and ensure they can be retrieved promptly if requested by the Commission.

If you are building or overhauling your incident management system ahead of a 2026 audit, the 74-document audit-ready SIL compliance kit available at ndiscompliant.com.au includes a pre-formatted reportable incident register, notification templates, investigation checklists, and all other Core and SIL module documentation you will need.