Most firms have a naming convention written down somewhere. Most firms' shared drives still look like Scan0043.pdf and contract_final_v2.pdf, because a convention only works when everyone applies it identically, and under deadline pressure nobody does. This guide covers what a good legal document naming convention contains, a pattern you can adopt, and the honest split on enforcement: relying on people, or letting a tool read each document and apply the convention for you.
Designing the convention is the easy part. Making every file follow it is where firms fail. These are the two paths.
| Manual enforcement | Automated (content-based) | |
|---|---|---|
| Who applies the convention | Every person, every file | The AI reads and names each file |
| Consistency | Drifts as staff and pressure vary | Uniform regardless of who files |
| Works on scanned intake | Only if someone reads and types it | Yes, via OCR |
| Effort | Ongoing, per document | Set the template once, review batches |
| Failure mode | Skipped under deadline | Low-confidence files flagged, not skipped |
A filename is useful when it identifies the document without opening it. For legal documents, that means four things carried in a consistent order: the client or parties, the matter, the document type, and the date. Add a status where it matters (Draft, Signed, Filed) and you've eliminated the two biggest sources of confusion, which version is authoritative and which matter a document belongs to.
A pattern that works for most firms, and reads cleanly in a document list, is date-first: {date}_{parties}_{doctype}_{status}. That produces 2025-03-02_Smith-v-Jones_MotionToDismiss_Filed.pdf, which sorts chronologically, groups a matter together when parties lead, and states plainly what the document is. Firms that keep a folder per client and matter often prefer {client}/{matter}/{date}_{doctype} so the folder carries the client and matter and the filename stays short.
Whichever you pick, write down the field order, the date format, the separators, and the abbreviations for common document types, and keep that one page as the reference. The convention itself is simple; the hard part is next.
A convention is a rule people have to follow. Across a firm, they don't follow it identically: one person abbreviates the client differently, another flips the date, a paralegal under a filing deadline skips naming entirely and drops in Scan0043.pdf to deal with later, which never comes. Within a month the drive is inconsistent again, and the convention on paper no longer matches the folder in practice.
The only durable fix is to remove the human step. If a tool reads each document and applies the convention automatically, consistency stops depending on discipline, and the convention holds whether the person filing is a partner or a first-week temp.
The documents hardest to keep to a convention are the scanned and photographed ones, because there's nothing in the filename to work from and someone has to read the page to name it. That's exactly the case where manual enforcement collapses and a content-based tool earns its place.
Renamer.ai runs OCR to read scanned and photographed legal documents, then applies your convention from what it read, so a scanned court order or a photographed signed agreement gets the same structured name as a digital PDF. Legibility matters, a clean scan reads reliably, a poor photo may be flagged for a manual check, so the convention holds without silently misnaming a file it couldn't read.
For a large historical batch, review the first 15 to 20 names to confirm the convention is being applied the way you intended before approving the rest. Once you've confirmed the pattern holds on your own documents, the rest of the batch, and every document after it, follows the same convention with no further effort, which is the outcome a written standard alone never quite reaches.
A few recurring choices quietly break an otherwise sensible convention. The first is a date format that doesn't sort: writing 03-02-2025 or Mar-2-2025 means a folder never lines up chronologically, so the one thing a date is for, ordering, is lost. Use YYYY-MM-DD and every file browser sorts the matter correctly with no extra effort.
The second is inconsistent party and client names: Smith v Jones in one file, SmithJones in another, S-v-J in a third. To a human they're the same matter; to search and sorting they're three different things. A convention has to fix not just the fields but their exact spelling, which is precisely the kind of consistency a person can't maintain by hand but a content-based tool applies automatically every time.
The third is overloading the filename with everything. A name that tries to carry the parties, matter, type, date, status, author, and a description becomes too long to read and too fiddly to apply, so people abandon it. Keep the filename to the four or five fields that identify the document, and let folders carry the rest. A convention people can actually follow beats a perfect one they quietly ignore, and a convention a tool applies for them beats both.
The value of a naming convention is retrieval: any staffer can find any document by its name, and the authoritative version is never in doubt. That value only exists if the convention is actually applied to every file, which is why enforcement, not design, is where firms should spend their attention.
Automating the application also makes the convention portable: because the names live in the documents, the benefit travels even if the firm changes its storage software. It also makes the convention teachable in one sentence, drop files here and the tool names them, instead of a training document nobody reads, which is often the difference between a convention that's adopted and one that stays on paper. For the wider view of legal document organization, start at the legal document management hub.
Enough to identify the document without opening it: the date (in a sortable format), the client or parties, the matter, the document type, and a status where it matters (Draft, Signed, Filed). A pattern like 2025-03-02_Smith-v-Jones_MotionToDismiss_Filed.pdf covers all of it.
Because they rely on every person applying them identically, and under deadline pressure that breaks down, abbreviations differ, dates flip, and naming gets skipped entirely. The durable fix is to have a tool read each document and apply the convention automatically.
Yes. A content-based tool uses OCR to read scanned and photographed documents, then names them to your convention, which is the case manual enforcement handles worst.
Yes. You define the template, field order, date format, separators, so the output matches your firm's convention rather than imposing its own.
No. Only the filename changes; the document's content, format, and pages stay exactly as they were.
Your files are kept private and secure.
View our Privacy Policy for more information.