A surprising amount of office work begins with a question that should be easy to answer: which file is the current one?
The problem usually does not start with bad intentions. Someone downloads a document, makes a small change, sends it by email, another person saves a copy, and before long the team has several versions with names such as final, final-2 and final-revised.
The cost is not only clutter. People review the wrong draft, repeat work, miss corrections and become cautious about changing anything because they are no longer sure what everyone else is using.
Give the current version one obvious home
For a document that several people use, choose one location that counts as the working source. That might be a shared drive, a team workspace or a document system the team already uses.
The important part is not the platform. It is the rule: if somebody wants the latest version, there should be one obvious place to look first.
Email attachments and downloaded copies can still exist, but they should not quietly become competing masters.
Use names that describe the document, not its history
A filename does not need to contain the entire editing story. Names such as final-final-v3 usually tell people that version control has already failed.
Use a stable, descriptive name for the working document. If dated snapshots are genuinely useful, add the date in a consistent format. If formal versions matter, use a simple version number and record what changed somewhere people can find it.
The goal is to make the document identifiable at a glance, not to encode every conversation into the filename.
Separate working files from approved records
Some documents move through a clear transition: draft, review, approved and archived. Treating all four as if they are interchangeable creates confusion.
A working file can continue to change. An approved record should normally be protected from casual editing. An old version that must be retained should be clearly archived rather than left beside the current file with a nearly identical name.
This distinction is especially useful for policies, procedures, client deliverables, price lists, templates and recurring operational documents.
Make ownership visible
When several people can edit a file, somebody should still be responsible for keeping the working version coherent.
That person does not need to approve every change. They simply make sure that comments are resolved, obsolete copies are not presented as current and the document reaches its next clear state.
Without ownership, version control often becomes everybody's concern and therefore nobody's job.
Link to the file instead of sending another copy
When the platform allows it, share a link to the working document rather than attaching a fresh copy every time.
This keeps discussion connected to the same source and reduces the number of independent files that can continue circulating after they are outdated.
There are exceptions, especially when a fixed record must be preserved or a recipient cannot access the shared system. Those exceptions should stay exceptions.
Archive deliberately
Old files are sometimes valuable. They can show what was agreed at a particular point, support an audit trail or make it possible to recover an earlier approach.
Keeping them is not the problem. Keeping them in the same place, with the same visual weight and almost the same name as the current version is.
Move superseded material into a clearly labelled archive and keep the active workspace focused on what people should use now.
A small test
Ask a colleague who did not create the document to find the current version without instructions.
If they have to search several folders, inspect modification dates, compare filenames or message somebody to confirm, the system is relying on memory rather than clarity.
Small teams do not need elaborate document governance for every file. They do need a reliable answer to one basic question: where is the version we are supposed to use?