Back to blog
Claims7 min read

SDA onsite shared support: A claim and access checklist

The NDIA's current onsite shared support guidance gives SDA apartment providers a new reason to tighten the boundary between accommodation, OOA space, unplanned support, planned daily supports and participant claims. Onsite shared support, or OSS, is unplanned support for participants who live alone in SDA apartments. It can be available 24 hours a day, seven days a week, usually shared between up to 10 people in the same apartment building. For SDA providers, the operating question is not only whether OSS is available onsite. It is whether the provider can show who uses the OOA apartment, which participants and support providers are in scope, which claim pathway applies, what evidence is retained, and what owner reporting can safely say.

Why OSS needs a separate SDA control

OSS sits beside SDA, but it is not the base SDA dwelling payment. Participant guidance says being eligible for SDA does not mean a participant is also eligible for OSS, and that participants with SIL in their plan will not receive OSS because it would duplicate supports already available through SIL funding.

The provider guidance also separates OSS from planned assistance with daily living. Planned support should be delivered through the participant's planned support arrangement, not treated as work for the OSS worker because another roster failed. OSS is for unplanned tasks and must not be treated as emergency services.

That distinction matters in operations. A provider may have an enrolled apartment, an OOA apartment, an OSS provider agreement, ADL providers, possible SIL providers, service agreements and owner reporting tied to the same site. If those records are not separated, a claim question can turn into an avoidable dispute about who delivered what, who can access the dwelling, and whether income is confirmed.

Control access to the OOA apartment

The NDIA says an OOA apartment must be available so OSS workers can be onsite when needed. SDA providers are paid to supply that OOA apartment for expected maintenance, property and tenancy management costs, and the guidance says SDA providers cannot charge rent for using the OOA.

The OSS provider needs an agreement with the SDA provider to use the OOA apartment. The NDIA recommends that the agreement address utility bills, damage beyond normal wear and tear, and that the OOA apartment is not used as a business headquarters, office or administrative space. If another provider will also use the OOA apartment, the agreement needs to change.

The access boundary runs both ways. The SDA provider controls the property, but the SDA Rules say a registered provider of supports must not restrict other NDIS providers from accessing an enrolled dwelling for the purpose of delivering support to an eligible participant. The NDIA OSS page says stopping OSS or other providers from accessing the OOA or participant apartment may breach that rule.

A practical OSS claim and access checklist

Use this checklist before opening an OSS arrangement, before the first weekly claim, when a participant moves in or out, when an OSS provider changes, when ADL or SIL boundaries change, and before reporting expected income to an owner.

Map the site and OOA record

Record the SDA site, enrolled apartment list, OOA apartment, access arrangements, utility responsibility, damage responsibility, permitted use, other provider access and date the SDA provider agreement was last reviewed.

Confirm participant fit

Check whether each participant lives alone in an SDA apartment with OSS, whether OSS funding or flexible core and home and living funding is being relied on, whether SIL is excluded, and whether the participant can safely use an unplanned support model.

Separate planned and unplanned support

Keep OSS states separate from ADL rosters, SIL support records, planned personal care, missed shifts, emergency response and maintenance work. Use clear labels so a weekly OSS claim is not used to hide unrelated service delivery issues.

Lock service agreement evidence

Keep the participant OSS service agreement, provider-to-provider OOA agreement, complaint process, change or exit terms, participant onboarding notes and consent boundaries linked to the site and participant records.

Check my provider and claim pathway

For NDIA-managed OSS claims, record registration status, my provider status and the support item 01_066_0115_1_1 before claiming. For plan-managed or self-managed pathways, keep invoice, agreement and payment evidence separate from direct provider claim states.

Reconcile before owner reporting

Report only owner-safe operational states: OOA available, OSS provider active, participant scope under review, claim submitted, payment reconciled, claim queried or income not confirmed. Do not disclose participant support details, portal screenshots or private provider correspondence.

Treat the weekly claim as an availability record

The NDIA says OSS is funded as a weekly amount and the provider claims the same amount each week for providing OSS because the worker is available when needed. The 2026-27 NDIS Pricing Schedule lists support item 01_066_0115_1_1, Unplanned onsite shared supports in Specialist Disability Accommodation, with a weekly unit.

That weekly structure creates a different evidence question from an hourly support log. The provider should still keep complete and accurate records, but the operational record needs to show availability, site coverage, participant scope, service agreement status, provider relationship status and any week where the ordinary assumptions changed.

Useful weekly exception labels include OOA unavailable, OSS worker not onsite, participant moved out, participant changed support model, SIL funding identified, service agreement unsigned, my provider request pending, claim queried, partial week under review, provider agreement expired or owner report on hold.

Manage viability without overpromising

The NDIA provider guidance says OSS pricing is based on support being shared among up to 10 participants, and that each SDA site will have different needs and requirements. It also says an OSS worker must always be at each site and that participants can only share an OSS worker within the same apartment building.

That means vacancy and site mix matter. An SDA provider should not present OSS as guaranteed income or guaranteed suitability for every participant. The record should show the number of participants expected in the OSS arrangement, the service provider responsible for staffing, whether the site coverage requirement is met, and which vacancies or transfers could change viability.

This is especially important for owner and investor reporting. Owners can understand that an OSS arrangement is active, under review or not yet claim-ready. They should not be told that the site will produce recurring OSS-related income until participant scope, provider agreement, claim pathway and payment evidence support that statement.

How StepFree fits the workflow

StepFree SDA can help providers keep OSS from becoming another loose spreadsheet or inbox trail. A useful OSS record connects the enrolled apartment, OOA apartment, participant scope, provider-to-provider agreement, service agreement, my provider state, weekly claim state, payment reconciliation, exception reason and owner-safe reporting status.

That does not replace the NDIA, the OSS provider, participant choice, emergency planning or official claiming guidance. It gives SDA operators one controlled place to show what was checked, who owns the next action, which claims are ready, and which owner-facing figures should stay conservative until payment evidence is clear.

Conclusion

Onsite shared support can make independent apartment living more workable, but only when the SDA provider keeps the accommodation, OOA access, unplanned support, planned support, service agreement and claim records separate. Providers should verify participant fit, control the OOA agreement, track weekly availability, check my provider and payment pathways, review site viability and keep owner reporting tied to confirmed evidence.

StepFree SDA can help providers manage OSS access records, participant scope, weekly claim states, payment exceptions and privacy-safe owner reporting in one SDA operations workflow.