Industry Reference Guide

Legal Document Naming Conventions

UTBMS codes, Bates numbering, EDRM integration, privilege protection, and practice-area naming patterns — everything a legal ops professional, paralegal, or firm administrator needs to implement a defensible document naming system.

6 practice areas covered35 UTBMS codes listed9 EDRM stages mappedCase law verified

Legal Naming Standard

A defensible legal document naming convention uses this pattern: {MatterNumber}_{DocumentType}_{Date}_{Version}.{ext}

Matter number first — aligns with your DMS (iManage, NetDocuments), enables ethical wall enforcement, and maps to UTBMS billing codes.
UTBMS-aligned document type — use consistent abbreviations (MSJ, Memo, DepTranscript, Complaint) derived from UTBMS task categories so every team member classifies the same way.
ISO 8601 date + version— YYYY-MM-DD sorts chronologically across every OS and DMS. Version suffixes (v1, v2, DRAFT, FINAL) prevent the "final_FINAL(2)" problem.

Used by 90% of AmLaw 100 firms via iManage. Aligns with UTBMS (ABA/ACC, 1995) and EDRM framework (2005).

Standard legal conventionNaming pattern

{MatterNo}_{DocType}_{Court}_{Date}_{Version}.{ext}

Result2024-1547_MSJ_SDNY_2026-03-15_v2.docx

Why it matters

Naming conventions are a compliance issue, not housekeeping

In most industries, inconsistent filenames are an annoyance. In legal practice, they create liability. A poorly named document can be missed during a privilege review, produced to opposing counsel by accident, or overlooked during a legal hold — any of which can result in sanctions, malpractice claims, or waiver of attorney-client privilege.

The stakes are quantifiable. In Qualcomm Inc. v. Broadcom Corp., document management failures led to $8.5 million in sanctions and referral of six attorneys to the State Bar. The court called it a "monumental and intentional discovery violation."

Who this guide is for

Legal operations professionals, paralegals, litigation support managers, firm administrators, and anyone implementing or evaluating document naming standards at a law firm or corporate legal department.

Classification standard

UTBMS Task Codes

The Uniform Task-Based Management System (UTBMS) was developed in 1995 by the ABA Section of Litigation, the Association of Corporate Counsel (ACC), and PricewaterhouseCoopers (PwC) to standardize how legal work is categorized for budgeting and billing. The original Litigation Code Set was published in 1997 with five phases and 29 task codes. In 2011, the LEDES Oversight Committee (LOC) ratified a sixth phase (L600) for e-Discovery.

For document naming, UTBMS codes provide a controlled vocabulary for the document type component of your filename convention — ensuring every team member classifies documents the same way and filenames align with matter budgets and e-billing requirements.

L100 — Case Assessment, Development and Administration

Code	Task
L110	Fact Investigation/Development
L120	Analysis/Strategy
L130	Experts/Consultants
L140	Document/File Management
L150	Budgeting
L160	Settlement/Non-Binding ADR
L190	Other Case Assessment

L200 — Pre-Trial Pleadings and Motions

Code	Task
L210	Pleadings
L220	Preliminary Injunctions/Provisional Remedies
L230	Court Mandated Conferences
L240	Dispositive Motions
L250	Other Written Motions/Submissions
L260	Class Action Certification and Notice

L300 — Discovery

Code	Task
L310	Written Discovery
L320	Document Production
L330	Depositions
L340	Expert Discovery
L350	Discovery Motions
L390	Other Discovery

L400 — Trial Preparation and Trial

Code	Task
L410	Fact Witnesses
L420	Expert Witnesses
L430	Written Motions/Submissions
L440	Other Trial Preparation and Support
L450	Trial and Hearing Attendance
L460	Post-Trial Motions and Submissions
L470	Enforcement

L500 — Appeal

Code	Task
L510	Appellate Motions and Submissions
L520	Appellate Briefs
L530	Oral Argument

L600 — e-Discovery

Code	Task
L600	Identification
L610	Preservation
L620	Collection
L630	Processing
L650	Review
L660	Analysis
L670	Production
L680	Presentation
L690	Project Management

Non-litigation code sets

UTBMS also defines codes for Bankruptcy (B-codes), Counseling (C-codes), and Project (P-codes). The principle is the same — each code maps to a billing category that can double as a document classification tag in your naming convention.

Production standard

Bates Numbering

Bates numbering (also called Bates stamping) applies unique, sequential identification numbers to every page in a document production. Named after Edwin G. Bates, who invented the Bates Automatic Numbering Machine in the late 19th century — a hand-held device that stamped a self-incrementing four-digit number (0000–9999) each time the handle was pressed.

