SCHADS Award changes and SDA: A roster-risk checklist

SDA funding pays for the dwelling and tenancy management, not the ordinary disability support roster. That distinction still matters. But the home does not operate in a vacuum. A roster change, classification correction, support-worker availability issue or provider cost shock can affect move-in timing, emergency response, shared-home compatibility, OOA access, service-agreement expectations and participant confidence.

The NDIS Annual Pricing Review explains that disability support worker prices are linked to SCHADS Award wage assumptions through the DSW Cost Model, while the Fair Work Ombudsman notes that SCHADS covers several streams with different pay and conditions. That is enough uncertainty to justify a controlled SDA dependency register, especially where the same organisation provides SDA and supports or where an external SIL, ADL or OSS provider is essential to the dwelling model.

The register should not decide award coverage. It should show which accommodation workflows depend on support rosters and where a payroll, pricing or workforce decision may create a participant, claim or owner-reporting risk.

Use this checklist before 1 December 2026, after any support-provider rate change, before accepting a complex vacancy, and whenever a shared home or apartment site relies on overnight or onsite support continuity.

Award classification and payroll compliance need HR, payroll or legal ownership. SDA operations should not make casual decisions about whether a worker belongs in a SCHADS stream, whether an enterprise agreement applies, or how a Fair Work decision translates into rates.

What SDA teams can do is create a handoff: affected dwelling, affected provider, support model, current service agreement state, participant communication owner, risk to move-in or continuity, claim-control impact and next review date. That makes the payroll issue visible without turning the property file into an employment-law file.

This is especially important for providers that run both SDA and support services. A combined organisation may have one brand, one finance team and one executive meeting, but the audit trail still needs to explain which function made which decision.

The highest-risk SDA scenarios are the ones where housing and support are tightly coupled: shared homes, OOA apartments, OSS buildings, residents with complex overnight needs, housemate-matching dependencies, hospital-return pathways and vacancies that only work if a support provider can sustain the roster.

NDIS OSS guidance says participants may have multiple providers, that clear information helps manage expectations, and that an OOA apartment must be available so OSS workers can be onsite when needed. It also says an OSS provider needs an agreement with the SDA provider to use the OOA apartment.

If workforce assumptions change, revisit those interfaces before they fail in daily operations. The practical questions are simple: who attends, who has access, who is backup, who tells the participant, who updates the agreement, who owns the evidence, and what owner-safe status should appear in reporting?

The September price-limit update says the 2026-27 Pricing Schedule will be updated later this year to reflect any required changes. That does not mean SDA owners should receive speculative income promises or warnings based on support-worker wage changes.

SDA teams should distinguish three registers: SDA price inputs for the enrolled dwelling, support-provider cost and roster assumptions, and owner distribution assumptions. They are related, but not interchangeable. A support-provider cost change may affect vacancy readiness or continuity risk without changing the SDA price for an enrolled dwelling.

Use neutral wording until there is an official source and an internal approval: pricing source under review, support-provider roster dependency being assessed, no current SDA claim change, owner forecast unchanged, or owner forecast pending approved pricing update.

NDIS record-keeping guidance expects complete and accurate records, including invoices, support logs, rosters, case notes and service agreements, and notes that SDA requires written service agreements. Roster and support-provider records also become important when a claim, incident, complaint, vacancy delay or continuity issue is reviewed later.

Keep the SDA record lean but connected. Store the dwelling status, participant agreement state, claim basis, support-provider dependency, communication task and owner-safe note. Link to the support or payroll source instead of duplicating sensitive worker records into the property file.

That gives finance, operations and compliance enough context to act without mixing participant support details, employment records and owner reporting into one uncontrolled folder.

StepFree SDA is built for the operating layer where dwellings, residents, claims, vacancies, support handoffs, exceptions and owner reporting meet.

For SCHADS-related roster risk, that means providers can keep support dependencies visible beside the SDA record, hold claim controls steady, assign follow-up owners and keep investor updates factual while the official pricing and workforce settings settle.