File Naming, reloaded
What if a file name were not a stopgap but an address — findable, versioned, auditable? A single convention cuts search time per file by around 40% and clears up almost every “FINAL_FINAL” conflict; the migration effort stays at roughly one and a half person-days per team, with payback inside six months.
- Around 12% of files in the legacy estate follow no convention today — a manual sweep is still needed.
- Without training and a lead-by-example, shadow IT is a risk.
- SharePoint sync does not respect case — the convention has to be robust case-insensitively.
Why this matters now
We have crossed the line where file names stop serving the person and start blocking them. Cloud sync, AI search and compliance audits now treat the file name like an API — not like a sticky note.
The rules
YYYY-MM-DD at the front turns your file explorer into a timeline. ISO 8601 sorts alphabetically and chronologically at once — for free.
One word, not a sentence. The scheme decides the order, not the length.
_v01, _v02 — two digits, starting at 01. Saves you the sorting bugs that bite from v10 onwards.
Status tags like _DRAFT, _REVIEW, _FINAL only when the workflow forces it. Otherwise they just clutter the eye.
Lower-case the convention. Cloud storage sometimes ignores upper and lower case — and you should not have to know when.
Before / after
| Before | After |
|---|---|
| Quote Acme Ltd REVISED 2 (copy)_FINAL_now_really.docx | 2026-05-01_quote_acme_v03.docx |
Which scheme for which use case
- DIN 5008 (S1/S2): office, contracts, quotes, reporting.
- SemVer (S6): APIs, SDKs, software releases — MAJOR.MINOR.PATCH.
- ISO 8601 + time (S3): logs, capture streams, telemetry.
- GAMP 5 (S5): regulated systems (pharma, medical devices).
- Logseq convention (S11): personal knowledge vaults with Git.
- SemVer
- Semantic Versioning — MAJOR.MINOR.PATCH. MAJOR = breaking, MINOR = feature, PATCH = bugfix. The standard for APIs, because machines can reason about the order of the numbers.
# Example migration for a directory
for f in *.docx; do
mv "$f" "$(date -I)_${f// /_}"
doneThe human side
The most common cause of failure is not the wrong scheme but the missing example from the top. If the leadership team keeps sending “xyzFINAL.docx”, the team learns that the convention is optional.
A file-naming convention is 30% standard and 70% discipline.
Done in three weeks
- Week 1: decide the scheme (one workshop, 90 minutes).
- Week 2: pilot in a single team — old files live on, new ones follow the rule.
- Week 3: organisation-wide roll-out with a short cheat sheet (one PDF page).