Registered NDIS providers must tell the NDIS Quality and Safeguards Commission about every reportable incident. Deaths, serious injuries, abuse or neglect, unlawful sexual or physical contact, and sexual misconduct must be notified within 24 hours of the provider becoming aware, with a 5-day report to follow within five business days. Unauthorised use of a restrictive practice is reported within five business days, unless it harmed the person, in which case it's 24 hours too.

Those rules come from the Commission's reportable incidents page and the NDIS (Incident Management and Reportable Incidents) Rules 2018. Below: when the clock starts, what each report needs, what your own record needs, and which paperwork is worth automating.

The short version: the 24-hour clock starts when a worker tells a manager, a supervisor or your nominated person. Get the first notice in with what you know, send the rest in the 5-day report, keep the record for 7 years, and lodge anything new in the new NDIS Commission Portal, which took over new incidents from 12 October 2026.

What counts as a reportable incident?

The Commission separates two things. An incident is anything that has or could have caused harm to a person with disability, or where a person with disability caused serious harm, or the risk of it, to someone else. Registered providers must record and manage these in an incident management system.

A reportable incident is a narrower group that must also go to the Commission. The Commission describes it as an act or event that has happened, or is alleged to have happened, in connection with delivering NDIS supports or services. There are six kinds:

  • the death of a person with disability
  • serious injury of a person with disability
  • abuse or neglect of a person with disability
  • unlawful sexual or physical contact with, or assault of, a person with disability
  • sexual misconduct against, or in the presence of, a person with disability, including grooming for sexual activity
  • use of a restrictive practice that isn't authorised by your state or territory, or doesn't follow the person's behaviour support plan

Allegations count, so you don't wait until you're sure. The Commission also says this includes incidents you've already handled in your own system. And its detailed guidance says reporting to the Commission doesn't replace reports to police or mandatory reports to child protection agencies.

NDIS incident reporting timeframes

This table sets out the timeframes as the Commission's reportable incidents page and sections 20, 21 and 24 of the Rules describe them. The first two timeframes run from when the provider became aware of the incident.

Incident typeFirst noticeFollow-upWorth knowing
Death24 hours5-day report within five business daysYou don't need to describe the impact or harm for a death
Serious injury24 hours5-day report within five business daysThe Commission's guidance lists fractures, burns, deep cuts and head injuries among the examples
Abuse or neglect24 hours5-day report within five business daysAllegations and past events a person tells you about count
Unlawful sexual or physical contact, or assault24 hours5-day report within five business daysSome physical contact is excluded under section 16(2) of the Rules
Sexual misconduct, including grooming24 hours5-day report within five business daysIncludes misconduct in the presence of a person with disability
Unauthorised restrictive practice, no harm5-day report within five business daysNone needed beyond the 5-day reportThe Commission says the 5-day report is the only form needed here
Unauthorised restrictive practice that caused harm24 hours5-day report within five business daysThe Commission says anything that resulted in harm must be reported within 24 hours
Final report, if askedNot applicableWithin 60 business days after the 5-day notificationOnly when the Commissioner requires one, and they can allow longer

The Commission's page warns that missing these timeframes "might result in an infringement notice or other compliance actions", and its quarterly reports track how many notifications arrive on time.

When does the clock start?

Section 19 of the Rules says a worker who becomes aware of a reportable incident must tell one of three people as soon as possible: a member of your key personnel, their own supervisor or manager, or the person your incident management system names as responsible for notifying the Commission.

The Commission's guidance says a provider is taken to be aware once a worker has told one of those people. So if a support worker rings the team leader at 9pm on a Friday, your 24 hours started at 9pm on Friday, even if the form doesn't reach the office until Monday morning.

So a late report is often a handover problem. The information existed, it just sat in a text message or a paper form in someone's car.

What goes in the 24-hour and 5-day reports?

Section 20 of the Rules says the 24-hour notice must include your organisation's details, a description of the incident, the impact or harm to the person (except for a death), the immediate actions you took and whether police or another body were told, the name and contact details of whoever is notifying, the time, date and place if known, and the names and contact details of the people involved.

If you don't have everything inside 24 hours, section 20(3) lets you send the first five items within the 24 hours and the rest within five business days. The 5-day report then adds the names and contact details of any witnesses and any further actions you plan to take. Section 22 also says you don't have to obtain or give some details if doing so could prejudice a criminal investigation or expose the person to a risk of harm.

Two newer details from the Commission matter for how you set up your forms:

  • From 12 October 2026, all new incidents, including the 24-hour and 5-day reports, are lodged in the new NDIS Commission Portal. Incidents lodged before that date stay in the existing portal for their 5-day reports and any requests for information.
  • The Commission's October 2026 glossary for the new portal says each report can only have one impacted participant. If more than one person is hurt, you fill out a separate report for each of them.

The new portal also asks for a category, subcategory and cause, what was happening just before, and what staff did to try to prevent it. If your internal form doesn't capture those, someone has to ring the worker back.

NDIS incident report template: what your own record needs

"NDIS incident report template" is one of Google Australia's top suggestions for this topic, and most of the templates floating around are copies of copies. The safest starting point is the list in the Rules themselves. Section 12 says your incident management system must record the following for each incident, and keep the record for 7 years from the day it's made. Section 25 separately says the record of a reportable incident is kept for 7 years from the day you notify the Commission.

