While checking a fictional demonstration against the Handoff sheet, one useful pattern became obvious: evidence is easiest to interpret when the untested part sits directly beside it.
The demonstration used an imaginary printable packing checklist. No client supplied it, no reader reviewed it, and it is not evidence that such a checklist was used in real work. Its job was to exercise the five fields with a complete, clearly labeled example.
A result has an edge
In the example, opening a one-page PDF and printing it on A4 paper would support a narrow statement: the file opens and works in that tested setup. It would not show that the same layout fits Letter paper or that a new user understands the checklist.
Writing those gaps under Limitations does not weaken the completed checks. It stops them from being asked to prove something they never tested.
Keep the five fields connected
- Intended result defines the claim you are trying to support.
- Delivered result points to the thing someone can inspect.
- Checks record what was actually tried and observed.
- Limitations mark the nearest important unknown.
- Next action turns that unknown into a specific follow-up, or says “None” when no action is needed.
The fields are less useful as five unrelated status boxes. Read together, they show where the result ends and where the next question begins.
A limitation is not a footnote to hide. It is the border around what the receipt can honestly prove.