Legal File Naming Conventions: Matter-Based Examples (2026)

Quick answer: name legal documents Matter – YYYY-MM-DD – DocumentType – Party – Version.pdf, for example 2026-0142 – 2026-06-11 – NDA – Vertex GmbH – v03.pdf. The matter number scopes every file to its engagement, the ISO date builds a chronological record, the document type and party make the folder scannable, and an explicit version number ends the final_FINAL_v2 problem. Zush reads each document and applies the convention automatically.

Legal work generates the worst-named files of any profession: filings arrive from courts as case-number strings, opposing counsel sends Agreement (clean).docx, clients forward scan.pdf, and internally every draft tends toward final. Unlike most professions, lawyers also pay for the mess twice — once in lost time, and again when a matter is handed to a colleague, audited, or subpoenaed, and the file record has to speak for itself.

This is the convention layer. For the mechanics of bulk-applying it, see renaming PDF files automatically and the scanned documents guide.

The components, and why this order

Matter number first

The matter (or case, or client-matter) number is the organizing unit of legal work, so it leads the filename: 2026-0142 – … groups every document of an engagement in any sorted listing, even when files escape their folder — which email attachments and desktop copies always do. Use exactly the format from your practice management system.

Solo practitioners without formal matter numbers should still adopt one — ClientCode-Year-Seq takes a minute to define and pays off at the first conflict check.

Date second — the date of the document

YYYY-MM-DD, using the document’s own date: the date a contract was executed, a filing was stamped, a letter was sent. This turns each matter’s file listing into a chronology of the engagement — effectively a free case timeline. Received-date or scanned-date belongs in metadata, not the name.

Document type third, from a fixed vocabulary

Complaint, Answer, Motion, Order, NDA, MSA, Engagement Letter, Correspondence, Memo, Exhibit. Fifteen to twenty consistent labels cover most practices. The discipline point is singular: one label per concept — not Agreement in June and Contract in July.

Party fourth

The counterparty, court, or witness the document concerns: – Vertex GmbH, – SDNY, – Chen Deposition. Within a matter folder this is what the eye scans for. Standardize spellings, and keep client-confidential specifics out of names that travel — the same filename-leakage logic as medical records: filenames show up in email previews, sync logs, and shared listings before anyone opens a file.

Version last — numbers, never “final”

v01, v02, v03 (executed). Zero-padded so v10 sorts after v09. The executed or as-filed copy gets a terminal marker instead of a higher number, because “final” as a label is a lie the first time a judge requests changes, but “executed” is a fact. Drafts and the executed copy then sort adjacently and unambiguously:

2026-0142 – 2026-06-11 – NDA – Vertex GmbH – v01.pdf
2026-0142 – 2026-06-11 – NDA – Vertex GmbH – v02.pdf
2026-0142 – 2026-06-14 – NDA – Vertex GmbH – executed.pdf

What stays out of the filename

• Privileged descriptions. – re settlement strategy in a filename discloses work product to anyone who sees a directory listing or attachment line. Type-and-party is enough; the substance lives inside the file.
• Bates numbers. Discovery productions have their own numbering regime; keep production naming (ABC000001–ABC000450) in the production set, separate from the working-file convention.
• Redundant client names — when the folder is already Clients/Vertex/, the matter number carries the link; repeating the client in every filename just consumes length budget.

Incoming chaos: courts, counsel, and scanners

The convention is easy to keep for documents you create and hard for documents that arrive: e-filing confirmations named by case-number hash, Document(1).pdf from opposing counsel, and the office scanner’s Scan_0042.pdf for everything on paper.

This intake pile is where automation changes the economics. Zush reads each incoming file — scans via AI vision, no OCR pass needed — and proposes names in your convention. Two features map directly onto legal intake:

• Custom AI Blocks: describe an extraction in plain language — “the matter number, formatted YYYY-NNNN”, “the filing type as stamped”, “the counterparty” — and it becomes a reusable block in the naming pattern.
• Folder monitoring: a Template watching the scan folder or the e-filing download folder renames arrivals continuously, with every name previewed in a batch you approve and can undo.

For confidentiality postures: Zush’s Offline AI mode analyzes supported files with local models on Mac or Windows, so client documents never leave the machine; BYOK routes analysis through your firm’s own AI provider account. The privacy docs state exactly what each mode transmits.

A worked matter folder

2026-0142 Vertex – Services Dispute/
  2026-0142 – 2026-03-02 – Engagement Letter – Vertex GmbH – executed.pdf
  2026-0142 – 2026-04-18 – Demand Letter – Meridian LLC – v02.pdf
  2026-0142 – 2026-05-06 – Complaint – SDNY – as-filed.pdf
  2026-0142 – 2026-05-29 – Answer – Meridian LLC – as-filed.pdf
  2026-0142 – 2026-06-11 – Settlement Agreement – Meridian LLC – v04.pdf
  2026-0142 – 2026-06-12 – Correspondence – Opposing Counsel.pdf

Sorted by name, the folder is the case chronology — no index document to maintain, no practice-management lookup to find the answer’s filing date.

FAQ

What is the standard naming convention for legal documents?

There is no single bar-mandated standard, but the pattern that recurs across firm style guides is matter number, ISO date, document type, party, and version: 2026-0142 – 2026-06-11 – NDA – Vertex GmbH – v03.pdf. It scopes files to engagements and reads as a chronology.

How should law firms handle document versions in filenames?

Zero-padded version numbers (v01…v12) for drafts, and a factual terminal marker — executed, as-filed — instead of “final”. Labels like final_v2 fail precisely when accuracy matters most.

Can AI apply a naming convention to old case files?

Yes. A content-aware renamer reads each document, extracts the matter number, date, type, and parties, and applies the convention in a reviewed batch — including scanned filings via AI vision. A closed-matter archive becomes a one-pass cleanup instead of a paralegal-week.

Is it safe to use AI renaming on confidential client documents?

Use a mode that matches your confidentiality posture. Zush’s Offline AI runs local models so files never leave the machine; BYOK uses your firm’s own API account and terms. Upload-based web renamers put client documents on third-party servers and are the option to avoid.

Should the client name appear in every filename?

Only when files travel outside a client-scoped folder. Inside Clients/Vertex/, the matter number already links each file to the client; adding the name spends filename length without adding information.