Best File Naming Conventions for Digital Archives

A file naming convention is one of the simplest things you can implement and one of the most impactful. Good naming means anyone can find, identify and understand a document without opening it. Bad naming — or no convention at all — means an archive full of files called Scan001.pdf, Document_final_v3_REVISED.pdf and things nobody can decipher six months later.

Core Principles

Be Consistent

The single most important principle. A mediocre convention applied consistently is far more useful than a perfect convention applied sporadically. Choose a pattern and enforce it across the entire archive. Document it, train staff on it, and correct deviations when you find them.

Be Descriptive

A file name should tell you what the document is without opening it. Include enough information to identify the document — typically the date, document type, and a key reference or description.

Put the Date First

Starting file names with the date in YYYY-MM-DD format means files automatically sort in chronological order in any file manager or system. This is the single most useful naming decision for archives.

• Correct: 2024-03-15 (ISO 8601 format — sorts correctly everywhere)
• Wrong: 15-03-2024 (DD-MM-YYYY — sorts by day, not chronologically)
• Wrong: 03-15-2024 (US format — confusing in UK context and sorts by month)
• Wrong: March 15 2024 (text month — does not sort correctly)

Avoid Special Characters

Restrict file names to letters, numbers, hyphens and underscores. Avoid:

• Spaces (use hyphens or underscores instead) — spaces cause problems in URLs, command-line tools and some systems
• Ampersands (&), percentage signs (%), hash symbols (#), question marks (?)
• Slashes (/ or \) — these are directory separators and will break file paths
• Apostrophes and quotation marks
• Accented characters (e, u, a) — these can cause encoding issues across systems

Recommended Pattern

A versatile pattern that works for most business archives:

YYYY-MM-DD_Type_Reference_Description.pdf

Where:

• YYYY-MM-DD: Document date (not scan date)
• Type: Short document type label (Invoice, Contract, Letter, Report, Minutes, Policy)
• Reference: The unique identifier for this document (invoice number, contract reference, matter number)
• Description: Brief additional context if needed

Examples by Document Type

Invoices

• 2024-03-15_Invoice_INV-4521_Acme-Supplies.pdf
• 2024-03-18_Invoice_INV-4522_JB-Electrical.pdf
• 2024-04-01_Credit-Note_CN-891_Acme-Supplies.pdf

Contracts

• 2024-01-10_Contract_C-2024-015_Office-Lease-Renewal.pdf
• 2024-02-28_Contract_C-2024-023_IT-Support-Agreement.pdf
• 2023-11-15_NDA_NDA-2023-042_Project-Phoenix.pdf

Personnel Records

• 2024-03-01_Offer-Letter_EMP-1247_Jane-Smith.pdf
• 2024-03-15_Contract_EMP-1247_Jane-Smith.pdf
• 2024-06-01_Performance-Review_EMP-1247_Jane-Smith.pdf

Correspondence

• 2024-03-15_Letter_REF-2024-089_Planning-Application-Response.pdf
• 2024-03-20_Email_REF-2024-089_Council-Follow-Up.pdf

Meeting Minutes

• 2024-03-05_Minutes_Board-Meeting.pdf
• 2024-03-12_Minutes_Finance-Committee.pdf
• 2024-04-02_Minutes_Board-Meeting.pdf

Versioning

For documents that go through revisions (contracts, policies, reports), include a version indicator:

• Simple approach: Append _v1, _v2, _v3 to the file name — 2024-03-15_Policy_Health-and-Safety_v2.pdf
• Draft/Final approach: Append _DRAFT or _FINAL — 2024-03-15_Report_Annual-Accounts_FINAL.pdf
• DMS approach: If using a document management system, let the system handle versioning automatically and keep file names version-free

Never use vague version labels like _final_v2, _FINAL_REVISED, _latest or _new. These proliferate and rapidly become meaningless. If a document is revised after being marked FINAL, increment the version number — _v3, not _FINAL2.

Common Mistakes

• Using scan dates instead of document dates: The date in the file name should be the date of the document (when the invoice was issued, when the letter was written), not the date it was scanned. Scan date is metadata, not part of the name
• Excessively long names: Keep file names under 80 characters where possible. Very long names get truncated in file managers and cause problems with file path length limits (260 characters on some Windows systems)
• Abbreviations nobody understands: INV for Invoice is fine — everyone knows it. PRRQ for Purchase Requisition is not — use Purchase-Req or the full word
• Inconsistent separators: Pick either hyphens or underscores and use them consistently. Do not mix them randomly within the same archive
• Including information already in the folder path: If the file is in Finance/Invoices/2024/, the file name does not need to repeat “Finance” or “2024” — that is redundant

Implementing a Convention

Practical steps to roll out a naming convention:

• Document the convention in a short, clear guide (one page maximum)
• Share examples for each common document type — real examples are more useful than abstract rules
• Configure scanners to prompt for or auto-generate compliant file names where possible
• Rename existing files gradually — start with the most-accessed records and work backwards
• Review compliance periodically — spot-check a sample of recent files to ensure the convention is being followed

Get a Free Quote

Every project is different, so the best way to understand your options is to get in touch with our team. We provide clear, no-obligation advice — usually within the same day.

Call us on 01691 650355 or use the form below.