Programs of Support in shared accommodation: An SDA boundary checklist

The NDIA says a Program of Support is an optional agreement between a participant and a provider for up to six months. It sets out the activities to be delivered, the outcomes being worked towards and the level of support needed. The same update says participants can leave a Program of Supports at any time, with no cost, by giving up to two weeks' notice.

For SDA providers, the key word is optional. A Program of Support may sit beside an SDA tenancy, SIL arrangement or daily support model, but it is not the SDA agreement and it is not the SDA pricing basis. Treat it as a linked support record that may affect household operations, not as proof that SDA income is locked in for six months.

Use plain states that operations, finance and compliance teams can understand: no linked Program of Support, program proposed, program active, participant notice given, support provider changing, support continuity risk, and closed. That language is more useful than burying the issue in notes.

NDIS SDA guidance says SDA is the housing itself and does not include personal care, supported independent living, individualised living options or assistive technology. It also says many people in SDA have other in-home supports, and that SDA funding pays the SDA provider while SIL funding pays for carers and the participant pays rent and bills.

That distinction should be visible in your records. The SDA service agreement should identify the dwelling, SDA provider, reasonable rent contribution handling, SDA claim pathway, responsibilities for the home and review triggers. The support provider's Program of Support or service agreement should identify the support activities, outcomes, level of support, dates, notice terms and support-provider responsibilities.

Do not merge these records just because the same person lives in the same home. A shared accommodation support program can help explain how daily support is organised, but SDA claim readiness still needs the enrolled dwelling, eligible participant, written SDA agreement, correct provider relationship and accurate claim dates.

SDA teams do not need to own every support-provider document. They do need a reliable summary of the linked supports that affect the home. Useful fields include participant consent status, support provider entity, support category, program start and end dates, notice period, support-provider registration or application status where relevant, household coverage assumptions, after-hours escalation, incident handoff, and the date the record was last confirmed.

For SIL-linked households, add the 0138 transition fields. Current NDIA guidance says SIL claims and registration requirements changed from 1 July 2026, and unregistered SIL providers who were delivering SIL before 1 July need to apply for registration by 1 October 2026 if they want to keep providing SIL after that date. That matters to SDA operations because a support-provider disruption can affect placement stability even when the SDA dwelling remains enrolled.

Keep the register factual. It should tell the team whether support continuity is clear, pending or at risk. It should not contain unnecessary clinical detail, private plan notes or unsupported conclusions about participant suitability.

Shared accommodation can blur commercial incentives. An SDA provider may have a preferred SIL partner, an owner may want fast occupancy, or a support provider may want a program to cover several residents. Those pressures should not erase participant choice or make support-provider selection look like a condition of housing unless there is a clearly documented and lawful basis for the requirement.

Use a boundary review before move-in and when a support program changes. Confirm who introduced the support provider, whether alternatives were discussed, who explained the agreement, whether consent is current, who handles complaints, and whether the participant can change support providers without losing clear access to housing communications.

This also helps manage conflicts of interest. If the SDA provider, SIL provider, property manager, referral partner or owner has a related-party interest, record the disclosure and the control. The practical test is simple: a reviewer should be able to see who provides the home, who provides the supports, who claims which funding, and who the participant can contact if something is not working.

Because a participant can leave a Program of Supports with up to two weeks' notice, do not treat a six-month program period as a six-month occupancy guarantee. A support arrangement may end while the participant remains in the SDA dwelling, or a support breakdown may become an early signal that a resident transfer, housemate review or vacancy process is needed.

Add triggers that notify the right teams. Vacancy teams need to know if household support coverage changes before accepting another resident. Finance needs to know if an SDA claim remains ready or if my provider, agreement or occupancy evidence needs review. Owner-reporting teams need to avoid describing a support program as guaranteed rental or SDA income.

For support-provider invoices, keep the claim pathway separate. NDIA guidance for my providers says claims for SDA, home and living supports and behaviour supports can be automatically rejected if the provider is not recorded for those supports on the participant's plan. That is a support and provider-relationship control; it should not be discovered only after a payment rejection.

NDIS record-keeping guidance says providers need complete and accurate records for NDIS supports delivered, and lists examples such as invoices, support logs, rosters, case notes and service agreements. An SDA provider may need to know that a linked support record exists, but that does not mean every support log or case note belongs in the SDA operating file.

Use a minimum necessary evidence approach. Store the existence, status, date, owner and operational implication of a Program of Support. Link to detailed support-provider evidence only where consent, role and business need allow it. Keep participant-identifying support details out of owner reports unless an existing permission and clear need authorise disclosure.

The best record is one that lets a manager act without exposing more information than required: support program active until a date, two-week notice received, support provider registration pending, household coverage review needed, or no owner-facing income change confirmed.

StepFree SDA can help providers keep the shared accommodation record connected without flattening the boundaries. The same operating view can show the enrolled dwelling, resident status, SDA agreement, my provider state, support-provider summary, vacancy implications, claim readiness and owner-safe reporting status.

That is the practical goal. Programs of Support may make support delivery more flexible for participants, but SDA providers still need disciplined records that separate housing, support, claims, privacy and owner communication.