Contingency Option Register¶
Operational register — instantiates Wild-Card Contingency Mapping
Holds the authoritative ledger of preserved response moves — each with its trigger, authority, and live-or-retired status — so a contingency can be found, trusted, and used the moment it is needed.
The Contingency Option Register is the maintained ledger of response moves a system has preserved in advance — one record per option, each stating what the move is, who is authorized to pull it, what it needs, and whether it is currently live or retired. Its distinguishing job is findable, accountable options: not imagining disruptions or tracing them, but making sure that when a mapped contingency arrives, the response isn't improvised — there is an entry, and it says who may act and on what trigger. An option here is concrete — "divert wide-body traffic to the alternate hub," "activate the standby crew reserve," "switch to the backup ground-handling contract" — and it is only as good as its status field: the register's core discipline is that a move nobody has kept current is marked stale, not left looking ready.
Example¶
A regional airline keeps a Contingency Option Register for operational shocks. When a wild card lands — say, its primary hub closes with no notice after a runway incident — the duty controller opens the register instead of starting from a blank page. Entries read as records: "Divert schedule to secondary hub — activatable by the duty ops director — requires the pre-signed handling agreement (status: live, reviewed 2 months ago) — capacity ≈40% of normal." Another: "Recall reserve crews — activatable by crew scheduling — bounded by legal duty-time limits (status: live)."
A third, "Charter replacement lift from a partner carrier," is flagged stale — contract lapsed last quarter — which is itself the most useful thing on the screen: it tells the controller not to count on it and tells someone to go fix it. Each option also carries a retirement rule — the secondary-hub diversion retires automatically if that airport's own capacity is ever cut — so the register sheds moves that quietly stopped being real.
How it works¶
- One record per move. Each preserved option is a discrete entry — the action, who may authorize it, what it consumes — so it can be found under pressure, not reconstructed.
- Attach an activation and retirement rule. Every entry states the trigger and authority that turn it on and the condition that ends it, so the register neither waits on improvisation nor accretes dead options.
- Carry an honest status. Live / stale / retired, with a last-reviewed stamp; an option that can't be shown current is flagged, not assumed.
- Point outward, don't duplicate. Entries link to the map branch they serve and the reserve that supplies them, rather than re-describing either.
Tuning parameters¶
- Option granularity — broad moves versus finely specified procedures. Fine entries are ready to execute but rot faster; broad ones age well but demand improvisation in the moment.
- Authority pre-binding — how much decision right is pre-delegated in the entry. Pre-bound authority speeds activation but risks premature or wrongful triggering; unbound options are safe but slow.
- Staleness window — how long an unreviewed entry stays trusted before it auto-flags stale. Tight windows keep the register honest but generate review churn.
- Coverage vs. maintainability — how many options to hold. More options cover more branches but dilute the upkeep that keeps any of them real.
- Retirement aggressiveness — how readily dead moves are culled versus archived for reference.
When it helps, and when it misleads¶
Its strength is turning "we'll figure it out" into a found, authorized, resourced move — and, through the status field, making the difference between an option that is real and one that only looks real explicit on the page instead of discovered mid-crisis.
The register's signature pathology is paper preparedness: a fat list of impressive-sounding options, none rehearsed, none resourced, producing confidence without capability — the administrative cousin of what is often called security theater.[n1] It is also easily run backwards — back-filled after an incident to show the option "existed," when in truth it was stale. And it can drift into a graveyard of retired moves nobody prunes. The discipline that keeps it honest is a ruthless status field, periodic culling, and the rule that an option counts only when its reserve and its rehearsal both check out — which is why the register leans on its siblings rather than standing alone.
How it implements the components¶
The Contingency Option Register fills the response-ledger side of the archetype — holding the moves and governing their lifecycle, nothing upstream or resource-side of that:
contingency_option— the register is the collection of preserved response moves, one auditable record each.activation_and_retirement_rule— every entry carries the trigger and authority that activate it and the condition that retires it, keeping the ledger between panic-activation and permanent accretion.
It does not size the standby capacity an option draws on — that is the Strategic Reserve Plan; it does not test whether the move actually works under pressure — that is a Readiness Drill or a Red-Team Disruption Challenge; and it does not trace what each option protects against — that is the Contingency Map.
Related¶
- Instantiates: Wild-Card Contingency Mapping — the register is where the archetype's response side is kept ready and findable.
- Consumes: Contingency Map — the map's exposures and owners tell the register which options must exist and for whom.
- Sibling mechanisms: Contingency Map · Strategic Reserve Plan · Crisis Scenario Catalog · Red-Team Disruption Challenge · Precursor Watchlist · Disruption Playbook · Tabletop Exercise · Readiness Drill · Wild-Card Workshop
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Holds the authoritative ledger of preserved response moves — each with its trigger, authority, and live-or-retired status — so a contingency can be found, trusted, and used the moment it is needed, making its operative form a durable record, ledger, register, or trace whose value depends on preserving actual state or history.
Independent corroboration: The frozen evidence defines Contingency Option Register as 'Holds the authoritative ledger of preserved response moves — each with its trigger, authority, and live-or-retired status — so a contingency can be found, trusted, and used the moment it is needed', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Disaster Management & Risk Reduction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Emergency and continuity planning cohered maintaining executable response options with activation triggers, authority, prerequisites, and current readiness status.
Related originating lineages:
- Military & Strategic Studies — Operational planning supplied preserved branches and sequels for changing conditions.
- Organizational & Management Science — Business-continuity and portfolio governance contribute maintained status, ownership, dependency, and retirement fields for preserved response options.
Review resolution: Continuity planning is the closest primary, while military branches and sequels and organizational option governance materially shape the register; the exact lifecycle ledger is synthesized and moderately attributable.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- FEMA Continuity Guidance Circular, 2024 Update
- FM 6-0: Commander and Staff Organization and Operations
Notes¶
The register lists moves; it does not execute them. When a disruption hits, the step-by-step doing is a Disruption Playbook's job — the register only guarantees the move exists, is authorized, and is current. Keeping the ledger and the runbook separate is what lets options be maintained without rewriting procedures every time.
[n1] Security theater — measures that create a feeling of preparedness without materially improving it; a term from security analysis. A register of impressive but untested, unresourced options is its administrative form, which is why status honesty and rehearsal are the correctives. ↩