File naming convention: names that sort, search and survive

A file naming convention is an agreed pattern for naming documents so that they sort sensibly, can be found by search, and still make sense to somebody who was not there when they were created. It is the least glamorous piece of information management and among the highest-return, because every person who looks for a file benefits from it and nobody has to be trained.

The test of a convention is simple: can a colleague, a year from now, find the right file without asking you, and can they tell what it is without opening it? Most ad hoc names fail both.

The rules that carry most of the value

• Dates first, in year-month-day: 2026-09-03. It sorts chronologically by default in every system, and it is unambiguous internationally — 03-09-2026 means two different days depending on where the reader is.
• No spaces. Hyphens or underscores. Spaces break links, complicate scripts, and turn into %20 in URLs.
• No special characters. Slashes, colons and question marks are illegal or hazardous in some systems, and files travel between systems.
• Most general to most specific, left to right: date, project, document type, version. Sorting then groups things the way you look for them.
• No meaningless words. Final, new, latest and copy are true for about a day and misleading afterwards.
• Short but complete. Long paths plus long names still hit limits in some tools, and the fix is usually removing words that repeat the folder name.

A pattern that works

1. Pick the fields you actually need — usually date, project or client, document type, and version.
2. Fix the order and the separator, and write one line of example: 2026-09-03_acme_proposal_v2.
3. Use consistent abbreviations for recurring names, and write them down once. Inconsistent short forms are worse than long names.
4. Do not repeat the folder in the filename. If the folder is Acme, the file does not need acme unless it will travel.
5. Write the convention on one page and put it where documents are stored. A convention nobody can find is a convention nobody follows.
6. Apply it going forward. Renaming the archive is rarely worth it, and search covers the past adequately.

The date format is the rule that pays for itself immediately. Writing 2026-09-03 rather than 3 Sept 26 makes files sort chronologically in every file list without anybody doing anything, which is the whole point — a convention that requires effort at read time has not saved anything. It is also the standard order in ISO 8601, so it is the one format nobody misreads.

Where the convention stops helping

Names cannot carry metadata that changes. Status, owner and approval state belong in the system rather than in the filename, because renaming forty files when a status changes is not going to happen. That is the boundary between naming and records management proper — the point at which you need fields rather than characters, discussed in records management and, for controlled documents, document control system.

Naming solves half the problem; the other half is where the file goes. A shared drive structure organises by client, project or function rather than by team, because reorganisations happen and the work outlives the org chart.

Where it lives

Ettex Records holds the structured fields that a filename cannot — status, owner, review date — while the documents themselves sit in Ettex Docs with their versions tracked, covered in document version control.

Being direct: there is no bulk rename tool and no enforcement of naming rules. A convention is an agreement, and the only enforcement that works at small scale is that the person who breaks it cannot find their own file three months later.