Simplifying Service Agreements Without Losing Compliance

Winter, EnableUs Community

You hand a new participant your service agreement to sign, they flip through the first couple of pages, and you can just see it on their face straight away, that mix of confusion and anxiety. If you’ve seen that look before, this episode is for you.

Will, EnableUs Community

Yeah, and the tricky part is, from the provider side, you’re probably thinking, look, this thing is solid. It ticks every legal and compliance box, the auditor’s happy, the lawyer’s happy. But if the participant can’t actually understand it, it’s failing the most important test.

Winter, EnableUs Community

Exactly. In the NDIS space, we see service agreements that read like full-on legal textbooks. Long sentences, technical terminology, complex clauses that make perfect sense to you as the provider, but for someone with a cognitive disability or limited literacy, it may as well be in another language.

Will, EnableUs Community

And it’s not just a bit annoying, it’s actually a barrier to real participation. If participants are signing stuff they don’t truly understand, they’re not giving informed consent. They can’t meaningfully engage with their supports, their rights, or their choices.

Winter, EnableUs Community

Yeah. People end up signing just to get it over with. Or they avoid giving feedback, or they never use the complaints process, because all of those forms feel just as overwhelming as the agreement did.

Will, EnableUs Community

And when you think about who the NDIS serves, this becomes even more important. We’re talking about people with intellectual disability, acquired brain injury, psychosocial disability, physical disability, and plenty of folks with limited literacy or from culturally and linguistically diverse backgrounds.

Winter, EnableUs Community

Totally. Many participants process written information differently. If you hand them dense paragraphs, long, winding sentences, and jargon, you’re basically putting a wall between them and their own supports.

Will, EnableUs Community

And the research backs this up, not just in disability but across the general population. The more complex the document, the worse people understand it. Even highly educated people struggle when something is written in really formal, bureaucratic language with no white space.

Winter, EnableUs Community

I remember chatting with a small provider who was so proud of their twenty-page service agreement. They’d paid a lawyer a lot of money, and technically it was rock solid. But when they actually sat down with participants and asked, hey, what do you think this means, most people couldn’t tell them.

Will, EnableUs Community

Yeah, and that’s the key bit. The NDIS Practice Standards talk about supporting participants to exercise choice and control. You literally can’t do that if your paperwork is so complex that people can’t understand what they’re choosing.

Winter, EnableUs Community

Exactly. Accessible documentation isn’t a nice-to-have add-on. It’s part of person-centred practice and respect for autonomy. It’s how you show participants, we actually want you to understand your rights and your options here.

Will, EnableUs Community

So in this episode, we’re not saying, throw away compliance or dump the legal protection. We’re talking about simplifying and clarifying, so your agreement still does its legal job, but it also passes the participant test: can they genuinely understand it?

Winter, EnableUs Community

And we’re going to get really practical. We’ll walk through how to turn those legal-textbook style agreements into plain-language, accessible documents. Then we’ll talk about design, Easy Read, translations, and how to make sure you’re still covered legally while being clear.

Will, EnableUs Community

Alright, let’s talk about how you actually do this. When we say plain language, we don’t mean dumbing things down or leaving out important legal points. We mean saying the same important stuff in a way people can understand quickly.

Winter, EnableUs Community

Yeah, plain language is about clarity. It’s choosing familiar words instead of technical terms where you can, it’s using short sentences, and it’s organising the information logically. One idea per sentence, not three or four jammed together.

Will, EnableUs Community

Let’s go through some really simple swaps. Instead of a phrase like "in the event that," just say "if." Instead of "facilitate the provision of supports," say "provide supports" or "deliver supports." And that classic one "due to the fact that" can just be "because."

Winter, EnableUs Community

Yeah, these sound tiny, but when you change them across an entire document, the reading experience shifts massively. Suddenly the agreement sounds like something you’d actually say out loud to a participant, instead of a court transcript.

Will, EnableUs Community

Sentence length is a big one as well. Long sentences with multiple clauses force people to hold a lot of ideas in their head at once. For many participants, that’s just not realistic.

Winter, EnableUs Community

Let’s use an example from the kind of wording we see all the time. Something like, "The participant agrees that the provider may share information with other professionals involved in their care where such sharing is necessary for coordination of supports and is consistent with the privacy policy previously provided."

Will, EnableUs Community

Yeah, that’s one sentence doing a lot of heavy lifting. If we simplify it, we might say, "We may share your information with other professionals who support you. We only share your information when it’s needed to coordinate your supports. We follow our privacy policy when we do this." Same meaning, three short sentences.

Winter, EnableUs Community

And notice how that version is much easier to read aloud to someone, or for them to read themselves. It breaks the idea down step by step, which reduces the cognitive load.

Will, EnableUs Community

Structure is the other big lever you can pull. Many agreements are structured around internal admin categories, not around what a participant actually wants to know first.

Winter, EnableUs Community

Instead, think about the participant’s journey. Start with the most important stuff they need right now. What is this service? How will you support them? What can they expect from you, and what do you need from them?

