1. Document Automation
  2. Features
  3. Document revisions
Feature · Document revisions

Document revisions

Identify matter documents by revision, privilege and content hash.

OverviewDocuments awaiting privilege review
Document Automation · Document revisions

Documents awaiting privilege review

Legal documents

New
TitleRevisionPrivilegeContent hashMatter
Unreviewed ld-913550UnreviewedCH-766MTT-22495
Unreviewed ld-586670UnreviewedCH-469MTT-70274
Unreviewed ld-116810UnreviewedCH-959MTT-82172
Unreviewed ld-795120UnreviewedCH-160MTT-95011
Unreviewed ld-465320UnreviewedCH-636MTT-94939
6 of 6 records
Unreviewed ld-913Legal documents · LD-61232
Unreviewed
Revision550
Content hashCH-766
MatterMTT-22495
Example screen with sample data

What you can do

Know which document was reviewed

A title alone cannot identify the exact document the team intends to file or disclose. The matter document records its revision and content hash, along with the file when one is attached. A privilege classification tells the reviewer whether the document remains unreviewed, is privileged or has been found not privileged. The approving person’s name is retained with the record.

The Matter Coordinator registers a document against its matter. The Supervising Attorney checks the intended revision before the team treats it as ready for a downstream action. A production record points to the document and records its own production hash, recipient and authorization reference. These facts let the team distinguish an authorized disclosure from an earlier draft or a similarly named file.

How the work is organized

  • Revision identity. Keep the title, revision and hash together with the matter.
  • Privilege review. Record the classification before a filing or disclosure decision.
  • Production trace. Link each recipient and authorization reference to the document produced.

What to agree during setup

Agree how a revision is numbered and how the content hash is calculated when a file is registered. A newly revised file should be checked as its own content, even when its title resembles a previously approved document. Decide who can classify privilege and which authorization references are sufficient for production. The Supervising Attorney should review the exact content being disclosed.

Establish how the team handles a document that is privileged or still unreviewed. A coordinator may prepare the matter and upload evidence, but a production action needs the legal decision and the right recipient. If delivery happens through another service, agree how its receipt is reconciled with the local production record.

Check the handoff on an actual case

A coordinator registers a draft agreement, including its revision and hash. The attorney reviews it and finds a privileged annex. The document remains classified as privileged while the team prepares a revised version. The replacement has a different revision and hash, so the attorney can make a fresh decision rather than relying on the earlier document’s title.

Before a recipient receives a document, the attorney checks the exact revision and the authorization reference. The team records who received it and when. Later, an auditor can follow the matter to the document and production record, compare the hash and see which authorization was used. A mismatch is an issue to resolve before calling the handoff complete.

What your team sees

  • Documents awaiting privilege review — Find unreviewed matter documents.
  • Matters in progress — Open the associated matter and its current owner.

What it keeps track of

Data model
Legal documents
Matter documents with revision, privilege status and content hash.
Document productions
Authorized disclosures of an exact document revision to a recipient.
Matters
Legal or contract matters with lifecycle, owner and agreed fee.
Record attachments
Evidence files attached to a matter with uploader and visibility.

Who uses it

Permissions
Supervising Attorney
, Matter Coordinator, Auditor.

Set up Document Automation your way.

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

How to get started