What information does a court-mandated discovery run log actually require?

A discovery run log is the only thing standing between a successful document production and a motion for sanctions when a numbering gap is discovered. In 2026, simply providing a list of file names isn't enough to satisfy the technical requirements of most court-approved production standards. A defensible log must provide a granular, verifiable link between the original source file and the final Bates-stamped output.

Without a structured log, your firm lacks a technical backstop. If a judge asks how you verified that a 20,000-page production is sequential and complete, "we checked it manually" is rarely an acceptable answer for modern litigation support.

The fundamental components of an audit-ready log

A professional run log serves as a map. It tracks the transformation of data from a raw discovery dump into a formal production set. At a minimum, your log should include the original file name, the file size, and the corresponding Bates range assigned to that specific document. This allows any third party to reconstruct the sequence if the integrity of the production is challenged.

Required Field	Purpose in Litigation	Impact of Omission
Original Filename	Identifies source data for chain of custody.	Impossible to trace specific documents back to the client.
Page Count	Verifies the physical volume of the document.	Metadata discrepancies can hide missing pages.
Bates Start	Defines the beginning of the evidentiary sequence.	Sequence breaks go unnoticed until trial.
Bates End	Defines the conclusion of the document set.	Cross-referencing becomes a manual nightmare.
Processing Timestamp	Records when the production was finalized.	Vital for meeting 11:59 PM filing deadlines.

Why file metadata and Bates sequences must stay synced

When we process documents for production, the biggest risk isn't just a typo in the prefix; it's a drift in the metadata. If your run log says a PDF has 40 pages but the Bates stamp sequence only accounts for 38, you have a non-compliant production. This usually happens when software fails to account for hidden layers, attachments, or non-standard page sizes during the labeling process.

Modern legal teams use automated Bates labeling software to generate these logs simultaneously with the stamping process. This ensures the log isn't just a separate spreadsheet—it's a direct reflection of the pixels placed on the page.

The risk of external data handling in log generation

Many firms mistakenly believe that generating these logs requires a heavy cloud-based e-discovery suite. This is a misconception that creates a massive security liability. Every time you upload a sensitive discovery set to a remote server just to generate a run log, you're creating a potential data exfiltration point.

In 2026, the standard for confidentiality is local processing. Your documents should never leave your device. The run log should be generated inside your local browser environment, ensuring that the sensitive contents of the discovery remain behind your firm's firewall while the software handles the high-scale mathematics of sequential numbering.

Core checklist for verifying a production log:

• Prefix Validity: Does the prefix match the court order exactly (e.g., PLTF_001)?
• Sequential Integrity: Is there any overlap between document A's end number and document B's start number?
• Checksums or File Sizes: Does the log record the original file size to prevent accidental document swaps?
• Exclusion Notes: Does the log clearly identify files that were skipped (e.g., corrupt files or password-protected PDFs)?

Frequently Asked Questions

Does a run log replace a privilege log?

No. A run log is a technical record of the production's physical sequence. A privilege log is a legal document explaining why certain materials were withheld. However, the run log is often used as the foundation for identifying where redacted documents fall within the total production volume.

Can a run log be generated after the documents are stamped?

It's technically possible but legally risky. Reconstructing a log after the fact relies on manual data entry or OCR, both of which are prone to error. An audit-ready run log should be generated in real-time as the Bates labeling software applies the stamps to ensure 100% accuracy.

Why are page counts frequently wrong in manual logs?

Manual logs often fail to account for landscape rotations or mixed-media files (like a JPEG inserted into a PDF). Automated processing identifies the true page count of every file in the batch, ensuring the Bates-sequential numbering remains perfectly aligned with the actual document volume.

Do I need special software to open a run log?

No. Most court-approved formats utilize standard CSV or XLSX files. These are widely accepted because they are easily searchable and can be imported into any database for quick verification during a meet-and-confer session.

Sources / Further reading: Federal Rules of Civil Procedure (Rule 34), E-Discovery Reference Model (EDRM) production standards.