Will, EnableUs Community

Headings really help here. And again, use plain language in the headings themselves. So instead of "Participant Rights and Responsibilities," you might say, "What you can expect from us and what we need from you." It’s more direct and actually tells people what they’ll find in that section.

Winter, EnableUs Community

Another one we see is "Service Delivery Framework." Like, what does that even mean to most people? You could just call it "How we will support you." Straight away that feels more human and more understandable.

Will, EnableUs Community

And once you’ve got those clear headings, don’t bury key points in long paragraphs. Use bullet points for lists or when you’ve got a few related pieces of information. That way participants can scan and find what matters.

Winter, EnableUs Community

Also, if there are technical or legal terms you absolutely have to keep, explain them in simple language right next to where they appear. Don’t just dump a glossary at the back and hope people flick to it.

Will, EnableUs Community

Yeah, like if you have to use "reasonable notice," you might write, "You must give us reasonable notice, which means at least 24 hours before a scheduled shift." Suddenly, "reasonable" has a concrete meaning.

Winter, EnableUs Community

So we’ve talked about language and structure, but design really matters too. You can have the clearest wording in the world and still lose people if the document is visually overwhelming.

Will, EnableUs Community

Yeah, if everything is crammed onto the page in tiny font with no white space, most people are going to check out, and it’s especially hard for anyone with low vision or visual processing differences.

Winter, EnableUs Community

A few practical things you can do straight away: choose an easy-to-read font, make your body text at least size 12, preferably a bit bigger, and use larger sizes for headings. Keep a good amount of spacing between lines and between sections.

Will, EnableUs Community

Contrast is huge as well. Black text on a white background is the safest option. Avoid light grey text, text over images, or bright coloured backgrounds that make it harder to read. It might look "designed," but it often kills readability.

Winter, EnableUs Community

And leave some breathing room. White space isn’t wasted space, it actually helps people focus on one section at a time without feeling hit by a wall of text.

Will, EnableUs Community

Then there’s the question of accessible formats. For some participants, a standard service agreement, even simplified, still won’t be enough. That’s where Easy Read versions come in.

Winter, EnableUs Community

An Easy Read version uses really simple sentences, large text, lots of white space, and often images to support key ideas. It’s super helpful for participants with intellectual disability who want to understand things independently or with minimal support.

Will, EnableUs Community

You might not need Easy Read for every single document in your business, but doing it for your key documents – your service agreement, your rights and responsibilities, your feedback and complaints process – can make a huge difference.

Winter, EnableUs Community

For participants from culturally and linguistically diverse backgrounds, think about translated versions too. Interpreters are great in meetings, but having a translated document lets people take it home, sit with it, and go through it with family.

Will, EnableUs Community

And don’t forget examples. Instead of just saying, "You have the right to make a complaint," you can add something like, "If you are unhappy with your support worker, you can make a complaint. Here is how." That kind of concrete scenario helps people see how the process works in real life.

Winter, EnableUs Community

Now, a lot of providers worry that if they simplify things too much, they’ll lose legal protection or fall short of compliance. But clear language and legal validity actually work together. Courts increasingly look at whether both parties genuinely understood what they agreed to.

Will, EnableUs Community

A practical approach is to build in two kinds of review for your key documents. First, have your legal advisor check that the agreement protects your organisation and meets your obligations. Then, just as importantly, have a couple of participants or a participant advisory group review it for clarity.

Winter, EnableUs Community

Yeah, you want both voices. The legal review keeps you covered; the participant review tells you if the thing is actually usable. And if you’re nervous, start small: take one section of your current agreement and run this plain-language treatment on it.

Will, EnableUs Community

Maybe start with "What you can expect from us" or "How we will support you." Rewrite the heading in plain language, shorten the sentences, swap out the jargon, add bullet points, and look at the layout. Then test it with a couple of participants and ask, does this make more sense?

Winter, EnableUs Community

Over time, you can work through the whole agreement like that. The end goal is a document that still satisfies an auditor or a court, but that a participant can read and say, yep, I actually get what I’m signing.

Will, EnableUs Community

And that’s where compliance and person-centred practice line up really nicely. You’re not just meeting the Practice Standards on paper, you’re living them by making information genuinely accessible.

Winter, EnableUs Community

Alright, we’ll wrap it there. If you’re listening and thinking, our forms are a bit of a legal maze, you’re definitely not alone, and you don’t have to fix everything overnight. Just pick one high-impact document, like your service agreement, and start simplifying.

Will, EnableUs Community

Yeah, tiny changes add up fast. Shorter sentences, clearer headings, better layout – your participants will feel the difference, and so will your staff who have to explain these documents every day.

Winter, EnableUs Community

Thanks for hanging out with us on the The EnableUs Community Podcast podcast. I’m Winter…

Will, EnableUs Community

And I’m Will. Take care, keep your paperwork simple and accessible, and we’ll catch you in the next episode.