A load file is a structured data file that accompanies a set of produced documents and contains metadata, text extracts, and organizational information needed to import those documents into a review platform. Load files enable searchability, sorting, and document relationship tracking. They're the standard mechanism for transferring document collections between litigation support systems.
What is a load file?
Load file formats are primarily governed by industry convention rather than federal rules, though FRCP Rule 34(b)(2)(D)-(E) addresses the form of production and requires that ESI be produced in a reasonably usable form. In practice, the specific load file format is typically negotiated between the parties or specified in a court order, often as part of the FRCP Rule 26(f) conference or an ESI protocol.
The most common load file formats include Concordance DAT files, which use delimited text with metadata fields such as Bates numbers, custodian, date, author, and document type. Opticon OPT files serve as image cross-reference files, mapping Bates numbers to the corresponding image files in a production set. These formats have become de facto standards in the e-discovery industry, and the Sedona Conference provides guidance on production formats and load file specifications.
A well-structured load file typically contains document-level metadata (custodian, date ranges, file types), page-level information (Bates numbers, image file paths), extracted or OCR text references, and family relationship data linking parent documents to their attachments. Without a properly formatted load file, a production set is little more than an unorganized collection of files.
"The load file is the backbone of any document production. Without accurate metadata mapping and consistent formatting, even the most thoroughly reviewed document set becomes unusable upon receipt."-- The Sedona Conference, Commentary on ESI Production Formats
Load file standards and common issues
Load file quality directly impacts the efficiency of document review and production workflows:
- According to EDRM data, misformatted or incomplete load files are among the top causes of production re-work, adding weeks to discovery timelines.
- A properly structured load file can reduce document ingestion time from days to hours by automating metadata assignment and document organization.
- Common load file errors include mismatched Bates number ranges, missing text file references, incorrect delimiter encoding, and broken family relationship links.
- Industry best practice is to validate load files before delivery by checking record counts, verifying file path references, and confirming that all Bates ranges are accounted for.
Load files in Hintyr
Hintyr generates standard-format load files during the production export process. Load files are created automatically as part of every export, ensuring that the receiving party can import the production into their review platform without manual formatting.
Export options allow you to configure which metadata fields are included in the load file, text extraction settings, and image conversion preferences. Bates numbering information is automatically included in load file metadata, linking each document and page to its assigned Bates range.