Unregistered NDIS providers and SDA: A boundary checklist

The first control is to keep the SDA provider role clean. The Commission's registration guidance says providers must be registered to provide SDA, specialist behaviour support services, supports or services to NDIA-managed participants, plan management services, SIL and NDIS digital platform services. It also says unregistered providers can deliver supports and services except for listed activities, and only self-managed or plan-managed participants can choose to use unregistered providers.

That means an SDA provider should not describe an unregistered support provider as part of the SDA service unless the arrangement is legally and operationally clear. If a participant separately chooses an unregistered worker or business, the SDA record should show the boundary: who engaged them, what support they deliver, how they enter the home, who receives invoices, who responds to concerns, and whether any agreement, consent or house rule affects other residents.

A useful test is simple: can the team explain which organisation is the registered SDA provider, which supports are being delivered by others, whether any of those supports require registration, and what the SDA provider will do if a concern affects safety, access, privacy or claim evidence?

Start with the participant and dwelling, then map the organisations and workers who may influence the home. Do not rely on a referral note or a support coordinator email as the whole record. The register should distinguish independent participant choices from brokerage, subcontracting, related-party services and preferred-provider arrangements.

Use this checklist for shared homes, apartment models, vacancies, move-ins, behaviour support concerns, support-provider changes, participant complaints, owner pressure, referral handovers and any situation where a non-SDA provider's conduct could affect the home environment.

The NDIS Commission's 4 September notice says the Code of Conduct applies to businesses that claim funds from an NDIS plan to deliver supports or services, whether or not they choose to register. The Commission's Code page also says the Code must be followed by registered providers, unregistered providers, key personnel and workers.

For SDA providers, that creates a common language for interface concerns: respect for rights and self-determination, privacy, safe and competent service delivery, integrity, prompt action on concerns, prevention and response to violence, exploitation, neglect and abuse, prevention and response to sexual misconduct, and fair pricing. The SDA provider does not become the regulator of every independent provider in a participant's life, but it should not ignore a Code concern that affects the home, other residents, service continuity or participant safety.

Turn the Code into operating prompts. If a worker pressures a participant to use a related service, record the participant-choice issue. If a provider discusses plan details in a shared area, record the privacy issue. If a support provider repeatedly misses attendance and that affects safe use of the dwelling, record the safety and continuity issue. If an invoice or price looks unfair, record the concern and the referral path rather than hiding it in a vacancy note.

The risk is sharper in shared SDA homes. One participant may choose an unregistered provider for plan-managed or self-managed supports, but that person's attendance can affect housemates, common areas, privacy, visitors, behavioural triggers, fire safety, infection control, maintenance access or overnight routines. The SDA provider needs to respect participant choice while protecting the dwelling and other residents.

Use house-level controls that do not turn into support control. Record agreed visitor and worker access routes, shared-area expectations, emergency instructions, privacy rules, communication preferences, resident-impact review points and who to contact if access becomes unsafe. Keep these separate from support plans that belong to another provider unless the participant has given appropriate consent to share.

Do not treat every support-provider concern as a tenancy breach. A missed support shift, unpaid third-party invoice or disagreement with an independent provider may affect the home, but it should be triaged under the right pathway: participant support, complaint, incident, access review, service agreement discussion, claim hold or tenancy risk.

The Commission's participant pack says people can raise concerns about safety or quality with a provider or the NDIS Commission, and that complaints can cover whether an NDIS support or service meets safety and quality standards. It also points participants to the NDIA for funding and plan-management issues. SDA teams should build that split into their own triage so residents are not bounced between teams.

If the issue relates to the SDA provider's own service, treat it under the SDA provider's complaint or incident process. If it relates to another NDIS provider, help the participant understand the available complaint pathway without taking over their decision. If the issue affects immediate safety in the dwelling, act on the safety risk first and record what was done.

Incident management guidance says incidents in NDIS supports and services need to be identified, assessed, recorded, managed and resolved while making the person feel safe, respected and informed. Registered providers must have incident management systems and report certain incidents. Where another provider is involved, record the handoff, consent limits, known facts, immediate safeguards and whether the SDA provider has its own reportable-incident question to assess.

NDIS provider responsibility guidance says providers need to keep full and accurate records, give invoices after delivering a support, request payment only after the support is delivered and take reasonable steps to avoid and manage conflicts of interest. Record-keeping guidance says invoices and support records need minimum identifying information, and for SDA invoices that includes the participant address and postcode, support item number, claim type, total invoice amount and GST component if applicable.

Do not let an unregistered-provider issue distort SDA claim evidence. The SDA claim still needs the enrolled dwelling, participant, plan dates, service agreement, support item, price basis, occupancy or vacancy evidence, my provider status where relevant, and payment outcome. A dispute with an independent provider may explain an operational delay, but it should not become a reason to backdate claims, reshape RRC records, suppress a complaint or promise owners that income is certain.

Owner reporting should be narrow and factual. The owner may need to know that access is being reviewed, a move-in is paused, a complaint is open, a shared-home issue affects vacancy timing, or a claim is held pending verified evidence. They do not need the participant's support-provider file, complaint details, health information, plan documents, NDIS number or private correspondence.

StepFree SDA can help providers connect participant records, dwelling access notes, provider-interface registers, complaints, incident triage, service agreements, claim states, RRC records and owner-safe reporting in one SDA-specific workflow.

That structure matters because unregistered-provider interface risk rarely belongs to one team. Intake sees participant choice, operations sees home access, compliance sees Code and incident concerns, finance sees claim impacts, and owners see vacancy or income movement. A shared record helps each team act from verified facts without exposing sensitive participant or third-party information to the wrong audience.