File names that make shared documents easier to understand

A filename is the only part of a document that everybody sees and nobody edits. It shows up in email lists, upload confirmations, shared folders, and the download folder of a person who will never open your carefully structured system, and it survives every conversion. Naming badly is not untidy, it is a transfer of work to the recipient, and the fix is a scheme you apply without thinking about it.

Three components in a fixed order

Date, then what it is, then which one. The date goes first in year-month-day order because that is the only format that sorts chronologically when a folder is sorted by name, which is what happens by default in most listings and in most email clients. Written the other way around, a folder of a hundred files orders itself by day of the month, which is worse than random.

The middle component is the document type in the words the recipient uses: invoice, contract, transcript, proof-of-address. The last identifies the instance: the client, the property, the month, the project. Fix the order and never vary it, because the value of the scheme comes from every file in a listing lining up the same way, and one file with the pieces reversed breaks the visual scan for the whole folder.

Characters, and what other systems will do to them

Use hyphens between words and underscores between the three components if you want the boundaries visible. Avoid spaces, which get rewritten in links and can break scripts on the receiving end. Avoid slashes and colons, which are reserved on at least one major operating system and will be silently replaced. Avoid characters outside the basic set for anything going to a public form, since some upload handlers mangle them and you will not find out until the file has been rejected.

Keep the whole thing shorter than you think you need, roughly under sixty characters. Long names get truncated in the middle of a listing, and the part that disappears is usually the end, which is where you put the identifying piece. Test your scheme by looking at a folder of ten files in a narrow window and checking that you can still tell them apart.

Versions, and why final is the wrong word

If a document will be revised, number the versions with padded digits so that v02 sorts before v10, and increment on every version that left your machine. A name containing final is a claim that will be falsified, usually twice, and the sequence that follows is the familiar one where nobody can tell which file is authoritative and the newest timestamp belongs to a copy somebody opened by accident.

Decide whether the date in the name is the date of the document or the date of the version, and be consistent, because mixing them is what produces two files that appear to be the same thing on different days. For a document with legal or invoice significance, the document date belongs in the name and the version number carries the revision. For a working draft, the version date is more useful.

Adapt the name to the destination

When a file is going into a specific upload field, echo the field label in the name. A reviewer working through a submission is matching your files against the list of things they asked for, and a name that uses their wording is checked in a second while a name using your internal terminology has to be opened. This single adjustment removes a surprising share of resubmission requests.

When sending several files at once, rename them as a set so they read as a set: the same date, the same type wording, differing only in the identifying part. And take the internal wording out before anything leaves the building. Draft, do-not-send, and the name of a person or a competitor in a filename are read by everyone in the thread, and the filename is the one thing nobody remembers to check before pressing send.

Before you commit

• Put date and purpose first
• Avoid vague final-final names
• Match names to the upload field

Three components in a fixed order, safe characters, a real version number instead of the word final, and a name that echoes the destination. Applied consistently it takes no extra time, and it removes the recipient-side work of opening four files to find out which one you meant.