SDA conflict of interest: A provider register checklist
Conflict of interest is becoming a sharper operating issue for SDA providers because accommodation decisions rarely happen in isolation. A vacancy can involve a participant, nominee, support coordinator, SIL provider, plan manager, owner, builder, related entity and internal intake team. The current NDIS conflict of interest guidance says conflicts can be actual, potential or perceived, and the NDIS Commission's SDA Practice Standards expect perceived or actual conflicts to be proactively managed and documented. For SDA teams, that means the control cannot be a generic policy file. It needs to be a live register that shows how participant choice was protected at the point where housing, daily supports, referrals, claims and commercial interests met.
Why a register is stronger than a policy
The NDIS conflict of interest page says conflicts can limit participant choice and control, create participant safety risks, create business risk and affect NDIS sustainability and integrity. It also says providers should avoid real or perceived conflicts, declare and manage unavoidable conflicts, keep accurate records and provide alternative options where appropriate.
The SDA supplementary module makes this specific to housing. Its conflict of interest outcome is that a participant's right to choose other NDIS supports is not limited by their choice of SDA dwelling. It expects providers to have participant-accessible policies, document perceived or actual conflicts, explain the distinction between SDA and other supports, use separate service agreements where the same provider delivers SDA and other supports, and uphold housing rights regardless of decisions about other supports in the dwelling.
A register turns those obligations into daily operating evidence. It gives intake, tenancy, compliance, finance and owner-reporting teams one place to see what interest exists, who was told, what alternatives were provided, what agreement boundaries apply, when the issue will be reviewed and what must not be reported outside the participant-safe context.
Map the conflict pathways before intake
Conflicts often appear before a participant signs an SDA agreement. They can arise when a related SIL provider is preferred, a support coordinator refers to a connected vacancy, a plan manager pays a related entity, an owner expects a particular tenant source, a staff member works across multiple businesses, or a regional market has very few alternatives.
The NDIS home and living conflict resource gives SDA-specific examples, including a participant feeling pressured by an SDA provider to choose a particular in-home support provider or service, and a provider delivering SDA while also delivering other NDIS-funded supports such as support coordination or plan management.
For providers, the practical step is to map relationships before vacancy discussions become commitments. A conflict identified early can often be declared, explained and managed. A conflict found after a participant feels pressured can become a complaint, a delayed move-in, a tenancy dispute, an audit finding or an owner-reporting problem.
Record the referral source
Capture who introduced the participant, whether that person or organisation has a commercial or employment link to the SDA provider, and whether the participant was shown alternative SDA or support options.
Link related providers
List connected SIL, support coordination, plan management, allied health, behaviour support, property management, maintenance, owner or brokerage entities beside each dwelling and participant pathway.
Flag pressure risks
Use exception labels for preferred-provider wording, bundled service language, time-pressure sales, unclear alternatives, nominee involvement, participant complaint risk and regional scarcity.
Assign an independent reviewer
Where the same organisation benefits from more than one support, route the record to a manager or compliance lead who is not financially responsible for filling the vacancy.
Separate SDA from SIL and other supports
The NDIS Commission's supported accommodation work says the interaction of SIL and SDA arrangements affects the ability of people in supported accommodation to make changes to their living arrangements. It has also consulted on legal and practical separation of SIL and SDA, while SIL registration changes continue to sharpen attention on shared-home boundaries.
That reform context does not mean every SDA provider must immediately redesign its structure. It does mean the operating file should make the boundary obvious. The participant should be able to understand the SDA agreement, any SIL or other support agreement, the right to choose supports, the complaint pathway and what happens if they want to change a support provider while staying in the home.
The Disability Royal Commission progress reporting also records a recommendation to review mechanisms for transitioning away from the same provider delivering SIL and SDA, with interim arrangements to strengthen oversight and monitor conflicts of interest. Providers do not need to turn that into unsupported legal claims. They should treat it as a clear signal that conflict records in supported accommodation will keep mattering.
Build the register fields
A useful SDA conflict register should be structured enough to run weekly, not so legalistic that staff avoid using it. Start with fields that show the conflict type, participant communication, agreement boundary, mitigation owner and review date.
Keep participant-facing and owner-facing records separate. A conflict register may contain private information about support choices, family concerns, complaints, nominee discussions or provider relationships. Owner reporting should explain property-level risk without exposing participant identity or support decision details.
Classify the conflict
Use actual, potential or perceived as the primary state. Add a practical category such as related SIL provider, support coordinator referral, plan manager link, owner interest, staff relationship, nominee role or scarce-market dependency.
Document the disclosure
Record when the participant or decision supporter was told, the format used, whether accessible communication was required, and where a copy of the disclosure is stored.
Show alternatives
List alternative providers, dwellings, support pathways or decision supports offered. If alternatives are limited, record the reason and the steps taken to reduce pressure on the participant.
Separate agreements
Confirm the SDA service or tenancy agreement is distinct from SIL, support coordination, plan management or other NDIS support agreements where the same organisation or related organisation is involved.
Set review dates
Review the conflict when a participant moves in, changes support provider, changes funding management, raises a complaint, changes nominee arrangements, receives a plan reassessment or exits the dwelling.
Record exit protections
Show how housing rights, security of tenure, complaint escalation and support-provider change pathways are protected if the participant declines or later exits a related support arrangement.
Connect controls to claims and owner reporting
Conflict records are not pricing records, but they affect claim readiness. If the participant has not clearly accepted the SDA arrangement, if the agreement boundaries are unclear, or if a bundled support arrangement is being challenged, finance should know that the move-in or claim-start state is under review.
Where the same organisation delivers multiple supports, keep SDA claims separate from SIL invoices, plan management payments, support coordination records and participant-side support notes. The NDIS Code of Conduct expects integrity, honesty and transparency, and the NDIS provider responsibilities page points to fair dealing, accurate information and registration obligations for SDA.
Owner reporting needs an even tighter privacy filter. Owners may need to know that a vacancy is awaiting participant choice confirmation, that a support-provider dependency is under review, or that move-in timing is delayed. They do not need participant names, plan details, complaint specifics, family communications or private support-provider preferences.
How StepFree fits the workflow
StepFree SDA can help providers treat conflict management as part of the operating record rather than a separate compliance spreadsheet. The useful pattern is a connected view of dwellings, participants, referrals, SIL partner status, agreements, claim-readiness states, RRC records, exceptions and owner-safe updates.
That does not replace the NDIS Commission, NDIA guidance, legal advice, tenancy advice or participant decision support. It gives provider teams a cleaner audit trail when a vacancy, referral or support-provider relationship needs to be checked before a claim, move-in or owner report is treated as settled.
Conclusion
SDA conflict of interest control works best when it is visible before pressure appears. Providers should map related entities, declare and document actual, potential and perceived conflicts, keep SDA and other supports separated, show participant alternatives, review the record at key changes and protect owner reporting from private support information. A live register gives teams evidence that participant choice was not traded for vacancy speed, claim convenience or a related-provider arrangement.
StepFree SDA can help providers manage conflict registers, SDA/SIL partner boundaries, claim-readiness exceptions and privacy-safe owner reporting in one SDA operations workflow.