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.
More articles
- What an auditor may ask about document control
- How to record staff acknowledgements
- Prepare documents for document control
- Plan your audits before they are due
- Who should approve a work procedure
- How to tell field staff about changed procedures
- How to handle a nonconformance
- Corrective action that tackles the cause
- How to carry out an internal audit
- Make management reviews useful
- Managing risks and opportunities
- How to handle customer complaints
- Choosing and reviewing suppliers
- Keeping calibration records
- Do you need a quality management system?
- Policies, procedures and work instructions: what’s the difference?
- Document control for aged care and disability providers
- How often should you review your procedures?
- Moving from paper or shared drives without disrupting work
- Document control for construction and trades
- Inducting new staff on your procedures
- Quality records for manufacturers and engineering firms
- Contractor inductions: what to give contractors and what to record
- Food safety records that hold up in an inspection