How to write an NDIS continuity of supports plan (2026 template + example)

What is a continuity of supports plan and who needs one?

A continuity of supports plan (sometimes called a business continuity plan or continuity of service plan) is a written document that sets out how a registered NDIS provider will keep delivering safe, quality supports to participants when its normal operations are disrupted. Disruptions can include sudden staff absences, a key worker leaving, natural disasters, IT system outages, a notifiable incident, or a public health emergency.

Under the NDIS Practice Standards, all registered providers must have governance and operational management systems that protect participants from harm — including from gaps in service delivery. For SIL (Supported Independent Living) providers, this obligation is particularly critical: participants living in SIL arrangements often have high support needs and cannot safely go without assistance even briefly. The strengthened 2026 framework reinforces that continuity planning must be a live, tested document — not a template that sits in a folder untouched.

The NDIS Quality and Safeguards Commission can and does review continuity arrangements during audits and in response to serious incidents. Providers without an adequate plan risk non-conformance findings, conditions on their registration, or enforcement action.

What the NDIS Practice Standards require

The NDIS Practice Standards sit under the National Disability Insurance Scheme Act 2013 and are administered by the NDIS Commission. For SIL and most registered providers, the relevant Practice Standards include:

• Governance and Operational Management — requires documented policies and procedures for maintaining safe service delivery, including when there are workforce or operational risks.
• Risk Management — requires providers to identify, assess, and manage risks to participants, including service continuity risks.
• Human Resources — requires sufficient, appropriately trained staff at all times, including contingency arrangements for unplanned absences.
• Incident Management — includes obligations to respond to and learn from events that disrupt or could disrupt supports.

The 2026 strengthened framework further emphasises active governance: Boards and senior leaders must be able to demonstrate — not just assert — that continuity arrangements are in place, tested, and understood by staff.

Step-by-step: how to write your continuity of supports plan

1. Define the scope and purpose
   State which services, locations, and participant cohorts the plan covers. For a SIL provider, name each house or cluster. Include the document owner, version date, and review schedule (at minimum annually, or after any activation).
2. Identify your risks and triggers
   List the scenarios that could disrupt supports. Common triggers for SIL providers include: unplanned staff absences or resignations, severe weather or natural disasters, a notifiable incident requiring site closure or staff stand-down, IT or rostering system failure, and participant health emergencies requiring hospital admission.
3. Map critical supports and minimum staffing
   For each SIL house, document the minimum safe staffing level (by time of day and day of week), which supports are critical to participant health and safety, and which participant needs are highest risk if a support gap occurs (e.g., medication administration, personal care, behavioural support).
4. Document your response procedures
   For each trigger scenario, write a numbered action sequence. Specify who is notified first, who has authority to call in agency or casual staff, what the escalation path is if cover cannot be found, and when the NDIS Commission must be notified (e.g., where a reportable incident has occurred or where participant safety is at risk).
5. List your contingency resources
   Include: names and contacts for casual/relief staff, your approved staffing agency contacts, mutual-aid arrangements with other providers if any, after-hours manager contact chain, and emergency services contacts. Keep this list current — outdated contacts are a common audit non-conformance.
6. Include participant-specific considerations
   Reference each participant's support plan for any continuity-relevant information, such as medication management needs, communication requirements, or behaviour support plan instructions that must be followed even in an emergency. Do not duplicate participant records — cross-reference them.
7. Set out communication obligations
   Document how and when participants and their nominees will be notified of a disruption, how you will keep them informed during an extended incident, and how you will document those communications.
8. Define testing and review requirements
   The plan must be tested — a paper document that has never been walked through is not sufficient for a Commission audit. Document at least an annual tabletop exercise, and record who participated and what actions were taken as a result. After any real activation, complete a post-incident review and update the plan accordingly.
9. Get sign-off from governance
   The plan should be approved by the CEO or Board (as appropriate to your governance structure) and that approval recorded. This evidences active governance oversight.

What to include: a practical template structure

Filled example: staffing shortage response procedure (excerpt)

Common mistakes to avoid

• Treating the plan as a one-off document. Auditors look for evidence of review, testing, and updates. A plan dated several years ago with no revision history is a red flag.
• No participant-specific content. A generic plan that does not acknowledge the specific needs of participants in each SIL arrangement will not satisfy the Practice Standards' person-centred requirements.
• Outdated contact lists. Staff contact lists and agency contacts that are not maintained are routinely flagged at audit as evidence of inadequate governance.
• No clear decision authority. If the plan does not specify who can make which decisions during an incident, staff will hesitate — and delays cost participant safety.
• Forgetting NDIS Commission notification obligations. Providers sometimes focus entirely on internal response and overlook their legal obligation to notify the Commission of certain events. The plan must reference the reportable incident framework.

If you are building or overhauling your SIL compliance documentation, the 136-document SIL compliance kit available at ndiscompliant.com.au includes a full continuity of supports plan template alongside your policies, procedures, and evidence registers — structured to align with the 2026 strengthened Practice Standards audit criteria.