Bates Numbering PDF Guide for Ordered, Verifiable Document Sets

What Bates numbering does - and does not do

This Bates numbering PDF guide treats each label as a stable locator within a defined document set. A sequence such as MATTER-000001 gives reviewers a concise way to cite a page, reconcile a production and discuss exceptions. The value comes from a controlled assignment process and a retained mapping, not from the visual stamp alone.

A Bates label does not prove when a source was created, who authored it, whether every relevant document was included or whether the page has remained unchanged. It is not a certificate signature. Anyone with editing software may be able to alter a visible label, so preserve source records and protect the approved production using the controls required by the matter.

The Bates Number PDF tool applies zero-padded numbering across one or more PDFs. Its manifest should be retained with the output where traceability matters. The operator still owns file selection, order, numbering policy and quality review.

Freeze the production order before numbering

Begin with an approved source list. Sort by the matter's rule - chronology, custodian, document family, exhibit order or another recorded scheme - and resolve duplicates before assigning labels. File-system name order can be surprising when numbers are not padded, so inspect the actual ordered list rather than trusting a folder view.

Decide whether numbering continues across file boundaries or restarts for each volume. Continuous numbering simplifies uniqueness across one production, while per-volume sequences may suit an established protocol. If families such as an email and its attachments must stay together, preserve that relationship in both order and manifest.

Do not append an overlooked file into the middle after final numbering without a documented exception. Depending on the agreed protocol, you may need a suffix, a reserved range or a complete rerun. The important property is not one universal method but a method another reviewer can understand and reproduce.

1. 1

   Inventory

   Create the approved file list and resolve duplicates, missing files and unreadable inputs.

2. 2

   Order

   Apply the documented sort and keep document families or exhibits together where required.

3. 3

   Lock

   Freeze the production list before assigning the first identifier.

Choose a numbering pattern that will survive growth

Use a short, unambiguous prefix that identifies the production, party, custodian or matter without exposing unnecessary personal information. Select a starting number and enough zero padding for the likely maximum. Fixed-width labels sort reliably: 000001 through 999999 stays in numeric order when handled as text.

A suffix can distinguish a production or confidentiality class, but complex labels are easier to mistype and harder to place. Confirm the total label length against page margins. Keep the prefix and suffix stable within the declared range, and record every reserved or skipped interval.

Run a dry calculation before processing. If the set begins at 004501 and contains 820 pages, the expected final label is 005320. Compare that expectation with the processor's result and manifest. A simple range reconciliation catches many order and page-count mistakes early.

• Prefix: stable code for the defined production or document set.
• Start: first numeric value after accounting for prior or reserved ranges.
• Padding: fixed width large enough for the expected final number.
• Suffix: optional stable qualifier used only when the protocol calls for it.
• Placement: a location that remains readable without covering page content.

Protect content when placing Bates labels

Inspect page sizes, rotations and existing headers or footers before choosing a corner. Mixed portrait, landscape and scanned pages can put the same coordinates over very different content. A label should remain legible at normal viewing and printing size without obscuring text, signatures, page numbers, barcodes or court stamps.

Test representative extremes: the smallest page, the largest page, every rotation and pages with content close to each edge. If no safe margin exists, adding a margin or cover sheet may be preferable, but that changes layout and page geometry and must be agreed. Do not assume a white patch is harmless; it may conceal underlying evidence.

Image-only and searchable PDFs can both receive visible labels. OCR status affects searching, not whether a stamp can be drawn. If reviewers need searchable productions, run and verify the scanned PDF OCR workflow in the agreed order and remember that each later rewrite can change file identity or signatures.

Use the manifest as the production map

A useful manifest maps each source or production file to its page count, first Bates label and last Bates label. It may also record input order, output filename, timestamp, settings and warnings. The manifest lets a reviewer reconcile the set without opening every page and provides a starting point when a range is missing.

Keep the manifest beside the exact output set. If files are renamed, split, merged or compressed later, update the delivery record rather than pretending the original mapping still describes the new artifacts. Hashes can strengthen identity tracking when generated and stored by an approved process.

Review warnings instead of treating manifest creation as proof of success. An encrypted or malformed input, an unexpected blank page or a file with zero readable pages should stop or qualify the production according to policy. A complete sequence over an incomplete input list is still incomplete.

• Input order and original filename.
• Output filename and page count.
• First and last Bates identifier for each file.
• Numbering settings, warnings and any reserved ranges.
• Artifact identity information required by the matter's protocol.

Quality-control the numbered set

Compare manifest totals with the source inventory and expected numeric range. Open the first and last page of every file, plus every page-size and rotation variant. Search for labels where possible, but do not rely only on extracted text because a visible stamp may not be represented as ordinary page text in every processor or viewer.

Check that labels are unique, sequential under the agreed exception rules, legible and clear of content. Confirm bookmarks, links, OCR text, attachments and signatures according to the production specification. Any PDF rewrite may invalidate an existing certificate signature; preserve the signed source if its signature must remain verifiable.

Record approval of the exact delivered set and use a controlled sharing route. The wider private PDF workflows guide covers source preservation, output verification and retention. Bates numbering becomes defensible when those controls surround the label sequence.

1. 1

   Reconcile

   Match source page totals, manifest totals and expected first-to-last range.

2. 2

   Sample

   Inspect file boundaries, rotations, page-size variants and pages with crowded margins.

3. 3

   Exception

   Document gaps, suffixes, reruns or excluded files under the agreed production protocol.

4. 4

   Approve

   Identify and retain the exact production set and its manifest before delivery.