Contingency Buffer Review¶
Planning review — instantiates Premortem Calibration
Converts ranked failure causes into right-sized schedule, budget, and scope buffers, anchored on how much slack comparable efforts actually needed.
The Contingency Buffer Review is the archetype's provisioning step: the point at which ranked vulnerabilities stop being findings and become deliberate slack in the plan — time buffers, budget contingency, capacity reserve, or trimmed scope. Its defining move is sizing a reserve to a specific failure cause and calibrating that size against real base rates, not against a comfortable habit. This is the difference between the archetype's version and the non-example the source warns about: a flat 10% added to every budget is not premortem-derived; a buffer sized to this plan's identified failure paths, checked against how much slack comparable efforts actually consumed, is. The review's job is to make each buffer both targeted (attached to a named vulnerability) and right-sized (anchored on outside evidence rather than optimism), and then to fold it into the plan as an actual change.
Example¶
A line producer is locking the budget and schedule for a feature-film shoot. The premortem has already ranked the vulnerabilities: an exterior sequence that lives or dies on weather, a lead actor with a hard availability window, and a complex water tank scene with a first-time rig. A naïve plan would sprinkle a uniform 10% contingency across the board. The contingency buffer review does something sharper. For each ranked cause it sizes a targeted reserve and checks it against reference cases — not this producer's optimism but the record of comparable shoots: weather-dependent exteriors on similar productions historically burned three to six extra days, so the schedule gets weather-cover days built specifically around that sequence, not spread thin everywhere. The actor's window gets a scene-reordering buffer so the critical days sit early. The water tank — where comparable rigs routinely overran on their first setup day — gets a dedicated tech-rehearsal day and a budget line, while the low-risk interior scenes get no padding at all. The output is a revised schedule and budget where every buffer points at a named failure and is sized to what actually tends to happen. The film's reserve is smaller in total than the flat 10% would have been, and far better placed.
How it works¶
- Attach each buffer to a ranked cause. No reserve exists in the abstract; every buffer is provisioned against a specific prioritized vulnerability, and low-risk areas get none.
- Size to base rates, not habit. Calibrate the buffer against how much slack comparable efforts actually needed, correcting the optimism that a self-generated estimate carries.
- Choose the buffer type to fit the failure. Time, money, capacity, or scope — a schedule risk wants schedule slack, a cost risk wants contingency, an execution risk may want a rehearsal or a descoped commitment.
- Fold it into the plan. The review's output is a revised schedule, budget, or scope — a real safeguard change — not a note recommending one.
Tuning parameters¶
- Buffer concentration — slack pooled against the top few risks versus spread across many. Concentration is efficient and pointed; spreading feels safer but reproduces the flat-percentage anti-pattern.
- Reference-class breadth — how wide and comparable the base-rate set is. A tight, similar reference class sizes buffers well; a loose one imports irrelevant overruns.
- Optimism correction strength — how hard the outside-view base rate overrides the team's inside estimate. Strong correction fights the planning fallacy but can over-pad if the reference class ran unusually badly.
- Reserve visibility — transparent, named buffers versus hidden padding. Visible buffers can be managed and defended but invite others to spend them; hidden ones resist raiding but corrode trust.
When it helps, and when it misleads¶
Its strength is that it turns worry into provisioned resilience while resisting both extremes — the plan with no slack and the plan padded reflexively everywhere. By anchoring buffer size on comparable efforts it applies reference-class forecasting, the outside-view correction to the systematic underestimation of time and cost[n1], so the reserve reflects how these things actually go rather than how the team hopes they will.
It misleads when buffers become a substitute for fixing the plan or a licence to underperform. A generous buffer can absorb a fixable design flaw that should have been engineered out, and a visible buffer tends to get consumed simply because it exists (work expands to fill the slack). The guarding discipline is to prefer eliminating or de-risking a failure cause over merely padding around it, and to size buffers to evidence rather than to the level of anxiety in the room — an unranked, unreferenced buffer is just optimism with extra steps.
How it implements the components¶
The review realizes the archetype's provisioning components:
safeguard_revision— its core: it converts ranked vulnerabilities into concrete plan changes — schedule buffers, budget contingency, capacity reserve, or reduced scope — folded into the plan itself.reference_case_anchor— it sizes those buffers against how much slack comparable efforts actually needed, using the outside view to correct optimistic self-estimates.
It does not keep the decision_revision_trace — recording what changed in a durable, dated ledger is Risk Register Update — and it does not build the early_warning_indicator_set or assign the contingency_owner_assignment that make up Failure Trigger Dashboard; the review sizes the reserves, while the dashboard watches for the triggers that would draw them down.
Related¶
- Instantiates: Premortem Calibration — the review turns ranked vulnerabilities into provisioned safeguards.
- Consumes: Assumption Stress Test supplies the ranked vulnerabilities each buffer is sized against.
- Sibling mechanisms: Premortem Workshop · Prospective Hindsight Prompt · Failure-Mode Brainstorm · Assumption Stress Test · Red-Team Failure Review · Risk Register Update · Failure Trigger Dashboard
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Converts ranked failure causes into right-sized schedule, budget, and scope buffers, anchored on how much slack comparable efforts actually needed, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Contingency Buffer Review as 'Converts ranked failure causes into right-sized schedule, budget, and scope buffers, anchored on how much slack comparable efforts actually needed', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Project-management practice cohered explicit schedule, budget, capacity, and scope contingencies tied to identified delivery risks.
Related originating lineages:
- Operations Research — Risk analysis contributes sizing each buffer against observed distributions for comparable failures.
- Psychology — Premortem and planning-fallacy research motivates external calibration instead of optimistic inside-view padding.
Review resolution: Project risk management supplies the review, operations research supplies quantitative sizing, and psychology supplies optimism-bias correction; the combined calibration procedure is synthesized.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Reference-class forecasting predicts a plan's cost, duration, or outcome by looking at the actual results of a class of comparable past efforts rather than building up from the plan's own assumptions. It is the standard corrective to the planning fallacy, and here it is what keeps a contingency buffer honest instead of habitual. ↩