NDIS service agreements: what to keep on file

An NDIS service agreement records what you and a participant agreed: who they are, which supports you will deliver and how often, the dates, the price, how either side can change or end it, how to complain, and what they consented to. Keeping it signed, dated and on file is what gets tested.

In short

• A service agreement records the participant, the supports and their frequency, the dates, the price, the notice terms, the complaints path and consent.
• Service agreements are a standard in the NDIS Practice Standards, in the Core module under provision of supports, as at November 2026.
• Record keeping is a separate standard. How you store and retrieve the agreement is assessed as well as what it says.
• A service agreement is not a service booking. One is an agreement with the participant, the other is a funding arrangement.
• Supported independent living and specialist disability accommodation carry extra agreement standards, so one template will not cover every support.

What an NDIS service agreement includes

An NDIS service agreement includes seven parts: the parties, the supports, the dates, the price, the notice terms, the complaints path and the consent given. Work through these and you have the substance of a complete one.

Who it is between. The participant's name and NDIS number, and your organisation's legal name and ABN. If somebody signs on the participant's behalf, record who they are, the authority they act under, and the date. A signature with no named signer and no date is the most common gap of all.

What you will deliver. The supports described the way the participant would describe them, not the way a price guide describes them. "Two hours of support with cooking and shopping on Tuesday mornings" is useful. A line item code on its own is not. Say how often, for how long, and where.

When it runs. A start date and an end date, or a clear statement that it continues until either side ends it. Tie the dates to the participant's plan where you can, because a plan that ends mid-agreement is where confusion starts.

What it costs and who pays. The price for each support, whether travel or cancellation charges apply, and how invoices are paid: agency managed, plan managed or self managed.

How it changes and how it ends. Notice periods for both sides, who to tell, and what happens to supports already booked.

How to complain. Where the participant goes inside your organisation, that they can go to the NDIS Quality and Safeguards Commission as well, and that complaining will not cost them their supports.

What they consented to. Participant consent is the thinnest part of most files. Record what the participant agreed to, such as sharing information with a plan manager, a support coordinator or a family member, and record what they declined.

Where the rule comes from

The rule comes from the NDIS Practice Standards, which sit in the schedules of the NDIS (Provider Registration and Practice Standards) Rules 2018, not from a service agreement template published by the agency. In Schedule 1, the Core module, Part 4 covers provision of supports and lists service agreements as a standard beside access to supports, support planning, responsive support provision and transitions to and from a provider, as at November 2026.

Two things follow. Your agreement is read as part of a set, so an auditor looking at it will also ask how the support was planned and what happened when the participant moved to or from another provider. And the standard describes an outcome rather than a form, which is why two well run providers can have agreements that look nothing alike and both hold up. Read the clause before you rewrite your template. It is shorter than guessing at it.

Record keeping is a standard of its own

Record keeping is a standard of its own: how you store and retrieve a service agreement is assessed separately from what the agreement says. In the same Core module, Part 3 covers provider governance and operational management, and information management is one of its standards, as at November 2026. A sound agreement that nobody can find is still a gap.

In practice: one file per participant, the current agreement on top, superseded versions kept underneath rather than thrown out, and consent recorded with its date. If the file lives in two places, decide which one is the real one and write that down. The question is rarely "do you have it". It is "show me", and the clock runs while you look.

Agreements are one of several record sets opened together. Our notes on what to have on file before an NDIS audit and on worker screening records cover the neighbouring piles.

A service agreement is not a service booking

A service agreement is not a service booking: the agreement is between you and the participant, and the booking sets aside part of that participant's plan budget for your supports in the agency's systems. They describe the same work from two sides and they are not interchangeable.

The risk is a mismatch. A booking can cover an amount and a period that no longer match the agreement, usually because the supports changed and only one record was updated. When you check your files, check the pair. If you want to see plan budgets and utilisation across a whole caseload rather than one participant at a time, our NDIS page sets out that view.

Changing, reviewing and ending an agreement

A service agreement can be changed after both sides have signed it, provided both sides agree and the change is recorded. The method matters less than the record: a variation page, a reissued agreement, or a dated note signed by both sides all work, as long as the file shows what changed, when, and that the participant agreed.

Put a service agreement review on a schedule rather than waiting for a problem. The obvious trigger is the participant's plan reassessment, because budgets and goals can both move. Others worth writing into your own process: the supports change in kind or frequency, the price guide changes, the participant's circumstances change, or the person signing on their behalf changes. When an agreement ends, record the end date and the reason in neutral terms, and record what you did to support the move to or from another provider.

Plain language is part of the standard

Plain language is part of the standard: a service agreement has to be written so the participant can read it and understand what they agreed to. The point of the standard is informed agreement, and a reader who cannot follow the document has not given it. Short sentences, headings, and a plain word beside every short form.

Where a participant needs the agreement in another format, record what you provided: an Easy Read version, a translation, an interpreter at the conversation, or a support person who went through it with them. That note is the evidence the agreement was understood, not just signed.

How to check your own files this week

You can check your own service agreement files in an hour. Pull five participant files at random and score each against the seven parts above, then answer three questions for each one: is the current agreement there, is it signed and dated by both sides, and does it match the supports you are actually delivering and billing.

If more than one of the five fails, the cause is rarely that staff do not care. It is usually a template missing a field, or nobody owning the review date. Both are fixable in an afternoon, and both are cheaper to fix now than to explain later.

Common questions

Does an NDIS provider need a written service agreement with every participant?

Service agreements are a standard in the NDIS Practice Standards, so a registered provider is assessed on them for the supports it delivers, as at November 2026. Some supports carry stricter agreement standards: specialist disability accommodation and supported independent living each have their own in the Rules. Treat a written, signed agreement as the normal case, and read the clause that applies to your supports.

What happens if a provider has no signed service agreement on file?

A missing agreement shows up as a gap against the service agreements standard at audit. It also weakens everything that depends on it: what was agreed, at what price, and with whose consent. A billing dispute becomes very hard to resolve.

How long must an NDIS provider keep a service agreement after it ends?

The service agreements standard does not set a single retention period. The answer comes from your information management practice, your conditions of registration, and other laws such as tax and employment record rules. Check the current requirement with the NDIS Quality and Safeguards Commission and write the period into your own records policy.

Can a service agreement be changed once both sides have signed it?

Yes, when both sides agree and the change is recorded. Keep the superseded version in the file beside the new one, with the date of the change, so the history reads in order.

What is the difference between a service agreement and a service booking?

A service agreement is between the provider and the participant and sets out the supports, the price and the terms. A service booking reserves part of the participant's plan budget for those supports in the agency's systems. Both need to say the same thing.

Sources

• National Disability Insurance Scheme (Provider Registration and Practice Standards) Rules 2018, Federal Register of Legislation, compilation F2026C00527 in force 1 July 2026, as at November 2026. Schedule 1 Core module, Part 4, clause 20 Service agreements; Part 3, clause 12 Information management; Schedule 7 Module 5, clause 5 Service agreements with participants; Schedule 7A Module 5A, clause 6 Agreements about tenancy, housing and support arrangements.