Productions & eDiscovery

This guide covers the discovery‑production side of litigation: building productions you hand to other parties, tracking received productions, maintaining a privilege log, and bulk‑importing documents through eDiscovery intake.

These are litigation‑mode features.

Productions (outbound)

A production is a formal set of documents handed to another party, with Bates numbering and stamping. In the Productions workspace you:

1. Select the documents to produce.
2. Choose a numbering scheme (Bates prefix and padding) and export format.
3. Generate the production — Sentinel stamps the documents and tracks progress.
4. Download the export and keep a record of what was produced.

Bates defaults (prefix, padding) can be set tenant‑wide in tenant settings; you can override per production.

Received productions (inbound)

When you receive a production from an opposing party, track it under Received Productions. You can review opposing documents in the same review workspace (filtered to the opposing set) and tie received items back to your document requests.

RFP coverage

RFP Coverage links received production items to your requests for production and tracks which requests have been satisfied — so you can see, at a glance, what the other side has and hasn't produced against each request.

Privilege log

The Privilege Log records documents withheld or redacted on privilege grounds. Each entry captures the document's metadata, the privilege type (e.g. attorney‑client, work product), the basis, whether it's a full or partial redaction, and review status. The log is a searchable, sortable table you can filter and export (for example to serve a privilege log on opposing counsel).

Documents are typically added to the privilege log during Document Review as reviewers make privilege calls.

Review Intelligence (TAR / CAL)

For large collections, predictive coding prioritizes and measures review. See Document Review → Predictive coding.

eDiscovery intake (bulk ingestion)

eDiscovery Intake is the path for bringing large volumes of documents into a matter — bulk uploads and email archives that flow through the same ingestion pipeline (parse → split → OCR/extract → embed → complete) as everything else, so the collection becomes searchable and reviewable. See Core Concepts → The content pipeline.

A typical discovery flow

1. Collect custodian data into the matter (uploads, mailbox sync, eDiscovery intake).
2. Review and code documents, making responsiveness and privilege calls.
3. Log privilege for withheld/redacted documents.
4. Produce responsive, non‑privileged documents with Bates stamping.
5. Track received productions from the other side and map them to your RFPs.

Tips

• Set tenant‑wide Bates defaults once so productions are consistent across the team.
• Use saved searches and bulk coding to define and clear review batches before producing.
• Keep the privilege log current during review rather than reconstructing it at production time.