guide

Why Bates numbers land in the wrong order across files

When you number a folder of PDFs in one pass, the numbering follows the order the files were added, which is usually alphabetical by filename - and neither the filename order nor the file-modified order is the order a production is served in. The sequence is still continuous, so nothing looks wrong until a receiving party reads the set. The check that catches it compares the Bates range of each file against the order the files are meant to appear.

How the wrong order happens

Numbering tools take a list of files and number them front to back. The list usually comes from a file picker or a folder drop, so it is sorted by name. VOL0002 then VOL0010 sorts before VOL0003 in a plain string sort, and a production that was served volume by volume ends up numbered in an order no one intended.

The result is a set where every number is unique and the sequence has no gaps. That is exactly why it survives a visual check: the defect is not in the numbers, it is in the mapping between numbers and documents.

What the order check looks at

The audit reads the Bates stamp from each page, groups the stamps by file, and asks whether the range boundaries are monotonic across the set in the order you declared. A file whose start number is lower than the previous file's end number is reported as out of order, with both filenames and both pages named.

  • A gap inside a file is reported against that file and page.
  • A duplicate number is reported against both occurrences.
  • A change of prefix or padding mid-set is reported as a warning, because it usually means two numbering runs were merged.

The fix is renumbering, and that is a different job

We do not stamp or renumber at launch - stamping and index generation are the fix, and they ship with Prepare. What this check gives you is the exact list of files and pages that would need it, and the range each file currently occupies, so the renumbering run is a decision rather than a guess.

Frequently asked questions

Can I reorder files and number them again in one pass?

Yes, in whichever tool you use for numbering. The check does not care how the numbers were applied; it cares whether the finished set runs in the order it will be served.

Does the audit change my files?

No. Every input is hashed before and after the run, and a run that changed an input fails. The audit is read-only by construction.