SDA service agreements: A claim and record-keeping checklist for providers
SDA service agreements can look like a participant-facing admin step, but for providers they are a claim, compliance and operating control. The current NDIS guidance says written service agreements are mandatory for specialist disability accommodation supports. Providers should therefore treat each agreement as part of the live SDA operating record, connected to the participant, dwelling, funding management pathway, rent contribution, claim evidence and review rhythm.
What the current guidance says
The NDIS service agreement guidance says a service agreement records what the participant and provider have agreed about NDIS supports, including how supports will be delivered, what they cost, how the provider will be paid and how changes are managed.
The same guidance says written service agreements are only mandatory for specialist disability accommodation supports. The NDIS SDA participant guidance also says the participant and provider must create a written service agreement when the participant has SDA supports.
For SDA providers, this matters because record keeping and claiming sit beside the agreement. The NDIS record keeping guidance says providers need complete and accurate records of supports delivered, including service agreements, and that claims for payment must be complete, truthful and accurate.
Why agreements become an operational risk
The risk is not usually that a provider has no template. The risk is that the signed agreement is not connected to the daily operating record. A participant may move in, funding management may change, a my provider relationship may be pending, rent contribution details may sit in a separate tenancy file, and finance may still be asked to claim based on incomplete evidence.
SDA teams should avoid treating the agreement as a static PDF. It should be a controlled status in the participant and dwelling workflow, with enough metadata for operations, finance, compliance and owner-facing teams to understand what has been agreed and what still blocks claim readiness.
A practical SDA service agreement checklist
Use the agreement as a workflow gate before move-in, claim submission and owner reporting. The useful question is whether another team member could review the record and understand the current claim position without asking for the history in Slack, email or a spreadsheet note.
Record the participant and dwelling link
Attach the signed agreement to the participant and enrolled dwelling, then capture the agreement start date, review date, exit or notice terms, approved SDA category details and any relevant support coordination or nominee contact details.
Separate SDA funding from rent contribution
The NDIS SDA guidance says the participant pays a reasonable rent contribution and that this detail should be included in the service agreement. Track the agreed amount separately from SDA claim pricing so finance does not mix participant rent, owner reporting and NDIA payment assumptions.
Check funding management before claiming
The NDIS payment guidance separates self-managed, plan-managed and NDIA-managed payment pathways. For NDIA-managed funding, confirm the provider is recorded as a my provider where required before submitting the payment request.
Keep price and payment terms traceable
Record the support item, agreed price basis, effective dates, invoice pathway, claim owner and source version of the relevant SDA pricing arrangements. Do not rely on an old agreement if the participant's plan, dwelling status or pricing assumptions have changed.
Make review triggers explicit
Create review triggers for new plans, move-in or exit changes, funding-management changes, my provider relationship updates, dwelling enrolment changes, rent contribution changes and any dispute or complaint that affects the agreed supports.
Controls for claim assurance and reviews
The NDIS guide to getting paid says providers need information such as participant details, support dates, support item reference number and support item price when making payment requests. It also notes that claims may be reviewed before or after payment and that providers may need to supply information to verify a claim.
That makes agreement discipline practical rather than theoretical. If a claim is queried, the team should be able to show the signed SDA agreement, relevant dates, pricing basis, invoice or claim record, participant relationship status and any notes explaining a change. If those records live in different places, the review response becomes slower and less reliable.
How StepFree fits the workflow
StepFree SDA should help providers connect service agreements to the rest of the SDA operating record. The agreement should sit beside participant status, dwelling enrolment, my provider status, claim readiness, rent contribution tracking, exceptions, owner reporting and evidence history.
Providers using spreadsheets can still apply the same discipline: one agreement register, one source of truth for review dates, one claim-readiness checklist and one place to record changes. The key is to stop agreement details from drifting away from the claim and reporting workflow.
Conclusion
Written SDA service agreements are a mandatory participant relationship control and a practical claim evidence control. Providers reduce payment delays, record gaps and owner-reporting confusion when each agreement is connected to funding management, rent contribution, pricing, review triggers and the live SDA operating record.
StepFree SDA can help providers connect service agreements, participant records, claim readiness, rent contribution tracking, exceptions and owner reporting in one controlled SDA operating workflow.