NDIS Incident Reporting: Reportable Incidents and Documentation Obligations

Reportable incidents under the NDIS framework

Registered NDIS providers are required to maintain an incident management system under Standard 2 of the NDIS Practice Standards, and to report certain incidents — called "reportable incidents" — to the NDIS Quality and Safeguards Commission. The framework is established under the National Disability Insurance Scheme Act 2013 (Cth) and the National Disability Insurance Scheme (Incident Management and Reportable Incidents) Rules 2018 (the Rules). The Rules define both the categories of reportable incident and the notification timeframes that apply to each.

Reportable incidents are divided into two priority categories based on severity and the nature of the harm involved. The distinction between Priority 1 and Priority 2 is not merely procedural — it carries different notification timeframes, different Commission response expectations, and different evidentiary demands on the underlying documentation.

Priority 1 reportable incidents are the most serious category. They include: the death of a participant in connection with the delivery of NDIS supports; 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; and the use of a regulated restrictive practice in relation to a participant that has not been authorised as required under the Act or the Rules. Each of these triggers the most urgent notification obligation the framework imposes.

Priority 2 reportable incidents cover incidents involving a participant that constitute a reportable incident under the Rules but do not meet the Priority 1 threshold. These are generally incidents involving harm or risk of harm below the Priority 1 severity level, or where the full extent of harm was not known at the time the provider became aware of the incident and it was not initially classified as Priority 1. The reporting timeframe for Priority 2 incidents is significantly longer than for Priority 1, but the documentation obligations are identical.

Notification timeframes and what triggers them

For Priority 1 incidents, the registered provider must notify the Commission as soon as practicable, and in any event no later than 24 hours after the provider becomes aware of the incident. This initial notification may be verbal or through the Commission's Provider Reporting Portal. A written report must follow within 5 business days of the initial notification. The written report must set out the details of the incident, the immediate response taken, and the actions proposed or underway to address the incident and prevent recurrence.

For Priority 2 incidents, there is no 24-hour notification obligation. The provider must submit a written report to the Commission within 30 days of becoming aware of the incident. The content requirements for the written report are equivalent to those for Priority 1 — the shorter timeframe for Priority 1 does not mean the written report can be less detailed.

The threshold question in both categories is when the provider "became aware" of the incident. This is the moment from which the notification clock runs — and it is a question the Commission will scrutinise closely if a notification is late. The provider's awareness is established by its records: the shift note, the handover record, the supervisor notification log, the incident management system entry. If any of these records is vague, delayed, or internally inconsistent, the Commission cannot determine when awareness occurred — and a determination adverse to the provider becomes more likely.

There is a critically important implication for shift note practice: a shift note completed the following day, purporting to describe events from the previous shift, cannot establish that the provider was unaware of the incident until the note was written. Where a shift note is the first record of an event that should have been classified as a reportable incident, its timestamp establishes the outer boundary of the awareness claim. If the note was completed 18 hours after the shift ended, the Commission may treat that delay as evidence of awareness — or, alternatively, as evidence of inadequate incident management systems. Neither outcome is defensible.

The shift note as the incident's evidentiary foundation

The Commission does not assess incident reports in isolation. When reviewing a reported incident, auditors examine the incident report alongside the underlying shift notes, progress records, handover records, and any supervisor or management communication records that relate to the incident. The incident report and the underlying records must be mutually consistent. Where the incident report describes the event in terms that differ materially from the contemporaneous record — whether by adding detail, omitting detail, or characterising the event differently — auditors treat this as a documentation integrity concern. This concern can elevate the Commission's regulatory response well beyond what the incident itself would otherwise warrant.

The shift note provides the evidentiary foundation for the incident classification itself. A Priority 1 incident — particularly one involving serious injury, abuse, or an unauthorised restrictive practice — cannot be supported by a vague narrative. The specific details that establish the incident type, the severity of the harm, the circumstances in which it occurred, and the immediate response taken must be present in the contemporaneous record. "Participant appeared distressed and the shift was difficult" is not a record that establishes the factual basis for any incident classification. A record that describes, with specificity, what the worker observed, what the participant said or did, what happened physically, who was present, what was done immediately, and who was notified — that is a record that provides the incident report with a foundation it can stand on.

This is not merely a compliance formality. In the event of a Commission investigation, a coronial inquiry, or civil proceedings, the shift note is the primary contemporaneous evidence of what occurred during a support. Its integrity, specificity, and timeliness are material to every downstream regulatory and legal process.

Documentation failure modes in NDIS incident records

The Commission's audit and investigation experience identifies recurring documentation failures that complicate incident reporting and, in some cases, transform a manageable compliance concern into a systemic finding. Understanding these failure modes is the first step to eliminating them.

Delayed completion. Shift notes completed the day after the shift — particularly where an incident occurred — undermine the awareness timeline and compromise the record's value as contemporaneous evidence. The Commission treats late records with scepticism, particularly when they are suspiciously detailed relative to the timeliness with which they were apparently completed.

Vague descriptions that cannot establish incident type. The Rules require that the provider report a specific category of incident. A shift note that describes "a difficult interaction" or "the participant was upset" cannot ground a Priority 2 classification, let alone Priority 1. The specificity required to classify the incident must be present in the underlying record, not reconstructed after the fact.

No record of immediate response or notifications made. An incident record that describes what happened but contains no documentation of the response is incomplete. The Commission expects to see evidence that the worker acted appropriately — sought help, notified a supervisor, called emergency services where warranted — and that this is reflected in the record, not assumed.

Mismatch between the incident report and the shift record. Where the formal incident report to the Commission describes events that differ from the shift note in material ways, the integrity of both documents is called into question. This is one of the most serious documentation failure patterns the Commission encounters, because it raises questions about whether the records were manipulated after the fact.

No follow-up trail in subsequent records. A single incident record, even a complete one, does not close the documentation loop. Subsequent shift records should evidence that the follow-up actions recorded were carried out — that the supervisor was contacted, that the participant was monitored, that the behaviour support practitioner was engaged where relevant. An incident that disappears from the record after the initial note raises questions about how seriously the event was treated.