Field in your recordWhat it coversWho usually fills it in
DescriptionWhat happened, including the impact on or harm to any person with disabilityThe worker who saw it or was told
When and whereThe time, date and place, if known. If not, when and where it was first identifiedThe worker
People involvedNames and contact details of the people involvedThe worker, checked by a manager
WitnessesNames and contact details of any witnessesThe worker, checked by a manager
Reportable or notWhether it's a reportable incident, and which kindYour nominated person or a manager
AssessmentWhether it could have been prevented, how well it was handled, and whether anyone else needs to be toldA manager
ResponseActions taken, including support given to the person affectedThe worker and manager
ConsultationConsultations with the person affected, and whether they've been given reports or findingsA manager
InvestigationDetails and outcome of any investigation you ranThe person who investigated
Recorded byName and contact details of the person making the recordWhoever writes it up

I'd add three times for your own tracking: when a manager or your nominated person was told, when the 24-hour notice was lodged, and when the 5-day report was lodged. Those show whether you met the timeframes. The Commission also says records must protect the privacy of the people affected, so keep them access-controlled, not in a spreadsheet anyone can open.

How many incidents get reported?

The Commission's Quarterly Performance Report for January to March 2026 says 9,494 reportable incidents were notified that quarter, a 13% increase on the previous quarter. Its April to June 2026 report breaks notifications down by state and type.

The Commission says the number of notifications "does not correlate to the number of actual instances of harm", because reports include allegations, repeats and near misses. For a small provider the point is the workload. One incident means a write-up, an assessment, a 24-hour notice, a 5-day report, follow-up actions and a record kept for 7 years. Even a handful a month is a real load on the managers who also run rosters and claims.

Where incident paperwork goes wrong, and what to automate

Most of the risk sits in the gaps between people. These are the parts I'd look at automating, and they all keep a person making the decisions:

  • One way to report: a single online form on any phone. The Commission's incident management page gives this very example, "an online form that's submitted in the appropriate business system and automatically assigned to the Client Safety Manager".
  • Instant alerts to your nominated person and a backup, showing when the 24 hours runs out, then reminders before the 5-day and any 60 business day deadline. If nobody ticks "lodged", the reminder goes to the next person up.
  • Drafts from the form, so the manager reviews the portal fields instead of retyping them. A person still decides and lodges.
  • A register that shows each incident from report to close, with Commission emails filed against the right incident.

If you're not sure whether incidents are your biggest time drain, the free AI readiness check takes about 3 minutes and shows where automation would save your team the most time. Incident reporting is one piece of a wider compliance picture. For the other dates, like insurance, worker screening renewals and registration, our guide on how NDIS providers stop missing compliance deadlines covers the obligations register method.

If AI drafting is part of the plan, our post on whether ChatGPT is safe for NDIS participant data explains how to keep participant names out of it.

We've built compliance reminders before. For an NDIS provider in the middle of an audit, we built a compliance setup where every obligation sat in one register and reminders went out on their own, with a watcher on the regulator inbox writing to an evidence log. You can read about it in our NDIS compliance automation case study.

Worked example: one incident, start to finish

Say a 20-person registered disability support provider in Mackay, with an on-call team leader, an operations manager named as the person who notifies the Commission, and Microsoft 365. The example is made up and has no real person's details.

  1. Friday, 7:40pm. A support worker finishes a shift and fills in the incident form on her phone. She describes a fall that looks like a broken wrist, what she did, and who else was there. The form saves straight into the provider's incident register.
  2. Friday, 7:41pm. The team leader and the operations manager get a text showing when the 24-hour window closes. The team leader calls the worker to check the person is safe and the family knows.
  3. Saturday morning. The operations manager reads the form. She decides it's a reportable serious injury, because the Commission's guidance lists fractures as serious injuries. The system has already drafted the portal fields from the worker's write-up, so she checks them, fixes two lines and lodges the 24-hour report herself in the NDIS Commission Portal. She ticks "24-hour lodged" and the time is recorded.
  4. The following week. A reminder lands with the time left to lodge the 5-day report. She adds the witness details and the follow-up actions: a review of the person's mobility support and a refresher for staff. She lodges it and ticks it off.
  5. After that. Each action has an owner and due date in the register. She records the outcome and the conversation with the person and their family, and the record stays in an access-controlled folder for 7 years.

Every decision in that list stayed with a person, and the automation just kept the information from sitting in someone's car over the weekend.

What stays with a person

Some parts of incident management should never be automated, and I'd say no to building them:

  • Making sure the person is safe, and calling 000 if they need medical care or a crime may have happened. The Commission says not to delay this.
  • Deciding whether an incident is reportable and which kind it is.
  • Lodging the report and signing off what it says.
  • Talking with the person affected and their family or guardian, and involving them in how it's resolved.
  • Investigations, findings and any action about a worker.

Software can help you keep the records and reminders the Commission asks for. The judgement calls stay with your team.

What else is changing for providers

Registration and plan changes are coming in 2027, and our guide to the NDIS changes in 2027 sets out the dates. For what else providers can safely automate, see AI automation for NDIS providers.

If your incident forms, alerts and register live in three different places, book a free call and I'll tell you what I'd connect first. Our workflow automation service builds this kind of form, alert and register setup in the Microsoft 365 or Google Workspace you already use, and you own it.

This guide is general information, not legal advice. Your obligations are set by the NDIS Act and Rules, so check the NDIS Commission's reportable incidents page or contact the Commission if you're unsure about a particular incident.

Sources

Facts checked 19 November 2026.

Incident forms, alerts and records in too many places? Tell us how incidents reach you now. We'll show you what we'd connect first, and what should stay with your team. Book a free call.