Bates numbering is the practice of stamping every page of a document set with a unique, sequential identifier, so that any page in a production of fifty thousand can be named unambiguously by anyone holding a copy. It comes from a nineteenth-century hand-stamping machine and it remains the backbone of how litigation refers to documents. If you work anywhere near legal discovery, understanding it is not optional; if you do not, the underlying idea is still worth borrowing.
The problem it solves
Two parties exchange ten thousand pages. Someone needs to refer to a specific page in a deposition, a brief, or a court filing. "Page 4 of the March invoice" fails immediately: there are twelve March invoices, the page numbering restarts in every document, and the other side's copy may be paginated differently.
Bates numbering assigns each page a number that is unique across the entire production and printed on the page itself. SMITH-00042317 refers to exactly one page, forever, in every copy anyone holds. The number is on the page, so it survives printing, copying, scanning, extraction and re-merging.
That last property is the whole point. Any numbering scheme that lives in metadata, in a filename, or in a database can be lost. Ink on the page cannot.
Anatomy of a Bates number
A typical number has three parts:
- A prefix identifying the producing party or matter:
SMITH,ACME,DEF,PLTF. - A zero-padded sequence:
00042317. Padding is essential so numbers sort correctly as text — eight digits is common, six for smaller matters. - An optional suffix for confidentiality designations:
SMITH-00042317-CONFor a separate stamp readingCONFIDENTIAL — ATTORNEYS' EYES ONLY.
Conventions that matter in practice:
- Never reuse a number. Once issued, that number refers to that page permanently, even if the document is later withdrawn.
- Number every page, including blanks, slip sheets, and placeholder pages for withheld documents.
- Keep the sequence continuous across the production, not restarting per document.
- Record the ranges. A document is cited by its range —
SMITH-00042317toSMITH-00042344— so the mapping from document to range must be recorded, usually in a load file or production log. - Position consistently, conventionally bottom-right, in a margin, never over content.
Doing it in Acrobat
Acrobat Pro has native support, and it handles the multi-file case properly:
- Tools → Edit PDF → More → Bates Numbering → Add.
- Add the files, in order. The order in this dialog determines the sequence — check it carefully, because a misordered production is a serious problem to unwind.
- Set the prefix, suffix, number of digits, and starting number.
- Choose the position (bottom-right by default), the margin, the font and size.
- Apply.
Acrobat numbers across the whole set continuously, which is exactly the required behaviour, and it writes the numbers into the page content so they survive everything downstream.
To continue a sequence in a later production, set the starting number to one past the last number used. Keeping a running record of the last issued number per matter is a basic administrative discipline and a common source of error when it is not kept.
Other tools
Dedicated litigation-support software — Relativity, Everlaw, Nuix, Logikcull and their peers — handle Bates numbering as one small part of a discovery workflow that also covers deduplication, privilege review, redaction and production load files. If you are producing at any real volume, this is the category you are in, and the numbering is the least of what you are paying for.
pdftk and Ghostscript can stamp pages via overlays, and a script can generate a per-page number image or text overlay. This is workable for small matters and for adjacent uses (numbering an evidence bundle, an appendix set, a construction submittal), but you are rebuilding the accounting yourself.
PDF-XChange Editor and Foxit both have Bates features in their paid tiers.
For general page numbering that is not Bates numbering — a report's page numbers, an appendix sequence — see how to add page numbers to a PDF, which is a different job with different rules.
The rules that cause trouble
Do not stamp over content. A number that lands on top of text obscures evidence and, in scanned material, damages OCR of that region. Check the margins of the worst documents in the set, not the best — the landscape spreadsheet and the annotated fax are where the collision happens.
Number the final version. Applying Bates numbers and then discovering a document needs to be withdrawn or replaced means either leaving a gap or renumbering, and renumbering after production is close to unthinkable. Complete the review first.
Redact before numbering. Redaction changes pages, and doing it afterwards risks either altering a numbered page or destroying the stamp. And redaction must be real removal, not a black rectangle — the failure modes are laid out in PDF redaction failures and how to avoid them and how to redact text in a PDF.
Flatten the stamps. If numbers are applied as annotations rather than page content, they can be removed or moved. Ensure they are burned into the page — how to flatten a PDF.
Watch the file order. Sorting a folder of files by name gives you doc1, doc10, doc2 unless the names are zero-padded, and that ordering will silently become your production order. See naming and versioning shared files.
Keep the load file consistent. Most productions are accompanied by a load file (DAT/OPT or similar) mapping Bates ranges to documents and metadata. If the numbering and the load file disagree, the production is defective.
Production formats
Bates numbering sits inside a broader set of production conventions that are usually negotiated between the parties:
- Native production — original files, with a Bates-numbered slip sheet standing in for each. Spreadsheets in particular are usually produced natively, because printing them destroys formulas and hidden columns.
- Image production — every document as TIFF or PDF pages, Bates numbered, with a load file. The traditional format.
- Searchable PDF production — increasingly the norm: image with an OCR text layer, Bates numbered, so the pages are both faithful and searchable. See how to make a PDF searchable with OCR.
The choice affects the numbering workflow: a native production still needs numbers on its placeholder pages, and the mapping matters as much as the stamping.
Borrowing the idea outside litigation
The underlying principle — a stable, unique, page-level identifier printed on the artefact — is useful well beyond law:
- Construction and engineering submittals, where a drawing set is revised repeatedly and everyone must be able to reference the same sheet. See PDF workflows for architects and PDF workflows for engineers.
- Audit evidence packs, where a finding must cite a specific page of supporting documentation.
- Regulatory submissions, where a reviewer's comment has to point at something unambiguously.
- Board and committee packs, where "page 12 of the appendix" reliably means three different things to three people.
- Insurance claim files, where a claim is assessed from a bundle assembled from many sources — see PDF workflows for insurance claims.
In all of these, a continuous numbering scheme across a compiled bundle costs one Acrobat operation and removes an entire category of ambiguity from every subsequent conversation.
Summary
Bates numbering stamps a unique, sequential, prefixed identifier onto every page of a document set so that any page can be cited unambiguously by anyone holding a copy. Apply it after review and redaction, never reuse a number, number every page including blanks, flatten the stamps into the page, and keep a record of the last number issued per matter. Acrobat handles it natively for small productions; anything at volume belongs in litigation-support software — and the idea is worth stealing for any bundle that people will need to argue about.
