File names are the cheapest piece of documentation you will ever write. A good name tells you what a file is, which project it belongs to, when it is from, and what state it is in, without opening it. A bad name such as "Proposal final FINAL v3 (revised).docx" tells you almost nothing and invites mistakes. This guide offers a simple, adaptable convention and explains the reasoning behind each choice so you can tailor it to your team.
What a good file name does
- Sorts naturally in a file browser, so related files appear together.
- Identifies content without opening the file.
- Survives sharing across operating systems, sync tools, and email.
- Signals status only when status is not tracked elsewhere.
A template you can adopt today
A widely used pattern puts the most stable information first and the most changeable last:
YYYY-MM-DD_Project_DocumentType_Descriptor_v01.extExamples:
2026-10-09_Harbor-Dental_Proposal_Website-Refresh_v02.docx2026-09-30_Finance_Expense-Report_Q3.xlsx2026-10-01_Team_Meeting-Notes_Weekly-Planning.docx
Why dates in year-month-day order?
The format YYYY-MM-DD sorts chronologically when sorted alphabetically. Formats like 10-09-2026 sort by month first and scramble years. Pick one format and apply it everywhere.
Why hyphens and underscores?
Spaces can be converted to %20 in web links, which makes links harder to read. Using underscores to separate fields and hyphens to separate words inside a field is a simple, readable convention. Camel case is also fine if your team prefers it; consistency is the goal.
Characters to avoid
Avoid characters that some systems treat specially: \ / : * ? " < > |, as well as leading or trailing spaces and periods. Keep full paths reasonably short, since very long paths cause sync problems on some systems.
Handling versions
If your tool has built-in version history, do not put versions in file names for documents that are edited in place. Let the tool track them (see Version History and File Recovery). Use version numbers only when you must distribute distinct snapshots, such as sending a contract draft to an outside party.
When you do, use zero-padded numbers (v01, v02, ... v10) so they sort correctly. Avoid words like "final," "latest," and "new." They stop being true within a day. Instead, use a status label in a controlled list: DRAFT, REVIEW, APPROVED, SENT.
Step-by-step: introducing a convention without a revolt
- Collect pain points. Ask the team which searches fail most often. Use real examples.
- Draft a one-page rule. Include the template, three examples, and the list of allowed status labels.
- Pilot with one project for a few weeks and note what is awkward.
- Revise, then publish the rule in your shared resources folder.
- Apply it going forward. Renaming the entire archive is rarely worth the effort; rename files when you next touch them.
Examples: before and after
| Before | After |
|---|---|
| invoice new.pdf | 2026-10-02_Acme-Supply_Invoice_INV-1048.pdf |
| Meeting notes Tuesday.docx | 2026-10-06_Team_Meeting-Notes_Weekly-Planning.docx |
| Budget v3 FINAL revised.xlsx | 2026-10-01_Finance_Budget_FY2027_v03_REVIEW.xlsx |
Advantages and limitations
Advantages
- Faster searching and sorting.
- Fewer accidental uses of outdated files.
- Works with any storage tool, because it needs no features.
Limitations
- Depends on people following it; it is not enforced by software.
- Long names can be truncated in narrow views.
- Over-detailed conventions get ignored, so keep it short.
Conclusion
Pick a pattern, write it on one page, and apply it from today forward. Combined with a predictable folder structure, consistent names make your files findable by anyone on the team, now and in the future.
Independent and educational. This article is general information, not professional, legal, or technical-support advice. Workplace Productivity Hub is not affiliated with any software vendor. Features, menu names, and limits vary by product and plan and change over time, so confirm details in your own tools' official documentation. See our editorial standards and corrections policy.