File Naming Conventions People Actually Follow
Most naming conventions fail because they ask too much. A short, sortable pattern, the rules worth enforcing, and the ones to drop so your team actually uses it.
A file naming convention works when it is short enough to remember, sorts correctly by default and answers the one question people ask when they see a list of files: what is this, and which one is newest? Most conventions fail because they try to encode everything, the author, the department, the project code, the status, the version, and nobody types all that at five o'clock on a Friday.
The pattern
For most small teams this is enough:
YYYY-MM-DD matter-reference short-description
For example: 2024-02-06 T-114 gas safety certificate or 2024-01-30 INV-22 interview notes witness 2. Three parts, in that order, and nothing else.
Why each part is there
- Date first, year first. YYYY-MM-DD sorts chronologically in every file browser in every country, and avoids the ambiguity of 02/06 meaning February or June. Use the date of the content (the date on the letter, the day the photos were taken), not the date you saved it.
- A matter reference. A short, stable identifier for the tenancy, client or case. It lets a file be recognised even when it escapes its folder, as an email attachment or a download.
- A plain description. Three to six words a colleague would search for. "Inspection report", not "IR".
Rules worth enforcing
- No "final". "Final", "final2" and "final REAL" are the most reliable signs of a broken system. If versions matter, use v01, v02 at the end, or better, let your storage keep version history.
- Leading zeros. Write 01 to 09, not 1 to 9, so that 10 does not sort before 2.
- No personal names in file names where avoidable. A name in a file name is personal data that travels with every copy, appears in previews and search results, and is hard to redact later. The matter reference points to the person without naming them.
- Avoid special characters. Slashes, colons, question marks and some accented characters break on one system or another. Spaces or hyphens are fine.
Rules to drop
Author initials (the system already knows who uploaded it), department codes (the matter tells you), status words like "draft" or "approved" (status changes; file names should not), and long project codes nobody remembers. Every extra element lowers the chance the convention gets used at all.
Make it easy
Put the pattern and three real examples at the top of the shared folder, or in whatever place people see when they save. When you review a file with a bad name, rename it yourself rather than sending a reminder. After a few weeks the good names outnumber the bad ones and people copy what they see.
Where naming stops mattering
Naming conventions exist mainly because folders are weak: a file on its own carries no context. When files are attached to a matter record with its own dates, people and history, the name matters less, because the context comes from where the file lives. Even then, a dated, descriptive name helps when the file leaves the system. For the bigger picture of keeping working files and governed records apart, see records management vs document management.
