Document Productions: Bates Stamping for FRCP Requests and Subpoenas

Document productions are where Bates numbering earns its keep. Whether you're responding to FRCP Rule 34 requests as a party or to a Rule 45 subpoena as a third party, the stamping you apply determines how the entire case will refer to those documents for the rest of the litigation. Skip a step here and you create months of downstream cleanup; do it right and every motion, deposition, and trial reference works on the first try.

Two production tracks

Rule 34: party productions

Federal Rule of Civil Procedure 34 allows a party to request documents and electronically stored information (ESI) from another party. The producing party identifies responsive documents, applies privilege review, and produces what's left under the case's protective order (if there is one) or subject to confidentiality designations the producing party asserts.

The producing party owns the Bates prefix. Standard convention is to use the producing party's initials or short name as the prefix: SMITH000001 for documents produced by Smith, ACME000001 for documents produced by Acme Corp. The prefix carries through every supplemental production in the case, and the numbers never reset — Smith's second production starts wherever the first left off.

Rule 45: third-party subpoenas

Rule 45 lets a party serve a subpoena on a non-party for documents or testimony. The non-party (often a bank, employer, medical provider, or service vendor) produces under different mechanics: usually no protective order automatically applies, confidentiality has to be asserted by the subpoenaed party, and the prefix typically identifies the responding non-party rather than the requesting party.

A subpoena response from First National Bank in a case styled Doe v. Roe would carry a prefix like FNB000001 — not the producing-party convention from Rule 34. The bank isn't a party; the prefix tells everyone the documents came from the subpoena response, not from a party's own files.

Why you stamp before you produce

A production without Bates numbers is technically valid but functionally broken. Every reference to a document — in motion briefs, deposition transcripts, expert reports — needs a stable identifier. If you produce 5,000 pages without Bates numbers and opposing counsel cites "the email about the meeting," you spend the next year disambiguating. Pre-stamping is what turns the production from a stack of paper into a citable corpus.

Other reasons to stamp before producing:

• Privilege clawback. If a privileged document slips through, the protective order (and FRE 502) lets you claw it back — but the clawback notice has to identify the document by Bates number. Without numbers, no clean clawback.
• Privilege log alignment. Documents withheld on privilege grounds are listed by Bates range on the privilege log. The log assumes every produced document has a stable number; pages without numbers create gaps the court will challenge.
• Re-production after redaction. If a redaction is challenged and ordered re-produced unredacted, the replacement page has to keep the same Bates number. Mid-case renumbering is unworkable.
• Discovery order compliance. Many federal districts have ESI orders or local rules requiring Bates numbering on every produced page. The Sedona Conference's principles treat sequential numbering as a baseline.

Bates conventions for productions

Prefix selection

• Party productions (Rule 34): the producing party's short name or initials, all caps — SMITH, ACME, JONES.
• Subpoena responses (Rule 45): the responding non-party's short name — FNB for First National Bank, KAISER for Kaiser medical records.
• Multi-party cases: use distinguishable prefixes so SMITH and SMITH-CORP don't collide.

Digit width

Pick a width that comfortably exceeds your expected total. For most productions:

• 6 digits (000001 → 999999) for typical productions up to ~1M pages.
• 7 digits for large productions (multi-million pages) or cases where you want headroom.

Once you pick the width, don't change it mid-case. A supplemental production that goes from SMITH000147 to SMITH148 breaks every regex the receiving party has built to extract citations.

Sequence continuity

Each supplemental production picks up where the prior one ended. If your initial production ended at SMITH002847, your first supplement starts at SMITH002848. Never reset, never overlap.

Confidentiality endorsements

Productions almost always involve some confidentiality designation under the case's protective order. Common patterns:

• Page-level endorsement on every protected page: "CONFIDENTIAL," "ATTORNEYS' EYES ONLY," or the order's specific designation. Goes on every page (not just the first).
• Bates-suffix designation as an alternative or companion: SMITH000147-CONF, SMITH000148-AEO. Some protective orders prefer this; check the order's text.
• Mixed designations within a single production. Most productions have a mix — pages 1–50 are CONFIDENTIAL, pages 51–60 are AEO, pages 61–200 are non-confidential. Stamp accordingly per page, never blanket.

See our guide on endorsements for what each tier means and when it applies.

Producing electronically

Most modern productions are delivered as a folder of stamped PDFs alongside a load file (CSV or Concordance .DAT format) listing each document's metadata: Bates start, Bates end, custodian, file path, original filename, hash, etc. Standard load file fields:

• BEGDOC — first Bates of the document.
• ENDDOC — last Bates of the document.
• CUSTODIAN — who possessed the document.
• CONFIDENTIALITY — designation per the protective order.
• NATIVE — link to the native file when produced in native format.

Common production mistakes

• Bates numbers don't match the load file. BEGDOC says SMITH000001 but the actual stamp says SMITH000002. Receiving counsel rejects the production.
• Confidentiality designation in the load file but not on the page. The protective order is enforced by what's stamped on the page, not what's in metadata. Without page-level marking, the designation may not stick.
• Sequence breaks. Initial production ends at SMITH001500, supplement starts at SMITH001500 instead of 001501 (overlap) or 002000 (gap). Both are problems.
• Mixed prefix conventions across supplements. First production uses SMITH, supplement uses S, third uses SMITHCORP. Receiving party can't reliably regex-match citations.
• No load file at all. A folder of stamped PDFs without a load file isn't a Rule 34-compliant production for any case requiring metadata; expect a meet-and-confer.

How Stampify handles productions

Stampify is built for this exact workflow. Drop the production, set the prefix and digit width, choose the per-document confidentiality designations (or apply blanket and override per file), and the output is:

• Stamped PDFs with Bates numbers + page-level endorsements.
• A CSV load file with BEGDOC, ENDDOC, CUSTODIAN, CONFIDENTIALITY columns ready for any e-discovery platform.
• A combined production binder with hyperlinked TOC if the receiving party wants that format.
• Sequence continuity tracked across supplements — drop in a new batch and Stampify computes the start number from the prior production.

Stamping productions in your browser also means files never leave your device — relevant for subpoena responses where the subpoenaed non-party may not have a vendor on retainer and doesn't want to upload sensitive records to a third-party processor.