Back to blog
Compliance7 min read

NDIS Commission regulatory priorities: An SDA action-register checklist

The NDIS Commission's 2026-27 regulatory priorities are not a new SDA rulebook, but they are a useful signal for provider governance. The priorities focus on unregistered providers implementing regulated restrictive practices, exploitative or misleading behaviour that puts participants at risk, and governance failures in high-risk settings. For SDA providers, the practical response is not another policy folder. It is a live action register that connects participant rights, SIL boundaries, incidents, complaints, behaviour support handoffs, service agreements, owner reporting and claim controls to named owners and evidence.

Translate priorities into operating controls

SDA providers already have SDA-specific Practice Standards covering rights and responsibilities, conflicts of interest, service agreements, enrolment of SDA properties and tenancy management. The 2026-27 priorities should sit above those obligations as a risk lens: where could the provider's records fail to show participant choice, safe governance, truthful communication or clear escalation?

That matters because supported accommodation risk is rarely isolated to one team. A behaviour support issue may appear first as property damage. A complaint may sit with a support provider while the SDA provider keeps claiming. A vacancy discussion may pressure staff to overstate demand to an owner. A marketing statement may imply certainty that the NDIS does not provide.

Use a register that names the priority area, linked dwelling or participant where relevant, accountable manager, evidence source, next action, due date, escalation path and closure standard. Avoid broad status labels such as compliant or under review unless the underlying evidence is visible.

Watch restrictive-practice boundaries at the dwelling level

The Commission has called out providers implementing regulated restrictive practices without being registered to do so. Many SDA providers do not deliver daily supports, but they still operate the dwelling where behaviour support, support-provider rosters, environmental changes, tenancy notices and emergency responses can intersect.

The action register should separate what the SDA provider controls from what the SIL or support provider controls. Useful fields include behaviour support practitioner, implementing provider, restrictive-practice status, consent and authorisation source where applicable, dwelling feature affected, incident link, participant communication state and review date.

Do not let housing records obscure practice responsibility. If a door lock, alarm, access control, furniture arrangement or room-use rule has a safeguarding implication, record who requested it, why it is being considered, which provider is responsible for behaviour support advice, and whether the SDA provider's role is maintenance, tenancy management or escalation only.

Control misleading conduct in marketing and owner updates

The regulatory priorities also identify exploitative, coercive, dishonest or misleading behaviour as an integrity risk. SDA providers should read that alongside official SDA investment guidance, which warns against guaranteed occupancy, guaranteed returns, government-backed income claims and advertising dwellings as enrolled SDA before NDIA enrolment approval.

For operations teams, this is not only a marketing issue. The same risk can appear in investor packs, vacancy listings, referral emails, owner reports, pipeline dashboards and staff conversations with support coordinators. A provider should be able to show which statements are verified, which are assumptions, and which must not be used.

Good control language is specific: enrolled dwelling, design-stage dwelling, vacancy notified, resident matched pending plan evidence, claim hold pending my provider, RRC receipt pending, owner forecast held pending evidence, or unsupported return claim removed. Bad control language implies certainty where the participant, plan, enrolment or claim evidence is not settled.

Treat SIL reform as an SDA dependency

Mandatory registration for SIL and NDIS digital platform providers started from 1 July 2026, with transition pathways applying. The Commission's reform hub also says new SIL Practice Standards apply from 1 July 2026 and that reform is strengthening requirements around registration, events and ownership changes.

Even where SDA registration requirements have not changed, an SDA provider's risk position can change when the support provider changes status, changes ownership, loses staff capability, fails incident reporting, or cannot meet the participant's support needs in the dwelling.

Maintain a support-provider dependency register by dwelling. Track SIL provider status, registration or transition evidence, contact owner, service boundary, incident and complaint handoff, emergency handoff, behaviour support handoff, vacancy coordination process and unresolved risks. If the same organisation provides SDA and SIL, the register should still show separate agreements, responsibilities and conflict controls.

Build the 2026-27 action register

Use this checklist for board reporting, compliance meetings, audit preparation or monthly SDA operations reviews. It should be practical enough for managers to update, but structured enough to survive a later complaint, incident review or audit sample.

Map priority to workflow

Classify each item as restrictive-practice boundary, misleading conduct risk, governance failure, SIL dependency, incident trend, complaint trend, owner-reporting risk, claim-control risk or participant-rights risk.

Assign a named owner

Give every item a responsible person and escalation path. A shared compliance inbox is not enough when the issue affects participant safety, claim decisions or owner communication.

Link evidence at source

Connect the item to the dwelling, participant where appropriate, service agreement, incident record, complaint record, support-provider handoff, owner report, marketing asset or claim exception.

Set a decision state

Use states such as evidence requested, support-provider response due, participant communication pending, owner update held, claim hold applied, correction completed, escalated to executive or closed with evidence.

Review patterns monthly

Do not only close individual items. Review repeat issues by dwelling, support provider, worker group, referral source, owner, claim type and participant feedback theme.

Keep owner and investor views private

Owner reports can show confirmed operating states and commercial risk without revealing behaviour support details, complaints, incident specifics, health information or participant identity beyond approved permissions.

Connect incidents and complaints to governance

The Commission's incident guidance says incidents in NDIS supports and services need to be identified, assessed, recorded, managed and resolved. Reportable incident guidance also sets notification timeframes for serious categories of harm for registered providers. SDA teams should not wait for a separate support provider to decide whether a housing record matters.

If an incident, complaint or near miss touches the dwelling, tenancy management, access, repairs, support-provider boundary, vacancy decision, participant communication or owner reporting, it needs a visible SDA action. That action may be escalation, evidence preservation, service-agreement review, property repair, claim hold, owner-safe status update or participant communication.

This is especially important in shared living. The Commission's supported accommodation work has identified the interaction of SIL and SDA arrangements as a factor that can affect people's ability to make changes to their living arrangements. A good SDA register therefore shows where the housing provider has acted, where another provider owns the response, and where participant choice or safety remains unresolved.

How StepFree fits the workflow

StepFree SDA can help providers turn regulatory priorities into operating records rather than disconnected spreadsheets. The same workspace can link dwellings, participants, service agreements, support-provider dependencies, incidents, complaints, claim holds, RRC ledgers, vacancy states and owner-safe reporting.

That connected view matters because a governance priority is only useful if it changes day-to-day decisions. StepFree gives SDA teams a controlled way to see what is known, what is blocked, which claims should pause, which owner updates must stay factual, and which evidence is ready for a compliance or audit review.

Conclusion

The NDIS Commission's 2026-27 priorities are a prompt to tighten the operating record around SDA risk. Providers should be able to show clear boundaries for restrictive practices, truthful marketing and owner communication, active SIL dependency controls, visible incident and complaint actions, and evidence-backed claim decisions. The strongest register is not the longest one. It is the one that shows who owns the risk, what evidence exists, what is blocked and what changed because the issue was identified.

StepFree SDA can help providers manage regulatory-priority actions, support-provider dependencies, incidents, claims, RRC records and owner-safe reporting in one SDA operations workflow.