Gap Detection

Last updated: 2026-03-23

Hintyr detects gaps and overlaps in your Bates number sequences. Run a gap detection report to find missing numbers, duplicate entries, and discontinuities. Download the report as a CSV for production completeness verification and audit compliance.

What gap detection finds

Gap detection analyzes the entire Bates sequence in your case and flags these issue types:

  • Missing sequences - Numbers that should exist but aren't assigned to any document or page. For example, if ABC000010 and ABC000012 are present but ABC000011 is not, the report flags the gap.
  • Duplicate entries - Two or more documents or pages that share the same Bates number. Duplicates can occur if files were manually re-stamped or if numbering was applied in overlapping batches.
  • Present ranges - Contiguous blocks of properly assigned numbers. The report lists each range so you can see which portions of the sequence are complete.

Running a gap detection report

Open the file menu in the document browser and select Bates Gap Report. Hintyr scans all Bates-numbered files in the case and produces a summary showing present ranges, missing sequences, and any duplicates. The report appears in a panel where you can review it on screen or download it.

For large cases with thousands of numbered pages, the report may take a few moments. The system processes all numbered documents in the case regardless of any active filters in the document browser.

Downloading gap reports

Click Download CSV in the gap report panel to export the report. The CSV includes columns for range type (present, missing, or duplicate), start number, end number, and count. This format opens in any spreadsheet application and can be shared with counsel, production managers, or opposing parties as proof of Bates sequence integrity.

Include the CSV in your production correspondence to demonstrate a complete Bates sequence, or use it to pinpoint specific numbers that need attention before delivery.

Use cases

Gap detection helps in several situations:

  • Production completeness - Before certifying a production, run gap detection to confirm the Bates sequence is continuous from start to end with no missing numbers.
  • Audit compliance - Regulatory reviews and government investigations often demand verifiable proof that all documents are accounted for. The gap report provides that proof.
  • Dispute resolution - If opposing counsel claims that certain Bates-numbered pages are missing from a production, the gap report can confirm or refute the claim with objective data.
  • Quality control - After batch numbering or re-stamping, run gap detection to verify that no numbers were skipped or duplicated during the process.

Frequently asked questions

Does gap detection work with multiple prefixes?
Yes. If your case contains files with different Bates prefixes, the report analyzes each prefix sequence independently and reports gaps within each one.
Can I automatically fix detected gaps?
Gap detection identifies issues but doesn't re-number files automatically. Review the report, determine what caused each gap, and use manual numbering to correct any that need fixing.
How often should I run gap detection?
Run gap detection before any production delivery and after major numbering operations. For rolling productions, run it before each delivery to verify the latest batch.

Related articles