How to Document a Reportable Incident in NDIS (Template + Steps)

Why Incident Documentation Matters Under the NDIS Framework

Every registered NDIS provider has a legal obligation to identify, record, and report incidents that occur in connection with the delivery of supports. For SIL and other high-intensity providers, this obligation is particularly stringent because the people supported often have complex needs and reduced capacity to self-advocate.

Under the NDIS (Incident Management and Reportable Incidents) Rules 2018, providers must maintain an incident management system and ensure all reportable incidents are notified to the NDIS Quality and Safeguards Commission (the Commission) within defined timeframes. Failure to report — or reporting inaccurately — can trigger compliance action, conditions on registration, or referral to the NDIS Commission for investigation.

The strengthened NDIS Practice Standards framework, progressively rolled out from 2024 and firming up through 2026, places even greater emphasis on systemic learning from incidents, meaning documentation must go beyond bare facts to capture root causes and corrective actions.

What Counts as a Reportable Incident?

Not every incident triggers Commission notification — but all incidents must be internally recorded. A reportable incident is defined in the NDIS Act and Rules and includes:

• 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 committed against, or in the presence of, a participant
• The use of a restrictive practice on a participant that was not in accordance with an authorisation (where required), or that was not notified to the Commission

Providers should never assume an incident "probably isn't reportable" without checking. When in doubt, report. The Commission has made clear that under-reporting is treated more seriously than over-reporting.

Step-by-Step: How to Document a Reportable Incident

Step 1 — Secure Immediate Safety

Before any paperwork, ensure the participant and any others involved are safe. Contact emergency services if required. The welfare of the person comes first. Your documentation will later record what actions were taken at this stage, so note the time emergency services were called if applicable.

Step 2 — Record the Initial Facts as Soon as Practicable

A staff member with direct knowledge of the incident should complete an initial incident record within hours of the event — not at the end of a shift, and certainly not the next day. Memory degrades and details become disputed. Record:

• Date and time the incident occurred
• Location (be specific — e.g., the participant's bedroom, the bathroom, the community transport vehicle)
• Name and NDIS number of the participant/s involved
• Names and roles of staff present
• Names of any witnesses (including other participants, family members, or visitors)
• A factual, chronological account of what happened — written in plain language, free of jargon and interpretation
• Immediate actions taken (first aid, contacting a supervisor, calling emergency services)
• Physical condition of the participant before and after the incident
• Whether a restrictive practice was involved

Step 3 — Notify Your Incident Manager Immediately

Your organisation's incident management system should designate who receives notification. In a SIL context, this is typically a Team Leader, Site Manager, or designated Incident Manager. They assess whether the incident meets the threshold for Commission notification and initiate the formal reporting process.

Step 4 — Notify the NDIS Commission Within Required Timeframes

The NDIS Incident Rules set specific notification windows depending on incident type:

Initial notifications are made through the My NDIS Commission Portal. The notification must include the type of incident, date, time, and a brief factual summary. A full written report is typically required within the timeframe the Commission specifies, and may include supporting documents such as witness statements, medical records, and your internal investigation findings.

Step 5 — Collect Supporting Evidence

Gather all relevant supporting material and attach it to the incident file:

• Signed witness statements from all staff and any others present
• Photographs of the scene or injuries (with participant consent where possible, or documented rationale where consent cannot be obtained at the time)
• Relevant sections of the participant's support plan or behaviour support plan
• Any prior incident records that indicate a pattern
• Medication administration records if medication is relevant to the incident
• CCTV footage if available and relevant — preserve it before automatic overwrite

Step 6 — Conduct an Internal Investigation

For serious incidents, a structured internal review is required. This should be completed by someone with appropriate authority who was not directly involved in the incident. The investigation should determine:

• What happened and why (root cause analysis)
• Whether policies, procedures, or training contributed to the incident
• Whether the participant's support plan or risk assessments need updating
• What corrective actions will prevent recurrence

The 2026 strengthened Practice Standards specifically require providers to demonstrate systemic learning — that incidents drive genuine improvement, not just paperwork closure.

Step 7 — Implement Corrective Actions and Close the Record

Every incident record should have a clearly documented closure stage. Record:

• Corrective actions assigned (who is responsible, by when)
• Whether the participant and/or their nominated representative were notified and how they responded
• Whether the incident was discussed at a team or management review meeting
• Sign-off from an authorised manager

Incident Report Template: What to Include

The following template structure reflects Commission expectations. Your system may use a digital platform or a paper-based form — the content requirements are the same.

Common Documentation Errors to Avoid

• Writing opinions instead of facts. "The participant was being difficult" is an opinion. "The participant shouted and pushed the staff member's arm" is a fact. Stick to observable behaviour and events.
• Delaying the initial record. Notes written hours or days later are far more likely to contain errors and gaps that auditors will flag.
• Incomplete witness statements. Unsigned or undated witness statements carry little weight in an investigation and will be noted as a non-conformance by a quality auditor.
• Failing to notify the participant. Participants (and often their nominee or guardian) have a right to be informed. Record every notification attempt and the outcome.
• Treating closure as automatic. An incident record is not closed by the passage of time. It requires an authorised sign-off confirming all corrective actions are complete.

Preparing Your Team and Systems

Consistent, high-quality incident documentation requires systems and training — not just good intentions. Providers preparing for the 2026 registration renewal cycle should ensure:

• All staff have completed incident identification and reporting training, with evidence records
• Your incident management system is accessible 24/7, including for after-hours staff
• Escalation pathways are clearly documented and tested
• Your policy references the current NDIS Incident Rules and is reviewed at least annually

If you are building or auditing your SIL compliance documentation suite, the 74-document audit-ready kit available at ndiscompliant.com.au includes an incident management policy, investigation templates, and Commission notification checklists aligned to the strengthened Practice Standards.