When and How to Update Your Compliance Documents

Will, EnableUs Community

Hey everyone, welcome back to Using Compliance Documents. I'm Will, and as always, I'm joined by Winter. Today, we're diving into a topic that, honestly, I think gets overlooked way too often—when and how to update your compliance documents. Winter, how often do you reckon people actually check their policies?

Winter, EnableUs Community

Oh, probably not as often as they should, Will. I mean, it's easy to set and forget, right? But with the NDIS changing things up—like the Price Guide updates or new Practice Standards—if you’re not on top of it, you’re basically inviting trouble.

Will, EnableUs Community

Yeah, and it’s not just about ticking boxes. Outdated documents can actually put your whole service at risk. Like, I remember this provider—won’t name names—but they expanded, added a bunch of new services, and totally forgot to update their service agreement. Next audit, the auditor’s like, “Hang on, where’s the info about your new transport service?” It was a mess. They had to scramble to fix it, and it nearly cost them their registration.

Winter, EnableUs Community

That’s such a classic scenario. And it’s not just big changes, either. Sometimes it’s as simple as a new staff member or a tweak in the NDIS rules. Like, if the Price Guide changes, your agreements and pricing policies need to reflect that—otherwise, you’re technically non-compliant.

Will, EnableUs Community

Exactly. And, I mean, the NDIS expects at least an annual review, right? But if you’re adding new locations, or there’s a new Practice Standard, or even after an incident or audit—those are all triggers for an immediate update. It’s not just a “once a year and you’re done” thing.

Winter, EnableUs Community

Yeah, and sometimes people wait until something goes wrong before they even think about it. But by then, you’re already playing catch-up. It’s way less stressful to just keep things current as you go.

Will, EnableUs Community

So, let’s talk about how to actually do it. Like, what’s the step-by-step? I always say, start with a review—look at what’s changed, what needs updating. Then you edit, save a new version, and make sure you name it clearly. I always mess up the version names, though. Is it v3, v4, or v3.2? I dunno, I get lost sometimes.

Winter, EnableUs Community

Oh, you’re not alone there! Version confusion is real. My team once had two “final” versions of a policy floating around, and no one knew which was which. We ended up creating a compliance log—a simple spreadsheet, really—where we tracked every update, who made it, and when. It saved us so much hassle.

Will, EnableUs Community

That’s smart. And, like, using the right tools helps too. Google Docs is great for collaboration and version history, but if you want something more robust, there’s compliance management software that keeps everything in one place. Even just using Microsoft Word and saving to a shared drive can work, as long as you’re consistent.

Winter, EnableUs Community

Yeah, and don’t forget about archiving. You shouldn’t just delete old versions—keep them in an archive folder. Auditors love to see that you’ve got a record of changes. And always, always communicate updates to your team. There’s no point updating a policy if no one knows about it.

Will, EnableUs Community

Totally. And, I mean, even the best system can get tripped up if people aren’t on the same page. That’s why naming conventions, version logs, and clear communication are so important. Otherwise, you end up with three different “final” policies and no idea which one’s current.

Winter, EnableUs Community

So, let’s get into how you actually tell your team about updates. There’s a bunch of ways—emails, staff meetings, even training videos if it’s a big change. We’ve started using chat platforms like Teams for quick updates, and it’s made a huge difference.

Will, EnableUs Community

Yeah, and I reckon the key is to use more than one channel. Like, send an email, but also bring it up in your next staff meeting. Maybe even do a quick video walkthrough if it’s a complicated update. And for new staff, make sure they get the latest versions during onboarding. Otherwise, you end up with people following old processes without even realising it.

Winter, EnableUs Community

Exactly. And don’t forget about the audit trail. Auditors might ask, “When was this last reviewed?” or “Who signed off on this?” If you’ve got a compliance log or a policy review register, you can answer those questions in seconds. We set up recurring calendar reminders to review our top policies every quarter, and it’s honestly saved us from last-minute panic.

Will, EnableUs Community

I heard about a provider who did just that—set up reminders, ran regular internal training, and when the NDIS audit came around, they passed with flying colours. The auditor even commented on how clear their version history and communication was. It’s not rocket science, but it does take a bit of discipline.

Winter, EnableUs Community

Yeah, and it’s about building a culture where compliance isn’t just a chore, but something everyone’s invested in. If you make it part of your routine, it stops being this big scary thing and just becomes how you do business.

Will, EnableUs Community

Couldn’t have said it better. Alright, that’s all we’ve got time for today. If you’re feeling overwhelmed, just remember—start small, set up a review schedule, and keep your team in the loop. We’ll be back next time with more tips on making compliance work for you.

Winter, EnableUs Community

Thanks for tuning in, everyone. Will, always a pleasure chatting with you. See you all next episode!

Will, EnableUs Community

Cheers, Winter. Bye everyone!