ILO and SDA: A provider boundary checklist for referrals

NDIS participant guidance says ILO is a package of supports that can include host or housemate arrangements, while SDA is the only NDIS funding that provides the housing itself and does not cover in-home supports or rent. That distinction is the anchor for the operating record.

An SDA provider may receive a referral where the participant is exploring ILO, has housemate preferences, needs support to make home and living decisions, or is comparing SDA with other options. Those facts are useful, but they do not prove that the participant has SDA funding, that a particular enrolled dwelling is suitable, or that an SDA claim can start.

The safe workflow is to record ILO status as a planning and support-design signal, then keep SDA eligibility, dwelling fit, service agreement, rent contribution, my provider status and claim readiness in their own states.

ILO conversations often happen around the same practical questions as SDA referrals: where the person wants to live, whether housemates are suitable, who provides day-to-day support, what informal supports are available, and what needs monitoring once the arrangement starts.

That overlap can create pressure to treat an ILO exploration record as enough to advance an SDA vacancy. It is not. The provider still needs the enrolled dwelling details, the participant's SDA funding evidence, authority to communicate, written SDA agreement, payment pathway and any support-provider dependencies.

For shared homes, the difference is especially important. ILO may include housemate or host arrangements, while SDA shared living needs a separate tenancy, safeguards, participant-choice and claim-readiness record. Mixing the two can confuse the participant, the support coordinator, the owner and finance.

Use this checklist when a referral mentions ILO, a participant is comparing home and living options, a vacancy needs housemate-fit evidence, or an owner asks whether an ILO lead is likely to convert into SDA occupancy.

NDIS ILO provider guidance describes two stages: exploration and design, then putting the supports in place. It also says a service proposal describes the participant's needs and preferences, primary and supplementary supports, and the quoted ILO costs. That is valuable context, but it is not the same document as an SDA service agreement.

NDIS service-agreement guidance says written service agreements are mandatory for SDA supports. That gives SDA providers a clean control point. If the referral is still at ILO exploration or service proposal stage, keep it in the referral and planning lane until the SDA-specific agreement evidence is ready.

A good record should show which agreement applies to which support, who the provider is, how payment will work, how changes are handled, what communication method the participant needs, and what has actually been agreed rather than assumed.

NDIS ILO guidance says payment arrangements for primary and supplementary supports depend on the support delivered, should be discussed and agreed with the participant, and should be specified in the service proposal. It also points participants and ILO providers to independent financial advice because some payments may have tax implications.

SDA finance teams should not interpret those ILO payment details as SDA pricing, RRC, owner remittance or claim evidence. Keep the ILO support package outside the SDA ledger unless there is a specific operational dependency that needs visibility.

For plan-managed and self-managed participants, the same principle applies. The provider can track invoice and payment blockers, but each support should be coded, invoiced and evidenced through the correct pathway. Blended notes such as ILO/SDA agreed are not enough for reconciliation.

ILO discussions can still make the SDA workflow better. They often reveal what the participant values in a home, who they trust, how they communicate, what support rhythm helps them feel safe, whether housemates are acceptable, and which risks need monitoring.

Capture those signals in structured referral fields: preferred living model, housemate preference, host or shared-home interest, informal support role, support coordinator involvement, communication format, support-design blocker, monitoring need and participant concerns. Then decide which fields are relevant to SDA suitability and which belong only in the support-design record.

That discipline helps providers avoid two bad outcomes: pushing a participant into an SDA vacancy before the fit is real, or ignoring useful ILO planning evidence that could explain why a vacancy is not suitable yet.

StepFree SDA is designed to keep home and living workflows structured without turning every referral into a generic CRM note. Providers can connect participants, dwellings, vacancies, SDA agreements, claims, RRC, support-provider dependencies and owner reporting while keeping non-SDA planning signals clearly labelled.

For ILO and SDA boundaries, that means teams can track a participant's home and living pathway, service proposal state, consent, referral fit, claim readiness and owner-safe labels without suggesting that one support pathway automatically authorises another.