1. Litigation Management
  2. Features
  3. Documents and productions
Feature · Documents and productions

Documents and productions

Connect document revisions, privilege review and recipient records.

OverviewUnreviewed legal documents
Litigation Management · Documents and productions

Unreviewed legal documents

Legal documents

New
MatterTitleRevisionPrivilegeContent hashApproved by
MTT-29458Unreviewed ld-992160UnreviewedCH-211AB-850
MTT-23913Unreviewed ld-501140UnreviewedCH-353AB-833
MTT-21023Unreviewed ld-690240UnreviewedCH-313AB-467
MTT-89825Unreviewed ld-419150UnreviewedCH-775AB-187
MTT-40704Unreviewed ld-187440UnreviewedCH-309AB-753
6 of 6 records
Unreviewed ld-992Legal documents · LD-10774
Unreviewed
MatterMTT-29458
Revision160
Content hashCH-211
Approved byAB-850
Example screen with sample data

What you can do

Keep a document's identity through production

A legal document belongs to a matter and carries a title, revision, privilege state, content hash and approval name. The file attachment can hold the document itself. A production is a separate record identifying when the document was sent, its recipient, authorization reference and production hash. These facts allow the team to distinguish an internal version from the material actually produced.

How the work is organized

Counsel checks the document revision and privilege state before authorizing a production. The coordinator should record a recipient and authorization reference for the specific document involved. The production hash ties that record to the content sent. Keep the produced revision as its own document record, linked from the production. Its content hash and production hash let a reviewer distinguish it from a later working version.

  • Review privilege explicitly. Unreviewed material calls for counsel’s decision before sharing.
  • Identify the revision. A title alone cannot distinguish changed content.
  • Record the recipient. Production evidence explains where the authorized material went.

What to agree during setup

Agree the convention for document revisions, content hashes and approval names. Decide which attorney reviews privilege and how the team records authorization references. Prepare a document that changes after counsel’s first review and another that contains material marked Privileged. Check how the production record identifies the exact content sent without overwriting either revision.

Check the handoff on an actual case

A response draft is attached to an active matter. The team records its first revision and content hash, while counsel reviews privilege. After comments, the revised document receives a new revision and hash. Counsel approves the version to send and gives the coordinator the authorization reference. The coordinator records the recipient, production date and hash of the produced material.

Later, an auditor asks what was sent and under whose authority. The team can open the matter, find the production, and compare its document link and production hash with the approved revision. Keep the later working version as a separate document record so the production still points to the version that was sent.

What your team sees

  • Unreviewed legal documents — Matter documents awaiting a privilege decision.
  • Matters in progress — The case record linking documents to activity.

Follow the work through

Follow document review to production. Review roles for access to evidence. Review integrations when choosing a document storage or delivery channel.

What it keeps track of

Data model
Legal documents
Versioned legal documents with privilege status and content hash.
Document productions
Authorized document productions to recipients.
Matters
Litigation matters from intake through closure.
Record attachments
Files and evidence attached to matters.

Who uses it

Permissions
Supervising Attorney
, Matter Coordinator, Auditor.
Counsel owns privilege and authorization decisions; the coordinator records the authorized production; the auditor can inspect the trail.

Set up Litigation Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started