Bates number formatNaming pattern

{Prefix}-{SequentialNumber}

ResultSMITH-000001

Format conventions

Alphabetic prefix identifies the producing party (SMITH, DEF, ACME_PI). Zero-padded sequential numbers (6–9 digits). Stamps placed on the lower right of each page. The District of Maryland ESI Principles recommend a four-digit alphanumeric prefix plus nine-character numeric value.

When required

Standard practice in virtually all U.S. civil litigation. Court ESI protocols require parties to agree on Bates format before production. Required for deposition exhibits, trial exhibits, and formal document productions. Enables precise citation: "See DEF-004523."

Filenames vs. Bates numbers

Internal filenames and Bates numbers are separate systems that must be coordinated. Filenames organize your documents pre-production; Bates numbers are applied at production time. During production, documents are renamed to their Bates range (e.g., DEF-000001.tif). A load file (.dat) maps Bates numbers back to original filenames and metadata.

eDiscovery framework

EDRM — Where Naming Fits in eDiscovery

The Electronic Discovery Reference Model (EDRM), created in 2005 by George Socha and Tom Gelbmann, defines nine stages for managing ESI from creation through courtroom presentation. Firms that implement structured naming before litigation reduce costs across the entire model — particularly during Processing (cheaper de-duplication), Review (faster reviewer comprehension), and Production (fewer naming conflicts).

Information Governance

Establish naming policies before litigation. Consistent conventions reduce downstream eDiscovery costs by making documents easier to identify and classify.

Identification

Descriptive filenames help custodian interviews. "2024-1547_MSJ_SDNY_2026-03-15.docx" is immediately identifiable vs. "Document1_final_FINAL(2).docx".

Preservation

Legal hold notices reference documents by matter number. Consistent naming enables automated preservation scans across DMS, email, and cloud storage.

Collection

Files with structured names can be collected selectively by matter number or date range, reducing over-collection and associated costs.

Processing

During ingestion into review platforms, original filenames become metadata fields. Structured names enable better de-duplication and family grouping.

Review

Documents are tracked by platform-assigned IDs, but original filenames appear in review interfaces, aiding reviewer comprehension and coding accuracy.

Production

Documents receive Bates numbers and are renamed to the production scheme (e.g., DEF-000001.tif). Load files map Bates numbers back to original filenames.

Presentation

At trial, exhibits are referenced by Bates number. Clear original naming makes it easier to locate source documents when preparing demonstratives.

The EDRM is iterative and non-linear — teams frequently cycle back to earlier stages. Maintained by edrm.net.

Risk mitigation

Attorney-Client Privilege Protection

Inadvertent production of privileged documents can result in privilege waiver — one of the most serious risks in litigation. While Federal Rule of Evidence 502(b) provides a "clawback" mechanism, courts evaluate the adequacy of your review process. Naming conventions are part of that evaluation.

Privilege-flagged filenames

Include _PRIV or _AC in filenames for attorney-client communications. Enables automated pre-production filtering. Documents flagged _PRIV trigger mandatory manual review before any production run.

Work product designation

Use _WP for attorney work product. Separates work product from ordinary business documents — particularly important for mixed-purpose documents with both legal analysis and business recommendations.

Privilege log generation

Structured filenames containing document type, date, author, and recipient enable automated generation of privilege logs — reducing the manual burden of logging thousands of withheld documents.

Pre-production QC

A filename-based filter (flag any file containing _PRIV, _AC, or _WP) provides a last-line-of-defense check before documents leave the firm.

Supplements, not replaces

Privilege flags in filenames are a supplement to, not a replacement for, privilege review in your eDiscovery platform. Some privileged documents will not be flagged at creation time. The naming convention catches the obvious ones; the review platform catches the rest.

Conflict management

Ethical Walls and Information Barriers

An ethical wall (information barrier) prevents the flow of confidential client information between lawyers who represent adverse or potentially conflicting interests. Governed by ABA Model Rule 1.10 (imputation of conflicts) and Rule 1.0(k)(defining "screened"), ethical walls require four elements: timeliness, no financial benefit from the screened matter, client notice, and ongoing compliance reporting.

Why matter-based naming is foundational

Automated access control

DMS platforms (iManage, NetDocuments, Worldox) restrict access based on the matter code in the filename — screened attorneys cannot view, search, or access documents with restricted matter prefixes.

Conflict checking

When a new matter is opened, the system scans filenames and metadata to flag potential conflicts with existing matters.

Audit trails

Consistent naming enables logging of all access attempts (including denied access), required to demonstrate screen compliance if challenged.

Cross-system enforcement

