Contingency Plan with Triggers¶
Procedure — instantiates Option Preservation
Pre-scripts alternative actions and the observable signals that fire them, so a viable fallback can be executed the moment conditions change rather than improvised under pressure.
A Contingency Plan with Triggers is a table of if-this-signal-then-that-action pairs, written before a crisis so a preserved fallback can be run on sight instead of invented under pressure. Its defining move is that it binds a named, observable trigger to a pre-decided action and a threshold at which that action fires: the plan sits dormant until a monitored signal crosses its threshold, and then the fallback executes without re-opening the decision. It is not a map of possible futures and not a way to keep many paths alive — it is the operational last mile that turns one preserved option into an executable response the instant its condition arrives.
Example¶
A coastal regional hospital's emergency-preparedness committee builds a storm-season contingency plan. Three triggers are wired, each with an owner, a crisp threshold, and an action that is already provisioned rather than hoped for. First: if the National Weather Service issues a hurricane warning inside 48 hours, the on-call administrator activates standing patient-transfer agreements with two inland hospitals. Second: if the utility issues a grid load-shed notice, facilities cuts the ICU over to generator power and tops off fuel from a vendor already on retainer. Third: if the basement flood sensor reads six inches, pharmacy stock relocates to the second floor.
When a Category 3 storm actually tracks toward the coast, the 48-hour warning fires the transfer protocol the same afternoon — no committee is convened, no one re-litigates whether transfers are wise, because that argument was settled in calm weather. The value is not any single choice but the removal of decision latency: a viable path was kept warm, its exercise condition was named in advance, and the plan simply executed when the signal arrived.
How it works¶
What separates this from a generic "plan B" is that every element is pre-committed and observable:
- Signal-to-action binding is decided in advance. Each row pairs one monitored signal with one specific action; nothing is left to on-the-spot invention.
- Each trigger carries an unambiguous threshold and an owner. "Flood sensor reads six inches, watched by facilities" leaves no room to argue about whether the condition has been met.
- The fallback is pre-provisioned, not merely named. Transfer agreements are signed, fuel is contracted, so the option can actually be exercised — the guard against a fallback that exists only on paper.
- It stops at execution. The plan does not decide which options to keep alive; it operationalizes the exercise of ones already chosen.
Tuning parameters¶
- Trigger sensitivity — how low the threshold sits. A low bar fires early and safe but invites false alarms and alert fatigue; a high bar is calm but can fire too late to act.
- Trigger count — how many conditions are watched. More coverage catches more contingencies but multiplies monitoring load and the chance of conflicting activations.
- Automation vs. human gate — whether a crossed threshold executes automatically or prompts a human to confirm. Automation removes latency; a human gate adds judgment but reintroduces delay.
- Fallback warmth — how much is spent keeping each fallback ready to run (retainers, reserved capacity). Warmer fallbacks activate faster but cost more to hold.
- Review cadence — how often triggers and agreements are re-verified, so a lapsed contract is caught before the storm rather than during it.
When it helps, and when it misleads¶
Its strength is eliminating deliberation at the worst possible moment: by settling the signal, the threshold, and the action ahead of time, it converts optionality into a reflex. It shines wherever the cost of a slow decision is high and the triggering conditions can be observed — disaster response, incident runbooks, financial circuit-breakers. The approach mirrors implementation intentions, the finding that concrete if-then plans dramatically improve follow-through compared with a mere intention to act.[n1]
Its central failure mode is false optionality: a plan that lists a fallback which cannot actually activate — an expired transfer agreement, a supplier who never signed, an authority nobody holds. The tidy table lends false confidence precisely where it is unearned. A related misuse is a trigger set tuned so twitchy that repeated false alarms train responders to ignore it, so the one real signal is dismissed as noise. The discipline that guards against both is to rehearse the plan — drill each fallback to prove it is live, and re-verify thresholds and agreements on a cadence rather than filing the plan and trusting it.
How it implements the components¶
Contingency Plan with Triggers fills the exercise-and-activation slot of the archetype — the parts that fire a preserved option, not the parts that choose or maintain the option set:
fallback_path— each row is a pre-decided, pre-provisioned alternative action ready to run.trigger_signal— the observable condition that, when it appears, activates the paired fallback.commitment_threshold— the exact value at which a signal counts as "fire now," making exercise unambiguous.
It does not map the unknowns or catalog the option set (uncertainty_map, option_set) — that is Scenario Planning Workshop; nor does it release resources in phased increments (staged_decision) — that is Staged Investment. This procedure executes a chosen fallback; it does not select which options to preserve.
Related¶
- Instantiates: Option Preservation — it is the mechanism that converts a preserved option into an executed action when its condition arrives.
- Consumes: Scenario Planning Workshop — its scenarios and early-warning signals tell this plan which contingencies deserve a wired trigger.
- Sibling mechanisms: Modular Design Option · Parallel Prototyping · Pilot-to-Scale Gate · Portfolio Exploration Backlog · Real Options Contract · Reversible Decision Protocol · Scenario Planning Workshop · Staged Investment · Rolling Forecast Review
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Pre-scripts alternative actions and the observable signals that fire them, so a viable fallback can be executed the moment conditions change rather than improvised under pressure, making its operative form a repeatable ordered procedure or handoff sequence coordinating action.
Independent corroboration: The frozen evidence defines Contingency Plan with Triggers as 'Pre-scripts alternative actions and the observable signals that fire them, so a viable fallback can be executed the moment conditions change rather than improvised under pressure', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Emergency preparedness cohered pre-scripted fallback actions bound to observable thresholds so response begins without crisis-time redesign.
Related originating lineages:
- Organizational & Management Science — Business-continuity planning contributes advance authority, contracts, resources, and execution ownership.
Review resolution: Trigger-based fallback plans are a recognizable emergency-management method, with business continuity a genuine organizational lineage; psychological precommitment is explanatory rather than co-origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Implementation intentions — Peter Gollwitzer's term for plans of the form "when situation X arises, I will perform response Y." The research finding is that binding an action to a specific triggering cue reliably improves the odds the action actually happens, versus holding only a general goal. A contingency plan with triggers is that structure applied at organizational scale. ↩