Somewhere on your file server is a document called final_v3_REAL.docx. Next to it, final_v3_REAL_updated.docx, and possibly final_v3_REAL_updated_USE_THIS_ONE.docx. Everyone knows which is correct, right up until the person who made them is on vacation and a client asks a question.
Here is the reframe that makes this worth fixing. File naming is not a tidiness problem. It is a search problem. You are writing the words a future person, possibly you, will type into a search box in three years while a client waits on the phone. Every filename is a small bet about what somebody will remember later, and most businesses lose that bet constantly.
Why final_v3_REAL Happens and What It Costs
Nobody sets out to create that filename. Naming a file is a decision made at the worst possible moment: you are finishing something, you are tired of it, and the dialog box stands between you and being done. So you type whatever gets you out fastest. The name describes your relationship to the document, not the document.
The cost never arrives as one big number. It arrives as a two minute search, forty times a week, across a dozen people. As a proposal sent with last quarter’s pricing because someone grabbed the wrong version. As an employee leaving and their filing logic going with them. We have written about why saving time takes priority over saving money. This is one of the purest examples: the fix costs nothing and the savings compound for years.
Write Dates So They Sort Correctly
If you change one thing after reading this, change this. Write dates as year, then month, then day, with leading zeros. The U.S. National Archives recommends international standard date notation in filenames, with hyphens or without.
The reason is mechanical, not aesthetic. Computers sort text left to right, character by character. A date written the American way puts the month first, so a folder sorted by name interleaves every January from every year, then every February. Put the year first and the sort order becomes chronological automatically, in every application.
Same logic applies to numbers. The National Archives recommends leading zeros so sequences sort correctly. Without them, item 10 lands ahead of item 2.
What Belongs in the Name Versus the Folder
This is where most conventions go wrong. Teams either repeat the whole folder path inside every filename, producing something unreadable, or put nothing in the name and rely on the folder for context, which breaks the moment a file is emailed, downloaded, or found through search.
Our test: a filename should make sense alone on someone’s desktop, no folder around it. That usually means four elements, no more.
- Who it is about. A client or project prefix, ideally a short abbreviation your team agrees on. Not the full legal name.
- What it is. The document type in one or two words: proposal, invoice, contract, scope, report.
- When. The date, year first, or a version number with leading zeros if the date is not the useful anchor.
- Anything that distinguishes it from its siblings. Only if needed. Usually it is not.
The National Archives also advises keeping filenames to roughly twenty five to thirty five characters, warning that an overly complex or lengthy scheme becomes susceptible to human error. That is tighter than most teams expect, which is why abbreviations matter. Long, precise names feel responsible and get abandoned within a month.
A few mechanical rules from the same guidance are worth adopting outright: use letters and numbers rather than symbols and spaces, use hyphens or underscores in place of spaces, and keep the file extension. Microsoft’s OneDrive and SharePoint documentation lists characters not allowed in file and folder names, including quotation marks, asterisks, colons, angle brackets, question marks, slashes, and the vertical bar. Leading and trailing spaces are out too.
Deep Folder Trees Lose to Good Names and Search
This is the contrarian part, and we will defend it. Elaborate folder hierarchies feel like organization, but they encode one person’s mental model of the business and then quietly rot. Clients get filed by industry until someone files by region. A project sits under the year it started, and nobody remembers which year. Every level you add is another guess a future person has to get right.
There is a hard technical limit too. Microsoft documents that the entire decoded file path, including the file name, cannot exceed 400 characters in OneDrive and SharePoint. That sounds enormous until you have four nested folders with descriptive names and a long document title inside. We have watched businesses hit that ceiling and be baffled by why a file will not sync.
A shallow structure with disciplined names does better. Two or three levels, then let the names and the search box work. Search cannot read your folder hierarchy’s intent, but it will find every file with a client abbreviation and the word “invoice” in the name.
Agreeing on It as a Team
A convention that lives in one person’s head is not a convention. It is a preference, and it will be politely ignored. Three things make it real.
- Write it down on one page with examples. Not abstract rules. Five actual filenames people can copy the shape of. Examples teach faster than policies.
- Publish the abbreviation list. Every client and project prefix, in one place everyone can reach. The moment two people invent different abbreviations for one client, the system breaks.
- Make it easy to be lazy correctly. Template files pre-named. A saved example in each project folder. The path of least resistance has to be the right one, because on a busy day that is the path people take.
Keep it simple enough that a new hire can use it correctly on day one. The National Archives warning about complexity applies to the rules as much as the names.
Fixing the Past Without a Migration Project
Here is where we save you an expensive mistake. Do not rename five years of files. We have watched businesses budget weeks for a great renaming, get a tenth of the way through, lose momentum, and end up with two inconsistent systems instead of one bad one. Worse than where they started.
Fix forward instead. Three rules handle it.
- Everything new gets the new name. Starting on a date you announce, not gradually. A clean line makes it obvious which side of the change a file came from.
- Anything you touch gets renamed as you touch it. Open an old file to edit it, rename it on the way out. This costs seconds and converts exactly the files that matter, because the ones people open are the ones worth finding.
- Bulk rename only where the pattern is obvious. A folder of consistently misnamed monthly reports is worth a batch fix. A drive full of one-off documents is not.
After a year, the files people use weekly will be named well and the ones nobody has opened will still be a mess. That is the correct outcome. Those were never the problem.
The Bottom Line
Good file naming is not about being organized. It is about making documents findable by someone who does not share your memory of creating them, which after enough time includes you. Put the date first so things sort. Put the client and document type in the name. Keep it short enough that people will type it. Go shallow on folders. Fix the past by fixing the present, not by launching a project.
Businesses that get this right are not more disciplined than everyone else. They decided once, wrote it on one page, and stopped renegotiating it.
If your shared drive has reached the point where nobody wants to look for anything in it, we can help you settle on a convention that fits your team and set up storage so search does the lifting. We work with businesses across Denton County. Contact us today.
Sources:
Comments are closed