Case information lives across email, DMS, practice management software, and cloud storage. Matter-number-based naming enables enforcement across all systems simultaneously.

Cautionary case

Qualcomm Inc. v. Broadcom Corp.

No. 05-cv-1958-B (BLM), S.D. Cal. | Sanctions Order: Jan. 7, 2008

Qualcomm sued Broadcom for patent infringement related to H.264 video coding standards. Broadcom's defense was that Qualcomm had waived patent enforceability by participating in the Joint Video Team (JVT) standard-setting organization without disclosing its patents.

During discovery, Qualcomm failed to produce tens of thousands of relevant emails showing its JVT participation. The violation surfaced when an attorney discovered an undisclosed August 2002 email while preparing a witness for trial. Subsequent searches revealed 21 additional undisclosed emails. The trial team chose not to produce them.

Post-trial discovery revealed more than 46,000 documentsfrom just 21 employees' email files that should have been produced.

$8,568,633

Attorneys' fees awarded

6 attorneys

Referred to State Bar

46,000+

Documents undisclosed

The lesson

Qualcomm's failure was organizational, not primarily technical. Without a consistent naming system tied to matter management, relevant documents were scattered across custodians' personal email stores with no systematic way to identify, collect, or produce them. A matter-centric naming convention would not have prevented the intentional concealment, but it would have made the 46,000+ overlooked documents discoverable during the initial collection sweep.

Preservation duties

Legal Hold Obligations and FRCP Rule 37(e)

Federal Rule of Civil Procedure 37(e), amended in December 2015, governs sanctions for failure to preserve ESI. It establishes a two-tier framework:

Tier 1 — Rule 37(e)(1)

When ESI is lost because a party failed to take reasonable steps to preserve it and the loss causes prejudice, the court may order curative measures no greater than necessary. Objective standard.

Tier 2 — Rule 37(e)(2)

Only when the party acted with intent to deprive may the court impose adverse inference instructions, dismissal, or default judgment. Subjective standard — significantly higher bar than negligence.

How renaming interacts with preservation duties

Renaming a file changes only the filename — not the file content, metadata hash, creation date, or modification date. Under Rule 37(e), the concern is whether ESI was "lost" — renaming does not destroy the document. However, a defensible renaming process requires:

Maintain an audit trail

Log every rename: old filename, new filename, timestamp, and who (or what system) performed the rename. This trail is your evidence of "reasonable steps" under Rule 37(e).

Preserve original metadata

Ensure the renaming tool preserves file metadata (creation date, author, last modified date). Tools that copy-and-delete rather than rename-in-place can alter metadata.

Document in your litigation hold

If a legal hold is in effect, record any renaming activity as part of the hold compliance record. The hold should specify whether renaming is permitted during the preservation period.

Selective renaming risk

Apply the same naming convention uniformly. Selective renaming of some documents but not others could be scrutinized as evidence of intent to obscure.

Apply consistently across custodians

Use the same convention for all custodians on the same matter. Inconsistency undermines defensibility and creates confusion during review and production.

By practice area

Practice-Area Naming Patterns

Each practice area has distinct naming requirements driven by regulatory frameworks, court rules, and workflow conventions. Patterns used in production by law firms and corporate legal departments.

Litigation

LitigationNaming pattern

{MatterNo}_{DocType}_{Court}_{Date}_{Version}

Result2024-1547_MSJ_SDNY_2026-03-15_v2.docx

Include court abbreviation (SDNY, CDCA, EDVA) for multi-jurisdiction matters. Deposition transcripts include the deponent name. Exhibits reference Bates numbers after production.

Corporate / M&A

Corporate / M&ANaming pattern

{ProjectCode}_{DocType}_{Counterparty}_{Date}_{Status}

ResultPROJ-ACME_SPA_TargetCo_2026-03-01_EXECUTION.docx

M&A deals use project codes (not matter numbers) for confidentiality. Due diligence documents include the DD category (Financial, Legal, Tax, IP). Status tags: DRAFT, REVIEW, EXECUTION, FINAL, SIGNED.

Intellectual Property / Patent

Intellectual Property / PatentNaming pattern

{AppNo}_{DocType}_{JurisdictionCode}_{Date}

ResultUS17-234567_OA_Response_USPTO_2026-03-15.docx

Patent filenames embed the application number (US, EP, PCT prefix), document type (OA = Office Action, ISR = International Search Report), and jurisdiction. Version tracking is critical — patent prosecution involves many iterative filings.

Real Estate

Real EstateNaming pattern

{PropertyID}_{DocType}_{Address}_{Date}

ResultRE-2024-089_Lease_123MainSt_2026-03-01_EXECUTED.pdf

