# Check the result that matters

Verification means checking the output against your task. Match the check to what you asked the teammate to do.

## Inspect the evidence

| Result           | Useful check                                                |
| ---------------- | ----------------------------------------------------------- |
| Research answer  | Open the important sources and check dates and claims       |
| Written document | Open the file and review its actual contents                |
| Data analysis    | Check units, inputs, missing values, and a few calculations |
| App update       | Inspect the changed record in the intended account          |
| Coding task      | Review the published diff, commit, and reported checks      |
| Routine          | Inspect an actual run and its output                        |

## Ask for the boundary

A useful completion report distinguishes completed work, checks performed, and unresolved steps. “Queued,” “running,” and “awaiting approval” describe work that has not yet completed.

> **Try this**
> Before we finish, give me the output links, the checks you actually ran, and anything you could not verify. Separate observed results from assumptions.

## Use another review when it helps

A second teammate can compare a draft with its sources or inspect a change against its requirements. Give that reviewer explicit criteria and access to the same material.

Use the [review checklists](/docs/resources/review-checklists) for common tasks. If an action failed, inspect its activity details and continue from the unfinished step rather than assuming the entire job needs to be repeated.