Version control is the practice of tracking changes to a document over time so that you always know which version is current, what changed between versions, and how to recover an earlier state if needed.
For most office workers, version control does not require specialized software. It requires a consistent habit and a clear naming convention.
What Is a Document Version?
A version is a distinct state of a document at a point in time. When you make significant changes to a document — especially one that others will review or approve — saving a new version preserves the history of those changes. This is different from simply saving the file, which overwrites the previous state.
Manual Version Naming
The simplest approach to version control is including a version number in the file name:
ProjectProposal-v1.docx— first draft sent for reviewProjectProposal-v2.docx— revised after feedbackProjectProposal-v3-Approved.docx— final approved version
When a version is superseded, move it to an "Archive" or "Previous Versions" subfolder rather than deleting it. This preserves the history without cluttering the active workspace.
Identifying the Current Version
The current version should always be easy to identify. Options include:
- Keeping only the current version in the active folder and moving older versions to an archive subfolder
- Using a consistent suffix like "-Current" or "-Approved" on the authoritative file
- Maintaining a simple version log — a text file or spreadsheet row noting what changed in each version
Avoid using "final" in file names. Once a file is named "final", the next revision becomes "final2", then "final-REVISED", then "final-USE-THIS-ONE". Version numbers (v1, v2, v3) are unambiguous and sort correctly. Reserve a suffix like "-Approved" or "-Submitted" for the genuinely completed version.
Collaboration and Version Conflicts
Version conflicts happen when two people edit the same file simultaneously and save different versions. Common scenarios:
- Two people download the same file, edit it separately, and both upload their version
- One person emails a file for review while another continues editing the original
- A file is copied to a personal device, edited there, and the changes are never merged back
The best prevention is a clear rule: only one person edits a file at a time, or the team uses a shared editing tool that handles simultaneous edits automatically.
File Versioning vs. Software Source Control
Software developers use specialized tools like Git to track every change to every line of code. This level of version control is powerful but unnecessary for most document work. The lightweight approach described here — version numbers in file names, archived previous versions, a simple change log — is sufficient for the vast majority of office, nonprofit, and municipal document management needs.
Key Takeaways
- Use version numbers (v1, v2, v3) in file names instead of "final"
- Move superseded versions to an archive folder rather than deleting them
- Make the current version easy to identify at a glance
- Prevent version conflicts by establishing clear editing rules for shared files
Learn how to manage files on shared drives and collaborate effectively in Shared Drives and Collaboration.