NDIS Incident Management System for SIL: What the Practice Standards Require

What the Practice Standards require of a SIL incident system

There are two sources of truth here, and you have to satisfy both. The first is the NDIS Practice Standards, which set the quality benchmark for your systems. Incident management is a specific outcome the Standards require: every registered provider must have, and actually use, a documented system for receiving, recording, responding to, investigating and learning from incidents — and for making sure participants know how to raise one and are supported to do so. The second is the NDIS (Incident Management and Reportable Incidents) Rules 2018 (the Rules), which sit under the National Disability Insurance Scheme Act 2013 and set the legal obligations for what you must report to the NDIS Commission, and how fast.

The distinction matters because a SIL provider can be doing one well and failing the other. You can investigate incidents diligently and still be non-compliant if you miss a Commission notification. You can notify the Commission on time and still be non-compliant if you have no internal system to investigate the incident and stop it happening again. The Practice Standards and the Rules are designed to interlock, and your documentation has to give effect to both. For the broader, line-by-line breakdown of the policy document itself, our companion guide on the 12 elements of an NDIS incident management policy walks through each required clause; this article is about the system — how those obligations actually run inside a supported living home.

Why incident management is different in a SIL home

Most NDIS incident guidance is written for services delivered in blocks — a few hours of community access, a therapy session, a day program. Supported Independent Living is different in ways that change the whole shape of your incident system, and it is exactly these differences the new SIL module of the Practice Standards is built to scrutinise.

SIL supports are delivered around the clock, inside a person's home. That means incidents can happen at 3am, on a weekend, with a single worker on shift and no manager in the building. It means the "environment" the auditor examines is a real house — its medication storage, its exits, its bathrooms — not a clinic. And in shared SIL arrangements it means incidents can arise between co-tenants, not just between a worker and a participant: one resident's behaviour can be a safeguarding incident for another resident living in the same home.

This is also where incident management connects to the rest of your SIL paperwork. The line between a participant's tenancy and the supports you deliver has to be clear before you can manage an incident properly — our guide on the difference between a SIL tenancy agreement and a service agreement explains why a co-tenant conflict is handled differently from a support-delivery failure. And because SIL is where the audit physically enters a home, the things an auditor checks in a SIL service include whether your incident system reaches into overnight shifts and the physical environment, not just office hours.

Reportable incidents in a SIL setting

Not every incident is a reportable incident, and conflating the two is one of the most common SIL audit failures. An incident is any act, omission, event or circumstance that occurs in connection with providing supports and has, or could have, caused harm to a participant — a fall, a medication error, property damage, a near miss. All of these go into your incident system. A reportable incident is a specific, defined subset that must also be notified to the NDIS Commission.

The reportable incident categories are set out in the NDIS Act and the Rules. They are a closed list — only events that match these definitions are reportable to the Commission. In a SIL home, each one has a characteristic way of arising:

For the precise legal definitions, the difference between a serious and a non-serious reportable incident, and how the follow-up report works, see our dedicated NDIS reportable incidents guide. The point for SIL specifically is this: your workers have to be able to recognise these categories in a real home, under pressure, often alone. A policy that lists the categories is not enough — your system has to put that knowledge into the hands of the person on shift.

The notification timeframes you cannot miss

The Rules prescribe timeframes that are not targets — they are legal obligations, and they start running the moment your organisation becomes aware of the incident, not when a manager next checks their email. For a SIL provider running overnight shifts, this is the single most important operational design choice in your whole system.

The seven parts of a working SIL incident system

An incident "system" is not a single document. It is the set of moving parts that, together, let you detect an incident, respond safely, report it on time, learn from it, and prove all of that to an auditor. For a small SIL provider, here is what each part has to do.

1. Incident management policy The governing document: purpose, scope, definitions aligned to the Rules, the reportable categories, timeframes, the investigation and corrective-action process, training, review cycle and document control. This is the policy our companion guide breaks into 12 elements.
2. Incident management procedure The step-by-step "what do I do right now" for the worker on shift — immediate safety first, who to call, how to escalate after hours, when something is reportable, and how to complete the form. This is the part that has to work at 3am.
3. Incident report form A structured form capturing date, time, location, participant (by identifier), workers present, a factual description, immediate actions and a first classification. In SIL it should prompt for co-tenant involvement and the physical environment.
4. Incident register The contemporaneous log of every incident and its lifecycle — the time-series proof the system is being used. The most-checked, most-failed component (see below).
5. Escalation and on-call pathway A documented after-hours route from the worker on shift to a decision-maker who can assess reportability and lodge a Commission notification inside the 24-hour window. Non-negotiable for SIL.
6. Investigation and corrective action Who investigates (someone not involved in the incident), how findings translate into actions with an owner and due date, and how completion is verified. Corrective actions without follow-through are a classic finding.
7. Training and review Evidence that every worker has been trained to recognise and report incidents, and a scheduled review of incident data so a pattern across shifts, workers or homes gets caught — exactly what the new SIL consistency focus is looking for.

