Full launch: week of 1 February 2027. Build Partner places are open now

Article

Version control without the chaos

Files named “final”, “final2” and “use-this-one” are a familiar problem. People save copies to make sure they have the right instructions, then nobody can tell which copy is current. Version control is simply a way to make that answer clear.

Choose one source for the current document

Agree where approved documents live and tell staff to use that location. Avoid circulating editable copies as a normal way of working. If people need offline or printed instructions, decide how those copies are identified and replaced. One reliable source is more useful than an elaborate numbering scheme.

Give each document a sensible identity

Use a title people recognise and a consistent way to identify versions. Include an owner and approval date where it helps. A number can be useful, but staff should not need to decode it to understand the document. The important test is whether two people can find the same approved instruction.

Control changes before release

Let staff suggest improvements, but decide who can edit and approve the final document. Check what has changed and who needs to know. Do not put a draft into the current-document folder simply because someone has updated it. Retain the earlier version when it is useful to explain previous decisions.

Remove old copies from everyday use

When a new version takes effect, archive the old version and make the current one obvious. Search common shared folders and noticeboards for stray copies. If staff have to print an instruction, have a method to replace it when it changes. Otherwise the paper quickly defeats the electronic system.

Keep it proportionate

For a small stable set of documents, a disciplined folder structure and a simple register may be enough. With several sites, frequent revisions or many staff acknowledgements, dedicated document control can save time. Review the method when it stops working, not simply because a newer tool is available.

Document Controller is intended to keep a clear current version, retain older versions, record approvals and track staff acknowledgements. Your business still decides which version to approve, how to tell people about changes and when a document should be withdrawn.

Planned for February 2027: try Document Controller free for 14 days.

This article provides general information only and is not legal or professional advice. Consider your own circumstances and get advice where needed.

Build Partner programme

Become a Build Partner

Build Partners help shape Document Controller for their industry, at 50% off for 12 months from the day your first card payment goes through: A$150.50/month + GST for 10 full users, instead of A$301/month + GST, and A$9.50/month + GST instead of A$19/month + GST per additional user, for businesses that apply by 31 December 2026. After that, 25% off for as long as they remain paying customers. The Build Partner discount covers the platform licence, the modules you lead and all your users, with no cap on the number of people, and excludes other modules, one-off services, usage charges, other non-subscription charges and Iridium AI Assistant Pro. Build Partners get guided setup and industry alignment with one of our team, their industry pack for the module they lead, as it's released, at their Build Partner discount, first access to new modules and direct input into what we build next.

Build Partner places are for businesses with 10 or more people, and we prefer 20 or more.

Document Controller is coming at launch. A small pilot with up to 3 Build Partners is planned from December 2026, and Document Controller is planned to go on sale from January 2027. We'll confirm your start date when we offer your place.