How to write an NDIS incident register (2026 template + example)

Why your incident register matters under the 2026 NDIS framework

The NDIS Quality and Safeguards Commission requires all registered providers — and from 2026 all providers seeking or renewing registration under the strengthened framework — to maintain a systematic record of incidents. For SIL (Supported Independent Living) providers, the stakes are particularly high: you are delivering supports in people's homes around the clock, and the incident register is a primary piece of evidence that auditors examine to assess whether your organisation identifies risk, responds appropriately, and learns from what goes wrong.

An incident register is not simply a log. Under the NDIS (Incident Management and Reportable Incidents) Rules 2018 and the corresponding Practice Standards, the register must be part of a broader incident management system that includes detection, response, investigation, review, and improvement. Getting the document right from the outset protects participants, protects your registration, and demonstrates the genuine accountability that the Commission expects.

What the NDIS Practice Standards require you to record

The NDIS Practice Standards (Core Module, Indicator 1.7 and the associated Quality Indicators) specify that providers must have a system to:

• Identify and record incidents, including near-misses and events that did not result in harm but had the potential to do so.
• Respond in a timely way that prioritises participant safety.
• Report to the NDIS Commission within the mandatory timeframes for reportable incidents (including death, serious injury, abuse, neglect, unlawful sexual or physical contact, and use of unauthorised restrictive practices).
• Investigate incidents and implement corrective actions.
• Use incident data to identify trends and drive continuous improvement.

The 2026 strengthened Practice Standards place greater emphasis on participant voice, co-design of safety systems, and provider accountability — meaning your register must also connect to how you have listened to and involved the participant affected.

Step-by-step: how to write and maintain an NDIS incident register

1. Define your incident categories before you start. Agree on a consistent taxonomy that separates reportable incidents (which trigger mandatory Commission notification) from internal incidents (managed in-house). Common categories include: falls and physical injury, medication errors, challenging behaviour, property damage, participant-to-participant incidents, staff misconduct, restrictive practice use, missing/absent participant, and near-misses.
2. Choose a format that is always accessible. A shared, permission-controlled spreadsheet or purpose-built software works better than a paper folder kept in one location. SIL services operating across multiple houses need a centralised register so patterns can be spotted across sites.
3. Set your mandatory fields. Every row in the register must capture, at minimum, the fields described in the template section below.
4. Assign a responsible person for each entry. The worker who was present or first aware of the incident creates the initial record, ideally within 24 hours. A supervisor or quality lead reviews and signs off within a set timeframe (typically 48–72 hours for non-reportable incidents).
5. Trigger the NDIS Commission notification pathway for reportable incidents. Reportable incidents must be notified to the Commission via the myNDIS Provider Portal. Initial notification is required within 24 hours of the provider becoming aware. The register entry must cross-reference the Commission notification reference number so there is a clear audit trail.
6. Complete the investigation and corrective action fields. Every incident — not just reportable ones — should have a brief investigation note and at least one documented corrective or preventive action. This is where many providers are found non-conformant during audits.
7. Review the register at regular intervals. Conduct a formal register review at least quarterly. Look for patterns: same participant, same time of day, same location, same support worker, same type of incident. Document your analysis and the actions you took as a result.
8. Retain records for the required period. The Commission's guidance requires incident records to be retained for a minimum of seven years (longer for incidents involving children, consistent with state and territory requirements).

Incident register template: mandatory fields

Filled-in example entry

The following is a realistic sample of a completed incident register row for a SIL property. All participant and worker details are fictional.

Common non-conformances found during audits

Approved quality auditors consistently find the following gaps when reviewing SIL providers' incident registers:

• Entries created days or weeks after the incident. Delayed entries raise questions about accuracy and whether mandatory notification timeframes were met.
• No corrective action recorded. Describing what happened without documenting what changed is the single most common finding across registered providers.
• Near-misses excluded. Many providers only record incidents where harm occurred. Near-misses must also be recorded — they are your early-warning system.
• No quarterly or periodic review. A register with no evidence of management oversight fails the continuous improvement requirement.
• Commission notification reference missing. Auditors look for the cross-reference between the register and the myNDIS portal submission. If it is absent, the provider cannot demonstrate timely reporting.
• Privacy breaches in the register itself. Using full participant names in a shared register that all staff can access may breach the Privacy Act 1988 and the NDIS Practice Standards on information management.

Connecting your register to continuous improvement

The register is only as valuable as the conversations it generates. At your quarterly review, summarise your data: total incidents by category, which participants were involved in multiple incidents, whether corrective actions from previous quarters were actually completed, and what patterns suggest a systemic risk. Present this summary to your leadership team and document the discussion. This is the evidence that separates providers who comply on paper from providers who genuinely protect participants.

If you are preparing for your NDIS audit or building your document suite from scratch, ndiscompliant.com.au offers a 74-document audit-ready SIL compliance kit that includes a pre-formatted incident register, investigation templates, quarterly review frameworks, and all supporting policies — purpose-built for the 2026 strengthened Practice Standards.