The overnight and lone-worker problem (and how to solve it)

This is the part of a SIL incident system that fails most often in practice, and it is unique to around-the-clock supported living. Picture the realistic scenario: a single worker is on a sleepover or active-night shift. At 2am a participant falls and is clearly seriously injured. The worker calls an ambulance and provides first aid — good. But your reportable-incident clock has now started, and the worker is alone, focused on the participant, with no manager in the building.

If your "system" assumes a manager will pick this up when the office opens at 9am, you have already missed seven hours of a 24-hour deadline before anyone with portal access even knows. The fix is to design for the worst realistic shift, not the best:

• A documented on-call number the worker can reach at any hour, staffed by someone authorised to assess reportability
• At least two people with my.ndiscommission.gov.au portal access, so a notification can be lodged even outside business hours
• A laminated immediate-response card in each home — safety steps, who to call, what's reportable — so nothing relies on memory under stress
• A clear instruction that a verbal report to on-call comes first, with the written form to follow within 24 hours
• Handover notes that flag any injury, behaviour or near-miss discovered (not witnessed) so the next shift assesses it against the reportable threshold

Good SIL overnight shift notes are part of this safety net — they are often where a discovered injury or an escalating behaviour first gets recorded, which is why the new SIL module's focus on consistency across shifts is really a focus on whether your overnight system is as strong as your daytime one.

The incident register: your proof the system runs

If an auditor only had time to look at one thing in your incident system, it would be the register. A polished policy proves you can describe a system; a current register proves you have one. The register is an internal governance log — it holds more detail than what you submit to the Commission portal — and it is where the auditor reconciles your paperwork against what actually happened in the home.

For a SIL provider, a defensible incident register tracks each incident from the moment it occurs to the moment the file is closed:

• Unique incident reference number
• Date and time of the incident, and date and time you became aware
• Location (which home, which area)
• Participant identifier and any co-tenant involvement
• Worker(s) on shift (by role or identifier)
• Classification — minor / moderate / serious / reportable
• Whether it was reported to the Commission, plus the notification date and reference number
• Investigation status and the responsible person
• Corrective actions with an owner and due date, and their completion status
• Date the incident file was closed

The two failures auditors flag most are the stale register (entries that stop months ago, suggesting the system died) and the unexplained gap (an event in the register that looks serious but has no matching Commission notification). The Commission can see what you have lodged, so a discrepancy between your register and your notifications is visible to the auditor. Our deeper incident register guide covers what to track and how to keep it audit-ready; the SIL-specific lesson is to add columns for the home and for co-tenant involvement so trends in a particular house are visible.

The templates a small SIL provider needs

You do not need to invent any of this from a blank page, and you should not download a generic template that has never been checked against the current Rules. A small SIL provider needs a tight, mapped set of documents that work together:

The reason a mapped set beats a single downloaded policy is that auditors test for consistency between them: the timeframe in your policy has to match the timeframe in your procedure, which has to match what your form prompts and what your register records. Mismatches between documents are findings even when each document looks fine on its own. If you are weighing the build-it-yourself route against buying a mapped set, our breakdown of what NDIS compliance actually costs compares the real hours against template and consultant pricing.

What an auditor checks in a SIL incident system

Understanding the auditor's view is the fastest way to close gaps before your audit date. For a SIL service specifically, expect them to test four things:

The documents agree with each other

Policy, procedure, form and register are pulled together and checked for consistency. Definitions, timeframes and the reporting pathway must line up across all of them, and they must describe what you actually do — not placeholder text with another provider's name still in it.

Frontline workers can answer the practical questions

Auditors interview support workers, not just managers, with questions like "What would you do if you found a participant injured at the start of your shift?" and "What's a reportable incident?" In SIL they will probe the overnight scenario specifically. Training records alone will not satisfy this — the worker has to be able to demonstrate the knowledge.

The register reconciles to reality

The register is checked for currency and completeness, and any serious-looking entry is cross-checked against whether a Commission notification was lodged. Gaps and stale entries are findings.

You are using the data, not just collecting it

Evidence that incident trends are reviewed — meeting minutes, a periodic incident summary — shows the system is functioning as a continuous-improvement loop, which is exactly what the new SIL module's consistency and safeguarding focus is built to detect. This connects to the wider set of evidence layers in our guide to what auditors check for SIL providers.