Bates Numbering Best Practices: Production QC Checklist

Legal content overseen by Nathan Walter, Esq., attorney licensed in California (State Bar No. 313299).

A second production that reuses an earlier range, or an attachment separated from its parent email, creates citation problems that are slow to untangle. Bates numbering best practices come down to three habits: agree on a numbering convention before the first release, keep each document’s file relationships intact, and test every delivered set against your production log.

A Bates identifier is a unique label on each page (or, for native files, each file) of a production. For more background, see what Bates numbering means.

This guide covers federal civil discovery under the Federal Rules of Civil Procedure and focuses on checks a defense team can run before a production goes out.

Bates numbering best practices start with the production protocol

Separate Rule 34 requirements from numbering conventions

Rule 34 says little about labels. Under Rule 34(b)(2)(E), unless the parties stipulate or the court orders otherwise, three procedures apply:

• A party must produce documents as they are kept in the usual course of business, or organize and label them to correspond to the categories in the request (Rule 34(b)(2)(E)(i)).
• If the request does not specify a form for electronically stored information (ESI), the party must produce it in a form in which it is ordinarily maintained or in a reasonably usable form (Rule 34(b)(2)(E)(ii)).
• A party need not produce the same ESI in more than one form (Rule 34(b)(2)(E)(iii)).

The first item is an “or”: usual-course production or organization by category. A Bates stamp alone does not establish either route.

The rule text does not prescribe a prefix, digit width, stamp position or gap-free sequence. Those are conventions that parties adopt, and a court order or stipulation may change the default procedures.

Form of ESI is also a request-and-response issue. A request may specify the form (Rule 34(b)(1)(C)), and a responding party that objects to the requested form, or receives no specified form, must state the form it intends to use (Rule 34(b)(2)(D)). For more on requests for production (RFPs), see requests for production: rules and examples.

Record the agreed production settings

At the discovery planning conference, parties must discuss preservation issues and develop a proposed discovery plan (Rule 26(f)(2)). Numbering, production format, native files and privilege handling are natural items to settle then, in a stipulation or protocol. For the broader document, see creating an ESI protocol.

A numbering clause can be short. The following is an invented drafting illustration, not a model order or a complete ESI agreement:

Choose unique prefixes, padding and production ranges

The examples in this guide are invented and use a fictional corporate defendant, “Acme.”

Reserve one namespace per producing party

Give each producing party its own prefix, such as ACME, so that identifiers cannot collide with another party’s. Keep the prefix stable.

Putting a category label or a confidentiality designation inside the identifier forces a new identifier when the designation changes. Carry designations in a separate legend or field instead. For how prefixes fit into the larger scheme, see the components of a Bates numbering system.

Fix the digit width and control the next available number

Zero-padding keeps identifiers sortable as text: Unpadded, ACME10 sorts ahead of ACME2 in text order; padded, ACME000002 sorts ahead of ACME000010. Six digits is an illustrative choice, not a federal minimum. Pick a width with room to grow.

When several vendors, paralegals or attorneys stamp documents in parallel, one person should control the next available number. That person also records reserved and voided ranges.

Keep ranges unique across releases

A three-page produced PDF takes the range ACME000001–ACME000003. The next release continues from the next unused identifier and never reuses one that has been assigned.

Place readable stamps and preserve document families

Test placement on difficult pages

Check portrait and landscape pages, scans with small margins, pages with signatures near the edge, pages that already carry a number, and pages that will also carry a redaction label. Where the standard location would cover text, use an alternate location the protocol permits and document the exception.

Keep parents and attachments linked

Preserve document boundaries, parent identifiers and attachment relationships. Sequential numbering helps when the parties agree to it, but a Bates sequence does not by itself encode a family. A parent-child field in the load file, if the protocol uses one, is a more reliable record than adjacency.

Do not produce a privileged attachment just to fill the family range. Withhold it and identify the exception on the log without revealing protected content (see the privilege section below).

