Stolen Orbit
ENIT
Let’s talk
FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

Human review plan

Turn “a person checks it” into a task someone can actually perform. Reviewers need evidence, time and the authority to correct or stop a proposed action.

By Stolen OrbitRevision

When to use it and what to produce

When AI prepares content, changes records or proposes actions that need judgement before producing effects.

Routing and approval rules with named roles, review evidence, handling windows and a fallback when the reviewer is unavailable.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

Download the complete blank template (.md)

1. Decide what needs review

Classify actions by consequence and reversibility. Do not treat confidence reported by the model as the sole assurance that an answer is correct.

See a worked example

Illustrative example: a response draft stays internal. A proposed discount needs a sales owner; changes to bank details leave the automated workflow entirely.

List drafts, writes and sends; describe the operational harm that an error could cause.

Specify always-reviewed cases, verifiable automated checks and circumstances where work must not proceed.

Define ambiguities and decisions the ordinary reviewer is not authorised to resolve.

2. Make the review feasible

Design the interface and workload with the reviewer. Approval without access to sources and changes is not a useful control.

See a worked example

Illustrative example: the reviewer sees the original email beside the draft, corrects a product code and approves a specific identified version before it can be sent.

List source material, extracted fields, proposed action, changes from the current state and warnings.

Define approve, correct, reject and request clarification; state the effects of each choice.

Estimate case volume and review minutes, absence coverage and a manageable queue size.

3. Handle delays and learning

Retain control when approval does not arrive. Record outcomes and use repeated errors to improve rules, source data and training.

See a worked example

Illustrative example: a draft without approval during the internal review window stays paused. The backup receives its reference and decides whether to resume the case.

Specify when to alert the backup and suspend the case; silence must not silently become consent.

Preserve case reference, approved version, reviewer, time and correction reason with appropriate access.

Define who examines missed errors, queue delays and unusually rapid approvals.

Pitfalls to avoid

  • Assigning accountability without authority to stop the workflow.
  • Allowing content to change after approval without another check.
  • Increasing volume beyond the reviewers’ actual capacity.

Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.