The platform carries the matter through the last stage of the EDRM - turning reviewed documents into a served, Bates-numbered production. No export to a second tool, no re-keying of decisions, no gap where mistakes creep in.
Decide Once, in Place
Review decisions are made right in the document viewer on any page: produce, withhold for privilege, or needs redaction. Every change is appended to an audit trail recording who decided, when, and what the prior value was - and decisions are instantly searchable as a filter, so "everything decided produce but not yet produced" is a query, not a spreadsheet.
Lock With Confidence
- Draft sets are assembled explicitly or automatically from review decisions.
- Locking a set freezes its membership and assigns Bates numbers in a deterministic order, continuing the case-wide sequence so numbers never overlap between productions.
- The privilege gate fails closed: any privilege-flagged document is withheld with a slip sheet and a privilege-log entry unless an explicit, audited override says otherwise.
- An unresolved redaction blocks the lock entirely. The safe outcome is the default outcome.
A Package You Can Defend
The built package contains Bates- and confidentiality-stamped PDFs (stamped on every page), native email files reproduced bit-for-bit from the collected mailbox, native copies of other formats, an extracted-text sidecar per document, a standard load file, the privilege log, and a manifest recording a SHA-256 hash of every artifact - so a served production can later be re-verified byte for byte. Delivery is by secure, expiring download links; serving remains an attorney action.
Works Together With
- Chain of CustodyImmutable originals, content hashing, full lineage, inventory sign-off, and append-only audit trails throughout.
- AI Issue CodingEvery document coded for issues, helpful or harmful bearing, privilege, key quotes, entities, amounts, and dated facts.
- Case IntelligenceA cited case chat, chronology, hot and adverse document queues, truth table, entity graph, and per-claim strategy pages.
Frequently Asked Questions
What exactly is in a built production package?
Bates- and confidentiality-stamped PDFs (stamped on every page), native email files reproduced bit-for-bit from the collected mailbox, native copies of other formats, an extracted-text sidecar per document, a standard load file, the privilege log, and a manifest recording a SHA-256 hash of every artifact.
How are privileged documents protected from accidental production?
The privilege gate fails closed. Any privilege-flagged document is withheld with a slip sheet and a privilege-log entry unless an explicit, audited override says otherwise - and an unresolved redaction blocks the lock entirely. The safe outcome is the default outcome.
Can Bates numbers overlap between productions?
No. Locking a set assigns Bates numbers in a deterministic order and continues the case-wide sequence, so numbers never overlap between sets - including sets produced weeks apart.
Can a served production be verified after the fact?
Yes, byte for byte. The manifest records a SHA-256 hash of every artifact in the package, so anyone can later re-verify that what was served is exactly what was built.