Bates Numbering PDF Online: A Privilege-Safe Workflow

You sat down to bates numbering pdf online on a Tuesday afternoon because the production cutoff is Friday and the partner just walked in with a third supplemental volume. You search, you click the first result, and the upload widget asks for a 2,800-page PDF that includes a draft pleading, two privilege-log documents that slipped past review, and a settlement memo. You close the tab. That hesitation is correct: handing a privileged production to a third-party server is the kind of step a court looking at FRCP 26(b)(5)(B) clawback later will not call reasonable.

This guide walks through bates numbering the way litigation support actually does it — what the rules require, what the conventions are, why uploading is the wrong default, and how to stamp an entire production volume in your browser without the file crossing your network boundary. Every step references the rule or the platform behavior that drives it, because bates is one of those workflows where small choices echo into deposition exhibits and motion practice three months later.

Why bates numbering exists

Bates numbering exists because Federal Rule of Civil Procedure 34 — and its state-court analogs — require parties to produce documents in a form where every individual page can be cited. Without stable page identifiers, depositions degrade into argument over which page the witness is being shown; motion practice becomes unworkable when one side cites "the third email in the second binder" and the other side has reorganized the binder. The Bates Manufacturing Company built the original self-incrementing hand stamps in the 1890s; the name stuck even after the hardware did not. The text of FRCP 34 still drives the practice today.

Three other rules sit alongside it. FRCP 26(b)(5)(B) governs clawback of inadvertently produced privileged material — the producing party retains the right to demand return only if reasonable steps were taken to prevent disclosure. Federal Rule of Evidence 502(b) tracks the same inquiry for waiver, and FRE 502(d) allows a court order to lock in non-waiver protection across jurisdictions. State equivalents exist in every major commercial forum (CCP § 2031.285 in California, CPLR § 4503 in New York). What ties these together for bates is the workflow: every page you stamp becomes a citable artifact in motion practice, and the way you generated it gets re-litigated if anything privileged slipped through.

Prefix, padding, and exhibit-group conventions

Three conventions have hardened over three decades of e-discovery practice. They are not in the federal rules — they are in the local rules, the protective orders, and the agreed-to ESI protocols that govern modern productions.

• Prefix. A short alphanumeric string tied to the producing party (ABC, JOHNSON-, SMITH-001) or the document category (PRIV for privilege log, EXH-A for the first exhibit group, WP- for work product). Five to ten characters is the normal range. Hyphens are common; spaces and slashes are not — they break the load-file column parsers that review platforms use during ingestion.
• Padding width. Six is the workhorse: ABC000001 through ABC999999 covers nearly every commercial litigation matter. Width four is acceptable for small employment-case productions you are confident will stay under 10,000 pages. Width seven or eight is used in multi-district litigation, antitrust matters, and regulatory investigations where total page counts run into the millions. The Sedona Conference's Sedona Principles, Principle 12, recommends agreeing on the bates format in the ESI protocol up front for exactly this reason.
• Alphabetic prefixes for exhibit grouping. Deposition exhibits are typically prefixed by deponent (SMITH-EX-001, JOHNSON-EX-001) or by category (EXH-A0001 for the first exhibit group, EXH-B0001 for the second). Trial exhibits usually follow PX (plaintiff) and DX (defendant) with short numbers, no padding — PX1, PX2, DX1, DX2. The convention is whatever the court's standing order or the trial-prep spreadsheet says it is.

Whatever you choose, freeze it for the matter on day one. Switching widths or prefixes mid-production breaks sortability in Relativity, Concordance, and Everlaw, and creates the kind of pagination dispute opposing counsel will exploit in a motion to compel.

Why uploading a draft pleading is the wrong move

Every web-based bates tool that asks you to upload your production set creates a privilege problem. The clawback regime under FRCP 26(b)(5)(B) is designed to forgive the inadvertent inclusion of a privileged document in a production — but only if the producing party took reasonable steps to prevent disclosure in the first place. Sending a 50,000-page production through a third-party SaaS vendor's bates utility puts the documents on someone else's infrastructure for the duration of processing.

If a privileged document slipped through your privilege review and got bates-stamped on a vendor server, you have created a disclosure event before the production even leaves your office. The vendor's logging, retention policy, and breach posture all become evidentiary issues if opposing counsel challenges the clawback. Courts have grown more willing to scrutinize the "reasonable steps" inquiry under FRE 502(b); a vendor-uploaded processing step is a measurably weaker defense than a fully client-side workflow.

The same concern applies in three adjacent contexts. Attorney work product covered by FRCP 26(b)(3). Trade secrets governed by a protective order under FRCP 26(c). HIPAA-regulated medical records produced under a qualified protective order pursuant to 45 CFR § 164.512(e). Each of these has a regulatory or ethical-rule layer on top of the bare-rule analysis, and each of those layers gets harder to defend the moment the document crossed your network boundary.

