File Naming Conventions
Find project documents without opening every file. Read a concrete example, examine the trade-offs, and try a small exercise to see whether the principle applies to your situation.
The working principle
- Start here. Use a stable structure such as YYYY-MM-DD_project_topic_v01.
- Add context. Avoid characters that cause cross-platform filename problems.
- Keep in mind. Separate working drafts from the approved final version.
A workplace example
“2026-10-09_project-budget_v02.xlsx” sorts by date and conveys purpose and version better than “final2_NEW.xlsx.” A shared naming convention is especially helpful when dozens of files circulate by email.
Good filenames make retrieval predictable without relying on the memory of the person who created them.
Common failure points
Filename rules differ across systems; slashes, trailing dots and unusually long paths can cause trouble. Including private client details in filenames can expose information.
Put it into practice
Pick a pattern of date, project, description and version. Rename five recent files consistently and test that they sort and search well.
Further reading and verification
Read the linked reference for additional background on work & productivity. Review the applicable rules and update dates before using any example in a consequential decision.
Related BlogJD guides
Published October 9, 2026 · BlogJD Editorial Desk · How we prepare and correct content · Report a correction.