Finalize the source pages
Resolve page rotation, missing pages and the intended file order. Check that there is a clear location for a visible identifier on every page size.
Calculate document ranges, check stamp placement and verify the delivered files. BatesFast applies the prefixed, zero-padded identifiers across your PDF set.

One continuous sequence. Every page carries its own identifier.
A Bates-stamped PDF has a visible, unique identifier on each page so it can be referenced within a document set. A Bates workflow includes the numbering scheme, file order, continuous ranges and verification of the delivered files. Plan those here; BatesFast applies prefixed identifiers with the digit padding and batch continuity a production needs. Confirm any load-file requirement against the receiving specification.
Bates numbering adds page identifiers; OCR recognizes text inside scanned pages. Choose the tasks your files need separately, then inspect the delivered PDF for correct labels, readable placement and any searchability the workflow requires.
| PDF task | When it fits | Constraint to check |
|---|---|---|
| Bates numbering only | The PDF already has usable text and needs a visible page reference. | Test stamp placement on rotated and mixed-size pages; verify the first and last labels in every file. |
| OCR only | Image-only scans need searchable or selectable document text. | Check the recognized text against the scan; OCR does not reserve or apply a continuous Bates range. |
| OCR and Bates numbering | Scanned files need both searchable content and page identifiers. | Verify document-text searches and label searches independently in the final output. |
| Continuous batch numbering | Several PDFs must share one planned sequence. | Lock file order and page counts before stamping, then reconcile file boundaries with the range ledger. |
Documentation: Adobe Acrobat Pro: batch file order and Bates number settings · Adobe Acrobat: recognize text in scanned PDFs
Workflow guidance updated .
Agree the scheme, lock the file order, then number the set in BatesFast.
Resolve page rotation, missing pages and the intended file order. Check that there is a clear location for a visible identifier on every page size.
Start from the first unused number. Add each file's page count, subtract one for its final number, and record the next starting point.
Check continuous ranges across filesOpen BatesFast and choose the prefix, digit width, first number and stamp position. Run the set, then verify each document’s first and last identifier against the ledger.
The end of a range is start plus count minus one. Writing the arithmetic down prevents the next file from sharing the previous file's last number.
Mixed sizes, landscape exhibits and existing footers need a placement review so the stamp remains visible without hiding material.
Compare the final files with the range ledger, including every document's first and last page and the total produced count.
The earlier production ended at DOC-000250. This illustrative continuation contains 18, 9 and 23 pages. Plan the continuation here, then apply it in BatesFast.
WORKED EXAMPLE| Document | Pages | BEGBATES | ENDBATES |
|---|---|---|---|
| File A | 18 | DOC-000251 | DOC-000268 |
| File B | 9 | DOC-000269 | DOC-000277 |
| File C | 23 | DOC-000278 | DOC-000300 |
18 + 9 + 23 = 50 pages; 300 − 251 + 1 = 50 identifiers. The next series would begin at DOC-000301. BEGBATES and ENDBATES refer to the first and last page identifiers of each document.
Work through the essentials for this workflow.
Your checklist stays on this page.
0 of 6 checks complete
Bates number your PDFHow to run continuous Bates numbering across hundreds of PDFs: folder order pitfalls, collision checks, and output naming by Bates range.
Read the guide FIELD NOTE / 02How BEGBATES, ENDBATES, and BEGATTACH work in Concordance DAT and Opticon OPT load files, and why mismatched ranges break review imports.
Read the guide FIELD NOTE / 03Scanned pages are images, so stamped identifiers and document text behave differently. How OCR, stamping order and searchable output fit together in a production.
Read the guideThe practical details, explained plainly.
Yes. BatesFast is built for prefixed, zero-padded identifiers that continue across a multi-file set, which is the pattern used in the table above. Check placement on landscape and mixed-size pages before running the full production.
BEGBATES identifies the first page of a document; ENDBATES identifies its last page. For a continuous range, the document's page count equals the numeric end minus the numeric beginning plus one.
A merged PDF alone does not replace a document-level ledger or load file. Preserve the original boundaries and metadata required by the receiving workflow when preparing a combined working copy.
That is fine for ordinary page numbering but would repeat identifiers in a continuous Bates series. For a production, use the agreed unique format and confirm how numbering carries across files.
Visible page content and PDF viewer page labels are different things. Check both when they matter to the workflow; a stamp on the page does not imply that navigation labels have changed.
For the underlying legal and PDF conventions:
Number a mixed PDF set while maintaining one sequence across files. Prepare scans and searchable text before final stamping when required.
Check rotation, document boundaries, stamp overlap and exported ranges. Confirm OCR and load-file requirements separately.
Prepare scanned and mixed-size files →
Google sign-in is required. One complete production is free, with downloads available for seven days. Further productions require a paid per-device license. Check the current BatesFast price, offer and refund terms before purchase.
View current BatesFast plans →
This is a product-operated field guide in the PDFImpose network. Confirm the exported result and current terms before paying.
Apply the identifiers in BatesFast, then use the range plan above to verify every document before the production goes out.
Bates number your PDF