Guide to NDIS Reportable Incidents [2025]

What is a NDIS Reportable Incident?

An NDIS Reportable Incident is a mandatory component of the NDIS practice standards, which are overseen by the NDIS Quality and Safeguards Commission.

These incidents, including alleged reportable incidents that occur or are alleged to occur in connection with the provision of NDIS supports or services, must be recorded by an NDIS provider in a compliant incident management system AND reported through to the NDIS Quality and Safeguards Commission.

There are specific timeframes for NDIS reportable incidents to be reported to the NDIS Quality and Safeguards Commission, which are noted below.

Examples of NDIS Reportable Incidents

Reportable incidents encompass a range of serious occurrences, including:

The death of a person with a disability.
Serious injury of a person with a disability.
Abuse or neglect of a person with a disability.
Unlawful sexual or physical contact with or assault of a person with a disability.
Sexual misconduct committed against or in the presence of a person with a disability, including grooming for sexual activity.
The use of a restrictive practice in relation to a person with a disability if it is not in accordance with required state or territory authorization or a behavioral support plan.

What is Not an NDIS Reportable Incident?

An incident is considered reportable to the NDIS Quality and Safeguards Commission if it occurs or is alleged to occur in connection with the provision of NDIS supports.

Incidents that occur or are alleged to have occurred outside of this context, such as abuse or neglect by a member of the public or a family member, should be reported to the appropriate regulatory authorities such as the police and captured within the provider’s incident management system.

Who is Responsible for Reporting Incidents?

NDIS providers must clearly outline in their policies and procedures who is responsible for managing the incident management system and reporting reportable incidents to the NDIS Quality and Safeguards Commission.

It is important to note however that ALL staff must be trained to identify and report incidents.

The team responsible for reviewing and submitting reportable incidents to the Quality and Safeguards Commission must also be adequately trained in how to complete incident investigations and root cause analyses.

How Long Do You Have to Report Incidents to the NDIS?

Registered providers must be aware of the required timeframe to submit an incident report to the NDIS Quality and Safeguards Commission based on the type of incident.

A guideline of required timeframes for different reportable incidents can be found here.

Reporting incidents to the NDIS Quality and Safeguards Commission is a mandatory requirement for NDIS providers. Failure to report an incident within the required timeframe can jeopardise the provider’s registration and may even result in civil and financial penalties.

What Should You Include in an NDIS Incident Report?

NDIS registered providers must capture specific information when receiving an incident report. You can read more about the required information here but this includes items such as:

Details of the incident (time, date, place, witnesses)
Initial response
Regulatory bodies notified
Assessments, investigations, and follow-up actions

Logic’s incident management form simplifies this process, ensuring compliance with NDIS practice standards.

By adhering to these guidelines and utilising effective incident management systems, NDIS providers can ensure the safety and well-being of participants, maintain compliance, and foster continuous improvement within their organisations.

What Training is Available for NDIS Reportable Incidents?

There is a range of training available on the market by different third party providers on NDIS reportable incidents.

Importantly, there’s no one-size-fits-all approach to training. Each provider must assess their organisation’s specific training needs — a key part of meeting their responsibilities under the NDIS Practice Standards.

At Take5Learning, we deliver bite-sized training aligned with the NDIS Practice Standards — helping workers understand what reportable incidents are, how to identify them, and when they must be reported.

How To Onboard New Staff And Teach Them NDIS Incident Reporting

It’s important to recognise that new staff will come with varying levels of experience. Some may have worked within the NDIS sector for many years, while for others, this could be their first role under the NDIS, regardless of their broader experience.

That’s why it’s essential for organisations to provide a standardised training platform — one where every team member accesses and completes the same material to ensure consistent knowledge and processes across the organisation.

A platform like Take5Learning ensures that all staff — whether new or experienced — can engage with critical topics, such as NDIS reportable incidents, in a clear, consistent, and enjoyable way.

What Should Providers Consider When Reporting Incidents Involving Third Parties?

I.e. Transport Services Or Shared Living Providers

One of the most important principles when liaising with third parties about an NDIS participant’s care and services is obtaining consent from the participant or their plan nominee.

The participant or nominee must always remain at the centre of care — and that includes during incident management. Before engaging with any third party, it’s essential to ensure you have the appropriate consent.

Once consent is obtained, the next key principle is maintaining clear documentation and adhering to timeframes when communicating with third parties.

Are There Differences In How Sole Traders And Larger Organisations Should Approach Incident Management?

At a broad level, the responsibilities for NDIS reportable incidents are the same, regardless of the size of your organisation.

Whether you’re a sole trader or part of a team with 2,000 staff, the mandatory reporting guidelines and timelines still apply.

That said, the approach to risk management, incident handling, and quality improvement will naturally differ. Larger organisations may use dedicated systems for managing risk, tracking incidents, and monitoring continuous improvement. In contrast, a sole trader might not experience a single incident all year — and may manage their compliance and quality processes with nothing more than a simple spreadsheet.

What Are The Consequences For Not Reporting Incidents Or Poorly Recording Them?

The consequences for a provider or worker can be severe.

The NDIS Quality and Safeguards Commission may issue infringement notices, revoke registration, impose conditions on a provider, or place a worker or provider on the banning list.

In some cases, failing to report can lead to legal consequences, including civil or criminal charges, and there are many real-world examples of this occurring.

Beyond legal and regulatory outcomes, there’s also the risk of reputational damage. While the NDIS is a large funding scheme, it’s also a closely connected community where word spreads quickly.

What is an Incident Management System and What Does It Do?

An Incident Management System is a structured process used by organisations to record, manage, respond to, and review incidents—particularly those that affect the safety, wellbeing, or rights of individuals.

In the context of the NDIS, an Incident Management System is a mandatory requirement for providers.

Incident Ledger – Maintaining an incident management system is crucial for NDIS registration and adherence to practice standards. During audits, auditors review how the system has been used and its effectiveness in managing incidents, driving continuous improvement, and involving participants and their representatives in investigations.

An incident management system should include an easily searchable incident ledger.

Root Cause Analyses – An incident management system that includes root cause analysis is vital for continuous improvement within an NDIS organisation. This analysis helps determine if changes to the organisation’s support services, policies, and procedures can prevent future incidents.

Audits – When an NDIS provider registers for the first time or undergoes re-registration, auditors will review the provider’s incident management system. This review ensures the system is adequate to meet the organisation’s needs and ensures participant safety. The system should facilitate easy incident submission, review, and root cause analysis to drive continuous improvement.

How Take5Learning Can Support You

Take5Learning’s leadership team are experienced NDIS providers who know what is required to run an organisation that is compliant against the NDIS practice standards.

Ensuring staff are trained across the requirements of the NDIS Practice Standards, including NDIS Incident Management, is essential.

If you are looking for bite-sized, engaging e-learning for your staff, please reach out to us via our contact page.