Search is helpful until a file moves to another drive, another operating system, or a long-term archive. A useful filename should still identify the document without the folder around it.
A durable file name carries date, subject, and version without depending on one app’s search index. Use a stable pattern for repeated work: date when chronology matters, short subject, meaningful status, and a version only when you truly maintain versions.
Collect ten real files from the same workflow and identify what distinguishes them: date, client, project, document type, or approval state. Build the pattern from those differences.
Build one readable pattern
Use ISO-style dates such as 2026-07-11 when order matters. Use YYYY-MM-DD when chronological sorting matters because text sorting then matches date order. Skip the date for documents whose identity is not time-based.
Dates, subjects, and honest versions
Put the stable subject before temporary status words
Put the durable subject before temporary words such as draft or signed. Someone should understand the file without opening it or seeing its folder.
Use short version labels only when versions are real
Use v01 and v02 only for deliberately preserved versions. Replace “final-final” with a status that has a defined meaning, such as approved or filed.
Choose separators that work across operating systems
Avoid Windows-reserved characters and trailing periods. Hyphens, underscores, and spaces travel more reliably between Windows, macOS, cloud drives, and archives.
Create one written example for recurring documents
Create five realistic sample names and sort them on another device. Fix the pattern before renaming hundreds of existing files.
A folder of monthly statements might use 2026-07-bank-statement.pdf; a living policy might use security-policy-approved.pdf with version history handled by the document system. The pattern should match how the record changes.
Characters that break on another system
- Avoid characters that operating systems reserve.
- Avoid final-final-really-final naming.
- Do not encode sensitive personal data in a shareable filename.
Rework the convention when filenames are routinely truncated, sorting produces the wrong order, or collaborators keep creating alternate spellings.
Test the names outside their folder
Menus, limits, and recovery options change. Confirm the current steps in “Naming Files, Paths, and Namespaces” and “Best Practices for File Naming” before acting.
Microsoft reserves characters and device names that cannot be used normally in Windows filenames.
The Smithsonian’s digital-preservation guidance emphasizes durable formats and preservation planning for electronic records.
