1. Legal Hold Management
  2. Features
  3. Review and operations
Feature · Review and operations

Review and operations

Make independent decisions and operation outcomes traceable.

OverviewFailed operations
Legal Hold Management · Review and operations

Failed operations

Operation receipts

New
ParentOperation keyActionResult stateFailure reasonOccurred at
MTT-69251OK-294ACT-825FailedCut to length17 Oct
MTT-99985OK-895ACT-944Needs ReviewWeld frame05 Oct
MTT-70809OK-796ACT-959FailedDrill and tap23 Oct
MTT-63160OK-706ACT-202Needs ReviewDeburr19 Oct
MTT-58733OK-757ACT-815FailedAssemble03 Oct
6 of 6 records
OK-294Operation receipts · OR-91266
Failed
ParentMTT-69251
ActionACT-825
Failure reasonCut to length
Occurred at17 Oct
Example screen with sample data

What you can do

Make independent decisions and operation outcomes traceable

A review decision stores the source revision, deciding reviewer, decision date, reason and operation key against a matter. An operation receipt stores the action, expected revision, result state, occurrence time and references to resulting effects. Staff compare their shared matter and operation key to distinguish a review decision from the recorded result of a guarded action. A completed receipt has different meaning from a hold approved by a person.

How the work is organized

  • Decide the revision. Hold Reviewer records a reason, source revision and operation key under the matter.
  • Read the receipt. Legal Operations checks the expected revision, result state and effect references for the guarded action.
  • Assign an exception. Matter Owner investigates failed and review-needed results before anyone reports completion.

Operations Overview gathers matter activity, deadlines, pending review decisions and failed operations into an aggregate operational screen. Use it to choose the next investigation, then open the parent matter and the corresponding receipt. A failed or review-needed result needs a reason and a responsible follow-up; it must not be represented as a completed preservation action.

What to agree during setup

Agree who records operation receipts, who investigates failures and who checks a human review before the team treats an action as authorized. Use the parent matter and operation key to trace each decision and receipt to the intended hold. Test a matter with two submitted holds and confirm staff can identify which revision and operation each decision covers. Keep failed receipts visible while a later attempt is investigated.

Check the handoff on an actual case

Suppose a hold revision receives approval but the operation receipt shows Failed. Legal Operations opens the receipt, checks the operation key and expected revision, and compares the effect references with the intended matter. The Hold Reviewer can see the decision that authorized the revision. The owner leaves the case open until the failed action is explained and a new, traceable result is checked.

Ask the next Legal Operations user to locate the failed receipt from Operations Overview and open the parent matter. They should compare the expected revision, operation key and failure reason with the review decision. If another attempt completes, keep the first failure available for the matter owner’s investigation.

What your team sees

  • Failed operations — Receipts whose result needs investigation.
  • Pending operations — Receipts awaiting an outcome.

What it keeps track of

Data model
Review decisions
Independent review decisions on submitted revisions
Operation receipts
Persisted receipts for guarded operations
Custodian holds
Preservation holds issued to custodians
Matters
Legal matters and engagements

Who uses it

Permissions
Hold Reviewer
, Legal Operations and Admin work from the same matter context with different decision rights.
Check roles and permissions before assigning live access.

Set up Legal Hold Management your way.

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

How to get started