Use a property identifier rather than a party name (properties change hands). Include the address abbreviated. Environmental and title documents must be permanently retrievable for warranty claims.

Bankruptcy

BankruptcyNaming pattern

{CaseNo}_{DocType}_{Debtor}_{Date}_{DocketNo}

ResultBK-24-12345_POR_AcmeCorp_2026-03-15_Dkt247.pdf

Reference the case number and docket number. POR = Plan of Reorganization. Schedules use official designations (Schedule A/B, Schedule D). UTBMS B-codes apply: B100 (Case Administration), B200 (Asset Analysis), B300 (Relief from Stay).

Regulatory / Compliance

Regulatory / ComplianceNaming pattern

{RegBody}_{MatterRef}_{DocType}_{Date}_{Submission}

ResultSEC_INV-2024-789_WellsResponse_2026-03-15_FILED.pdf

Name the agency (SEC, DOJ, FTC, CFPB, OFAC) and the investigation or submission reference number. HSR = Hart-Scott-Rodino filing. CID = Civil Investigative Demand. Retention periods follow specific regulatory requirements (often 5-7 years minimum).

Real examples

Before and after: legal document filenames

What a typical legal team's document folder looks like — and what it should look like with a consistent convention.

BeforeAfter

scan_001.pdf

2024-1547_Complaint_SDNY_2026-01-15.pdf

Document (3).docx

2024-1547_MSJ_SDNY_2026-03-15_v2.docx

IMG_20260115_142355.pdf

2024-1547_DepTranscript_JDoe_2026-02-28.pdf

download.pdf

PROJ-ACME_SPA_TargetCo_2026-03-01_EXECUTION.pdf

final FINAL v2 (2).docx

RE-2024-089_Lease_123MainSt_2026-03-01_FINAL.docx

Copy of memo.docx

2024-1547_Memo_PrivilegeReview_2026-02-20_PRIV.docx

Production formats

ESI Protocols and Production Formats

An ESI (Electronically Stored Information) protocol is a written agreement between parties governing how electronic documents will be discovered, reviewed, and produced. Under FRCP Rule 34(b)(2)(E), if no production format is agreed upon, ESI must be produced in either the form in which it is ordinarily maintained (native) or a form that is reasonably usable.

Native Format

Original application format (.docx, .xlsx, .msg). Preserves all metadata. Cheapest to produce. Cannot be Bates-stamped on the face and can be inadvertently altered.

TIFF

Single-page image conversions. Most common in complex litigation. Can be Bates-stamped, redacted, branded. Produced with extracted text files and load files (.dat, .opt).

PDF

Static format supporting searchable text (via OCR), Bates stamping, and redaction. Often used in smaller productions or government proceedings.

Load files

.opt

Image load file— Maps Bates numbers to image files

.dat

Data load file— Contains metadata fields (custodian, date, subject, file type)

.txt

Extracted text files— One per document, enabling full-text search in the review platform

Hybrid production

Best practice: produce most documents as TIFF or PDF with load files and extracted text, but produce spreadsheets, databases, and presentations in native format. A federal court held that "producing documents without the underlying metadata is the equivalent of manufacturing a car without an engine."

Technology ecosystem

Document Management & eDiscovery Platforms

Naming conventions must integrate with the firm's DMS and, during litigation, with eDiscovery platforms.

Document Management Systems

iManage

Used by approximately 90% of AmLaw 100 firms and 4,000+ organizations worldwide. Assigns each document a unique number and version within a workspace (matter). Filenames should align with workspace naming conventions.

NetDocuments

Cloud-native DMS used by 3,500+ firms. Profile-based filing system associates metadata (matter number, document type, author) with each document. Consistent filenames matter for email attachments, exports, and cross-system transfers.

Clio

Practice management platform popular with small and midsize firms. Less robust naming enforcement than iManage or NetDocuments — consistent filenames are especially important because the system relies more on human discipline.

eDiscovery Platforms

Relativity

The dominant eDiscovery platform in complex litigation. Ingests documents with original filenames as metadata, assigns control numbers, and applies Bates numbers during production. Structured source filenames improve reviewer efficiency.

Everlaw

Cloud-native review platform with strong analytics. Predictive coding and concept clustering work on document content, but filename metadata contributes to document family understanding.

DISCO

AI-powered eDiscovery platform emphasizing speed and simplicity. Preserves original filenames as searchable metadata and applies Bates numbers at production.

Honest positioning

AI naming tools like renamed.to are a complement to your DMS, not a replacement. They solve the "intake problem" — getting documents named correctly beforethey enter iManage, NetDocuments, or your review platform. They do not replace the DMS's version control, access management, or search capabilities.

