Back to blog
Operations8 min read

SDA 2026 report: A market-alignment checklist for providers

The NDIA's 2026 Specialist Disability Accommodation Report is useful precisely because it is not a sales deck. It shows an SDA market that continued to grow in 2025, while also showing where supply and participant need can diverge by location, design category, build type and support model. For SDA providers, the report should become an operating-control prompt: review where vacancies are forming, where owner expectations are ahead of claim-ready demand, and where pipeline records need to be kept separate from enrolled dwelling income.

Read the report as an operations source

The report gives extra context to SDA data published through NDIA quarterly reports and uses current Agency system data up to 31 December 2025. It also says the report is not investment advice and does not predict future market performance. That framing matters for providers because the report is best used as a structured risk input, not as a promise that any one dwelling will fill.

The headline numbers are mixed in the way operators should expect. Participants with an identified SDA need increased during 2025, more participants were using SDA funding, and enrolled dwellings also increased sharply. At the same time, the report flags localised oversupply and mismatch risks where available SDA places exceed recorded participant need or where the dwellings being built do not match the build type most commonly recorded in participant home and living decisions.

That means a provider should not read national growth as portfolio-level certainty. A one-bedroom villa, a two-resident High Physical Support house, a three-resident house, a Robust dwelling and an older existing-stock home can all face different vacancy, claim, support-provider and owner-reporting risks in the same state.

Use build-type mismatch as a vacancy trigger

One of the most practical signals in the 2026 report is the gap between participant build-type records and recent supply growth. The report says house with 3 residents is the most common build type among participants with an SDA need who have a Home and Living recommendation. It also notes that recent supply growth has been concentrated in smaller dwelling types, including two-resident houses.

For providers, this should trigger a dwelling-by-dwelling review rather than a general vacancy campaign. If a vacancy sits in a two-resident dwelling, the provider needs to know whether the local participant pipeline actually includes people whose plan, support model, housemate preference, behaviour support needs, location preference and funding management align with that configuration.

The same logic applies to owner updates. It is not enough to say there is SDA demand in the state. Owner reporting should show the operational match: local SA3 demand signal, dwelling type, design category, maximum residents, support-provider availability, enquiry pipeline, vacancy listing status, claim-readiness state and any constraints that can be shared without exposing participant identity.

Build the market-alignment checklist

Use this checklist after each quarterly SDA data release, before accepting a new investor property, when a dwelling sits vacant, when a support partner changes, or when owner forecasts assume a faster move-in than the live participant pipeline supports.

Version the data source

Record the report, quarterly data release, demand-data extract, SDA Finder check and pricing source used for the review. Add the source date so future owner reports do not mix old market assumptions with current operating states.

Segment each dwelling locally

Track state, SA3, design category, building type, maximum residents, SDA type, enrolment status, OOA or OSS dependencies, available room count, vacancy age and whether the dwelling is actually ready for a participant inspection.

Match pipeline to participant need

Compare live enquiries against plan evidence, design category, build type, preferred location, housemate preferences, support model, funding management, my provider status and any current service-agreement dependency.

Separate pipeline from enrolment

Keep design-stage, under-construction, enrolment-submitted, enrolled-but-unoccupied and claim-ready states separate. A design-stage registration does not guarantee NDIA enrolment, participant fit or claim income.

Protect vacancy and claim controls

When a participant leaves, connect market activity to the vacancy record: NDIA notification, vacancy listing, notice evidence, room availability, enquiry history, move-in notification and whether any vacancy payment position is supported.

Filter owner reporting

Report market alignment, vacancy status, confirmed income, pending claim states and operational blockers without exposing participant plan details, support needs, nominee communications, disability information or private housemate discussions.

Treat pipeline data cautiously

The 2026 report shows a large design-stage pipeline and explains that design-stage registrations are for market oversight, not a guarantee that all listed dwellings will be enrolled once built. The report also notes that the NDIA has improved how it manages unfinished dwelling data to provide a more reliable view of potential future supply.

That should change how providers talk about pipeline. A dwelling in design stage is not the same as an enrolled dwelling. An enrolled dwelling is not the same as an occupied dwelling. An occupied dwelling is not the same as paid claim income until the participant, funding, service agreement, my provider pathway and claim period all line up.

A practical pipeline register should therefore carry conservative states: design-stage only, build complete, certificate available, final as-built certification held, enrolment documents ready, application submitted, RFI open, enrolled, participant matched, service agreement signed, claim started, payment reconciled and owner reportable.

Connect market alignment to claims and RRC

The NDIA investment guidance is clear that the NDIA does not guarantee returns and that SDA funding applies to participants, not dwellings. It also says owners and investors cannot make SDA claims unless they are the registered SDA provider, and that income depends on an eligible participant living in the dwelling.

Finance teams need that distinction in the operating record. Market demand can explain why a vacancy strategy is reasonable, but it does not prove a claim. The claim file still needs the enrolled dwelling, participant plan and funding basis, written service agreement, dates of residence, correct price source, funding management pathway and reconciliation to actual payment.

RRC and ordinary living-cost records need the same separation. A provider can use market data to decide whether a room is attractive to the right participant cohort, but RRC receipts, SDA claim income, vacancy payment evidence and owner distributions should remain separate ledgers with their own evidence and review states.

How StepFree fits the workflow

StepFree SDA can help providers turn market data into controlled operating records: enrolled properties, dwellings, participant pipeline, vacancies, service agreements, claims, RRC ledgers, owner reporting and compliance evidence.

The important part is the shared state. Business development can see whether a vacancy is market-aligned, operations can see whether a participant match is claim-ready, finance can reconcile actual payment, and owners receive a status that is useful without being privacy-invasive or unsupported by the source record.

Conclusion

The 2026 SDA Report gives providers a better market signal, but the operational value comes from how the signal is controlled. Treat national growth carefully, review local mismatch by design category and build type, keep design-stage pipeline separate from enrolled and occupied stock, protect claim evidence, and keep owner reports grounded in verified operating states.

StepFree SDA can help providers manage SDA market-alignment reviews, vacancies, claims, RRC ledgers, participant pipeline evidence and owner-safe reporting from one SDA operations workflow.