WorkhogWORKHOG

Free document-production tool

Produce documents for discovery — Bates numbers and a load file, without a Bates hole

Drop your PDF set. A production associate stamps every page, applies your confidentiality legends, builds the Concordance / Relativity / CSV load file, and runs an integrity check — a stamped set, a load file, and a production index, ready to hand over.

Drop your documents here — or choose files

PDFs. Nothing is uploaded until you run the production.

How to produce documents for discovery with Bates numbers and a load file

A defensible production has three parts: Bates-stamped pages (one sequential number per page, conventionally lower-right, plus any confidentiality legend), a load file (a delimited file — Concordance .DAT + Opticon .OPT, a Relativity-style .DAT, or a generic .CSV — that tells the receiving tool each document's Bates range, custodian, and designation), and a production index mapping every original filename to its Bates range. The two failure modes that get a production challenged are a Bates hole (a gap in the sequence) and a duplicate Bates number — so the last, non-optional step is an integrity check: no gaps, no duplicates, every document present in the load file, every designation applied.

Load-file field reference

The standard fields a production load file carries, one row per document. These map cleanly into Concordance, Relativity, and most review platforms. Download the CSV template ↓

FieldWhat it holdsExample
BegBatesFirst Bates number of the documentSMITH000001
EndBatesLast Bates number of the documentSMITH000004
BegAttachFirst Bates number of the attachment family (the parent's BegBates)SMITH000001
EndAttachLast Bates number of the attachment familySMITH000012
CustodianThe person or source the document was collected fromJane Smith
ConfidentialityDesignation legend applied to the documentCONFIDENTIAL
DocDateDate of the document (sortable, ISO where possible)2024-03-14
DocTypeDocument type / family roleEmail / Attachment
PageCountNumber of pages in the document4
OriginalFileNameSource filename before stamping (for your index)closing statement.pdf

Concordance .DAT delimiters: (ASCII 20) field separator, þ (ASCII 254) text qualifier, ® (ASCII 174) in-field newline. A companion Opticon .OPT marks a document break (Y) on each document's first page.

The defensible-production checklist

  1. 1Validate the set first. Separate out encrypted, corrupt, and image-only (scanned, no text layer) files. Image-only pages must be OCR-processed before stamping, or the load file has no searchable text.
  2. 2Fix off-size and image pages. Convert stray images and non-standard page sizes to standard 8.5×11 so the Bates endorsement never runs off the page or over content.
  3. 3Number sequentially with a consistent scheme. One Bates number per page, same prefix and zero-padding throughout. If a prior production exists, continue from the last number used — never restart.
  4. 4Endorse designations correctly. Apply CONFIDENTIAL / ATTORNEYS’ EYES ONLY exactly where the protective order requires — and record each in the load file’s Confidentiality field.
  5. 5Keep attachment families together. A parent email and its attachments share a contiguous Bates range; BegAttach/EndAttach span the whole family.
  6. 6Build the load file in the requested format. Concordance DAT + OPT, Relativity-style DAT, or CSV — with every field the receiving platform expects populated.
  7. 7Produce an index and run the integrity gate. Map original filename → Bates range → page count → designation, then verify: no duplicate numbers, no gaps, every document in the load file, every designation applied.

Why run this in a workspace instead of a one-off stamper

A stamper stamps once and forgets. Real productions come in waves, and the numbering has to carry forward without collisions. On Workhog the production lands in a private workspace that remembers the matter's Bates scheme — the prefix, the padding, and the last number used — so the next rolling set continues from where the last one ended, re-applies the same designations, and appends to the running load file and production log. It is the same file system that has assembled real forensic productions for practitioners — for example combining months of statements into a single Bates-stamped, sequentially numbered exhibit set for a contested matter. The agent stamps, builds the load file, indexes, and grades its own work against a no-Bates-hole integrity check before you hand anything over — and shows the sources for every number it assigned, so you can verify rather than trust.

Producing documents with Bates numbers and a load file — FAQ

What is a load file in document production?

A load file is a delimited text file that tells an e-discovery platform (or opposing counsel’s review tool) how to import your produced documents — which pages belong to which document, each document’s Bates range, its custodian, and its confidentiality designation. The two common shapes are a Concordance-style .DAT (metadata, one row per document) paired with an Opticon .OPT (an image cross-reference that marks where each document begins), and a generic .CSV. Without a matching load file, a production is just a pile of stamped PDFs the other side has to re-organize by hand.

What is a "Bates hole" and why does it matter?

A Bates hole is a gap in the Bates sequence — e.g. the numbering jumps from SMITH000120 to SMITH000122 with nothing at 000121. Because Bates numbers are the shared reference for every document in a case, an unexplained gap looks like a document was withheld or lost, and it invites a challenge from opposing counsel or the court. Duplicate Bates numbers are the mirror-image problem: two different pages carrying the same identifier. A defensible production has neither — every page has exactly one number, in an unbroken run (unless a gap is intentional and logged).

How do I keep Bates numbers from colliding across rolling productions?

Productions come in waves — an initial production, then supplemental sets. The rule is to never restart numbering: the next production continues from the last Bates number used. If your first production ended at SMITH004312, the next one starts at SMITH004313 with the same prefix and padding. That means the last-used number is a fact you have to carry forward. A workspace that remembers the prefix, padding, and last number for the matter continues automatically; a one-off tool that forgets it is how collisions happen.

What do CONFIDENTIAL and ATTORNEYS’ EYES ONLY endorsements do?

They are the confidentiality designations from a protective order. CONFIDENTIAL limits who may see a document; ATTORNEYS’ EYES ONLY (AEO) is stricter — typically only outside counsel and experts, not the opposing party itself. The designation is endorsed on the page (usually near the Bates number) and recorded in the load file’s Confidentiality field so the receiving side’s tool enforces it. Getting this wrong — stamping an AEO document only CONFIDENTIAL — is a disclosure error, which is exactly why the integrity check verifies every designation was applied.

What are the Concordance DAT delimiters?

A Concordance/Relativity .DAT uses non-printing characters so real commas and quotes inside a field don’t break the file: ¶ (ASCII 20) separates fields, þ (ASCII 254) qualifies (wraps) text values, and ® (ASCII 174) marks a newline inside a field. The first row holds the field names. A companion Opticon .OPT image cross-reference lists each image with a "Y" in the DocBreak column on the first page of every document and blank on continuation pages — that is how the platform knows where one document ends and the next begins.

Can I do this without a Relativity or Everlaw seat?

Yes. Bates numbering, confidentiality endorsements, and load-file generation are mechanical steps that do not require an enterprise e-discovery platform — they require getting the numbering math and the load-file fields exactly right. This page runs the whole production for you: you upload the set, and an agent stamps every page, builds the load file in the format the other side asked for, produces the index, and verifies there are no Bates holes — then hands you a set you can deliver to a platform or to opposing counsel directly.

Produce Documents for Discovery: Bates Numbers + a Load File (Free Tool) | Workhog