A load file pairs the Bates numbers stamped on a PDF with metadata a review platform can index. Concordance-style DAT files carry BEGBATES, ENDBATES and BEGATTACH fields at the document level, while Opticon OPT files map each individual page image to its own Bates-numbered key, and any mismatch between the two breaks the import. The two files describe the same production at different resolutions, so they have to agree: the page keys listed in the OPT must fall inside the BEGBATES-to-ENDBATES span the DAT claims for that document, and attachment ranges must point at documents that actually exist in the volume. Delimiters are a common failure point, because Concordance files traditionally use non-printable characters rather than commas, and a field containing a stray delimiter silently shifts every column after it. Validating a small sample import before delivering the full volume catches most of these problems cheaply.

This guide explains legal Bates workflows. BatesFast applies the identifiers; it does not replace review, redaction, or production validation.
What a Load File Actually Carries
Stamping Bates numbers onto a PDF is only half the job when the output is headed into a document review platform. The platform needs to know, for every document, what its Bates range is, what metadata fields apply, and where the underlying page images live on disk. That information travels separately from the PDF itself, in one or more load files.
When the agreed delivery uses document metadata plus page-image imports, Concordance-style DAT and Opticon OPT are common companion formats. Direct PDF delivery does not automatically require either. Confirm the receiving platform, field mapping, delimiters, encoding and production specification before generating files.
BEGBATES, ENDBATES, and BEGATTACH in a DAT File
A DAT file holds document-level metadata in a delimited text format. Configure the delimiter, text qualifier and encoding for the receiving importer; a displayed pilcrow is not a universal byte-level delimiter. For example, Relativity’s import specification identifies the default column delimiter as character 020 and allows it to be configured. Match the actual code point and encoding, not a symbol copied from a web page.
BEGATTACH is a third field used for document families, most often email threads with attachments. It holds the Bates number of the first page of the parent document in the family, so an attachment three levels deep in a thread can still be traced back to where its family begins. A reviewer filtering by family, rather than by individual document, relies entirely on BEGATTACH being populated correctly.
| Field | Meaning | Example value |
|---|---|---|
| BEGBATES | First Bates number of this document | ABC000001 |
| ENDBATES | Last Bates number of this document | ABC000008 |
| BEGATTACH | First Bates number of the parent family | ABC000001 |
| PAGECOUNT | Total pages in this document | 8 |
How Opticon OPT Files Map Bates Numbers to Page Images
An Opticon OPT row represents one page image. Its fields identify the page, optional volume and image path; field four marks a document’s first page with Y. The optional seventh field stores document page count, not that page’s ordinal position. Relativity Import/Export does not require or use that seventh field; check the receiving importer’s convention.
The image key in an OPT row is exactly the Bates number stamped on that page, which is what ties the physical page image back to the numbering visible when someone views or prints the page. If the OPT file lists ABC000005 as a page image but no page in the actual production carries that stamp, the review platform has an image key with nothing behind it.
Why Mismatched Ranges Break Review Platform Imports
Review platforms validate a load file import by cross-checking the DAT file's declared ranges against the OPT file's actual page keys. When ENDBATES in the DAT file says a document ends at ABC000008 but the OPT file's last page image for that document is keyed ABC000009, the platform either rejects the import outright or, worse, imports it with a silent page miscount that surfaces later during review.
This is why the stamping step and the load file generation step must use identical ranges. If a PDF gets re-stamped after a load file was already generated, for example to fix a typo on one page, the load file has to be regenerated too, because the old DAT and OPT rows now describe a Bates sequence that no longer matches the file on disk.
Building a Load File That Matches Your Stamped PDFs
The safest sequence is to finalize Bates stamping first, verify the ranges using the checks described in our how to Bates number a PDF guide, and only then generate the DAT and OPT files from the finished, stamped output. Generating load files before stamping, or stamping again after load files exist, is the most common source of the mismatches review platforms flag.
For productions spanning many files, apply the same continuous-range discipline covered in our batch Bates numbering guide: lock file order, verify no collisions with prior productions, and only then generate load files against the final, confirmed range.
Common Fields Beyond BEGBATES and ENDBATES
Most DAT files carry a handful of additional fields alongside the Bates range that reviewers rely on daily. CUSTODIAN identifies whose files a document came from, useful for filtering a review by individual. PARENTDOCID and CHILDDOCID track family relationships more granularly than BEGATTACH alone. CONFIDENTIALITY often carries a designation stamped directly on the page, such as "Confidential" or "Attorneys' Eyes Only," which should be tracked as metadata even though it is also visible on the page image itself.
None of these additional fields replace BEGBATES and ENDBATES; they extend the same document-level row with context a reviewer needs beyond just locating the page range. Getting the Bates fields right first matters most, because every other field in the row is indexed against that same document, and a wrong Bates range undermines the reliability of everything else in that row.
Testing an Import Before Final Delivery
Before delivering a load file to opposing counsel or uploading it to a shared review platform, run a test import into a scratch workspace if the platform supports one. Confirm the document count matches the number of documents in the DAT file, the total page count matches the sum of pages implied by the OPT file, and a handful of spot-checked documents open with the correct Bates range visible on the correct pages.
This test costs a few minutes for even a large production and catches the two most common load file errors: an off-by-one range from a late re-stamp, and a broken image path from files being moved after the OPT file was generated. Both are far cheaper to fix before delivery than after opposing counsel reports a failed import.
Background on the discovery and review workflows that these load file formats support is covered in general references such as Wikipedia's entry on litigation support.
BatesFast handles prefixes, digit padding and continuous batch ranges, so the output matches the production specification you agreed.
Common questions
What is BEGATTACH in a DAT load file?
BEGATTACH holds the Bates number of the first page of the parent document in a family, so every attachment in an email thread can be traced back to the family's starting page even when each attachment has its own BEGBATES and ENDBATES.
What is the difference between a DAT file and an OPT file?
A DAT file carries document-level metadata. An OPT file maps page-level image identifiers and paths; field four marks a document break. Its optional seventh field is document page count, not page position, and support depends on the receiving importer.
Why would a review platform reject a load file import?
The most common cause is a mismatch between the Bates range declared in the DAT file and the actual Bates-numbered pages listed in the OPT file, such as a document's ENDBATES not matching the last page image key associated with that document.
Do I need a load file if I am only sharing a stamped PDF directly?
No. Load files are only needed when importing into a document review platform that indexes documents by metadata and page images separately. Sharing a stamped PDF directly does not require a DAT or OPT file.
Why do load-file imports fail most often?
Check the importer’s delimiters and encoding, required field mapping, image paths, document boundaries and Bates ranges. A wrong delimiter or a range that does not match the delivered images can prevent a reliable import. Test a small sample before delivery.
Is a PDF-only production acceptable?
Follow the agreed delivery format and receiving system’s requirements. Direct PDF delivery does not automatically require DAT or OPT files. If metadata and page-image imports are required, validate the requested files together before delivery.