SIL Practice Standards: An SDA handover checklist for shared homes
Supported Independent Living providers must now work with new SIL Practice Standards that apply from 1 July 2026, alongside mandatory registration and the new 0138 registration group pathway. The standards are aimed at SIL providers, but SDA providers cannot ignore them when the same home, resident, support team, service agreement, tenancy record and owner-reporting workflow are connected. The practical issue is not whether SDA has become SIL. It has not. The issue is whether an SDA provider can show where housing responsibilities end, where support responsibilities begin, and how participant rights are protected when shared-home operations change.
Treat SIL standards as a handover trigger
The NDIS Commission says the SIL Practice Standards cover supported decision-making, safeguarding, practice governance, and agreements about tenancy, housing and support arrangements. Those themes land directly beside common SDA records: service agreements, tenancy notices, maintenance, housemate matching, incident handoffs, support-provider access, vacancy decisions and owner updates.
For SDA teams, the new standards should trigger a handover register rather than a vague compliance memo. A register helps the provider record which SIL provider is connected to each dwelling, what agreement evidence is current, who owns participant communication, which risks belong to the support provider, and which issues still affect the SDA claim or tenancy record.
This is especially important where one organisation delivers both SDA and SIL, or where a related SIL provider is promoted during vacancy intake. The record should make separation visible to participants, staff, auditors and owners without forcing sensitive support notes into property reporting.
Separate tenancy from support agreements
NDIS guidance for SIL providers says a tenancy agreement may be needed where the provider also has a housing arrangement, and that the agreement helps clarify tenancy rights and how housing differs from SIL supports. The SIL Practice Standards also expect separate tenancy and service agreements where the same provider delivers SIL and tenancy to the same participant.
SDA providers already have their own service-agreement obligations. NDIS participant guidance says SDA is the housing itself, does not include in-home support such as SIL, and requires a written service agreement for SDA supports. The NDIS Commission SDA supplementary module also expects participants to understand the distinction between SDA and other supports, with separate service agreements where the same provider delivers both.
That means shared-home onboarding should not rely on one mixed document or one welcome email. A clean record separates the SDA service agreement, tenancy or occupancy documents, RRC and living-cost arrangements, SIL service agreement, roster or support model evidence, support-provider access terms, complaint pathways and emergency handoffs.
Build the SDA and SIL handover checklist
Use this checklist for existing shared homes, new resident intake, support-provider changes, SIL registration transitions, housemate matching, serious incidents, complaints, vacancy advertising, plan changes and owner statements.
Map the provider roles
Record the SDA provider, SIL provider, related entities, support coordinator, plan manager, behaviour support practitioner and owner-facing contact for each dwelling. Make the role boundary readable without opening private support notes.
Lock agreement evidence
Attach the current SDA service agreement, tenancy or occupancy record, RRC basis, SIL service agreement status, support-provider access agreement and any participant-readable explanation of how housing and support arrangements differ.
Track participant choice
Show how the participant, nominee or decision supporter was given accessible information about who they live with, who supports them, how concerns are raised, and whether changing a support provider affects their housing position.
Create safeguarding handoff states
Use structured states for complaint raised, incident handoff required, behaviour support boundary, co-tenant conflict, repair risk, emergency-plan dependency, privacy review and support-provider action overdue.
Protect claim and vacancy decisions
Keep SDA claim readiness, vacancy payment evidence, RRC records and owner income assumptions separate from SIL roster, support-delivery, 0138 registration or plan-manager issues unless there is a documented operational dependency.
Filter owner reporting
Report owner-safe states such as support-provider transition, move-in dependency, vacancy risk, claim not yet confirmed or site issue under review without exposing participant identity, support plans, incident narratives or private complaints.
Connect safeguarding to the dwelling record
The SIL standards put emphasis on safe, respectful and supportive home environments, including managing risks such as bullying, conflict and harm in the home. The SDA supplementary module also expects documented arrangements with participants and other providers who deliver SIL in an SDA dwelling, including how shared living is working, how conflicts are managed and how concerns about the dwelling are communicated.
The SDA provider does not need to duplicate the SIL provider's daily support file. It does need enough connected evidence to manage the home. A complaint about support staff access may affect privacy and keys. A co-tenant conflict may affect housemate matching, repairs, vacancy decisions or tenancy notices. A behaviour-support issue may affect modifications or whether the dwelling still fits the participant's needs.
Useful fields include incident owner, support-provider notified, SDA action required, tenancy advice required, repair action open, participant communication completed, regulator notification considered by relevant provider, claim hold required, owner update restricted and next review date.
Keep registration changes out of owner promises
Current NDIS and Commission guidance says some SIL providers must register from 1 July 2026, existing unregistered SIL providers must apply by 1 October 2026 if they want to continue, and SIL providers must comply with the new SIL Practice Standards. That can create move-in and continuity questions for SDA providers, but it should not become an unsupported promise to owners or investors.
Owner reporting should distinguish confirmed property income from support-provider transition risk. A SIL provider's registration pathway, audit status or support model may affect timing, but it is not SDA rent, RRC or paid SDA claim income. Keep those states separate so finance does not forecast income from assumptions about support delivery.
The same control protects participants. A provider should not imply that a participant must accept a particular SIL provider to keep their SDA tenancy, and owner updates should never include private support choices, complaints, nominee discussions or plan details.
How StepFree fits the workflow
StepFree SDA can help providers keep the SDA/SIL handover attached to the live operating record: properties, dwellings, participants, service agreements, tenancies, claims, RRC ledgers, vacancies, incidents, complaints, partner statuses and owner-safe reporting.
The value is a shared operational state. Tenancy staff can see what affects the home, finance can see what affects claims, compliance can see the evidence boundary, and owner-reporting users can see only the status that is safe to share.
Conclusion
The new SIL Practice Standards should push SDA providers toward clearer shared-home records. Keep tenancy and support agreements separate, make participant choice visible, connect safeguarding signals to the dwelling record, keep claims and vacancies distinct from SIL support issues, and filter owner updates carefully. That gives SDA teams a stronger operating position when support-provider arrangements change inside homes they manage.
StepFree SDA can help providers manage SDA/SIL handovers, participant records, claims, vacancies, RRC ledgers, compliance actions and owner-safe reporting from one controlled SDA operations workflow.