A personal injury firm has medical records, insurance correspondence, incident reports, employment documents, and image exhibits ready for production. The team needs every page to remain traceable after files are merged, shared, supplemented, or cited in a deposition. The best Bates numbering example isn't merely readable. It preserves sequence integrity, supports page-level citations, survives corrections, and fits the forum's discovery expectations.
The six formats below range from a simple numeric sequence to prefix-based, date-based, category-based, hierarchical, and hybrid systems. Sequential numbering is usually the safest baseline. Prefixes and organizational layers should be added only when they solve a specific retrieval problem.
Bates numbers generally identify pages in a production, while a document-level identifier may identify an entire native file. PDFs and TIFFs need visible page stamping or an equivalent control. Native files may instead use the Bates value in the filename, with the original filename preserved in a load file, as explained in native-file Bates naming guidance. Before delivery, validate padding, duplicates, gaps, placement, confidentiality treatment, and the production index. Ares can help organize medical-record facts and connect extracted dates, providers, diagnoses, and treatments back to source documents, but it doesn't replace counsel's review or the governing discovery rules.
1. Sequential Numeric Bates Numbering
The standard format is a continuous numeric sequence assigned across the production, such as 000001, 000002, 000003. It's the clearest choice when opposing counsel, a court, or a review platform needs a straightforward page locator without decoding a custom system.
For a personal injury production, the sequence might run from 000001 through 000450 for a medical-record package, then continue through the insurance file and investigation materials. The same approach works for state-court discovery responses, federal exhibits, and a consolidated PDF assembled from records received from multiple custodians. The point is continuity across the set, not a separate page count for every document.
A fixed-width sequence with leading zeros sorts cleanly in file lists and makes the production look deliberate. A commonly used modern pattern combines a prefix with zero-padded digits, as shown in this litigation Bates numbering format guide. If the forum or requesting party specifies a format, follow that instruction rather than imposing a house preference.
Where this format works best
Use sequential numbering when:
- Court-facing simplicity matters: A citation such as “Bates 000127” is immediately understandable.
- The production is consolidated: One sequence avoids confusion when medical, insurance, and investigative files are delivered together.
- The team expects supplements: Continue from the last used number instead of restarting the sequence.
- Ares is extracting medical facts: Stable page identifiers help reviewers verify a treatment date or diagnosis against the source page. The broader workflow is consistent with discovery document management practices.
This format has a trade-off. It tells the reader where a page sits in the production, but not whether the page came from a hospital, insurer, or police department. Keep that source information in the index and document metadata rather than forcing it into every identifier.
Practical rule: Number only after the document order, redactions, and page count are settled. Renumbering after production can undermine citations already used in correspondence or motion practice.
2. Prefix-Based Bates Numbering
A prefix-based format places a party, custodian, or production-set code before the running sequence. Examples include SMITH-001-000001, MERCY-HOSP-001-000001, and INSURE-ABC-002-000001. The numeric portion identifies the page, while the prefix supplies immediate source context.
For a personal injury team, this format can be practical when hospital records, insurer files, police materials, and separate defendant productions arrive independently. A hospital set might use MERCY-HOSP-001-000001, while an insurer set uses INSURE-ABC-002-000001. These are organizational examples, not mandatory conventions. The governing discovery protocol and production order control.
The main benefit is quick orientation. The main risk is inconsistency. An improvised abbreviation, a changed code, or a reused set identifier can make citations difficult to interpret. Keep the visible code short enough for pleadings and correspondence, but specific enough that reviewers can distinguish sources without guessing.
Set the register before stamping
At intake, create a written prefix register. Assign a code to each source or production set, identify the custodian, and decide whether the sequence applies to that set or the matter as a whole. Reserve the next range before processing. The firm's file-naming conventions guidance can help align folder names, native files, exports, and Bates identifiers.
Record these fields:
- Source code: The abbreviation for the party, provider, or custodian.
- Set code: The production or collection grouping.
- Sequence rule: Whether numbering continues within the set or across the matter.
- Index location: Where the code, range, and document metadata are mapped.
- Supplement rule: How later material continues the series or identifies a replacement set.
Use the prefix for organization, not page-level meaning beyond the assigned set. For court productions, confirm whether the protocol requires one continuous Bates range. Image files also need stamping instructions, since a Bates mark can obscure injury photographs or scan details. Keep sensitive information out of the visible code. Store diagnoses, disputes, and privilege details in controlled metadata instead.
3. Date-Based Bates Numbering
A date-based format incorporates a date into the identifier, such as 20240115-00001. It can help a personal injury team understand the chronology of treatment or collection at a glance, especially when records arrive in separate batches over the life of a claim.
For example, a medical timeline may contain records associated with the accident date, an emergency visit, specialist treatment, and later therapy. A date component can make a production's organization intuitive when the files are deliberately grouped by record date or collection date. It may also help a case manager locate a batch during internal review.
The danger is that a document has more than one relevant date. A medical record may show the date of service, the date it was signed, the date it was exported, and the date it was received by counsel. Choosing the wrong date can make the Bates identifier misleading. An undated document creates another judgment call, and a corrected date can require rework.
Treat dates as an organizational layer
For court-facing productions, a date-based value is usually safer as a supplementary organizational aid than as the only production control. A primary sequential series preserves stable page-level citation, while a chronology, index, or filename can carry date information. That separation prevents a later correction to a medical date from changing the page locator.
The medical chronology template guidance is useful for thinking about the distinction between a fact's date and a source page's identifier. Ares can organize dates, providers, diagnoses, and treatment events, but the reviewer should verify each extracted fact against the underlying record.
A treatment date explains when an event occurred. A Bates number explains where the supporting page can be found. Keep those functions separate.
Before using a date component, write down whether it represents date of service, document date, collection date, or another defined field. Apply the same rule to every record in the set. If the date is uncertain, preserve that uncertainty in the index rather than encoding an unsupported assumption into the Bates value.
4. Document Type and Category Based Bates Numbering
A personal injury production may contain hospital charts, claim correspondence, police photographs, wage-loss records, and prescription histories. Category-based numbering places a document-type code in the Bates identifier, such as MED-REC-001-000001, INS-DOC-002-000001, POLICE-003-000001, or PHARMA-004-000001.
The code gives the reviewer an immediate orientation point. A lawyer preparing a damages argument can locate the medical-record range quickly. A paralegal answering an insurer's request can isolate claim materials without opening every file. The final padded sequence remains the page-level locator, while the category identifies the broader group.
Use category codes for retrieval, not as a substitute for a production control. A record may fit several groups. An invoice could be classified as a medical record, damages support, or billing material, depending on the agreed protocol. Classification can also change during review. If codes become too specific, the team spends more time learning exceptions and correcting labels.
Set the scheme before stamping. Limit it to groups that affect retrieval, privilege review, or a required production grouping. Record each code, its definition, the sequence owner, and the relationship to the production index. Keep unusual items in metadata rather than creating a new category for each exception.
A workable register might use:
- Medical records: Provider charts, diagnostic materials, and treatment documentation.
- Insurance documents: Claim correspondence, coverage materials, and insurer communications.
- Investigation materials: Reports, photographs, diagrams, and scene documentation.
- Employment records: Wage-loss support and work-status materials.
- Pharmacy records: Medication histories and prescription documentation.
For medical records, Ares can organize providers, diagnoses, treatment events, and source pages, but reviewers should verify extracted details against the underlying files before stamping or producing them. Apply the Bates value consistently at the page level when citing individual pages. Use document-level grouping only when the production protocol and index make the document boundary clear.
The index still needs the source, description, date range, confidentiality status, and Bates range. MED-REC-001-000127 shows category and page location. It does not establish authenticity, relevance, admissibility, or privilege. Preserve those determinations separately in review fields and production logs.
5. Hierarchical and Nested Bates Numbering
A personal injury team with records from a hospital, cardiologist, physical therapy clinic, and accident investigator may need more structure than one uninterrupted sequence. A hierarchical identifier can show that context, for example 2024-PI-001-MED-MERCY-HOSP-001-000001. Its layers may identify the matter, case group, evidence type, provider, collection set, and page sequence.
That detail helps staff locate records in an internal repository, but it is not automatically a better discovery convention. Long citations take longer to say and type, increase transcription errors, and depend on stable abbreviations. Providers can change names, merge facilities, or appear under several names in the source files. Each additional embedded fact creates another point that may require a new scheme.
Reserve hierarchy for retrieval problems
Before collecting or stamping files, document each level, permitted value, separator, abbreviation, and connection to the production index. A practical internal structure is:
- Matter: The internal case identifier.
- Evidence type: Medical, police, employment, or another major group.
- Source: Provider, facility, party, or custodian.
- Collection set: The relevant production or batch.
- Page sequence: The unique page-level locator.
Keep the page stamp short enough for counsel to cite accurately. Store the full record genealogy in the index, then use a shorter prefix-plus-sequence Bates number on the page when the production protocol permits it. The index should carry the source, description, date range, confidentiality status, and Bates range. A value such as MED-REC-001-000127 identifies category and page location. It does not establish authenticity, relevance, admissibility, or privilege, so preserve those decisions in review fields and production logs.
For medical records, Ares can organize providers, diagnoses, treatment events, and source pages. Reviewers should verify extracted details against the underlying files before stamping or producing them. Use page-level Bates values when a brief cites an individual page. Use document-level grouping only when the production protocol and index clearly define the document boundary.
Set a supplement rule before production. If a provider sends more records, continue the relevant sequence or assign a documented new set. Do not insert pages into a cited range. Preserve the prior production, record the change, and describe the relationship between original and supplemental materials in the production log.
6. Alphanumeric and Hybrid Bates Numbering
A hybrid format combines letters, numbers, and optional exhibit or production markers. Examples include A-000001, B-SMITH-000045, ABC-12-0001-EXHIBITS, EX-A-001, and SUPP-00001-00050. The flexibility can be valuable when a firm must distinguish exhibits, offices, supplemental materials, or internal collection groups.
For a personal injury team, an exhibit marker may separate photographs or demonstratives from the core discovery production. A supplemental marker can distinguish a later delivery from the original set. A multi-office matter might use location identifiers internally, although those identifiers should be explained before anyone relies on them in a citation.
Hybrid systems are also the easiest to overdesign. A letter that means “privileged,” “supplemental,” or “exhibit” can expose workflow information and invite confusion with the actual privilege log. Bates identifiers should not be used as a substitute for withholding procedures, redaction review, or a proper privilege designation.
Keep the pattern predictable
Write the convention before numbering begins and circulate a one-page key. State whether the final sequence identifies pages, documents, exhibits, or another unit. For native files, decide whether the Bates value will be placed in the filename, stamped after conversion, or recorded through a load-file field. For page-based PDFs and TIFFs, confirm that each page receives the intended visible identifier.
Avoid characters that readers can confuse, particularly combinations involving 0, O, 1, I, or L. Use separators consistently. Don't change from ORIG-00001 to ORIGINAL-00001 halfway through a matter, and don't restart a supplemental series without documenting why the new range is distinct.
A hybrid scheme works when each added element answers a real question. If the team only needs a stable page locator, a short prefix and padded sequence will usually be easier to defend and use.
6-Format Bates Numbering Comparison
| Bates Format | Implementation Complexity | Resource Requirements | Expected Outcomes | Ideal Use Cases | Key Advantages |
|---|---|---|---|---|---|
| Sequential Numeric (Standard Format) | Very low, simple consecutive numbering | Minimal, basic Bates software or scripts, little training | Linear, court-accepted pagination; easy page-count verification | Standard litigation, baseline for personal injury discovery | Universal acceptance, fast to assign, consistent pagination |
| Prefix-Based (Case/Party Identifier) | Low–moderate, requires agreed prefix conventions | Prefix planning, master index, team coordination | Sequential numbers with clear source identification | Multi-party or multi-source litigation requiring source clarity | Identifies document source quickly; simplifies multi-set management |
| Date-Based (Chronological Format) | Moderate, must verify and standardize dates | Date extraction/verification, indexing, possible manual review | Chronologically sortable records; clear timeline context | Personal injury timelines, treatment progression, incident chronology | Immediate temporal context; aids timeline reconstruction and analysis |
| Document Type/Category-Based (Classified) | Moderate–high, requires category schema design | Category codebook, training, pre-planning, indexing tools | Documents grouped by type for fast retrieval and reduced tagging | Complex cases with many evidence types needing rapid pulls | Built-in classification; efficient search by document type; reduces post-processing |
| Hierarchical/Nested (Multi-Level) | High, complex multi-level schema and governance | Extensive planning, documentation, training, robust tools | Self-documenting identifiers enabling multi-dimensional sorting | Highly complex, multi-provider or multi-defendant cases | Full hierarchy embedded in ID; supports sophisticated sorting and AI parsing |
| Alphanumeric/Hybrid (Mixed Format) | Variable, depends on chosen patterns; needs strict rules | Convention documentation, QA, coordination across teams | Flexible, case-specific labels with exhibit/version control; less standardized | Cases needing custom labeling (exhibits, supplements, versions) | Maximum flexibility; supports exhibits, versions, privileged markers |
Make Every Stamp Defensible and Findable
Choose sequential numbering when court-facing simplicity and citation clarity matter most. Add a short prefix when the source or production set needs to be visible. Use dates and categories as organizational aids only after confirming that they won't undermine the primary production sequence. Reserve nested and hybrid formats for complex workflows with a written codebook, a maintained index, and a clear supplement policy.
A Bates number is a locator, not a document index and not a legal conclusion. It doesn't prove that a record is complete, establish relevance, resolve privilege, or replace the review required before production. It gives the team and opposing counsel a durable way to identify a page or, for native files, a controlled way to identify the file.
Before delivery, confirm the following:
- Page-level control: PDFs and TIFFs have a consistent, legible stamp in a location that doesn't obscure content.
- Native-file control: Each native file has a documented file-level identifier, with the original filename preserved where the load file or protocol requires it.
- Fixed formatting: Prefixes, separators, and zero padding remain consistent throughout the set.
- Sequence integrity: The team checks for duplicates, gaps, unintended restarts, and incorrect file order.
- Production index: The index maps Bates ranges to source, description, custodian, dates, and relevant metadata.
- Supplement handling: Later productions continue or clearly identify a new range without altering already cited pages.
- Privilege and redaction review: Counsel confirms that withheld or redacted material is treated under the applicable rule and production protocol.
- Forum requirements: The team follows jurisdiction-specific discovery instructions, protective orders, and agreed technical specifications.
Historical continuity explains why the method remains useful. Edwin G. Bates patented an automatic numbering machine in 1891, received U.S. Patent No. 484,391 for a consecutive-numbering machine in 1892, and received the Franklin Institute's Longstreth Award by 1895, according to the history of Bates numbering. The mechanical stamp solved the same basic problem modern software solves, unique and durable identification across paper-heavy records.
Ares fits into the review layer rather than replacing the production-control layer. The team can organize medical records, review extracted dates, diagnoses, providers, treatments, and symptom chronology, then verify those facts against source pages before using approved Bates references in demands, correspondence, or collaboration. For another perspective on why physical stamping alone can be unreliable, see AutoProv's discussion of paper service stamps.
Take the time to approve the scheme before stamping. A short, consistent identifier supported by a reliable index is usually more valuable than a clever format that nobody can maintain.
Ares helps personal injury firms organize medical records, connect extracted facts to source pages, and prepare case-ready summaries and demand drafts for review. Visit Ares to see how a source-linked medical-record workflow can support accurate Bates references and faster collaboration.