Give native files a usable identifier and slip-sheet mapping

Distinguish file identifiers from page citations

A native Excel workbook need not have fixed production pages. If the agreed form is native, produce the native, and do not flatten it to PDF only to have something to stamp when that loses functionality or conflicts with the production specification. Rule 34 leaves form to the request, response, stipulation or order (Rule 34(b)(2)(D)–(E)).

Cross-check the native, placeholder and load file

If the protocol uses placeholders, pair each native with a document-level identifier and a Bates-labeled slip sheet, and keep the mapping to the original filename and the family. The exact fields and file formats are negotiated technical choices, not Rule 34 requirements.

A later citation to a spreadsheet may need the document identifier plus a worksheet and cell reference. Do not invent a Bates page for a file that has none.

Separate privilege withholding from redaction checks

Use the privilege log for withheld material

A party that withholds information as privileged or protected must expressly make the claim and describe the nature of what is withheld in a way that lets other parties assess the claim without revealing protected information (Rule 26(b)(5)(A)). A skipped Bates number is not a description. A wholly withheld document can carry its own control identifier on the log, such as PRIV-001, and no produced Bates range. The rule does not prescribe log columns.

An objection must also state whether responsive materials are being withheld on the basis of that objection (Rule 34(b)(2)(C)). A log or a page label does not replace that statement.

Check what the receiving party can recover

For produced redacted copies, confirm that the approved redactions are in place and the stamp is still readable. Then test whether protected text survives in the export’s text or optical character recognition (OCR) layer, in metadata, or in a native attachment included by mistake. This is a practical quality-control step, not a rule requirement.

Confidentiality designations and privilege withholding are different decisions. If produced information is subject to a privilege or trial-preparation protection claim, the claiming party may notify recipients of the claim and its basis. After notice, a recipient must promptly return, sequester or destroy the specified information and any copies, and must not use or disclose it until the claim is resolved.

A recipient must take reasonable steps to retrieve information it disclosed before notice. A recipient may also promptly present the information to the court under seal for a determination of the claim. The producing party must preserve the information until the claim is resolved (Rule 26(b)(5)(B)).

Reconcile the production log and each rolling release

Compare the delivered package with the approved selection

A production log is an internal control record. It is not the privilege log or the written response, and it is different from a production index served on the other side. Useful fields:

• Release, date and producing party: which delivery, when, and whose documents.
• File or control ID: the internal identifier for each document.
• Beginning and ending Bates: the range, with the page or file count.
• Parent ID and native path: the family link and the native file’s location.
• Request cross-reference: the request for production the document was reviewed against.
• Disposition and exception: produced, withheld, redacted, voided or replaced.
• Reviewer and correction link: who checked it, and any later release that corrects it.

Continue the sequence without changing earlier citations

Keep copies of every delivered package. Record reserved and voided ranges separately rather than hiding them by renumbering. If an earlier release has an error, use a counsel-approved correction notice with an old-to-new mapping, and do not silently restamp pages that have already been served. Whether an identical replacement copy may reuse an identifier is a protocol question.

A party that has responded to a request for production must supplement or correct the response in a timely manner if it learns that the response is materially incomplete or incorrect and the additional or corrective information has not otherwise been made known to the other parties during discovery or in writing. The party must also supplement or correct as ordered by the court (Rule 26(e)(1)). When a responding party states that it will produce copies instead of permitting inspection, production must be completed no later than the inspection time specified in the request or another reasonable time specified in the response (Rule 34(b)(2)(B)). A rolling release plan must account for that completion date; dividing a production into batches does not itself extend it.

Run a release check

Before each release goes out, confirm that:

1. No identifier appears in this release and an earlier one.
2. Every gap is explained as reserved, voided or withheld.
3. First and last identifiers and counts match the reviewed set.
4. Sample files open, and stamps are legible.
5. Family and native links match the log.
6. Redacted pages pass the export check above.
7. Citations in the response match the delivered ranges.
8. An attorney has signed off.

