What incidents must be reported to the NDIS Commission?

Reportable incidents under the NDIS (Incident Management and Reportable Incidents) Rules 2018 include the death of a participant, serious injury, abuse or neglect, unauthorised use of a restrictive practice, and any incident that impacts a participant's health, safety, or wellbeing in a significant way. Check the current Rules on the NDIS Commission website for the complete list, as definitions are specific.

How quickly must a SIL provider notify the NDIS Commission of a reportable incident?

For most reportable incidents, notification to the NDIS Commission is required within 24 hours of the provider becoming aware of the incident. A follow-up written report with full details is then required within a further specified period. Always refer to the current Incident Management Rules for the exact timeframes applicable to each incident category.

Does the NDIS Commission provide an official incident register template?

The NDIS Commission does not mandate a specific template format, but it does specify what information must be recorded. Providers are free to design their own register or use a commercially available template, provided all required fields are captured and the register can be produced for audit on request.

Can a SIL provider use electronic incident management software instead of a paper register?

Yes. Electronic systems are acceptable and often preferable for SIL providers, as they can automate notification reminders and generate reports for trend analysis. The key requirement is that the system captures all mandatory information, records are secure, and they can be accessed and exported for Commission review when required.

What happens if a SIL provider fails to maintain an adequate incident register?

Failure to maintain an adequate incident register can result in the NDIS Commission issuing a compliance notice, banning order, or civil penalty. It can also trigger a broader compliance investigation into the provider's practices. In serious cases, registration can be suspended or cancelled.

Do near misses need to be recorded in the incident register?

Yes. Best-practice incident management — and the spirit of the NDIS Practice Standards — requires near misses to be recorded, not just incidents where harm occurred. Near miss data is essential for identifying systemic risks before they result in injury or a reportable incident. Many auditors specifically check for near miss entries as evidence of a proactive safety culture.

NDIS Incident Register Example (Filled-In Sample)

What is an NDIS Incident Register and Why Do SIL Providers Need One?

An incident register is a structured, ongoing record that captures every incident — including near misses, reportable incidents, and allegations of abuse or neglect — occurring within an NDIS-registered provider's service environment. For Supported Independent Living (SIL) providers, maintaining a compliant incident register is not optional. It is a core obligation under the NDIS Practice Standards and the NDIS (Incident Management and Reportable Incidents) Rules 2018.

The NDIS Commission can request your incident register during a compliance audit, following a complaint, or as part of an investigation. A gap-filled or poorly maintained register is one of the most commonly cited non-conformances for SIL providers. The strengthened Practice Standards framework reinforces that incident management must be systemic, not reactive — meaning every entry must be traceable from first notification through to resolution and quality improvement action.

Mandatory Fields: What Every Entry Must Include

Before looking at the filled-in sample below, it helps to understand what the NDIS Commission expects each register entry to contain. While the Commission does not prescribe a specific template format, the Incident Management and Reportable Incidents Rules and associated guidance make clear that each entry should capture:

Date, time, and location of the incident
Name (or unique identifier) of the participant affected
Category of incident (e.g., injury, abuse allegation, unauthorised restrictive practice, medication error)
Whether the incident is a reportable incident requiring NDIS Commission notification
Names of staff or contractors present
Description of what occurred, including immediate context
Immediate actions taken (first aid, emergency services, notifications to family/guardian)
Date and method of NDIS Commission notification (for reportable incidents)
Investigation status and outcome
Corrective or preventive actions implemented
Date the record was closed

Filled-In Sample Incident Register Entry

The following is a realistic example of a completed incident register entry for a SIL house. This is illustrative only — adapt field names and layout to match your organisation's approved incident management system.

