Here is something I’ve seen more times than I can count. An organisation updates a policy. The new version goes into the shared folder and the old one is left where it was, because nobody likes deleting things. Some time later somebody opens the old one to check a detail, and it saves. Now the old policy is the most recently updated file in the folder. It sits at the top when anybody sorts by date, and people keep going back to it whilst the updated policy sits in the same folder, ignored.
Budget drafts are the other place I see it most, and the confusion there costs more, because two people can be working to two sets of numbers and both believe theirs is current.
I don’t think any of that comes down to carelessness. Everybody involved did something sensible. Dealing with version control on documents can feel like a frustrating challenge, not least because it’s not something a single person can own. What I’ve found useful is understanding why the folder gets it wrong, because once you know that, the habits that fix it stop feeling fussy.
What the folder is actually sorting
A folder gives you two ways to answer “which one is the latest?”, and both can mislead you.
The first is sorting by date modified, which is the one most of us reach for. It records the last time anybody touched a file. That is a different question from which file is current, and the policy story above is what happens when the two answers come apart.
The second is sorting by name, and this is where dated file names ought to help. Usually they don’t. Name a report 03-11-2025 and the next one 01-03-2026, sort the folder by name, and the March one sits above the November one. Most people have seen that, shrugged, and gone back to date modified.
The reason is that the computer is not reading the date. It has no idea those characters are a date. It compares the first character of one name with the first character of the other, and if they match it moves on to the second, and it stops the moment it finds a difference. So 01-03-2026 sorts above 03-11-2025 because 0 comes before 3, and the years never get looked at.
Put the year first
Once you know that, you can work out the fix without me. Write the date year first: 2025-11-03, then 2026-03-01. Now the first difference between any two names is the year, then the month, then the day, and the folder turns into a calendar and stays one, with nobody maintaining anything. That order is the international standard for writing a date, ISO 8601, and this is a large part of why it exists.
It also fixes the policy problem, which is the bit I like. A date in the name doesn’t change when somebody opens the file to check a detail. Whilst this might not be your natural preference, it makes your folders much faster to browse and means the default folder sorting (by name) puts your files in date order, so the latest one is always at the same end of the list.
The same comparison explains two other things you’ve probably met. If you number versions, v10 sorts as though it were older than v2, because the 1 loses to the 2, which is why people who do this a lot write v02 and v03. And the word final fails for a reason that has nothing to do with the computer. Final is a prediction. The file needs one more change, it becomes final2, and the name has stopped telling the truth. The University of Cambridge’s guide to file naming and version control covers all of this with worked examples. It was written for researchers and every rule in it transfers to a shared drive.
You may not need separate versions at all
This is the one almost nobody is told. If the document lives in SharePoint, OneDrive or Google Drive you may not need separate versions at all, because every save is already being kept. Right-click the file and look for version history. Every draft is in there, with who changed it and when, and you can open or restore any of them. The trick is to keep it that way by sending people a link rather than the file, so there’s only ever one copy and the history stays attached to it.
It has limits, and they’re worth knowing before you lean on it. It only works for files stored online, so a document sitting on your desktop has no history at all. How much is kept is a setting somebody chose: Microsoft keeps a capped number of versions, which whoever administers your Microsoft 365 can change, and Google may merge older versions together to save space. And it isn’t a backup. It protects you from your own edits, and does nothing if the account or the site the document sits in is lost.
Give the document a named person
For more important documents, it can be worth adding a cover page. For policies, strategy documents or operational documents, a cover page with a ‘last reviewed by [person] on [date]’ not only helps you manage regular reviews, it also makes sure you know who to talk to if a document feels out of date. It gives the document the one thing the drive can’t: a named person who looks after it.
That would have settled the policy story in about ten seconds. Open either copy, read the review date on the front, and you know which one you’re holding. It’s the same question I asked in Who owns your payment system?, at a much smaller size. If your organisation already has a document control template or a policy register, use that before you invent your own.
Start with your own files
I wouldn’t try to introduce a naming convention across a team. They feel fussy, and nobody values one until they’re hunting for a report against a deadline. Rename the working files of one thing you have on the go instead, year first, and open the folder again to watch it sort itself.
None of these needs a project, a budget or anyone’s sign-off. You can do the first two on your own files this afternoon, and the third on the next policy you touch. That’s the thing I find encouraging about most digital capability: it’s rarely the big system that makes the difference, it’s a handful of habits like these, and they spread because somebody sees them working and copies them.
Tools & Systems is one of the six areas in the free Personal Digital Assessment, which takes about ten minutes.