The checklist finds defects. It does not show that collection, search or responsiveness review was complete. To compare tools, see Bates numbering software.

A worked example

Suppose Acme produces an email as ACME000001–ACME000003. Its spreadsheet attachment is a native file mapped to the slip sheet ACME000004. A second attachment is wholly withheld as privileged and appears on the privilege log as PRIV-001, with no produced range. The next image set starts at ACME000005 only if the log confirms that number is free. A range that was reserved but then voided is recorded in the log, not covered by renumbering.

State rules

This guide addresses federal civil discovery only. For New York document-demand procedure, see New York document demands under CPLR 3122.

Prepare Bates-cited RFP responses with Briefpoint

Briefpoint drafts responses and objections to requests for production, and the output is editable in Microsoft Word. Attorneys keep final review. See drafting RFP responses and objections for the product overview and federal discovery responses for the response side of discovery.

Autodoc’s responsive-document and Bates-citation workflow finds responsive documents, adds page-level Bates citations and builds a Bates-numbered production package. That ties a response to a production, so the attorney can check each cited range against the reviewed documents before service.

The production log, release check, native mapping, privilege log and redaction checks above are practice recommendations. These recommendations do not describe built-in Briefpoint automation or establish that a production satisfies an ESI order. Responsive-document selection, privilege calls, citations and the draft responses all stay with the attorney.

To see how Briefpoint supports attorney-reviewed, Bates-cited discovery responses, Book a demo.

Watch the Briefpoint demo video:

FAQs About Bates Numbering Best Practices

Does the FRCP require Bates numbering by name?

No. Rule 34 does not mention Bates numbering. It requires production as documents are kept in the usual course of business or organized and labeled to the request’s categories, and it sets default ESI form rules, subject to any stipulation or order (Rule 34(b)(2)(E)). A Bates stamp alone does not satisfy either organization option.

Do I need to Bates stamp blank pages in a production?

Rule 34 does not address blank pages. Treatment is a matter of the production specification or protocol. A protocol may provide for numbering every page of an imaged production, but that is an agreed convention, not a federal command. Whatever the agreement, reconcile the page count against the reviewed source.

How are native files, such as spreadsheets, numbered without converting them to an image?

Under a typical agreement, each native file gets a document-level identifier, often paired with a Bates-labeled slip sheet and a load-file entry that maps it to the original filename and family. The native itself is still delivered when native is the agreed form. These fields are negotiated, not set by Rule 34.

Can Bates numbers be reused between separate productions in the same case?

The numeric portion should not repeat across releases from the same producing party, because the full identifier must point to one set of content. If an error requires a change, follow the agreed correction procedure and keep an old-to-new mapping rather than silently reassigning a number.

How are email families numbered?

Families are usually preserved through parent-child fields in the load file, with the parent and its attachments often numbered in sequence. Adjacency alone does not prove the family is complete, and an attachment may be withheld as privileged. Log that exception rather than filling the gap with unrelated pages.

The information provided on this website does not, and is not intended to, constitute legal advice; instead, all information, content, and materials available on this site are for general informational purposes only. Information on this website may not constitute the most up-to-date legal or other information. This website contains links to other third-party websites. Such links are only for the convenience of the reader, user or browser. Readers of this website should contact their attorney to obtain advice with respect to any particular legal matter. No reader, user, or browser of this site should act or refrain from acting on the basis of information on this site without first seeking legal advice from counsel in the relevant jurisdiction. Only your individual attorney can provide assurances that the information contained herein – and your interpretation of it – is applicable or appropriate to your particular situation. Use of, and access to, this website or any of the links or resources contained within the site do not create an attorney-client relationship between the reader, user, or browser and website authors, contributors, contributing law firms, or committee members and their respective employers.