The idea
A forecast should specify an event, a deadline, and an assessment made before the outcome is known. Recording these elements makes later learning possible. Without a stable record, memory can quietly rewrite an uncertain prediction into something that felt obvious.
Worked example
A neighborhood organizer predicts a 70% chance that at least 40 people will attend Saturday’s cleanup, provided rain stays below a stated threshold. She records the number before sending invitations and defines how attendance will be counted. After the event she records the result and her reasons. Over many events, she checks whether events assigned about 70% occur roughly seven times in ten, rather than judging her skill from one lucky success.
Use it carefully
Calibration is a pattern across many forecasts; a single event cannot validate a probability. Forecasts also need useful discrimination: repeatedly saying 50% may avoid extreme mistakes while adding little practical help. Conditional forecasts require recording whether their conditions occurred. A scorecard is a tool for comparing judgment with reality, not a way to remove genuine uncertainty or turn social outcomes into mechanical laws.
FROM UNDERSTANDING TO ACTION
Put it to work.
Record three dated forecasts with explicit outcomes. Schedule a review and preserve your original reasoning.
RETRIEVE. REASON. REMEMBER.
Knowledge check.
Choose one answer for each question, then check your reasoning.
Sources & further reading.
Links support the core concepts or identify the book. Examples, exercises, and critical analysis are original Institute material. Source checks are not an independent expert review of every claim.
- OpenStax: probability as a basis for explicit event assessment ↗
OpenStax: probability as a basis for explicit event assessment; supports the core concept. Scenarios, calculations, and practice questions are original. Source reviewed 2026-10-19.