eDiscovery Document Production Organization

In litigation and regulatory investigations, parties exchange relevant documents through a process called document production. When those documents are electronic, such as emails, spreadsheets, PDFs, chat exports, and scanned images, the production is part of eDiscovery. eDiscovery document production organization covers how those files are packaged: the folder hierarchy, file naming, volume numbering, and the load files that tell a review platform how the pieces fit together.

A typical ediscovery production folder structure follows a predictable pattern. Each production volume (for example, VOL001) contains subfolders such as IMAGES for TIFF or PDF page images, NATIVES for files produced in original format like spreadsheets, TEXT for extracted or OCR text, and DATA for load files such as DAT and OPT files. Documents are usually named by their beginning Bates number so every file can be matched to its metadata record.

This matters because a disorganized production creates real problems. Missing files, mismatched Bates ranges, or inconsistent folder layouts can lead to meet-and-confer disputes, re-productions, and questions about whether discovery obligations were met. Clean organization also helps your own team, since the same structure makes it easier to track what was produced, when, and under which protective order designation.

Production organization starts well before export. Collected ESI is processed, deduplicated, reviewed for responsiveness and privilege, and then assigned Bates numbers in a defined order, often by custodian and date. The review platform or processing tool then exports the production set into the agreed structure, which is frequently specified in an ESI protocol or stipulated order negotiated between the parties. That protocol typically defines image format, which file types are produced natively, required metadata fields, and the load file format.

During export, each document is written to the correct subfolder and named after its Bates number, while the load files record fields like BegBates, EndBates, Custodian, DateSent, and the relative paths to images, natives, and text. Large productions are split into numbered volumes, and subfolders are often capped at a set number of files so they remain manageable. Before delivery, the team runs quality control checks: confirming Bates ranges are continuous, every load file path resolves to a real file, and privileged documents are withheld and logged.

Outside the formal review platform, legal teams still handle many loose files: incoming productions from other parties, cover letters, privilege logs, ESI protocols, and correspondence. Sortio can help organize these supporting materials using natural language prompts, such as sorting incoming productions into folders by matter, producing party, and date received. Sortio does not assign Bates numbers or generate load files, so it complements rather than replaces your eDiscovery platform. Because it backs up files before making changes, you can revert a sort if the result is not what you intended.