Anticipatory Forecasting¶
Use plausible forecasts to prepare before future states arrive.
The Diagnostic Story¶
Symptom: The conditions everyone feared arrive on schedule, and the system scrambles because it was waiting for certainty that never came early enough. Signals were visible weeks or months before the crisis, but they were not connected to any preparation trigger. Capacity runs short, queues spike, and costs multiply because action started too late. Forecasts exist on a dashboard somewhere, but no one agreed on what threshold would start a response.
Pivot: Attach each forecast to an explicit lead time and a preparation action, so the estimate is no longer just information — it is a trigger. Build in explicit uncertainty bands and an update cadence, so the response can scale up or de-escalate as evidence changes rather than locking into the first guess.
Resolution: Preparation starts when there is still time to make it matter, and the scale of that preparation stays proportional to forecast confidence. Avoidable emergencies shrink because signals are operationalized rather than observed and forgotten. When forecasts turn out wrong, the update rule already exists, so the system corrects rather than doubles down.
Reach for this when you hear…¶
[emergency management] “We had the weather data a week out — the reason we ran out of shelter beds is we waited for the flood to actually start before calling it.”
[retail supply chain] “Every holiday season we're expediting freight at triple the cost because no one pulled the reorder trigger when the demand signal was already there in September.”
[hospital capacity] “The ICU census model was predicting this surge for ten days, but we didn't activate the overflow protocol until we were already full.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A reactive system has partially knowable future conditions whose advance signals are not converted into timely uncertainty-aware preparation, where preparation needs lead time or waiting for certainty degrades the response.
What this problem means
The structural problem is reactive operation in a partially forecastable environment. Signals exist, but the system does not convert them into timely preparation. By the time the future condition is certain, the useful preparation window has closed.
This creates avoidable surprise, emergency spending, capacity overload, rushed decisions, fragile plans, and repeated late responses. It can also create the opposite failure: overconfident preparation for a point forecast with no update or de-escalation path.
Show the applicability expression
Applicability expression3 distinct conditions
groundedpartly groundedopen
Equivalent to the 2 condition sets it replaces, with 1 duplicate condition card removed.
1Required in every casenumbered 1–1
These hold no matter which pattern applies.
Unconverted advance signals · open
Partially knowable future conditions provide advance signals, but the system remains reactive because it fails to convert them into timely uncertainty-aware preparation.
This condition preserves a load-bearing part of the diagnostic problem that was not captured by a source-condition atom. It remains explicit because omitting it would weaken the sufficient condition set.
2At least one of theselettered A–B
Any single one of these completes the pattern.
Preparation lead time · grounded · any one of 2
The actions needed to prepare require nontrivial lead time before they become effective.
The source archetype describes the situation as follows: Preparation actions need lead time, such as staffing, procurement, capacity reservation, public warning, hedging, staging, redesign, or scheduling. The normalized requirement above isolates the load-bearing portion used in this condition set.
Certainty-induced delay · grounded
Waiting for certainty would make the response late, expensive, brittle, or impossible.
This creates avoidable surprise, emergency spending, capacity overload, rushed decisions, fragile plans, and repeated late responses. The narrower requirement in this condition set is: Waiting for certainty would make the response late, expensive, brittle, or impossible.
Other requirements and context (3)
Why these sit outside the expression
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Solution feasibilityA future demand, risk, failure, shortage, overload, opportunity, or environmental condition can be estimated before it arrives.
Use Anticipatory Forecasting when a future demand, risk, shortage, overload, opportunity, or environmental condition can be estimated before it arrives and when preparation takes time. In this archetype, the relevant feasibility condition is: A future demand, risk, failure, shortage, overload, opportunity, or environmental condition can be estimated before it arrives. It identifies something that must be possible or available for the intervention to be workable.
Application gateThe cost of modest preparation is justified by the risk of being unprepared, but overreaction remains possible.
Use Anticipatory Forecasting when a future demand, risk, shortage, overload, opportunity, or environmental condition can be estimated before it arrives and when preparation takes time. In this archetype, the relevant application gate is: The cost of modest preparation is justified by the risk of being unprepared, but overreaction remains possible. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Solution feasibilityThe decision can tolerate approximate forecasts if uncertainty and update rules are explicit.
It can also create the opposite failure: overconfident preparation for a point forecast with no update or de-escalation path. In this archetype, the relevant feasibility condition is: The decision can tolerate approximate forecasts if uncertainty and update rules are explicit. It identifies something that must be possible or available for the intervention to be workable.
Coverage
2 of 3 conditions grounded · 1 open.
All 1 open condition sit in the shared core, so it blocks every alternative equally. Grounding it would make this archetype fully grounded outright — not one condition set at a time.
Mechanisms / Implementations¶
- Capacity Forecast: Converts a forecast of future load into the resource capacity it will require, then starts the long-lead provisioning so the capacity is in place before the peak arrives.
- Demand Forecasting: Estimates how much of something will be demanded in a future period by decomposing demand into its drivers, and re-runs the estimate each cycle as fresh actuals arrive.
- Early Warning Forecast: Predicts whether and when a threatening condition will cross a harm threshold, issues the warning far enough ahead to act, and stands the response down when the threat recedes.
- Forecast After-Action Review: After the forecasted future has arrived, scores what was predicted against what happened, records the error and its owner, and feeds the lesson back into how the next forecast is made.
- Forecast Trigger Dashboard: A standing live display that pulls forecast signals against their trigger lines, refreshes continuously, and communicates status so the right people see a threshold approaching before it is crossed.
- Reference-Class Forecast: Forecasts a case by locating the class of comparable past cases and reading their actual outcome distribution, replacing the optimistic inside view with a base rate drawn from how similar efforts really turned out.
- Rolling Forecast Review: A scheduled and event-triggered ritual that re-forecasts where the target is heading and refreshes the scenario spread, so plans always ride current evidence rather than a fixed period boundary.
- Scenario-Informed Preparation: Takes a small set of divergent plausible futures and prepares a hedged bundle of actions robust across all of them, then narrows or stands down each hedge as one future is ruled out.
- Trend Projection: Extends an observed pattern in a single series forward over a horizon, carrying a band that widens with distance, to answer where a quantity is heading if its recent behavior continues.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (3)
- Foreseeing (Prediction): Predict future states.
- Horizon Scanning: Monitor emerging trends.
- Uncertainty: Incomplete knowledge.
Also references 7 related abstractions
- Adaptation: Systems adjust to conditions.
- Approximation: Good-enough representation.
- Boundedness: Values remain within limits.
- Environmental Scanning: Analyze external factors.
- Feedback: Outputs influence inputs.
- Probability: Quantifies uncertainty and likelihoods.
- Scenario Planning: Construct plausible futures.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Demand Anticipation · domain variant · recognized
Forecasts future demand with enough lead time to adjust capacity, supply, staffing, or outreach before load arrives.
Capacity-Stress Forecasting · implementation variant · recognized
Forecasts future stress on constrained capacity so reserves, rate limits, staffing, or rerouting can be prepared before overload.
Early-Warning Preparation · risk or failure variant · recognized
Uses early signals to forecast an emerging threat or disruption and activate preparation before the full event arrives.
Rolling Forecast Preparation Loop · temporal variant · recognized
Continuously refreshes forecast, uncertainty, thresholds, and preparation actions as new evidence arrives.
Forecast-Triggered Hedging · governance variant · candidate
Uses forecast thresholds to activate hedges, option-preserving moves, reserves, or staged commitments under uncertain futures.
Editorial Notes¶
Problem Classification¶
Classification: Timing, Transition & Path-Dependence Failure → Opportunity Window, Threshold & Readiness Timing
Problem kernel: lead-time preparation starts only after foreseeable demand arrives
Rationale: The earliest necessary failure is that preparation requiring lead time begins only after forecasted demand arrives, an inclusion cue stated directly for readiness timing. Uncertain evidence must be handled responsibly, but the record does not primarily allege hidden forecast assumptions or omitted scenario ranges; it alleges failure to translate partially knowable conditions into action before the readiness window closes.
Boundary considered: Uncertainty, Evidence & Inference Failure → Forecast, Scenario, Assumption & Sensitivity Uncertainty
Why this classification prevailed: Readiness timing governs when preparation must begin under partial knowledge; forecast uncertainty governs whether assumptions, alternatives, sensitivities, and revision conditions are adequately represented.
Review outcome: Adjudicated after independent review; high confidence.