# The Flag-List Template (Chapter 11)

**Use when:** source-check is done and some claims failed. Rung four of the verification ladder, and the output is the point: every claim that failed goes on the list, in four fields.

The flag-list is what makes verification a job instead of a feeling. "I checked it" is a memory. The flag-list is evidence, and it is the evidence you attach when the document ships, so the next reader does not redo the source-check.

```
Claim | Source it should have been supported by | What I found | What I did
[THE CLAIM, VERBATIM] | [THE SOURCE] | [WHAT THE SOURCE ACTUALLY SAYS, OR THAT IT DOES NOT EXIST] | [CORRECTED / CUT / FLAGGED FOR THE AUTHOR, AND HOW]
```

A filled row:

```
"74 comments supported the tree-preservation requirement" | Round two comments file | 52 supported it; 22 mentioned trees while arguing against | Corrected to 52, note added
```

Four fields, one line per failure, and every line ends in an action. Corrected. Cut. Flagged for the author. There is no fourth option, and there is no silent.

## Rules that travel with it

- A claim that fails source-check ships exactly one of two ways: corrected, or flagged. Never silent.
- Attach the flag-list when the document ships. The next reviewer inherits your head start instead of redoing rung three.
- If the document feeds a public record, a regulatory review, or a board packet, the ladder is not optional.
- "I've looked it over, it's good" means your name is on every claim in it, no matter who drafted it. Forwarding, recommending, and reviewing are all forms of signing.

Verify: you can answer "what did you check?" with the flag-list in your hand.