A file name is the first thing anyone sees when looking for a document. A good name tells you what the file contains, when it was created, and where it fits in a sequence — without opening it. A bad name tells you nothing, or worse, misleads you.
Why Naming Conventions Matter
When everyone on a team names files differently, the shared drive becomes a guessing game. One person saves "Budget.xlsx", another saves "2024 Budget Final v3 REVISED.xlsx", and a third saves "budget_jan_FINAL_USE THIS ONE.xlsx". All three might be the same file at different points in time — or they might be completely different documents. Nobody can tell without opening each one.
A naming convention is a shared agreement about how files will be named. It does not need to be elaborate. It needs to be consistent and understood by everyone who uses the system.
Elements of a Good File Name
Most useful file names include some combination of:
- Date. Using ISO 8601 format (YYYY-MM-DD) ensures files sort chronologically. For example: 2024-03-15. Avoid formats like "March 15" or "15-03-24" which sort unpredictably.
- Project or subject. A short identifier for the project, client, or topic. Keep it brief and consistent.
- Document type. What kind of document is it? Report, invoice, contract, minutes, proposal.
- Version identifier. If the document goes through revisions, include a version number: v1, v2, v3. Avoid "final", "final2", or "FINAL USE THIS".
Practical Naming Examples
A budget document for a 2024 community grant, version 2:
2024-CommunityGrant-Budget-v2.xlsx
Meeting minutes from March 15, 2024:
2024-03-15-BoardMeeting-Minutes.docx
A client contract for Acme Corp, signed version:
AcmeCorp-ServiceContract-2024-Signed.pdf
Characters to Avoid
Some characters cause problems across operating systems, file systems, and web servers:
- Spaces (use hyphens or underscores instead)
- Slashes (/ and \)
- Colons, asterisks, question marks, quotation marks, angle brackets, pipes
- Accented characters in file names intended for cross-platform use
Hyphens and underscores are both acceptable separators. Choose one and use it consistently.
There is no single correct naming convention. The right convention is the one your team agrees on and actually follows. What matters is consistency, not the specific format you choose. Document your convention and share it with everyone who saves files to the shared system.
Common Mistakes to Avoid
- Using "final" in a file name (there is always a "final2")
- Including your name in a shared file name (the file system already tracks who created it)
- Using dates in formats that do not sort correctly (Jan-2024, 15/03/24)
- Making names so long they get truncated in file explorers
- Using different conventions for different projects without documenting the difference
Key Takeaways
- A good file name tells you what the file contains without opening it
- Include date (YYYY-MM-DD), subject, document type, and version where relevant
- Avoid spaces and special characters that cause cross-platform problems
- The best convention is the one your team agrees on and consistently follows
Once you have a naming convention, learn how to track document versions in Version Control Basics.