Why names matter more than people think
A file name is seen every time you browse, search, attach or share a document. It is the first and sometimes only information you have about what a file contains. Names also decide how files are ordered in a list, and how reliably search finds them.
Yet many people name files in the moment: “report,” “report2,” “report final,” “report final REAL.” Each name made sense when it was typed. A few months later, none can be told apart without opening it. A consistent convention costs very little and prevents this.
What a good name does
A useful name satisfies three tests:
- It describes the contents well enough that you can recognize the file without opening it.
- It sorts sensibly in a plain alphabetical list.
- It is understandable to someone else, including you in a year.
Everything else is detail in service of those three goals.
Put dates in a sortable form
The most useful habit is writing dates in year-month-day order, such as 2026-11-01. Alphabetical sorting then matches chronological sorting, so a folder of files naturally lines up by date. Formats like 11-01-2026 or 1 Nov 2026 sort by month or day first, which scrambles the order across years.
Use leading zeros for months and days (03 rather than 3) so that 10 does not sort before 2. Use hyphens or no separators consistently. If you only need a year or a month, use just that: 2026 or 2026-11.
Decide what the date represents, and keep it the same way every time. It might be the date the document was created, the date it was sent, or the date of the event it describes. Tools often record a modified date automatically, but that changes whenever the file is touched, so a date in the name is more stable.
Use a predictable order of parts
Choose an order for the parts of a name, and stick to it. A common pattern is:
date, project or client, short description, version
For example (hypothetical): 2026-11-01_acme-website_project-brief_v02
What goes first controls how files group. If you lead with the date, files sort in time order. If you lead with the client, all of one client’s files cluster together. Pick the one that matches how you usually look for things. This is the same retrieval question discussed in the pillar guide on file organization.
Avoid including so many parts that names become unwieldy. Three or four elements are usually enough, because the folder already supplies context. If a file lives in a folder called “Acme Website,” repeating “acme-website” in every name may be redundant, although it helps when files are separated from their folders, for example when attached to an email.
Handle versions deliberately
Version control by file name is a common source of mess. Two practices help.
First, use a simple, ordered marker: v01, v02, v03. Numbers with leading zeros sort correctly up to 99. Avoid words like “final,” “latest” and “new,” which cannot sort and become false the moment another version appears. If you need to mark a state, use a short label such as “draft,” “review” or “approved” consistently, perhaps alongside the number.
Second, consider whether you need versions in the name at all. Many tools keep a version history automatically, which lets you restore an earlier state of a single file without keeping multiple copies. For documents that you edit alone and that stay in one tool, version history may be enough, and one file name stays stable. For documents that go out to others and come back, such as drafts for comment, numbered names make it clear which copy is which. The approach to review rounds is covered in document approval.
Mind the characters
Some characters cause trouble across systems. Different operating systems restrict certain characters, and spaces, accents or unusual symbols can break links, scripts or uploads in some tools. Safer habits include:
- Using letters, numbers, hyphens and underscores
- Avoiding slashes, colons, question marks and asterisks
- Keeping names reasonably short, since very long paths can cause problems in some environments
- Using lowercase or a single consistent capitalization style
Choose either hyphens or underscores as separators and use them the same way throughout. A common approach is underscores between parts and hyphens within a part.
Agree on it as a team
A personal convention is easy. A team convention requires agreement and a visible reference. Write the pattern on a short page, perhaps in the team wiki, with two or three examples. Keep it brief; a rule that takes a page to explain will not be followed.
Resist the urge to rename every old file. Apply the convention to new files and rename old ones only when you touch them. A bulk rename of a shared folder can break links from other documents and confuse people who know the old names.
Names and search
Consistent names make document search far more effective. If client names are spelled the same way every time, a search for the client returns everything. If one file says “Acme Inc” and another “ACME” and a third “acme-co,” search returns fragments. A short list of approved spellings for clients and projects is a small piece of discipline with a large payoff.
A quick checklist
Before saving a file, ask:
- Would I recognize this in a list a year from now?
- Does the date sort correctly?
- Could a colleague tell it apart from the other versions?
- Did I avoid “final,” “new” and “misc”?
If yes to each, the name is doing its job.