Law Firm File Naming Convention: Template, Worked Examples, and DocType Codes

A consistent law firm file naming convention is the single highest leverage workflow change a small firm can make in a weekend. It cuts time hunting for documents, prevents the embarrassing moment of attaching the wrong draft to opposing counsel, makes Bates production cleaner, and turns any shared drive into something a new paralegal can navigate on day one. This article gives you one opinionated, copy paste ready convention, worked examples for every common practice area, a controlled vocabulary of DocType codes, and a plan for rolling it out across an existing matter folder that is already messy.

The convention is Mac and Windows safe, Clio and SharePoint friendly, and sortable by date in any file explorer. If you have a clean slate, adopt it as is. If you have ten years of inherited files, jump to the Rolling It Out section.

For day to day matter documents, use this exact template:

YYYY-MM-DD_ClientLastName_MatterShortName_DocType_v##.ext

Worked example for a motion to dismiss in the Henderson v Acme matter, drafted on March 4, 2026, second revision:

2026-03-04_Henderson_AcmeBreach_PLD-MTD_v02.docx

This single pattern handles 90 percent of what flows across a paralegal's desk. The remaining 10 percent (Bates produced documents, sealed matters, multi client matters, exhibits with sub indices) gets covered in the sections below. Use this matter centric folder structure guide alongside it so filenames and folders reinforce each other.

The order is not arbitrary. Each component sits where it sits because of how operating systems sort, how humans scan, and how cloud sync tools handle conflicts.

• YYYY-MM-DD first. ISO 8601 dates sort chronologically as plain text. No file explorer needs a special view. Put the date last and your folder becomes alphabetical chaos.
• ClientLastName second. When several matters share a folder or when a paralegal greps across a drive, the client surname is the strongest mental anchor.
• MatterShortName third. A short, PascalCase token (e.g. AcmeBreach, EstateAdmin, GreenCardI130) keeps the filename readable and disambiguates clients with multiple active matters.
• DocType fourth. A three to seven character code from the controlled vocabulary below. Putting it after the matter means filtering by DocType still works inside a single matter folder.
• Version suffix last. _v01, _v02, _vFINAL only when the document is genuinely final. Version is the most volatile component, so it goes at the end where edits are least disruptive.

If a partner walks up and asks the question conversationally, the honest answer is: any consistent convention beats no convention, but the strongest legal document naming convention for a small or mid sized firm is a date prefixed, underscore delimited, PascalCase pattern with a controlled DocType vocabulary. That is what the template above gives you. It works because:

1. It sorts correctly in Finder, Explorer, OneDrive, Dropbox, Google Drive, NetDocuments, iManage, and Clio Documents without any custom view.
2. It survives copy paste into email subject lines and Bates stamps.
3. It is parseable by scripts and AI tools, which matters when you eventually want to auto file by DocType.
4. It tells you who, what, and when in one glance, without opening the document.

Avoid spaces, slashes, colons, and trailing periods. Avoid client first names (privacy and ambiguity). Avoid initials only for DocType (PLD is unambiguous, MTD alone is not).

YYYY-MM-DD: the document's effective date

This is the date the document was signed, filed, served, or dated on its face, not the date you saved the file. A contract dated June 1 that you scan and save on June 5 is still 2026-06-01. If a document is undated (a draft circulating internally), use the date of the working session that produced this version. Get this wrong and your chronological view of the matter becomes a fiction.

ClientLastName: dealing with collisions

When two clients share a surname (very common in immigration and estates practices), append a single initial: Patel-A and Patel-R. Do not use a number suffix because numbers create false ordering. For corporate clients, use a short trademarked name without Inc, LLC, or LP: Acme not AcmeIncorporated.

MatterShortName: disambiguating multiple matters

One client, several matters, one short name per matter. Pick a name from the underlying claim or transaction, not from the file number: AcmeBreach (better than AcmeMatter01), EstateAdmin (better than Smith2026), GreenCardI130. Use PascalCase. Keep it under 20 characters.

Sealed, anonymized, and confidential matters

If the client name itself is sealed or anonymized, replace ClientLastName with the case number: 2026-03-04_24CV01234_Doe_PLD-MTD_v02.docx. Internal drafts on highly sensitive matters can use a project code that maps back to the client only through a key kept off the shared drive.

The DocType code is the single most powerful component because it lets you slice the matter folder by document type in seconds. Pick from this controlled list. Resist the urge to invent new codes. If you need a new one, add it to the firm wide list rather than letting individual users freelance.

The table below shows the convention in action across the most common practice areas. Use it as a quick reference when staff ask how to name a specific document. Each filename obeys the same template, which means anyone trained on one practice area can read filenames from any other practice area in the firm.

Two things break naive conventions: Bates production and revision history. Handle both with explicit suffixes so nothing is ambiguous when opposing counsel asks for a specific page range.

Bates ranges in filenames

When a file is part of a Bates produced set, append the Bates range using a _BATES_ token before the version suffix:

2026-03-30_Henderson_AcmeBreach_DISC-RESP_BATES_00001-00450_v01.pdf

Keep the range zero padded to the width you have agreed to with opposing counsel (typically five or six digits). If a single PDF contains discontinuous Bates ranges, prefer splitting it. If you cannot split it, use a hyphenated list: BATES_00001-00120_00500-00525.

Version control with _v##