Field	Entry
Incident Reference No.	INC-2026-0047
Date of Incident	3 June 2026
Time of Incident	07:45 AM
Location	SIL House — Kitchen, 12 Banksia Court, Participant Home (SIL)
Participant Identifier	P-1041 (pseudonym: "Alex")
Incident Category	Injury to participant — fall with suspected laceration
Reportable Incident?	Yes — injury requiring medical attention (hospital presentation)
Staff Present	Support Worker: J. Nguyen (SW-0312); House Supervisor: L. Patel (HS-0018)
Description of Incident	Participant was preparing breakfast independently. Participant slipped on a wet section of the kitchen floor (tap had been left running the previous evening) and struck the left forearm on the benchtop edge, resulting in a visible laceration approximately 4 cm in length with moderate bleeding. Participant reported pain at the site. No loss of consciousness was observed.
Immediate Actions Taken	First aid applied by SW J. Nguyen (gloves worn, wound cleaned and temporarily dressed). Ambulance called at 07:52 AM. Participant transported to Royal Melbourne Hospital Emergency. Next of kin (guardian Ms. T. Chen) notified by phone at 08:05 AM. Participant's NDIS Support Coordinator notified by email at 08:30 AM. House Supervisor documented scene and secured area.
NDIS Commission Notification	Submitted via NDIS Commission portal at 11:20 AM on 3 June 2026 (within 24-hour reportable incident requirement). Notification reference: NDISCOM-RPT-2026-XXXXX.
Medical Outcome	Laceration sutured (4 stitches). No fracture detected on X-ray. Participant discharged same day and returned to SIL house at 2:45 PM with wound care plan.
Investigation Status	Internal investigation opened 3 June 2026. Assigned to Quality and Safety Lead: R. Obi. Root cause analysis in progress — reviewing overnight cleaning procedures and handover documentation.
Investigation Outcome	Completed 10 June 2026. Root cause identified: tap left running after evening meal preparation — not identified during overnight check. Handover checklist did not include kitchen safety check item.
Corrective Actions	1. Kitchen safety checklist updated to include "all taps off and floor dry" as a mandatory end-of-shift item. 2. All SIL staff briefed at team meeting 11 June 2026 (sign-off sheet retained). 3. Non-slip mat installed at kitchen sink area (completed 8 June 2026). 4. Risk assessment for participant's kitchen independence plan reviewed and updated.
Record Closed	12 June 2026
Completed by	R. Obi, Quality and Safety Lead — signed 12 June 2026

Key Points to Note in This Example

Timely Notification

The sample shows NDIS Commission notification submitted within 24 hours of the incident. For injuries requiring immediate medical treatment, this is the standard notification window. Your incident management policy must define who is responsible for submitting this notification and what information must accompany it. A missed or late notification is a serious compliance failure that can trigger further investigation by the Commission.

Participant Privacy

Participants are identified by a unique reference code and pseudonym rather than full name. This is good practice for a register that may be accessed by multiple staff members. Your full incident record system (separate from the public-facing or multi-user register) may contain identifiable information stored securely and with appropriate access controls.

Linking Incidents to Improvement

Notice that the entry does not simply document what happened — it traces through to a root cause, specific corrective actions, and a verified close-out date. This is exactly what an approved quality auditor will look for under the NDIS Practice Standards Quality Indicators. An entry with no corrective action, or one closed the same day it was opened, is a red flag during an audit.

Restrictive Practices and Allegations

The sample above covers a physical injury. Your register must also be able to capture incidents involving alleged abuse or neglect, unauthorised restrictive practices, and incidents affecting the safety of others in the home. These categories often have distinct notification requirements and investigation pathways. Ensure your register template has separate fields or categorisation to distinguish these incident types clearly.

How Long Must You Retain Your Incident Register?

The NDIS Commission's record-keeping requirements specify that incident records must be retained for a defined period. Given that the requirements can be updated, always verify the current retention period in the NDIS Practice Standards guidance or directly with the Commission. For SIL providers specifically, records relating to participants with complex support needs or ongoing investigations should be retained until all related matters are formally closed, regardless of the standard retention period.

Common Non-Conformances Auditors Identify

Incomplete entries — fields left blank, particularly investigation outcome and corrective actions.
Late NDIS Commission notifications — notification submitted days after the event rather than within the required window.
No evidence of staff review or briefing — corrective action noted but no sign-off sheet or training record to prove it occurred.
Incidents not categorised correctly — a medication error recorded under "general incident" rather than a distinct category that triggers a specific review process.
Register not accessible — stored on a personal device or in a format the Commission cannot readily review during an audit visit.

Building a Complete Incident Management System

Your incident register is one component of a broader incident management framework. The NDIS Practice Standards require providers to have a documented policy, a clear reporting chain, staff training on incident identification and reporting, regular analysis of incident trends, and a feedback loop to participants and their families where appropriate.

If you are building or auditing your SIL compliance documentation suite, ndiscompliant.com.au offers a 74-document audit-ready SIL compliance kit that includes a pre-formatted incident register template, investigation report template, and incident management policy — designed to align with the current Practice Standards and the strengthened 2026 framework requirements.

Important: This article provides general guidance about NDIS compliance requirements. It is not legal or professional advice. Requirements may change as the NDIS Commission updates its policies and Practice Standards. Always verify current requirements with the NDIS Quality and Safeguards Commission or a registered NDIS consultant before making compliance decisions.