Mastering Consent and Preferences

Will, EnableUs Community

G’day everyone, and welcome back to The EnableUs Community Podcast. I’m Will, here with Winter, and today we’re gonna dig into something that, honestly, I think gets way oversimplified—consent. Not just that one-off ‘sign here’ moment, but the idea of consent as a growing, living agreement between providers and participants. Winter, I feel like this came up heaps in our last episode about support agreements, but consent isn’t a checklist, is it? It’s sort of... an evolving record, right?

Winter, EnableUs Community

Totally, Will! Consent really is dynamic. Like, yes, getting a signature on a form is more concrete, but it isn’t the end of the story. The best practice is to treat consent as something active—something that’s revisited as people’s circumstances or wishes change. Written consent is definitely clearer and, honestly, so much safer for both sides, but if you’re stuck in a position where it’s only verbal, you really need to document every detail—what’s been agreed, who agreed to it, when, all that.

Will, EnableUs Community

Yeah, look, I learned that the hard way back in my provider days. I had this participant who’d verbally agreed to share some details with another provider, but—classic rookie error—I just wrote ‘agreed to share info’ in the notes. No specifics about what info, or for how long it was valid, or who was meant to get it. Months later, their needs changed, but we had nothing clear to fall back on, just my hazy memory and… I mean, you can guess how well that worked out. There was confusion, a bit of frustration on their end, and to be fair, I kinda deserved it for not being thorough. So please, for anyone listening—don’t do what I did. Get it in writing, and if you go verbal, lock every detail down in your documentation.

Winter, EnableUs Community

That’s it—you want to ask yourself, “If someone looked at these notes in a year, would they know exactly what was agreed and with whom?” Vague consent just doesn’t cut it, especially if things ever go sideways, or you get an NDIA audit. It protects everyone—participants, workers, the whole org—if it’s super clear, specific, and up-to-date.

Winter, EnableUs Community

Building on that, consent forms are great, but, Will, don’t you think capturing preferences is just as important? You’ve got permissions on one side and then you’ve got how someone actually wants to be supported on the other. Even tiny details, like whether someone prefers SMS over calls, or wants appointments in the afternoons, prevents a tonne of friction later on.

Will, EnableUs Community

Completely. I also reckon a lot of providers underestimate just how much these details shape someone’s day-to-day service. I mean, if you don’t document things like preferred communication style, or foods to avoid, you’re kind of setting the team up for mix-ups. Honestly, updating these details regularly should be as normal as checking someone’s NDIS plan status.

Winter, EnableUs Community

Yeah, exactly. Actually, I’ve got a little case study that sticks with me. We had a participant whose preferences around appointment times and worker gender changed a couple of times over six months. Because we made it a habit to review everything during every plan review—and honestly, just whenever anything felt different—it meant the team never missed the switch. There was zero drama; everyone felt heard, and the participant’s satisfaction never dropped.

Will, EnableUs Community

It’s such a smooth outcome when you get that right. Plus, updating consent or preferences shouldn’t be some big drama—if a participant calls up, or even just mentions a change during check-in, that’s your cue to update the records and note when and why. I always say, each update is just as important as the first go, otherwise you risk acting on old info and, yeah, that never ends well.

Winter, EnableUs Community

And the history matters—keeping track of what’s changed, who asked for the change, and the exact date. It’s that evidence trail that saves you if things ever get questioned later on. Old preferences shouldn’t just disappear, they need to be traceable for compliance and for trust.

Will, EnableUs Community

So, now we’ve got all these detailed records—consent, preferences, the works—let’s talk about keeping them safe but also useful. Security is non-negotiable. I mean, you’ve got to store everything encrypted and lock down access, ‘cause you’re dealing with the most personal info possible. But it’s gotta be accessible—otherwise, what’s the point?

Winter, EnableUs Community

Yeah, security’s only half the job if nobody can find what they need when they’re supporting someone. Systems have to be locked up tight but also practical—things like secure cloud-based storage so workers can pull up info in the field, but only if they’re supposed to. And you always want those access logs, right? Because having an audit trail is your protection if there’s ever a complaint or an NDIA check.

Will, EnableUs Community

Absolutely. I remember this one time—bit nerve-wracking—there was a service complaint, and the only thing that kept things calm was our audit trail. We saw exactly who accessed the doc, who updated the consent, even the timestamp. It was clear everyone followed the right process. Ended up reminding us how important regular team training is—doesn’t matter how good your policy is if no one can follow it or find what they need in a pinch.

Winter, EnableUs Community

That training piece is huge. If you’re not showing staff why this all matters, how to document the right way, and what to do if a participant wants to update or withdraw consent, you’re just hoping things go right. Audit trails, regular reviews, secure but accessible systems—it’s all part of protecting both sides and showing respect for participants’ autonomy.

Will, EnableUs Community

Well said. Alright, that’s all we’ve got time for in today’s episode. Thanks for tuning in, everyone. We’ll be diving into more real-world tips and stories in future episodes. Winter, always a pleasure chatting.

Winter, EnableUs Community

Thanks, Will, and thanks to everyone listening. Looking forward to next time—bye for now!