Lesson 2.4 · D2 Output Evaluation & Validation · 5 min
Decide when human review is required
The higher the stakes and the harder to reverse, the more qualified and accountable the review must be.
What the exam tests
Picking which outputs need expert review, and recognising when a review step is being bypassed.
Key ideas
- Always needs qualified review
- Public statements, legal or regulatory content, financial commitments or promised outcomes, health and safety guidance, decisions or records about individuals, anything sent to courts, regulators or funders.
- Light review is fine for
- Internal brainstorms, agendas, reformatting, first-pass ideas that a person will develop.
- Review must be real
- Pasting drafts without reading them defeats the control. Spot checks, accountability and tracking error rates keep review meaningful.
- Accountability stays human
- The person and organisation that approve and send content are responsible for it, not Claude and not the vendor.
- Drafts must not invent decisions
- Watch for drafts that promise compensation, state an outcome not yet decided or make guarantees (“this will never happen again”).
Common traps
- Removing review because Claude's drafts are “usually right”.
- Asking Claude to review in place of the required approver.
- Sending first and getting approval afterwards.
Remember
High stakes, external or about people → qualified human review before it goes out.