Evidence Checklist
Prove your app works with evidence: build a claim-by-claim verification pack with receipts.
The route
5 steps to Done
- 01
Inventory every claim
Collect what the product says about itself - everywhere.
Preview prompt + verify gate ▾ Hide ▴
Inventory every claim this product makes. Sources: the landing page, feature lists, README, submission/marketing copy, and UI microcopy. Extract each claim as a testable statement (e.g. 'users can export to CSV', 'data syncs across devices', 'works on mobile'). Flag vague claims ('fast', 'secure', 'seamless') for definition - each must be rewritten as something checkable or marked for removal. Produce the numbered claim list.
- ✓ All copy sources were scraped for claims
- ✓ Each claim is phrased testably
- ✓ Vague claims are flagged
- 02
Define verification procedures
Each claim needs a repeatable test a stranger could run.
Preview prompt + verify gate ▾ Hide ▴
For every claim, write the verification procedure: the exact steps (from a fresh state), what to observe, and the pass condition. Procedures must be reproducible by someone who has never seen the app - include starting state, test data, and where to look. Mark which claims need special setups (second account, mobile viewport, network throttling).
- ✓ Procedures start from a defined state
- ✓ Pass conditions are observable
- ✓ Special setups are noted
- 03
Execute and collect evidence
Run every procedure and record what actually happened.
Preview prompt + verify gate ▾ Hide ▴
Execute every verification procedure now. For each claim record: the result (VERIFIED/FAILED/PARTIAL), what was observed (specific - the record created, the state after refresh, the error shown), and the evidence artifact (what a screenshot/recording would show - describe the exact moment worth capturing). Function claims require action evidence (before/after data), not interface screenshots. No claim gets VERIFIED without execution.
- ✓ Every procedure was executed
- ✓ Function evidence shows actions and data, not just UI
- ✓ PARTIAL results explain the gap
- 04
Fix or reword failures
Reality and copy must match - change one of them.
Preview prompt + verify gate ▾ Hide ▴
Resolve every FAILED and PARTIAL claim: either fix the product so the claim verifies (then re-run the procedure), or rewrite the claim honestly (downgrade 'real-time' to 'updates on refresh', remove what cannot be delivered). Update all copy sources where reworded claims live. Deliver the change list: claim -> action taken -> final status.
- ✓ Each failure has an explicit resolution
- ✓ Reworded claims updated everywhere they appear
- ✓ Fixed claims were re-executed
- 05
Assemble the evidence pack
Package the proof so anyone can audit it.
Preview prompt + verify gate ▾ Hide ▴
Assemble the final evidence pack document: the claim list with final statuses; per-claim procedure and observed evidence; the environment tested (browser, viewport, date); known limitations stated plainly; and a 5-minute re-verification script - the ordered subset of procedures a reviewer should run to spot-check the pack. Keep it honest, specific, and reproducible.
- ✓ All claims appear with final statuses
- ✓ A stranger could re-verify from the pack
- ✓ Limitations are stated