Making Policies Participant-Friendly

Will, EnableUs Community

Alright, welcome back to The EnableUs Community Podcast! I’m Will, and as always, I’m joined by Winter. Today, we’re diving into something that honestly gets overlooked way too often—making policies participant-friendly. And, look, I know “participant-friendly” sounds like a buzzword, but it’s actually the difference between ticking a compliance box and building real trust with the people you support.

Winter, EnableUs Community

Absolutely, Will. I mean, we’ve talked a lot in past episodes about how paperwork isn’t just paperwork—it’s about people, right? And when your policies read like a legal contract, you’re not just making life harder for participants, you’re kind of putting up a wall. The NDIS Practice Standards actually require us to make sure participants understand their rights, the complaints process, and how services are delivered. But it’s not just about meeting the standard—it’s about empowering people to make informed decisions and feel confident to speak up.

Will, EnableUs Community

Yeah, and I reckon the best example is the Complaints Process. If that’s buried in jargon, participants might never feel comfortable raising concerns. But if it’s clear—like, “If you’re unhappy, here’s what you do, and here’s what happens next”—suddenly, you’re building trust. You’re saying, “We want your feedback, and we’ll actually listen.”

Winter, EnableUs Community

That’s so true. I had this moment with a client a while back—she’d always been a bit hesitant, never really asked questions. Then we gave her an Easy Read version of our policies, with pictures and plain language. Next meeting, she actually brought up a question about her service agreement. It was like, just having that document in a format she could understand gave her permission to speak up. It was honestly one of those moments where you see the impact of getting this stuff right.

Will, EnableUs Community

Yeah, and it’s not just about the participants, either. Auditors love seeing that you’ve made the effort to provide info in a way that suits the participant. It’s a win-win—smoother audits, stronger trust, and, honestly, less stress for everyone.

Winter, EnableUs Community

Exactly. And it’s not just the Complaints Process—think about Service Agreements, Rights and Responsibilities, Consent Forms, even your welcome packs. Every single one is a chance to build understanding and connection. So, let’s talk about how to actually make these documents clear and welcoming, not just compliant.

Will, EnableUs Community

Alright, so, how do you actually turn those dense, jargon-filled policies into something people can actually use? There’s this thing called the Plain Language Test, and it’s honestly a game-changer. Basically, you run your document through five checks: is it at a Grade 8 reading level or below, are the sentences short and simple, do you avoid acronyms or explain them, does it sound natural when you read it out loud, and is the tone friendly and respectful?

Winter, EnableUs Community

Yeah, and don’t forget layout—clear headings, white space, bullet points. It’s not just about the words, it’s about how easy it is to find what you need. I remember we had this Service Agreement that was, honestly, a nightmare. Full of “hereby” and “incumbent upon” and all that. We rewrote it to say things like, “If you’re unhappy, you can make a complaint at any time. We’ll listen and respond within two business days.” Suddenly, people actually read it—and understood it.

Will, EnableUs Community

Yeah, I’ve seen that too. During onboarding, when I switched to using simple, friendly language—like, “Please tell us if your needs change! Call or email us, and we’ll update your plan”—participants started engaging way more. They’d ask questions, clarify things, and you could see they felt more comfortable. It’s like, the more human your documents sound, the more human your service feels.

Winter, EnableUs Community

And it’s not just about being nice, it’s about being clear on responsibilities too. Like, instead of vague promises, say, “We’ll respond to complaints in two business days.” That way, everyone knows what to expect. It’s so much better than, “We’ll address concerns in a timely manner”—what does that even mean?

Will, EnableUs Community

Yeah, “timely” could mean anything! And, look, if you’re not sure if your document passes the Plain Language Test, just read it out loud. If you trip over the words or it sounds like a robot wrote it, it’s time for a rewrite. I always say, if my mum can’t understand it, it’s too complicated.

Winter, EnableUs Community

That’s a good rule! And honestly, it’s not about dumbing things down—it’s about making sure everyone has the same chance to understand and make decisions. That’s real empowerment.

Will, EnableUs Community

So, you’ve got your policies in plain language—now you’ve gotta make sure everyone can actually access them. That means thinking about digital, print, Easy Read, translations, even visual formats. I’ve seen providers use flowcharts and images to explain the Incident Response process, and it made a massive difference for one participant who’d never really understood it before. Suddenly, it just clicked for them.

Winter, EnableUs Community

Yeah, and there are so many tools out there now. Canva is great for designing visual layouts, and even Google Docs or Microsoft Word’s Read Aloud feature can help you check if your tone is right. And don’t forget, some people need large print, or documents in their first language, or even just a printed copy instead of a PDF. It’s about meeting people where they’re at.

Will, EnableUs Community

Exactly. And, like, don’t underestimate the power of a good welcome pack or a website with all your key documents in one place. Add footers with version dates and contact details so people know they’ve got the latest info and can reach out if they need help. It’s those little touches that make a big difference.

Winter, EnableUs Community

And remember, even the best documents don’t mean much if your team isn’t confident explaining them. So, train your staff to walk participants through policies, check for understanding, and always be open to questions. That’s how you turn compliance into connection.

Will, EnableUs Community

Couldn’t agree more. Alright, that’s a wrap for today’s episode on making policies participant-friendly. Next time, we’ll dig even deeper into practical tools and maybe share a few more stories from the field. Winter, always a pleasure chatting with you.

Winter, EnableUs Community

You too, Will. Thanks everyone for listening—don’t forget to check out our previous episodes if you missed them, and we’ll catch you next time on Using Compliance Documents. See ya!

Will, EnableUs Community

See ya, everyone!