What file naming conventions should we use to keep electronic records organized?
A good file naming convention is one of the simplest, lowest-cost ways to keep electronic records organized. The goal is not a single “perfect” name but a consistent, documented rule that everyone follows, so records remain easy to find, sort, and retain over time. Conventions work best when paired with broader practices for electronic records management.
Core principles
- Be consistent. Agree on one pattern and apply it everywhere. Consistency matters more than any particular style.
- Be descriptive but concise. A name should tell you what the record is without opening it, while staying short enough to remain manageable.
- Order elements from general to specific. Lead with the most stable, broadest element (such as project or record series) and move toward detail.
- Document the convention. Write it down, give examples, and make it part of onboarding so the rule outlives any individual.
Practical formatting rules
- Dates: Use a numeric, sortable format such as YYYY-MM-DD. This keeps files in chronological order automatically.
- Avoid spaces and special characters. Use hyphens or underscores instead of spaces, and avoid characters like / \ : * ? ” < > | that some systems reject.
- Use version indicators. Add a clear version element (for example, v01, v02, FINAL) rather than relying on “final-final” guesswork.
- Keep names reasonably short. Long paths plus long names can exceed system limits and break links.
- Use leading zeros for sequence numbers (001, 002) so they sort correctly.
A simple pattern might be: Project_RecordType_YYYY-MM-DD_v01.
Pair naming with metadata and folders
File names are only one layer of organization. Recordkeeping standards such as ISO 15489 emphasize that records should carry metadata describing their content, context, and structure. Don’t try to pack every attribute into the file name; let the name handle quick human recognition while metadata, folder structure, and your file plan carry classification, retention, and security information.
Sustain the convention
Conventions drift without maintenance. Review them periodically, retire elements that no longer make sense, and align naming with your retention schedule so records can be located when it’s time to keep, transfer, or dispose of them. Consistency applied over years is what turns a naming rule into reliable, findable records.
Sources & further reading
Authoritative government and non-profit references.
- ISO 15489-1 Records management — ISO
- Records management (NARA) — National Archives (NARA)
How to cite this page
APA
RM University Editorial. (2026). What file naming conventions should we use to keep electronic records organized?. Records Management University. https://www.recordsmgmt.org/questions/what-file-naming-conventions-for-electronic-records/
MLA
RM University Editorial. "What file naming conventions should we use to keep electronic records organized?." Records Management University, 16 June 2026, www.recordsmgmt.org/questions/what-file-naming-conventions-for-electronic-records/.
Related questions
- Are digital signatures legally valid on records?
- Are spreadsheets and database entries considered records I need to retain?
- Can a company be sanctioned for not preserving electronic records when it should have anticipated litigation?
- Can I just save a file as a PDF and call it a permanent electronic record?
- Can I store official records in the cloud?