Every shared folder I have ever inherited contains the same fossils: document(3).docx, FINAL_v2, New folder (copy). The files are not lost — they are unfindable, which in a busy week amounts to the same thing. File naming is the cheapest organisation system there is, and here is the version I install everywhere.
The pattern
YYYY-MM-DD – Name – Description
For example: 2026-06-15 – Dela Cruz – Service Agreement. Four things happen automatically with this pattern: files sort chronologically inside any folder, search finds them by person or by topic, two people never create the same name on the same day without noticing, and the name still makes sense when the file is emailed out of its folder — which is where most names fall apart.
The rules that make it work
- Dates first, always in ISO format.
2026-06-15, never15-6or "June version." - No status words in names. Final, latest, new, updated — they expire. Versions belong in version history or a
v1,v2suffix while drafting. - Short descriptions, real words. Abbreviations only the whole team shares. Your future self is also a team member.
- Same pattern for photos and downloads. Camera names like
IMG_4021get renamed on arrival, in batch, before they breed.
Rolling it out without pain
We never rename an entire archive in a day. The rule applies to everything new from Monday; the current project's active files get renamed in one short session; history keeps its names inside an Archive folder. Within a month, the files anyone actually touches all follow the system — and nobody misses the old way.
Naming is a small rule with an outsized effect: it is the difference between a folder you browse and a folder you search. It is one of the first systems I set up in any organisation project.