How to Track Edits Without Losing Document History

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 sounds a bit dry but, honestly, it's one of those things that can make or break your audit—tracking policy changes without losing your document history.

Winter, EnableUs Community

Hey everyone! Yeah, this is one of those topics that seems simple until you’re in the middle of an audit and someone asks, “So, when did you last update this policy, and who signed off on it?” Suddenly, you’re sweating, scrolling through old files, and hoping you didn’t just overwrite the last version.

Will, EnableUs Community

Exactly! And under NDIS requirements, it’s not enough to just have the policy sitting there. You’ve gotta show when it was updated, who did it, and what actually changed. If you can’t, you’re already out of compliance. I mean, I learned this the hard way. There was this small provider in Melbourne I worked with—great team, but they missed adding a version number to their complaints policy. When the auditor came, there was this whole confusion about which version was current. We spent hours digging through emails and old files. Nearly failed the audit just because of that one missing detail.

Winter, EnableUs Community

That’s such a common story. And it’s not just about ticking boxes, right? If you don’t have a clear audit trail, you risk using outdated policies, or worse, not being able to prove you’ve actually reviewed and improved your processes. That’s a big deal for participant safety and trust, not just compliance.

Will, EnableUs Community

Yeah, and if you can’t show a record of approvals or what’s changed, you’re basically inviting audit gaps. It’s like, you might have done all the right things, but if you can’t prove it, it doesn’t count. That’s the risk—no version control, no record of who approved what, and suddenly you’re scrambling.

Winter, EnableUs Community

And it’s not just policies, either. Forms, registers, service agreements—they all need the same level of tracking. If you’re not careful, you end up with a mess of files and no idea which one’s the right one to use.

Winter, EnableUs Community

So, let’s break down what auditors are actually looking for. There’s a few must-haves: version numbers, review dates, a summary of changes, and who was responsible for the update. If you’re missing any of those, you’re gonna have a tough time in an audit.

Will, EnableUs Community

Yeah, and the version number thing—honestly, it’s so simple but so easy to forget. Just a little “v2.3” or whatever in the footer, and suddenly you’ve got a clear progression. But it’s not just about the number. Auditors want to see when the document was last reviewed, what actually changed, and who signed off. That’s your review date, your change summary, and the responsible person all in one place.

Winter, EnableUs Community

And don’t forget the next review date! That’s one I see people miss all the time. Auditors want to know you’re not just updating things once and forgetting about them. They want to see you’ve got a plan to check back in, whether it’s quarterly, annually, whatever fits your organisation.

Will, EnableUs Community

Yeah, and I think it’s worth mentioning—sometimes auditors will ask for the actual change log or register. Like, “Show me what changed in your complaints policy and when.” If you’ve got that ready, you look super organised. If not, well, it’s a bit awkward.

Winter, EnableUs Community

I had a recent audit with a Sydney support organisation, and honestly, their versioning was so clear. Every document had a version number, review date, summary of changes, and the person responsible. The auditor was in and out of that section in minutes. It just made the whole process seamless. No digging, no confusion, just straight to the point.

Will, EnableUs Community

That’s the dream, isn’t it? And it’s not just about passing the audit. It’s about being able to show your team, your participants, and anyone else that you’re on top of things. It builds trust, and it makes your life so much easier when you need to find something fast.

Will, EnableUs Community

Alright, so let’s get practical. How do you actually track all this without drowning in admin? There’s the old-school manual way—Excel or Google Sheets. You set up a policy register table, track the version, review date, who did it, what changed, and when the next review is due. It’s simple, but it works.

Winter, EnableUs Community

Yeah, and even just putting the version number and review date in the footer of your document helps. Or, if you’re saving files, use a naming convention like “Incident-Policy_v2.0_Reviewed-June2025.docx.” That way, you can see at a glance what’s what. But if you’re managing a lot of documents or a bigger team, digital tools can save you heaps of time.

Will, EnableUs Community

Totally. Google Workspace is a game changer for this. The version history shows who edited what and when, and you can even restore old versions if you need to. Microsoft Word with OneDrive or SharePoint does the same thing—track changes, autosave, and you can set up approval workflows if you want to get fancy.

Winter, EnableUs Community

And for bigger organisations, a Document Management System like ShiftCare or Lumary is worth considering. They’ve got built-in audit logs, approval workflows, and you can restrict editing rights so only the right people can make changes. It’s a bit more setup, but it pays off if you’ve got a lot to manage.

Will, EnableUs Community

One thing we do at EnableUs Community is a dual-review process for high-risk documents. So, two people have to check and sign off before anything goes live. It actually saved us once—a critical policy update was about to go out with a mistake, but the second review caught it just in time. It’s a bit of extra work, but it’s worth it for peace of mind.

Winter, EnableUs Community

Yeah, and don’t forget to archive old versions. Never delete them! Just move them to a “Superseded Documents” folder. That way, if an auditor asks for an old version, you’ve got it ready. And always keep a change log, even if it’s just a quick summary in the document or your register.

Will, EnableUs Community

Assigning a compliance lead helps too—someone to oversee updates and make sure nothing slips through the cracks. And set a regular review schedule, like quarterly or annually, so you’re not scrambling at the last minute.

Winter, EnableUs Community

And share those updates with your team! Whether it’s in a meeting or a quick email, let everyone know what’s changed and why. It keeps everyone on the same page and makes compliance a team effort, not just a paperwork exercise.

Will, EnableUs Community

Alright, I think that’s a good place to wrap up. Tracking edits doesn’t have to be complicated, but it does have to be consistent. Use version numbers, keep your change logs, and never delete old versions. Your future self—and your auditor—will thank you.

Winter, EnableUs Community

Absolutely. And remember, staying compliant is an ongoing process. Start with these steps, and you’ll be ready for whatever comes next. Thanks for joining us, and we’ll catch you in the next episode!

Will, EnableUs Community

Thanks, Winter. See you next time, everyone!