Skip to content
Skip to content
Build n Bloom
Menu
How we helpExamplesAbout
Book a Fit Call
FIELD NOTES / Continuity archive
Continuity archive·3 min read

NDIS Reportable Incidents: Notification, Further Information and Evidence

Distinguish immediate incident notification, further information and restrictive practice timeframes; retain awareness and submission evidence under current Commission instructions.

11 June 2026·Rayan Ratego

The reporting timetable depends on the category. This article was checked against the Commission's portal guide on 27 September 2026. Use current Commission instructions and the rules applicable to your organisation; this is a preparation guide, not a finding that any provider is compliant.

Notification and further information are different steps

For most reportable categories, the immediate notification is due within 24 hours of key personnel becoming aware. Further information is due within five business days of that awareness. The five-day submission is not necessarily the final investigation outcome: the Commission can request more information and providers can add updates. The Commission's reporting process map describes these steps.

Unauthorised restrictive practices have a different timetable. The Commission's reportable incidents guidance lists five business days, with reporting within 24 hours where harm resulted. Check the category and current instructions rather than applying one clock to everything. Actual and alleged incidents require attention; do not wait for a completed investigation before making a required notification.

Categories to check

Check whether the actual or alleged event connected with NDIS support delivery falls within the reportable categories: death, serious injury, abuse or neglect, unlawful sexual or physical contact or assault, sexual misconduct, or unauthorised restrictive practice. Keep the facts and immediate safety response visible while the authorised person determines the applicable category; this list does not make that determination for them.

Keep the awareness chain visible

Participant safety and prompt internal escalation come first. Record the occurrence time, discovery time, when key personnel became aware, who received the report and each escalation. Do not treat a slow internal handoff as permission to defer action. The original article's hypothetical auditor scenario did not establish a different legal trigger.

Useful checks for your own operation include:

  • Trace one recent permitted case from first report to escalation and submission, retaining the actual timestamps.
  • Check who receives an after-hours report and who can act when the ordinary owner is unavailable.
  • Separate what was reported, what the records establish and what remains unverified.
  • Preserve the original intake and later corrections; do not reconstruct a clean-looking initial record retrospectively.
  • Record immediate safety actions, outstanding information, the accountable decision-maker and submission receipts.

These are preparation methods, not measured claims about typical providers or a substitute for professional advice.

Registration requires its own applicability check

The SIL registration guidance describes transition pathways based on services and existing registration status. Do not infer that every previously unregistered operator had the same day-one pathway. Determine the applicable registration position separately from the incident-reporting process.

Where a system can help

Structured intake can help prepare an evidence record, flag incomplete information, route it to a named person and track a chosen deadline. Its output does not establish the legal category, timely notification or compliance. A responsible person decides, reviews and submits through the organisation's authorised process. A draft or saved portal entry is not a submission receipt.

The current Firm Capacity System concerns defined work within services a firm already sells. This NDIS reference does not broaden an existing client agreement or promise automated compliance. Any implementation requires separately agreed scope and acceptance.

RR

Rayan Ratego · Co-Founder, Build n Bloom

Rayan Ratego is co-founder of Build n Bloom. He brings 13 years of operating experience in disability services and leads delivery architecture, controls and system performance.

Next step

Have one recurring workflow your senior people keep searching for, correcting or rescuing? The no-fee Fit Call tests whether it has a clear owner, material consequence and responsible next step.