Browser-local stamping eliminates the upload entirely. pdf-lib runs the page modifications in JavaScript inside your browser tab; the file is read with File.arrayBuffer(), parsed in memory, stamped page by page, and re-serialized — never crossing the network. You can verify this in DevTools by opening the Network tab and confirming no request goes out during a bates run.

How to bates-number in your browser

1. Open the tool. Go to the bates numbering tool and drop one or more PDFs into the upload zone. Files stay on your laptop — the page never sends them anywhere.
2. Set the prefix and starting number. Type your matter prefix (up to ten characters) and the starting number for this batch. For volume one of a new production, that is usually 1. For volume two, copy the last bates number from volume one's result panel and add one.
3. Pick padding width, position, and font. Width six and bottom-right are the safe defaults for a federal commercial production; Courier is the standard font. Adjust margin (in PDF points; 36 = half-inch from the edge) and font size if the receiving party's review platform has known crop behavior.
4. Stamp and download. Click stamp. A single PDF downloads as a single file; multiple PDFs download as a ZIP. Inspect the result panel — the last bates number actually written is shown explicitly so you can resume the next batch without overlap.

Three scenarios: discovery, exhibits, contracts

1. Discovery production volume

You have three custodian PDFs (Smith, Johnson, Lee) totaling 6,400 pages, due to opposing counsel by Friday under a Rule 34 request. Drag the PDFs into the upload zone in production order (custodial-priority order is the convention), set prefix to your matter code (e.g. ACME-) with width six, starting number 1, position bottom-right, font Courier 8pt. Stamp. Download the ZIP, attach the load-file your review platform exports, and ship. The result panel shows the last number — copy it before closing the tab.

2. Deposition exhibit indexing

For a Smith deposition with 23 exhibits, set prefix to SMITH-EX- with width 3, starting number 1. The deposition exhibits stamp as SMITH-EX-001 through SMITH-EX-023. Court reporters and opposing counsel can cite SMITH-EX-014 page 3 unambiguously. If the exhibits arrive as separate PDFs (one per exhibit), drop them in order; if they arrive as a single combined PDF, you may want to split the PDF into per-exhibit files first so the bates ranges align with the exhibit boundaries.

3. Contract negotiation rounds

For a transactional matter where both sides exchange redlines across multiple rounds, prefix the bates with the round and the party (R3-BUYER- or R3-SELLER-) and width 4. This is not a litigation use of bates — it is a navigation use, so both sides can cite a specific page in a 200-page asset purchase agreement during a call. Closing-binder assembly later is straightforward because every page already carries a stable identifier. Pair with the sign tool for execution copies and flatten-pdf to lock down the final signed version.

Multi-volume gen-numbering across rolling productions

Real productions arrive in volumes. Volume 1 might contain the custodial documents for the first witness; volume 2 the centralized accounting records; volume 3 a later supplemental production ordered to cure deficiencies. Each volume needs a distinct, non-overlapping bates range, and the convention (called gen-numbering or generational numbering) is to track the last number used in volume 1 and start volume 2 at that number plus one.

The arithmetic is mechanical, but the failure mode is not — if you restart at 1 for each volume, every motion that cites a specific bates number becomes ambiguous (which volume?), and opposing counsel can move to compel a re-numbered production. A tool that surfaces the last-number-used after every batch prevents the mistake; copy it into the starting-number field on the next run, and the volumes chain cleanly.

For supplemental productions ordered weeks or months later, the same logic applies — pick up where the last volume ended. Document the bates range of each volume in the production cover letter, in the load file, and in the privilege log. The cover letter references "ACME-000001 through ACME-050000 (Volume 1, March 14)" so the receiving party can map any citation to the correct volume without checking the file metadata.

Quality assurance before you ship

Before sending a stamped production to opposing counsel, verify three things. First, open the first and last page of the first PDF and confirm the bates range matches what you expected — ABC000001 on the first page, ABC000050 on the last page of a 50-page file. Second, open the first page of the second PDF and confirm the number is exactly one greater than the last number of the first PDF. Gaps and overlaps are the two failure modes opposing counsel raises in a motion to compel a re-production. Third, search the stamped PDF for the bates number; if it appears as searchable text, the stamp was written into the page content stream correctly rather than as a flattened raster image, which means OCR pipelines and review-platform load-file parsers will recognize it.

For matter-critical productions — anything with a protective order, anything in front of a federal judge, anything with a clawback issue already in motion — run a few sample pages through your review platform's load-file generator before stamping the full set. This catches cases where the platform's coordinate parser disagrees with the stamp position. Adjusting the margin or position before stamping 6,000 pages is far cheaper than re-stamping after opposing counsel objects.

One last QA step: redaction. If your privilege review identified partially-privileged pages (a contract attachment with one privileged paragraph), use redact-pdf to permanently black out the privileged text before bates stamping. Bates numbers go on the page content stream; redaction also modifies the content stream. Doing redaction after bates means the redaction tool re-encodes the page and can move the bates stamp by a few coordinate points, which is usually invisible but occasionally catches a review-platform OCR region. Redact first, stamp second.