How to Explain Service Agreements to Your Participants
This episode breaks down the NDIA’s latest thinking on service agreements, showing why the real focus is on clear explanation, supported decision-making, and making sure participants genuinely understand what they’re agreeing to.
It also covers valid consent for information sharing, practical communication adjustments, audit-ready documentation, and how providers can build trust through honesty and consistent team training.
Chapter 1
Beyond the Signature
Will, EnableUs Community
So I- I- I was looking at this report from the NDIA, right? They did this massive consultation on service agreements, wrapped up on the 31st of March 2026. And the big takeaway isn't about, you know, updating the legal jargon in the document. It's actually about how we explain the thing. Like, literally, the conversation you have while sitting across from a participant.
Winter, EnableUs Community
Wait, the 31st of March 2026? That's, um, that's incredibly recent. So they're basically saying a signed piece of paper means... what, nothing? If the person didn't actually grasp what they were signing?
Will, EnableUs Community
Exactly, yeah! It's- it's no longer just "did they sign on the dotted line." It's "did they genuinely understand their options and make an informed decision?" The NDIA is shifting the benchmark. If you just hand over a twenty-page document and say, "Oh, just look this over and sign here," you are... well, you're failing the compliance test, even if the contract itself is legally perfect.
Winter, EnableUs Community
Right, right. Because, let's be real, most people see a thick contract and their eyes just, you know, glaze over. It's- it's intimidating. So, how do we actually do this? Like, practically, when a provider is sitting down with someone?
Will, EnableUs Community
Well, first off, you don't send them home with it to read alone. You set aside unhurried time. You sit down together—with their family or an advocate if they want—and you walk through it. Section by section. But here's the kicker: the way we check if they get it. We all do that thing where we ask, "Does that make sense?" or "Any questions?" right?
Winter, EnableUs Community
Guilty. I- I do that all the time. It's just a habit.
Will, EnableUs Community
Yeah! But the problem is, a participant might just say "yes" because they feel put on the spot, or they're tired, or they don't want to seem like they don't get it. So, instead, you ask them to explain a key point back to you in their own words. Like, "Just to make sure we're on the same page, what's your understanding of what happens if you need to cancel a session?"
Winter, EnableUs Community
Oh, that's clever. Because if they can't put it in their own words, they haven't actually... it hasn't clicked. It forces you to translate the legal speak into, you know, actual plain English. And what about how they want to communicate in the first place? Like, surely we have to match their style?
Will, EnableUs Community
Absolutely. And this isn't just about being polite, Winter. If a participant has specific disability-related communication needs, ignoring them can actually breach the NDIS Practice Standards and the Disability Discrimination Act. It's a legal obligation to make reasonable adjustments.
Winter, EnableUs Community
So, wait, what does that look like in practice? Proactively offering Easy Read or visual guides?
Will, EnableUs Community
Yes, exactly! Don't wait for them to ask for an Easy Read version, or large print, or Braille. Proactively offer those formats as standard practice. You could even have a simple visual summary—like a one-page diagram with icons showing the schedule, the costs, and the cancellation process—alongside the formal contract. It makes a world of difference.
Winter, EnableUs Community
I love that. It takes the pressure off the participant to have to advocate for their basic communication needs right at the start.
Chapter 2
Consent, Limits, and Audits
Will, EnableUs Community
Now, the other huge part of this is consent. Often, the service agreement is where the participant gives consent for us to start working, but also to share their information. And legally, for consent to share NDIS participant information to be valid, it has to meet five specific elements.
Winter, EnableUs Community
Five? Okay, wait, let me guess. It has to be... freely given? Like, no pressure?
Will, EnableUs Community
Spot on. No pressure, no coercion. And crucially, they have to know that if they say "no" to sharing information, they still get the service. You can't withhold support just because they don't want you sharing their details with, say, an allied health provider or a family member.
Winter, EnableUs Community
Right, so you have to be super explicit about that. It can't be some hidden, default tick-box. What are the other elements?
Will, EnableUs Community
Well, it has to be informed—they must understand exactly what will be shared, with whom, and why. It has to be specific to the current situation, not some blanket, forever consent. It has to be current, and they must have the capacity to give it. And from an audit perspective, you have to prove all of this. Auditors aren't just checking for a signature anymore. They want to see the evidence of the *process* of how you got that consent.
Winter, EnableUs Community
Wait, how do you document a conversation? Like, do you write a story about it?
Will, EnableUs Community
Sort of! You keep detailed file notes. You record who was in the room, if there was an interpreter or advocate, what formats you used—like if you used the visual guide—and any specific questions the participant asked and how you answered them. That's the paper trail that proves the consent was genuinely informed.
Winter, EnableUs Community
That makes sense. It's about showing the quality of the interaction, not just the result. And I suppose that honesty extends to what you *can't* do, right? Like, being upfront about your limitations as a provider.
Will, EnableUs Community
Oh, absolutely. This is huge for building trust. If a participant asks for, say, weekend support, and you don't have the staff for it, don't give a vague "we'll see what we can do" just to get the contract signed. Be direct. Say, "We can't provide weekend support right now, but we can help you find someone who can." It builds so much more credibility than over-promising and under-delivering two weeks later.
Winter, EnableUs Community
Yeah, because then you've broken that trust right at the start. And really, this whole agreement thing... it shouldn't just be a "one and done" task at onboarding, should it?
Will, EnableUs Community
No, not at all. It's a living document. You should build explanations into your regular reviews. Check back in to see if the arrangements still work, if they still understand the costs, or if their needs have changed. And lastly, make sure your whole team is trained to do this consistently. The quality of this conversation shouldn't depend on which intake officer happens to be working that day.
Winter, EnableUs Community
Yeah, consistency is key. Well, that's a lot of really practical stuff to think about. Definitely shifts how we look at those sign-up meetings. Thanks for walking us through it.
Will, EnableUs Community
No worries at all. Talk soon.