1. Document Automation
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Keep reviewer decisions and guarded outcomes available for inspection.

OverviewOperations needing review
Document Automation · Review and evidence

Operations needing review

Operation receipts

New
Operation keyActionResult stateOccurred atFailure reasonParent
OK-401ACT-188Needs review13 OctCut to lengthMTT-18873
OK-643ACT-181Needs review08 OctWeld frameMTT-94823
OK-542ACT-527Needs review06 OctDrill and tapMTT-54766
OK-365ACT-540Needs review20 OctDeburrMTT-77296
OK-136ACT-264Needs review13 OctAssembleMTT-77692
6 of 6 records
OK-401Operation receipts · OR-20122
Needs review
ActionACT-188
Occurred at13 Oct
Failure reasonCut to length
ParentMTT-18873
Example screen with sample data

What you can do

Retain the decision with its source

A review decision identifies the matter revision considered, the reviewer, the outcome and the reason. Approval, rejection and return are distinct decisions. A returned case needs work by the coordinator before another review; a rejected case should not quietly advance as though it were approved. The operation key gives the decision a stable link to the guarded action it concerns.

Attachments supply supporting files for a matter. Their title, upload time, uploader, evidence type and internal or shared visibility give readers context for use. Sharing is a deliberate choice because a file may contain internal legal reasoning or client material. Auditors can read authorized evidence without becoming editors of the matter.

How the work is organized

  • Independent decision. Record the source revision, named reviewer, outcome and reason.
  • Evidence context. Link each attachment to the matter with its uploader and visibility.
  • Operation outcome. Use a stable key, expected revision and result state for guarded actions.

What to agree during setup

Agree which actions require a separate reviewer and what evidence the reviewer must see. The Matter Coordinator can prepare a revision and its attachments; the Supervising Attorney decides whether it can proceed. Define how a returned decision is resubmitted. A new revision should be reviewed as new material rather than inheriting the old approval.

Agree who investigates a failed or review-needed operation receipt. Its action, expected revision, failure reason and external reference should be inspected before any retry. If an outside service may have performed the effect, reconcile that result first. The team’s evidence practice should make it possible to explain what was requested and what actually completed.

Check the handoff on an actual case

A coordinator submits a matter revision for review with a supporting attachment. The attorney returns it with a reason because the supporting authorization is unclear. The coordinator prepares a corrected revision and supplies the missing evidence. A later approval refers to the corrected revision, while the earlier return remains visible to the auditor.

Suppose the subsequent guarded operation reports that it needs review. The attorney examines the receipt and its external reference before deciding whether the action completed elsewhere. The team should not simply repeat the action and create two effects. The case is finished only when the decision, operation result and retained evidence tell the same story.

When the matter changes after a return, compare the new source revision with the one named in the earlier decision. That comparison shows why a fresh approval is needed and keeps the prior reason useful to a later reviewer.

What your team sees

  • Operations needing review — Investigate guarded outcomes that need reconciliation.
  • Returned decisions — Find revisions sent back for correction.

Follow the work through

What it keeps track of

Data model
Review decisions
Independent reviewer decisions on submitted matter revisions.
Record attachments
Evidence files attached to a matter with uploader and visibility.
Operation receipts
Guarded operation outcomes with stable operation keys and result state.
Matters
Legal or contract matters with lifecycle, owner and agreed fee.

Who uses it

Permissions
Supervising Attorney
, Matter Coordinator, Auditor, App Administrator.

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