July 4, 2026
Which metadata markers are essential for court-mandated discovery run logs?
A discovery run log isn't just a list of files. It’s the definitive record that proves every document was processed, numbered, and accounted for without any gaps in the chain of custody. In 2026, cour
A discovery run log isn't just a list of files. It’s the definitive record that proves every document was processed, numbered, and accounted for without any gaps in the chain of custody. In 2026, courts increasingly demand more than a visual scan of Bates stamps; they want a data-backed trail that verifies the production’s integrity. If you can’t show exactly where one document ends and the next begins across a 50,000-page set, you’re inviting a motion to compel.
We’ve found that the most defensible productions rely on logs generated simultaneously with the labeling process. This eliminates the clerical drift that happens when a paralegal tries to reconstruct a sequence after the fact. A proper log should serve as an immutable map of the entire production.
The four pillars of an audit-ready production log
To meet court-approved formats, your documentation needs to link the original file state to its produced state. If you simply provide a list of Bates numbers without referencing the source filenames or page counts, the receiving party has a valid reason to question the production's completeness.
We prioritize these four data points for every production batch:
- Original Filename vs. Bates Range: The direct link between the file on your local drive and its corresponding range (e.g., ABC-0001 to ABC-0045).
- Sequential Integrity Check: A verification that no numbers were skipped and no duplicates were created during the batch run.
- Timestamped Processing Data: Proof that the production happened on a specific date, which is critical for meeting discovery deadlines.
- Local Execution Hash: Verification that the files were processed locally, ensuring the data stayed within your firm’s secure environment.
Comparison: Manual logs vs. automated discovery logs
| Feature | Manual Spreadsheets | Automated Run Logs |
|---|---|---|
| Entry Speed | 5-10 minutes per batch | Instant (sub-millisecond) |
| Error Risk | High (typos, skipped numbers) | Zero (algorithmic sequencing) |
| Chain of Custody | Anecdotal/Human-verify | Audit-ready/System-verify |
| Scale | Limits at ~100 files | Production-scale (unlimited) |
| Matter Consistency | Dependent on memory | Forced by prefix settings |
Why local processing is the only way to generate secure logs
When you use a cloud-based service, your log is usually generated on a remote server. This creates a security gap. If the server goes down or your connection drops during a massive 4GB production, that log is either lost or incomplete.
By keeping the processing local—meaning the documents never leave your device—the run log is generated directly in your browser’s memory. It’s faster because there’s no upload lag, and it’s safer because the internal file structure of your client’s sensitive discovery remains behind your firewall. At OmniBates, we built our workflow around this privacy-first architecture. The resulting log isn't just a report; it’s a technical safeguard.
Essential metadata to include in your 2026 production sets
Don't settle for just "Bates Beginning" and "Bates End." To truly insulate your firm from metadata challenges, your log should include the page count per file and the specific prefix used. This is especially important when you’re dealing with mixed-media discovery—combining professional scans with smartphone photos and variable-sized PDFs.
- Prefix consistency: Ensure every file in a specific matter uses the exact same character string.
- Leading zeros: Maintain a uniform digit count (e.g., 000001 vs 1) to ensure files sort correctly in litigation databases.
- Suffix handling: Clearly mark if any documents required specialized suffixes for late-additions to a production set.
FAQ: Standardizing your discovery run logs
Do I need a separate log for every folder in a discovery production?
It’s better to have one master log per production volume. This makes it easier for the receiving counsel to verify the entire sequence in one go. If you process in batches, look for software that can append new runs to an existing audit trail to keep the sequence clean.
How does a run log help with missing Bates pages?
If a judge asks why there is a jump from page 10 to page 15, a manual spreadsheet might not have the answer. An automated log will show if those pages were intentionally excluded (e.g., for privilege) or if it was a technical error. It provides an immediate answer during high-stakes hearings.
Can I export these logs to Excel or CSV?
Yes. Any professional Bates labeling software should export in structured formats like CSV. This allows technical staff to import the data into larger e-discovery platforms or litigation databases without manual data entry.
Does OmniBates store my production logs on their servers?
No. Because we use local processing, your documents—and the logs describing them—never leave your machine. You download the log directly from your browser once the production is finished. We have no access to your client data or your production history.
Source: OmniBates Audit-ready Run Logs