- Why "final 2" files keep appearing
- Deciding the official location, status and who signs off
- Why co-editing and version history still need agreed rules
The short answer
Confusion over the latest version comes less from having many files and more from never deciding which one counts as official. Three things need deciding: where the official file lives, what state it is in, and who makes it final. Once those are settled, a folder full of files becomes much less confusing.
When "final 2" appears
When several people work on the same document, extra files appear in situations like these.
- You email it as an attachment for review, and the reviewer replies with an edited copy.
- Someone copies it to their own computer, edits it there, and forgets to put it back in the shared folder.
- To keep the earlier version, someone saves a new copy called "final," then "final 2."
Each of these is a reasonable thing to do at the time. But without an agreed home for the official file, attachments and local copies look just as authoritative.
A newer save time does not mean a file has been reviewed. The most recently saved file is not necessarily the approved one.
Pick one official location
First, agree on the one place where the official file lives, such as a specific folder in a shared folder or a cloud shared drive. Treat email attachments and local copies as working copies for review or editing, and bring any changes back to the file in the official location.
Tell in progress, awaiting review and final apart
Next, give each file one of three states.
| State | Meaning |
|---|---|
| In progress | The author is still editing |
| Awaiting review | Handed to the reviewer |
| Final | Approved by the person who signs off; no further edits |
Choose a way of showing the state that your team can keep up without effort: a suffix on the file name, a folder for each state, or a status feature in the service you already use, if it has one. Also agree whether a final file that needs changing goes back to awaiting review.
Example: a quote
For example, say a salesperson writes a quote, their manager checks it, and it is sent to the client once final.
- The salesperson creates it in the official location and marks it in progress.
- When done, they mark it awaiting review and tell the manager where it is.
- The manager reviews it and, if all is well, marks it final.
- Only the final file is sent.
If the price needs to change after it is final, do not edit it in place. Move it back to awaiting review and have the manager look again.
There is one official location, and only a file marked final is sent.
Being saved most recently is not the same as being reviewed.
Even with co-editing and version history
Co-editing, where several people can edit a file at once, and version history, which lets you go back to an earlier state, both help reduce confusion. But neither tells you which point in time is official or who approved it. You still need the agreed rules.
Do not delete old versions or history just to tidy up. Some documents and records need to be kept for business reasons. Before deleting anything, check your retention rules and who is responsible.
In summary
Checklist
- Is there a single official location?
- Are attachments and local copies treated as working copies?
- Can you tell in progress, awaiting review and final apart?
- Is it clear who makes a file final?
- Have you agreed what happens when a final file needs changes?
One thing to check today
Pick one document you use often and share its official location with your team.