FAQ

Frequently asked questions

What naming convention do AmLaw 100 firms use for legal documents?

Most AmLaw 100 firms use a matter-centric naming pattern: {MatterNumber}_{DocumentType}_{Date}_{Version}.{ext}. The matter number is the primary key, matching the identifier in their Document Management System (typically iManage or NetDocuments). Document types follow UTBMS-aligned categories. Dates use ISO 8601 (YYYY-MM-DD) for chronological sorting. Version suffixes (v1, v2, FINAL, DRAFT) track revisions. Example: 2024-1547_MSJ_2026-03-15_v2.docx for a Motion for Summary Judgment.

How do Bates numbers relate to document filenames in eDiscovery?

Bates numbers and filenames serve different purposes but must be coordinated. Filenames identify documents in your internal DMS before production. Bates numbers are sequential stamps applied during production (e.g., SMITH-000001 through SMITH-004523) that provide permanent, unambiguous page-level references for citation in briefs, depositions, and at trial. During production, documents are renamed to their Bates range (e.g., DEF-000001.tif). The load file (.dat) maps Bates numbers back to original filenames and metadata. Best practice: maintain a cross-reference table linking internal filenames to Bates ranges.

Does renaming legal documents create spoliation risk under FRCP Rule 37(e)?

Renaming a file changes only the filename, not the file content, metadata, or hash value. Under FRCP Rule 37(e), spoliation concerns arise when ESI "is lost because a party failed to take reasonable steps to preserve it." Renaming does not destroy or alter the document itself. However, you must: (1) maintain an audit trail mapping old names to new names, (2) preserve original metadata (creation date, author, modification date), and (3) ensure the renaming process is documented as part of your litigation hold procedures. Courts examine whether "reasonable steps" were taken — a documented, consistent renaming process supports defensibility.

What UTBMS codes should legal ops teams use for document classification?

The UTBMS Litigation Code Set (developed by the ABA Section of Litigation, ACC, and PwC in 1995) provides standardized codes: L100 (Case Assessment), L200 (Pre-Trial Pleadings), L300 (Discovery), L400 (Trial Preparation), L500 (Appeal), and L600 (e-Discovery, added 2011). Within these, L140 (Document/File Management), L320 (Document Production), and L650 (Review) are most relevant to naming conventions. Map your document types to these codes so filenames align with matter budgets and e-billing requirements. Non-litigation code sets exist for Bankruptcy (B-codes), Counseling (C-codes), and Project (P-codes).

How do document naming conventions support ethical walls in law firms?

Matter-based naming conventions are foundational to information barriers. When filenames include the matter number as a prefix (e.g., 2024-1547_Memo_2026-03-15.docx), the DMS can automatically enforce access restrictions — screened attorneys cannot view, search, or access any documents with that matter prefix. This is required under ABA Model Rule 1.10 for imputed conflict screening. Consistent naming enables: automated access control in iManage/NetDocuments, audit trails proving screen compliance, conflict checking when new matters are opened, and prevention of inadvertent disclosure across conflicted matters.

What is the EDRM and how does document naming fit into eDiscovery?

The Electronic Discovery Reference Model (EDRM), created in 2005 by George Socha and Tom Gelbmann, defines nine stages: Information Governance, Identification, Preservation, Collection, Processing, Review, Analysis, Production, and Presentation. Document naming intersects at multiple stages: during Processing, files are indexed with unique identifiers; during Review, documents are tracked by document IDs in platforms like Relativity; during Production, documents receive Bates numbers and are renamed to the production numbering scheme. Consistent pre-litigation naming conventions reduce costs at every downstream stage by making documents easier to identify, de-duplicate, and classify.

Can AI tools generate legal document filenames that comply with DMS requirements?

Yes. AI document processing tools like renamed.to can extract matter numbers, client names, document types, and dates from PDF content using OCR and natural language processing, then generate filenames matching your firm's convention. The key requirement is configuring the naming template to match your DMS profile format (e.g., iManage's {MatterNumber}_{DocType}_{Date} pattern). However, AI-generated names should be reviewed before application — tools that offer a confidence preview and batch approval workflow (rather than automatic application) are safer for legal use. AI is a pre-processing step; the DMS remains the system of record.

Try AI-powered legal document naming

Upload a few legal documents and see how AI extracts matter numbers, dates, and document types to generate consistent filenames. 50 free renames, no credit card required.

Try Renamed.to Free

50 free file credits · No credit card · $0.009/file after

Continue exploring

Related guides, integrations, and resources

Legal document naming solution Contract naming convention guide Invoice naming convention guide Google Drive integration Dropbox integration Compare plans and pricing