NDIS planning testing and SDA: A role-boundary checklist
The NDIA's 28 September 2026 update says thousands of people have now taken part in testing the new way of planning before rollout from April 2027. Early feedback is encouraging, but it also names practical gaps: some participants want clearer information before the assessment, more time to explain fluctuating support needs, and better support or adjustments to take part. For SDA providers, that should not trigger a scramble to predict future plan budgets. It should trigger a cleaner role-boundary workflow: support residents with factual preparation, protect consent, separate testing from current claims, and keep owners away from private planning details.
Keep testing separate from live SDA decisions
The current testing invitation is clear that taking part is voluntary and does not change a participant's current plan, future funding, eligibility, supports or plan budget. That matters for SDA teams because a support needs assessment conversation can sound close to the evidence providers already hold about dwelling fit, support routines, overnight risk, communication needs and home access.
A provider can help a resident understand their records and rights without treating the test session as a planning submission or claim trigger. The operating record should show the difference between a current plan fact, a service agreement requirement, an SDA claim control, a participant preference and a voluntary testing activity.
That separation protects the participant from pressure and protects the provider from making unsupported promises about April 2027 reforms.
Build the planning-testing role checklist
Use this checklist when a resident, nominee or support network asks for help with new-way-of-planning testing, a support needs assessment practice session, a planning forum, or preparation material connected to the reform rollout.
Confirm authority first
Record whether the request came from the participant, nominee, guardian, support coordinator, family member or another provider. Check consent before sharing plan, agreement, support or dwelling information.
Log the testing status
Use states such as interested, invited, applied, selected, session booked, adjustments requested, attended, feedback submitted or no action. Do not use claim-ready or plan-approved language.
Prepare facts, not scripts
Help the participant find factual records about their current dwelling, communication needs, routines, access requirements, service agreement, incidents, repairs and support-provider handoffs without coaching answers.
Record requested adjustments
Capture interpreter, captioning, communication, technology, meeting-length, support-person, sensory or timing needs so the provider can support access without taking control of the participant's feedback.
Separate claims and testing
Keep SDA claim runs tied to the current plan, enrolled dwelling, service dates, pricing inputs, my provider status and agreement evidence. A test session does not create or remove claim authority.
Protect feedback privacy
Store only the operational facts the provider needs. A resident's comments about the planning experience should not be copied into owner reports or broad referral notes.
Close with next actions
After the session, record any participant-requested follow-up such as plan-sharing consent, service-agreement review, communication preference update, support-provider handoff or ordinary plan-change enquiry.
Support needs language matters in SDA homes
The NDIA says support needs assessments will be a guided conversation about disability-related support needs. The Department's new framework planning page describes a four-step future journey: preparing for a support needs assessment, completing the assessment, building a plan and using the plan.
SDA providers sit close to real daily-life evidence, but they are not neutral assessors and should not try to become one. The useful provider role is to keep source facts clean: what dwelling features are used, what environmental barriers exist, what communication support works, what support-provider handoffs affect safety, how routines fluctuate, and what incidents or repairs changed the living arrangement.
That record helps participants and authorised supporters talk from facts. It also prevents the provider from slipping into sales language such as this design category will be funded or this testing session should unlock a move-in.
Consent controls need to be visible
NDIS consent guidance says participants can choose who can access information, talk on their behalf, receive letters, make requests or update information. It also says consent can change and that ongoing consent needs the right record.
For SDA, the consent map should be easy to find before anyone helps with testing preparation. A provider may hold service agreements, dwelling notes, incident records, rent contribution records, my provider status, plan-sharing evidence and owner-reporting data. Those records should only be used in ways consistent with the participant's consent and the provider's role.
When a support coordinator, SIL provider or family member asks the SDA provider for evidence before a testing session, the response should be source-controlled. Share the minimum relevant information, record who received it, and do not bundle private participant history into a generic housing pack.
Do not turn testing into an owner forecast
Owner and investor reporting is where reform updates can become risky. A resident taking part in testing is not evidence that their SDA funding will change, improve, reduce, continue or end. It is also not a reason to disclose their disability details, planning feedback or assessment concerns.
Use neutral portfolio states instead: planning reform monitored, participant communication support updated, consent check pending, ordinary plan evidence under review, no current claim impact, or owner reporting restricted. If a current plan change, move, vacancy or claim issue exists, report that separately on its own evidence.
This discipline is especially important while many residents remain on current planning pathways and future new framework plans are expected to roll out gradually from April 2027.
Use the runway before April 2027
The new way of planning page says support needs assessments are intended to become part of planning from April 2027 and to make planning clearer, fairer and more consistent. The Department also says adults will move to new framework plans gradually from April 2027 to December 2030.
That gives SDA providers time to clean the operating record. Start with high-risk residents and vacancies: people with complex communication needs, recent incidents, possible transfers, plan changes, shared-home compatibility issues, OOA or OSS dependencies, RRC queries, support-provider changes or claim exceptions.
The goal is not to predict the final rules. It is to make sure each participant record can explain the current dwelling fit, current plan basis, consent position, service agreement state, support handoff, claim status and owner-safe reporting boundary.
How StepFree fits the workflow
StepFree SDA is designed for the operational layer beneath policy change: participants, dwellings, agreements, claims, communication, consent, vacancies, owner reporting and exceptions.
For planning testing, that means a provider can keep voluntary testing states, participant authority, evidence sources, claim controls and owner-safe labels connected without turning reform uncertainty into scattered spreadsheets or overconfident forecasts.
Conclusion
The new way of planning is still being tested, but SDA providers do not need to wait passively. They can prepare by separating voluntary testing from current claims, recording participant authority, keeping support-needs evidence factual, respecting consent, filtering owner updates and using the lead time before April 2027 to tidy high-risk records. That gives residents better support and gives providers a cleaner operating record when planning reform reaches live SDA workflows.
StepFree SDA helps providers keep planning reform notes, participant consent, claim readiness, service agreements and owner-safe reporting connected in one operating workflow.