Guide
Interim behaviour support plan deadlines: what to track and when to review
In short: An interim behaviour support plan addresses immediate support needs while assessment and comprehensive planning continue. Where section 19 applies, development is due within one month of the specialist provider’s engagement, with a comprehensive plan within six months. Record development, lodgement and review dates separately. NDPRO helps behaviour support practices review recorded BSP dates and milestones across their caseload.
A useful review answers three questions: which participant needs attention, what is actually outstanding, and who will follow up? A date without its meaning can hide a problem. A plan marked complete may still have a separate lodgement or evidence question to resolve.
Keep the underlying duty separate from an internal target. Where section 19 applies, the specialist provider's one- and six-month plan-development periods run from engagement. The implementing provider's relevant first-use responsibilities must be checked separately. See the Restrictive Practices and Behaviour Support Rules, sections 11–13, 19 and 24. The detailed scope and trigger explanation below remains part of this guide.
What's the difference between an interim and a comprehensive behaviour support plan?
An interim behaviour support plan provides initial strategies for a person's immediate support needs while further assessment and planning continue. A comprehensive behaviour support plan is informed by a functional behaviour assessment and provides the fuller plan for support. See the Commission's specialist-provider guidance.
For a practice manager, the useful distinction is what has been completed and what is still needed. Record the current plan version, the development milestone and the next task. A completed interim plan does not by itself close the comprehensive-plan milestone.
The deadline, and what it applies to
Section 19 applies where a regulated restrictive practice has been used in relation to a participant and a specialist provider is engaged as a result to develop a plan containing that practice. It requires the specialist provider to develop an interim plan within one month and a comprehensive plan within six months of engagement. Section 24 separately requires lodgement as soon as practicable after development. The development and lodgement milestones must not be merged.
This is scoped narrowly, and it matters that it stays that way. The statutory deadline applies specifically to plans that contain a regulated restrictive practice. A plan without one does not carry the same legal clock — though the Commission's own guidance still recommends working to the same timeframes, and a practice that only watches the clock when a restrictive practice is already identified will find that out too late for the participants where it was not obvious on day one.
What starts the clock — and what does not
The clock starts on engagement, not on the referral and not on the initial assessment. The Commission's specialist-provider guidance explains engagement as the date of the service agreement, or a date specified within the agreement — an agreement can state when the provider is to begin developing the plan.
A separate clock binds the implementing provider. Where a regulated restrictive practice is being used without a plan and is likely to continue, the Rules (ss11–13) require the implementing provider to take reasonable steps to facilitate an interim plan within one month, and a comprehensive plan within six months, of the practice's first use — not of engagement.
That distinction is where tracking actually breaks. A referral can sit for weeks before it becomes an engagement. An assessment can be scheduled before either. If the date a practice uses internally to "start the countdown" is the referral date, the wrong plan looks late and the right one looks early — and if it's the assessment date instead, a genuinely overdue interim plan can look like it still has time. Neither error is visible until someone checks the actual service agreement date against the actual development-completion date, which is exactly the kind of reconciliation that doesn't happen until an audit asks for it.
What the evidence has to show
Two things, and they are different questions:
- That the plan was developed inside the period. This is a date comparison — engagement date against the date development was completed; record lodgement separately — and it is only as reliable as whichever date the practice used to start counting, which is the point above.
- That workers were trained to implement it. The Commission's guidance on this outcome asks not just that the interim plan existed, but that the people delivering support against it knew what was in it. Finishing development on time does not establish that the support team received the plan or was trained to implement it.
Module 2A's interim-plan outcome asks for collaboration with mainstream services, support for the specialist provider's development of the plan, and trained workers; the timeframe itself is a Rules obligation. Track the development deadline and retain evidence of when the plan was completed. Record lodgement separately, and retain evidence that workers received the implementation training relevant to their role. See what Module 2A asks for, outcome by outcome for the full picture of how this sits alongside the other seven outcomes.
Where this fails across a caseload
One participant is a date comparison anyone can do by hand. A practice running twenty, forty, or a hundred participants at once is running that comparison that many times, continuously, against engagement dates that don't all fall on the same day — and the failure mode isn't usually "we missed the deadline". It's "we noticed three weeks after we should have", because nothing was watching the gap between engagement and development completion until someone went looking.
A weekly deadline review a Director can actually use
The following is a synthetic NSW practice example, not a participant record or a measured NDPRO result. Use it to test your own process and any software demonstration.
| Review item | What to record | What closes the question |
|---|---|---|
| Engagement anchor | The service agreement's applicable engagement/start date and its evidence reference | An authorised person has checked the source date |
| Provider role and scope | Specialist provider or implementing provider; whether a regulated restrictive practice is in scope | The relevant duty and trigger have been identified |
| Original plan deadline | Interim and comprehensive dates derived from the applicable trigger | The original date remains visible after a target is changed |
| Operational target | An earlier internal target, or a later recovery target with reason and owner | A target is clearly distinguished from the underlying obligation |
| Development and lodgement | Separate completion dates, plan version and official lodgement receipt | The actual plan and receipt can be retrieved |
| Next action | Named owner, due action and next review | Evidence is reviewed before an item is closed |
For a fictional specialist provider engaged on 1 September 2026 following use of a regulated restrictive practice to develop a plan containing it, the one- and six-month development dates are 1 October 2026 and 1 March 2027. An internal target of 25 September brings preparation forward. Moving that internal target to 8 October does not itself extend the statutory deadline. The implementing provider's first-use responsibilities must be checked separately.
A date labelled “complete” is not enough: ask the person reviewing it to open the supporting record. A plan with no regulated restrictive practice needs the correct clinical review arrangement; do not present the statutory RRP timeframes as universally mandatory.
Download the synthetic Director review worksheet. It provides example questions and closure evidence, not automated date calculations or a legal determination. For the wider record trail, use the specialist audit-readiness guide.
Common BSP deadline and review questions
Does changing the allocated practitioner restart the deadline?
No. A practitioner change within the same specialist provider does not move the engagement anchor. The Commission's February 2026 position statement distinguishes this from changing specialist providers. Keep the original source date visible when reallocating a participant.
Is the lodgement date the development-completion date?
They are separate events. Keep a reference to the finalised plan and a separate official submission record. Section 24 requires a plan containing a regulated restrictive practice, including a reviewed plan, to be lodged as soon as practicable after development; a completed internal task is not a lodgement receipt. Behaviour Support Rules, section 24.
When is a comprehensive BSP due for review?
For a comprehensive plan containing a regulated restrictive practice, section 22 requires review at least every 12 months while it is in force, and as soon as practicable after a change in circumstances requiring amendment. This is separate from the original one- and six-month development periods. Behaviour Support Rules, section 22.
Does correcting a plan restart the annual review clock?
Administrative edits alone do not demonstrate a review or change the date the plan came into force. The Commission's May 2026 guidance distinguishes these edits from a substantive review. Record the reason for a version change rather than treating every new file date as a new review date. If an edit affects RRP authorisation status, the guidance calls for a full review.
What should a Director check in a weekly review?
Start with unresolved work rather than a colour or completion percentage. For each item, ask for the applicable date, the record supporting it, the outstanding action and the person following up. These are suggested review questions, not a prescribed Commission checklist. The fictional example above shows one way to organise them. Review the capability evidence behind workforce decisions separately from the participant's plan dates.
A caseload review using NDPRO
NDPRO's participant pathway brings the recorded engagement anchor, interim and comprehensive plan dates and milestone status into the same workflow. Original due dates and operational targets remain distinct.
Start with a participant whose pathway needs attention. Review the recorded stage and dates, then open the relevant evidence. Is the outstanding work plan development, lodgement, a clinical review or clarification of a source date? Agree the next action through your practice's follow-up process.
For a fictional review, an interim plan's original development deadline is 1 October. The team records a later recovery target of 8 October. That later target helps organise the follow-up, but does not itself extend a statutory deadline. A completed milestone should be supported by the corresponding record; development and lodgement remain separate steps.
In a 30-minute walkthrough, ask to see the original dates, a later-target request, its recorded status and the completed milestones for a fictional participant. This shows how the practice can review its dates and decisions without suggesting that a status change makes a legal determination.
NDPRO works independently. The Splose connection is optional. Your team remains responsible for clinical decisions, the applicable legal triggers, the correctness of the dates and required submissions; NDPRO does not develop the clinical plan or submit it to the Commission.
Review the linked restrictive-practice records or book a 30-minute NDPRO walkthrough.
Related: what Module 2A asks for, outcome by outcome · behaviour support supervision, and what has to be on the record · state-by-state restrictive practice authorisation.
Sources: NDIS (Restrictive Practices and Behaviour Support) Rules 2018, ss19 and 24, the Commission's specialist-provider guidance, and the NDIS Quality and Safeguards Commission's Supplementary module: Implementing behaviour support plans. Originally read 1 September 2026; reviewed 21 October 2026 alongside the February provider-transfer position statement and May monitoring/review guidance cited above. Check the current official sources for your circumstances.
Related workflow: BSP handover to implementing providers.
Related guides: Changing specialist provider with an existing BSP · Preparing BSP monitoring and review evidence.