Skip to content
BatesKit

QA

A QC pass before you certify

The receiving side runs QC on every production. BatesKit runs the same checks first — numbering gaps, duplicates, mixed page geometry, scans, and filename coverage — so a returned production never becomes a credibility cost.

A photograph of a reviewer working down a document checklist with a pen.

The numbers are the inventory

No gaps and no duplicates — any break means a missing or double document. Every output filename carries its beginning number, so a reviewer can jump to a page without opening files one by one.

What the QA pass checks

Numbering integrity

Adjacent ranges must not gap or overlap the ranges you already used, and no page may already carry a Bates-like number from a previous production — two sequences on one page is a citation hazard.

Content

No two files with identical content hashes — a document produced twice is one of the most common QC failures. No privileged metadata, no recoverable text under redaction bars, no unapplied redact annotations. Scans are flagged so the receiver knows there is no text layer.

Geometry

Mixed page sizes and rotations are legal and common, but they are what breaks a stamped number’s position. Each page is measured on its own, and the tool flags the mixed set so the person signing the certification knows it was checked.

Certify with confidence

The QA report lists every finding with a page number and a plain-language explanation. Free on one file up to 25 pages.