SDA compliance site visits: A readiness checklist for providers

A compliance visit, audit sample or information request usually lands at the point where many workflows meet: participant rights, tenancy records, repairs, complaints, incident response, support-provider boundaries, worker access, emergency planning and claims. If those records are split across inboxes, shared drives, owner spreadsheets and portal screenshots, the provider can lose time proving basic control.

Site readiness does not mean over-collecting participant information. It means keeping the right evidence linked to the dwelling and participant workflow, with clear access limits. A useful register shows the current dwelling status, enrolled design category, service agreement state, tenancy notice state, participant communication needs, known maintenance risks, support-provider handoff points and open safeguarding issues.

This is especially important where the SDA provider and SIL provider are different organisations. The SDA provider still needs evidence that housing rights, privacy, repairs, vacancies and agreed communication pathways are working, while avoiding unsupported assumptions about daily support delivery.

The SDA supplementary module covers rights and responsibilities, conflicts of interest, service agreements, enrolment of SDA properties and tenancy management. The core governance module covers risk management, quality management, information management, feedback and complaints, incident management, human resources, continuity of supports, and emergency and disaster management.

A site-ready evidence register should therefore be organised around operational controls rather than document names. For each dwelling, record which standard the evidence supports, who owns the record, when it was last reviewed, what changed, and whether any action remains open.

Good evidence is current and traceable. A signed service agreement from move-in matters, but so does the latest repair communication, the participant's accessible notice format, the complaint closure note, the SIL handoff record, the emergency-plan review and the reason a vacancy decision was accepted or deferred.

Use this checklist for existing dwellings, new properties, shared-living homes, participant transfers, support-provider changes, serious repairs, complaints, incident reviews and any situation where a regulator, auditor or executive asks whether the site is under control.

The Commission's compliance and enforcement policy describes risk-based and intelligence-led action, and lists tools that can include requiring information, warnings, compliance notices, infringement notices, changes to registration conditions, banning orders and registration cancellation. Most SDA providers will never see the most serious levers, but every provider should be able to answer a basic information request quickly and accurately.

Create response packs by site, not by team. A useful pack includes the dwelling summary, registration and enrolment evidence, service agreement state, open risk register, incident and complaint summary, maintenance summary, support-provider agreement map, vacancy history, current participant-facing communication records and privacy note for what can be shared externally.

Version the response. Record what was requested, who approved the response, what evidence was supplied, what was withheld for privacy or relevance, and what follow-up action remains. That record helps the provider stay consistent if the same issue later appears in an audit, complaint, owner query, claim review or board report.

The Commission's incident guidance says incidents should be identified, assessed, recorded, managed and resolved while keeping the person with disability safe, respected and informed. Registered providers must notify the Commission of reportable incidents within the relevant timeframes, including 24 hours for serious categories such as death, serious injury, abuse or neglect, and five business days for certain unauthorised restrictive practice events that have not caused immediate harm.

For SDA teams, the key is to connect the incident or complaint to the dwelling control it reveals. A fall may expose a maintenance or access issue. A conflict may expose housemate matching, tenancy communication or support-provider boundary problems. A complaint about delays may expose unclear repair ownership or poor participant updates.

Do not close the record just because the immediate event is resolved. Close it when the site action is also clear: no dwelling action required, repair completed, agreement updated, participant communication changed, SIL handoff revised, emergency plan updated, claim held, owner update restricted or executive review required.

Governance evidence should show that managers and the governing body can see trends across dwellings: repeat repairs, complaint themes, open incident actions, support-provider handoff failures, vacancy delays, overdue service agreements, claim holds and participant communication gaps. That is more useful than a static policy register.

Owner reporting needs a narrower view. It should explain operational status, vacancy activity, maintenance impacts, claim readiness and income timing without turning participant-sensitive compliance records into commercial reporting. Use fields such as owner-safe summary, participant-identifying details restricted, regulator matter open, claim forecast withheld or privacy review required.

This split protects the provider and the participant. It also makes the site-readiness register usable by finance, tenancy, compliance and executive teams without forcing every user into full incident or participant-history access.

StepFree SDA can help providers keep site-readiness evidence connected to the live operating record: properties, dwellings, participants, tenancies, vacancies, claims, RRC records, repairs, documents, tasks and owner reporting. The value is not just storage. It is keeping the operational state visible before a regulator, auditor, owner or finance lead asks for it.

A provider that can see open site risks, unresolved evidence, claim dependencies and privacy-safe owner messages in one place is better placed to respond calmly. The same record that supports a compliance visit can also reduce claim confusion, vacancy drift and unsupported owner promises.