Use _v01, _v02, _v03 in zero padded sequence. Reserve _vFINAL only for the version that is signed, filed, or executed. Never have two files marked vFINAL in the same folder. If a final document is later superseded, rename the old one to _vFINAL-Superseded-YYYY-MM-DD and create the new _vFINAL. The date prefix is the document's effective date, not the file save date. That separation is what lets you sort the folder chronologically by what the document actually represents.

Redlines and clean copies

Add a qualifier to the DocType: _COMPARE for a redline against the prior version, _CLEAN for a clean accepted copy. Example: 2026-03-04_Henderson_AcmeBreach_AGR-Settlement_COMPARE_v02.docx.

Most failed conventions die the same way. Watch for these:

• Spaces in filenames. Use underscores. Spaces survive most modern tools but they still break command line scripts, some legacy DMS imports, and URL encoded shared links.
• Inconsistent capitalization. Use PascalCase for every component (ClientLastName, MatterShortName, DocType). Mixing camelCase and lowercase is the fastest way to lose trust in the convention.
• Special characters. Avoid the Windows reserved set: colon, slash, backslash, asterisk, question mark, double quote, pipe, less than, greater than. These either break sync or get silently sanitized by Dropbox, OneDrive, and SharePoint. A filename that opens locally but fails to sync is the worst kind of bug.
• Filenames over 200 characters. Windows has a 260 character path limit by default. Cloud sync tools cap individual filenames at 255 characters. Stay under 200 characters for the filename itself to leave headroom for the folder path.
• Client first names. Privacy risk if the file is ever shared externally, and ambiguous when you have several Davids on your roster.
• Letting DocType drift. One person types MTD, another types MtnDismiss, another types Motion. Pick one (PLD-MTD) and put the controlled vocabulary on the wall.
• Dates at the end. A common mistake from generic attorney file naming best practices guides. Dates at the end mean files sort alphabetically by document type, which is rarely what you want inside a single matter folder.
• Embedding the file number from your billing system. The file number changes when matters are reorganized. The convention should survive a billing migration.

A clean convention on new matters is easy. The hard part is the ten years of inherited files in a shared drive that nobody wants to touch. Three approaches, in order of speed:

Manual batch renaming

For small folders (under 100 files), use the native tools. Finder on macOS supports multi select rename with Find and Replace, sequential numbering, and date insertion. On Windows, PowerToys PowerRename is the free, search and replace, regex aware equivalent. Both are fine for a single matter folder where you can see what you are doing.

Scripted rename

For drives with thousands of files where you can identify a stable pattern in the existing names (say, everything starts with the matter number), a short PowerShell or Python script can do it in minutes. The risk is that legacy filenames rarely follow any pattern at all, so the script ends up needing manual review.

AI assisted rename

For the more common case (legacy drives where filenames are a free for all of initials, dates in three different formats, and project codenames nobody remembers), an AI assisted rename tool can read the document content, infer the date, client, matter, and DocType, and propose a new name. Sortio's Rule Builder is built for exactly this case on Mac and Windows and runs locally so privileged content never leaves the machine. See the Rule Builder for law firms walkthrough for a step by step.

Whichever route you pick, do not rename in place on the live shared drive. Copy to a staging folder, rename there, sanity check a sample, then swap. Cloud sync conflicts during a mass rename are how firms lose work.

What's the best filename format for a law firm?

YYYY-MM-DD_ClientLastName_MatterShortName_DocType_v##.ext. Date first so the folder sorts chronologically, client surname for human recall, matter short name for disambiguation, DocType from a controlled vocabulary, version at the end where edits are least disruptive. Use underscores, PascalCase, and no special characters.

Should I put dates first or last in a filename?

First, in ISO 8601 format (YYYY-MM-DD). Date last means your folder sorts alphabetically by document type, which is rarely what you want. Date first in ISO format sorts chronologically as plain text in every file explorer, no special view required.

How do I handle versioning in legal file names?

Use a zero padded _v01, _v02, _v03 suffix at the very end of the filename, before the extension. Reserve _vFINAL for the executed or filed version. Never have two _vFINAL files in the same folder. If a final document is superseded, rename the old one with a _vFINAL-Superseded-YYYY-MM-DD qualifier and create the new _vFINAL.

Can I rename hundreds of files at once?

Yes. For under 100 files, use Finder rename on macOS or PowerToys PowerRename on Windows. For thousands of files with no consistent pattern, an AI assisted tool that reads document content (such as Sortio's Rule Builder) is faster and more accurate than a script because it can infer date, client, and DocType from the file itself rather than from a brittle filename pattern.

Do file names need to match Clio matter names?

They should be compatible but they do not need to be identical. Clio matter names tend to be verbose (Henderson, Robert v Acme Corporation, Inc.) while filename MatterShortName tokens should be tight (AcmeBreach). Keep a one to one mapping in your firm's matter intake checklist so the short name and the Clio matter are obviously the same thing.

Pick one practice area, one paralegal, and one week. Print the template, the DocType table, and the worked examples. Apply the convention to every new file created that week. Friday afternoon, review the matter folder with the paralegal and tighten anything that felt awkward. The following week, expand to the rest of the team. Conventions stick when one person practices them in a real matter and shows the rest of the firm what the folder looks like at the end of the week.

If you have inherited thousands of files that do not follow this convention, Sortio's Rule Builder can rename them in bulk on your Mac or Windows machine, then route them into matter centric folders that reinforce the same structure. It runs locally, so privileged content stays on the device. For a deeper look at how the same naming logic translates into folder structure, see this paralegal document management checklist.