START HERE

What you will learn

  • Distinguish a meaningful check from a quick read-through.
  • Create a review checklist for one task.
  • Decide what happens when the evidence is missing or contradictory.

Before you start: Bring an example of an AI draft and the original information it used.

Why reading an answer is not the same as checking it

A fluent answer is easy to accept because it sounds complete. Review requires a different question: “What would I need to verify before acting on this?” A reviewer must be able to compare the answer with the original material, not judge its tone alone.

The depth of checking should match the consequences of a mistake. An outline for your private notes may need a light check. A message that promises a refund or a command that changes a live system needs explicit verification before it is sent or executed.

Give the reviewer something concrete to decide

Define the decision before the model produces an answer. For a research brief, the checks might cover factual claims, missing evidence and whether the conclusion follows from the sources. For a deployment change, they might cover the target environment, proposed operations and recovery plan.

The reviewer can be the person who created the draft, provided they can perform the required checks. Being called “the reviewer” is not enough: they need time, relevant knowledge and access to the evidence. If a necessary fact cannot be established, the right result may be to pause the task.

Step-by-step process

  1. List the claims or actions that matter

    Mark facts, commitments, calculations and system changes. These are the points where a plausible-looking error can have consequences.

  2. Put the original evidence beside the draft

    Open the source document, customer request or change plan. A citation is a starting point for inspection, not automatic proof that a claim is supported.

  3. Apply a short task-specific checklist

    For a customer reply: correct customer, correct policy, no invented commitment and a suitable next step. Keep the checklist short enough to use consistently.

  4. Accept, correct or escalate

    Accept only when the required checks pass. Correct an answer when the evidence is clear. Escalate when you need information or authority you do not have.

  5. Record recurring problems

    Keep a brief, appropriate record of corrections. If the same error appears repeatedly, change the instructions, source material or workflow rather than expecting reviewers to catch it indefinitely.

FOLLOW ONE EXAMPLE

Worked scenario

Reviewing a draft response about a refund

An AI draft says a customer will receive a refund within three days. The supplied policy allows a refund after inspection but gives no processing time. This is an illustrative scenario.

  1. Find the sentence making the three-day promise and look for its supporting policy passage. There is none.
  2. Remove the invented timescale. Check whether inspection has actually happened before saying the refund is approved.
  3. If the inspection status is unknown, ask the person responsible for it or draft a reply explaining the next confirmed step.

What this shows: The final response communicates what is known without creating an unsupported commitment. The review changes the decision, not merely the wording.

The process at a glance

Review has three useful outcomes: approve, correct or pause for a decision. An uncertain result should not be forced through approval.
ProcessDecisionHuman checkpoint
Read Mermaid diagram source
flowchart TD
 A[Read the draft] --> B[Check claims against evidence]
 B --> C{Required checks pass?}
 C -->|Yes| D[Human approves use]
 C -->|Correctable| E[Correct and check again]
 E --> B
 C -->|Uncertain| F[Pause and escalate]

What you should have at the end

  • A checklist tied to the actual consequences of the task.
  • A visible accept, correct or escalate decision.
  • A record of repeated errors that can guide improvements.

Common mistakes and how to avoid them

Approving because the answer sounds professional

Style does not establish that the facts or commitments are correct.

Assigning responsibility without evidence access

A person cannot verify a source they are not allowed or able to open.

Treating escalation as failure

Pausing an uncertain answer can be the correct outcome of review.

APPLY THE IDEA

Try it yourself

Your task: Annotate one AI draft. Underline factual claims, circle commitments and mark anything you cannot verify.

What to produce: A five-item review checklist and one example of when you would escalate.

Check your understanding: Would the checklist have caught the most consequential error in the draft?

Key terms in plain English

Reviewer
The person deciding whether an output meets the agreed checks.
Escalation
Passing an unresolved decision to someone with the required knowledge or authority.
Unsupported claim
A statement that is not established by the available evidence.