Critical Incident Reports (CIRs) are something most Support Coordinators encounter regularly. However, many people working within the NDIS are not always clear about what a critical incident is, who should report it, and what happens after a report is written.
Understanding the purpose and process of Critical Incident Reporting is important. It is not simply an administrative task, it plays a key role in protecting participants, identifying risks, and ensuring the right supports are in place.
What Is a Critical Incident Report?
A Critical Incident Report documents an event that involves:
- Harm experienced by a participant
- Harm experienced by others caused by a participant
- Damage to property
- A near miss where harm could have occurred but did not
Examples of harm may include:
- Death of a participant
- Physical injury
- Verbal abuse
- Sexual abuse, grooming or exploitation
- Financial abuse
- Neglect
- Unauthorised restrictive practices
A CIR should record objective facts about what happened before, during and after the incident. This includes details such as:
- What occurred
- Where and when it occurred
- Who was involved
- The duration, intensity or frequency of behaviours
- What actions were taken in response
In most situations, the person who witnessed the event should complete the report.
Providers usually have a standard template or incident reporting system to record this information.
All registered NDIS providers must also have policies and procedures outlining what happens after an incident is reported. These procedures should cover:
- Internal review processes
- Debriefing procedures
- Where the report must be sent
- Required reporting timeframes
Who Should Write a Critical Incident Report?
Where possible, the person who witnessed or was directly involved in the incident should write the report.
If multiple staff members witnessed the incident, each person should document their own account of what occurred.
However, there are situations where no NDIS-funded worker was present. For example, when:
- A family member or nominee reports an incident
- A member of the public raises concerns
- Another provider shares information about an incident
In these situations, the NDIS provider connected to the participant who first receives the information should document the incident.
Often, the provider delivering core supports (such as support workers) will be the first point of contact.
However, it is also common for a Support Coordinator to receive the initial report.
When this occurs, your organisation should have a template or reporting system to record:
- Details of the event
- Environmental context
- The identity and role of the person reporting the incident
Registered Support Coordination providers must also have clear procedures outlining what happens after an incident is recorded, including supervision pathways and reporting timeframes.
What Happens After a Critical Incident Is Reported?
Once the incident has been documented and reviewed internally by the provider, the next step is determining who the report must be sent to.
Depending on the nature of the incident, the report may need to be shared with several different parties.
These may include:
- The NDIA
- The NDIS Quality and Safeguards Commission
- The participant’s Support Coordinator
- A guardian or plan nominee
- Other authorities such as police, the Coroner or child protection services
Understanding why reports are sent to each body helps determine when reporting is required.
Reporting to the NDIA
The NDIA is the funding body of the NDIS. Incident reports can provide important evidence of:
- Risks facing a participant
- Gaps in existing supports
- The need for additional services or supervision
- The need for assistive technology or environmental changes
Importantly, near misses or incidents that were successfully de-escalated can still provide valuable evidence.
For example:
- A participant with behaviours of concern de-escalates before serious injury occurs
- A participant prone to falls experiences multiple falls without major injury
If these incidents are not formally documented, requests for additional funding may later be rejected due to insufficient evidence.
It is common for incidents to be mentioned later in reports, such as end-of-plan reviews, but never formally recorded at the time they occurred. Recording incidents as they happen strengthens the evidence available to support future funding requests.
Reporting to the NDIS Quality and Safeguards Commission
The NDIS Quality and Safeguards Commission is responsible for regulating providers and ensuring participant safety.
Some incidents must be reported to the Commission as reportable incidents, including:
- Death of a participant
- Serious injury
- Abuse or neglect
- Unauthorised use of restrictive practices
These incidents must be reported when they occur during the delivery of NDIS-funded supports or are directly connected to those supports.
Examples may include:
- An injury during a therapy program
- An incident occurring during scheduled support hours
- An event that may have been prevented if supports were in place
The Commission reviews these reports to determine whether investigation, corrective action or regulatory oversight is required.
The Role of the Support Coordinator
Support Coordinators play an important role in monitoring and tracking incidents affecting participants.
Registered Support Coordination providers are required to maintain a Critical Incident Register for participants. While not mandatory for unregistered providers, it is definitely considered best practice.
A register should:
- Record all incidents affecting a participant
- Document required follow-up actions
- Track completion of those actions
- Identify patterns or emerging risks
These registers should be reviewed regularly.
Even if a Support Coordinator is not responsible for submitting a report to the Commission, they should ensure that the appropriate provider has met their reporting obligations.
Failure to monitor incident reporting can result in:
- Audit non-conformities
- Complaints to the NDIS Commission
- Poor risk management outcomes for participants
- Guardians, Nominees and Other Authorities
Where a participant has a formally appointed guardian or plan nominee, they should usually be informed of incidents so they can make informed decisions about the participant’s supports and safety.
In some circumstances, other authorities must also be notified.
This may include:
- Police if a crime may have occurred
- The Coroner if a participant has died
- Child protection authorities if a child may be at risk
In some cases, the NDIS Commission may also refer matters to external authorities if further investigation is required.
What If the Incident Occurs When No Supports Were Scheduled?
If an incident occurs outside of scheduled NDIS supports, it usually does not need to be reported to the NDIS Commission.
However, the incident may still be important to document.
If it appears that adequate supports could have prevented the incident, reporting the event to the NDIA may help demonstrate unmet support needs.
Responsibilities of Support Coordinators
Regardless of whether your organisation is registered or unregistered, Support Coordinators must understand:
- Their own reporting obligations
- The reporting obligations of participant providers
- NDIS Commission reporting categories
- Required reporting timeframes
All Support Coordination providers should have internal procedures that clearly outline:
- Supervision and escalation pathways
- Internal reporting requirements
- External reporting responsibilities
- Privacy and confidentiality protections
It is also important to remember that any person receiving NDIS funding must comply with the NDIS Code of Conduct.
Failure to appropriately report incidents can lead to:
- Regulatory consequences
- Funding impacts
- Audit non-conformities
- Complaints to the NDIS Commission
In Summary
Critical Incident Reporting is much more than paperwork. It plays a central role in:
- Safeguarding participants
- Identifying risks and patterns of harm
- Providing evidence for funding decisions
- Meeting regulatory obligations
For Support Coordinators, understanding when, how and where incidents must be reported is an essential part of professional practice.
How Support Coordination Software Can Help
Support Coordination Software allows you to efficiently document and retrieve Critical Incident Reports through dedicated CIR folders within each participant file.
You can also record and monitor associated risks using the Risk Assessment and Risk Management Plan templates available within the platform.
Active subscribers can also access our Community of Support Coordinators, including Masterclasses and Communities of Practice.
👉 To find out more about our Support Coordination Community visit:
You can also book a demo or sign up for a 14-day free trial to explore Support Coordination Software firsthand!