Preflight Consequence Checklist¶
Checklist protocol — instantiates Predictive Precommitment Correction
A fixed, human-run checklist executed at the commitment point that walks through each predictable consequence of the intended action and verifies it against the target before anyone proceeds.
A Preflight Consequence Checklist is a low-tech, human-run verification ritual performed at the commitment point: before the irreversible step, the team pauses and reads through a fixed list of the action's known, predictable consequences, confirming each one against the acceptable envelope before anyone proceeds. Its defining move is disciplined enumeration under a hard stop — it forces the predictable downstream effects to be named and checked out loud, precisely the effects that get skipped when people are busy, confident, or rushed. It runs no simulation and computes no forecast; its power is that it makes a human deliberately anticipate what they already know could go wrong, at the one moment when catching it still costs nothing. It converts "we probably thought of everything" into a checked, spoken confirmation before the point of no return.
Example¶
An operating room runs the WHO Surgical Safety Checklist, and its "Time Out" is performed at the commitment point of any operation: the moment before the first incision, after which correcting a mistake means correcting it in the patient. The whole team stops. They read the list: patient identity, surgical site, and procedure confirmed out loud (the intended action, specified unambiguously); anticipated blood loss and airway difficulty stated and confirmed to be within what the plan and the room are prepared for (the predictable consequences, checked against the tolerance for a safe case); antibiotics given, imaging displayed, instrument counts correct.
Each item is a predictable consequence named and verified before the cut, not discovered during it. On a case where the anticipated blood loss is flagged as high, the Time Out surfaces it while extra blood can still be made ready — a pre-correction — rather than during a crisis. The checklist forecasts nothing; it simply refuses to let the team cross the commitment boundary until each known consequence has been spoken and confirmed against what a safe operation requires.[n1]
How it works¶
What distinguishes it from a simulation or an automated gate is that it is a human enumeration at a hard stop:
- Fix the commitment boundary. Place the checklist at the exact point past which correction becomes costly, and make crossing it conditional on completing the list.
- Specify the action unambiguously. Confirm precisely what is about to be done — the who, what, and where — so everyone is checking the same action.
- Walk each predictable consequence against tolerance. For every known downstream effect, state it and confirm it falls within the acceptable envelope; a miss triggers pre-correction or a halt.
- Require an explicit go. Proceed only on a spoken, shared confirmation — never on silence or assumption.
Tuning parameters¶
- Checklist length — how many items it covers. Longer catches more predictable failures but risks becoming a rote recitation nobody engages with.
- Format — read-and-do versus challenge-and-response between team members; the interactive form resists box-ticking but takes longer.
- Gate placement — exactly where in the workflow the hard stop sits; too early and conditions change before commitment, too late and correction is already costly.
- Stop authority — whether any member can halt on a failed item, or only a lead; broad authority catches more but can be overridden by hierarchy.
- Revision cadence — how often items are added or retired as new failure modes appear; a list that only grows eventually collapses into ritual.
When it helps, and when it misleads¶
Its strength is being cheap, fast, and robust against exactly the human failure the archetype targets: the predictable consequence skipped under time pressure or overconfidence. It needs no model and no data feed, works when the fancier mechanisms are unavailable, and its very simplicity is what lets it run every single time. For known, recurring, high-stakes actions it is often the highest-leverage pre-correction available.
Its failure mode is degeneration into ritual: a checklist read on autopilot, items ticked without engagement, is theater that produces the feeling of a check without the substance. Its structural blind spot is that it only catches consequences someone already put on the list — it is powerless against the genuinely novel failure that no one anticipated, and it can breed false confidence that "we checked" when the list was incomplete. The classic misuse is bloating it with items until it is too long to take seriously and gets skipped or rushed. The guarding discipline is to keep it short and focused on the consequential few, use challenge-response to force engagement, protect anyone's authority to stop on a failed item, and prune items that no longer earn their place.
How it implements the components¶
Preflight Consequence Checklist fills the archetype's human-verification-at-the-gate slot — the parts that force a deliberate check before the irreversible step:
commitment_point_boundary— it is anchored to the exact point past which correction is costly, and crossing it is conditional on completing the list.intended_action_specification— it opens by confirming precisely what is about to be done, so the whole team checks the same action.target_state_or_tolerance_envelope— each predictable consequence is verified against the envelope of an acceptable outcome before the go.
It runs no library of simulated futures and reports no spread of outcomes — the scenario_library, predicted_gap_signal, and forecast_uncertainty_band of a computational sweep belong to its nearest cousin Precommitment What-If Simulation: the checklist enumerates *known consequences from experience at the gate, whereas the simulation explores hypothetical futures. It also fires no automatic precorrection_rule; the correction here is a human decision.*
Related¶
- Instantiates: Predictive Precommitment Correction — the human hard-stop that verifies predictable consequences before the irreversible step.
- Sibling mechanisms: Digital-Twin Preview · Precommitment What-If Simulation · Feedforward Adjustment Dashboard · Leading-Indicator Trigger Rule · Predictive Scheduling Rule · Forecast-Based Resource Prepositioning · Forecast-Error Backtest · Model Predictive Control · Staged Commitment Gate
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Preflight Consequence Checklist operates as a repeatable ordered procedure or handoff sequence that coordinates action because it a fixed, human-run checklist executed at the commitment point that walks through each predictable consequence of the intended action and verifies it against the target before anyone proceeds.
Independent corroboration: The frozen evidence defines Preflight Consequence Checklist as 'A fixed, human-run checklist executed at the commitment point that walks through each predictable consequence of the intended action and verifies it against the target before anyone proceeds', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Its commitment-point checklist form descends directly from aviation preflight procedure.
Related originating lineages:
- Engineering & Design — Engineering contributes hazard-based go/no-go verification.
- Operations Research — Scenario and decision analysis materially shape systematic consequence comparison against a target.
- Psychology — Psychology contributes prospective consideration of predictable consequences and omission control.
Review resolution: Both blind reviewers agree that aviation aeronautics is the primary origin. Reconciliation resolves reported ambiguity, alternate origin disagreement. Formative alternate lineages are retained as engineering_design, psychology, operations_research; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Attribution caveat: The consequence-focused checklist is an encyclopedia-specific extension of canonical preflight practice.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] The WHO Surgical Safety Checklist, popularized by Atul Gawande in The Checklist Manifesto, is a short pre-procedure list run at defined stops (including a "Time Out" before incision) to confirm predictable safety items. It descends from the aviation preflight checklist — the same idea of forcing a deliberate, spoken verification of known risks before a point of no return. ↩