File Naming, reloaded
Why a file-naming scheme makes your knowledge faster to find, safer and auditable
Transcript
What if a file name were not a stopgap but an address — findable, versioned, auditable? Over the next three minutes you will hear why a small naming scheme makes your knowledge faster to find, safer and easier to audit.
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 as an address for machines, not as a sticky note. That is precisely why a convention you can hit in your sleep is worth the effort.
The first rule matters most — the date up front. A “YYYY-MM-DD” at the start turns the file explorer into a timeline, because ISO 8601 sorts alphabetically just as it sorts chronologically, free of cost. After that comes a single keyword instead of a whole story, because the scheme decides the order, not the length of the name.
The version belongs in the name explicitly and in two digits — “_v01”, “_v02”, starting at zero one. That saves you the sorting bugs that bite from version ten onwards. Status marks such as draft or final go in only when the workflow truly forces them, and you keep the convention in lower case, because cloud storage tells upper and lower case apart one way today and another tomorrow.
Which scheme goes where? DIN 5008 for the office, contracts and quotations. SemVer for APIs and releases, in the form major dot minor dot patch. ISO 8601 with time for logs and telemetry. GAMP 5 for regulated systems in pharma and medical devices. One scheme per domain is enough — the craft is not the choice but the discipline behind it.
Because the commonest 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 naming convention is thirty per cent standard and seventy per cent attitude.
You can roll this out in three weeks — one week for the scheme, one for the pilot team, one for the roll-out with a one-page cheat-sheet. In the pilot, search time per file fell from twenty-three to six seconds, and nobody wished to go back. Give your knowledge a name you find again — your second brain holds the convention so you need not.
Why this topic, 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 start turns the file explorer into a timeline. ISO 8601 sorts alphabetically just as it sorts chronologically — free of cost.
One word, not a sentence. The scheme decides the order, not the length.
_v01, _v02 — two digits, starting at 01. Saves you sorting bugs from v10 onwards.
Status tags like _DRAFT, _REVIEW, _FINAL only when the workflow forces it. Otherwise it troubles the eye.
Keep the convention in lower case. Cloud storage sometimes does not tell upper and lower case apart — and you should not have to know.
Before / after
| Before | After |
|---|---|
| Quote Patel Industries REVISED 2 (Copy)_FINAL_now_really.docx | 2026-05-01_quote_patelindustries_v03.docx |
Which scheme for which use case
- DIN 5008 (S1/S2): office, contracts, quotations, reportings.
- 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 compute on the order of the numbers.
# Example migration for a directory
for f in *.docx; do
mv "$f" "$(date -I)_${f// /_}"
doneThe human side
The commonest 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 (1 workshop, 90 min).
- Week 2: pilot in one team — old files live on, new ones follow the rule.
- Week 3: company-wide roll-out with a short cheat-sheet (1 PDF page).
Bring your knowledge into shape.
Give your knowledge a name you find again. Your second brain holds the convention so you need not — a companion, not a filing cabinet.
Reserve your slot··free of cost →