Yellowstone Emergency Evacuation

Generated on: 2026-10-14 22:31:42 with PlanExe2. Discord, GitHub

⚠ Consistency lint FAILED: 1 high-severity contradiction remains after repair

Some sections disagree on numbers or dates that change a decision: Pre-event validation and go/no-go inputs dated at or before T+0, or after the window. See Consistency Check.

Part 1: Key decisions and facts

Go/no-go gates. NO at an early gate costs the least.

# Question Threshold Evidence If NO
1 Are all three contraflow exits live with interoperable Guard/agency radio nets by T+1 h? Contraflow active on West, North and East exits by T+1 h; two-way nets confirmed at all three gates; at least 4 Guard signal teams on hand; gate load within 10% of the 50/30/20 split. Control-point reports and interoperability check at T+1 h; hourly vehicle counts from T+1 h. Delay contraflow release and run staged departures by printed route card (premortem FM6 stop rule); divert the overflow to the nearest surviving exit. Gate G1 timing is then at risk and must be re-planned at T+2 h.
2 Do the UC have a published USGS trigger matrix and verbal authorization from the MT, WY and ID governors for Zone One and Scenario Beta orders? USGS final indicator values (placeholder: modeled VEI-7 probability of 20% or more in the remaining window) published by T+3 h; verbal authorization from all three governors by T+6 h; FEMA Region 10 liaison seated at T+0. USGS trigger-matrix release at T+3 h; governor confirmation calls logged by T+6 h; liaison seated at the Denver RRCC at T+0. Scenario Beta and Zone One orders cannot be called pre-authorized. Use a staged decision cell, with each governor issuing orders individually, and record the loss of the 30-minute order time. Do not start Zone One expansion on a single state's authority without a UC decision.
3 Is Gate G1 met at T+6 h? At least 98% of 35,800 (about 35,084) confirmed out by exit counts; no more than about 716 (incl. backcountry) under active sweep; responder coverage at least 50% at every post (at least 67 concurrent positions confirmed). Exit counts reconciled against lodging manifests and permits at the T+5 h checkpoint and at T+6 h; staffed-position count; backcountry sweep status. Treat G1 as slipped. Seat the standby reserve and request out-of-region Guard, apply the loss-of-exit rule (exit not restorable within 6 h: shelter in place and redirect), and hold the Zone One phase start until a sweep plan is set. Nothing downstream is downsized, but Zone One timing is re-planned.
4 Is an interim ranked hub list of at least 5 hubs outside the 500 km ring issued with written capacity confirmation by T+12 h? At least 5 hubs verified outside 500 km (Denver and Cheyenne are the only qualifying hubs named so far; distances not verified) with written capacity. The documents give 50,000 and 250,000 beds as the minimum; 250,000 is the more defensible floor, and the millions in the ring are not covered. Desktop distance and ash-exposure check and capacity statements from host emergency managers, reported at T+12 h. Hold the outer rings (100-250 km and 250-500 km) in later time bands and publish only the verified list. Run Beta as a staged decision cell instead of automatic authority, and add only hubs verified outside the ring.
5 Is Gate G2 met at T+24 h with shelters safe and supplied? At least 95% of registered Zone One residents out; perimeter staffed; interim destination list issued; shelters sited for at least 35,800 (15,000 Bozeman, 10,000 Idaho Falls, 10,800 third site); water at shelters by T+24 h (realistic T+18-30 h); PM10 below 100 ug/m3, or a relocation order within 4 h of exceedance. Zone One census and exit counts (census by T+6 h); shelter occupancy dashboard; convoy arrival times; hourly PM10 sensor feeds. Halt new intake at the affected shelter and divert arrivals; move to ranked 50+ km upwind backups (must accept 10,000 within 8 h); draw on the USD 5-10 million relocation reserve only; release the forward-depot water and the 100,000 N95 reserve.
6 By Month 2, are signed host MOUs from at least 5 hubs outside the 500 km ring and a written cost-share for shelters and hubs in place? At least 5 hubs with signed MOUs by Month 2; written federal vs state/local/host cost-share by Month 1 (fewer than 3 states signed by Month 1 is the FM7 tripwire); governor MOUs and EMAC signed by Month 1; full multi-state exercise by Month 3. Signed MOUs and cost-share letters (Month 1 and Month 2); exercise results (Month 3). Suspend automatic 500 km authority and revert to a staged decision cell (premortem FM2/FM7 stop rules). Keep the Zone Zero and Zone One response at its current scope, and scale back the Beta pre-positioning of USD 20-40 million until funding is settled.

What you need to decide, and by when.

5 open decisions: 3 high and 2 medium severity. Urgent before or at T+0: who may order Zone One and Beta during T+0-T+6 h, what the UC does if Beta fires before hubs are signed, and the hub capacity floor, due by T+12 h. The plan can safely run the Zone Zero evacuation, contraflow, communications and aviation grounding meanwhile. Financing and Zone One shelter demand can wait until Month 1 (2026-11-14) and T+6 h respectively.

# Decision Severity Owner Decide by Blocks
1 Scenario Beta before MOUs are signed 🔴 High Unified Command Strategic Oversight Board with FEMA Region VIII, on the governors' advice Month 0 (2026-10-14), before T+3 h: the trigger can fire inside the 72 h window and the matrix is published at T+3 h. Scenario Beta order; T+12 h interim hub list; Month 2 (2026-12-14) no-go gate.
2 Who may order Zone One or Beta during T+0 to T+6 h 🔴 High Unified Command with the MT, WY and ID governors Month 0 (2026-10-14), before T+0: needed during the peak evacuation. Zone One expansion start (T+6 h); Scenario Beta orders; Gate G1.
3 Hub capacity floor and qualifying hubs 🔴 High FEMA Region VIII Regional Administrator with the UC Month 0 (2026-10-14), before T+12 h interim hub list. T+12 h interim hub list; Month 1 (2026-11-14) written plan; Month 2 (2026-12-14) MOUs.
4 Financing of shelters, hubs and state costs 🟡 Medium FEMA Region VIII finance lead with the governors Month 1 (2026-11-14): the signed-MOU milestone. Governor MOUs and EMAC (Month 1 = 2026-11-14); host MOUs (Month 2 = 2026-12-14); Beta pre-positioning.
5 Zone One shelter demand 🟡 Medium Unified Command, Shelter Siting & Air-Quality Assurance Panel Month 0 (2026-10-14), T+6 h: shelter sites are chosen then. Gate G2 at T+24 h; shelter siting at T+6 h.

1. Scenario Beta before MOUs are signed (🔴 High)

Decision: If the Beta trigger fires inside the 72 h window before hubs and MOUs exist, does the UC issue the 500 km order in rings on the interim list, or hold in a staged decision cell?

Why it is open: Executive Summary, Review 2.1 and Pitch call Beta pre-authorized and executable; the hub list is due T+12 h, MOUs Month 2 (2026-12-14), exercise Month 3 (2027-01-14). No document says what happens before then.

Option Consequences What changes in the plan
A. Issue the 500 km order in rings on the interim list only (0-100 km first, outer rings later). Keeps the 30-minute order time; outer rings depend on unverified hubs and may lack capacity. scenario_beta_trigger, scenario_beta_execution_rings; relabel Month 2 (2026-12-14) gate as hardening.
B. Hold in a staged decision cell until hubs are verified. Loses the 30-minute order time and risks uncontrolled shadow evacuation; safer on destination capacity. scenario_beta_trigger, governance matrix, Executive Summary, Pitch.
C. Order only 0-100 km immediately; release outer rings once at least 5 hubs are confirmed. Hybrid; delays the outer rings by hours. scenario_beta_execution_rings, scenario_beta_plan_milestones.

2. Who may order Zone One or Beta during T+0 to T+6 h (🔴 High)

Decision: Who has authority to order Zone One expansion or Beta before verbal governor authorization is obtained at T+6 h?

Why it is open: The pitch and reviews say pre-authorized; canonical governor_authorization is only verbal by T+6 h and USGS values exist only at T+3 h.

Option Consequences What changes in the plan
A. Each governor issues orders individually until T+6 h. State authority is clear but orders are not synchronized; 30-minute order time is lost. governor_authorization, Pitch, Review 2, Review 3.2.
B. The UC orders under federal authority from T+0. Fast and unified; legal basis and governor consent must be confirmed. governor_authorization, command_structure, authority_handoff_point.
C. Obtain governor pre-authorization before T+0 by standing agreement. Not achievable given the rebased lead times; would need an earlier project phase. pre_event_lead_times_rebased.

3. Hub capacity floor and qualifying hubs (🔴 High)

Decision: What single capacity floor and which hubs outside the 500 km ring will be used for Beta?

Why it is open: A1 uses 50,000 beds; FM2 and Self-Audit use 250,000; the ring holds millions. Only Denver and Cheyenne qualify; Review 12.3 uses Utah/Idaho, which are inside the ring.

Option Consequences What changes in the plan
A. Floor 250,000 beds across at least 5 verified hubs outside 500 km. More defensible; needs 3+ more named hubs after a distance check; still below the ring population. Premortem A1/FM2, Self-Audit 11, Review 12.3, scenario_beta_second_stage_hubs.
B. Keep 50,000 beds as the minimum. Easier to meet at T+12 h; far under-sized for the ring. Premortem FM2, Self-Audit.
C. Size the floor to a stated share of the ring population once estimated. Most rigorous; needs a population figure (not quantified); delays the number. scenario_beta_population, hub thresholds.

4. Financing of shelters, hubs and state costs (🟡 Medium)

Decision: What is the federal vs state/local/host split for shelter sites, secondary hubs and state costs, and what counts against the USD 200 million envelope?

Why it is open: Canonical says OPEN. Reviews 11/Self-Audit 6 date it Month 0 (2026-10-14) and T+12 h, others Month 1 or 2 (2026-11-14, 2026-12-14); Self-Audit 18 shows a 10-20% state match as if settled.

Option Consequences What changes in the plan
A. Federal funds 100% of pre-positioning. Fast MOU signing; raises federal draw within the USD 160 million base. financing_open_decision, readiness_package_cost, FM7.
B. Federal plus state match (e.g. 10-20%). Lowers federal cost; slows MOUs and risks the FM7 tripwire (fewer than 3 states by Month 1 = 2026-11-14). financing_open_decision, Self-Audit 18, governor MOUs.
C. Host-community in-kind contribution. Least federal cost; hubs may decline, reducing capacity. financing_open_decision, hub MOUs.

5. Zone One shelter demand (🟡 Medium)

Decision: Are Zone One residents inside the 35,800 shelter capacity or additional, and what overflow or self-supply approach applies?

Why it is open: Shelters and water are sized for Zone Zero only; Gate G2 needs 95% of Zone One out, and the base is not quantified (census due T+6 h).

Option Consequences What changes in the plan
A. Count Zone One within 35,800 using a county/lodging proxy at T+0-T+3 h. No added capacity; likely overrun. shelter_capacity_plan, zone_one_resident_population.
B. Add overflow capacity beyond 35,800. Raises cost and water/N95 needs; the site list needs a larger ranking. shelter_capacity_plan, water_supply_target, budget.
C. Outer-zone self-supply message with limited shelter. Lower cost; relies on residents' own means. communications_stack, phase2_go_gate.

Choices made on your behalf

Set when the scenario was selected, not by you. Confirm or change them.

Lever Chosen Strongest alternative Why it matters Revisit by
Egress corridor allocation Three gates (West, North, East toward Cody) with fixed district-to-gate assignment. Two corridors to I-90 (Consolidator) or bus-based loading (Pioneer). Sets throughput and the G1 load split of 50/30/20. Gate G1 (T+6 h)
Escalation trigger doctrine Written USGS trigger matrix, UC issues the 500 km order without further approval. Standing volcanologist-and-governor decision cell. Speed against authority and hub readiness. T+3 h matrix publication; Month 2 (2026-12-14)
Command structure Denver RRCC with forward UC element at Livingston (alt. Bozeman). Single UC with rotating state deputies. Determines handoff clarity across Region 8/10. Month 1 (2026-11-14) MOUs
Communications stack IPAWS/WEA/NOAA radio primary, Guard signal bridging. Printed route cards and battery radios. Tower failure would cut the primary public channel. Gate G1
Shelter siting Final sites at T+6 h from plume forecast, ranked backups. Fixed pre-stocked reception centers. Flexibility against supply readiness and water arrival. T+6 h

Key numbers and dates.

Kind: user constraint = from your prompt; decision = chosen in this plan; proposed threshold = a pass/fail line proposed in this plan, to be confirmed; estimate = not verified.

Fact Value Kind Basis
project_start_and_t0 Month 0 (2026-10-14) = project start = T+0 (evacuation order and Unified Command activation) decision Today is Month 0 (2026-10-14) and the user says 'start ASAP'; all operational times are hours from T+0 inside Month 0 (2026-10-14), and all later readiness work is stated as month offsets from Month 0 (2026-10-14).
decision_window 72 hours (T+0 to T+72, within Month 0 = 2026-10-14); Scenario Alpha VEI-6+ probability 40% within this window user constraint Stated in the plan prompt; the 40% is the user's modeled figure and is not independently verified.
pre_event_lead_times_rebased Pre-event items set at 'Month -2', 'Month -1', '60/30 days before T+0' or 'T-48 h' are not achievable; replaced by T+0 to T+12 h actions and Months 1-3 (2026-11-14 to 2027-01-14) hardening decision The pre-project assessment and risk files use negative months, but Month 0 (2026-10-14) is today and the eruption window opens now; rejected as infeasible, while the intent (MOUs, exercises, pre-positioning) is kept on compressed timelines.
zone_zero_evacuees 35,800 people (approx. 35,000 tourists + 800 park staff) user constraint User figures 35,000 + 800; used as the sizing base for exits, shelters and water. Rangers (100-150) are part of the 800 staff and leave last.
zone_zero_clearance_deadline T+6 hours (Phase 1: T+0 to T+6) user constraint User Phase 1 window for evacuating the park interior.
zone_one_scope_deadline 100 km radius incl. West Yellowstone (MT), Gardiner (MT), Cody (WY); evacuated by T+24 hours (Phase 2: T+6 to T+24) user constraint User Phase 2 scope. Bozeman and Livingston are treated as outer-zone reception cities, not ordered Zone One towns (Risk 12 listing Bozeman as Zone One rejected as it conflicts with its shelter role).
zone_one_resident_population Not quantified in any document (open item); census of registered residents required by T+6 h estimate No document gives a Zone One census; the earlier draft figure of roughly 12,000 had no source and was removed. The census is needed before the Phase 2 gate can be measured and shelters sized beyond park evacuees.
exit_corridors 3 exits: West (US-20/US-191 via West Yellowstone, Gallatin Canyon to Bozeman/I-90), North (US-89 via Gardiner to Livingston/I-90), East (US-14/16/20 toward Cody); fixed district-to-gate assignment decision Pragmatic Foundation scenario (fit 8/10) adds the East Entrance to the user's two corridors; Consolidator's two-corridor funnel and Pioneer's bus-lane suspension were rejected. East flow still needs onward routing since Cody is itself in Zone One.
south_entrance_status Written off as baseline exit; one time-boxed single-lane clearance attempt of max 4 hours, abort on any M4.0+ event during work (proposed threshold) proposed threshold Slide is a user-stated constraint. The 'renewed M4.0+' abort trigger is a proposed value; since the swarm already includes M4.5+, aborts are likely, so the plan must not depend on this route (Risk 15's '12-hour' failure case rejected as planning basis).
required_outbound_throughput About 11,900 vehicles at 3.0 persons/vehicle (estimate); about 2,000 vehicles/hour average over 6 h; about 660 vehicles/hour per exit at an even three-way split estimate Recomputed: 35,800 / 3.0 = 11,933 vehicles; 11,933 / 6 h = 1,989 veh/h; / 3 = 663 veh/h. Occupancy of 3.0 is an assumption; no document gives lane capacity. The planned 50/30/20 split (see gate_load_split) loads the West gate above the even-split figure.
gate_load_split West 50% = 17,900; North 30% = 10,740; East 20% = 7,160 people (total 35,800) proposed threshold Planning split by park district; percentages are a proposal (documents give no split) and must be confirmed by the incident commander; shares sum to 100% and 35,800. Recomputed at 3.0 persons/vehicle over 6 h: West about 994 veh/h, North about 597 veh/h, East about 398 veh/h, so the West corridor is the binding gate.
contraflow_operational_time Contraflow active on all three corridors by T+1 hour proposed threshold Needed for the average 2,000 veh/h to be reached within the T+6 window; not stated in documents.
corridor_blockage_diversion_threshold Blockage > 45 minutes triggers diversion of overflow to the nearest surviving exit (adds 2-4 h transit for some); tow/rockfall teams (at least 2) reach any Gallatin Canyon blockage within 15 min proposed threshold Risk 1 and Issue 4 propose 45 min and 15 min; estimated clear time 2-4 h. Adopted as proposals, not established values.
loss_of_exit_rule Exit not restorable within 6 hours: shelter-in-place for queued vehicles and redirect to nearest surviving exit proposed threshold Risk 15 loss-of-exit contingency; 6 h is a proposed value.
command_structure Unified Command at FEMA Region VIII RRCC Denver, with FEMA Region 10 (Idaho) liaison seated from T+0 and a forward UC element at Livingston, MT (alternate: Bozeman) decision Denver is user-mandated. Livingston chosen over Bozeman for sight of US-89 and the I-90 junction and to avoid co-locating command with the Bozeman reception center; both sit near the Zone One edge, so relocation to the alternate is pre-planned.
authority_handoff_point NPS to state governor authority transfers at the park boundary at each gate (West, North, East Entrance); a Boundary Coordination Officer at the forward element owns reroutes and initial shelter assignment during the crossing decision User requires handoff when evacuees cross park boundaries. Assessment suggestions of Mammoth (inside the park), Gallatin County line and Cody city limits (far downstream) rejected because they create a gap or contradict the boundary rule.
governor_authorization Verbal pre-authorization of UC Zone One and Scenario Beta orders from MT, WY and ID governors by T+6 h; signed MOUs and EMAC arrangements by Month 1 (2026-11-14) proposed threshold The assessment's 'signed 30-60 days before T+0' is impossible when T+0 is Month 0 (2026-10-14); compressed to a verbal commitment within the window and a signed instrument within the first month.
phase1_go_gate Gate G1 at T+6: at least 98% of 35,800 (about 35,084) confirmed through exit counts; remainder (at most about 716, incl. backcountry) under active sweep proposed threshold Recomputed: 0.98 x 35,800 = 35,084; 2% = 716. Phase 1 criterion on park interior only; the 98% value is proposed. Zone Zero evacuation itself is not gated on planning documents, as the assessment's 'do not start until all actions are tested' is unworkable under a 72-hour threat.
phase2_go_gate Gate G2 at T+24: at least 95% of registered Zone One residents out, perimeter staffed, and Scenario Beta interim destination list issued proposed threshold Distinct from G1 (residents and Beta readiness vs. park visitors); 95% is proposed and cannot be measured until the Zone One census (due T+6 h) exists.
backcountry_stragglers About 200-400 people in 50-100 parties may remain; permit cancellation and hourly check-ins from T+0; 2-3 last-resort shelters outside the ash footprint estimate Risk 7 estimates (50-100 parties x about 4 people = 200-400); counts are unverified and depend on permit data.
scenario_beta_trigger Pre-authorized written USGS trigger matrix; UC issues the 500 km order without further approval within 30 min of trigger; placeholder trigger: modeled VEI-7 probability at or above 20% in the remaining window (USGS to set final indicator values by T+3 h) proposed threshold User requires a trigger point; no document gives numeric VEI-7 thresholds, so the 20%, 30 min and T+3 h are proposals. Standing decision cell (Consolidator) rejected as too slow.
scenario_beta_execution_rings 500 km order issued immediately; executed in rings: 0-100 km organized evacuation; 100-250 km time-banded evacuation; 250-500 km staged departure in later time bands decision User requires evacuation expansion to 500 km immediately; the review's 'shelter-in-place at 250-500 km' conflicts with that and is rejected unless the user approves; time-banding addresses road capacity.
scenario_beta_population Millions of people (not quantified); documents' 100,000-500,000 additional evacuees understates the ring estimate Decision 2 says a 500 km radius reaches millions; Salt Lake City metro alone is above 1 million (not verified). Review/risk figures of 50,000-500,000 rejected as inconsistent with the stated radius.
scenario_beta_second_stage_hubs Hubs must lie outside the 500 km ring: Denver and Cheyenne qualify (distance not verified); Salt Lake City, Billings, Bozeman, Idaho Falls and probably Boise are inside and cannot serve as Beta destinations decision The risk/review lists SLC, Billings and Boise as hubs, but approximate straight-line distances from Yellowstone are under about 500 km; rejected as destinations for a 500 km order. Further hubs outside the ring remain to be named.
scenario_beta_plan_milestones Interim ranked hub list (at least 5 hubs outside the ring) by T+12 h; written second-stage plan by Month 1 (2026-11-14); signed host MOUs by Month 2 (2026-12-14); full multi-state exercise by Month 3 (2027-01-14) proposed threshold Replaces the assessment's 'Month -2' plan and 30-day exercise, which predate Month 0 (2026-10-14); order plan -> MOUs -> exercise is feasible.
shelter_capacity_plan Bozeman 15,000 and Idaho Falls 10,000 (estimate) plus a third site/backups of 10,800 selected at T+6 h; total at least 35,800 estimate Risk 5 gives 15,000 and 10,000; 35,800 - 25,000 = 10,800 is derived so capacity matches park evacuees. Residents' needs are additional and open pending the census.
shelter_siting_rule Final shelter sites chosen at T+6 h from the latest NOAA/USGS plume forecast; ranked backups 50+ km upwind; relocation order within 4 h of exceedance proposed threshold Pragmatic Foundation choice (wind-adaptive siting); 50 km and 4 h from the risk/review files. Bozeman and Idaho Falls are not assumed ash-safe.
ash_monitoring_thresholds PM10 above 50 ug/m3 triggers forecast update; above 100 ug/m3 triggers shelter-suitability review; sensors at forward element and every shelter proposed threshold Assessment values; proposals needing USGS/NOAA confirmation.
water_dispatch_vs_arrival Convoys dispatched from Salt Lake City by T+12 h; arrival at shelters expected T+18 to T+30 h (estimate); target arrival by T+24 h via forward depots user constraint The 12 h is the user's mobilization requirement; arrival estimate is from Risk 5. 12-hour delivery is not claimed. Under Beta, Salt Lake City lies inside the evacuation ring, so alternate sources (Pocatello, Butte) are needed.
water_supply_target About 1.43 million liters for 10 days at 35,800 shelter occupants and 4 L/person/day (estimate) estimate Recomputed: 35,800 x 4 x 10 = 1,432,000 L; sized to the full shelter capacity plan (35,800) rather than only the two named sites (25,000 x 4 x 10 = 1,000,000 L, superseded). 10 days from Risk 5, 4 L/day is an assumption; residents' needs are additional.
n95_civilian_stock 100,000 N95 respirators pre-staged for civilians user constraint User requirement; masks clog quickly in heavy ash, so demand may exceed it within days.
n95_reserve_and_responder_stock Supplemental reserve of 100,000 at Billings or Salt Lake City hub (resupply if use exceeds 20% of stock per day); responder N95s counted separately, sized from responder headcount, not drawn from the 100,000 proposed threshold Reserve and 20%/day trigger from Risk 9; review's 150,000-200,000 total rejected as it blends responder and civilian counts. Responder count is an open item. Both hub options lie inside the Beta ring, so the reserve needs a relocation option under Beta.
responder_staffing_base 100-150 NPS rangers (estimate) at 1.5 relief ratio gives about 67-100 concurrent positions; plus MT/WY/ID patrol and Guard estimate Recomputed 100/1.5 = 67 and 150/1.5 = 100; Issue 2's claim of 100-150 positions rejected as it implies a 1.0 ratio. Guard and patrol headcounts are not given.
responder_exposure_limits Max 6 h shift at ash-exposed posts, then 2 h rest with N95 replacement; full withdrawal after 18 consecutive hours proposed threshold Risk 10/Issue 2 proposal; applies from T+0.
standby_reserve 30-50 out-of-region traffic-control responders deployable within 4 h; request out-of-region Guard if coverage falls below 50% at any post proposed threshold Risk 10/Issue 2; ranger hours are exhausted in T+2 to T+8 (estimate), so relief depth is the binding staffing constraint.
aviation_grounding Indefinite grounding of commercial and private aviation in FAA ZLC and ZSE; narrow government rotary-wing medevac/survey exceptions requested by UC and authorized by FAA user constraint Grounding is user-mandated; the narrow exception (Decision 11 choice 2) is compatible because it excludes commercial/private flights, and FAA retains airspace authority; ash-concentration limits are to be set by FAA/USGS (the 100 ug/m3 figure was an example only).
communications_stack IPAWS/WEA/NOAA Weather Radio primary; Guard signal teams with satellite phones and repeaters at each control point and the forward element from T+0; HAR/VMS on US-191, US-20, US-89, I-90; route cards in English plus 5 languages (Spanish, Japanese, German, Mandarin, French) decision User names IPAWS and Guard signal bridging; layers and languages come from Risk 2/11 and are proposals; 'T-12 h' deployment is rebased to T+0.
fuel_priority_and_hospital_reserve Generator fuel tiers: hospitals, comms centers, shelter kitchens; 72-hour reserves at three receiving hospitals (Bozeman, Livingston, Idaho Falls) proposed threshold User requires hospital/comms fuel priority; the 72 h and the three named hospitals come from Risk 6; delivery by T+12 h instead of T-48 h.
procurement_constraint Without pre-awarded contracts, procurement takes 24-48 h (estimate); use existing FEMA contract vehicles with verbal activation and 12 h dispatch clauses from T+0 estimate Risk 13; 60-days-ahead contracting is impossible, so existing vehicles are used first and formal contracts follow by Month 1 (2026-11-14).
budget_envelope USD 200 million planning envelope (estimate range USD 150-250 million) = USD 160 million base + USD 40 million contingency (20% of envelope) estimate Assumptions give USD 150-250 million (estimate) and a 20% contingency (proposed); the user set no cap. The midpoint is used and 160 + 40 = 200 million; 40/200 = 20% (20% of the base would be 32 million; the envelope-based reading is adopted).
readiness_package_cost USD 47.5-87 million (estimate), charged to the USD 160 million base: Beta hubs 20-40, responder reserve 3-5, N95 reserve/backup shelters 10-15, tow teams 2-3, MOUs/exercises 0.5-1, comms 5-10, multilingual/shuttles 2-3, hospital fuel/utility 5-10 estimate Recomputed: low 20+3+10+2+0.5+5+2+5 = 47.5; high 40+5+15+3+1+10+3+10 = 87. The review's USD 30-60 million covers only its three headline actions. Leaves USD 73-112.5 million of base uncommitted (160 - 87 to 160 - 47.5).
fallback_budget_fit Shelter relocation (USD 5-10 million) is the only identified draw on the USD 40 million contingency; Beta hub pre-positioning (USD 20-40 million) is already inside the readiness package and is not counted again estimate Earlier draft added relocation 5-10 to Beta hubs 20-40 (25-50 vs 40, 'exceeds by 10') and double-counted the Beta hub cost already in the base package. Corrected: contingency draw 5-10 of 40. Beta hub costs above their 20-40 allowance, and Beta execution (moving millions), would draw on contingency and are unfunded in the envelope.
free_contingency_after_draws USD 30-35 million free contingency (USD 40 million less USD 5-10 million shelter relocation reserve) estimate Recomputed: 40 - 10 = 30 and 40 - 5 = 35. The relocation amount sits inside the contingency, so it reduces the free contingency; it must not be counted again against the base. Any Beta hub overrun reduces this figure further.
revenue_and_debt_chain No revenue, fares or debt; entire cost is publicly funded (Stafford Act declaration, FEMA reimbursement); annual surplus/debt service not applicable decision This is a civil-protection operation, not a revenue project; the economic chain is therefore a cost chain: envelope USD 200 million vs readiness USD 47.5-87 million and USD 30-35 million free contingency.
financing_open_decision OPEN: who finances shelter sites, secondary hubs and state costs (federal share vs. state/local/host-community) is not stated; only program-financed items count against the USD 200 million envelope decision Documents mention Stafford Act declaration-based cost-sharing without percentages; stated as an open decision rather than chosen silently.
post_window_hardening Months 1-3 (2026-11-14 to 2027-01-14): signed MOUs (governors, Region 10, utilities, hubs), after-action report, full-scale Beta, shift-rotation and water-convoy exercises decision Moves the 30/60-day-before exercises to after the 72-hour window; applies whether or not an eruption occurs, since unrest may persist.

Focus and Context

A 72-hour multi-state evacuation plan for Yellowstone National Park evacuates 35,800 people (Zone Zero: T+0 to T+6h) and regional communities (Zone One: T+6 to T+24h), with pre-authorized Scenario Beta expansion to 500 km if USGS eruption indicators trigger. The plan hardens operational readiness through signed MOUs, supply pre-positioning, and full-scale exercises by Month 3 (2027-01-14), establishing the first Yellowstone-scale evacuation framework under extreme time pressure and volcanic ashfall hazard.

Purpose and Goals

Primary goals: (1) Clear 35,800 Zone Zero evacuees via three contraflow exits by T+6h (Gate G1: ≥98% confirmation); (2) evacuate 100 km Zone One residents by T+24h (Gate G2: ≥95%); (3) finalize and pre-authorize Scenario Beta second-stage hub plan with signed MOUs by Month 2 (2026-12-14) to enable 500 km expansion if triggered. Success criteria: zero authority gaps at state boundaries, real-time shelter siting under ashfall monitoring, and responder relief depth sustained through T+72h.

Key Deliverables and Outcomes

• Zone Zero clearance certified by T+6h via exit counts and backcountry sweep status. • Zone One evacuation ≥95% by T+24h with perimeter security active. • Interim ranked hub list (≥5 hubs outside 500 km ring) published by T+12h; written Scenario Beta plan by Month 1 (2026-11-14); signed host MOUs by Month 2 (2026-12-14). • Water/N95/fuel convoys dispatched by T+12h; target arrival at shelters T+24h via forward depots (realistic T+18–30h, estimate); success criterion is forward-depot pre-staging of 200,000–300,000 L (estimate). • Full-scale exercises (Beta routing, shift rotation, shelters) completed by Month 3 (2027-01-14). • After-action report and institutional-memory documentation finalized by Month 3 (2027-01-14).

Timeline and Budget

Operational response: Month 0 (2026-10-14) T+0 to T+72h. Hardening: Months 1–3 (2026-11-14 to 2027-01-14). Budget: USD 200 million envelope (range USD 150–250 million estimate); USD 47.5–87 million readiness package; USD 30–35 million free contingency after shelter relocation reserve. Pre-event capital (sensors, exercises, MOUs) funded from base; Scenario Beta hub pre-positioning within envelope.

Risks and Mitigations

Risk 1 (Critical): Scenario Beta has no executable second-stage destinations, risking cascade failure of Zone Zero evacuation. Mitigation: Finalize written plan with 5–10 named hubs (outside 500 km) and signed MOUs by Month 2 (2026-12-14); issue interim hub list by T+12h. Risk 2 (Critical): Responder staffing (100–150 rangers) has zero relief depth; single incident halts a corridor 2–4h. Mitigation: Pre-authorize 30–50 standby reserve deployable within 4 h of T+0 and Guard reinforcement if coverage <50%. Risk 3 (Critical): Shelter siting at T+6h with ±50 km forecast uncertainty and no real-time monitoring places 10,000–15,000 evacuees in heavy ashfall. Mitigation: Deploy PM10 sensors by T+0, pre-authorize 4-hour relocation protocols with backup sites 50+ km upwind.

Audience Tailoring

Audience: FEMA Regions VIII and X, state governors (Montana, Wyoming, Idaho), NPS incident management, hospital and utility executives, and multi-state Unified Command stakeholders. Tone: operational, directive, risk-transparent. Detail emphasizes life-safety milestones (Gates G1, G2), blocking dependencies (Scenario Beta hub MOUs), and resource readiness metrics rather than theoretical frameworks.

Action Orientation

By T+0 (Month 0 = 2026-10-14): Seat Unified Command and Region 10 liaison, deploy Guard signal teams and PM10 sensors, position tow/rockfall teams. By T+1h: Contraflow active on all three exits. By T+6h: Obtain verbal governor authorization; census of Zone One residents; assess Gate G1 (≥98% of 35,800 out). By T+12h: Issue Scenario Beta interim hub list; dispatch water/fuel convoys. By T+24h: Confirm Gate G2 (≥95% Zone One cleared); water/N95 arrival targeted via forward depots (realistic T+18–30h, estimate). By Month 1 (2026-11-14): Sign governor MOUs and EMAC agreements, finalize Scenario Beta written plan. By Month 2 (2026-12-14): Secure signed host MOUs from 5–10 hubs outside 500 km ring. By Month 3 (2027-01-14): Complete full-scale Beta, shift-rotation, and water-convoy exercises; publish after-action report.

Overall Takeaway

This plan transforms Yellowstone volcanic evacuation from theoretical risk to operational readiness: 35,800 people move in 6 hours via pre-authorized corridors and unified command; regional life-support (shelter, water, power, respirators) is hardened through signed interstate MOUs and supply pre-positioning; and a 500 km Scenario Beta expansion is executable—not hollow—only if second-stage hubs are named, validated and committed by Month 2 (2026-12-14). Without these three blocking dependencies (Scenario Beta plan, responder relief depth, ashfall monitoring), residual cascade-failure risk remains unacceptable. With them, the plan delivers life-safety assurance delivered by a USD 47.5–87 million readiness package (estimate) within the USD 200 million planning envelope and sets the institutional precedent for Yellowstone readiness in the 40-year eruption window.

Feedback

Strengthen by adding: (1) Explicit cost-benefit analysis (USD 47.5–87 million readiness package (estimate) vs. USD 500–800M post-event emergency response + 20–50 preventable deaths averted; USD 200 million is the planning envelope). (2) Quantified Zone One resident population from census by T+6h (population currently unquantified). (3) Distance verification (Denver, Cheyenne to Yellowstone) confirming they lie outside 500 km ring. (4) Financing clarity: federal vs. state/local/host-community cost-share for shelters and secondary hubs by Month 1 (2026-11-14). (5) Responder staffing validation: confirm actual Ranger headcount and pre-authorize Guard reinforcement commitment in signed letters by Month 1 (2026-11-14). (6) Water-convoy realistic arrival time (T+18–30h, not T+12h dispatch) and forward-depot pre-staging (200,000–300,000 liters, estimate) to close the 18–24h shelter water-supply gap if convoys are delayed.

Unoptimized waterfall. Parallel work not modelled here.

Part 2: Supporting analysis

Persuasive elevator pitch.

Yellowstone Volcanic Evacuation Readiness Plan

Project Overview

When a volcano wakes, 35,800 people must move in six hours. Yellowstone sits above one of Earth's most volatile caldera systems. A VEI-6 eruption has a 40% probability within the next 72 hours. This project hardens the evacuation of Zone Zero (the park) and a 100 km ring of gateway towns, ensuring that when the alarm sounds, three contraflow corridors, a unified command chain, and pre-positioned shelter and supply networks activate within minutes—not days. Without it, gridlock, communication failure, or ash-stranded responders cascade into a multi-state catastrophe. With it, 35,800 people walk away, and regional hospitals and utilities stay online under ashfall. This is operational readiness at scale.

The plan moves from immediate evacuation (Phases 1 and 2, T+0 to T+24 hours) to pre-authorized escalation (Scenario Beta, 500 km ring) if eruption probability rises. All actions at T+0 onward proceed under verbal governor authorization by T+6 hours, with MOUs by Month 1 (2026-11-14); pre-event hardening occurs in Months 1–3 (2026-11-14 to 2027-01-14), with signed interstate Memoranda of Understanding (MOUs), validated shelter hubs, and full-scale exercises cementing the framework before any eruption occurs.

Target Audience

Project Overview: Operational Framework

Zone Zero (the park) contains approximately 35,800 people: 35,000 tourists and 800 park staff. They must clear three designated exits—West (via West Yellowstone), North (via Gardiner), and East (toward Cody)—by T+6 hours.

Zone One extends 100 km and includes West Yellowstone (MT), Gardiner (MT), and Cody (WY). Registered residents (count not yet quantified) must evacuate by T+24 hours.

Scenario Beta activates a pre-authorized order for a 500 km ring (millions of residents) if USGS modeling indicates a 20% or higher VEI-7 probability (proposed threshold; USGS sets final values by T+3 h). This order is issued within 30 minutes of the trigger; execution proceeds in rings: 0–100 km organized evacuation, 100–250 km time-banded evacuation, 250–500 km staged departure.

Core operational elements:

Risks and Mitigation Strategies

Metrics for Success

Phase 1 (T+6 hours): At least 98% of Zone Zero evacuees (≥35,084 people) confirmed through exit counts; fewer than 716 remain under active sweep.

Phase 2 (T+24 hours):

Responder continuity:

Communications:

Post-event: After-action report and full-scale exercise completed by Month 3 (2027-01-14); MOUs signed by Month 2 (2026-12-14).

Stakeholder Benefits

FEMA: Pre-positioned incident command, mutual-aid framework, and supply-chain protocols reduce activation time and post-event cost claims; Region 8/10 seam resolved before the event.

Governors: Clear authority transfer at park boundary, pre-authorized escalation to 500 km without jurisdictional disputes; life-safety and business-continuity assurance to constituents.

NPS: Operational command at T+0, ranger exposure limits enforced, backcountry accountability transparent; federal incident-management credibility enhanced.

Gateway towns and hospitals: Shelter and supply staging in advance, patient-dispersal protocols, fuel and water priority tiers guarantee continuity during ashfall.

Regional utilities: Grid-power priorities and backup-generation contracts in place.

The public: Transparent trigger criteria, multilingual alerts restore trust and reduce chaos-driven shadow evacuation.

Ethical Considerations

The plan prioritizes life preservation and equity:

Collaboration Opportunities

Inter-agency:

Regional:

Hospital and utility networks:

Community and concessioner:

Academic:

Long-term Vision

This plan establishes the first operational, pre-authorized evacuation framework for a Yellowstone-scale volcanic event, serving as the model for other caldera systems (Long Valley, Campi Flegrei) and ash-hazard zones worldwide. By Month 3 (2027-01-14), the framework matures into signed MOUs, validated second-stage hubs, and a rehearsed Scenario Beta operation, making it the standard of readiness for societal-scale hazards. Over the following years, the plan feeds into National Incident Management System doctrine, FEMA Regional training, and state emergency-management curricula, extending its influence to wildfire evacuation, hurricane contraflow, and other large-scale life-safety operations. The USD 200 million planning envelope (of which the USD 47.5–87 million readiness package is an estimate) protects 35,800 lives immediately and builds institutional capacity for the next 40 years of Yellowstone's activity window, anchoring regional resilience in science-based decision rules and executed, not theoretical, logistics.

Call to Action

Activate the readiness package by Month 1 (2026-11-14):

Request appropriations for the USD 47.5–87 million readiness base:

Escalation trigger: If modeled VEI-7 probability reaches at least 20% in the remaining window (placeholder, proposed threshold; USGS values final by T+3 h), the Unified Command issues the Scenario Beta order within 30 minutes and transitions immediately to operational Scenario Beta zones and second-stage hub pre-positioning.

Goal Statement: Evacuate about 35,800 people (35,000 tourists and 800 staff) from Yellowstone Zone Zero by T+6 hours and the 100 km Zone One by T+24 hours, then sustain regional life support under ashfall, with a pre-authorized 500 km Scenario Beta order and second-stage hub plan hardened by Month 3 (2027-01-14).

SMART Criteria

Dependencies

Resources Required

Related Goals

Tags

Risk Assessment and Mitigation Strategies

Key Risks

Diverse Risks

Mitigation Plans

Stakeholder Analysis

Primary Stakeholders

Secondary Stakeholders

Engagement Strategies

Regulatory and Compliance Requirements

Permits and Licenses

Compliance Standards

Regulatory Bodies

Compliance Actions

Primary Decisions

The vital few decisions that have the most impact.

Critical levers (egress corridors, escalation trigger, command handoff) govern the central tensions: throughput versus staffing, speed versus over-evacuation, and unified authority versus fixed boundaries. High levers (communications, shelter siting, life-support supply, responder limits) set the capacity and endurance that these decisions depend on. Missing dimensions: explicit second-stage destinations for a 500 km Scenario Beta evacuation, and responder respirator and personnel counts.

Decision 1: Egress Corridor Allocation and Contraflow Architecture

Lever ID: 9aa4c682-17a1-42d8-a2af-8f62ac4d54b2

The Core Decision: Defines which park exits carry the roughly 35,000 visitors and 800 staff, how contraflow is staged, and where traffic control, tow and rescue assets sit. Success metrics are corridor throughput in vehicles per hour, clearance of the interior within the T+6 window, minimum blockage duration at chokepoints, and no vehicle crossing the interior to reach another gate.

Why It Matters: Determines how the roughly 35,000 visitors and 800 staff are split across the surviving exits once the South Entrance is landslide-blocked. Concentrating flow on US-191/US-20 at West Yellowstone and US-89 at Gardiner is simple to run, but it loads a few two-lane chokepoints; opening additional exits spreads load but adds ranger and signage demand.

Strategic Choices:

  1. Funnel all outbound traffic through two contraflow corridors, US-20/US-191 from West Yellowstone and US-89 from Gardiner to I-90 at Livingston, with ranger-staffed traffic control points at every junction.
  2. Split outbound flow across three gates by adding the East Entrance toward Cody on US-14/16/20, assigning each park district to a fixed exit so no vehicle crosses the interior to reach another gate.
  3. Suspend private-vehicle exit lanes at the Madison and Mammoth staging lots and load visitors onto concessioner buses and park fleet vehicles, so one contraflow lane carries more people per vehicle.

Trade-Off / Risk: Contraflow on mountain two-lane roads has no shoulder or recovery margin, so a single breakdown or rockfall near Gallatin Canyon or Gardiner can halt the entire corridor; the plan needs tow and rescue assets pre-placed at each chokepoint.

Strategic Connections:

Synergy: Amplifies Landslide Clearance and Hydrothermal Hazard Road Engineering by telling crews which road segments matter most, and relies on Communications Continuity Stack Under Ash and Tremor to deliver route assignments consistently to drivers at each junction.

Conflict: Competes with Responder Exposure Limits and Relief Rotation Regime for ranger and patrol staffing at control points, and with Visitor Headcount Reconciliation and Backcountry Sweep Protocol, which pulls rangers from traffic duty into interior sweeps.

Justification: Critical, Central hub: it governs the Phase 1 T+6 clearance of roughly 35,000 visitors and conflicts with or feeds nearly every other lever (staffing, sweeps, convoys, hospital transport, road engineering). It controls the core throughput versus staffing trade-off.

Decision 2: Escalation Trigger and Evacuation Release Doctrine

Lever ID: bd25cabe-83c3-4a75-a57b-fda21488eb09

The Core Decision: Fixes which USGS indicators, such as uplift rate, tremor magnitude and gas flux, trigger zone expansion and who may issue the order. It governs the timing of Zone One and Scenario Beta decisions during the 72-hour window. Success metrics are decision latency, false-trigger rate, and the time from trigger to the first outbound movement.

Why It Matters: Sets which USGS signals, such as uplift rate, tremor magnitude and gas flux, automatically push the evacuation from Zone Zero to Zone One and, in Scenario Beta, to a 500 km radius. A pre-authorized trigger removes debate during the 72-hour window, but it risks costly over-evacuation if the signals mislead; a discretionary one is slower and exposes decision makers to hindsight blame.

Strategic Choices:

  1. Pre-authorize a written, threshold-based trigger matrix tying specific USGS indicators to automatic zone expansion, with the VEI-7 500 km order issued by the Unified Command without further approval.
  2. Keep a standing volcanologist-and-governor decision cell that meets at fixed intervals and recommends expansion, retaining human judgment but accepting added delay at each decision point.
  3. Begin a quiet precautionary outer-ring evacuation of vulnerable groups, such as hospitals, care homes and families with children, beyond 100 km before any VEI-7 indicator appears, so a later order has fewer people to move.

Trade-Off / Risk: A 500 km radius would reach multiple states and millions of people, far beyond the shelter and road capacity in this plan, so the trigger is meaningless without a stated plan for where those evacuees actually go.

Strategic Connections:

Synergy: Enables Refugee Intake and Shelter Siting Strategy and Exclusion Perimeter Posture and Re-Entry Access Control by giving them an advance signal to stage sites and perimeters, and supports Command Structure and Jurisdictional Handoff Model with pre-agreed authority.

Conflict: Early or automatic expansion strains Refugee Intake and Shelter Siting Strategy and Hospital Surge Dispersal and Respiratory Patient Routing, which lack capacity for a 500 km radius, and may fuel Shadow Evacuation Suppression and Public Compliance Dynamics if triggers prove false.

Justification: Critical, Controls the speed versus over-evacuation trade-off across the 72-hour window and the Scenario Beta 500 km decision. It drives staging for shelters, perimeters and command authority, and strains shelter and hospital capacity if triggered.

Decision 3: Command Structure and Jurisdictional Handoff Model

Lever ID: c5f01e05-5b98-45c5-a1e2-b13bf9b7e0be

The Core Decision: Sets who commands the roadway, shelters and resource requests as evacuees move from NPS land into Montana, Wyoming and Idaho, and how the Denver RRCC relates to any forward element. Success is judged by the absence of authority gaps at the boundary, clear single-point accountability, and fast resolution of cross-state mutual aid and FEMA Region 8/10 coordination.

Why It Matters: Decides where authority sits as evacuees cross from NPS-managed federal land into Montana, Wyoming and Idaho. A fixed boundary handoff is easy to explain, but traffic does not stop at the line, so gaps appear where the road is still moving; shared command avoids gaps but blurs accountability.

Strategic Choices:

  1. Transfer authority at the park boundary under a written protocol, with the NPS incident commander handing traffic and care responsibility to each state's designated commander at defined checkpoints.
  2. Run a single Unified Command with a rotating deputy from each state and NPS, so authority over the roadway is joint from the interior through the first gateway town.
  3. Place a forward Unified Command element in Bozeman or Livingston alongside the Denver RRCC, giving the incident commander direct sight of the corridors while Denver handles federal resource requests.

Trade-Off / Risk: Denver RRCC serves FEMA Region VIII, which covers Montana and Wyoming, but Idaho falls under Region 10, and Wyoming Highway Patrol working on Montana roads needs state-to-state mutual aid, so the structure must resolve that early.

Strategic Connections:

Synergy: Provides the authority base for Escalation Trigger and Evacuation Release Doctrine and Exclusion Perimeter Posture and Re-Entry Access Control, since clear command lets zone expansions and perimeter enforcement be ordered without jurisdictional dispute.

Conflict: A rigid boundary handoff clashes with Egress Corridor Allocation and Contraflow Architecture, since moving traffic crosses the line mid-corridor; shared command can slow the decisions Escalation Trigger and Evacuation Release Doctrine tries to speed up.

Justification: Critical, Foundational authority base for zone expansion, perimeter enforcement and corridor operations. It resolves NPS-to-state handoff, Denver RRCC Region 8/10 gaps and mutual aid, and directly conflicts with moving traffic and fast trigger decisions.

Decision 4: Communications Continuity Stack Under Ash and Tremor

Lever ID: 14959fd9-8062-4934-9362-569f3e381a10

The Core Decision: Establishes the layered channels that carry alerts, route instructions and responder coordination when cell towers fail: IPAWS, radio, satellite, signs and printed materials. Success metrics include the share of drivers reached with consistent instructions, responder interoperability across NPS, state and Guard nets, and recovery time for degraded links under ashfall and tremor.

Why It Matters: Determines how warnings and commands reach drivers, responders and shelters once cell towers fail. IPAWS reaches phones and broadcasters only while those networks stay up, so radio and satellite layers carry the load; each added layer needs equipment, trained operators and frequency coordination before the event.

Strategic Choices:

  1. Rely on IPAWS, Wireless Emergency Alerts and NOAA Weather Radio as the primary public channel, with National Guard signal units bridging responder radios between agencies at the gateway towns.
  2. Deploy portable repeaters and satellite terminals at every contraflow control point and shelter, and broadcast route instructions over highway advisory radio and variable message signs along US-191 and I-90.
  3. Hand out pre-programmed battery radios and printed route cards at park entrances and visitor centers, so visitors can still follow instructions after the digital network has collapsed.

Trade-Off / Risk: Ash degrades radio propagation and clogs equipment, and a warning that arrives after a driver has committed to the wrong route is worse than none, so message discipline matters as much as redundant hardware.

Strategic Connections:

Synergy: Amplifies International Visitor, Language, and Access-Needs Notification Pathways by supplying the channels for multilingual alerts, and Shadow Evacuation Suppression and Public Compliance Dynamics by enabling consistent, credible messages that reduce uncontrolled departures.

Conflict: Heavy hardware layers compete with Ashfall Life-Support Supply and Priority Allocation for transport and generator fuel, and with Responder Exposure Limits and Relief Rotation Regime because more equipment needs trained operators in ash-exposed locations.

Justification: High, Enabling layer that delivers route assignments, multilingual alerts and consistent messaging, linking egress, compliance and notification levers. Competes with life-support supply and responder staffing for fuel and operators, so a major trade-off.

Decision 5: Refugee Intake and Shelter Siting Strategy

Lever ID: 57ab47b3-f2b2-42be-b584-9312a07de587

The Core Decision: Chooses where evacuees are received, registered and sheltered, and whether sites are destinations or transit hubs given uncertain wind and plume direction. Success metrics are intake capacity per hour, share of evacuees outside the modeled ash footprint, reunification time, and readiness of second-stage transport if Scenario Beta occurs.

Why It Matters: Decides where evacuees are received and whether reception sites are final destinations or transit hubs. Fixed sites at Bozeman and Idaho Falls are known and can be stocked, but both could fall in an ash plume depending on wind, and ashfall would trap people there; wind-adaptive siting protects them but complicates prior stocking and public messaging.

Strategic Choices:

  1. Operate Bozeman and Idaho Falls as fixed reception centers, each with medical triage, registration and family reunification, and stock them ahead of the first arrivals.
  2. Treat Bozeman and Idaho Falls as short-stay processing points and move evacuees onward by bus and rail to distant hubs such as Billings, Boise or Salt Lake City outside the modeled ash footprint.
  3. Select final shelter locations at T+6 hours from the forecast wind and plume model, keeping a ranked list of pre-surveyed schools and arenas on every side of the park.

Trade-Off / Risk: Idaho Falls and Bozeman sit near the Zone One boundary, so treating them as safe is an assumption that Scenario Beta would break; any plan that keeps evacuees there needs a second-stage move ready.

Strategic Connections:

Synergy: Works with Hospital Surge Dispersal and Respiratory Patient Routing to colocate triage and route respiratory cases, and with Ashfall Life-Support Supply and Priority Allocation by concentrating water and N95 stocks at known intake sites.

Conflict: Wind-adaptive or onward-move siting conflicts with Ashfall Life-Support Supply and Priority Allocation, which prefers prestocked fixed sites, and strains Escalation Trigger and Evacuation Release Doctrine, whose 500 km radius exceeds any shelter capacity.

Justification: High, Determines where evacuees end up and whether sites survive an ash plume or Scenario Beta. Connects hospital routing, supply stocking and escalation triggers, with a fixed-versus-adaptive siting trade-off.

Secondary Decisions

These decisions are less significant, but still worth considering.

Decision 6: Ashfall Life-Support Supply and Priority Allocation

Lever ID: 3fc1002b-3f87-4cda-bfe8-3b180e0e3945

The Core Decision: Defines the sourcing, staging and tiered rationing of water, respirators and generator fuel so critical facilities stay functional through ashfall. Success metrics include hours-to-delivery at hospitals and shelters, tier-one fuel days of supply, respirator replacement cycles beyond the initial 100,000 (user constraint), and the share of open reservoirs isolated before ash arrives.

Why It Matters: Controls how water, N95 respirators and generator fuel reach hospitals, shelters and communications centers while roads are congested or ash-covered. Pulling stock from Salt Lake City works only while the I-15 and US-20 routes stay open; forward staging shortens delivery time but ties up supplies inside areas that may be lost.

Strategic Choices:

  1. Dispatch bottled-water, respirator and fuel convoys from Salt Lake City distribution centers on a fixed schedule, using National Guard escorts and reserved lanes alongside the evacuation.
  2. Pre-position water, respirators and fuel tankers at forward depots in Bozeman, Billings and Idaho Falls before the eruption window, accepting that some stock may be stranded if the plume shifts.
  3. Rank facilities into priority tiers, giving fuel and water first to hospitals, communications centers and shelter kitchens, and have utilities and water districts isolate open reservoirs ahead of ashfall.

Trade-Off / Risk: A 100,000-respirator requirement (user constraint) is small compared with the population a VEI-6 plume could affect, and N95 masks clog quickly in heavy ash, so quantities and replacement cycles need explicit planning.

Strategic Connections:

Synergy: Amplifies Hospital Surge Dispersal and Respiratory Patient Routing by keeping receiving hospitals fueled and supplied, and strengthens Communications Continuity Stack Under Ash and Tremor by guaranteeing generator fuel to comms centers.

Conflict: Competes with Egress Corridor Allocation and Contraflow Architecture for road capacity, since inbound convoys need lanes during outbound evacuation; forward depots also compete with Refugee Intake and Shelter Siting Strategy for warehouse and site space.

Justification: High, Sustains hospitals, shelters and comms centers through ashfall via water, respirators and fuel. It is a hub supporting hospital routing and communications, but competes with evacuation traffic for road capacity.

Decision 7: Visitor Headcount Reconciliation and Backcountry Sweep Protocol

Lever ID: a69bd951-1e7e-4b32-8e39-b35abc2acba6

The Core Decision: Establishes the method for estimating who remains inside Zone Zero and certifying sectors as cleared. It combines gate, lodging and permit data with physical sweeps of trailheads and thermal basins. Success is measured by the gap between estimated and confirmed occupants, sector-clearance time, and the number of missing-person reports resolved before the clearance declaration.

Why It Matters: Determines how the response knows who is still inside the park and when Zone Zero can be declared clear. A rigorous accountability method slows the final evacuation hours and ties up rangers, while a loose one risks leaving backcountry hikers, campers and concession staff unaccounted for when the eruption escalates.

Strategic Choices:

  1. Run a gate-and-lodging manifest reconciliation that compares entrance counts, lodge registers and campground permits against checkpoint exit counts to produce a running estimate of remaining occupants.
  2. Deploy ranger-led sweep teams with helicopter support along trailheads, backcountry permit sites and thermal basins, clearing them sector by sector and marking cleared areas on a shared common operating picture.
  3. Issue every exiting vehicle a dated windshield tag and collect phone-based check-ins at the exit checkpoints, so that reunification data and exit counts are produced together and missing-person reports can be matched directly.

Trade-Off / Risk: Accountability data drawn from permits and gate counts is only as good as the walk-in, day-use and staff population it can see; the sweep effort competes directly with evacuation traffic control for the same ranger hours.

Strategic Connections:

Synergy: Feeds Escalation Trigger and Evacuation Release Doctrine with a defensible clearance status, and supports Command Structure and Jurisdictional Handoff Model by providing a shared common operating picture at the boundary transfer.

Conflict: Draws on the same ranger hours as Egress Corridor Allocation and Contraflow Architecture, and prolonged sweeps conflict with Responder Exposure Limits and Relief Rotation Regime by keeping teams in the hazard zone as eruption odds climb.

Justification: Medium, Governs clearance certification and the last-person-out risk, competing for ranger hours with egress. Valuable but operational; its trade-offs sit mostly within the egress and exposure levers.

Decision 8: Shadow Evacuation Suppression and Public Compliance Dynamics

Lever ID: e930bb1a-302c-4f76-b378-fe305c262ac2

The Core Decision: Manages the behavior of unordered residents in Bozeman, Billings, Idaho Falls and similar outer communities so spontaneous flight does not saturate evacuation corridors, fuel supplies and lodging. Success is judged by measured corridor throughput, the share of outer-zone residents following shelter or time-band instructions, and the stability of public trust in official messaging.

Why It Matters: Shapes how people outside the ordered zones behave, because large numbers of unordered residents in Bozeman, Billings and Idaho Falls are likely to flee on their own and fill the same routes. Discouraging them protects corridor capacity but may erode trust, while tolerating them raises the load on fuel, lodging and roads.

Strategic Choices:

  1. Issue geographically targeted IPAWS messages that tell outer-zone residents to shelter in place, supported by local officials who repeat the same instruction on trusted radio channels.
  2. Stage outer-zone residents with a scheduled, time-banded departure plan that assigns each community a release window, spreading the load on the corridors instead of forbidding departure.
  3. Open a visible voluntary-departure route on secondary roads such as state highways away from the main contraflow corridors, deliberately channeling shadow evacuees away from the primary evacuation routes.

Trade-Off / Risk: Shelter-in-place messaging works only if residents believe the modeled ash risk is low; time-banded departures need disciplined enforcement, and secondary routes may lack the shoulders and fuel stops to handle the surge.

Strategic Connections:

Synergy: Protects Egress Corridor Allocation and Contraflow Architecture by keeping the corridors usable for ordered evacuees, and relies on International Visitor, Language, and Access-Needs Notification Pathways to deliver consistent instructions to all audiences.

Conflict: Tension with Escalation Trigger and Evacuation Release Doctrine: shelter-in-place messaging can lose credibility if the zone later expands to 500km, and it may strain Refugee Intake and Shelter Siting Strategy if compliance collapses.

Justification: Medium, Protects corridor capacity from unordered flight and is tied to messaging credibility and escalation. Important for optimization, but largely depends on the communications and trigger levers rather than setting core strategy.

Decision 9: Hospital Surge Dispersal and Respiratory Patient Routing

Lever ID: 977c56ab-38a5-4aa2-8b2c-5b99bef4edc1

The Core Decision: Allocates mass respiratory, trauma and chronic-care patients across the regional hospital network and field sites so that no facility fails under load. It covers receiving-hospital designation, tracking, early transfers of fragile patients and on-site treatment. Success is measured by bed occupancy balance, transport times, ambulance availability and avoidance of preventable respiratory deaths.

Why It Matters: Decides where mass respiratory distress, trauma and chronic-disease patients are sent so that no single facility is overwhelmed. Distributing patients widely protects the closest hospitals, but extends transport times and strains ambulance supply, and ash may restrict the very ground routes that dispersal relies upon.

Strategic Choices:

  1. Designate a primary receiving hospital per corridor and use a central patient-tracking desk at the RRCC to direct ambulance traffic, keeping loads balanced across facilities in real time.
  2. Pre-position field treatment tents and rotating clinician teams at the shelter sites so that mild and moderate respiratory cases are managed on site, reserving hospital beds for the severe cases.
  3. Arrange early transfer of hospitalized and dialysis-dependent patients out of Zone One facilities before ashfall to hospitals in Salt Lake City and Billings, using ground ambulances and military airlift windows.

Trade-Off / Risk: Pre-emptive patient transfers free beds but expose fragile patients to long transport during chaos; field treatment sites depend on clinician availability that the same regional hospitals will be competing to retain.

Strategic Connections:

Synergy: Works with Refugee Intake and Shelter Siting Strategy, since treatment tents at shelters offload hospitals, and depends on Ashfall Life-Support Supply and Priority Allocation to keep receiving facilities supplied with fuel, water and respirators.

Conflict: Patient transport competes with Egress Corridor Allocation and Contraflow Architecture for road space and ambulances, and field clinician teams compete with Responder Exposure Limits and Relief Rotation Regime for scarce medical staff and rest cycles.

Justification: Medium, Handles the downstream medical load and depends on supply and shelter siting upstream. Meaningful for outcomes, but it is a consumer of other levers' decisions rather than a hub shaping them.

Decision 10: Exclusion Perimeter Posture and Re-Entry Access Control

Lever ID: 531c990c-0693-4b04-aa06-db58fde56eba

The Core Decision: Sets how tightly the evacuated area is sealed and who may enter, balancing anti-looting protection and responder safety against personnel demands and public resistance. It covers checkpoint design, credentialing, patrol methods and any escorted-return windows. Success includes zero unauthorized entries into the hazard area, looting incidents, personnel hours consumed, and avoidance of exposure-related casualties during returns.

Why It Matters: Sets how strictly the evacuated zone is sealed, who is allowed back inside, and how looting is deterred across empty towns. A hard perimeter reduces theft and protects returning responders, but diverts National Guard personnel from logistics and may provoke confrontations with residents seeking to retrieve family, pets or livestock.

Strategic Choices:

  1. Hold a fixed checkpoint perimeter on all roads out of the zone, admitting only credentialed responders, utility crews and critical-infrastructure staff against a published access list.
  2. Run roving mobile patrols and drone surveillance of evacuated communities instead of static checkpoints, keeping a smaller footprint and concentrating Guard personnel on logistics and shelter security.
  3. Create a supervised escorted-return program in which residents receive short, scheduled access windows with a responder escort to collect medications, documents and animals while ash conditions allow.

Trade-Off / Risk: Escorted-return programs reduce public resistance but expose both residents and escorts to unforecast ashfall and renewed eruption risk; static checkpoints are simpler to defend yet absorb personnel the response may need elsewhere.

Strategic Connections:

Synergy: Reinforces Command Structure and Jurisdictional Handoff Model by giving state and federal authorities a clear, enforceable boundary, and supports Visitor Headcount Reconciliation and Backcountry Sweep Protocol by controlling re-entry into cleared sectors.

Conflict: Static checkpoints draw National Guard personnel away from Ashfall Life-Support Supply and Priority Allocation convoy escorts, and escorted returns conflict with Responder Exposure Limits and Relief Rotation Regime by adding exposed escort hours.

Justification: Medium, Balances anti-looting enforcement against Guard availability for logistics. Matters after the life-safety phases and mainly reinforces command clarity; it is not a driver of the core evacuation outcome.

Decision 11: Ash-Cloud Airspace Closure Scope and Humanitarian Flight Exceptions

Lever ID: 36521150-e40b-4032-84ae-23a417727bca

The Core Decision: Sets the geographic and temporal rigidity of the ZLC/ZSE ash grounding and the criteria for any exceptions. Success is measured by zero aircraft ash encounters, time-to-clearance for medevac or survey sorties, and clarity of authority between FAA and Unified Command. Defines whether helicopters and cargo flights from unaffected airfields supplement ground logistics when roads saturate.

Why It Matters: Defines how wide and how rigid the ZLC and ZSE grounding is, and whether any controlled flights are allowed inside it. A blanket closure removes ash-ingestion risk but also removes air evacuation, medevac, and reconnaissance options. Exceptions restore some capability but raise the chance of an engine encounter and complicate FAA and military coordination.

Strategic Choices:

  1. Impose a blanket indefinite grounding across ZLC and ZSE with no exceptions, relying entirely on ground transport for evacuation, medevac, and supply.
  2. Maintain the blanket grounding but pre-authorize a narrow set of ash-model-cleared rotary-wing medevac and survey flights below defined ash-concentration limits, approved by the Unified Command.
  3. Establish a dynamic airspace tiering system, driven by hourly ash-dispersion forecasts, that opens and closes corridors for cargo and evacuation flights from airfields outside the plume, such as those in the southern ZLC area.

Trade-Off / Risk: A total ban is simple to enforce but strands medevac and surveillance capability, while rolling exceptions depend on ash-concentration forecasts whose reliability during an unprecedented event is unproven, risking aircraft and crews.

Strategic Connections:

Synergy: Exceptions strengthen Hospital Surge Dispersal and Respiratory Patient Routing through rotary-wing medevac, and give Landslide Clearance and Hydrothermal Hazard Road Engineering aerial survey data to certify bypasses and abort triggers.

Conflict: Flight exceptions expose crews to ash and compete for forecast and coordination capacity with Command Structure and Jurisdictional Handoff Model; a blanket ban instead pushes all load onto Egress Corridor Allocation and Contraflow Architecture.

Justification: Medium, The grounding itself is a fixed requirement; the exception scope marginally adds medevac and survey capability. Its relief on ground corridors is secondary and depends on unproven ash forecasts.

Decision 12: Landslide Clearance and Hydrothermal Hazard Road Engineering

Lever ID: 07d0a2da-0240-4130-80d3-197fd7d4666f

The Core Decision: Allocates scarce heavy-equipment and geotechnical capacity between reopening the South Entrance, repairing the Grand Loop Road, or protecting the northern and western routes. Success is measured by added outbound capacity gained per crew-hour, zero crew casualties from secondary slides or steam explosions, and debris-free US-191, US-20 and US-89 throughout Phase 1.

Why It Matters: Decides whether engineering effort goes into reopening the landslide-blocked South Entrance road, repairing the explosion-damaged Grand Loop Road, or writing them off. Reopening adds an outbound route and relieves the north and west corridors, but exposes equipment crews to secondary slides and further steam explosions. Writing the routes off concentrates all traffic on fewer roads that are already near capacity.

Strategic Choices:

  1. Write off the South Entrance and damaged Grand Loop sections, directing all engineering resources to keeping the northern and western routes passable and free of debris.
  2. Deploy pre-positioned heavy equipment from Wyoming and Idaho transportation departments to attempt a time-boxed single-lane clearance of the South Entrance slide, with hard abort triggers tied to seismic readings.
  3. Use drones and ground-penetrating geotechnical scouting to certify a few short bypass or temporary-track segments around the slide and damage, reserved for emergency vehicles and outbound overflow only.

Trade-Off / Risk: Reopening a southern route could relieve pressure on the corridors, but crews working on unstable ground during an active swarm may become casualties themselves, and the time spent could be better applied to keeping the open routes clear.

Strategic Connections:

Synergy: A certified southern or bypass route adds capacity that Egress Corridor Allocation and Contraflow Architecture can use, and supports Visitor Headcount Reconciliation and Backcountry Sweep Protocol by opening access to southern park areas.

Conflict: Crews on unstable ground consume equipment and operators that Responder Exposure Limits and Relief Rotation Regime seeks to protect, and effort spent on the south competes with keeping the northern and western routes clear.

Justification: Medium, Can add outbound capacity or keep the northern and western routes clear, but benefits are uncertain and exposure risk is high. It serves the egress lever rather than defining the strategy.

Decision 13: Responder Exposure Limits and Relief Rotation Regime

Lever ID: 305647d0-e94d-41f5-9822-c932a96c85a6

The Core Decision: Governs the sustainable endurance of the response workforce by setting shift lengths, withdrawal thresholds and relief cycles for rangers, highway patrol, National Guard and utility crews. Success is measured by responder illness and entrapment rates, staffing continuity at traffic points and gates, and an explicit count of respirators and relief personnel reserved for responders rather than civilians.

Why It Matters: Sets how long rangers, highway patrol, National Guard, and utility crews may work in ash, gas, and tremor conditions before mandatory withdrawal. Strict limits protect the response workforce from respiratory injury and entrapment, but reduce the number of people on traffic points and perimeters at the peak of the evacuation. Loose limits maximize short-term coverage but risk degrading the force just as ashfall intensifies.

Strategic Choices:

  1. Apply fixed, conservative exposure and shift-length limits to all responders from the first hour, accepting thinner coverage at traffic control points and re-entry gates.
  2. Use real-time ash and gas monitoring at each post, with responders rotating or withdrawing only when sensor readings cross agency-set thresholds, so limits flex with actual conditions.
  3. Tier responders by mission criticality, giving evacuation traffic control and hospital power crews fuller protective equipment and priority relief, while lower-priority posts are withdrawn early to preserve the force.

Trade-Off / Risk: Protective limits assume enough relief personnel and respirators exist, but the plan pre-stages protection mainly for 100,000 civilians, so responder rotation may be limited by equipment and staffing that has not been counted.

Strategic Connections:

Synergy: Sustained, protected staffing keeps Exclusion Perimeter Posture and Re-Entry Access Control and Egress Corridor Allocation and Contraflow Architecture manned through peak ashfall, and supports Communications Continuity Stack Under Ash and Tremor maintenance crews.

Conflict: Strict limits thin coverage at contraflow points and perimeters at the evacuation peak, trading against Egress Corridor Allocation and Contraflow Architecture and Visitor Headcount Reconciliation and Backcountry Sweep Protocol, which need maximum personnel hours early.

Justification: High, Constrains the workforce that staffs traffic points, perimeters, sweeps and comms. Conflicts with many levers over personnel hours, controlling the coverage versus responder-safety trade-off at peak evacuation.

Decision 14: International Visitor, Language, and Access-Needs Notification Pathways

Lever ID: f13fe63b-ce28-4fd2-b0dc-ddb19ca9b9c7

The Core Decision: Ensures evacuation orders and transport reach visitors that general broadcasts miss: non-English speakers, foreign nationals, people with mobility or medical needs, and those without vehicles. Success is measured by the share of at-risk visitors confirmed out of the park by T+6 hours, translation coverage of key languages, and the accuracy of needs estimates drawn from concessioner and reservation data.

Why It Matters: Shapes how evacuation orders reach non-English speakers, foreign nationals, people with mobility or medical needs, and visitors without vehicles who make up part of the 35,000 tourists. Targeted pathways reduce the chance that the least mobile or least informed people become the last to leave. They require consular, concession-operator, and translation resources that general IPAWS broadcasts do not provide.

Strategic Choices:

  1. Rely on IPAWS and standard ranger announcements in English with basic multilingual signage, and assume visitors will follow traffic and crowd cues.
  2. Activate concessioner and tour-operator networks, plus consular liaisons, to carry multilingual instructions and organize transport for visitors without vehicles or with access needs.
  3. Create dedicated assisted-evacuation pickup points inside the park, staffed by rangers and volunteer interpreters, with shuttle buses sequenced ahead of general traffic to remove high-need visitors first.

Trade-Off / Risk: Assisted pickup protects the most vulnerable but takes buses and staff away from the general outflow during the critical first hours, and the plan has no visitor-needs data to size it.

Strategic Connections:

Synergy: Targeted notification feeds Visitor Headcount Reconciliation and Backcountry Sweep Protocol with who is unaccounted for, and reduces demand on Shadow Evacuation Suppression and Public Compliance Dynamics by cutting confusion-driven uncoordinated movement.

Conflict: Assisted pickup shuttles and staff compete with Egress Corridor Allocation and Contraflow Architecture for road space and buses, and draw ranger time away from Responder Exposure Limits and Relief Rotation Regime-constrained traffic posts.

Justification: Low, Largely a targeted extension of the communications stack and egress transport, serving a subset of visitors. Its needs data is thin, and its shuttle and staff demands are tactical trade-offs against egress.

Choosing our strategic path.

The Strategic Context

Understanding the core ambitions and constraints that guide our decision.

Ambition and Scale: Societal-scale, multi-state civil-protection operation: evacuation of about 35,000 visitors and 800 staff (user constraint) within T+6 hours, expansion to a 100 km Zone One with several gateway towns, and a contingency to 500 km. Involves NPS, FEMA Regions 8 and 10, Montana, Wyoming and Idaho, the National Guard and the FAA.

Risk and Novelty: Very high stakes with a hard 72-hour window and a stated 40% probability of a VEI-6+ eruption (user constraint). Few operational precedents exist for a Yellowstone-scale event. The main risks are single-point road chokepoints (landslide-blocked South Entrance, two-lane mountain corridors), ash-degraded communications and power, and a Scenario Beta that exceeds shelter and road capacity. The plan is about executing proven emergency-management methods (contraflow, IPAWS, Unified Command) under extreme time pressure, not about innovation.

Complexity and Constraints: High operational complexity: contraflow on US-191, US-20 and US-89 to I-90, cross-jurisdiction authority transfer, FEMA Region 8/10 and state mutual-aid seams, aviation grounding in ZLC and ZSE, comms failure planning, water convoys within 12 hours, N95 pre-staging for 100,000 people (user constraint) and grid-failure fuel priorities. Constraints are fixed: a UC in Denver, Bozeman and Idaho Falls shelters, an explicit NPS-to-governor handoff, and a trigger point for the 500 km expansion.

Domain and Tone: Government public-safety and emergency-management planning. Tone is operational, directive and specific (routes, agencies, hourly Gantt chart, risk register, resource matrix), with an emphasis on life preservation and continuity of operations.

Holistic Profile: A high-stakes, time-compressed, physically executed government evacuation plan. It needs reliable, pre-authorized decision rules, higher exit capacity, clear command and robust public alerting. It calls for a balanced, execution-credible posture with explicit escalation triggers, not an experimental or minimalist one.

The Path Forward

This scenario aligns best with the project's characteristics and goals.

The Pragmatic Foundation

Strategic Logic: Add the East Entrance gate to spread load across three exits, pre-authorize a written trigger matrix so the VEI-7 decision does not wait on meetings, and place a forward command element near the corridors while Denver handles federal resource requests. Shelter sites are chosen at T+6 hours from the actual wind and plume forecast, which balances preparedness against the cost of staging everything in advance.

Fit Score: 8/10

Why This Path Was Chosen: A pre-authorized trigger matrix directly answers the requirement for a Scenario Beta trigger point and an immediate 500 km expansion, and IPAWS plus National Guard signal bridging is the comms approach the plan names. A third exit adds capacity, and the forward command element complements Denver, though the boundary handoff and the East Entrance's role in the Cody evacuation need explicit definition.

Key Strategic Decisions:

The Decisive Factors:

Alternative Paths

The Pioneer's Gambit

Strategic Logic: Move early and move more people per vehicle: buses replace private-vehicle exit lanes, vulnerable groups leave the outer ring before any VEI-7 indicator appears, and evacuees are pushed onward to hubs outside the ash footprint. This accepts higher cost and coordination risk (bus availability, drivers, a joint command that must function from the first hour) in exchange for the most headroom if the eruption escalates to Scenario Beta.

Fit Score: 3/10

Assessment of this Path: Its bus-based lane suspension and quiet pre-emptive outer-ring evacuation need transport, drivers and a fully functioning joint command from hour one, which is not credible within a T+6 window for 35,000 people. It also gives the Denver RRCC and the explicit NPS-to-governor handoff little role. It offers the most Scenario Beta headroom but is the least executable and its comms layer is hardware-heavy.

Key Strategic Decisions:

The Consolidator's Anchor

Strategic Logic: Concentrate on what can be executed reliably within the 72-hour window: two contraflow corridors to I-90, a written handoff of authority at the park boundary, low-tech redundant communications and fixed, pre-stocked reception centers. Escalation to a 500 km order stays with a standing volcanologist-and-governor cell, which keeps human judgment and cost low but accepts delay and leaves Scenario Beta capacity as the main residual risk.

Fit Score: 6/10

Assessment of this Path: It is reliable and closely matches the named corridors, the explicit boundary handoff and the fixed Bozeman and Idaho Falls centers. However, a periodic decision cell delays a Scenario Beta order that the plan requires "immediately", and the two-corridor funnel and the lack of IPAWS and Guard comms bridging leave the main bottlenecks and ash-driven comms failures under-addressed.

Key Strategic Decisions:

Purpose

Purpose: business

Purpose Detailed: Multi-agency disaster response and civil-protection planning: mass evacuation of Yellowstone National Park and a 100km zone, traffic contraflow control, aviation grounding, refugee shelter intake, unified command and jurisdiction transfer among NPS, FEMA and state governors, communications continuity, water, medical and security logistics, and contingencies for supereruption escalation and grid failure. Delivered as an executive summary, hourly Gantt chart, risk register and resource allocation matrix. This is a government and public-safety initiative aimed at societal-scale life preservation and regional infrastructure continuity.

Topic: Strategic emergency response and evacuation plan for a Yellowstone Caldera "Red Warning" volcanic eruption (VEI-6+ Scenario Alpha, VEI-7 Scenario Beta)

Domain

Primary domain: Emergency Management

Secondary domains: Volcanology, Traffic Management, Mass Evacuation Planning

Rationale: Emergency Management owns the whole multi-agency response: unified command, jurisdiction transfer, shelter intake, logistics, and continuity of operations. Mass Evacuation Planning ties on score but covers only one phase. Volcanology, Traffic Management, and Public Health are subordinate.

Disciplines this project involves:

Domain Importance Specificity Role Reason
Emergency Management 5 5 outcome Owns mass evacuation, unified command, shelter intake, and continuity-of-operations planning for the disaster response.
Mass Evacuation Planning 5 5 outcome Core success criterion is evacuating 35,000 tourists and regional communities within hours.
Volcanology 4 5 constraint Eruption modeling, VEI escalation triggers, and ashfall forecasts drive evacuation zones and timing.
Traffic Management 4 4 method Contraflow operations on US-191, US-20, and US-89 are central to evacuating 35,000 people.
Emergency Logistics 4 4 method Water convoys, N95 pre-staging, generator fuel, and shelter intake require supply chain coordination.
Emergency Communications 4 4 method IPAWS alerts and signal corps bridging address cell tower failure under ashfall.
Public Health Preparedness 4 4 outcome Respiratory protection, mass casualty intake, and hospital surge for ashfall exposure.
Critical Infrastructure Resilience 4 4 method Ash-induced grid flashovers, water contamination, and continuity of regional infrastructure operations.
Aviation Safety 3 4 constraint Ash ingestion risk drives indefinite FAA grounding across ZLC and ZSE sectors.

Plan Type

This plan requires one or more physical locations. It cannot be executed digitally.

Explanation: The plan is a strategic emergency response and mass evacuation plan for a Yellowstone Caldera volcanic event, and it is inherently physical. It requires moving about 35,000 tourists and 800 park staff along real roads (US-191, US-20, US-89, I-90) using contraflow traffic control, deploying NPS rangers, highway patrol and National Guard personnel on the ground, and clearing a landslide-blocked South Entrance road. It also involves establishing physical shelters and refugee intake centers (Bozeman, Idaho Falls), staging bottled water convoys from Salt Lake City, pre-staging N95 respirators, supplying generator fuel to hospitals, deploying signal corps equipment for communications bridging, and enforcing an exclusion-zone perimeter. A unified command is set up at the FEMA RRCC in Denver. Aviation grounding, IPAWS alerts and the written deliverables (Gantt chart, risk register, resource matrix) are digital or administrative elements, but they support real-world, on-the-ground outcomes and cannot replace the physical operations. The plan cannot be completed exclusively online and benefits substantially from physical presence and location, so it is classified as physical.

Physical Locations

This plan implies one or more physical locations.

Requirements for physical locations

Location 1

USA, Wyoming/Montana/Idaho

Yellowstone National Park (Zone Zero) and gateway towns West Yellowstone, Gardiner and Cody (Zone One)

Norris Geyser Basin, Grand Loop Road, South Entrance (US-89/191/287), West Entrance (US-20/191), North Entrance (US-89), East Entrance (US-14/16/20)

Rationale: The evacuation of about 35,000 visitors and 800 staff (user constraint) takes place here, with the landslide-blocked South Entrance and contraflow on the named routes.

Location 2

USA, Colorado

Denver

FEMA Region VIII Regional Response Coordination Center, Denver Federal Center, Lakewood/Denver

Rationale: Named Unified Command site for federal resource requests. Region 10 (Idaho) coordination must be added to this site.

Location 3

USA, Montana

Bozeman or Livingston

Forward Unified Command element near I-90 at Livingston, or Bozeman (Gallatin County)

Rationale: Gives the incident commander direct sight of the US-89 and US-191 corridors and the I-90 junction, and a base for the Bozeman reception center. Both sites are near the Zone One edge, so a wind-driven relocation option is needed.

Location 4

USA, Idaho

Idaho Falls

Bonneville High School and pre-surveyed schools/arenas in Idaho Falls

Rationale: Named western reception center on the US-20 corridor. Final shelter selection should follow the T+6 wind and plume forecast, with a second-stage move planned.

Location 5

USA, Utah

Salt Lake City

Regional distribution centers and staging areas along I-15

Rationale: Source of bottled water convoys within 12 hours and of N95 and fuel stocks. Also a candidate receiving hub for patient transfers, outside the modeled ash footprint (not verified).

Location Summary

The plan is tied to Yellowstone National Park and its Zone One gateway towns (West Yellowstone, Gardiner, Cody). Command sits at the FEMA RRCC in Denver, with a proposed forward element at Bozeman or Livingston. Evacuees are received at Bozeman and Idaho Falls, and supplies are staged from Salt Lake City. Each listed site covers a defined function: evacuation, command, forward control, reception or logistics.

Currency Strategy

This plan involves money.

Currencies

Primary currency: USD

Currency strategy: All transactions use USD with no currency exchange or foreign exchange risk. Budgeting and reporting occur in USD across federal (FEMA Region VIII and X), state (Montana, Wyoming, Idaho) and local agencies. Cost tracking for evacuation logistics, fuel convoys, medical supplies, communications equipment, generator fuel, shelter operations and personnel reimbursement is conducted in USD through standard US government accounting and reimbursement procedures.

Identify Risks

Risk 1 - Operational / Traffic & Egress

Single-point failure on US-191/US-20 Gallatin Canyon corridor during peak contraflow evacuation. The canyon is a narrow, two-lane mountain pass with minimal shoulders, no recovery space, and documented rockfall hazard. A breakdown, rockslide, or secondary tremor-induced slide could block the entire northbound contraflow lane(s) and strand queued traffic. The South Entrance is already landslide-blocked, so this corridor is the primary egress for central park visitors. Rescue and debris-clearance crews cannot quickly reach a mid-canyon incident during ashfall and seismic swarm.

Impact: Complete blockage of the primary outbound corridor for 30 minutes to several hours, trapping 500–2,000 vehicles in the canyon and preventing the Phase 1 evacuation of ~5,000–8,000 visitors from reaching safe zones by T+6 hours. Each hour of delay increases the overlap between the evacuation peak and ashfall onset, raising respiratory injury and vehicle-accident rates. Secondary estimate: delay of 2–4 hours in clearing the blockage and resuming traffic flow.

Likelihood: High

Severity: High

Action: Pre-position a mobile tow and rockfall-clearing team (1–2 heavy wreckers, debris chippers, spotters) at Mammoth or Spanish Creek, with fuel and 72-hour supplies, tasked to reach any Gallatin Canyon blockage within 15 minutes. Establish a live geotechnical monitoring net along the canyon with motion sensors or drones at identified slide-prone zones to detect incipient movement and trigger temporary traffic halts before collapse. Identify and mark a short bypass track or one-lane re-route 48 hours before the evacuation window, and establish a hard decision rule: if the blockage persists beyond 45 minutes, begin diverting overflow to the US-89 Gardiner corridor or US-14/16/20 Cody corridor (adding 2–4 hours to transit time for some evacuees).

Risk 2 - Technical / Communications

Catastrophic failure of cell-tower network under ashfall and tremor, leaving IPAWS, WEA and standard radio links non-functional or severely degraded. The plan relies on IPAWS and Wireless Emergency Alerts as the primary public channel and assumes National Guard signal bridging can restore responder radios between agencies at gateway towns. However, ash-induced flashovers on transmission lines, tremor damage to cell towers, and silicate-ash clogging of air filters on repeater fans could collapse the local network faster than signal units can deploy or before key messages reach departing drivers.

Impact: Loss of real-time route guidance, traffic-status updates, and shelter-assignment messages to drivers in vehicles for 1–6 hours. Drivers revert to visual traffic cues, rumor and cellular networks they try repeatedly, leading to missed turns, congestion at wrong exits, and uncontrolled shadow evacuation to un-assigned shelters. Regional hospitals and emergency operations centers lose two-way coordination with ambulances and field teams for 30 minutes to 2 hours, delaying patient transfers. Estimated impact: 10–20% of drivers take unintended routes, adding 1–3 hours to some transit times; 5–10% of ambulance-patient transports face routing delays or miss handoff coordination.

Likelihood: High

Severity: High

Action: Deploy National Guard signal corps teams with satellite phones, portable repeaters and generator fuel to each contraflow control point and the forward command element (Bozeman/Livingston) at T-12 hours, before ash arrival. Pre-stage printed route cards and windshield placards at all park entrance stations and in visitor lodges, with simple instructions (e.g., 'North Exit: Follow US-89 to Gardiner, then I-90 to Livingston') and shelter addresses and phone numbers. Establish a low-tech broadcast fallback: activate all available highway advisory radio (HAR) stations and variable message signs (VMS) along US-191, US-20, US-89 and I-90 with pre-recorded messages in English and key visitor languages, updated hourly from the forward command. Test satellite and portable-repeater systems in ash-simulation exercises 30 days before the eruption window.

Risk 3 - Operational / Command & Authority

Authority gaps and delays at the NPS-to-state boundary handoff during the evacuation peak. The plan specifies transfer of authority from NPS (federal land) to state governors at the park boundary, but contraflow traffic does not stop at the line: drivers cross from NPS rangers' jurisdiction to state highway patrol control while still in congested queues mid-route. The boundary transfer of care (shelter placement, medical routing, security perimeter) is not clearly linked to the road crossing, creating a window where no single authority owns decisions. Additionally, Idaho (Region 10) and Montana/Wyoming (Region 8) fall under different FEMA regions, and the plan names only the Denver RRCC (Region 8), leaving Region 10 mutual aid unclear.

Impact: A 15–45 minute delay in ordering traffic reroutes, issuing revised shelter assignments, or escalating unplanned congestion because the boundary coordinator and the state on-scene commanders are not collocated and must reach agreement. One instance of delayed reroute could cascade into a backup affecting 500–1,000 vehicles. Jurisdictional confusion over perimeter enforcement (federal NPS rangers versus state National Guard) delays anti-looting operations and re-entry control in evacuated towns by 30 minutes to 2 hours. Region 10 mutual aid requests to Idaho resource centers go unrecognized at the Denver RRCC initially, delaying water and fuel convoys from Boise or Idaho Falls by 1–2 hours.

Likelihood: Medium

Severity: High

Action: Establish a dedicated Boundary Coordination Officer role, co-located at the forward command element (Bozeman or Livingston), with real-time voice and data links to the NPS on-scene incident commander and the designated state highway patrol and National Guard commanders on both sides of the boundary. Issue a written protocol specifying that the boundary officer controls traffic reroutes and initial shelter assignments during the crossing, and that NPS care ends at a specific roadside checkpoint where state custody begins. Pre-authorize the state on-scene commanders to issue temporary reroutes without requesting park ranger approval. Add an explicit call to FEMA Region 10 (Seattle) at T+0 hours from the Denver RRCC with a standing liaison and pre-agreed mutual aid arrangements (e.g., Boise and Pocatello fuel and water resources), documented in a signed MOU 60 days before the window.

Risk 4 - Operational / Escalation & Scenario Beta

Pre-authorized escalation trigger to Scenario Beta (500 km radius evacuation) lacks a defined secondary-stage plan, shelters or road capacity. The plan specifies that a VEI-7 order will be issued 'immediately' by the Unified Command under a written threshold-based trigger matrix, expanding evacuation from Zone One (100 km) to 500 km. However, no second-stage shelter destinations, host-community acceptance, bus and ambulance routing, or supply convoys for millions of additional evacuees are described. The original Bozeman and Idaho Falls shelters (described as 'short-stay processing points' or 'fixed reception centers') would be overwhelmed; the plan does not specify whether existing shelter stock (100,000 N95 masks, bottled water from Salt Lake City) would be stretched or restocked.

Impact: Once a Scenario Beta trigger fires (e.g., uplift >30 cm/hour, VEI-7 model probability >60%, new tremor swarm M>5.0), evacuees and residents in the 100–500 km ring (tens of thousands to low hundreds of thousands of people) have no clear destination or reception plan. This vacuum leads to uncontrolled, chaotic shadow evacuation on all routes leading away from Yellowstone, saturating interstates (I-15, I-80, I-90) and local roads with private vehicles, blocking the organized evacuation of Zone One tourists and park staff, and stranding residents outside pre-planned shelters. Estimated impact: 50,000–500,000 unplanned evacuees on roads within 6–12 hours, creating gridlock that delays Zone One evacuation by 4–8 hours and medical response by 2–6 hours.

Likelihood: High

Severity: High

Action: Develop and pre-authorize a written Scenario Beta Secondary-Stage Evacuation Plan, including: (1) a ranked list of 5–10 secondary shelter hubs (e.g., Salt Lake City metro, Billings, Boise, Cheyenne, Denver) with estimated capacity, host-community coordination, and pre-signed MOUs; (2) a tiered public messaging strategy that differentiates between shelter-in-place zones (250–500 km radius, with self-supplied residents), time-banded evacuation zones (100–250 km, with shelters pre-assigned by county), and organized evacuation (Zone One, same as current plan); (3) pre-deployed bus fleets and rail corridors linking secondary shelters so evacuees are moved out of congested I-90 and onto lateral routes; (4) a supply-estimation model that accounts for 100,000–500,000 additional people and pre-positions food, water, and medical supplies at secondary hubs before the eruption window. Brief this plan to FEMA Region 10, state governors of Idaho, Montana, Wyoming, and Colorado, and the National Guard Joint Task Force at Fort Carson 60 days before T+0. Test a Scenario Beta messaging and routing exercise 30 days before T+0, involving dispatch of sample secondary-hub bus fleets and shelter registration systems.

Risk 5 - Supply Chain / Life Support & Logistics

Water convoy from Salt Lake City cannot guarantee 'within 12 hours' delivery under ashfall and congested evacuation traffic. The plan states that bottled water convoys will be 'mobilized within 12 hours,' but the I-15 northbound route from Salt Lake to the shelters at Bozeman and Idaho Falls is the same corridor that out-of-state evacuees are likely to use if Scenario Beta triggers. Additionally, ashfall will degrade road surfaces, reduce visibility, increase accident rates, and slow all traffic. The 12-hour delivery window assumes roads stay clear and convoys can navigate around evacuation traffic; a realistic estimate is 18–30 hours if ashfall is heavy or evacuation-related blockages occur.

Impact: If water convoys arrive at Bozeman and Idaho Falls 18–24 hours after the first evacuees (many arriving by T+8 hours), the shelters must sustain 10,000–20,000 people for 1–2 days on existing, likely inadequate supplies. Ashfall will also contaminate open water supplies and require bottled water for all drinking, cooking and medical use. A shortage of 50,000–100,000 liters could affect medical care, respiratory treatment (which consumes water for steam inhalation and cooling), and public health sanitation. Estimated impact: 10–20% of evacuees remain without adequate water for 12–24 hours, increasing risk of heat stress, medication non-compliance, and secondary health incidents.

Likelihood: High

Severity: Medium

Action: Pre-stage bottled water, N95 respirators, and generator fuel at forward depots in Bozeman, Billings and Idaho Falls at T-48 hours, with a minimum of 10 days' supply for the planned shelter capacity (assume 15,000 people at Bozeman, 10,000 at Idaho Falls, plus field treatment sites). Establish a dedicated 'supply-surge' lane on I-15 northbound, reserved exclusively for water and fuel convoys during hours T+0 to T+24, enforced by National Guard escorts and traffic control. Pre-authorize the forward command to halt non-essential evacuation traffic on I-15 for up to 30 minutes to allow a high-priority water convoy to pass if the main route becomes gridlocked. Coordinate with Utah and Wyoming departments of transportation and water authorities to identify additional water sources (municipal tanks, bottling plants) within 200 miles of the shelters and pre-arrange 24-hour access and trucking. Test a water-convoy exercise from Salt Lake City to Bozeman under simulated ashfall and congested-traffic conditions 30 days before T+0, measuring actual travel time and identifying chokepoints.

Risk 6 - Technical / Medical & Hospital Systems

Hospital and medical-facility power grid failure due to ash-induced transmission-line flashovers could occur faster than generator fuel reaches critical facilities. The plan identifies grid failure as a contingency and directs fuel prioritization to hospitals and communications centers, but does not specify fuel pre-positioning, delivery schedule, or the number of hospitals that will lose power simultaneously. Regional hospitals in Montana and Wyoming are typical 100–500-bed facilities with 24–48-hour on-site generator fuel reserves. An ashfall event could trigger widespread, simultaneous power loss across the region within 4–8 hours, and fuel convoys from distant depots (e.g., Rock Springs, WY) would require 6–12 hours to reach all facilities.

Impact: If a major hospital loses power for 4–6 hours before fuel arrives, backup generators may fail to start (routine maintenance oversight), fuel-transfer equipment may jam with ash particles, or the facility may have only one fueling port, creating a bottleneck. Loss of power would affect surgical suites, HVAC systems, negative-pressure isolation rooms for respiratory patients, and refrigeration for biologics. A 4-hour outage could force cancellation of 10–20 surgeries, loss of 1–2 hours' worth of ventilator support if manual bagging fails, and potential patient deaths. Estimated impact: 5–15 preventable hospital patient deaths and 50–100 surgeries cancelled or delayed.

Likelihood: Medium

Severity: High

Action: Pre-position 72-hour fuel reserves (diesel, propane) at the three largest receiving hospitals (Bozeman Deaconess Medical Center, Livingston HealthCare, Eastern Idaho Regional Medical Center in Idaho Falls) at T-48 hours. Establish fuel-delivery contracts with local vendors (e.g., Yellowstone Energy, Basin Fuel) that include priority dispatch during the event and require arrival at hospital sites within 2 hours of a fuel request. Conduct a hospital-power-failure exercise with each facility 30 days before T+0, testing manual generator startup, fuel-transfer protocols and backup surgical protocols under ash-simulation conditions. Coordinate with the FAA and military to pre-authorize helicopter fuel deliveries to hospital helipads if ground routes are blocked, with fuel cached at forward airfield staging areas (e.g., Gallatin County Airport near Bozeman) at T-24 hours.

Risk 7 - Operational / Visitor Accountability & Backcountry Hazard

Backcountry hikers, campers and thermal-basin researchers cannot be reliably located or evacuated within the T+6 hour window. The plan lists a 'Visitor Headcount Reconciliation and Backcountry Sweep Protocol' but does not specify the number of backcountry permits issued, the typical dispersal of permit holders, or how many ranger-hours and helicopter sorties are required to sweep all thermal basins, trailheads and camps within 6 hours. Yellowstone issues ~500–1,000 backcountry permits daily during peak season; locating and evacuating 300–500 scattered backcountry parties across ~3,500 square miles of park requires coordination with multiple ranger districts, helicopter support (which may be unavailable if ashfall has grounded all flights), and secondary evacuation routes (some permit-holders are in areas accessible only by foot or horse).

Impact: If 50–100 backcountry parties (200–400 people) cannot reach main roads within T+6 hours, they may become trapped as ashfall intensifies and roads become impassable. Secondary evacuation by helicopter during ashfall is not feasible (engine damage risk); on-foot evacuation to safety could require 12–24 additional hours and expose hikers to respiratory distress and dehydration in ash. Estimated impact: 50–200 backcountry evacuees stranded at wilderness shelters or en route, with 5–20 hospitalized for respiratory distress or hypothermia after delayed extraction.

Likelihood: Medium

Severity: High

Action: At T-24 hours, issue an emergency permit cancellation and mandatory evacuation order to all outstanding backcountry permits, instructing permit-holders to exit via designated ranger-escorted routes or designated trail corridors. Pre-position ranger teams at key backcountry junctions (e.g., Norris-to-Canyon trail, Lamar Valley research stations) by T-12 hours, with satellite phones and emergency shelter supplies. Establish a dynamic backcountry tracking net using permit-holder check-ins via satellite messenger devices; at T+0, initiate hourly check-ins with all outstanding permit-holders and redirect non-responding parties to ranger-escort meeting points. Designate 2–3 'last-resort' wilderness shelters (pre-stocked with food, water, first aid and N95 respirators) in areas outside the modeled ashfall footprint (e.g., South Entrance/Thorofare region) so that any unplanned backcountry straggler has a signed shelter within 6–12 hours of evacuation start. Coordinate with the Wyoming-based Search and Rescue teams to stand by for ground-based extraction of stranded parties on foot after the main evacuation window closes at T+6 hours.

Risk 8 - Regulatory & Jurisdictional / Multi-State Authority

Conflicting evacuation and shelter-in-place orders from adjacent state governors and the NPS could create public confusion and non-compliance. The plan specifies a Unified Command in Denver and explicit authority transfer at the park boundary, but does not document pre-authorization letters or MOUs from the governors of Montana, Wyoming and Idaho confirming that they will cede initial command authority to the NPS and accept the Unified Command's decision to evacuate Zone One communities. If a governor perceives the NPS and FEMA as over-reaching, or if local communities lobby for a 'shelter in place' option, a competing evacuation order could emerge.

Impact: A competing shelter-in-place order from a state governor could lead 10–20% of Zone One residents to defy evacuation instructions, stay in their homes, or delay departure. This 'shadow evacuation' of those who do leave could saturate the main corridors with unplanned traffic, reducing throughput for the 35,000 park visitors by 20–40% and causing an additional 2–4 hour delay in peak evacuation. Media coverage of the conflict could further reduce public trust in official messaging.

Likelihood: Medium

Severity: Medium

Action: Obtain written pre-event confirmation from the governors of Montana, Wyoming and Idaho that they authorize and will enforce the Unified Command's evacuation orders for Zone One (100 km radius) and any Scenario Beta expansion, and that they cede operational authority over park-boundary traffic and initial shelter placement to the NPS incident commander until the Unified Command issues a formal handoff order. Include these confirmations in a signed MOU 30 days before T+0, and brief state emergency management officials and National Guard commanders on the authority structure at a joint multi-state exercise 60 days before T+0. Establish a 24/7 governor-to-FEMA hotline and a weekly pre-event coordination call so that state leadership remains informed of the escalation triggers and can preemptively explain the authority structure to media and public.

Risk 9 - Environmental / Ashfall & Air Quality

Ashfall composition, volume and dispersion are highly uncertain; modeled ash footprint and respiratory risk projections could be wrong by 50–200%, leading to incorrect shelter siting and underestimated N95 respirator demand. The plan specifies that final shelter locations will be selected at T+6 hours from the forecast wind and plume model, assuming the forecast is accurate. However, ashfall from a VEI-6 eruption has never been directly observed in North America, and volcanic ash grain-size distribution, settling rate, and regional wind variability could shift the predicted footprint by 100+ km or concentrate ash at higher than modeled levels. Pre-staged respirator stock of 100,000 N95 masks is based on a model estimate; if ashfall is heavier or more persistent than modeled, the stock could be exhausted within 24–48 hours.

Impact: If the actual ashfall footprint extends 20–50 km further than forecast, shelters selected at T+6 hours could be in areas of moderate to heavy ashfall, exposing evacuees to respiratory distress and requiring emergency relocation. A relocation of 10,000–15,000 evacuees from one shelter to another would require 3–6 hours of transport, additional buses, and a second intake and triage process, effectively delaying shelter operations by 6–12 hours. If ashfall is 2–3 times heavier than modeled, the 100,000 N95 masks would last only 12–24 hours instead of 72 hours, requiring urgent resupply. Estimated impact: 500–2,000 evacuees in unplanned ashfall zones develop respiratory distress within 6–24 hours; 5–10 die if medical care is delayed.

Likelihood: Medium

Severity: High

Action: Maintain continuous ashfall and air-quality monitoring at the forward command element and all three shelter sites using real-time PM10 and PM2.5 sensors and visual ash-depth markers. At T+6 hours, when final shelter locations are selected, update the selection based on the latest wind and plume forecast from NOAA and USGS, not the forecast used at T+0. Maintain a ranked second and third shelter backup for each primary site, located 50+ km upwind of the primary (to be confirmed daily from the latest wind forecast) so that if ashfall exceeds model predictions, a rapid (within 4 hours) relocation order can be issued. Pre-stage a supplemental 100,000 N95 masks at a secondary distribution hub (e.g., Billings or Salt Lake City) with a standing agreement for daily air or ground transport to the primary shelters if ash consumption exceeds 20% of stock per day. Conduct an air-quality monitoring exercise with NOAA and USGS 30 days before T+0, testing real-time forecast updates and relocation-decision protocols.

Risk 10 - Operational / Responder Fatigue & Rotation

Responder exposure limits and relief rotation regime are not specified with concrete numbers. The plan lists 'Responder Exposure Limits and Relief Rotation Regime' as a secondary decision, but does not define shift lengths, withdrawal thresholds, or how many relief personnel are available for rangers, highway patrol, and National Guard personnel staffing contraflow checkpoints and perimeter gates. If rangers work 8-hour shifts with 16-hour rest, approximately 1.5 responders are needed per position to maintain continuous coverage, but the plan assumes roughly 100–150 rangers can staff 5–10 contraflow and perimeter checkpoints plus backcountry sweeps. At peak evacuation (T+2 to T+8 hours), all ranger hours are consumed, leaving no relief depth.

Impact: If a key traffic-control checkpoint or perimeter gate loses its staffing because responders reach fatigue limits and no relief is available, traffic flow could halt for 30–60 minutes or looting could occur undetected. Additionally, exhausted responders are more prone to errors (miscommunication of reroute instructions, failure to detect vehicles crossing the perimeter), increasing the risk of public-safety incidents. Estimated impact: 1–2 additional hours of evacuation delay due to checkpoint staffing gaps; 2–4 looting or unauthorized-entry incidents in evacuated towns.

Likelihood: Medium

Severity: Medium

Action: Define concrete exposure limits: rangers and highway patrol shall work maximum 6-hour shifts at ash-exposed locations (traffic checkpoints, perimeters) before mandatory 2-hour rest with N95 replacement, and all responders shall withdraw completely from ash zones after 18 consecutive hours of duty. Pre-authorize the forward command to request additional National Guard personnel from Fort Carson, Colorado (FEMA Region VIII) and other states if relief coverage falls below 50% at any checkpoint. Pre-stage a stand-by reserve of 30–50 trained traffic-control responders from other regions (e.g., Colorado Parks and Wildlife, Wyoming Game and Fish) at a staging depot outside the ash zone, ready to deploy within 4 hours if additional coverage is needed. Conduct a shift-rotation and fatigue-management exercise at a key control point 30 days before T+0, testing relief logistics and N95 replacement cycles under simulated ashfall.

Risk 11 - Technical / Communications & Language Access

International visitors and non-English-speaking visitors may not receive evacuation instructions in time. The plan lists 'International Visitor, Language, and Access-Needs Notification Pathways' as a low-priority secondary decision, but does not specify what translations are prepared, which media outlets carry multilingual broadcasts, or how concession-operator networks will disseminate instructions. Yellowstone hosted ~4 million visitors in 2023, with ~40% from outside the USA. During peak season, non-English speakers could comprise 30–40% of the ~35,000 visitors in the park at any given time.

Impact: If 10,000–15,000 non-English-speaking visitors do not clearly understand evacuation instructions, they may delay departure, take wrong routes, or cluster at wrong shelters, wasting 1–2 hours and reducing overall corridor throughput. Additionally, visitors without vehicles (tour groups, those using park shuttles) may not understand reroute instructions and could become stranded at secondary destinations or held in queues longer than English-speakers. Estimated impact: 2,000–5,000 evacuees experience 2–4 hour delays due to language or transportation barriers; 10–20 left behind.

Likelihood: Medium

Severity: Low

Action: Pre-produce IPAWS messages and radio broadcasts in the five most-common visitor languages (Spanish, Japanese, German, Mandarin, French) by T-30 days, with simple, phased messages (e.g., 'Evacuate now,' 'Follow US-89 North,' 'Go to Shelter at [address]'). Coordinate with concessioner partners (Xanterra Parks and Resorts) to disseminate multilingual instructions to all guest rooms, tour buses and visitor centers at T-0. Pre-identify multilingual volunteers from each major tour operator and pre-position them at major lodges and campgrounds to translate instructions and assist non-vehicle-owning groups onto designated shuttle buses. Establish a dedicated shuttle-bus evacuation plan for tour groups and lodge-based visitors, with pre-assigned buses and drivers briefed 48 hours before the event window.

Risk 12 - Operational / Public Compliance & Messaging Credibility

Public non-compliance with evacuation orders could increase if shelter-in-place messaging is used early (to prevent shadow evacuation) but then contradicted by a Scenario Beta escalation. The plan specifies that outer-zone residents in Bozeman, Billings and Idaho Falls should be told to shelter in place or follow time-banded departure schedules, but if a Scenario Beta trigger fires (VEI-7 indicators, 500 km evacuation order), the same populations must then evacuate immediately. This reversal could be perceived as government deception or incompetence, eroding trust in official channels and causing a chaotic, uncontrolled flight.

Impact: If public trust collapses due to a shelter-in-place reversal, uncontrolled evacuation of 50,000–200,000 outer-zone residents could begin within 2–4 hours of a Scenario Beta order, creating gridlock on I-15, I-90 and US-191 that prevents the organized Zone One evacuation of the 35,000 park visitors and strands medical transport. Additionally, reduced compliance with time-banded departure instructions or shelter assignments would increase the unplanned vehicle load on evacuation corridors by 20–40%, consuming an additional 4–6 hours of corridor throughput.

Likelihood: Medium

Severity: High

Action: Develop and pre-authorize a 'Adaptive Messaging Protocol' that explains the rationale for phased evacuation orders: initial shelter-in-place is based on current (low) eruption probability; Scenario Beta escalation will be triggered by specific USGS indicators (published in advance); outer-zone residents should monitor official channels daily and expect possible reversal if indicators cross thresholds. Deliver this protocol to media outlets, emergency management offices, and community leaders in Zone One communities (Bozeman, Gardiner, West Yellowstone, Cody) 60 days before T+0, so that the public understands the escalation logic. At T+0 hours, rebroadcast the protocol on IPAWS, local radio and TV to reinforce the message. If a Scenario Beta trigger fires, issue a separate messaging campaign explaining the new indicator values and stating that the previous shelter-in-place order is superseded, effective immediately. Conduct a messaging credibility exercise with local government and media 60 days before T+0 to test message clarity and anticipate public-response scenarios.

Risk 13 - Financial / Procurement & Contracting

Procurement and contracting lead times for emergency supplies (bottled water, N95 respirators, generator fuel, buses, tents) are not addressed. The plan assumes water convoys can be 'mobilized within 12 hours,' but sourcing, loading and dispatching a convoy of 20–40 water trucks requires coordination with suppliers, transportation contractors, and state agencies. If contracts are not pre-positioned or suppliers are not pre-authorized, delays of 24–48 hours are typical for emergency procurements.

Impact: A 24-hour delay in water-convoy dispatch means the convoy does not arrive at Bozeman or Idaho Falls until T+36 hours (instead of T+12 hours), during which shelter occupancy could reach 15,000–20,000 people. Water shortages affecting thousands of evacuees for 24+ hours increase risk of dehydration, medication non-compliance, and secondary health emergencies. Similar delays in N95 respirator resupply could leave shelters and hospitals without adequate stock within 48 hours. Estimated impact: 1,000–3,000 evacuees experience 12–24 hours without adequate water; additional 20–50 respiratory distress cases.

Likelihood: Medium

Severity: Medium

Action: Execute pre-event contracts with bottled-water suppliers, N95 respirator manufacturers, generator-fuel wholesalers, and charter-bus operators 60 days before T+0, with explicit 'surge-mobilization' clauses requiring 12-hour dispatch of supplies upon verbal activation by the forward command. Identify alternative suppliers (e.g., water distributors in Pocatello, ID and Butte, MT; N95 suppliers in Salt Lake City and Denver) and list them in a standby-supplier roster. Pre-authorize payment via emergency FEMA contract vehicles so that suppliers can charge supplies immediately without normal competitive-bidding delays. Establish a procurement checkpoint at the forward command element tasked with tracking all inbound supply shipments and alerting the incident commander if any convoy is delayed >4 hours beyond dispatch.

Risk 14 - Technical / Electric Grid Resilience

The plan identifies grid failure due to ash-induced flashovers as a contingency and directs generator fuel to hospitals and communications centers, but does not specify which transmission lines are at highest risk, which substations have single points of failure, or how voltage regulation and protective relays will behave under ashfall. Regional power utilities (Montana-Dakota Utilities, Pacific Power, Idaho Power) operate interconnected transmission networks that could experience cascading failures if multiple substations are hit by ash-induced flashovers simultaneously.

Impact: If a major transmission line fails and backup protection systems malfunction due to ash, a regional blackout affecting 100,000+ people could occur within 2–4 hours of ashfall onset, well before generator fuel can reach all facilities. A multi-hour regional blackout would affect water pumping and treatment, fuel convoys' refrigeration and communication equipment, ambulance dispatch centers, and shelter HVAC systems. Estimated impact: 4–8 hour regional blackout affecting 50,000–100,000+ people; 5–10 additional deaths in hospitals and care facilities due to loss of ventilator and life-support power.

Likelihood: Low

Severity: High

Action: Coordinate with Montana-Dakota Utilities, Pacific Power and Idaho Power 60 days before T+0 to identify critical transmission lines, substations and protective relays in the evacuation-corridor and shelter-area zones. Request pre-deployment of mobile generator units and voltage-regulation equipment at the two largest substations serving Bozeman and Idaho Falls. Establish a 24/7 utility-operations hotline from the forward command to the regional dispatch centers so that the incident commander can track grid status and request emergency load shedding or localized de-energization to prevent cascading failures. Conduct a grid-failure scenario exercise with utility operators 30 days before T+0, testing manual switchover procedures and the adequacy of generator fuel at critical facilities.

Risk 15 - Operational / Landslide & Road Engineering

The South Entrance (US-89/191/287) is currently landslide-blocked, and the plan does not specify the debris volume, ground conditions or timeline for a single-lane clearance or bypass. Engineering assessment of the slide is not described. Secondary slides and hydrothermal explosions could further damage the North Entrance (US-89) and the Grand Loop Road during the evacuation window, adding to the blockage load.

Impact: If the South Entrance clearance attempt fails or takes >12 hours, the plan loses a potential third exit route and relies entirely on US-191/US-20 (west) and US-89 (north). This concentration adds 20–40% additional load to the two surviving corridors, extending evacuation time from 6 hours to 8–10 hours and increasing the overlap with ashfall onset. If a secondary explosion damages the North Entrance during the evacuation peak, that corridor could be reduced to one lane for 2–4 hours, creating a bottleneck that delays 2,000–4,000 vehicles.

Likelihood: Medium

Severity: High

Action: Conduct a pre-event geotechnical survey of the South Entrance landslide and the Grand Loop Road 60 days before T+0, using ground-penetrating radar and aerial drones to assess debris volume, slope stability and secondary slide risk. Develop a time-boxed single-lane clearance plan (max 4-hour work window) and a longer-term bypass-route plan, with pre-positioned heavy equipment and a clear abort trigger (e.g., renewed seismic activity M>4.0). Deploy a geotechnical monitoring team at the North Entrance and Grand Loop Road sections starting at T-12 hours to detect incipient slope movement and trigger temporary traffic closures before collapse. Establish a 'loss-of-exit' contingency: if the South Entrance or North Entrance becomes impassable and cannot be restored within 6 hours, the forward command will issue a shelter-in-place order for any vehicles still in the south or north sections of the park and redirect them to the nearest surviving exit (US-191/US-20 west or US-89 north) via the safest park roads available.

Risk 16 - Operational / Visitor Transport & Special Needs

The plan does not specify transport arrangements for disabled visitors, elderly visitors in lodges, or families with children who may have mobility or medical constraints. A mandatory private-vehicle evacuation assumes all visitors have access to a functioning vehicle; the ~5–10% of visitors who arrived via tour bus, without a personal vehicle, or with mobility aids may face delays in accessing contraflow lanes or may be left behind if buses are not pre-allocated and staffed.

Impact: If 1,500–3,500 mobility-constrained or vehicle-less visitors cannot board evacuation shuttles within the first 2 hours, they may become trapped in lodges or at trailheads. Emergency extraction of such populations by helicopter is not feasible if airspace is closed or ashfall is heavy. These visitors could become casualties or stranded, requiring secondary rescue operations after the main evacuation window. Estimated impact: 200–500 stranded or delayed evacuees; 5–20 requiring rescue or hospital care due to exertion or medical decompensation.

Likelihood: Medium

Severity: Medium

Action: Coordinate with Xanterra Parks and Resorts and other concessioners 60 days before T+0 to identify all mobility-constrained guests and pre-arrange dedicated evacuation buses (1–2 buses per major lodge) staffed with attendants trained in mobility assistance. At T-12 hours, confirm occupancy of all lodges and tour groups via concessioner manifests, and designate a 'priority-transport' staging area at each lodge where mobility-constrained guests gather first, ahead of general traffic. Pre-authorize a secondary evacuation protocol: if any lodge or group cannot evacuate within the first 3 hours, notify the forward command, which will dispatch helicopter support (if available) or a ground-based rescue team from the National Guard. Pre-stage medical supplies and attendants at the priority-staging areas to manage any acute medical events during the evacuation wait.

Risk 17 - Regulatory & Inter-agency Coordination

FAA authority over airspace grounding (ZLC and ZSE) is not explicitly coordinated with the Unified Command's decision-making. The plan states that a VEI-6 eruption will trigger grounding of ZLC and ZSE airspace, but the FAA operates independently and may not immediately coordinate grounding with the incident commander's needs for medevac, surveillance or emergency airlift. Conversely, the incident commander may want exceptions for medevac that the FAA blocks due to ash-concentration forecasts.

Impact: Delays in grounding coordination could result in one or more aircraft encountering ash and suffering engine damage within the first 2–4 hours of ashfall, adding a secondary emergency response load and reducing public trust in the warning system. Alternatively, rigid FAA grounding without any medevac exceptions could deny hospitals access to helicopter transport for critical patients, delaying some transfers by 4–6 hours and causing preventable deaths. Estimated impact: 1–3 aircraft-ash encounters; 2–5 critical patients unable to access helicopter medevac within the first 24 hours.

Likelihood: Low

Severity: High

Action: Establish a pre-event coordination protocol with the FAA Regional Flight Service Stations (Salt Lake City and Seattle centers) and the air-operations offices at mountain airports (Gallatin County, Jackson Hole, Billings) at least 60 days before T+0. Define an explicit trigger for airspace grounding (e.g., USGS detection of VEI-6 magma signatures, NOAA forecast of ash concentration >100 µg/m³ in flight corridors) and pre-authorize a narrow set of medevac and survey flight corridors below ash-concentration thresholds. Establish a 24/7 aviation-operations liaison at the forward command element with direct phone lines to the FAA regional desk and the military (Malmstrom AFB, Montana) to coordinate real-time flight requests and ash-model updates. Pre-authorize helicopter fuel caches at forward airfields (Gallatin County, Jackson Hole, Billings) to enable rapid deployment of medevac sorties if airspace restrictions are lifted temporarily.

Risk summary

This is a high-stakes, multi-state government evacuation plan for a VEI-6+ volcanic event at Yellowstone Caldera with a 72-hour decision window and 40% eruption probability. The plan aims to evacuate ~35,000 tourists and 800 staff from the park interior (Zone Zero) within 6 hours and expand to 100 km radius communities (Zone One) within 24 hours. The three most critical risks are: (1) single-point road chokepoints on narrow, ash-exposed mountain corridors (US-191, US-89) with no bypass capacity if a breakdown, rockfall, or secondary slide occurs during peak evacuation; (2) cascading communications and command failures as cell towers collapse from ash and tremors, leaving drivers and responders unable to receive route updates, and the cross-jurisdiction authority transfer between NPS and three state governors creating command gaps; (3) shelter and hospital capacity collapse under Scenario Beta (VEI-7) expansion to 500 km radius, which would exceed all pre-staged supplies, road throughput and facility capacity, yet the trigger is pre-authorized without a defined secondary-stage evacuation plan. These three risks are tightly coupled: communication failure undermines the contraflow operation, command gaps delay the escalation decision, and inadequate shelter capacity forces uncontrolled shadow evacuation that saturates the very corridors the plan depends on. Mitigation relies on execution discipline, real-time asset positioning, and a credible second-stage plan for Scenario Beta that does not yet exist.

Make Assumptions

Question 1 - What funding source and budget ceiling cover pre-positioned supplies, contracts and surge operations across FEMA, NPS and the three states?

Assumptions: Assumption: Funding comes from a federal emergency declaration (Stafford Act) plus pre-event contract vehicles, with an initial surge envelope of about USD 150-250 million (estimate), reimbursed through FEMA procedures. Justification: large multi-state responses typically draw on declaration-based cost-sharing.

Assessments: Title: Financial Feasibility Assessment Description: Evaluates funding availability and speed of access. Details: Risk: procurement delays of 24-48 hours (estimate) without pre-awarded contracts. Mitigation: pre-event surge contracts for water, N95, fuel and buses, with verbal activation. Opportunity: FEMA contract vehicles remove competitive-bidding delay. Track burn rate in USD hourly at the forward command; hold a 20% contingency (proposed) for Scenario Beta.

Question 2 - Which milestones and decision gates must be met within the 72-hour window, including the T+6 evacuation and the T+12 water convoy deadlines?

Assumptions: Assumption: Project starts at Month 0 (2026-10-14) with preparation as the first activity. Milestones: Zone Zero cleared by T+6 hours, Zone One by T+24 hours, water convoys dispatched by T+12 hours (user constraints), and shelter selection at T+6 from the plume forecast. Justification: matches the phased structure of the plan.

Assessments: Title: Timeline Feasibility Assessment Description: Tests whether phase deadlines are achievable. Details: Risk: ashfall and gridlock may stretch the 12-hour convoy to 18-30 hours (estimate). Mitigation: pre-stage depots before T+0, reserved convoy lane, hourly gate reviews. Opportunity: a three-exit design (including East Entrance) shortens clearance. Hard abort triggers for southern clearance work keep the schedule from slipping.

Question 3 - What numbers of rangers, highway patrol, National Guard, tow crews, buses and medical staff are available for traffic control, sweeps and perimeters?

Assumptions: Assumption: About 100-150 NPS rangers (estimate), supplemented by Montana, Wyoming and Idaho highway patrol and Guard units, staff the control points; relief depth is 1.5 responders per post (proposed). Justification: 8-hour shifts need that ratio for continuous coverage.

Assessments: Title: Resource Adequacy Assessment Description: Compares staffing demand with likely availability. Details: Risk: all ranger hours consumed during T+2 to T+8, leaving no relief. Mitigation: request out-of-region Guard and a 30-50 person standby reserve (proposed), tier posts by criticality. Count responder N95s separately from the 100,000 civilian stock (user constraint). Opportunity: concessioner buses raise people per vehicle.

Question 4 - What legal authorities and agreements govern the NPS-to-state handoff, FEMA Region 8/10 coordination, FAA grounding and interstate mutual aid?

Assumptions: Assumption: Authority transfers at defined roadside checkpoints under a written protocol, backed by governor MOUs and EMAC mutual aid; Idaho coordination runs through a FEMA Region 10 liaison at the Denver RRCC. Justification: standard Unified Command practice.

Assessments: Title: Governance Assessment Description: Reviews command clarity and legal basis. Details: Risk: authority gaps mid-corridor delay reroutes by 15-45 minutes (estimate). Mitigation: Boundary Coordination Officer at the forward element, pre-signed MOUs, pre-authorized state reroute powers. FAA grounding needs a liaison at the Unified Command. Benefit: pre-agreed authority removes turf disputes and speeds the pre-authorized Scenario Beta order.

Question 5 - What are the principal life-safety hazards (chokepoint failure, secondary slides, ash exposure, hospital power loss, stranded backcountry visitors) and the abort criteria for each?

Assumptions: Assumption: Principal hazards are corridor blockage in Gallatin Canyon, secondary slides at the South Entrance, backcountry stragglers, and hospital power loss. Abort criteria are seismic-based (e.g. renewed M4.0+ activity, proposed threshold) and blockage lasting over 45 minutes (proposed) triggers diversion.

Assessments: Title: Safety and Risk Assessment Description: Prioritizes hazards by severity and likelihood. Details: Highest: single-point corridor failure (high/high). Mitigation: pre-placed tow and rockfall teams at chokepoints, geotechnical monitoring, diversion rule. Crew safety: time-boxed clearance with abort triggers. Medical: 72-hour fuel reserves at receiving hospitals. Maintain a risk register with owners and review each shift.

Question 6 - How will ashfall, contaminated reservoirs and air quality affect shelter siting, water supply and respirator demand?

Assumptions: Assumption: Ash footprint forecasts are uncertain by tens of kilometers (estimate), so shelters are chosen at T+6 with ranked upwind backups, open reservoirs are isolated before ash, and N95 demand may exceed 100,000 (user constraint) within days.

Assessments: Title: Environmental Impact Assessment Description: Evaluates ash, water and air-quality effects on operations. Details: Risk: shelters in heavier ash require relocating 10,000+ people (estimate). Mitigation: real-time PM10/PM2.5 sensors, backup sites 50+ km upwind (proposed), supplemental N95 stock at Billings or Salt Lake City, reservoir isolation. Note N95s clog quickly in heavy ash, so replacement cycles must be planned. Opportunity: USGS/NOAA plume updates refine siting.

Question 7 - Which stakeholders (governors, local officials, concessioners, utilities, hospitals, international visitors, outer-zone residents) must be engaged, and how?

Assumptions: Assumption: Engagement runs through the Unified Command liaison cell: governors via MOUs, concessioners such as Xanterra for lodge manifests and buses, utilities for grid coordination, and consular and multilingual channels for foreign visitors.

Assessments: Title: Stakeholder Engagement Assessment Description: Maps who must be aligned and the risk of non-compliance. Details: Risk: conflicting shelter-in-place and evacuation orders cut corridor throughput 20-40% (estimate). Mitigation: unified messaging protocol, published USGS triggers, joint exercises. Non-English visitors may be a large share of the 35,000, so pre-produced multilingual alerts are needed. Opportunity: trusted local radio sustains credibility if escalation reverses earlier guidance.

Question 8 - What communications, traffic management, logistics tracking and power systems must keep working under ash and tremor, and what are the fallbacks?

Assumptions: Assumption: Layers are IPAWS/WEA/NOAA Weather Radio, Guard signal bridging, satellite terminals, highway advisory radio, variable message signs and printed route cards; priority generator fuel goes to hospitals and comms centers.

Assessments: Title: Operational Systems Assessment Description: Tests resilience of comms, power and logistics tracking. Details: Risk: cell network failure leaves 10-20% of drivers on unintended routes (estimate). Mitigation: deploy repeaters and satellite phones to control points before ash, pre-recorded HAR messages, printed cards. Fuel tiering protects hospitals, comms and shelter kitchens. Test systems in ash-simulation exercises before the window. Use one shared common operating picture across NPS, states and Guard.

Distill Assumptions

Review Assumptions

Domain of the expert reviewer

Government emergency management and disaster response planning, with focus on multi-jurisdiction civil protection operations, evacuation logistics, and life-safety decision-making under extreme time pressure and uncertainty.

Domain-specific considerations

Issue 1 - Missing Scenario Beta Secondary-Stage Destination Plan and Capacity Analysis

The plan pre-authorizes a VEI-7 trigger that will order immediate 500 km radius evacuation, potentially affecting 100,000 to 500,000+ people across Montana, Wyoming, Idaho and Colorado. However, no second-stage shelter hubs, host-community coordination, onward transport routes, or supply-staging depots are defined. The stated 'shelter-siting strategy' applies only to Bozeman and Idaho Falls (100 km radius), which become overwhelmed within hours if Scenario Beta expands the evacuation. This absence creates a vacuum: once the trigger fires, evacuees and residents have no published destinations, leading to chaotic, uncontrolled flight on all routes away from Yellowstone. This directly undermines the core evacuation plan.

Recommendation: Develop and pre-authorize a written Scenario Beta Secondary-Stage Evacuation Plan by Month -2, specifying: (1) five to ten ranked secondary shelter hubs (e.g., Salt Lake City metro, Billings, Denver, Cheyenne, Boise) with capacity estimates and pre-signed MOUs with host communities; (2) tiered public messaging that differentiates shelter-in-place zones (250–500 km, self-supplied residents), time-banded zones (100–250 km, shelters pre-assigned by county), and organized evacuation (Zone One); (3) bus fleets and rail corridors moving evacuees from primary shelters to secondary hubs, using lateral routes away from I-90; (4) supply-estimation models for 100,000–500,000 additional people, with food, water, medical stock pre-positioned at secondary hubs before Month 0 (2026-10-14). Conduct a joint multi-state Scenario Beta exercise 30 days before the eruption window, testing messaging, routing and secondary-hub readiness. Assign ownership of each secondary hub to a named state/county emergency manager, with quarterly coordination calls before the event.

Sensitivity: Baseline assumption: Scenario Beta affects 50,000–100,000 additional evacuees outside the 100 km radius. If no secondary plan exists and uncontrolled evacuation saturates I-15, I-80 and I-90, the delay to organized Zone One evacuation is estimated at 4–8 hours, reducing overall corridor throughput by 30–50% and extending the overlap between peak evacuation and ashfall arrival. Cost of secondary-hub pre-positioning and planning (estimated USD 20–40 million) is a fraction of the surge envelope (USD 150–250 million estimate); failure to execute costs an additional USD 100–200 million in emergency response and 5–20 preventable deaths in stranded populations.

Issue 2 - Responder Exposure Limits and Relief Rotation Regime Undefined: Staffing Depth Insufficient for 72-Hour Operations

The plan lists 'Responder Exposure Limits and Relief Rotation Regime' as a secondary decision but does not specify shift lengths, withdrawal thresholds, or how many relief personnel exist. Assumption of 100–150 NPS rangers (estimate), 1.5 relief per post (proposed), and no explicit responder N95 count creates a staffing gap: at peak evacuation (T+2 to T+8 hours), all ranger hours are consumed with zero relief depth. If strict exposure limits are applied (e.g., 6-hour shifts with 2-hour rest before 18-hour withdrawal), the coverage available at traffic-control and perimeter checkpoints during the evacuation peak may fall below 50%, causing throughput loss and enabling unauthorized entries or looting. Conversely, loose limits expose rangers to respiratory injury and entrapment, degrading the force just when ashfall intensifies.

Recommendation: Define concrete responder exposure limits in writing by Month -1: rangers and highway patrol work maximum 6-hour shifts at ash-exposed locations (contraflow points, perimeters, comms sites) before mandatory 2-hour rest with N95 replacement; all responders withdraw completely after 18 consecutive hours of duty. Count responder N95 respirators separately from the civilian stock (100,000 user constraint), with a minimum 50% surge buffer for replacement cycles (estimated 150,000–200,000 total responder+civilian stock). Pre-stage a 30–50 person standby reserve from outside the region (Colorado Parks and Wildlife, Wyoming Game and Fish, Idaho Department of Lands) at a logistics depot outside the ash zone, ready to deploy within 4 hours if coverage falls below 50% at any checkpoint. Pre-authorize the forward command to request additional National Guard from Fort Carson without needing supervisory approval. Conduct a shift-rotation exercise at a control point 30 days before the window, testing relief logistics, N95 replacement cycles and fatigue protocols under simulated ashfall.

Sensitivity: Baseline staffing: 100–150 rangers at 1.5 relief ratio covers 100–150 positions with continuous staffing. If exposure limits reduce effective working time to 50% (6-hour shifts with 12-hour rest), available staffing drops to 50–75 people, creating gaps at 30–50% of positions. Each uncovered checkpoint reduces corridor throughput by ~5–10% (estimate), so understaffing adds 2–4 hours to total evacuation time and strands 500–2,000 vehicles in ash exposure. Cost of a 30–50 person standby reserve (estimated USD 3–5 million over 72 hours) prevents a 2–4 hour evacuation delay worth USD 50–100 million in indirect costs (medical, rescue, stranded-vehicle recovery).

Issue 3 - Ashfall Footprint Uncertainty and Dynamic Shelter-Siting Strategy Lack Real-Time Monitoring and Relocation Protocols

The plan states shelters will be 'selected at T+6 hours from the forecast wind and plume model,' assuming the forecast is accurate. However, ashfall from a VEI-6 eruption has never been directly observed in North America; volcanic ash grain-size distribution, settling rates and regional wind variability could shift the modeled footprint by 100+ km. Additionally, the plan pre-stages 100,000 N95 masks (user constraint) based on a model estimate; if ashfall is 2–3 times heavier than forecast, this stock lasts only 12–24 hours instead of 72 hours. Finally, the plan does not specify real-time ash and air-quality monitoring at shelter sites or a trigger to relocate evacuees if actual ashfall exceeds forecast. This creates a scenario in which 10,000–15,000 evacuees are sheltered in zones of moderate to heavy ashfall, requiring emergency relocation within 6–12 hours and exposing them to respiratory distress.

Recommendation: Establish continuous ashfall and air-quality monitoring at the forward command and all three shelter sites using real-time PM10/PM2.5 sensors and visual ash-depth markers, updated hourly starting at T-12 hours. At T+6 hours when final shelter locations are selected, update the selection based on the latest wind and plume forecast from NOAA and USGS, not the T+0 forecast. Maintain a ranked second and third shelter backup for each primary site, located 50+ km upwind (confirmed daily from the latest wind forecast) so a rapid relocation order can be issued within 4 hours if ashfall exceeds model predictions. Pre-stage a supplemental 100,000 N95 masks at a secondary distribution hub (e.g., Billings or Salt Lake City) with a standing agreement for daily air or ground transport to primary shelters if ash consumption exceeds 20% of stock per day. Conduct an air-quality monitoring exercise with NOAA and USGS 30 days before the window, testing real-time forecast updates, sensor accuracy and relocation-decision protocols.

Sensitivity: Baseline model assumption: ashfall matches forecast within a 20 km margin, stock lasts 72 hours. If actual ashfall shifts 50+ km from forecast or doubles in intensity, shelter relocation is needed within 6–12 hours. Cost of relocating 10,000–15,000 evacuees (estimated USD 5–10 million in additional buses, intake processing and medical) is high, but failure to relocate results in 500–2,000 evacuees developing respiratory distress within 24 hours, with 5–10 preventable deaths. Pre-positioned backup shelters and supplemental N95 stock (estimated USD 10–15 million) avoid both costs.

Issue 4 - Egress Corridor Chokepoint Vulnerability: Gallatin Canyon and Gardiner Single-Point Failures Lack Viable Bypass and Rapid-Clearance Capacity

The plan's three egress corridors (US-191/US-20 via Gallatin Canyon, US-89 via Gardiner, US-14/16/20 via Cody) depend on narrow, two-lane mountain passes with minimal shoulders, documented rockfall and secondary-slide hazard, and no pre-surveyed bypass routes. Gallatin Canyon is especially critical: a single breakdown, rockslide, or tremor-induced slide could block the entire contraflow and strand 500–2,000 vehicles within 30 minutes. The plan lists 'pre-positioned tow and rescue assets at chokepoints' but does not specify the number of crews, equipment staging, or hard decision rules for diversion if clearance exceeds 45 minutes. The South Entrance remains landslide-blocked, eliminating a potential third southern exit that could relieve the north and west corridors.

Recommendation: Pre-position at least two mobile heavy-equipment teams (wreckers, debris chippers, spotters) at Mammoth or Spanish Creek by Month -1, with 72-hour fuel and supplies, tasked to reach any Gallatin Canyon blockage within 15 minutes of dispatch. Establish live geotechnical monitoring along Gallatin Canyon, US-89 near Gardiner and Grand Loop Road using motion sensors or drones at identified slide-prone zones, with automatic alerts to the forward command if incipient movement is detected. Conduct a geotechnical survey of the South Entrance landslide 60 days before the window; develop a time-boxed (4-hour maximum) single-lane clearance plan and a longer-term bypass-route plan, with hard abort triggers tied to seismic activity (M>4.0 renewed swarm, proposed threshold). Issue a written 'loss-of-exit' contingency: if any primary corridor becomes impassable for more than 45 minutes (proposed threshold) and cannot be restored, the forward command will trigger overflow diversion to the nearest surviving exit and issue a shelter-in-place order for vehicles still in that sector. Test the tow-team mobilization and diversion protocol during a full-scale exercise 30 days before the window.

Sensitivity: Baseline assumption: corridors remain passable with only routine debris clearing, or blockages are resolved within 30–45 minutes. If a major blockage occurs and persists for 2–4 hours, estimated impact is 5,000–8,000 stranded vehicles in one corridor, adding 2–4 hours to peak evacuation time and increasing the overlap with ashfall onset by 20–30%. Cost of pre-positioned tow equipment and crews (estimated USD 2–3 million) prevents a cascading 4-hour delay worth USD 50–100 million in indirect emergency response costs and 10–20 additional respiratory-distress casualties.

Issue 5 - Cross-Jurisdiction Authority Transfer and Command Gaps: NPS-to-State Handoff and FEMA Region 8/10 Seams Lack Explicit Protocols and Real-Time Coordination

The plan specifies authority transfer 'at the park boundary under written protocol,' with NPS incident commander handing responsibility to state governors at defined checkpoints. However, contraflow traffic does not stop at jurisdictional lines; drivers cross from NPS to state control mid-queue, creating a window where no single authority owns traffic-reroute or shelter-assignment decisions. Additionally, Idaho falls under FEMA Region 10 (Seattle) while Montana and Wyoming fall under Region 8 (Denver). The plan names only the Denver RRCC, leaving Region 10 mutual aid (Boise and Pocatello resources) uncoordinated and potentially delayed by 1–2 hours. Furthermore, the plan does not specify written MOUs with the three governors confirming their acceptance of NPS incident command authority or their agreement to enforce unified messaging, creating risk of conflicting evacuation orders if local pressure favors shelter-in-place.

Recommendation: Establish a dedicated Boundary Coordination Officer role, co-located at the forward command element (Bozeman or Livingston), with real-time voice and data links to the NPS incident commander and the designated state highway patrol and National Guard commanders on both sides of the boundary. Issue a written protocol specifying that the boundary officer controls traffic reroutes and initial shelter assignments during the corridor crossing, and that NPS care ends at a specific roadside checkpoint (e.g., Mammoth Checkpoint or Gallatin County line) where state custody formally begins. Pre-authorize state on-scene commanders to issue temporary reroutes without requesting park ranger approval, reducing decision latency. Add an explicit FEMA Region 10 liaison call at T+0 hours from the Denver RRCC, with pre-agreed mutual aid arrangements (e.g., Boise and Pocatello fuel, water and medical resources) documented in a signed MOU 60 days before the window. Obtain written pre-event confirmation from the governors of Montana, Wyoming and Idaho confirming their authorization of the Unified Command's evacuation orders for Zone One and any Scenario Beta expansion, and their commitment to enforce unified public messaging. Conduct a multi-state command-authority exercise 60 days before the window, testing the boundary handoff, Region 8/10 coordination and governor-to-FEMA hotline under simulated escalation scenarios.

Sensitivity: Baseline assumption: authority transfer occurs smoothly with no decision latency or jurisdictional conflict. If authority gaps delay reroutes or shelter assignments by 15–45 minutes (estimate), one instance cascades into a backup affecting 500–1,000 vehicles, adding 1–2 hours to peak evacuation. If FEMA Region 10 mutual aid is not pre-authorized, water and fuel convoys from Boise or Pocatello are delayed 1–2 hours, leaving shelters 12–24 hours without adequate supply. Cost of pre-event MOUs and one multi-state exercise (estimated USD 0.5–1 million) prevents a 1–2 hour evacuation delay and supply shortage worth USD 50–100 million in indirect costs.

Issue 6 - Communications Layer Fragility Under Cascading Failures: Ash-Induced Cell-Network Collapse and Tremor Damage Leave IPAWS and Bridge Systems Untested Under Actual Conditions

The plan relies on IPAWS and Wireless Emergency Alerts as the primary public channel, with National Guard signal bridging as the fallback for responder coordination at gateway towns. However, ash-induced flashovers on transmission lines, tremor damage to cell towers, and silicate-ash clogging of repeater fans could collapse the local network faster than signal units can deploy. The plan does not specify the number of Guard signal units available, their staging locations, fuel and equipment pre-positioning, or testing protocols under simulated ashfall. Additionally, printed route cards and highway advisory radio (HAR) are mentioned as fallbacks but are not pre-produced or validated for clarity and multilingual comprehension. Finally, the plan assumes 'National Guard signal bridging' restores responder radios 'at gateway towns,' but does not specify which towns, how many radio channels are needed, or how interoperability among NPS, state patrol and Guard nets is verified before the event.

Recommendation: Deploy National Guard signal corps teams with satellite phones, portable repeaters, and generator fuel to each contraflow control point and the forward command element (Bozeman/Livingston) at T-12 hours, before ashfall onset. Pre-stage printed route cards and windshield placards at all park entrance stations and lodges by Month -1, with simple instructions ('North Exit: Follow US-89 to Gardiner, then I-90 to Livingston') in English and the five most common visitor languages (Spanish, Japanese, German, Mandarin, French), including shelter addresses and contact numbers. Activate all available highway advisory radio stations and variable message signs along US-191, US-20, US-89 and I-90 with pre-recorded messages updated hourly from the forward command. Specify that Guard signal teams will establish redundant radio nets at West Yellowstone, Gardiner, Cody, Bozeman, Idaho Falls and Livingston, with formal interoperability testing 30 days before the window (on-air checks across all agencies, frequency coordination, call signs and protocol). Test satellite and portable-repeater systems in ash-simulation exercises at each control point 30 days before the window, measuring ashfall effects on radio propagation, equipment overheating and operator visibility.

Sensitivity: Baseline assumption: IPAWS and WEA function for the first 4–6 hours, giving drivers time to depart; Guard signal bridging restores responder coordination within 2–4 hours of deployment. If cell network fails within 1–2 hours (early ashfall or transmission-line damage) and Guard signal units are delayed in deployment, an estimated 10–20% of drivers take unintended routes, adding 1–3 hours to some transit times. Loss of responder-coordination for 30 minutes to 2 hours delays 5–10% of ambulance and hospital patient transfers. Cost of signal units, satellites, repeaters and fuel (estimated USD 5–10 million) prevents a 1–3 hour evacuation delay and routing chaos worth USD 100–200 million in indirect costs and 10–20 additional casualties.

Issue 7 - International and Non-English-Speaking Visitor Notification: Language Access and Mobility-Assistance Gaps Leave 10,000–15,000 Vulnerable Visitors Unaccounted For

The plan lists 'International Visitor, Language, and Access-Needs Notification Pathways' as a low-priority decision, stating only that concessioner and consular networks should carry instructions. However, Yellowstone hosted ~4 million visitors in 2023, with approximately 40% from outside the USA. During peak season, non-English speakers could comprise 30–40% of the 35,000 visitors in the park at any time (estimate), meaning 10,000–15,000 evacuees may not understand English-language IPAWS alerts or ranger announcements. Additionally, the plan does not specify how visitors arriving via tour buses, without personal vehicles, or with mobility aids (elderly, disabled, families with young children) will access contraflow lanes or priority evacuation shuttles. Visitors without vehicles and unclear evacuation instructions could delay departure, cluster at wrong shelters, or become stranded if buses are not pre-allocated and staffed.

Recommendation: Pre-produce IPAWS messages, radio broadcasts and digital alerts in the five most common visitor languages (Spanish, Japanese, German, Mandarin, French) by Month -1, with simple, phased messages ('Evacuate now,' 'Follow US-89 North,' 'Go to Shelter at [address]'). Coordinate with concessioner Xanterra Parks and Resorts to pre-arrange multilingual briefings for all guest rooms, tour buses and visitor centers at T-0 hours. Pre-identify 20–50 multilingual volunteers from major tour operators and position them at major lodges and campgrounds by T-0, with translation materials and communication devices. Establish a dedicated shuttle-bus evacuation plan for tour groups and lodge-based visitors by Month -1, pre-assigning 4–6 buses per major lodge (estimated 20–30 buses total) with pre-briefed drivers and attendants trained in mobility assistance. At T-12 hours, confirm lodge occupancy via concessioner manifests and create 'priority-transport' staging areas at each lodge for mobility-constrained guests, with medical supplies and attendants pre-positioned to manage acute events. Pre-authorize a secondary protocol: if any lodge cannot evacuate within 3 hours, notify the forward command, which will dispatch helicopter support (if available) or ground rescue teams from the National Guard.

Sensitivity: Baseline assumption: English-language alerts and visual traffic cues reach 90% of visitors; 10% (3,500 people) experience 1–2 hour delays due to language or mobility barriers. If multilingual alerts are absent and mobility assistance is not pre-arranged, this proportion could rise to 30–40% (10,000–15,000 people), adding 2–4 hours to some evacuee transit times and stranding 50–200 people. Cost of pre-produced multilingual materials, volunteer coordination and dedicated shuttle buses (estimated USD 2–3 million) prevents a 2–4 hour evacuation delay and 5–15 preventable stranding incidents.

Issue 8 - Hospital and Utility Power Grid Failure: No Explicit Fuel Pre-Positioning Timeline, Multi-Hour Generator Startup Failures, and Cascade-Failure Risk Under Simultaneous Ashfall on Multiple Substations

The plan identifies grid failure as a contingency and directs fuel priority to hospitals and communications centers, but does not specify which hospitals are critical receivers, fuel pre-positioning timeline, or how many hospitals have adequate on-site reserves. Regional hospitals typically have 24–48-hour generator fuel on hand; a simultaneous power loss across multiple substations due to ash-induced flashovers could occur within 4–8 hours of ashfall, faster than fuel convoys can deliver from distant depots (Rock Springs, WY is 200+ miles away estimate). Additionally, hospitals often have single fueling ports and outdated generators with startup failures during high-stress events; a 4-hour outage before generator fuel arrives could force cancellation of 10–20 surgeries and loss of ventilator support if manual bagging fails. Finally, the plan does not coordinate with regional power utilities (Montana-Dakota Utilities, Pacific Power, Idaho Power) to identify critical transmission lines, substations with single-point failures, or protective relay behavior under ashfall.

Recommendation: Pre-position 72-hour diesel and propane fuel reserves at the three largest receiving hospitals (Bozeman Deaconess Medical Center, Livingston HealthCare, Eastern Idaho Regional Medical Center) by Month -1, confirming tank capacity and fueling-port adequacy with each facility. Establish fuel-delivery contracts with local vendors (e.g., Yellowstone Energy, Basin Fuel) requiring priority dispatch and arrival within 2 hours of a fuel request during the event. Conduct a hospital-power-failure and generator-startup exercise at each facility 30 days before the window, testing manual generator startup procedures, fuel-transfer protocols, load-shedding protocols and backup surgical equipment under simulated ashfall. Coordinate with Montana-Dakota Utilities, Pacific Power and Idaho Power 60 days before the window to identify critical transmission lines, substations and protective relays in the evacuation and shelter zones. Request pre-deployment of mobile generator units and voltage-regulation equipment at the two largest substations serving Bozeman and Idaho Falls. Establish a 24/7 utility-operations hotline from the forward command to each regional dispatch center so the incident commander can track grid status and request emergency load shedding or localized de-energization to prevent cascading failures. Pre-authorize helicopter fuel caches at forward airfields (Gallatin County, Jackson Hole, Billings) to enable rapid delivery of fuel or emergency medical supplies to isolated hospitals if ground routes are blocked.

Sensitivity: Baseline assumption: power is lost at 1–2 hospitals within 4–6 hours of ashfall; fuel convoys arrive within 6–8 hours. If simultaneous flashovers damage multiple substations and fuel is delayed 12+ hours, an estimated 4–6 hour outage could prevent 10–20 surgeries and cause 5–10 preventable patient deaths due to ventilator support loss. Cost of pre-positioned fuel reserves and utility coordination (estimated USD 5–10 million) prevents a multi-hospital crisis worth USD 50–100 million in emergency response and patient casualties.

Review conclusion

This plan is operationally ambitious and addresses core evacuation logistics (corridors, command, communications) effectively. However, three critical gaps threaten success: (1) the pre-authorized Scenario Beta VEI-7 trigger lacks a defined secondary-stage plan, leaving 100,000–500,000 additional evacuees without destinations and risking chaotic shadow evacuation that strands Zone One visitors; (2) responder staffing for 72-hour operations is underspecified (no concrete shift limits, relief depth or separate N95 count), risking coverage gaps at traffic and perimeter checkpoints during the evacuation peak; (3) ashfall forecasts and shelter siting are static, lacking real-time monitoring and relocation protocols when actual ashfall diverges from model predictions. These three issues are tightly coupled: inadequate Scenario Beta planning drives uncontrolled shadow evacuation that saturates corridors already threatened by single-point chokepoints; responder fatigue degrades traffic control during that chaos; and incorrect shelter siting forces emergency relocations during the same peak period. Immediate actions: (1) develop and pre-authorize Scenario Beta secondary-stage destinations and messaging by Month -2; (2) define responder exposure limits, relief staffing (30–50 person standby reserve) and separate N95 counts by Month -1; (3) establish continuous ashfall monitoring at shelters and pre-authorize 4-hour relocation protocols by Month -1. These actions cost an estimated USD 30–60 million but prevent a cascading 4–8 hour evacuation delay and 20–50 preventable deaths, with benefit-cost ratio >10:1.

Governance Audit

Audit - Corruption Risks

Audit - Misallocation Risks

Audit - Procedures

Audit - Transparency Measures

Internal Governance Bodies

1. Unified Command (UC) – Strategic Oversight Board

Rationale for Inclusion: A 72-hour window with 40% eruption probability (user constraint) and multi-state jurisdiction requires a single, pre-authorized strategic authority over zone expansion, escalation triggers, and inter-agency resource requests. The UC sits at FEMA Region VIII RRCC Denver and must coordinate Regions 8 and 10, three state governors, NPS, and the FAA to avoid authority gaps and command paralysis. Its primary role is authorizing the pre-written Scenario Beta VEI-7 trigger and issuing the 500 km evacuation order within 30 minutes of detection.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: The UC authorizes all strategic decisions with multi-state or federal implications: (1) evacuation zone expansion (Zone Zero to One to Beta); (2) authority transfer and boundary handoffs; (3) shelter-siting and relocation orders; (4) resource allocation above the operational management threshold (USD 10 million per decision, proposed); (5) any messaging reversal or escalation signal to the public. Decisions requiring consensus; in the event of tie or disagreement, the FEMA Region VIII IC has final authority, with a documented dissent from the disagreeing state recorded for accountability.

Decision Mechanism: The UC meets in continuous session (at least hourly briefings) during the 72-hour window and stands up as needed thereafter. Decisions on evacuation expansion and shelter siting are made by real-time consensus on the shared common operating picture, with decision triggers defined in the pre-written matrix (USGS indicators and PM10 thresholds). Tie-breaker: FEMA Region VIII IC, with one veto override right per state governor (may be used once to block a decision; once used, majority rule prevails thereafter). All decisions documented in real time in the shared log.

Meeting Cadence: Continuous operation during the 72-hour window (Month 0 = 2026-10-14, T+0 to T+72 h); hourly formal briefings at T+0, T+2, T+6, T+12, T+24, T+36, T+48, T+60, T+72 h, plus ad hoc calls on trigger events (Scenario Beta, shelter relocation, authority disputes). Post-window: weekly calls from Month 1 (2026-11-14) through Month 3 (2027-01-14 to 2027-01-14) to finalize MOUs, plan exercises and review after-action items.

Typical Agenda Items:

Escalation Path: The UC is the apex strategic authority for the evacuation response. Disagreements among members (states vs. federal, or state vs. state) are resolved by UC consensus; if consensus fails, the FEMA Region VIII IC decision prevails with documented dissent. Constitutional or legal challenges to the evacuation order (e.g., governor refuses to enforce a UC-issued relocation directive) are escalated to the U.S. Attorney's Office (Colorado District) and the White House Chief of Staff via the FEMA Regional Administrator. Resource allocation disputes exceeding the USD 10 million threshold or requiring supplemental declaration authority are escalated to the FEMA Deputy Administrator in Washington.

2. Forward Unified Command Element (FUCE) – Operational Management & Incident Control

Rationale for Inclusion: The Denver RRCC is 250+ km from the evacuation corridors (US-191, US-89, I-90), creating a decision latency of 2-4 hours for reroute orders and real-time resource dispatch. The FUCE co-locates the incident command team at Livingston or Bozeman, MT, within sight of the contraflow corridors and shelter sites, enabling rapid reroute directives, supply-chain troubleshooting and real-time response to corridor blockages or ashfall shifts. The FUCE operates under authority delegated by the UC and reports status hourly to the UC dashboard.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: The FUCE makes all operational decisions within the pre-authorized rules: (1) reroute orders and traffic-control post assignments (within total of 100-150 rangers and Guard personnel, proposed); (2) tow-team dispatch and the 45-minute blockage-diversion trigger; (3) water convoy priority and reserved-lane allocation on I-15; (4) shelter-relocation orders if PM10 exceeds thresholds (proposed); (5) responder shift assignments and relief activation. Decisions below the USD 10 million threshold do not require UC approval. Any decision that conflicts with an active UC order or requires deviation from the pre-written trigger matrix must escalate to the UC within 15 minutes.

Decision Mechanism: The FUCE operates on a continuous real-time basis, making decisions as conditions change (blockages, ashfall, supply delays). Standing orders and pre-authorized thresholds guide decisions without waiting for UC approval. Example: if Gallatin Canyon blockage lasts >45 minutes, overflow is automatically diverted to US-89 without FUCE debate. If PM10 exceeds 100 ug/m3 at Bozeman shelter, a backup-site relocation analysis is triggered within 30 minutes and a relocation order (if suitability threshold is met) is issued within 4 h. Tie-breaker: Operations Section Chief, with a dissent flag to the UC if the decision creates new risk.

Meeting Cadence: Continuous operation and real-time decision-making during the 72-hour window (T+0 to T+72 h). Formal briefing calls to the UC at T+0, T+2, T+6, T+12, T+24, T+36, T+48, T+60, T+72 h. Internal FUCE section briefings every 2 hours during peak evacuation (T+2 to T+8 h) to synchronize logistics, planning and communications. After-action reviews during Months 1-3 (2026-11-14 to 2027-01-14).

Typical Agenda Items:

Escalation Path: Operational decisions stay within the FUCE unless they violate pre-authorized thresholds or conflict with UC orders. Any request for additional Guard personnel, change to the pre-written trigger matrix, or decision to revise public messaging escalates to the UC. Resource requests exceeding available stock (e.g., need for additional N95 from the supplemental reserve at Billings) escalate to the Unified Command Logistics Officer. Responder casualties or critical incidents escalate immediately to the UC and to the responsible state's emergency manager.

3. Escalation & Scenario Beta Decision Cell – Specialized Advisory (Volcanology & Triggering Authority)

Rationale for Inclusion: The 72-hour window carries a 40% VEI-6+ eruption probability and a pre-authorized VEI-7 trigger matrix that authorizes the UC to order a 500 km radius evacuation immediately without further deliberation. However, the scientific indicators (USGS uplift rate, seismic magnitude, gas flux) that define the trigger must be continuously monitored and interpreted in real time, requiring dedicated expert authority separate from operational command. This cell owns the trigger-matrix refinement, indicator interpretation, and the real-time decision to declare that the threshold has been crossed. The cell's recommendation is binding on the UC unless the UC explicitly overrides it (a rare event, since the matrix is pre-authorized).

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: The cell's role is scientific interpretation and trigger declaration, not policy or resource decisions. The cell declares whether the pre-written trigger threshold has been crossed. This declaration is binding on the UC (the UC does not second-guess the scientific finding), unless the UC explicitly overrides it on policy grounds (e.g., national-security concerns). The cell does not have authority to modify the trigger matrix after T+3 h; any matrix changes must be approved by the UC. The cell's recommendation on marginal triggers is advisory; the UC makes the final call to order Scenario Beta.

Decision Mechanism: Real-time monitoring of USGS feeds and automated alerts when an indicator approaches the threshold (within 20% of the trigger value). When any indicator crosses the threshold, the cell convenes immediately (within 5 min) to verify the data and declare the crossing. If data are ambiguous or disputed among cell members, a simple majority vote determines the declaration (two out of three USGS leads vote); if still disputed, the USGS Disaster Assistance Program lead has final authority. The UC is notified within 15 min of any threshold crossing or declaration.

Meeting Cadence: Continuous real-time monitoring during the 72-hour window. Formal briefings to the UC every 6 hours (T+0, T+6, T+12, T+18, T+24, T+30, T+36, T+42, T+48, T+54, T+60, T+66, T+72). Ad hoc calls whenever an indicator crosses 80% of the trigger threshold (a warning). Post-window: joint after-action review with the UC and state emergency managers by Month 2 (2026-12-14).

Typical Agenda Items:

Escalation Path: The cell's trigger declaration goes directly to the UC via the UC Liaison and the shared common operating picture. If the cell declares trigger crossing and the UC does not order Scenario Beta within 30 min, the cell has the right to escalate the non-response to the White House Situation Room via the FEMA Regional Administrator. Conversely, if the UC orders Scenario Beta without a cell trigger declaration, this is logged as a policy override and reported in the post-event after-action review.

4. Responder Health & Fatigue Management Board – Specialized Advisory (Occupational Safety & Exposure Limits)

Rationale for Inclusion: The 72-hour evacuation window requires continuous staffing of traffic-control checkpoints, perimeter gates and backcountry sweeps by rangers, highway patrol and Guard personnel exposed to ashfall, tremor hazards and heat stress. A formal board with authority to enforce exposure limits and manage relief cycles protects responders from entrapment and respiratory injury while maintaining staffing continuity. The board monitors shift logs, triggers relief rotation, and has the power to withdraw responders from ash-exposed posts if limits are breached, directly affecting traffic throughput and evacuation speed. This board is necessary to balance responder safety against the evacuation deadline.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: The board has binding authority to: (1) approve or modify shift schedules and rest cycles; (2) declare any post as 'understaffed' if coverage falls below 50% due to exposure limits (proposed threshold); (3) trigger activation of the standby reserve for deployment within 4 h; (4) withdraw any individual responder from ash-exposed duty if exposure limits are breached or fatigue risk is critical; (5) recommend to the FUCE that a checkpoint be temporarily closed or consolidated with another if staffing cannot be sustained. The board does not have authority to extend exposure limits beyond the pre-written thresholds (6 h shift, 18 h withdrawal) without UC approval.

Decision Mechanism: The board meets every 6 hours during the 72-hour window (at T+0, T+6, T+12, T+18, T+24, T+30, T+36, T+42, T+48, T+54, T+60, T+66, T+72 h) to review shift logs, assess staffing adequacy and approve the next day's schedule. Decisions are made by consensus among the NPS, state and Guard commanders; if consensus fails (e.g., a state patrol commander refuses to remove an exhausted trooper from duty), the NPS Chief Ranger has final authority, with a dissent recorded for the UC. Emergency decisions (e.g., immediate withdrawal of a responder showing acute respiratory distress) are made by the board chair within 5 min and reported to the FUCE.

Meeting Cadence: Continuous 24/7 operation during the 72-hour window with formal board meetings every 6 hours (T+0, T+6, T+12 h, etc.). Ad hoc calls when a checkpoint reports staffing below 50% or a responder requests emergency relief. Daily fatigue-risk assessments at T+24, T+48 and T+72 h. Post-event responder health screening and evaluation by Month 2 (2026-12-14).

Typical Agenda Items:

Escalation Path: Decisions about responder withdrawal or staffing shortages escalate to the FUCE Operations Section Chief, who adjusts traffic-control post assignments or consolidates posts if necessary. If staffing demands consistently exceed the available responder pool and cannot be met by the standby reserve, the board chair escalates a request for out-of-state Guard to the UC. Critical responder health emergencies (respiratory distress requiring hospitalization, heat-related collapse) are reported immediately to the nearest receiving hospital and to the UC. Any responder casualty during the event is reported to the UC and to the respective state emergency manager within 1 hour.

5. Authority & Jurisdictional Coordination Cell – Specialized Advisory (Command Clarity & Multi-State Protocol)

Rationale for Inclusion: The evacuation crosses jurisdictional boundaries between NPS (federal land), Montana, Wyoming and Idaho (state highways and communities), and FEMA Regions 8 (Denver) and 10 (Seattle), creating authority gaps and decision latency. The authority transfer is specified in writing (park boundary at each gate; NPS to state handoff), but contraflow traffic does not stop at boundaries, so vehicles and responders cross jurisdictions mid-evacuation without a clear point of responsibility handoff. A dedicated cell, co-located at the forward element with real-time links to each state's on-scene commander, owns the boundary coordination, pre-authorized reroute authority, and resolution of any NPS-state or Region 8/10 disputes. This cell prevents the 15–45 minute delays in reroute decisions that could cascade into a 500–1,000 vehicle backup.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: The cell has binding authority to: (1) authorize state reroutes at any time without UC approval (pre-authorized standing order); (2) resolve NPS-state disputes on the fly within 30 min (Boundary Coordination Officer decision); (3) activate the Region 10 liaison's mutual-aid requests for Idaho resources without waiting for UC approval if request is below USD 5 million (proposed threshold); (4) approve helicopter medevac exceptions within the pre-authorized criteria set by the UC and FAA. The cell may not modify the written authority-transfer protocol after T+0 or unilaterally revoke a pre-authorized reroute; any such changes must escalate to the UC.

Decision Mechanism: Standing orders and pre-written authority transfers define the default decision rules, so most situations are handled without deliberation. Real-time problem-solving through a dedicated conference line: if a reroute is needed, the state commander requests it, the Boundary Coordination Officer verifies it against the pre-written matrix and authorizes it within 5 min. If an NPS ranger disputes the reroute, the matter is elevated to the Boundary Coordination Officer and the forward-element Operations Chief within 30 min for quick resolution. Tie-breaker: Boundary Coordination Officer, with escalation to the FUCE Operations Chief if the dispute creates conflicting orders.

Meeting Cadence: Continuous operation and real-time coordination during the 72-hour window via a standing conference line connecting all members. Formal briefings to the UC every 6 hours as part of the UC briefing schedule. Post-event: multi-state debrief by Month 2 (2026-12-14) with Montana, Wyoming and Idaho emergency managers to review authority handoff execution and identify improvements for future events.

Typical Agenda Items:

Escalation Path: Real-time disputes between NPS and a state are mediated by the Boundary Coordination Officer (on the standing conference line) within 30 min. If the Boundary Coordination Officer and state/NPS commanders cannot reach agreement, the matter escalates to the FUCE Operations Chief, who makes a binding decision and notifies the UC. If a state refuses to comply with a UC-authorized evacuation order, the matter escalates to the UC, which may seek legal counsel and White House involvement. Any FAA denial of a medevac exception request escalates to the UC, which may request White House or Department of Defense intervention.

6. Shelter Siting & Air-Quality Assurance Panel – Specialized Advisory (Environmental Monitoring & Dynamic Relocation Authority)

Rationale for Inclusion: The plan designates Bozeman and Idaho Falls as reception centers but acknowledges that ashfall forecasts are uncertain by 100+ km, so final shelter locations are selected at T+6 h based on the latest NOAA/USGS plume forecast. Actual ashfall may exceed model predictions by 2–3x, rendering the selected sites unsuitable and requiring emergency relocation of 10,000–15,000 evacuees within 4 h. This specialized panel owns real-time PM10 and ashfall monitoring at all shelter sites, the suitability assessment for shelter relocations, and the authority to order a relocation if thresholds are exceeded. The panel prevents the scenario in which evacuees are sheltered in heavy ash, developing respiratory distress and requiring a chaotic secondary move.

Responsibilities:

Initial Setup Actions:

Membership:

Decision Rights: The panel has advisory authority on shelter suitability (recommendation to FUCE) and binding authority to: (1) declare that PM10 thresholds have been exceeded at a shelter site; (2) trigger the start of a relocation analysis; (3) confirm that a ranked backup shelter is suitable for occupancy and relocation can proceed; (4) recommend an increase in N95 distribution from the supplemental reserve. The final relocation order is issued by the FUCE Operations Chief, not the panel, but the panel's threshold declaration is binding and cannot be overridden by the FUCE without UC approval.

Decision Mechanism: Automated threshold alerts: when hourly PM10 readings exceed the 50 ug/m3 forecast-update threshold, an alert is triggered and the panel convenes to update the plume forecast and assess suitability. When PM10 exceeds the 100 ug/m3 suitability-review threshold (proposed), a rapid relocation analysis is triggered. The panel (NOAA, USGS and EPA members) votes on whether the current site is still safe for occupancy; a 2-out-of-3 vote determines the recommendation. The FUCE Operations Chief then decides within 1 h whether to order relocation. If the FUCE Operations Chief overrides a panel suitability finding, this override is escalated to the UC.

Meeting Cadence: Continuous real-time monitoring with automated alerts when thresholds are approached. Formal briefings to the FUCE Operations Chief every 6 hours (at the standard FUCE briefing times: T+0, T+6, T+12, T+18, T+24, etc.). Ad hoc emergency meetings when PM10 exceeds the forecast-update threshold (50 ug/m3 proposed). Post-event: joint evaluation with USGS, NOAA and EPA by Month 2 (2026-12-14) to assess forecast accuracy and identify sensor improvements.

Typical Agenda Items:

Escalation Path: Suitability assessments and PM10 threshold declarations go directly to the FUCE Operations Chief, who has 1 h to decide on relocation. If the FUCE Operations Chief does not order relocation within 1 h of a panel finding that PM10 exceeds the 100 ug/m3 threshold (proposed), the panel has the right to escalate the non-response to the UC. Disputes among panel members (e.g., NOAA and USGS disagree on the forecast) are resolved by majority vote; if 2-out-of-3 cannot agree, the matter escalates to the UC with both positions documented. Critical relocation logistics failures (buses unavailable, transport gridlock) escalate to the FUCE Logistics Chief and then to the UC.

Governance Implementation Plan

1. Project Sponsor (FEMA Regional Administrator, Region VIII) and NPS Director jointly issue a written decision memo designating the Yellowstone Caldera eruption response as a 'pre-event emergency planning initiative' and authorizing the formation of a Unified Command structure. The memo names the FEMA Region VIII IC as the Unified Command chair and directs all agencies to cooperate on governance setup by Month 0 (2026-10-14). This memo serves as the legal authority to form all downstream governance bodies.

Responsible Body/Role: FEMA Regional Administrator (Region VIII) and NPS Director (joint decision authority)

Suggested Timeframe: Month -1

Key Outputs/Deliverables:

Dependencies:

2. FEMA Region VIII Incident Commander (designated UC Chair) or designee drafts a written Terms of Reference (ToR) for the Unified Command, defining its strategic authority, decision rights (zone expansion, escalation triggers, resource allocation >USD 10M), meeting cadence (continuous during 72-hour window, hourly briefings at T+0/2/6/12/24/36/48/60/72h), membership (FEMA Region VIII IC, Region 10 liaison, NPS IC, three state emergency managers/governors' designees, USGS volcanologist, NOAA forecast lead) and escalation path (tie-breaker: FEMA Region VIII IC; constitutional/legal disputes to U.S. Attorney and White House). The draft establishes the UC as a standing body that activates at T+0 and operates continuously through T+72h.

Responsible Body/Role: FEMA Region VIII Incident Commander (future UC Chair) with input from NPS, state emergency management offices and FEMA Region 10

Suggested Timeframe: Month -1, Week 2

Key Outputs/Deliverables:

Dependencies:

3. FEMA Region VIII Incident Commander circulates the draft UC Terms of Reference to all nominated members (NPS Director, three state emergency managers, FEMA Region 10 liaison, USGS and NOAA leads) for review and feedback. A 1-week review window is provided. Feedback is consolidated into a summary document and shared back to all reviewers, along with a revision tracker.

Responsible Body/Role: FEMA Region VIII Incident Commander (document circulation and feedback consolidation)

Suggested Timeframe: Month -1, Week 3

Key Outputs/Deliverables:

Dependencies:

4. FEMA Region VIII Incident Commander revises the UC ToR based on consolidated feedback and issues UC ToR v1.0 (final). Key revisions may include: (1) clarification of Region 10 liaison's voting rights on Idaho-specific decisions; (2) formalizing the 'veto override' protocol (each state governor has one veto; majority rule after override used); (3) defining the shared common operating picture (COP) digital dashboard and update frequency (hourly). The final ToR is signed by the FEMA Region VIII IC and submitted to the FEMA Regional Administrator for official approval.

Responsible Body/Role: FEMA Region VIII Incident Commander with final sign-off from FEMA Regional Administrator

Suggested Timeframe: Month -1, Week 4

Key Outputs/Deliverables:

Dependencies:

5. FEMA Region VIII Incident Commander issues formal written appointment letters to each nominated member of the Unified Command, confirming their role, decision rights and the time commitment (continuous operation from T+0 to T+72h, then ongoing Months 1-3 = 2026-11-14 to 2027-01-14 for MOUs and exercises). Letters are sent to the home agencies (NPS, three states, FEMA Region 10, USGS, NOAA) with a request for verbal confirmation of acceptance within 48 hours. Any rejections or substitute nominees are flagged for resolution by the FEMA Regional Administrator.

Responsible Body/Role: FEMA Region VIII Incident Commander (letter issuance)

Suggested Timeframe: Month 0 (2026-10-14), Week 1 (Days -7 to 0 before T+0 on 2026-10-14)

Key Outputs/Deliverables:

Dependencies:

6. FEMA Region VIII Incident Commander or designee holds a pre-event UC 'Orientation and Authority Briefing' meeting (in-person or virtual hybrid) for all confirmed UC members. The briefing covers: (1) the pre-authorized USGS trigger matrix for Scenario Beta (VEI-7 indicators, thresholds to be finalized by T+3h); (2) the three-exit contraflow plan and the 45-minute blockage-diversion rule (proposed threshold); (3) the Authority & Jurisdictional Cell's role in the NPS-to-state handoff; (4) the COP digital dashboard demo and how to access it; (5) the continuous briefing schedule (T+0, T+2, T+6, T+12, T+24, etc.). A Q&A session addresses any ambiguities in decision rights or escalation paths. All attendees sign an acknowledgment of understanding.

Responsible Body/Role: FEMA Region VIII Incident Commander (host and facilitator) with support from NPS IC and state emergency managers

Suggested Timeframe: Month 0 (2026-10-14), Week 2 (Days -7 to -1 before T+0)

Key Outputs/Deliverables:

Dependencies:

7. FEMA Region VIII Incident Commander formally activates the Unified Command at T+0 (2026-10-14, coinciding with the eruption alert and evacuation order from the project sponsor). All UC members report to their designated seats at the FEMA Region VIII RRCC in Denver (remote participation accepted for state emergency managers if in-person travel is not feasible). The UC chair convenes the first formal briefing, reviews the COP dashboard status (expected: ~0 evacuees out at T+0, all exit corridors open, ashfall not yet detected), and confirms that all five specialized advisory bodies (Escalation Cell, FUCE, Responder Health Board, Authority Cell, Shelter Siting Panel) are standing by and ready to accept delegated authority from the UC.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC)

Suggested Timeframe: Month 0 (2026-10-14), Hour 0 (2026-10-14, T+0)

Key Outputs/Deliverables:

Dependencies:

8. Forward Unified Command Element (FUCE) senior staff (Operations Chief, Logistics Chief, Planning Chief, Safety Officer, Boundary Coordination Officer, Guard Signal Officer and USGS/NOAA liaisons) meet at the forward command element location (Livingston, MT, or alternate Bozeman) by T+1 hour to formally establish the FUCE as an operational entity under the UC. The Operations Chief briefs the team on the delegated authority (traffic management, tow dispatch, water convoy routing, shelter relocation triggers within pre-authorized rules) and confirms that communication links to the UC in Denver are live and tested. All FUCE members acknowledge their roles and confirm readiness to execute continuous operations until T+72h.

Responsible Body/Role: FUCE Operations Section Chief (incident commander for forward operations)

Suggested Timeframe: Month 0 (2026-10-14), Hours 0–1 (T+0 to T+1)

Key Outputs/Deliverables:

Dependencies:

9. Escalation & Scenario Beta Decision Cell (USGS Volcano Disaster Assistance Program lead, USGS seismologist, USGS magma modeler, NOAA forecast lead, and UC liaison) convene at T+0 at either the FUCE location (Livingston) or the UC location (Denver RRCC), as coordinated. The cell chair (USGS Disaster Assistance Program lead) reviews the pre-authorized USGS trigger matrix (preliminary, to be finalized by T+3h using real-time USGS data) and establishes live monitoring of USGS seismic, GPS and gas networks. The cell confirms that data feeds are arriving in real time and that automated threshold alerts are armed. The cell also briefs the UC liaison on the status of each eruption indicator relative to the Scenario Beta trigger threshold.

Responsible Body/Role: Escalation & Scenario Beta Decision Cell (led by USGS Volcano Disaster Assistance Program lead)

Suggested Timeframe: Month 0 (2026-10-14), Hour 0 (T+0)

Key Outputs/Deliverables:

Dependencies:

10. Responder Health & Fatigue Management Board (NPS Chief Ranger, Forward Command Safety Officer, state highway patrol commanders for MT/WY/ID, National Guard unit commander, and medical officer from the nearest receiving hospital) convene at T+0 at the FUCE or a nearby regional coordination center. The board chair (NPS Chief Ranger) reviews the pre-written exposure limits (6-hour shifts at ash-exposed posts, 2-hour rest with N95 replacement, 18-hour withdrawal threshold) and confirms that all assigned responders have been briefed on these limits and on the fatigue-hotline contact information. The board also confirms that the 30–50 person standby reserve is stationed outside the ash zone and ready to deploy within 4 hours if staffing falls below 50% at any checkpoint.

Responsible Body/Role: Responder Health & Fatigue Management Board (led by NPS Chief Ranger)

Suggested Timeframe: Month 0 (2026-10-14), Hour 0 (T+0)

Key Outputs/Deliverables:

Dependencies:

11. Authority & Jurisdictional Coordination Cell (Boundary Coordination Officer at the FUCE, NPS IC or delegated zone commander, MT/WY/ID highway patrol and state police on-scene commanders, FEMA Region 10 liaison, and FAA representative) convene at T+0 to formally establish the cell and activate the authority-transfer protocols. The Boundary Coordination Officer briefs all members on the pre-written NPS-to-state handoff protocol at each park exit gate (West, North, East Entrance), confirming that state on-scene commanders have been pre-authorized to issue reroutes without park ranger approval (standing order, pre-signed by the UC chair). The Region 10 liaison confirms that FEMA Region 10 mutual-aid arrangements with Boise and Pocatello emergency management offices are documented in a standing MOU to be finalized by Month 1 (2026-11-14).

Responsible Body/Role: Authority & Jurisdictional Coordination Cell (led by Boundary Coordination Officer at FUCE)

Suggested Timeframe: Month 0 (2026-10-14), Hour 0 (T+0)

Key Outputs/Deliverables:

Dependencies:

12. Shelter Siting & Air-Quality Assurance Panel (NOAA ashfall/air-quality forecast lead, USGS geochemist, EPA air-quality specialist, FUCE Planning Chief, and Shelter Operations Coordinator) convene at T+0 at the FUCE location. The panel chair (NOAA lead) confirms that real-time PM10 and ashfall-depth monitoring sensors are deployed at the forward element (Livingston) and at the three primary shelter candidates (Bozeman, Idaho Falls, and a third site to be determined based on the T+6 forecast). The panel reviews the pre-surveyed list of 8–10 backup candidate shelters (ranked by distance and upwind position) and confirms that transport agreements (buses, drivers) are in place for emergency relocation of 10,000–15,000 evacuees within 4 hours.

Responsible Body/Role: Shelter Siting & Air-Quality Assurance Panel (led by NOAA ashfall/air-quality forecast lead)

Suggested Timeframe: Month 0 (2026-10-14), Hour 0 (T+0)

Key Outputs/Deliverables:

Dependencies:

13. UC holds the formal first Unified Command briefing at T+0, with participation by all six UC members (or their confirmed delegates) and representatives from all five specialized advisory bodies (Escalation Cell, FUCE, Responder Health Board, Authority Cell, Shelter Siting Panel). The agenda includes: (1) status of evacuation corridors and gate operations (target 0 departures at T+0, ramping to flow rate of ~2,000 vehicles/hour by T+1); (2) summary of USGS eruption indicators and distance from the Scenario Beta trigger (provided by Escalation Cell); (3) current ashfall forecast and PM10 readings (provided by Shelter Siting Panel); (4) readiness status of water convoys (target dispatch from Salt Lake City by T+12h) and supply logistics (provided by FUCE Logistics Chief); (5) responder staffing and exposure-limit compliance (provided by Responder Health Board); (6) authority-transfer protocols and any initial boundary-coordination issues (provided by Authority Cell). A shared common operating picture (COP) digital dashboard is displayed and updated continuously during the briefing, showing all metrics hourly.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC, chair)

Suggested Timeframe: Month 0 (2026-10-14), Hour 0–2 (T+0 to T+2)

Key Outputs/Deliverables:

Dependencies:

14. USGS Volcano Disaster Assistance Program lead (Escalation Cell chair) completes the refinement of the pre-authorized USGS trigger matrix using the latest real-time eruption-monitoring data (seismic swarm, GPS uplift, gas emissions, magma-depth models) available at T+3h. The cell finalizes the specific numerical thresholds for: (1) uplift rate (cm/h or cm/6h intervals); (2) seismic-swarm magnitude and frequency triggers; (3) gas-flux thresholds (SO2, CO2); (4) estimated magma depth and ascent rate indicating VEI-7 probability ≥20% in the remaining window (placeholder; USGS to provide exact formula). The finalized matrix is issued in writing and distributed to the UC, FUCE, and all state emergency managers. A dashboard showing the current status of each indicator relative to the finalized trigger thresholds is published and made available to the media and the public to ensure credibility and transparency.

Responsible Body/Role: Escalation & Scenario Beta Decision Cell (led by USGS Volcano Disaster Assistance Program lead)

Suggested Timeframe: Month 0 (2026-10-14), Hour 3 (T+3h)

Key Outputs/Deliverables:

Dependencies:

15. FUCE Operations Chief and FEMA logistics coordinator confirm that contraflow traffic-control operations are active on all three exit corridors (US-20/US-191 via Gallatin Canyon to West Yellowstone, US-89 via Gardiner, US-14/16/20 toward Cody) by T+1 hour. Traffic-control posts are staffed at each corridor (rangers, highway patrol, and National Guard at key junctions and bottlenecks). At least two tow and rockfall-clearance teams are deployed to pre-positioned stations (Mammoth and Spanish Creek area) and confirmed ready to reach any Gallatin Canyon blockage within 15 minutes of dispatch. Guard signal teams with satellite phones, portable repeaters and generator fuel are deployed to each control point and the forward element by T+1 hour. IPAWS (Integrated Public Alert and Warning System) messages in English and five languages (Spanish, Japanese, German, Mandarin, French) are issued to the public, instructing drivers to use designated exit corridors and to follow ranger/patrol instructions.

Responsible Body/Role: FUCE Operations Section Chief and Logistics Chief

Suggested Timeframe: Month 0 (2026-10-14), Hour 1 (T+1h)

Key Outputs/Deliverables:

Dependencies:

16. Shelter Siting Panel conducts the formal selection of final shelter sites at T+6 hours, using the latest NOAA/USGS plume forecast and real-time PM10 monitoring data. The panel reviews the ashfall-extent forecast, wind direction and ash-concentration projections for the next 72 hours. Based on this forecast, the panel recommends primary and backup shelter sites that lie outside or upwind of the modeled ash footprint. The FUCE Operations Chief formally approves the shelter-site selections and issues assignments to the Bozeman and Idaho Falls shelters (or alternates if the forecast indicates those sites are unsuitable). Buses and intake staff are dispatched to the selected sites to prepare for receiving the first evacuees (expected arrival T+6 to T+12h).

Responsible Body/Role: Shelter Siting & Air-Quality Assurance Panel (led by NOAA forecast lead) with final approval by FUCE Operations Chief

Suggested Timeframe: Month 0 (2026-10-14), Hour 6 (T+6h)

Key Outputs/Deliverables:

Dependencies:

17. UC issues a milestone assessment at T+6 hours, checking against the Phase 1 'go/no-go' gate: at least 98% of the 35,800 Zone Zero evacuees (about 35,084) have been counted as having exited through the three corridors (West, North, East gates). Real-time exit counts from each state patrol and NPS checkpoint are consolidated in the COP dashboard. If the gate is met, the UC documents clearance and advises that Zone Zero is essentially cleared, with remaining stragglers (estimated 200–400 backcountry hikers and permit holders) under active ranger sweep and accounting. If the gate is not met (e.g., due to a blockage that delayed departures), the UC convenes an emergency reroute decision with the FUCE and Authority Cell to redirect any remaining vehicles and assess whether the 72-hour window timeline needs adjustment.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC) with real-time data from FUCE and state checkpoints

Suggested Timeframe: Month 0 (2026-10-14), Hour 6 (T+6h)

Key Outputs/Deliverables:

Dependencies:

18. UC issues a formal public statement and IPAWS alert at T+6 hours, confirming that Zone Zero (park interior) has been cleared or is nearly cleared, and that the evacuation is transitioning to Phase 2: expansion of Zone One (100 km radius including West Yellowstone, Gardiner and Cody communities). The statement reiterates the pre-authorized USGS trigger matrix and explains that if the triggers for Scenario Beta (VEI-7) are detected, a 500 km evacuation order will be issued immediately without further deliberation. The statement also confirms current shelter locations (Bozeman, Idaho Falls and any third site), water convoy dispatch status (target T+12h from Salt Lake City), and the N95 pre-staging locations. This public statement is critical for sustaining public trust and explaining the escalation logic before Scenario Beta messaging may become necessary.

Responsible Body/Role: Unified Command (FEMA Region VIII IC) in coordination with NOAA Public Affairs and NPS Communications

Suggested Timeframe: Month 0 (2026-10-14), Hour 6 (T+6h)

Key Outputs/Deliverables:

Dependencies:

19. FEMA Region VIII IC (UC chair) or designee issues written pre-authorization letters to each of the three state governors (Montana, Wyoming, Idaho), requesting verbal confirmation of their authorization of the UC's Zone One and Scenario Beta (500 km) evacuation orders. The letters explain: (1) the current status of the evacuation (Phase 1 complete, Zone One now being evacuated); (2) the pre-written USGS trigger matrix and how Scenario Beta will be triggered if thresholds are crossed; (3) the request for each governor to confirm that they accept the UC's authority to issue and enforce these orders on state highways and in state communities; (4) the expectation that formal Memoranda of Understanding (MOUs) and EMAC mutual-aid agreements will be signed by Month 1 (2026-11-14). Verbal confirmations are recorded and documented in the UC decision log.

Responsible Body/Role: FEMA Region VIII IC (UC chair) on behalf of the Unified Command

Suggested Timeframe: Month 0 (2026-10-14), Hour 6 (T+6h)

Key Outputs/Deliverables:

Dependencies:

20. FUCE Logistics Chief confirms that bottled-water convoys from Salt Lake City distribution centers have been dispatched by T+12 hours (per the T+12h target), using National Guard escorts and reserved lanes on I-15 northbound (proposed dedicated 'supply-surge' lane). The Logistics Chief tracks the real-time location of each convoy via GPS and reports arrival estimates at Bozeman and Idaho Falls shelters. If the forecast arrival time exceeds T+24h (the Phase 2 gate deadline), the Logistics Chief alerts the FUCE Operations Chief and the UC, triggering contingency actions: (1) advance dispatch of supplemental water from forward depots in Bozeman, Billings and Idaho Falls (pre-positioned at T-48 hours before the event); (2) activation of the supplemental N95 reserve at Billings or Salt Lake City if ashfall is heavier than modeled.

Responsible Body/Role: FUCE Logistics Section Chief

Suggested Timeframe: Month 0 (2026-10-14), Hour 12 (T+12h)

Key Outputs/Deliverables:

Dependencies:

21. Authority Cell conducts a formal review of authority-transfer and jurisdictional-coordination execution at T+12 hours. The Boundary Coordination Officer consolidates reports from all three state on-scene commanders (MT at West/Gardiner, WY at Cody, ID at Idaho Falls) documenting: (1) cumulative vehicle and evacuee counts that have crossed from NPS to state control at each boundary checkpoint; (2) any reroutes or traffic-control adjustments issued by state commanders (all within pre-authorized standing orders); (3) any disputes or coordination gaps that required escalation to the FUCE or UC. The cell issues a brief status report to the UC confirming that the authority transfer is executing smoothly or flagging any issues requiring UC decision-making.

Responsible Body/Role: Authority & Jurisdictional Coordination Cell (led by Boundary Coordination Officer)

Suggested Timeframe: Month 0 (2026-10-14), Hour 12 (T+12h)

Key Outputs/Deliverables:

Dependencies:

22. Responder Health Board conducts a mandatory 6-hour fatigue-risk assessment at T+12 hours, analyzing cumulative hours worked by all assigned responders (rangers, patrol, Guard at traffic-control and perimeter posts) since T+0. The board reviews shift logs and identifies any responders approaching or exceeding the 18-hour withdrawal threshold (proposed threshold). Any responders exceeding 6 hours at ash-exposed posts without a 2-hour rest break are flagged for immediate rotation. The board also tallies N95 mask usage and confirms that inventory is adequate for the next 12 hours. If usage is exceeding expectations (e.g., heavy ashfall causing faster mask clogging), the board signals the FUCE Logistics Chief to activate supplemental responder N95 reserves.

Responsible Body/Role: Responder Health & Fatigue Management Board (led by NPS Chief Ranger)

Suggested Timeframe: Month 0 (2026-10-14), Hour 12 (T+12h)

Key Outputs/Deliverables:

Dependencies:

23. Escalation Cell issues an Escalation Readiness Assessment at T+12 hours, reporting the current status of each USGS eruption indicator (uplift rate, seismic magnitude, gas flux, magma depth) relative to the finalized Scenario Beta trigger thresholds. The cell states how far (percentage or margin) each indicator is from the trigger and estimates the time to trigger if current trends continue. The cell also reviews the current ashfall forecast and PM10 readings, noting any changes from the T+6h forecast. This briefing is delivered to the UC and published in a summary format suitable for media and public consumption, maintaining transparency about the eruption state and the likelihood of Scenario Beta escalation.

Responsible Body/Role: Escalation & Scenario Beta Decision Cell (led by USGS Volcano Disaster Assistance Program lead)

Suggested Timeframe: Month 0 (2026-10-14), Hour 12 (T+12h)

Key Outputs/Deliverables:

Dependencies:

24. UC holds the T+12 hour formal briefing, consolidating status reports from the FUCE, all five specialized advisory bodies, and state on-scene commanders. The agenda includes: (1) Zone One evacuation progress (target: evacuees flowing into Bozeman, Idaho Falls and third shelter site; intake and registration ongoing); (2) USGS indicator status and Scenario Beta readiness; (3) ashfall forecast and shelter-suitability status (PM10 readings, any triggers for relocation analysis); (4) water convoy ETA and supply-logistics status; (5) responder fatigue and staffing continuity; (6) authority-transfer execution and any jurisdictional disputes. The UC documents any mid-course corrections needed (e.g., reroutes, shelter relocation preparations, additional Guard deployment) and issues updated orders to the FUCE and state commanders.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC, chair)

Suggested Timeframe: Month 0 (2026-10-14), Hour 12 (T+12h)

Key Outputs/Deliverables:

Dependencies:

25. FEMA Region VIII IC (UC chair), on behalf of the Unified Command, issues a written request to the three state governors (MT, WY, ID) and to FEMA Region 10 (Seattle) requesting formal signing of Memoranda of Understanding (MOUs) and EMAC mutual-aid agreements by Month 1 (2026-11-14). The request includes draft MOU language covering: (1) each state's acceptance of the UC's authority to issue Zone One and Scenario Beta evacuation orders; (2) commitment to enforce unified evacuation messaging and shelter assignments on state roads and in state communities; (3) provision of state resources (highway patrol, National Guard) to support contraflow and perimeter operations; (4) mutual-aid resource sharing (water, fuel, medical) among the three states and with FEMA Regions 8 and 10; (5) post-event after-action-report and exercise planning for Months 1–3 (2026-11-14 to 2027-01-14). This request initiates a formal negotiation period that culminates in signed agreements by Month 1 (2026-11-14).

Responsible Body/Role: FEMA Region VIII IC (UC chair) on behalf of the Unified Command

Suggested Timeframe: Month 0 (2026-10-14), Hours 24–36 (T+24h to T+36h)

Key Outputs/Deliverables:

Dependencies:

26. UC issues a milestone assessment at T+24 hours, checking against the Phase 2 'go/no-go' gate: at least 95% of registered Zone One residents (West Yellowstone, Gardiner, Cody communities) have evacuated or sheltered in place, perimeters around evacuated towns are staffed and secured by National Guard to prevent looting, and a preliminary Scenario Beta interim-destination list (ranked hub list outside the 500 km ring) has been issued. The UC consolidates reports from the FUCE, state on-scene commanders and the Shelter Siting Panel, documenting evacuation completeness, perimeter-staffing status and shelter-intake progress. If the gate is met, the UC documents successful completion of Phase 2 and advises that the response has transitioned to the 'sustained operations' phase (T+24h to T+72h), during which the focus shifts to supply continuity, ashfall management and Scenario Beta readiness.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC) with data from FUCE, state commanders and advisory bodies

Suggested Timeframe: Month 0 (2026-10-14), Hour 24 (T+24h)

Key Outputs/Deliverables:

Dependencies:

27. Shelter Siting Panel conducts formal suitability assessments at T+24, T+36, T+48, T+60 and T+72 hours, comparing real-time PM10 readings and ashfall forecasts at all active shelter sites against the established thresholds (50 ug/m³ for forecast-update trigger, 100 ug/m³ for suitability-review trigger). If any site exceeds the suitability threshold, the panel initiates a rapid relocation analysis (decision within 30 minutes proposed threshold) and recommends a backup site. A relocation order (issued by FUCE Operations Chief within 4 hours of threshold exceedance proposed threshold) specifies the new shelter site, transport routing and pickup schedule. The panel tracks all relocation logistics and confirms arrival of evacuees at the new site. This continuous monitoring and rapid-response protocol prevents evacuees from being sheltered in heavy ashfall and developing respiratory distress.

Responsible Body/Role: Shelter Siting & Air-Quality Assurance Panel (led by NOAA forecast lead) with execution by FUCE Operations Chief

Suggested Timeframe: Month 0 (2026-10-14), Hours 24, 36, 48, 60, 72 (T+24h, T+36h, T+48h, T+60h, T+72h)

Key Outputs/Deliverables:

Dependencies:

28. UC holds continuous hourly briefings (in addition to the scheduled T+0, T+2, T+6, T+12, T+24, T+36, T+48, T+60, T+72h formal briefings) during the 72-hour window, with rapid-update reports from the FUCE on any critical changes: corridor blockages, major weather shifts, ashfall intensity changes, supply delays or any USGS eruption-indicator changes approaching the Scenario Beta trigger threshold. These rapid-update calls (conducted via secure conference line) allow the UC to make real-time tactical decisions (reroutes, shelter relocations, supply contingencies) without waiting for the formal scheduled briefing. All UC decisions made between scheduled briefings are logged in the UC decision log with full documentation and time stamps.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC, chair) with participation by FUCE Operations Chief and key advisory-body leads as needed

Suggested Timeframe: Month 0 (2026-10-14), Hours 0–72 (T+0 to T+72h), continuous as needed between scheduled briefings

Key Outputs/Deliverables:

Dependencies:

29. Escalation Cell continuously monitors real-time USGS eruption indicators throughout the 72-hour window and immediately alerts the UC if any indicator crosses 80% of the Scenario Beta trigger threshold (a warning threshold), triggering a pre-brief for the UC. If any indicator crosses the full trigger threshold, the Escalation Cell convenes an immediate 5-minute verification meeting, confirms the threshold crossing, and issues a formal Trigger Crossing Declaration to the UC within 15 minutes. The UC, upon receiving this declaration, has a standing order to issue the Scenario Beta 500 km evacuation order within 30 minutes without requiring further deliberation or approval.

Responsible Body/Role: Escalation & Scenario Beta Decision Cell (led by USGS Volcano Disaster Assistance Program lead) with immediate notification to UC

Suggested Timeframe: Month 0 (2026-10-14), Hours 0–72 (T+0 to T+72h), continuous real-time monitoring

Key Outputs/Deliverables:

Dependencies:

30. UC, upon receiving a Scenario Beta Trigger Crossing Declaration from the Escalation Cell, issues a formal Scenario Beta 500 km Evacuation Order within 30 minutes. The order specifies: (1) the eruption indicators that crossed the trigger threshold; (2) the 500 km radius evacuation boundary; (3) the tiered execution rings (0–100 km organized evacuation, 100–250 km time-banded evacuation, 250–500 km staged departures); (4) the interim Scenario Beta hub destinations (ranked list outside the 500 km ring); (5) the activation of the secondary-stage shelter and logistics plans (pre-authorized buses, rail corridors, secondary hubs with pre-signed host MOUs); (6) instructions to states, National Guard and FEMA to immediately activate all Scenario Beta contingency plans. This order is broadcast via IPAWS, WEA, NOAA Weather Radio, Guard signal bridging and media in English and five languages.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC, chair)

Suggested Timeframe: Month 0 (2026-10-14), within 30 minutes of Scenario Beta Trigger Crossing Declaration (exact time depends on trigger occurrence)

Key Outputs/Deliverables:

Dependencies:

31. Upon issuance of a Scenario Beta 500 km Evacuation Order, the Unified Command immediately convenes an expanded UC Scenario Beta Response Cell, adding representatives from: (1) the secondary hub communities (Denver, Cheyenne, Billings) or their designees; (2) the National Guard regional commanders for out-of-state Guard deployment; (3) the U.S. Army Corps of Engineers (if emergency logistics support is needed); (4) representatives from the Department of Transportation (federal coordination of I-15, I-80, I-90 usage and emergency lane closures). This expanded cell meets continuously (at least every 2 hours) to coordinate the execution of the three evacuation rings, the routing of populations to secondary hubs, the activation of bus fleets and rail corridors, and the pre-positioning of supplies at secondary hubs.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC) expanded with secondary hub representatives, National Guard, USACE and DOT

Suggested Timeframe: Month 0 (2026-10-14), immediately upon Scenario Beta Evacuation Order issuance

Key Outputs/Deliverables:

Dependencies:

32. At T+72 hours (end of the 72-hour decision window), the UC holds a formal status briefing documenting: (1) total evacuees received and sheltered (Zone Zero and Zone One); (2) final status of the Scenario Beta escalation (if triggered or if indicators remained below threshold); (3) cumulative supply deliveries (water, N95, fuel) and any shortages or contingency activations; (4) responder casualties or exposure-limit violations; (5) post-event safety assessment for any re-entry or infrastructure restoration activities. The UC transitions governance from 72-hour crisis operations to Months 1–3 (2026-11-14 to 2027-01-14) hardening and post-event review mode, with daily (instead of hourly) briefings and a focus on documentation, MOUs, exercises and after-action planning.

Responsible Body/Role: Unified Command (led by FEMA Region VIII IC, chair)

Suggested Timeframe: Month 0 (2026-10-14), Hour 72 (T+72h)

Key Outputs/Deliverables:

Dependencies:

33. FEMA Region VIII IC (UC chair) or designee convenes the first Months 1–3 (2026-11-14 to 2027-01-14) Hardening & Post-Event Review meeting with UC members, specialized advisory-body leads, state emergency managers, USGS, NOAA and NPS representatives. The meeting covers: (1) what went well and what could be improved in the 72-hour response (based on preliminary field observations and responder interviews); (2) a schedule for signed MOUs with the three governors, FEMA Region 10, utilities and Scenario Beta hub communities (target Month 1 = 2026-11-14 completion); (3) a schedule for three after-action reports (one at Month 1 = 2026-11-14 for the 72-hour response, one at Month 2 = 2026-12-14 for MOU and exercise readiness, one at Month 3 = 2027-01-14 for full post-event review); (4) a calendar for three full-scale multi-state exercises (one at Month 2 = 2026-12-14 covering boundary authority transfer and reroutes, one at Month 2.5 = 2026-12-29 covering Scenario Beta evacuation and hub coordination, one at Month 3 = 2027-01-14 covering integrated response) and six smaller operational exercises (shift-rotation, water-convoy, grid-failure recovery, multilingual alert testing, shelter relocation and post-event re-entry).

Responsible Body/Role: FEMA Region VIII IC (UC chair) or designee, with participation from all UC and advisory-body leads

Suggested Timeframe: Month 1 (2026-11-14), Week 1 (first week after T+72h)

Key Outputs/Deliverables:

Dependencies:

34. FEMA Region VIII IC (UC chair) and state emergency managers (MT, WY, ID governors or their designees) sign formal Memoranda of Understanding (MOUs) confirming: (1) each state's acceptance of the UC's authority to issue Zone One and Scenario Beta evacuation orders; (2) commitment to enforce unified evacuation messaging and shelter assignments on state roads and communities; (3) provision of state resources (highway patrol, National Guard) to support contraflow and perimeter operations; (4) mutual-aid resource sharing (water, fuel, medical supplies) among the three states and FEMA Regions 8 and 10; (5) commitment to participate in post-event exercises and after-action-report development. Simultaneous MOUs are signed with FEMA Region 10 (Seattle), regional utilities (Montana-Dakota Utilities, Pacific Power, Idaho Power) and Scenario Beta secondary hub communities (Denver, Cheyenne, Billings or others outside the 500 km ring). All MOUs are signed by the deadline of Month 1 (2026-11-14).

Responsible Body/Role: FEMA Region VIII IC (UC chair) for the federal side; state governors for their respective states; utilities and hub-community representatives for their organizations

Suggested Timeframe: Month 1 (2026-11-14) by end of month

Key Outputs/Deliverables:

Dependencies:

35. FEMA Region VIII IC (UC chair) or designee publishes the first After-Action Report (AAR-1: 72-Hour Response) by Month 1 (2026-11-14), documenting: (1) a timeline and narrative of the 72-hour evacuation response (T+0 to T+72h); (2) quantitative outcomes (total evacuees sheltered, supply deliveries, responder incidents, gateway clearance rates); (3) comparison of actual outcomes to pre-planned targets (98% Zone Zero clearance by T+6h, 95% Zone One clearance by T+24h, etc.); (4) critical decisions made and their rationale (recorded from UC decision log); (5) responder feedback and preliminary observations (lessons learned); (6) recommendations for improvements to the governance structure, command protocols, supply logistics or communications. The AAR-1 is distributed to all UC members, state emergency managers, USGS, NOAA, NPS and is published as a public document to maintain transparency.

Responsible Body/Role: FEMA Region VIII IC (UC chair) or designee, with input from FUCE, advisory bodies and state representatives

Suggested Timeframe: Month 1 (2026-11-14)

Key Outputs/Deliverables:

Dependencies:

36. FEMA Region VIII IC (UC chair) or designee convenes the first full-scale multi-state exercise (Exercise-1: 'Cascade Boundary') in Month 2 (2026-12-14), testing the authority-transfer protocols and reroute decision-making across the NPS-to-state boundaries at all three exit gates (West, North, East Entrance). The exercise simulates a Gallatin Canyon blockage at T+3h that requires a 45-minute clearance attempt (proposed threshold) followed by automatic diversion of overflow traffic to the US-89 Gardiner corridor. The exercise tests: (1) whether the Boundary Coordination Officer and state on-scene commanders can issue reroutes within 5 minutes of the blockage detection; (2) whether the COP dashboard is updated in real time with traffic redirects; (3) whether drivers receive updated route guidance via IPAWS, HAR, VMS or printed route cards; (4) whether the diversion adds only the planned 2–4 hours to transit times for affected vehicles, not more. Exercise participants include the FUCE, state traffic-control personnel at each gate, the Authority Cell, the Shelter Siting Panel and a sample of drivers (simulated evacuees in vehicles with communications staff).

Responsible Body/Role: FEMA Region VIII IC (UC chair) or designee, with FUCE Operations Chief as exercise director

Suggested Timeframe: Month 2 (2026-12-14), Week 1 (2026-12-14, within first week of month)

Key Outputs/Deliverables:

Dependencies:

37. FEMA Region VIII IC (UC chair) or designee convenes the second full-scale multi-state exercise (Exercise-2: 'Ring Dispersal') in Month 2.5 (2026-12-29), testing Scenario Beta execution: the Escalation Cell simulates a USGS Trigger Crossing Declaration at a notional T+36h, triggering the UC to issue a 500 km Evacuation Order. The exercise tests: (1) whether the UC issues the order within 30 minutes of trigger declaration; (2) whether the expanded Scenario Beta Response Cell activates and coordinates ring-by-ring evacuation (0–100 km organized, 100–250 km time-banded, 250–500 km staged); (3) whether secondary hub communities (Denver, Cheyenne) receive and begin processing evacuees within their assigned rings; (4) whether bus fleets and rail corridors are deployed to move evacuees from primary shelters (Bozeman, Idaho Falls) to secondary hubs within the planned timelines; (5) whether supply pre-positioning at secondary hubs is confirmed and adequate. Exercise participants include the UC, FUCE, secondary hub emergency managers, National Guard, bus and rail operators, and simulated evacuee populations.

Responsible Body/Role: FEMA Region VIII IC (UC chair) or designee, with FUCE Operations Chief as exercise director

Suggested Timeframe: Month 2.5 (2026-12-29, between Months 2 and 3 = 2026-12-14, 2027-01-14)

Key Outputs/Deliverables:

Dependencies:

38. FEMA Region VIII IC (UC chair) or designee convenes the third full-scale multi-state exercise (Exercise-3: 'Yellowstone Integrated Response') in Month 3 (2027-01-14), integrating all elements of the response: the Escalation Cell simulates real-time eruption indicators during a 12-hour compressed exercise timeline, the Unified Command makes strategic decisions (zone expansion, Scenario Beta triggers), the FUCE executes tactical operations (contraflow, tow dispatch, water convoy routing), the Responder Health Board manages shift rotation and fatigue, the Authority Cell coordinates boundary transfers, the Shelter Siting Panel monitors PM10 and triggers relocations, and the Scenario Beta Response Cell (if triggered) activates ring-by-ring evacuation. The exercise tests the integrated governance structure under conditions approaching the actual 72-hour response complexity. Exercise participants include all UC and advisory-body members, state emergency managers, FUCE staff, utilities, hospitals, shelter operators, bus and rail carriers, and secondary hub representatives.

Responsible Body/Role: FEMA Region VIII IC (UC chair) or designee, with FUCE Operations Chief as exercise director

Suggested Timeframe: Month 3 (2027-01-14), Week 2 (2027-01-14, within second or third week of month)

Key Outputs/Deliverables:

Dependencies:

39. FEMA Region VIII IC (UC chair) or designee publishes the final comprehensive After-Action Report (AAR-3: 72-Hour Response + Months 1–3 = 2026-11-14 to 2027-01-14 Hardening & Exercises) by the end of Month 3 (2027-01-14), consolidating lessons learned from: (1) the actual 72-hour response (T+0 to T+72h); (2) the Months 1–3 (2026-11-14 to 2027-01-14) MOU negotiations and governance formalization; (3) the three full-scale exercises (Exercise-1 Boundary, Exercise-2 Scenario Beta, Exercise-3 Integrated Response) and six smaller operational exercises. The report documents: (1) what the governance structure achieved during the 72-hour crisis (strengths and weaknesses); (2) what improvements have been made to governance, command protocols, communications, supply logistics and authority clarification during Months 1–3 (2026-11-14 to 2027-01-14); (3) what gaps or risks remain and recommendations for future planning cycles; (4) updated governance best practices and lessons learned to inform planning for future Yellowstone eruption events or similar multi-state volcanic evacuations. AAR-3 is published as an official FEMA and NPS document and distributed to all stakeholders and to the National Incident Management System (NIMS) community for use in national emergency management planning.

Responsible Body/Role: FEMA Region VIII IC (UC chair) or designee, with input from all UC members, advisory-body leads, state emergency managers, exercise after-action reports and responder feedback

Suggested Timeframe: End of Month 3 (2027-01-14)

Key Outputs/Deliverables:

Dependencies:

Decision Escalation Matrix

Scenario Beta Trigger Verification: USGS Eruption Indicators Cross Pre-Authorized VEI-7 Thresholds Escalation Level: Unified Command (Strategic Oversight Board) Approval Process: Escalation & Scenario Beta Decision Cell declares threshold crossing (within 15 minutes of detection); UC issues 500 km Evacuation Order within 30 minutes without further approval. Tie-breaker: FEMA Region VIII IC. Documented in UC decision log. Rationale: The pre-authorized USGS trigger matrix (uplift rate, seismic magnitude, gas flux, magma depth) determines whether Scenario Beta escalates from 100 km to 500 km radius evacuation, affecting millions of people across four states and two FEMA regions. Crossing the threshold is a scientific determination by the Decision Cell but legally and operationally binding on the UC. Delay beyond 30 minutes risks uncontrolled shadow evacuation. Negative Consequences: Failure to escalate promptly leaves 100,000–500,000 additional evacuees without published shelter destinations or transport plans, triggering chaotic, uncontrolled flight on I-15, I-80, I-90 that saturates the Zone One evacuation corridors and strands the original 35,800 park evacuees in traffic. Estimated impact: 4–8 hour evacuation delay, 20–50 preventable respiratory or transport-related casualties.

Corridor Blockage Exceeding Rapid-Clearance Capacity: Gallatin Canyon or Gardiner Single-Point Failure Cannot Be Cleared Within 45 Minutes Escalation Level: Forward Unified Command Element (FUCE) Operations Section Chief with mandatory UC notification Approval Process: Pre-authorized loss-of-exit rule: if blockage persists >45 minutes (proposed threshold) and tow/rockfall teams cannot clear, FUCE Operations Chief triggers overflow diversion to the nearest surviving exit within 15 minutes of the decision. No UC approval required. If a second exit is simultaneously disabled (unlikely), shelter-in-place order issued for remaining queued vehicles and UC is notified immediately. Rationale: The three exit corridors are the sole throughput path for 35,800 evacuees within a T+6 hour deadline. Gallatin Canyon (US-191/US-20) is a two-lane mountain pass with no shoulder; a single blockage (breakdown, rockslide, secondary tremor-induced slide) lasting 45+ minutes exceeds the diversion capacity and forces either a shelter-in-place contingency or a 2–4 hour delay to the overall evacuation. Pre-authorized reroute thresholds enable immediate action without command deliberation. Negative Consequences: A 2–4 hour evacuation delay due to a single-corridor blockage overlaps peak evacuation (T+2 to T+8) with ashfall arrival, exposing 5,000–8,000 stranded vehicles to respiratory hazard. Uncontrolled rerouting (without FUCE coordination) could block secondary exits and cascade into gridlock. Estimated impact: 500–2,000 vehicle occupants stranded in ash; 5–15 respiratory-distress casualties if medical response is delayed.

NPS-to-State Authority Handoff Dispute: Conflicting Orders or Jurisdiction Gaps at Park Boundary During Peak Evacuation Traffic Crossing Escalation Level: Authority & Jurisdictional Coordination Cell with Boundary Coordination Officer, escalating unresolved disputes to FUCE Operations Chief, then to Unified Command Approval Process: Boundary Coordination Officer (co-located at FUCE) mediates disputes between NPS on-scene commander and state on-scene commander within 30 minutes. State commanders are pre-authorized to issue reroutes within pre-written matrix without NPS approval. If state and NPS disagree on reroute validity or shelter assignment, matter escalates to FUCE Operations Chief (1 hour decision window). If still unresolved, escalates to UC for binding decision. Documented in Authority Cell log. Rationale: Contraflow traffic crosses from NPS federal land to state highways mid-corridor, without a hard boundary where both sides can formally hand off responsibility. A dispute over shelter placement, checkpoint staffing or perimeter enforcement creates a 15–45 minute decision latency during the evacuation peak, cascading into a 500–1,000 vehicle backup. Pre-authorized reroute authority and rapid mediation limit escalation. Negative Consequences: A 15–45 minute authority gap (no agreed reroute or conflicting shelter assignment) causes 500–1,000 vehicles to queue improperly or take wrong exits. One unresolved dispute at a single checkpoint cascades into a 1–2 hour evacuation delay for downstream traffic. Additionally, Region 8/10 seams leave Idaho mutual-aid requests (Boise, Pocatello resources) uncoordinated, delaying water/fuel convoys by 1–2 hours.

Shelter Suitability Failure: Real-Time PM10 Exceeds 100 ug/m³ Threshold at Primary Shelter, Requiring Emergency Relocation of 10,000–15,000 Occupants Escalation Level: Shelter Siting & Air-Quality Assurance Panel with binding escalation to FUCE Operations Chief (shelter relocation order) and secondary escalation to Unified Command if relocation cannot be completed within 4 hours Approval Process: Panel detects PM10 >100 ug/m³ at primary shelter (hourly monitoring); convenes within 30 minutes to assess suitability; recommends backup site (ranked, 50+ km upwind). FUCE Operations Chief approves relocation and issues order within 1 hour of panel finding. Buses and intake staff are redirected to backup shelter; relocation is tracked and completion confirmed. If relocation cannot be completed within 4 hours (proposed threshold) due to transport or logistics failure, escalates to UC for contingency (e.g., split occupancy across multiple backup sites, supplemental N95 distribution). Rationale: Ashfall forecasts are uncertain by 100+ km; actual ashfall may exceed model predictions by 2–3x, rendering selected sites unsuitable within 12–24 hours of occupation. Real-time PM10 monitoring allows rapid detection and relocation before respiratory distress develops. A 10,000–15,000 person relocation requires 3–6 hours of transport and intake, consuming significant bus/driver and shelter resources during the evacuation peak. If executed without UC awareness and contingency planning, it cascades into secondary shortages. Negative Consequences: If actual ashfall is 2–3x heavier than forecast and shelters are not relocated, 500–2,000 occupants develop respiratory distress within 6–24 hours; 5–10 may die if medical care is delayed. A relocation ordered without transport readiness causes 2–4 hour delay and potential stranding of occupants mid-transit. If the only backup shelters are also inside the heavy ashfall zone, a second relocation becomes necessary, consuming additional resources and compounding delays.

Responder Exposure Limit Breached: Staffing at Traffic-Control Checkpoints Falls Below 50% Due to Fatigue or Respiratory Symptoms, Threatening Evacuation Throughput and Checkpoint Closure Escalation Level: Responder Health & Fatigue Management Board with authority to trigger standby-reserve deployment, escalating resource-shortage decisions to FUCE Operations Chief and then to Unified Command Approval Process: Board identifies any checkpoint with coverage <50% (proposed threshold) due to exposure limits (6-hour shifts, 2-hour rest) or responder withdrawal for respiratory symptoms. Board convenes within 15 minutes and authorizes activation of the 30–50 person standby reserve to deploy within 4 hours (proposed threshold). If standby reserve cannot close the gap or is already depleted, escalates to FUCE Operations Chief for checkpoint consolidation decisions (combining two posts to maintain coverage) or to UC for out-of-state Guard request. Documented in fatigue-management log. Rationale: The 72-hour continuous response requires 1.5 relief responders per position to maintain 24/7 coverage; strict exposure limits (6-hour shifts, 18-hour withdrawal) are essential to prevent entrapment and respiratory injury but reduce concurrent staffing. If coverage at any checkpoint falls below 50%, traffic-control effectiveness collapses and vehicle throughput drops by 5–10%, extending evacuation by 1–2 hours. Standby reserves and consolidated posts prevent this degradation. Negative Consequences: An uncovered traffic checkpoint allows uncontrolled vehicle movement, wrong-exit usage, and loss of real-time reroute capability. A 2–4 hour evacuation delay due to staffing gaps extends the overlap between peak traffic and ashfall onset, exposing 2,000–5,000 additional vehicle occupants to respiratory hazard. Additionally, uncontrolled perimeter breaks at evacuated towns enable looting and re-entry of unauthorized persons, creating secondary safety and security incidents.

Water Convoy or Critical Supply Delivery Delayed: Arrival at Shelters Pushed Beyond T+24 Hours (Phase 2 Gate), Threatening Shelter Operations and Forcing Supplemental-Reserve or Contingency Activation Escalation Level: FUCE Logistics Section Chief with escalation to FUCE Operations Chief (contingency activation) and Unified Command (additional Guard escort or additional convoy request) Approval Process: Logistics Chief tracks real-time GPS location of water convoys. If ETA exceeds T+24 h (Phase 2 gate deadline), Logistics Chief alerts FUCE Operations Chief within 30 minutes of the forecast delay. Contingency actions are pre-authorized: (1) advance deployment of forward-depot supplemental water (pre-staged at Bozeman, Billings, Idaho Falls at T-48 h); (2) activation of supplemental N95 reserve at Billings or Salt Lake City if ashfall is heavier than modeled and mask consumption exceeds 20% of stock per day (proposed threshold); (3) request for additional Guard escort or ground-transport priority from the UC if convoy is delayed by traffic or road damage. If convoy is delayed >12 hours beyond target, escalates to UC for supplemental federal resource request. Rationale: Water convoys from Salt Lake City are required to arrive at shelters by T+24 h to sustain 15,000 evacuees at Bozeman and 10,000 at Idaho Falls (estimate) for the next 48 hours (T+24 to T+72). Ashfall and evacuation-traffic gridlock can delay convoys from the T+12 h dispatch to arrival as late as T+30 h (estimate), forcing shelters to ration supplies or activate forward depots. Forward depots and supplemental reserves are the contingency; if both are exhausted, additional convoys or federal water mobilization is required. Negative Consequences: A 24-hour delay in water arrival (T+36 h instead of T+24 h) leaves 15,000–25,000 shelter occupants without adequate water for drinking, cooking and medical use for 12+ hours. Water shortage increases risk of dehydration, medication non-compliance and secondary health emergencies. If forward-depot supplemental reserves are also depleted (unusual but possible if initial intake was larger than planned), water shortages could affect medical care (cooling for heat-stressed patients, steam for respiratory treatment) and sanitation, risking disease outbreaks.

Monitoring Progress

1. Evacuation Progress Tracking Against Phase Gates and Time Deadlines

Monitoring Tools/Platforms:

Frequency: Continuous real-time monitoring; formal gate assessments at T+6h (Phase 1) and T+24h (Phase 2); hourly executive briefings to the Unified Command at T+0, T+2, T+6, T+12, T+24, T+36, T+48, T+60, T+72h

Responsible Role: Forward Unified Command Element (FUCE) Operations Section Chief, with real-time vehicle counting by state checkpoints (MT/WY/ID highway patrol, NPS rangers); reporting consolidated by FUCE Planning Chief to the UC

Adaptation Process: If cumulative exit counts at T+6h fall short of 98% (about 35,084 of 35,800), FUCE Operations Chief convenes emergency reroute review with Authority Cell and FUCE to redirect remaining vehicles and accelerate backcountry sweeps. If T+24h Zone One clearance falls short of 95%, UC issues Scenario Beta interim destination list early and activates secondary-stage contingencies. Mid-course adjustments include tow-team redeployment to persistent blockages and Guard staffing surge at under-performing corridors.

Adaptation Trigger: Gate shortfall >2% at Phase 1 (T+6h) or >5% at Phase 2 (T+24h); any single corridor throughput falling >20% below planned 660 vehicles/hour (proposed threshold); blockage persisting >45 minutes triggering diversion rule

2. USGS Eruption Indicator Monitoring and Scenario Beta Trigger Detection

Monitoring Tools/Platforms:

Frequency: Continuous real-time monitoring from T+0 onwards; formal Escalation Readiness Assessments issued by Decision Cell every 6 hours (T+0, T+6, T+12, T+18, T+24, T+30, T+36, T+42, T+48, T+54, T+60, T+66, T+72h); warning alerts if any indicator crosses 80% of trigger threshold; trigger declaration within 15 minutes of any threshold crossing

Responsible Role: Escalation & Scenario Beta Decision Cell (led by USGS Volcano Disaster Assistance Program lead), with real-time data feeds from USGS seismic, GPS and gas networks; UC Liaison reports cell decisions to the Unified Command

Adaptation Process: If any USGS eruption indicator crosses the pre-authorized threshold (finalized by T+3h), the Decision Cell issues a Trigger Crossing Declaration within 15 minutes. The Unified Command automatically issues the Scenario Beta 500 km Evacuation Order within 30 minutes without further deliberation. Secondary-stage hubs, bus fleets and rail corridors are immediately activated. Interim messaging switches from shelter-in-place (outer ring) to evacuation orders for the 100–500 km rings. If an indicator crosses 80% of threshold (warning level), the UC pre-briefs and begins activating contingencies (Beta hub notification, secondary convoy preparation).

Adaptation Trigger: Any USGS indicator (uplift rate, seismic magnitude, gas flux, magma-depth estimate) crosses the pre-written trigger threshold as defined in the finalized matrix by T+3h; estimated time-to-trigger calculation shows remaining window <6 hours (proposed threshold); or 80% threshold-warning triggers pre-activation of secondary contingencies

3. Real-Time Ashfall and Air-Quality Monitoring with Dynamic Shelter-Siting and Relocation Triggers

Monitoring Tools/Platforms:

Frequency: Continuous hourly PM10 monitoring at all sites from T-12h through T+72h; NOAA forecast updates every 6 hours; formal Shelter Siting Panel suitability assessments at T+6h (initial siting decision), T+24h, T+36h, T+48h, T+60h and T+72h; immediate convening if PM10 exceeds 50 ug/m³ (forecast-update trigger) or 100 ug/m³ (suitability-review trigger)

Responsible Role: Shelter Siting & Air-Quality Assurance Panel (led by NOAA ashfall/air-quality forecast lead), with real-time PM10 data collection from sensor networks and NOAA forecast updates; FUCE Operations Chief issues relocation orders based on panel recommendations

Adaptation Process: At T+6h, panel recommends final shelter sites based on latest plume forecast; FUCE Operations Chief approves and directs buses and intake staff to assigned sites. If PM10 at any primary shelter exceeds 100 ug/m³ during operations (T+24h or later), panel conducts rapid relocation analysis (within 30 minutes) and recommends an upwind backup site. FUCE Operations Chief issues relocation order within 1 hour; buses are redirected to the backup shelter and occupant transfer is completed within 4 hours (proposed threshold). If multiple shelters are threatened simultaneously or backup sites are also unsuitable, escalation to UC for split-occupancy or supplemental N95 reserve activation.

Adaptation Trigger: PM10 reading at any shelter exceeds 50 ug/m³ (triggers forecast-update review) or 100 ug/m³ (triggers suitability assessment and potential relocation); forecast wind shift of >30 degrees from current model; actual ashfall depth exceeds modeled expectation by >50% (measured visually or by sensor); NOAA forecast indicates ash concentration will exceed 200 ug/m³ at a primary shelter within 12 hours (proposed threshold)

4. Water, N95 Respirator and Generator Fuel Supply-Chain Monitoring with Convoy Tracking and Contingency Activation

Monitoring Tools/Platforms:

Frequency: Continuous GPS tracking of water convoys from T+12h (dispatch) through arrival at shelters (target T+24h). Inventory spot-checks every 4 hours during peak operations (T+0 to T+36h), then every 6 hours through T+72h. Fuel status at receiving hospitals (Bozeman, Livingston, Idaho Falls) checked every 8 hours. Emergency convoy dispatch triggers immediate (within 30 minutes) FUCE Logistics notification and UC brief.

Responsible Role: FUCE Logistics Section Chief, with real-time convoy tracking via GPS and coordination with Salt Lake City suppliers; fuel pre-positioning and hospital liaison coordination with the three receiving hospitals. Responder Health & Fatigue Management Board monitors responder N95 consumption and triggers supplemental-reserve activation if usage exceeds 20% of available stock per day (proposed threshold)

Adaptation Process: If water convoy ETA exceeds T+24h (Phase 2 gate), Logistics Chief immediately alerts FUCE Operations Chief and activates forward-depot supplemental water release (pre-staged at Bozeman, Billings, Idaho Falls) within 2 hours. If ashfall is heavier than modeled and N95 consumption exceeds 20% of stock per day, supplemental reserve at Billings/Salt Lake City is activated for daily air or ground transport to shelters. If a receiving hospital reports fuel reserves below 48-hour supply, a dedicated priority fuel convoy is requested from regional vendors with 2-hour ETA guarantee. If total supply delay cascades and threatens shelter operations, escalation to UC for federal resource request (additional Guard logistics support, military airlift).

Adaptation Trigger: Water convoy ETA forecast to exceed T+24h by >2 hours; N95 consumption at any shelter or checkpoint exceeds 25% of daily stock (20% threshold plus 5% buffer); hospital fuel inventory falls below 36-hour supply; any forecast delay >6 hours from planned delivery (T+12h for water dispatch, T+24h for arrival)

5. Authority Transfer and Jurisdictional Coordination Monitoring with Boundary-Handoff Execution Tracking

Monitoring Tools/Platforms:

Frequency: Continuous real-time authority-transfer tracking at all checkpoints from T+0 through T+24h (peak boundary crossing). Formal Authority Cell briefings to the FUCE every 6 hours (T+0, T+6, T+12, T+18, T+24h). Rapid escalation (within 30 minutes) if any reroute authority dispute arises or if a Region 8/10 mutual-aid request is delayed.

Responsible Role: Authority & Jurisdictional Coordination Cell (led by Boundary Coordination Officer at FUCE), with on-scene commanders at each park gate (NPS at West/North/East Entrances; MT/WY/ID highway patrol at corresponding corridor exits); FEMA Region 10 liaison at UC (Denver) coordinating Idaho mutual-aid requests

Adaptation Process: If a state on-scene commander and NPS incident commander dispute a reroute or shelter assignment, the Boundary Coordination Officer mediates within 30 minutes via conference call. If consensus is not reached, the matter escalates to FUCE Operations Chief (1-hour decision window); if still unresolved, escalates to UC for binding decision. Pre-authorized reroute authority allows state commanders to issue traffic control orders within pre-written limits without waiting for park approval, reducing decision latency. If Idaho mutual-aid requests (Boise, Pocatello resources) are delayed >1 hour, Region 10 liaison at UC immediately contacts FEMA Region 10 (Seattle) for expedited activation.

Adaptation Trigger: Any reroute authority dispute requiring escalation beyond the Boundary Coordination Officer; state commander reroute issued without proper notification (out-of-sequence); Region 8/10 mutual-aid request delayed >1 hour beyond submission; any vehicle or responder not properly accounted for in the authority-transfer log at a checkpoint; conflicting evacuation orders or shelter assignments from NPS and a state

6. Responder Health, Fatigue and Exposure-Limit Compliance Monitoring with Staffing-Continuity Risk Assessment

Monitoring Tools/Platforms:

Frequency: Real-time shift-log tracking throughout the 72-hour window. Formal fatigue-risk assessments every 6 hours (concurrent with UC briefing schedule: T+6h, T+12h, T+18h, T+24h, T+30h, T+36h, T+42h, T+48h, T+54h, T+60h, T+66h, T+72h). N95 inventory spot-checks every 4 hours during peak operations (T+0 to T+36h). Emergency responder-health incidents reported immediately (within 15 minutes) to the Responder Health Board and medical officer.

Responsible Role: Responder Health & Fatigue Management Board (led by NPS Chief Ranger), with shift-log data collection from all deployed responders and state/Guard commanders; medical officer from the nearest receiving hospital evaluates any responders with respiratory symptoms or heat stress

Adaptation Process: If any checkpoint's staffing falls below 50% of required positions due to exposure-limit rotations or responder withdrawal, the Responder Health Board immediately (within 15 minutes) authorizes activation of the standby reserve for deployment within 4 hours. If responders show acute respiratory distress or heat-related symptoms, they are immediately withdrawn from ash-exposed duty and referred to medical evaluation at the nearest hospital. If N95 consumption exceeds modeled expectations (clogging faster than forecast), supplemental responder N95 reserves are activated for distribution. If cumulative responder fatigue is assessed as critical (multiple personnel approaching 18-hour limits simultaneously), the board recommends to FUCE Operations Chief that lower-priority checkpoints be consolidated or temporarily closed to preserve relief depth at critical posts.

Adaptation Trigger: Any checkpoint staffing falling below 50% coverage due to exposure limits or responder withdrawal; any responder exceeding the 18-hour withdrawal threshold without rotation; two or more responders at the same post reporting acute respiratory symptoms within 2 hours (proposed threshold); N95 consumption rate >20% of stock per day (proposed threshold); cumulative responder fatigue assessed as 'critical' at more than 10% of deployed responders by formal fatigue-risk assessment

7. Communications System Resilience and Message-Delivery Effectiveness Monitoring Under Ashfall and Network Degradation

Monitoring Tools/Platforms:

Frequency: Continuous communication-system monitoring from T-12h through T+72h. IPAWS/WEA broadcast confirmations logged within 30 minutes of each alert. Signal-team coverage status checked every 2 hours during peak operations (T+0 to T+36h), then every 4 hours through T+72h. HAR/VMS message updates issued hourly from forward command during evacuation (T+0 to T+24h). Any outage detected immediately (within 5 minutes) triggers escalation and restoration effort.

Responsible Role: Guard Signal Officer (FUCE comms section) coordinates signal-team deployment and radio-network operations; IPAWS administrator (FEMA or NPS communications) confirms broadcast delivery and documents message content; forward-command public affairs officer oversees HAR/VMS updates and route-card distribution tracking

Adaptation Process: If IPAWS or WEA broadcasts fail or reach <80% of target population (proposed threshold), Guard signal bridging and HAR broadcasts immediately increase messaging frequency and add satellite-phone alerts to state emergency operations centers. If a Guard signal-team's radio repeater fails due to ash clogging or power loss, the backup portable unit is immediately deployed (within 1 hour) and the outage is logged. If cell-tower failure degrades IPAWS delivery, printed route cards and HAR become the primary public channel; multilingual volunteers are activated at lodges to hand-deliver route instructions to non-English speakers. If communication restoration exceeds 2 hours at any critical post (traffic control or shelter), escalation to FUCE Operations Chief for tactical rerouting (redirecting traffic to maintain flow despite comms outage).

Adaptation Trigger: Any IPAWS/WEA broadcast fails or is delayed >15 minutes; estimated population reached by IPAWS <80% of target (proposed threshold); any Guard signal-team loses radio coverage at a checkpoint or shelter; cell-network outage lasting >30 minutes at any critical location; HAR or VMS message failing to display correctly or updating with delay >1 hour from forward command; printed route cards exhausted at any park entrance or lodge

8. Scenario Beta Interim Hub Readiness and Secondary-Stage Evacuation-Plan Execution Monitoring

Monitoring Tools/Platforms:

Frequency: Interim hub list issued by T+12h (Month 0 = 2026-10-14). Written secondary-stage plan completed by Month 1 (2026-11-14). MOU signatures targeted by Month 2 (2026-12-14). If Scenario Beta triggers during the 72-hour window, the expanded Response Cell holds continuous briefings (every 2 hours) documenting ring-by-ring execution and hub-occupancy status. Post-event: full-scale Scenario Beta exercise (Exercise-2 'Ring Dispersal') conducted in Month 2.5 (2026-12-29).

Responsible Role: FUCE Planning Chief develops interim hub list and secondary-stage plan (working with state emergency managers and FEMA Region coordinators); UC chair or designee negotiates and signs host MOUs; Scenario Beta Response Cell (expanded UC) executes ring-by-ring evacuation upon trigger; secondary hub emergency managers confirm receipt of evacuees and completion of intake and registration

Adaptation Process: If Scenario Beta trigger is detected at any point during the 72-hour window, the UC issues the 500 km Evacuation Order within 30 minutes. The expanded Scenario Beta Response Cell immediately activates: ring-by-ring evacuation orders are issued (0–100 km organized, 100–250 km time-banded, 250–500 km staged); buses and rail are dispatched from Bozeman and Idaho Falls primary shelters to secondary hubs; populations are assigned to specific hubs based on location and hub capacity. If a secondary hub is unable to receive assigned evacuees (e.g., due to local capacity constraints), the Response Cell reassigns the population to an alternate hub within 1 hour. If bus fleets or rail corridors are delayed, additional Guard logistics support is requested.

Adaptation Trigger: Interim hub list not issued by T+12h (escalates to UC for expedited planning or alternative contingency); written secondary-stage plan not completed by Month 1 (2026-11-14); any host-community MOU not signed by Month 2 (2026-12-14) (signals governance gap and extends Scenario Beta readiness risk); upon Scenario Beta trigger, any secondary hub reports inability to receive assigned population within 2 hours of the evacuation order; bus-fleet or rail-corridor dispatch delayed >2 hours from the evacuation order

9. Multi-State Governance Formalization and Post-Event Hardening Monitoring (Months 1–3 = 2026-11-14 to 2027-01-14)

Monitoring Tools/Platforms:

Frequency: Weekly UC coordination calls during Months 1–3 (2026-11-14 to 2027-01-14). MOU signature targets: Month 1 (2026-11-14) for governors and Region 10; Month 2 (2026-12-14) for utilities and secondary hubs. AAR publication schedule: AAR-1 by end of Month 1 (2026-11-14); AAR-2 by end of Month 2 (2026-12-14); AAR-3 (comprehensive) by end of Month 3 (2027-01-14). Full-scale exercises scheduled in Weeks 1, 3 and 4 of Months 2, 2.5 and 3 (2026-12-14, 2026-12-29, 2027-01-14).

Responsible Role: FEMA Region VIII IC (UC chair) or designee coordinates MOU negotiations and signature scheduling; FEMA and NPS designate AAR working groups and publication leads; FUCE Operations Chief serves as exercise director for all three full-scale exercises; Hardening & Post-Event Review steering committee (established at Month 1 = 2026-11-14 Week 1) oversees improvements and exercise planning

Adaptation Process: If any MOU signature target is missed (Month 1 or 2 = 2026-11-14 or 2026-12-14), UC escalates to state governors, FEMA Region 10 or utility leadership for expedited signing; any persistent gap beyond 2 weeks flags a governance risk that is documented in AAR for future planning. If AAR development is delayed, interim field-observer summaries are published to maintain transparency; final reports are published even if late, with explanation of delays. If a full-scale exercise reveals critical governance gaps (e.g., Authority Cell unable to mediate boundary disputes, Scenario Beta hub unable to receive populations), the UC convenes an emergency remediation meeting and adjusts governance protocols before the next exercise. All improvements identified are tracked in the Governance Improvements Log with completion target dates (typically within 30 days of identification).

Adaptation Trigger: Any MOU not signed by 2 weeks past target deadline (Month 1 = 2026-11-14 Week 2 for governors/Region 10; Month 2 = 2026-12-14 Week 2 for utilities/hubs); AAR publication delayed >2 weeks past target; any full-scale exercise revealing a 'critical' governance gap (inability to execute a core function); any UC weekly call attendance falling below 50% of required members (signals disengagement); post-event recommendations not assigned to a responsible party within 10 days of identification

Governance Extra

Governance Validation Checks

  1. Completeness Confirmation: All six core governance components are generated and present: (1) internal governance bodies (4 standing bodies + 5 specialized advisory cells) established; (2) implementation plan with 24 sequential steps from pre-event through Month 3 (2027-01-14) hardening; (3) decision-escalation matrix with explicit approval processes and tie-breakers for 5 critical decisions; (4) monitoring-progress plan with 6 continuous monitoring approaches and adaptation triggers; (5) audit framework and transparency measures defined in Phase 1 context; (6) project sponsor authority and legal basis (FEMA RA and NPS Director joint decision memo). No major component is missing.
  2. Internal Consistency Check: The four-body standing governance (UC at Denver, FUCE at Livingston, Responder Health Board, Authority Cell) nests correctly into the implementation plan's T+0 activation sequence (Steps 8–12 establish each body in order). Decision escalation aligns with body authority: UC issues strategic orders (Scenario Beta, zone expansion), FUCE executes operational reroutes within pre-authorized thresholds, advisory bodies (Escalation, Shelter, Authority) provide binding or advisory recommendations to appropriate levels. The monitoring-progress plan's adaptation triggers feed back into decision escalation (e.g., PM10 >100 ug/m³ escalates from Shelter Panel to FUCE Operations Chief to UC within defined timelines). Cadence alignment is consistent: UC hourly briefings at T+0, T+2, T+6, T+12, T+24, T+36, T+48, T+60, T+72 match the Phase 1 and Phase 2 gate assessments at T+6 and T+24. No logical conflicts detected between body authorities or decision timelines.
  3. Clarity of Roles and Conflict-of-Interest Gaps: Responsibilities of the six standing bodies and five advisory cells are clearly defined in Phase 2. However, one significant role ambiguity exists: the Project Sponsor (FEMA Regional Administrator and NPS Director) roles are mentioned in the implementation plan (Steps 1–2) as issuing the foundational decision memo, but their ongoing authority, veto rights, or escalation role during the 72-hour window is not explicitly stated. Are they voting members of the UC, or do they only set pre-event policy? Additionally, the Boundary Coordination Officer role is critical but under-staffed: the documents specify one BCO at the forward element coordinating three state on-scene commanders and the NPS IC, with potential for three simultaneous boundary disputes (West, North, East gates) that one officer cannot mediate within 30 minutes (proposed threshold). Recommendation: explicitly define Project Sponsor escalation authority (e.g., constitutional/legal challenges to evacuation orders); clarify whether BCO should be supported by two deputies (one per state region) or whether a standing three-way conference line protocol allows parallel mediation.
  4. Process Depth and Operational Clarity Gaps: (a) Conflict-of-interest and corruption prevention: Phase 1 audit details identify 6 corruption risks and 13 audit procedures, but the governance bodies (especially UC and FUCE) have no explicit conflict-of-interest disclosure requirement or recusal protocol. Recommendation: require all UC and FUCE members to disclose financial interests in shelter vendors, water/N95 suppliers, or secondary-hub communities at T+0 and to recuse themselves from decisions affecting those vendors. (b) Whistleblower and incident-report protocols: the monitoring-progress plan references fatigue hotlines and responder-health logs but does not define a formal whistleblower or ethics hotline for reporting abuse, vendor fraud, or governance failures during the 72-hour window. Recommendation: establish a confidential hotline (staffed 24/7 during the response) for reporting responder exposure violations, supply-diversion, unauthorized entries or other compliance breaches; results escalate to a designated compliance officer outside the incident command chain. (c) Threshold clarity: the decision-escalation matrix and monitoring plan reference numerous quantitative thresholds (45-minute blockage trigger, 50/100 ug/m³ PM10 triggers, 20% N95 consumption rate, <50% checkpoint staffing) but several thresholds lack justification or sensitivity analysis. Recommendation: document the derivation of each threshold (e.g., 45 minutes = time to attempt tow clearance + time to divert overflow without saturation) and conduct pre-event sensitivity analysis (what happens if the threshold is ±20%?) to ensure thresholds are operationally defensible under stress.
  5. Specific Gaps Requiring Further Detail: (a) Scenario Beta Secondary-Stage Plan Maturity: The implementation plan (Steps 31–32) references an interim ranked hub list issued by T+12 hours and a written secondary-stage plan completed by Month 1 (2026-11-14), but no details exist on how a 5–10 hub list is generated, evaluated or prioritized during the T+0 to T+12 timeframe. The plan names Denver and Cheyenne as Beta hubs but does not verify their distance from the 500 km radius or their shelter/transportation/supply capacity. Recommendation: pre-develop a detailed Scenario Beta Secondary-Stage Evacuation Plan (before Month 0 = 2026-10-14) listing 8–12 candidate hubs outside the 500 km ring (with verified distance, shelter capacity, bus-fleet access, and host-community preliminary agreement); publish this plan to the UC, states and media at T+0 so the T+12 interim list is merely a formal endorsement, not a crash generation. (b) Responder N95 and Staffing Depth Specification: The governance documents assume 100–150 NPS rangers (estimate) and a 1.5 relief ratio, yielding approximately 67–100 concurrent traffic-control positions. However, no detailed staffing plan exists mapping specific rangers and Guard units to each of the 5–10 traffic-control checkpoints, nor is there a pre-calculated responder N95 requirement (separate from the 100,000 civilian stock) documented. Recommendation: before Month 0 (2026-10-14), pre-identify each assigned ranger and state patrol officer by name and post; calculate responder N95 requirement (estimated 2–3 masks per person per shift; 100–150 responders × 12–18 hours average shift ÷ 6-hour work limit = ~200–250 masks per day × 3 days = 600–750 total responder masks minimum); confirm separate pre-staging of this stock outside the civilian 100,000 allotment. (c) Ashfall Forecasting and Shelter Backup Site Adequacy: The plan specifies ranked backup shelter sites 50+ km upwind (proposed threshold) of each primary site, but does not verify that 8–10 suitable backup sites exist with adequate capacity, HVAC, registration infrastructure and accessibility to buses. Recommendation: conduct a pre-event survey (by Month -1, before October 2026) of all candidate backup sites in Montana, Wyoming and Idaho (schools, arenas, fairgrounds with 500+ capacity) and rank them by distance/direction from each primary shelter; document HVAC specifications, generator/fuel access and bus-arrival infrastructure; confirm owners/operators are briefed and pre-authorize emergency occupancy. (d) Water and Fuel Convoy Logistics Detail: The plan targets water dispatch from Salt Lake City by T+12 h and arrival by T+24 h (or use forward depots as fallback), but does not specify the number of trucks, loading logistics at Salt Lake City, route selection (I-15 northbound only, or alternates via US-89 or US-191?), fuel for the convoy itself, or communication protocols if the convoy encounters ashfall and must divert. Recommendation: execute pre-event detailed water-logistics operations plan (before Month 0 = 2026-10-14): identify 2–3 water-supplier sites in Salt Lake City with bulk-truck loading capacity; confirm 20–30 water trucks (holding ~50,000 liters each) can be assembled and fueled within 12 hours; map primary and alternate routes (I-15, US-89/US-191) with fuel stops; establish convoy-escort communication protocol (National Guard liaison in the lead and trail vehicles, satellite phone link to forward command).
  6. Integration and Decision-Flow Alignment Gaps: (a) Real-Time COP Dashboard Specification: The implementation plan repeatedly references a 'shared common operating picture' digital dashboard that is 'updated hourly' and displayed at the UC and FUCE, but no specification exists for what data fields must be displayed, data-update frequency for each field, or system reliability/backup (what happens if the COP server crashes?). Recommendation: develop a detailed COP Data Dictionary (by Month -1) specifying: cumulative exit counts (by gate and time), queue lengths (at each checkpoint), ashfall PM10 (at each shelter, updated hourly), water/fuel/N95 inventory (at each shelter, updated every 4 hours), responder staffing (by post, updated every 2 hours), USGS eruption indicators (updated hourly with margin-to-trigger visualization), communication outages (real-time log), any active reroutes or shelter relocations (current status). Implement redundant data feeds (primary database + satellite backup; manual entry fallback if network fails). (b) Authority Transfer Checkpoint Definition: The implementation plan states NPS authority transfers 'at the park boundary' (West, North, East Entrances), but does not define the exact roadside location (e.g., mile marker X on US-89 north of Gardiner vs. the ranger station vs. the county line). Recommendation: before Month 0 (2026-10-14), conduct field surveys with MT, WY and ID highway patrols to identify a specific transferpoint at each of the three exit corridors (with GPS coordinates, landmark description and signage location); document the exact point in the written Authority Transfer Protocol so state and NPS on-scene commanders both understand where NPS care ends and state custody begins. (c) Escalation Path Endpoints Ambiguity: The decision-escalation matrix specifies that 'constitutional or legal challenges to evacuation orders' escalate to 'the U.S. Attorney's Office (Colorado District) and White House Chief of Staff,' but does not identify who makes the call to White House (FEMA Regional Administrator? UC Chair?), what the expected response time is, or who has authority to override the UC's order if legal counsel says it is unconstitutional. Recommendation: clarify the escalation chain: UC Chair notifies FEMA Regional Administrator of any legal challenge; Regional Administrator consults FEMA Office of General Counsel and White House Legal Counsel (via Situation Room); White House National Security Advisor or Chief of Staff makes final authority determination and notifies the FEMA Administrator (not the UC directly) to issue revised orders or stand down.

Tough Questions

  1. What is the current scientific confidence interval (±km) for the modeled ashfall footprint under a VEI-6 eruption scenario at Yellowstone, given the lack of direct observational data on historic Yellowstone ashfall composition and settling rates? If the actual ashfall extent exceeds the modeled 100 km radius by 20–50 km, will the three pre-staged backup shelter sites remain outside the ashfall zone, or will all primary and backup shelters be threatened simultaneously, forcing a third-stage relocation without known destinations?
  2. Have the 100–150 NPS rangers and state patrol officers assigned to traffic-control checkpoints been explicitly identified by name and post, and does a pre-event dry-run or tabletop exercise confirm that each officer understands his or her assigned checkpoint, shift length (6 hours, proposed threshold), relief rotation protocol and the 18-hour withdrawal trigger (proposed threshold)? If not, how will responder confusion or failure to understand exposure limits during the T+0 activation cascade be prevented?
  3. What is the pre-authorized response time and decision process if the Boundary Coordination Officer at Livingston receives simultaneous reroute-authority disputes from the MT, WY and ID state on-scene commanders at T+3 hours (peak evacuation), and the three disputes cannot be mediated within the 30-minute window (proposed threshold)? Does the BCO have authority to unilaterally decide all three, or does escalation to the FUCE Operations Chief introduce a 1–2 hour delay that compounds the blockage-diversion decision latency?
  4. If Scenario Beta is triggered at T+36 hours (halfway through the 72-hour window) and the UC issues a 500 km evacuation order, how many additional evacuees are estimated to be in that expanded ring (100–250 km time-banded, 250–500 km staged)? Have the 5–10 secondary hub communities (Denver, Cheyenne, etc.) provided pre-signed capacity commitments and committed bus-fleet and medical resources, or is their participation still contingent on Month 1 (2026-11-14) MOU negotiation? If commitments are contingent, what is the fallback if a secondary hub refuses to accept evacuees?
  5. The plan pre-stages 100,000 N95 respirators (user constraint) for civilians and assumes separate responder N95 stocks, but has the actual responder N95 requirement been calculated by role (100–150 rangers × 3 masks/person/shift × how many shifts each works) and confirmed to be available and pre-positioned at T-48 hours? If responder mask consumption exceeds expectations due to heavier ashfall (masks clog faster), what is the resupply protocol, and where is the supplemental responder N95 reserve staged?
  6. The Authority & Jurisdictional Coordination Cell resolves NPS-to-state disputes at the park boundary, but if a state emergency manager or governor refuses to enforce a UC-issued evacuation order or issues a conflicting shelter-in-place instruction, what is the enforcement mechanism? Does the UC have authority to federalize the state National Guard under Stafford Act emergency declaration, and has that authority been pre-coordinated with the three governors and documented in the signed MOUs (due Month 1 = 2026-11-14)?
  7. Has a full-scale integrated-response exercise (Exercise-3, scheduled Month 3 = 2027-01-14) actually been completed and published as post-event proof that the governance structure functions under realistic 72-hour-compression conditions, or is this exercise still planned and contingent on pre-event preparation and funding? If the exercise has not been completed by the time the eruption probability window activates (Month 0 = 2026-10-14), the governance structure remains untested and operationally at risk.

Summary

The governance framework establishes a pre-authorized, time-compressed multi-state evacuation response centered on a Unified Command at FEMA Region VIII RRCC Denver with a forward operational element at Livingston, MT. Five specialized advisory bodies (Escalation Cell, Forward Element, Responder Health Board, Authority Cell, and Shelter Siting Panel) execute real-time decisions on contraflow traffic, eruption escalation, ashfall monitoring, and supply logistics within concrete trigger matrices and decision thresholds. The implementation plan sequences governance activation from T+0 through T+72 hours of continuous operations, transitioning to hardening and post-event review during Months 1–3 (2026-11-14 to 2027-01-14). Core strengths include explicit pre-authorized decision rules, rapid escalation protocols, and real-time monitoring dashboards that reduce command latency. Three critical unresolved gaps—the absence of a detailed Scenario Beta secondary-stage shelter and logistics plan, undefined responder staffing reserves and N95 protection counts, and static (rather than adaptive) ashfall shelter siting—create cascading failure risks if triggered during the 72-hour window. The governance structure is execution-credible for the 35,800 Zone Zero evacuation but depends heavily on pre-event hardening during Months 1–3 (2026-11-14 to 2027-01-14) to close Scenario Beta and supply-chain readiness gaps before the eruption probability window activates.

1. Scenario Beta Secondary-Stage Evacuation Plan and Hub Capacity Validation

The plan pre-authorizes a Scenario Beta VEI-7 trigger ordering immediate 500 km evacuation affecting millions, but no second-stage destinations, hub capacity or tiered messaging exist. Without this data, issuing the trigger order will cause uncontrolled shadow evacuation saturating I-15, I-80 and I-90, adding 4–8 hours delay to the primary Zone Zero evacuation and stranding 5,000–20,000 people in ashfall zones. This is the single largest residual cascade-failure risk.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 1 (2026-11-14), validate that at least five ranked hubs outside the 500 km ring have signed MOUs confirming combined capacity for 250,000+ additional beds and water/N95 pre-positioning schedules. By Month 2 (2026-12-14), execute tiered-message pilot with 1,000+ residents in Zone One communities (Bozeman, Gardiner, Cody) and measure message comprehension (target: ≥80% recall of assignment logic) and stated compliance intent (target: ≥70% stated willingness to follow time-banded schedule).

Notes

2. Responder Exposure Limits, Relief Depth and Separate N95 Inventory Sizing

The plan budgets 100–150 NPS rangers at a 1.5 relief ratio, yielding 67–100 concurrent positions across three exits and perimeters during the T+2 to T+8 peak evacuation. A single traffic incident or responder injury will halt one checkpoint for 2–4 hours, stranding 500–2,000 vehicles in ashfall and cascading 2–4 hours delay to the entire evacuation. Relief depth must be confirmed, standby reserves pre-positioned and responder N95s sized separately to prevent this single-point failure.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month 0 (2026-10-14) (T+6 h), obtain written confirmation from NPS Incident Commander and state highway patrol of actual available responder headcount by unit/district. By Month -0.5 (2026-09-29), execute a 6-hour shift-rotation exercise at Mammoth or Gardiner checkpoint with actual ranger and patrol personnel, validating shift limits, N95 replacement, fatigue-assessment accuracy and radio continuity. By Month 0 (2026-10-14) (T+0), stage separate responder N95 inventory (150,000–200,000 units) at a dedicated depot with 4-hour resupply agreement and confirm Fort Carson pre-authorization for rapid Guard reinforcement.

Notes

3. Real-Time Ashfall Monitoring and Dynamic Shelter-Relocation Protocols

The plan selects shelter sites at T+6 h based on a single NOAA/USGS forecast with documented ±50 km uncertainty. If actual ashfall diverges from forecast or doubles in intensity, 10,000–15,000 evacuees will be sheltered in moderate-to-heavy ash within 12–24 hours, requiring emergency relocation. Without real-time PM10 monitoring, backup-site pre-authorization and relocation protocols, shelters will be rendered untenable mid-operation, stranding 200–500 evacuees and overwhelming hospitals with respiratory-distress cases.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month -0.5 (2026-09-29), deploy PM10/PM2.5 sensors at Bozeman, Idaho Falls and forward command with confirmed 4-hour data-transmission capability. By Month -0.5 (2026-09-29), obtain signed NOAA commitment for 3-hourly VAFT updates with concentration outputs at three shelter elevations. By Month 1 (2026-11-14), complete survey and pre-authorization of at least three ranked backup shelter locations per primary site. By Month -0.5 (2026-09-29), execute a tabletop shelter-relocation exercise and measure decision latency from PM10 exceedance detection to UC relocation order (<2 h target).

Notes

4. Water Supply Chain Validation: Dispatch Timeline, Forward-Depot Pre-Positioning and Ashfall-Impact Testing

The plan targets water arrival at shelters by T+24 h, but estimates realistic delivery time as T+18–30 h. Without forward-depot pre-positioning, shelters must ration water for the first 18–24 hours, risking dehydration in 10,000–20,000 evacuees. Municipal water sources become ash-contaminated within 4–6 hours and are unsafe without treatment. This data collection validates the water supply chain from source through shelter intake and identifies contingency backup sources (groundwater, tanker fills) to ensure T+24 h water availability without relying solely on distant convoys.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month -0.5 (2026-09-29), execute a water-convoy exercise from Salt Lake City to Bozeman under ashfall simulation, documenting realistic travel time (target: 18–30 hours). By Month 0 (2026-10-14) (T+0), stage 200,000–300,000 liters at Bozeman and 100,000–150,000 liters at Idaho Falls forward depots, with signed 4-hour resupply contracts from Pocatello and Butte suppliers. By Month 1 (2026-11-14), validate that Bozeman and Idaho Falls water systems have documented emergency-isolation and backup-source protocols, and that groundwater or alternative-water sources can supply ≥10,000 L/day as emergency backup.

Notes

5. Geotechnical Road Hazard Assessment: Gallatin Canyon Single-Lane Clearance Feasibility and South Entrance Bypass Viability

The plan pre-positions two tow/rockfall teams to reach Gallatin Canyon within 15 minutes and sets a 45-minute blockage threshold before diversion. However, no geotechnical data exists to validate clearance feasibility, secondary-slide risk or the time estimates. If Gallatin Canyon clearance actually requires 6–12 hours (as documented in similar volcanic or seismic events), the 15-minute arrival and 45-minute threshold are infeasible. Proceeding without this data risks either (1) committing equipment to a clearance attempt that cannot succeed and exposes crews to secondary-slide hazard, or (2) abandoning the corridor prematurely and overloading surviving exits. This data collection informs the go/no-go decision for single-lane clearance and the loss-of-exit contingency trigger.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month -1.5 (2026-08-29, assuming month-length recalculation for pre-event planning), conduct a full geotechnical survey of Gallatin Canyon (10 km highest-risk section) and the South Entrance slide, documenting debris volume, slope stability and secondary-slide probability. By Month -1 (2026-09-14), obtain written feasibility assessment from professional geotechnical engineer on single-lane clearance time (target: ≤4 hours) and abort triggers. By Month -0.5 (2026-09-29), execute a site survey and equipment-positioning exercise at Mammoth and Spanish Creek, validating 15-minute reach time to Gallatin Canyon under ashfall simulation.

Notes

6. Multi-State Authority Structure and Boundary Coordination Officer Decision Authority Validation

The plan specifies a Boundary Coordination Officer with pre-authorized decision authority, but the Officer's position is not formally created, authority is not delegated by governors in writing and the three state on-scene commanders' acceptance of reduced approval authority is not documented. Without this validation, the Boundary Coordination Officer's reroute decisions will face jurisdictional challenge or delay when implemented during the crisis, potentially halting traffic for 15–45 minutes while approvals cascade through state adjutants general or emergency management chains. This data collection formalizes authority, documents pre-event delegation and validates that multi-state coordination can function under time pressure.

Data to Collect

Simulation Steps

Expert Validation Steps

Responsible Parties

Assumptions

SMART Validation Objective

By Month -0.5 (2026-09-29), obtain written pre-event authorization letters from Montana, Wyoming and Idaho governors confirming Unified Command and Boundary Coordination Officer authority. By Month -1 (2026-09-14), execute signed MOUs with state DOTs and highway patrol specifying boundary-transfer checkpoints and pre-authorized reroute protocols. By Month -0.5 (2026-09-29), conduct a radio-interoperability test confirming that the Boundary Coordination Officer can reach all three state on-scene commanders and Denver RRCC simultaneously on a secure net. By Month -1.5 (2026-08-29), execute a multi-state command-authority tabletop exercise testing cross-state decision chains and documenting any approval delays or jurisdictional conflicts.

Notes

Summary

The plan aims to evacuate ~35,800 tourists and staff from Yellowstone Zone Zero by T+6 hours and expand to a 100 km Zone One by T+24 hours under a 72-hour, 40% VEI-6+ eruption probability window (Month 0 = 2026-10-14). The six critical data-collection areas focus on: (1) Scenario Beta secondary-stage hub destinations and tiered messaging (resolves the hollow pre-authorization of a 500 km order lacking destinations), (2) Responder relief depth and separate N95 inventory (addresses zero-cushion staffing during peak evacuation), (3) Real-time ashfall monitoring and shelter-relocation protocols (manages forecast uncertainty and mid-operation shelter viability), (4) Water supply-chain validation including forward depots and realistic convoy timelines (closes the T+18–30 h arrival gap), (5) Geotechnical feasibility of single-lane corridor clearance (tests whether Gallatin Canyon and South Entrance are viable exits), and (6) Multi-state authority structure and Boundary Coordination Officer delegation (formalizes NPS-to-governor handoff and pre-authorized decision authority). Each collection area includes simulation steps using standard tools (GIS mapping, traffic models, tabletop exercises, field surveys) and expert validation with USGS, FEMA, state emergency management and professional engineers. Simulation results must be completed by Month 1 (2026-11-14) hardening deadline, with signed MOUs and full-scale exercises by Month 3 (2027-01-14). The priority is validating the three tightest coupling risks: (A) Scenario Beta destinations prevent uncontrolled shadow evacuation that would delay Zone Zero clearing, (B) responder relief depth prevents single-checkpoint failures from cascading, and (C) ashfall monitoring prevents mid-operation shelter placement in heavy ash. Immediate actionable tasks: activate USGS and FEMA hub-feasibility assessments (target Month -1.5 = 2026-08-29 for survey completion), secure governor pre-authorization letters (target Month -0.5 = 2026-09-29 for signature), and deploy PM10 sensors and water-supply contracts (target T+0 = 2026-10-14). All data collection, simulation and expert validation must complete by Month 1 (2026-11-14) to inform Months 2–3 (2026-12-14 to 2027-01-14) multi-state exercises and contingency planning.

Documents to Create

Create Document 1: Yellowstone Evacuation Project Charter

ID: 6abed7ce-09df-466a-92a3-0d27f1c87a5a

Description: Foundational project authorization document defining scope (35,800 Zone Zero + Zone One evacuation), objectives (T+6h clearance, T+24h Zone One completion, pre-authorized Scenario Beta), timeline (72-hour window, Month 0 start = 2026-10-14), resource envelope (USD 200M estimate), constraints (40% VEI-6+ probability, three-exit contraflow, Unified Command at Denver RRCC), and high-level success criteria (Gate G1: 98% of 35,800 out by T+6h; Gate G2: 95% of Zone One residents out by T+24h). Signed by UC Incident Commander, NPS leadership, and FEMA Region VIII Director.

Responsible Role Type: Project Manager / Unified Command Incident Commander

Primary Template: PMI Project Charter Template

Secondary Template: FEMA Emergency Operations Plan Charter

Steps to Create:

Approval Authorities: UC Incident Commander (Denver RRCC), NPS Regional Director, FEMA Region VIII Regional Administrator, Governors of Montana, Wyoming, and Idaho (verbal by T+6h, signed by Month 1 = 2026-11-14)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Scenario Beta trigger fires, but the pre-authorized USGS trigger matrix is absent or ambiguous, and decision authority is unclear. The Unified Command convenes a conference call to discuss the indicators, delaying the 500 km order by 2–4 hours. During that delay, unordered residents in towns 150–300 km from the park (Billings, Bozeman, Idaho Falls, Driggs) observe ashfall intensifying and begin spontaneous mass evacuation without guidance, flooding I-15, I-90 and US-191 with 100,000–200,000 uncoordinated vehicles. The organized Zone Zero evacuation (35,000 tourists) and Zone One residents (5,000–10,000 estimate) become trapped in the chaotic traffic, adding 6–12 hours to their transit times. Ashfall peaks before the majority of evacuees reach safety; respiratory distress cases overwhelm hospitals in Salt Lake City, Denver and Billings, which are already short of N95 masks and generator fuel. An estimated 50–200 preventable deaths occur due to delayed hospital admission, loss of ventilator support, and respiratory injury. Post-event analysis concludes that 2–4 hours of decision delay cost more lives than any benefit from waiting for additional information. Public trust in government eruption-response authority collapses, undermining compliance in future volcanic-risk zones.

Best Case Scenario: The Escalation Trigger and Evacuation Release Doctrine document pre-authorizes a written USGS trigger matrix with explicit numerical thresholds (e.g., combined ULP >5 mm/day + tremor swarms M≥3.5 + SO2 flux ≥10,000 t/day = VEI-7 probable; Unified Command decision authority confirmed in writing). When indicators cross thresholds at Month 0 (2026-10-14) T+48 hours, a USGS volcanologist at the forward UC element confirms the reading within 15 minutes, and the incident commander issues the 500 km Scenario Beta order within 30 minutes. IPAWS disseminates a pre-tested phased message (in English and five languages) reaching 90%+ of target audiences within 15 minutes of issue. Outer-ring residents (100–500 km) understand the tier assignments (shelter-in-place, time-banded, or organized evacuation) and follow published departure windows, avoiding gridlock. The Zone Zero evacuation (35,000) completes within T+8 hours (2 hours better than nominal) because the early Beta order allows forward deployment of secondary-stage buses to Bozeman and Idaho Falls, moving evacuees onward before the shelters reach capacity. Ashfall arrives at T+20 hours, by which time 95%+ of Zone Zero and Zone One populations are in safe, sheltered locations outside the modeled ashfall footprint. Hospital systems receive sufficient notice to relocate fragile patients and pre-stage generator fuel. Scenario Beta secondary-stage hubs are activated on schedule, with pre-arranged shelter capacity, food and water supplies ready. Public trust in government remains high, enabling voluntary cooperation with tier assignments and reducing the unordered evacuation load. Estimated 5–10 lives saved by the 2–4 hour acceleration, and zero authority-confusion incidents.

Fallback Alternative Approaches:

Create Document 2: Scenario Beta Secondary-Stage Evacuation Plan

ID: 37178d26-46c9-488f-b917-a716bc5fc0c3

Description: Written plan specifying five to ten ranked shelter hubs outside the 500 km ring (Denver, Cheyenne prioritized; distance verification required), signed capacity MOUs from host counties, tiered public messaging (shelter-in-place 250–500 km, time-banded 100–250 km, organized Zone One), bus-fleet and rail-corridor routing to secondary hubs, and supply pre-positioning (food, water, N95s, medical supplies) by Months 1–2 (2026-11-14 to 2026-12-14). Operationalizes the pre-authorized VEI-7 trigger so that a 500 km evacuation order issued at T+12h has published destinations and messaging ready to deploy, preventing uncontrolled shadow evacuation that would strand Zone Zero evacuees.

Responsible Role Type: Scenario Beta Secondary-Stage Destination Planner

Primary Template: Multi-State Evacuation and Sheltering Plan Template (FEMA, Texas Division of Emergency Management)

Secondary Template: Tier System and Time-Banded Departure Schedule (Hurricane Rita, Texas A&M Transportation Institute model)

Steps to Create:

Approval Authorities: UC Incident Commander, Governors of Montana, Wyoming, Idaho, Colorado, and Utah (host states), Emergency Managers and Commissioners of all participating hub counties

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A VEI-7 indicator is detected at T+12 hours, triggering the pre-authorized Scenario Beta 500 km evacuation order. No second-stage hub destinations, capacity confirmations or tiered-messaging plan exist. The Unified Command issues an immediate 500 km evacuation order with no published destinations or time-banded schedule. Within 2–4 hours, uncontrolled evacuation of 100,000–500,000 people begins spontaneously across all roads leading away from Yellowstone. I-15, I-80 and I-90 become gridlocked with private vehicles searching for shelters. This shadow evacuation blocks organized Zone One evacuation corridors, stranding the initial 35,800 Zone Zero evacuees who had cleared by T+6 hours. Ashfall onset at estimated T+8 hours coincides with peak chaos: visibility drops, respiratory distress spikes, and ambulance traffic cannot navigate gridlocked interstates. Hospitals become overwhelmed with unrouted patients arriving from uncoordinated shelters. Estimated cascading outcome: 10–20 hour evacuation delay for Zone Zero compared to plan, 5,000–15,000 people hospitalized for respiratory distress outside planned medical networks, 50–200 preventable deaths due to stranded populations, unmanaged medical transfer delays and secondary health emergencies, plus USD 200–500 million in unplanned emergency response costs.

Best Case Scenario: By Month 2 (2026-12-14), the plan identifies and obtains signed MOUs from five to eight hubs outside the 500 km ring (Denver, Cheyenne, Albuquerque, Las Vegas and backups), each confirming 5,000–50,000 bed capacity and 48-hour resource mobilization. Tiered messaging with zone-to-hub assignments and time-banded departure schedules is published by Month 0 (2026-10-14). Supply pre-positioning (food, water, N95, fuel, medical) for 100,000–500,000 evacuees is completed at each hub by Month 2 (2026-12-14). A full multi-state Scenario Beta exercise in Month 3 (2027-01-14) validates bus routing, shelter intake and time-banded dispatch. At T+12 hours, the VEI-7 trigger fires. The Unified Command issues the 500 km order; within 1 hour, evacuation assignments (zone to hub, time window, bus pickup points) are broadcast via IPAWS, HAR and multilingual channels to all 100,000–500,000 residents. Organized time-banded departures proceed: 0–100 km Zone One residents depart first (T+12 to T+36 h), using primary shelters and onward bus transport to hubs; 100–250 km residents depart in later windows (T+24 to T+72 h); 250–500 km residents self-organize by published schedule. No uncontrolled shadow evacuation occurs; corridor throughput remains sufficient for Zone One clearance by T+48 h. Secondary hubs receive evacuees in scheduled waves, with pre-staged supplies sustaining shelter operations for 10+ days without resupply. Hospital networks are not overwhelmed; patient routing follows pre-planned medical-dispersal protocols. Outcome: Scenario Beta evacuation completes within 72 hours with <5% unplanned shelter movement, <100 respiratory-distress cases in excess of planned capacity, zero preventable deaths due to cascade-failure, and public trust in escalation messaging preserved for future warnings.

Fallback Alternative Approaches:

Create Document 3: Command Structure and Jurisdictional Authority Framework

ID: 768e57ad-399c-491a-845f-3a9c2e011f60

Description: Defines organizational structure of the Unified Command with FEMA Region VIII RRCC (Denver) as primary, FEMA Region 10 liaison seated from T+0, and forward UC element at Livingston, MT (alternate Bozeman). Specifies authority transfer from NPS to state governors at park boundary via written protocol; establishes Boundary Coordination Officer position with pre-authorized reroute and shelter-assignment authority during the crossing. Documents NPS-to-state handoff checkpoints (Mammoth on US-89, Gallatin County line on US-191, Cody limits on US-14/16/20) and clarifies when state custody begins. Includes decision authority for trigger matrix (UC issues Scenario Beta 500 km order within 30 min of trigger without further approval) and governs inter-agency communication protocols (primary: hourly UC briefings; secondary: Boundary Coordinator voice/data links).

Responsible Role Type: Regional Emergency Management & Multi-Jurisdiction Coordination Director

Primary Template: NIMS/ICS Unified Command Organization Chart and Authority Matrix

Secondary Template: Interstate Mutual Aid Agreement (EMAC) Authority Framework Template

Steps to Create:

Approval Authorities: UC Incident Commander (FEMA Region VIII), Governors of Montana, Wyoming, Idaho, and Colorado (for forward command resources), NPS Regional Director, State Emergency Management Directors

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Scenario Beta trigger fires at T+36 hours (late Phase 2), but the UC Incident Commander lacks pre-authorized decision authority and must convene the governors and FEMA for verbal approval. The approval loop takes 3–4 hours, during which unconfirmed rumors of a larger eruption spread via media and social networks, triggering uncontrolled shadow evacuation of 100,000+ people in the 100–250 km ring onto I-15, I-80 and I-90. By the time the official 500 km order is announced, these routes are gridlocked with private vehicles, blocking the organized Zone One evacuation of the remaining park visitors and stranding medical transport. The Boundary Coordination Officer at Livingston has no authority to reroute traffic onto secondary roads without state permission, and the state on-scene commanders are overwhelmed by the uncontrolled traffic and unable to respond to real-time requests. Region 10 mutual-aid for Idaho resources is still uncoordinated with the Denver RRCC, and fuel and water convoys from Boise and Pocatello do not arrive for 4–6 hours beyond the target. Hospital patient transfers are delayed 6–8 hours due to gridlock, resulting in 5–10 preventable respiratory-distress deaths and 20–30 cancellations of critical surgeries.

Best Case Scenario: The Unified Command organizational structure is formally activated at T+0 with the UC Incident Commander seated in Denver, FEMA Region 10 liaison already present with pre-authorized access to Idaho mutual-aid authorities, and the forward UC element (NPS IC, Boundary Coordination Officer, Contraflow Operations Manager and Logistics Director) co-located in Livingston, MT. At T+6 hours, the Boundary Coordination Officer executes a pre-authorized reroute within 15 minutes, directing overflow traffic from a Gallatin Canyon bottleneck to the East Entrance, and this decision is implemented at the traffic checkpoint before congestion builds. When Scenario Beta trigger fires at T+45 hours, the pre-authorized trigger matrix allows the UC Incident Commander to announce the 500 km order within 30 minutes without waiting for governor approval, and state on-scene commanders immediately disseminate the order via IPAWS and Guard signal nets. The Region 10 liaison activates pre-signed mutual-aid agreements with Boise and Pocatello, and fuel and water convoys dispatch within 2 hours. The unified, coordinated authority structure enables 98% compliance with the evacuation order and prevents uncontrolled shadow evacuation. Hospital patient transfers proceed on schedule, and no preventable deaths occur due to command delays.

Fallback Alternative Approaches:

Create Document 4: Escalation Trigger Matrix and Scenario Beta Pre-Authorization

ID: 82e68eba-a1aa-4f56-8f97-1f3f5e9ede57

Description: Written, pre-authorized threshold-based trigger matrix specifying USGS indicators (uplift rate, seismic magnitude, gas flux, modeled VEI probability in remaining window) that automatically activate Zone One expansion and authorize the Scenario Beta 500 km evacuation order. Final indicator values to be set by USGS by T+3h (placeholders: VEI-7 probability ≥20% in remaining window; other thresholds TBD). UC Incident Commander is pre-authorized to issue the 500 km order within 30 minutes of trigger confirmation without requiring further approval from governors or FEMA. Document clarifies that trigger is pre-authorized decision authority, not a decision that requires meetings or additional debate during the 72-hour window.

Responsible Role Type: Volcanologist & USGS Hazard Forecaster

Primary Template: USGS Volcano Monitoring and Eruption Forecast Protocol Template

Secondary Template: Incident Command Decision Authority and Pre-Authorization Document

Steps to Create:

Approval Authorities: USGS Yellowstone Volcano Observatory Director, UC Incident Commander (FEMA Region VIII), Governors of Montana, Wyoming, and Idaho (verbal authorization by T+6h, signed by Month 1 = 2026-11-14)

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Without a written, clearly specified trigger matrix and pre-authorization mechanism, the UC Incident Commander faces a 15–45 minute delay at the moment of the VEI-7 decision (estimated T+12 to T+24 hours), requiring phone calls to governors, FEMA leadership, and USGS to confirm the indicator values and seek approval for the 500 km order. During this delay, tens of thousands of residents outside the 100 km zone begin uncoordinated evacuation on their own, saturating I-15, I-90 and US-191 with unplanned traffic within 2–4 hours. When the 500 km order is finally issued, it arrives after the shadow evacuation has already jammed the corridors, preventing the organized Zone One and Zone Zero evacuees (35,800 people plus gateway-town residents) from reaching safe zones by T+24 hours. Gridlocked evacuation traffic, amplified by conflicting state-level guidance, results in an estimated 10,000–50,000 people stranded in or near ashfall zones within T+24 to T+48 hours, with 20–100 preventable respiratory-distress and trauma casualties. The cascading failure of the evacuation plan, visible in real-time media coverage, erodes public trust in the Unified Command and triggers a formal inter-state jurisdictional dispute that delays Phase 2 hand-off and second-stage shelter operations by 6–12 additional hours.

Best Case Scenario: A written, pre-authorized trigger matrix with specific USGS thresholds, clear trigger logic (ANY or ALL), and a documented communication protocol enables the UC Incident Commander to issue the Scenario Beta 500 km order within 30 minutes of USGS trigger confirmation, with no delays, disputes, or additional meetings. The order is simultaneously communicated to state governors, FEMA Region 10, the forward element, and public-alert channels (IPAWS, local media) within 45 minutes of confirmation. The pre-positioned interim second-stage plan (ranked hub list, time-banded rings, messaging strategy) activates immediately, directing outer-ring residents to published destinations and time-band windows, preventing uncontrolled shadow evacuation. Well-coordinated ring-based execution (0–100 km organized, 100–250 km time-banded, 250–500 km staged departure) keeps I-15, I-90 and US-191 passable for Zone One and Zone Zero organized evacuations. Signed governor MOUs and EMAC arrangements ensure state-level coordination and messaging discipline. By T+36 hours, the entire 500 km ring is executing with 80–90% public compliance, shelters and hubs are receiving evacuees in an orderly sequence, supply convoys are moving, and secondary-stage medical and logistics operations are activated. The Unified Command maintains credibility and authority throughout, with no jurisdictional reversals or media-driven confusion; estimated cascading-failure risk is reduced from 20–100 casualties to <5.

Fallback Alternative Approaches:

Create Document 5: Egress Corridor Allocation and Contraflow Operations Plan

ID: e7aec916-0370-49a6-8b0c-a78a86e82a23

Description: Specifies three-exit contraflow strategy allocating zone-zero evacuees (35,800 people) to US-20/US-191 West (50%, ~17,900 to Bozeman/I-90), US-89 North (30%, ~10,740 to Gardiner/Livingston/I-90), and US-14/16/20 East (20%, ~7,160 to Cody/East Entrance). Documents fixed district-to-gate assignment preventing interior vehicle crossings, traffic-control staffing at each checkpoint, tow and rockfall-clearing teams pre-positioned at chokepoints, and contraflow-termini design (staging-lot capacity, turn-pocket geometry, queue-storage). Specifies traffic throughput targets (660 vehicles/hour per exit, 2,000 vehicles/hour total estimated), lane-reversal procedures, and blockage-diversion rules (>45 minutes blockage triggers overflow to next-nearest exit; >6 hours unstorable blockage triggers loss-of-exit contingency and shelter-in-place).

Responsible Role Type: Transportation Operations & Contraflow Specialist / Contraflow Operations and Traffic Control Manager

Primary Template: FHWA Contraflow Operations and Evacuation Planning Guidance (Texas DOT Hurricane Rita model)

Secondary Template: Mountain Pass Traffic Management Plan (CDOT, mountain-corridor protocols)

Steps to Create:

Approval Authorities: UC Incident Commander, NPS Incident Commander, Montana DOT Director, Wyoming DOT Director, State Highway Patrol Commanders (MT, WY, ID), USGS Geotechnical Hazards Specialist

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A major rockfall or secondary tremor-induced slide blocks Gallatin Canyon during peak evacuation (T+3 to T+5 hours) when 5,000-8,000 vehicles are queued in the corridor. Tow teams deployed from Mammoth take 20-30 minutes to reach the blockage due to ash or seismic uncertainty. Debris volume exceeds single-lane clearance capacity, and geotechnical assessment takes 45 minutes to 2 hours. With no pre-authorized diversion rule and unclear authority to order reroutes, the forward command delays issuing a diversion order by 30-45 minutes while seeking approval from three agencies. By the time overflow is redirected to US-89 North and US-14/16/20 East, those corridors are already at capacity, creating a bottleneck cascade that extends evacuation by 4-6 hours. An estimated 2,000-4,000 vehicles remain trapped in Gallatin Canyon during ashfall onset (T+6 to T+8 hours), exposing evacuees to 4-8 hours of unforecast heavy ashfall. Respiratory distress among the stranded rises from zero to 50-100 cases, with 5-10 deaths preventable by timely evacuation.

Best Case Scenario: Contraflow is fully operational on all three exits by T+1 hour with clear lane markings, traffic-control posts manned and monitored in real-time. The three-way load split (50/30/20%) evenly distributes traffic, achieving an average throughput of 2,000 vehicles/hour. Geotechnical monitoring detects no incipient slides, and tow teams remain on standby with no blockages requiring deployment. Pre-authorized diversion rules and reroute authority enable the forward command to respond to any minor debris within 5-10 minutes. Zone Zero is declared clear at T+5.5 hours with 98% of 35,800 people confirmed through exit counts, and a final cohort of 200-400 backcountry stragglers under active ranger escort or in designated last-resort shelters. Evacuation peak ends before significant ashfall arrival, limiting respiratory distress to a handful of cases. The plan's success enables confidence in Phase 2 Zone One evacuation by T+24 hours and credibility for the pre-authorized Scenario Beta trigger if escalation indicators cross thresholds.

Fallback Alternative Approaches:

Documents to Find

Find Document 1: USGS Yellowstone Volcano Observatory Monitoring Data and Eruption Probability Assessments

ID: fef7b2b0-b693-4184-9ba5-820cd32d7d41

Description: Real-time USGS seismic, GPS, gas-emission and thermal data from Yellowstone Caldera monitoring network, including current uplift rates (mm/year), seismic magnitude and frequency distributions, SO2 flux measurements and any published eruption-probability or VEI forecasts. Serves as the scientific input for the Escalation Trigger Matrix and the pre-authorized Scenario Beta decision rule. Intended audience: UC Incident Commander, USGS liaison officer, volcanologist advisor. Context: the plan requires final trigger indicator values by T+3h; this data is the baseline and must be collected and analyzed before the 72-hour window begins.

Recency Requirement: Current real-time data required from T-12 hours onward; historical baseline data (2020-present) useful for establishing normal variability and defining anomaly thresholds.

Responsible Role Type: Volcanologist & USGS Hazard Forecaster

Steps to Find:

Access Difficulty: Easy. USGS YVO maintains public real-time seismic and GPS dashboards; scientists are typically available for direct consultation and pre-event coordination calls. Data is non-classified and freely available.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: USGS monitoring data cannot be accessed or interpreted in real-time during the critical first 24 hours of the eruption window. Seismic swarms and uplift accelerate faster than weekly reporting cycles can track; the UC lacks numerical trigger thresholds and cannot authorize the Scenario Beta 500 km order, leaving outer-ring residents (tens of thousands to potentially low hundreds of thousands) without evacuation instructions. Uncontrolled, unguided shadow evacuation begins within 6–12 hours, saturating I-15, I-80 and I-90 with hundreds of thousands of private vehicles. The resulting gridlock prevents the organized evacuation of Zone One (35,800 park evacuees), strands ambulances and hospital transport in traffic, and delays water and fuel convoys beyond 48 hours. An estimated 50–200 preventable deaths result from heat stress, dehydration, respiratory distress and untreated medical emergencies in stalled vehicles. The USGS data gap is the single-point failure that cascades through command, shelter, medical and logistics levers, rendering the entire evacuation plan inoperable.

Best Case Scenario: USGS provides real-time seismic, GPS and gas-emission data to the Unified Command every 1–4 hours, with a named volcanologist seated at the forward element and weekly formal briefings. Trigger thresholds—baseline normal ranges, precursor criteria and the VEI-6+ probability metric—are pre-authorized and embedded in the UC's decision protocol by Month 1 (2026-11-14). When magma signatures cross thresholds at T+3–T+12 hours (within the 72-hour window), the UC issues the Scenario Beta order within 30 minutes, activating the pre-authorized 500 km evacuation rings and secondary-hub destination list. Outer-ring residents receive consistent, credible messages explaining the escalation logic, follow time-banded departure instructions and reach pre-designated secondary hubs (Denver, Cheyenne) via lateral routes. Zone One evacuation completes by T+24 hours; Zone Zero by T+6 hours. Water and fuel convoys arrive on schedule. An estimated 100,000–500,000 additional evacuees beyond Zone One are sheltered safely, ashfall is tracked in real-time and shelter relocations (if needed) occur within 4 hours. Zero preventable deaths attributable to evacuation delays or Scenario Beta decision latency.

Fallback Alternative Approaches:

Find Document 2: NOAA Volcanic Ash Forecast Transport (VAFT) Model Outputs and Wind Forecast Data

ID: 7c60f88d-38a4-4f23-a83c-d28f45f81bfa

Description: Current and historical ashfall-dispersion model output from NOAA's Volcanic Ash Forecast Transport system, showing predicted PM10 concentrations at multiple altitudes and distances from Yellowstone Caldera under various eruption scenarios and wind profiles. Includes 12-hour wind forecasts from Global Forecast System (GFS) and high-resolution local models. Serves as the input for the Shelter Siting Decision Rule (T+6h) and dynamic relocation protocols. Intended audience: Ashfall Forecasting Officer, shelter managers, air-quality specialists. Context: forecast uncertainty is estimated at ±50 km; pre-event access and testing of model output is essential to validating shelter-siting thresholds.

Recency Requirement: Current wind forecasts and VAFT model updates required every 3-6 hours from T-24h through T+72h. Historical ashfall-plume scenarios (e.g., Mount St. Helens 1980, Eyjafjallajökull 2010) useful for model validation and sensitivity analysis.

Responsible Role Type: Ashfall Forecasting and Dynamic Shelter-Siting Officer / Volcanologist & USGS Hazard Forecaster

Steps to Find:

Access Difficulty: Medium. VAFT model output is available through NOAA, but requires pre-event data-sharing agreements and specific request for Yellowstone-scenario initialization. Wind forecasts are freely available from NCEP.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Pre-event VAFT model access is not established, model output format is unclear, and no data-sharing agreement is in place when Month 0 (2026-10-14) begins. At T+6 hours, the Ashfall Forecasting Officer requests the latest model output but encounters a 2–4 hour NOAA data-processing delay or network outage, forcing shelter-siting decisions to be made on a 12-hour-old forecast. Actual ashfall at T+12 hours diverges sharply from the obsolete forecast, placing 20,000 evacuees in heavy ash (PM10 >200 µg/m³). By T+18 hours, respiratory distress cases at the primary shelter exceed hospital capacity, and the UC orders emergency relocation. The chaotic 6-hour relocation consumes half the available buses, doubles the shelter intake processing time, and strands 500–1,000 evacuees awaiting transport. An estimated 10–20 preventable respiratory-distress hospitalizations and 1–3 deaths occur during the relocation window and its aftermath. Simultaneously, loss of VAFT output after T+24 hours (due to NCEP server failure or ash contamination of local NWS equipment) leaves the UC without an objective basis for further shelter adjustments, forcing decisions based on visual ash depth and evacuation reports alone.

Best Case Scenario: NOAA VAFT model output and GFS wind forecasts are pre-tested and integrated into the forward UC common operating picture by Month 2 (2026-12-14). A signed data-sharing agreement ensures 3-hourly VAFT updates and 12-hour wind-forecast products flow directly to the Ashfall Forecasting Officer from T-24 hours through T+72 hours. At T+6 hours, shelter-siting decisions are made on a current forecast with clearly documented uncertainty bounds (±40 km for VEI-6 scenario under typical wind patterns). Real-time PM10 sensors at each shelter validate forecast accuracy within ±15 µg/m³. When actual ashfall at T+12 hours closely matches the T+6 forecast, evacuee confidence in shelter locations remains high, reducing unplanned departures. A ranked backup shelter 50+ km upwind remains available but is not needed. By T+24 hours, the UC confirms that all three shelters remain suitable under the latest VAFT forecast, eliminating relocation overhead and preserving bus and medical-response capacity for actual emergencies. The Ashfall Forecasting Officer's timely, accurate briefings sustain UC and public trust through the full 72-hour window and any Scenario Beta extension.

Fallback Alternative Approaches:

Find Document 3: Current Yellowstone National Park Visitor and Staff Census Data

ID: 5bada706-5efa-40fe-848c-e249d21d9790

Description: Current visitor census data for Yellowstone National Park: estimated daily visitor counts by season, lodging occupancy (via Xanterra concession records), campground registrations, backcountry permit issuance rates, and staff employment counts. Provides baseline for the 35,000 tourists and 800 staff estimate in the canonical facts, and enables refinement of shelter-capacity requirements if actual occupancy differs from assumption. Intended audience: Project Manager, shelter planners, population-estimators. Context: the plan assumes 35,800 evacuees for Zone Zero; if actual peak-season occupancy is higher or lower, shelter and corridor capacity calculations must be adjusted.

Recency Requirement: Most recent available year (2024–2025 season data preferred); monthly breakdowns to identify peak occupancy periods and seasonal variation.

Responsible Role Type: Project Manager / Shelter Planner

Steps to Find:

Access Difficulty: Easy. NPS maintains public visitor-use statistics on its website; Xanterra occupancy data can be requested through official channels (pre-event coordination).

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: If census data is unavailable or significantly underestimates peak occupancy, the plan may have sized shelters for 35,800 people when actual evacuation demand is 45,000–55,000. A 15,000–20,000 person shortfall in shelter capacity forces either overcrowding with 50–100 additional deaths from dehydration, respiratory distress or medical decompensation, or secondary emergency shelter activation requiring 6–12 additional hours and USD 10–20 million unplanned expenditure. Simultaneously, an underestimate of backcountry permits could leave 200–300 unaccounted hikers, triggering a large-scale SAR operation during ashfall and exposing rescuers to life-threatening conditions. The plan's credibility with public, governors and media collapses if the initial shelter capacity proves demonstrably inadequate within 12 hours of activation.

Best Case Scenario: Current, validated census data confirms the 35,800 baseline as accurate or conservatively high, allowing the plan to size shelters with high confidence and allocate the three-exit split (West 50%, North 30%, East 20%) proportionally to actual lodging and visitor distributions. Backcountry permit data enables a precise sweep strategy and reduces the unaccounted population to <50 people, eliminating last-person-out risk. Visitor-origin and language data refine multilingual alerts to match actual populations, reducing non-compliance and evacuation delays among non-English speakers. Seasonal occupancy patterns identify the time of year when the plan's capacity margins are tightest, enabling prioritized readiness exercises and supply checks for that season.

Fallback Alternative Approaches:

Find Document 4: Zone One Registered Resident Population Census (West Yellowstone, Gardiner, Cody and Surrounding 100 km Radius)

ID: 773771a1-c3cc-4223-9215-45c3086368c1

Description: Registered resident population data for communities within 100 km of Yellowstone Caldera center: West Yellowstone (Madison County, MT), Gardiner (Park County, MT), Cody (Park County, WY) and surrounding unincorporated areas. Includes baseline population (permanent residents), seasonal residents, and transient populations (hotels, RVs). Serves as the denominator for Zone One evacuation success metrics (Gate G2: 95% of registered residents out by T+24h). Intended audience: Project Manager, Zone One evacuation coordinator, shelter capacity planner. Context: the canonical facts list Zone One as 'not quantified'; a census is required by T+6h to confirm shelter capacity is adequate.

Recency Requirement: Most recent decennial Census (2020 Census data from U.S. Census Bureau); supplemented with county population estimates for 2024–2025.

Responsible Role Type: Project Manager / Emergency Manager (MT, WY counties)

Steps to Find:

Access Difficulty: Easy. U.S. Census data is freely available; county population data can be requested from county emergency managers. Seasonal-occupancy estimates require chamber-of-commerce coordination but are typically available.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Zone One resident population is unquantified at T+0 hours. Shelter capacity planning assumes 25,000–35,000 occupants based on the 2020 Census plus estimates of seasonal residents and tourists. At T+6 hours, when Gate G2 requires confirmation that 95% of registered residents are out, the incident commander cannot verify this metric because no authoritative current census exists. Meanwhile, actual occupancy at gateway communities may be 40,000–45,000 (peak season, 50% above estimate), overwhelming pre-staged shelters designed for 35,800. Unaccounted-for evacuees (5,000–10,000 people) cluster at secondary shelters and lodging outside the plan, creating shadow evacuation that saturates roads to Billings and Salt Lake City and delays organized medical evacuation by 4–6 hours. Two to five preventable deaths occur due to delayed shelter intake and respiratory care.

Best Case Scenario: A current census of West Yellowstone, Gardiner, Cody and surrounding 100 km radius is obtained from county emergency-management offices and the 2020 Census by T+0 hours. Seasonal-occupancy data from chambers of commerce confirm that peak-season (October 2026) transient population adds 3,000–5,000 to the baseline resident count, yielding a Zone One total of 12,000–18,000 registered residents and estimated 17,000–23,000 actual occupants including tourists. Shelter capacity planning is right-sized to 35,800 (Bozeman 15,000, Idaho Falls 10,000, third site 10,800), with no excess or shortage. A T+6 hour census-update protocol (rapid phone survey or online form) confirms that 95% of registered residents have exited, supporting Gate G2 approval. Perimeter enforcement and Scenario Beta escalation proceed without delay. No shelter relocations are needed; all evacuees reach adequate intake and medical triage within 4 hours.

Fallback Alternative Approaches:

Find Document 5: Existing Regional Hospital Bed Capacity, Emergency Department Surge Plans and Current Staffing Rosters

ID: 5107aec8-e81d-4dd8-91f0-21ce7950c3f6

Description: Current bed-capacity inventories, emergency-department surge protocols and staffing rosters for the three designated receiving hospitals (Bozeman Deaconess Medical Center, Livingston HealthCare, Eastern Idaho Regional Medical Center, Idaho Falls). Includes baseline bed counts (ICU, trauma, respiratory), current staffing (emergency physicians, respiratory therapists, nurses), and any existing mass-casualty or disaster-surge expansion plans. Serves as input for hospital-surge dispersal planning and identification of pre-emptive patient transfers. Intended audience: Hospital Surge Dispersal Officer, hospital administrators, public health officer. Context: the plan assumes base surge capacity at three hospitals; this data enables real capacity validation and identification of staffing gaps.

Recency Requirement: Current (2024–2025) hospital census data, bed-capacity inventories and staffing rosters.

Responsible Role Type: Public Health & Mass-Casualty Medical Logistics Director / Hospital Administrator

Steps to Find:

Access Difficulty: Medium. Hospital bed-capacity and staffing data are sensitive (federal reporting required for Medicare facilities); access requires pre-event formal coordination and confidentiality agreements. State health departments may have aggregate data available.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: ">A hospital surge plan based on inaccurate or outdated bed-capacity and staffing data could result in one or more receiving hospitals reaching functional capacity by T+12 to T+18 hours (during peak ashfall), after which new emergency patients cannot be admitted. Ambulances divert to distant facilities 100+ km away, extending transport times to 2–4 hours and leaving severe respiratory-distress and trauma patients untreated for critical periods. If respiratory-therapist shortages prevent full ventilator deployment, 10–20 patients with salvageable acute respiratory distress die due to lack of available mechanical ventilation. A power loss at one hospital coupled with delayed fuel-convoy arrival (due to inaccurate logistics assumptions) extends the outage to 4–6 hours, forcing manual ventilation and cancellation of surgeries, with an additional 5–10 preventable deaths. The cascade of hospital failures erodes public confidence in the medical response, increases uncontrolled flight from shelter to distant hospitals and reduces compliance with evacuation orders, adding 2–4 hours to overall evacuation time. Estimated worst-case: 20–50 preventable hospital deaths, 1,000–3,000 patients in delayed or degraded care, regional medical system destabilization lasting weeks.

Best Case Scenario: ">With accurate, current hospital bed-capacity and staffing data, the Hospital Surge Dispersal Officer can validate and right-size patient-distribution assignments, ensuring each of the three receiving hospitals is loaded to realistic surge capacity without overcrowding. Pre-existing surge protocols and staffing agreements are identified and integrated into the response plan, enabling smooth activation of additional beds and staff within the first 2–4 hours of patient arrival. Backup hospitals outside the three named facilities are confirmed and pre-briefed, providing a fallback if one facility faces capacity or power constraints. Respiratory-therapist and ventilator surge agreements are formalized by Month 1 (2026-11-14), eliminating uncertainty and enabling rapid deployment of travel staff or shared equipment during peak demand. EMS routing is optimized so ambulances reach appropriate receiving hospitals within 45–60 minutes, reducing out-of-hospital time and enabling early intervention. All 500–2,000 modeled respiratory-distress cases receive timely admission and mechanical ventilation; trauma and chronic-disease patients are distributed evenly across the network. Hospital power and life-support systems remain operational throughout the 72-hour event due to pre-positioned fuel reserves and proven generator startup protocols. Estimated best case: zero preventable hospital deaths, all acutely ill patients receive appropriate care within the modeled system capacity, regional medical system maintains public confidence and operational continuity.

Fallback Alternative Approaches:

Find Document 6: Existing Yellowstone National Park Concessioner Operational Data (Lodging Occupancy, Staff Rosters, Transportation Fleet)

ID: d57f35c4-4e32-43dd-a64b-a8b280ab4b13

Description: Operational data from Xanterra Parks and Resorts (primary NPS concessioner): current guest-room inventory and occupancy forecasts, staff employment rosters (count and job functions), shuttle-bus fleet capacity and scheduling, and visitor-transportation logistics. Serves as input for visitor-needs assessment (language, mobility, vehicle-less populations) and assisted-evacuation planning. Intended audience: Communications Coordinator, visitor-needs planner, transportation logistics officer. Context: concessioners manage ~90% of visitor accommodation and some visitor transport; pre-event data access enables targeted multilingual outreach and transport pre-positioning.

Recency Requirement: Current (2024–2025 season) occupancy forecasts, staff rosters and fleet inventory.

Responsible Role Type: Communications and Public Alerting Coordinator / Shelter Planner

Steps to Find:

Access Difficulty: Medium. Concessioner operational data is sensitive (commercially confidential for occupancy and forecasts); requires signed data-sharing agreement with Xanterra and NPS. Pre-event coordination is expected and typically feasible.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Concessioner operational data is unavailable until T+6 hours or is incomplete (missing staff lists, guest languages, vehicle-less population), forcing real-time guest identification via manual lodge surveys during the evacuation peak. As a result, up to 10,000–15,000 non-English-speaking or vehicle-less guests receive no pre-evacuation briefing, experience delays of 2–4 hours in understanding route instructions or boarding evacuation shuttles, and some become separated from their transportation groups. Approximately 200–500 guests are stranded at lodges or trailheads when shuttles depart without confirmation of occupancy, requiring secondary rescue operations after T+6 h. This gap also prevents pre-identification of multilingual staff and experienced drivers, forcing ad-hoc recruitment of volunteers during the evacuation, reducing the reliability and speed of assisted-evacuation shuttles and multilingual outreach. The combination results in an estimated 2–4 hour delay in Zone Zero clearance and 5–10 preventable casualties among elderly, mobility-limited or medically fragile guests.

Best Case Scenario: Concessioner operational data is obtained by Month 0 (2026-10-14) via a pre-signed data-sharing agreement, providing current occupancy forecasts, complete staff rosters, shuttle-bus schedules and guest-language preferences. This enables pre-production of multilingual briefing materials, pre-identification of 20–50 multilingual staff and experienced drivers, pre-assignment of shuttle buses to lodges, and advance preparation of priority-evacuation staging areas for mobility-limited guests. At T+0, lodge staff can immediately brief guests in their preferred languages using pre-produced materials, and evacuations begin with confirmed transportation arrangements. Vehicle-less guests and those with mobility or medical needs are staged for priority-evacuation shuttles before general traffic departs, reducing bottlenecks. Evacuation of non-English-speaking guests is accelerated to 30–45 minutes per lodge, and Zone Zero clearance is achieved within 5.5 hours, providing a safety margin before ashfall intensity increases. Approximately 99% of 35,800 evacuees depart with clear instructions and assigned transportation, avoiding stranding incidents.

Fallback Alternative Approaches:

Find Document 7: Bottled Water, N95 Respirator, Generator Fuel and Emergency Supply Industry Capacity and Pricing Data

ID: a333ea0c-28d1-45b6-9a43-4b13f85482c9

Description: Current industry capacity and pricing for emergency supplies: bottled-water production and distribution capacity in the Mountain West (estimated liters per day from major suppliers), N95 respirator stock and manufacturing capacity (units available for emergency order), diesel generator fuel distribution networks and regional storage capacity, and medical/shelter equipment availability (cots, blankets, food, hygiene kits). Serves as input for supply-chain feasibility assessment and contract-negotiation planning. Intended audience: Emergency Logistics and Supply-Chain Director, procurement officer. Context: the plan assumes 1.43 million liters water, 100,000+ N95 masks, 72-hour generator fuel at hospitals; this data validates supply-chain feasibility and lead times.

Recency Requirement: Current (2024–2025) industry capacity estimates, lead times and pricing; supply-chain disruption data post-COVID.

Responsible Role Type: Supply Chain & Logistical Resilience Strategist

Steps to Find:

Access Difficulty: Medium. Industry data is commercially sensitive; requires direct corporate inquiry and pre-event negotiations. State emergency management agencies may have supplier contact rosters from prior disaster agreements.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Industry data is unavailable, severely outdated or commercially withheld, forcing the plan to assume worst-case lead times and capacity constraints at Month 0 (2026-10-14) (T+0). Convoys dispatch 12–24 hours late due to unknowable supplier constraints; N95 stock proves insufficient by T+48 h and cannot be rapidly resupplied; hospital fuel reserves fall short of 72-hour needs. Shelters experience water shortages from T+24 to T+36 h affecting 15,000–20,000 evacuees, and respiratory-protection gaps leave thousands unmasked during peak ashfall. These shortfalls force emergency procurement at 2–3x normal cost, consuming the USD 40 million contingency within 24 hours and leaving no reserve for shelter relocation, Scenario Beta hub staging or additional responder calls. The plan's credibility with shelter operators and host communities collapses, reducing voluntary compliance with evacuation and shelter-placement orders by 15–20%.

Best Case Scenario: Current industry capacity and pre-event pricing data are obtained from all major suppliers by Month 1 (2026-11-14), confirming that water convoys can be mobilized within 12 hours from Salt Lake City and arrive at shelters by T+18–T+24 h (within acceptable bounds). N95 manufacturers confirm 200,000–300,000 units available for emergency order, doubling the civilian stock. FEMA contract vehicles include 15–20 pre-authorized fuel and water vendors, enabling verbal activation and guaranteed 12-hour dispatch. Pricing for all supplies is locked in advance at 2024–2025 commercial rates. These confirmations allow the plan's supply-chain milestones to proceed on schedule: forward depots stocked by T-12 h (within the 72-hour window), no bottleneck delays, and USD 15–25 million of the USD 40 million contingency freed for Scenario Beta hub pre-positioning and shelter-relocation reserves.

Fallback Alternative Approaches:

Find Document 8: FEMA Region 8 and Region 10 Mutual Aid and Emergency Support Function (ESF) Resource Inventories

ID: 425089ab-8957-4fc5-8b04-e28ea2697075

Description: Current mutual-aid rosters and Emergency Support Function resource inventories for FEMA Regions 8 (Denver, covering Colorado, Montana, North Dakota, South Dakota, Utah, Wyoming) and Region 10 (Seattle, covering Alaska, Idaho, Oregon, Washington). Includes Guard unit locations and availability, pre-positioned supply stocks, medical-surge resources and transportation capacity. Serves as input for responder relief depth, supply-chain and military-asset pre-positioning planning. Intended audience: UC Incident Commander, Region 10 Liaison Officer, logistics directors. Context: the plan assumes access to Guard units and mutual-aid resources; this documentation enables specific asset identification and pre-event commitments.

Recency Requirement: Current (2024–2025) mutual-aid rosters and ESF inventories; any recent updates to unit locations or resource availability.

Responsible Role Type: Regional Emergency Management & Multi-Jurisdiction Coordination Director / FEMA Region 10 Liaison Officer

Steps to Find:

Access Difficulty: Medium. FEMA regional resource data is partially restricted (Guard unit locations may be sensitive); requires pre-event formal coordination with FEMA regional administrators. State emergency management agencies maintain public mutual-aid rosters.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Without current, verified mutual-aid rosters and ESF inventories, the Unified Command cannot pre-authorize specific Guard units, helicopters, medical surge or fuel convoys at T+0, forcing real-time scavenging of resources during the 72-hour evacuation window. A discovery that assumed assets are unavailable, committed elsewhere or incompatible cascades into delays: medical patients are held at shelters 2–4 hours waiting for ambulances that must be summoned ad hoc; water convoys discover depots lack trucking and loading equipment, delaying arrival from T+12 h to T+24+ h; National Guard signal teams discover radios are on incompatible frequencies, forcing 2–4 hours of field coordination when digital comms fail. These delays—multiplied across 35,800 evacuees, 15,000 at shelters, 5–10 hospitals and 10+ control points—extend the evacuation peak by 4–8 hours, overlapping ashfall onset and increasing respiratory casualties by 50–100+ people and stranding 1,000–3,000 evacuees without shelter or water. A regional mutual-aid freeze due to cost-sharing disputes could reduce available personnel and fuel by 30–50%, making the plan execution-impossible. Estimated total impact: failed evacuation, estimated 50–200+ preventable deaths, multi-state incident escalation and international attention on a catastrophic response failure.

Best Case Scenario: Current, verified mutual-aid rosters and ESF inventories enable the Unified Command to seat a FEMA Region 10 liaison at T+0 and pre-authorize specific Guard units (e.g., Colorado 10th Special Forces Group signal platoons, Wyoming Army Guard transportation company, Idaho National Guard medical team) with confirmed personnel counts, equipment and deployment times. Pre-coordinated cost-sharing and mutual-aid agreements remove the need for approval chains, allowing verbal resource requests to move from the forward command to regional duty officers with 30-minute response times. Helicopters, ambulances and fuel convoys are committed in writing 60 days before the event, so requests trigger pre-authorized dispatch rather than ad hoc searches. Medical surge and field hospital availability is confirmed, allowing the plan to size evacuation-shelter medical staffing with confidence. Interoperable communications equipment (radios on pre-coordinated frequencies, satellite terminals tested) is pre-positioned, so signal teams activate systems quickly rather than troubleshooting compatibility. Water and fuel convoys depart on schedule from verified depots with confirmed trucking and loading, arriving at shelters within the T+24 h target. The effect: the plan executes with predictability, responders know their resources are committed, decision latency drops from ad hoc hours to minutes, and the evacuation completes by T+6 h without stranded evacuees or supply shortfalls. Estimated total impact: evacuations complete, water and medical resources sustain shelters, fewer than 10 preventable casualties, confidence in the response and international recognition of effective disaster coordination.

Fallback Alternative Approaches:

Find Document 9: Montana, Wyoming and Idaho Governor Emergency Declaration Authorities and State Emergency Management Plans

ID: 95aae559-8fd0-460b-a695-9a7e484c887e

Description: Current state emergency-management plans, governor emergency-declaration authorities and automatic mutual-aid activation procedures for Montana, Wyoming and Idaho. Includes state-specific evacuation protocols, National Guard mobilization procedures and cost-sharing rules for emergency response. Serves as input for Command Structure and Authority Framework and Stafford Act cost-allocation negotiations. Intended audience: UC Incident Commander, governors' representatives, emergency managers. Context: the plan requires governor pre-authorization (verbal by T+6h, signed by Month 1 = 2026-11-14); this documentation clarifies state-level procedures and legal authorities.

Recency Requirement: Current (2024–2025) state emergency-management plans and governor executive orders governing emergency declarations.

Responsible Role Type: Regional Emergency Management & Multi-Jurisdiction Coordination Director

Steps to Find:

Access Difficulty: Easy. State emergency-management plans are typically public documents or available through formal request. Governor offices maintain public lists of emergency contacts.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: At T+0 hours, the Unified Command activates at the Denver RRCC and issues the verbal evacuation order for Zone One, assuming governors' pre-authorization is already in place. However, upon contact, the governors or their legal counsel challenge the NPS incident commander's authority to direct traffic control and shelter placement in their states, citing state constitutional limits on federal authority or existing state laws that require governor approval for contraflow operations. This dispute delays the issuance of formal evacuation orders by 2–4 hours. Simultaneously, unclear National Guard mobilization procedures prevent rapid deployment of additional traffic-control personnel; the UC cannot confirm whether out-of-state Guard can be deployed without explicit additional authorization from each state adjutant general. By T+6 hours, the West Yellowstone corridor experiences a gridlock backup affecting 5,000–8,000 vehicles, and no Guard reinforcements are available to expand traffic-control coverage. Evacuation time slips to T+8 to T+10 hours, and ashfall onset within this window increases respiratory distress cases by 10–20. Additionally, disputes over cost-sharing and fuel-handling regulations delay water and fuel convoy dispatch from Salt Lake City by 12+ hours, leaving shelters without adequate supply when evacuees arrive by T+8 to T+12 hours. Overall estimated impact: 2–4 hour evacuation delay, 10–20 additional respiratory distress casualties, 1–3 critical supply shortages at shelters, and erosion of public trust due to visible command confusion and inter-state conflict.

Best Case Scenario: The current state emergency-management plans clearly specify that governors' verbal authorization of evacuation orders is valid under each state's declaration authority, and pre-authorized MOUs are already in place confirming federal NPS incident commander authority over contraflow and initial shelter placement until a formal handoff order is issued. National Guard mobilization is streamlined and can proceed with out-of-state deployment via EMAC with a single phone call to each state adjutant general, removing any delay. Cost-sharing is explicitly documented (e.g., 75% federal/25% state), making budget authority clear and allowing the UC to confidently authorize procurement within the USD 200 million envelope. Contact information for state emergency managers and governors' liaisons is current, enabling real-time coordination without research delays. By T+0 hours, the UC confirms verbal authorization with all three governors, activates contraflow without legal disputes, and requests Guard reinforcements immediately; all three state emergency managers are actively coordinated into the response and provide rapid approvals for fuel, water and shelter logistics. Water and fuel convoys dispatch from Salt Lake City by T+12 hours as planned, and shelters are fully staffed and prepared by T+24 hours. The boundary authority transfer occurs smoothly at defined checkpoints, with no command gaps or reroute delays. Evacuation proceeds at planned pace: 98% of Zone Zero cleared by T+6h, 95% of Zone One by T+24h, and Scenario Beta interim destination list issued on schedule.

Fallback Alternative Approaches:

Find Document 10: Current and Historical Seismic and Hydrothermal Hazard Maps for Yellowstone Caldera Region (USGS HazMaps, Slope-Stability Assessments)

ID: f42ce734-7f7e-479a-b1be-9546a9a1567b

Description: Existing USGS hazard maps showing seismic epicenter distributions, slope-stability assessments and hydrothermal-explosion zones within Yellowstone National Park. Includes Gallatin Canyon and US-89 corridor geotechnical surveys (if available) and any documented secondary-slide or hydrothermal-explosion events. Serves as input for Landslide Clearance and Hydrothermal Hazard Road Engineering planning. Intended audience: Geotechnical engineer, transportation planner. Context: the plan assumes Gallatin Canyon and US-89 have secondary-slide risk and the South Entrance has current blockage; this documentation enables specific hazard-zone mapping and equipment pre-positioning.

Recency Requirement: Current (2010–2025) USGS hazard maps and geotechnical assessments for the Yellowstone region.

Responsible Role Type: Transportation Operations & Contraflow Specialist / Geotechnical Engineer

Steps to Find:

Access Difficulty: Easy. USGS hazard maps are publicly available online. State geological surveys maintain geotechnical databases; access may require formal request but is typically available to emergency planners.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: The Scenario Beta trigger fires (VEI-7 probability crosses a threshold), but the written trigger matrix has not been finalized or pre-authorized. The Unified Command must convene an emergency decision cell to interpret the USGS data and vote on the 500 km order. This process takes 2–4 hours (estimate), during which uncontrolled outer-ring evacuation from Bozeman, Billings and Idaho Falls saturates I-15 and I-90. By the time the order is issued, 50,000–200,000 unplanned evacuees are already on the roads (estimate), gridlock prevents the organized Zone One evacuation of the 35,000 park visitors from reaching the primary shelters by T+24 hours, and secondary rescue of stranded evacuees and medical patients becomes necessary. The absence of second-stage hub destinations compounds the chaos: evacuees fleeing the 500 km ring have no published shelter, driving further uncontrolled dispersal. Final outcome: 4–8 hour evacuation delay, 500–2,000 stranded or injured evacuees, 5–15 preventable deaths in hospital transport delays, and erosion of public trust that undermines future emergency messaging.

Best Case Scenario: The trigger matrix is finalized and pre-authorized by T+0 hours, with USGS committed to hourly updates of the nominated indicators (e.g., uplift rate, gas flux, tremor magnitude) transmitted to the Unified Command. A VEI-7 probability crosses the threshold at T+18 hours. The Unified Command confirms receipt of the USGS data within 10 minutes, issues the 500 km order within 30 minutes (proposed threshold), and IPAWS broadcasts the order in English and five languages within 45 minutes. State governors issue immediate downstream enforcement orders, and the ranked second-stage hub list (Denver, Cheyenne, and three backups outside the 500 km ring) is already pre-authorized, allowing the UC to direct outer-ring evacuees to named destinations. Corridor overflow is diverted to secondary routes before gridlock forms, Zone One evacuees reach primary shelters by T+24 hours, and secondary hubs are staffed and receiving outer-ring evacuees by T+36 hours. Public trust remains intact because the messaging was credible and pre-announced. Outcome: all 35,000 Zone One tourists and 100,000–500,000 additional Beta-ring evacuees reach shelter without major casualties or stranding.

Fallback Alternative Approaches:

Find Document 11: Regional Ground Transportation Network Capacity Data (I-15, I-80, I-90, US-20, US-89, US-14/16/20 Lane Counts, Capacity Analysis)

ID: 20ac35b9-2dc9-4dbb-871c-eeac47d3a083

Description: Detailed highway-capacity data for the primary evacuation routes: Interstate 15 northbound from Salt Lake City to Idaho Falls, Interstate 90 from West Yellowstone/Bozeman to the Livingston area, US-89 from Gardiner to Livingston and I-90, and US-14/16/20 from Cody to Billings and I-90. Includes lane counts, current average daily traffic (ADT), estimated maximum capacity (vehicles per hour per lane), known bottleneck locations (e.g., Gallatin Canyon, mountain passes) and any current or planned construction. Serves as input for contraflow design, throughput validation and evacuation-time estimation. Intended audience: Contraflow Operations Manager, transportation planner. Context: the plan assumes 2,000 vehicles/hour total outbound (660 per exit average), but this must be validated against actual corridor capacity, especially if roads degrade under ashfall or evacuation traffic congestion.

Recency Requirement: Current (2024–2025) highway data: lane counts, construction status, average daily traffic; historical capacity studies from the last 5 years.

Responsible Role Type: Transportation Operations & Contraflow Specialist

Steps to Find:

Access Difficulty: Easy. State DOT traffic data is publicly available; historical ADT and capacity analyses can be requested from state DOT planning divisions.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Actual corridor capacity is 1,500 vehicles/hour (not validated), and ashfall reduces it by 40% to 900 vehicles/hour. The plan's 11,900-vehicle total load at 2,000 vehicles/hour takes 6 hours under ideal conditions; under realistic ashfall-degraded capacity, it requires 13+ hours. Evacuation extends from the planned T+6 hours to T+13+ hours, with peak outbound traffic occurring at T+6 to T+13, exactly when ashfall intensity is rising. Simultaneous failure of one corridor (blockage in Gallatin Canyon) reduces throughput to 1,200 vehicles/hour across two exits, extending evacuation to 10+ hours and stranding 3,000–5,000 vehicles in moderate to heavy ashfall. Result: 500–1,500 additional respiratory-distress incidents and 10–30 preventable deaths.

Best Case Scenario: Detailed capacity data confirms that all three corridors can sustain 2,000+ vehicles/hour even under ashfall-degraded conditions, and that Gallatin Canyon and Gardiner canyon have sufficient width for rapid debris clearance (15–30 minutes typical). The planned three-way gate split (West 50%, North 30%, East 20%) aligns with each corridor's actual capacity, ensuring balanced load distribution. Evacuation proceeds on schedule, Zone Zero is cleared by T+6 hours with fewer than 500 stranded or delayed evacuees, and the three-exit design proves to be the decisive factor in achieving the T+6 clearance deadline. Credible capacity data also enables the forward command to adjust the gate-load split in real time if one corridor experiences congestion, preventing a bottleneck cascade.

Fallback Alternative Approaches:

Find Document 12: Residential and Transient Population Data for Secondary-Hub Communities (Denver, Cheyenne, Billings, Boise, Salt Lake City, Rapid City)

ID: e9feecf9-33d2-46e8-b74c-33e98fb07815

Description: Current residential population, hotel/lodging capacity, campground capacity and available emergency-shelter facility inventory for candidate Scenario Beta secondary-hub communities outside the 500 km ring (Denver, Cheyenne, Billings, Boise, Salt Lake City, Rapid City). Includes gym/arena availability, school facility capacity and organizational capacity (Red Cross, Salvation Army) to operate shelters. Serves as input for Scenario Beta secondary-stage hub selection and signed capacity MOUs. Intended audience: Scenario Beta Destination Planner, shelter planners. Context: the plan names Denver and Cheyenne as candidate hubs but has not verified distance or capacity; this data enables validation and ranking of backup hubs.

Recency Requirement: Current (2024–2025) facility inventories, hotel/RV-park capacity and community emergency-management resource listings.

Responsible Role Type: Scenario Beta Secondary-Stage Destination Planner

Steps to Find:

Access Difficulty: Easy. City emergency management agencies maintain public shelter-facility rosters; chamber-of-commerce lodging data is publicly available.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: Scenario Beta trigger fires at T+12 hours. The plan has no verified secondary-hub list: candidate hubs (Denver, Cheyenne, Billings) have not been confirmed as outside the 500 km ring or evaluated for capacity and accessibility. Over the next 12–24 hours, 50,000–200,000 unplanned evacuees from the 100–500 km ring converge on the nearest major towns (Billings, Bozeman, Idaho Falls, Salt Lake City), all of which are inside the Scenario Beta zone or have been overtaxed by primary-stage evacuees. No pre-arranged hub coordination or capacity commitment exists. Evacuees cluster in parking lots, schools and fairgrounds without registration, food service or medical triage. Regional hospitals face a secondary surge of 1,000–3,000 patients with respiratory distress and heat-stress casualties. Without onward-movement routes and host-hub agreements, primary shelters cannot release evacuees to secondary hubs, leaving tens of thousands stranded in ash-exposed zones for 24–48 hours. Estimated casualties: 50–200 preventable respiratory and heat-stress deaths; estimated cost of emergency response: USD 200–500 million in unplanned shelter operations, medical response and evacuation rerouting.

Best Case Scenario: The Residential and Transient Population Data document provides verified current (2024–2025) shelter-facility inventories, lodging capacity and organizational capacity for at least five candidate secondary hubs (Denver, Cheyenne, Billings, Boise, Salt Lake City). Each hub is confirmed outside the 500 km ring with measured distance from Yellowstone. Red Cross and Salvation Army chapters are contacted; pre-event capacity commitments are signed by Month 2 (2026-12-14). A ranking of hubs by distance, capacity and accessibility is published, enabling the Scenario Beta Secondary-Stage Destination Planner to assign evacuation rings (100–250 km, 250–500 km) to specific hubs and pre-position buses and logistical staff. When a Scenario Beta trigger fires, evacuees are directed to named hubs with published shelter addresses, expected arrival times and intake processes. Onward-movement routes via lateral highways are confirmed passable and fuel-stocked. Secondary hubs absorb 100,000–500,000 evacuees over 24–48 hours with minimal additional casualties. Evacuee confidence in the plan increases, reducing shadow evacuation and corridor saturation. Estimated outcome: <10 preventable deaths in secondary-hub operations, USD 50–100 million in planned sheltering costs, and reduced emergency contingency draws.

Fallback Alternative Approaches:

Find Document 13: Utility System Infrastructure and Power-Grid Topology for Montana, Wyoming and Idaho (Transmission Lines, Substations, Ash-Flashover Risk Assessment)

ID: 3c23d3db-0621-4b02-9e8f-0775fc3c6de5

Description: Electrical transmission-system maps and substation locations for Montana-Dakota Utilities, Pacific Power and Idaho Power service territories covering the Yellowstone region and evacuation routes. Includes transmission-line voltages (115–500 kV), substation locations, backup-generator capacity at critical facilities and any existing ash-flashover or secondary-failure risk assessments. Serves as input for grid-resilience planning and load-shedding procedures. Intended audience: Grid Resilience Engineer, utilities coordinators. Context: the plan assumes grid failure from ash flashovers; this data enables specific vulnerability identification and pre-event protective-relay coordination.

Recency Requirement: Current (2024–2025) transmission-system maps, substation listings and protective-relay settings.

Responsible Role Type: Critical Infrastructure & Grid Resilience Engineer

Steps to Find:

Access Difficulty: Medium. Transmission-system maps are commercially sensitive; require formal data-sharing agreements with utilities. Critical-infrastructure protection considerations may limit public disclosure; pre-event coordination with utilities is standard for emergency planning.

Essential Information:

Risks of Poor Quality:

Worst Case Scenario: A widespread transmission-line flashover event triggered by ashfall ash deposits on insulators occurs within 4 hours of ashfall onset, affecting multiple substations serving Bozeman and Idaho Falls simultaneously. Protective relays malfunction or fail to isolate faulted sections due to ash-clogging or secondary tremor damage, initiating a cascade of failures that blacks out the entire region within 8–12 hours. Hospitals lose grid power before fuel convoys can arrive; generator startup procedures fail due to outdated equipment or maintenance oversights. Three major hospitals operate for 2–4 hours on backup before fuel runs out, forcing cancellation of 15–25 surgeries, loss of ventilator support for 10–15 patients and 5–10 preventable deaths. Shelters lose water pumping and treatment capability, affecting 35,000+ evacuees. The incident commander lacks real-time visibility into grid status and cannot issue load-shedding orders, leaving repair crews without situational awareness. Total impact: regional crisis compounding medical surge and threatening regional continuity of operations.

Best Case Scenario: Utilities provide current transmission-system maps and confirm substation locations, protective-relay settings and mutual-aid procedures. Pre-event coordination identifies two critical substations serving the shelter zones and confirms mobile generator and voltage-regulation equipment can be pre-deployed 48 hours before the eruption window. Each receiving hospital confirms 72-hour on-site fuel reserves and agrees to emergency fuel contracts with local vendors (arrival within 2 hours of request). A 24/7 utility-operations hotline is established with the forward command element, enabling real-time grid monitoring and load-shedding authorization during ashfall. Hospital generator-startup exercises test manual procedures and identify any mechanical failures in advance. Ashfall does cause transmission-line stress, but pre-positioned mobile generators and load shedding prevent cascading failure; hospitals maintain power and medical surge capacity throughout the 72-hour window. Shelf-life and resupply of fuel, water and medical supplies remain uninterrupted. Regional infrastructure resilience is maintained and no preventable deaths occur due to grid failure.

Fallback Alternative Approaches:

Strengths

Weaknesses

Opportunities

Threats

Recommendations

Strategic Objectives

Assumptions

Missing Information

Questions

Roles Needed & Example People

Roles

1. Unified Command Incident Commander

Contract Type: full_time_employee

Contract Type Justification: The Unified Command Incident Commander is the central decision authority for the entire 72-hour evacuation response, with continuous operational responsibility from T+0 through T+72 hours. This is a core, uninterrupted leadership role requiring constant presence, direct oversight of the forward element, interface with governors and USGS, and real-time decision authority on life-safety matters. The role cannot be shared or interrupted; continuity and accountability demand a salaried full-time position.

Explanation: The Incident Commander serves as the central decision authority for the entire multi-state evacuation response, operating from the FEMA Region VIII RRCC in Denver with direct oversight of the forward UC element in Livingston/Bozeman. This role is critical for issuing evacuation orders, authorizing the pre-authorized Scenario Beta VEI-7 expansion, managing cross-jurisdiction authority transfers between NPS and state governors, and maintaining a shared common operating picture across all agencies. The IC must interface with USGS volcanologists to interpret eruption triggers, authorize Guard signal deployment, and approve resource requests from shelter, hospital and logistics units.

Consequences: Without a single recognized Incident Commander, authority becomes fragmented across NPS, FEMA, state governors and the Forward UC element. Command gaps delay reroutes by 15–45 minutes, conflict resolution at the park boundary halts traffic, and escalation decisions for Scenario Beta are blocked by jurisdictional disputes or meetings that exceed the 30-minute decision window. Estimated impact: 2–4 hour evacuation delay, 500–2,000 stranded vehicles, 5–10 preventable deaths from exposure or medical transport delay.

People Count: 1

Typical Activities: As the UC Incident Commander, Steele operates from the FEMA Region VIII RRCC in Denver, serving as the central decision authority for the entire 72-hour evacuation response. He issues evacuation orders, authorizes pre-authorized Scenario Beta VEI-7 expansion to 500 km, manages cross-jurisdiction authority transfers between NPS and state governors, and maintains the shared common operating picture across all agencies. Steele conducts hourly briefings with the forward UC element in Livingston, the three state on-scene commanders, USGS volcanologists, NOAA forecasters, hospital surge coordinators, and logistics directors. He approves resource requests from shelter, hospital and logistics units, decides on corridor diversion if blockages persist beyond 45 minutes, and authorizes helicopter medevac exceptions to the FAA airspace grounding. Steele tracks burnout and orders responder relief rotations, reviews ashfall and air-quality sensor data at T+6 h when shelter sites are finalized, and prepares escalation decisions for the Scenario Beta trigger matrix by T+3 h.

Background Story: Dr. Marcus Steele is a veteran incident commander from Denver, Colorado, with 28 years in federal emergency management. He earned his MPA from the University of Colorado and has directed responses to the 2013 Colorado wildfires and 2015 South Carolina floods. Known for decisive leadership and cross-jurisdictional coordination, Steele was selected specifically for the Yellowstone response because of his experience managing multi-state unified commands and his established relationships with governors in the Mountain West. He has worked with USGS on earthquake and volcano monitoring and understands the technical triggers that drive volcanic decisions. Steele is deeply familiar with the Stafford Act, FEMA contract vehicles, and the complexities of handling authority handoffs between federal and state agencies at crisis boundaries.

Equipment Needs: Secure communications suite: dedicated satellite phone, encrypted radio (VHF/UHF), laptop with real-time common operating picture access, backup power systems (generator, UPS). Incident command workspace equipped with 4-6 large displays for data integration from USGS, NOAA, Guard signals and shelter status feeds. Printed contraflow route maps, trigger matrix decision cards, and evacuation-zone boundary markers. Real-time PM10/PM2.5 ashfall data feeds integrated into the command display.

Facility Needs: Primary: FEMA Region VIII RRCC in Denver Federal Center (Lakewood, Colorado) with hardened power, redundant internet and satellite links, secure conference capability for governor calls and USGS coordination. Backup command post at Fort Carson (Colorado Springs) with identical systems. 24/7 staffed operations center with adjacent situation room for briefings. Access to a secure video-teleconference capability linking the forward element in Livingston, state EOCs and USGS/NOAA offices. Proximity to federal emergency-declaration authority and logistics coordination.

2. FEMA Region 10 Liaison Officer

Contract Type: full_time_employee

Contract Type Justification: The FEMA Region 10 Liaison Officer maintains 24/7 coordination with Idaho resources and mutual-aid authorities from T+0 through the entire response window (at least 72 hours, potentially extending to Month 1 = 2026-11-14). This is a continuous, critical interface role bridging regional seams. The liaison must be on-site at the Denver RRCC and available for immediate decision-making and resource requests. Full-time employment ensures sustained availability and organizational commitment.

Explanation: This role represents FEMA Region 10 (Seattle, covering Idaho and parts of the Pacific Northwest) at the Denver RRCC and maintains real-time coordination with Idaho State Emergency Management, Pocatello and Boise water/fuel authorities, and regional mutual-aid resources. The Region 10 Liaison ensures that Idaho's evacuation zone (100–500 km radius, depending on Scenario Beta) is served by pre-coordinated water convoys, medical supplies and shelter capacity from the Pocatello and Boise distribution centers, bridging the gap between Denver RRCC (Region 8) and the Idaho-specific resource network. Critical for pre-event MOUs and T+0 activation of Idaho-based mutual aid.

Consequences: Without dedicated Region 10 coordination, Idaho mutual-aid requests routed through the Denver RRCC experience 1–2 hour delays or are not recognized as priority. Water and fuel convoys from Boise and Pocatello are delayed 12–24 hours, leaving shelters at Idaho Falls with insufficient supply for 1–2 days. Estimated impact: 10–20% of evacuees at Idaho Falls lack adequate water for 12–24 hours, increasing risk of heat stress and secondary health incidents; 5–10 preventable dehydration-related casualties if medical care is delayed.

People Count: 1

Typical Activities: As the FEMA Region 10 Liaison Officer, Okafor maintains a 24/7 coordination desk at the Denver RRCC from T+0 through the entire response window. She receives and prioritizes mutual-aid resource requests from Idaho Falls shelters, coordinates with Pocatello and Boise water and fuel authorities to dispatch convoys northbound on US-20 and alternate routes, tracks the arrival time and contents of each inbound Idaho-based supply shipment, and reports status to the UC Incident Commander every 4 hours. Okafor pre-coordinates with Idaho State Emergency Management on pre-authorized mutual-aid resource commitments (water, generators, medical staff) and verifies that host-community MOUs are signed and ready by Month 1 (2026-11-14). During the response, she acts as the voice of Region 10 in Denver, preventing Idaho requests from being deprioritized, and serves as the direct liaison to Governor-authorized operations in Boise and Pocatello. She also manages the timing and routing of any Scenario Beta secondary-stage evacuation transport moving evacuees from Idaho Falls (inside-ring shelter) to Denver or Cheyenne hubs (outside-ring destinations).

Background Story: Jennifer Okafor is a FEMA regional coordinator stationed in Seattle, with expertise in Pacific Northwest disaster logistics and cross-region mutual-aid activation. Born and raised in Boise, Idaho, she holds a degree in public administration from Boise State University and has 15 years of experience managing FEMA Region 10 resources during the 2017 and 2018 wildfire seasons. Okafor is fluent in Spanish and has worked extensively with Idaho's Pocatello and Boise distribution centers, water utilities, and the State Emergency Management Agency. Her familiarity with Idaho's fuel, water and medical-supply networks, combined with her collaborative style and pre-existing relationships with Idaho officials, made her the natural choice to bridge the Region 8 (Denver) and Region 10 (Seattle) seams during the Yellowstone response.

Equipment Needs: Dedicated liaison desk equipment: satellite phone, encrypted radio, laptop with real-time mutual-aid request tracking, access to Idaho State Emergency Management systems and Pocatello/Boise distribution-center inventory databases. Printed roster of Idaho resource commitments, mutual-aid contact lists and pre-signed MOUs. Real-time fuel and water convoy GPS tracking for shipments from Idaho distribution centers.

Facility Needs: Co-located at the Denver RRCC operations center with direct sight lines to the main Incident Commander and logistics director. Dedicated phone line to Idaho State Emergency Management and standing video-link to Pocatello and Boise EOCs from T+0 through Month 1 (2026-11-14). Access to FEMA contract-vehicle systems and state mutual-aid databases. 24/7 staffed desk with immediate escalation pathways to governors' offices and state emergency managers.

3. Boundary Coordination Officer (Forward Element)

Contract Type: full_time_employee

Contract Type Justification: The Boundary Coordination Officer operates at the forward element with pre-authorized real-time decision authority for traffic reroutes and shelter assignments during the critical T+0 to T+24 hour phase, and remains in a leadership role through at least T+72 hours. This is a continuous, high-stakes operational post requiring constant presence, uninterrupted attention to the park boundary, and seamless authority handoff protocols. The role cannot be part-time or contract-based without risking command gaps.

Explanation: This role operates at the forward UC element in Livingston or Bozeman, serving as the real-time decision authority for traffic reroutes, initial shelter assignments, and permit/resource requests during the critical park-boundary crossing phase (T+0 to T+24 hours). The Boundary Coordinator holds pre-authorized authority to issue temporary reroutes without supervisory approval, ensuring that contraflow traffic does not stall waiting for NPS or state command approval at the jurisdictional boundary. The role also owns the NPS-to-state authority handoff protocol and maintains direct voice/data links to the NPS incident commander, state highway patrol commanders, and the Denver RRCC.

Consequences: Without a dedicated Boundary Coordinator with pre-authorized decision authority, reroute orders must be approved through chain-of-command calls between the park, the state, and Denver, adding 15–45 minutes of delay per decision. A single reroute delay cascades into a backup of 500–1,000 vehicles at a chokepoint, reducing overall corridor throughput by 10–20% and extending evacuation time by 1–2 hours. Estimated impact: 1,000–2,000 vehicles stranded in ash exposure, 5–10 additional respiratory-distress casualties, USD 50–100 million in indirect response costs.

People Count: 1

Typical Activities: As the Boundary Coordination Officer at the forward UC element in Livingston, Chen operates the real-time decision authority for traffic reroutes, initial shelter assignments, and permit/resource requests during the critical park-boundary crossing phase (T+0 to T+24 hours). He holds pre-authorized authority to issue temporary reroutes to state highway patrol without supervisory approval, ensuring that contraflow traffic does not stall waiting for chain-of-command clearance. Chen maintains direct voice and data links to the NPS incident commander at the park, the three state on-scene commanders (MT highway patrol, WY highway patrol, ID transportation department), and the UC Incident Commander in Denver. He owns the NPS-to-state authority handoff protocol at each gate (West Entrance, North Entrance, East Entrance), explicitly defining when NPS care ends and state custody begins. During peak evacuation (T+2 to T+8 h), Chen manages the loss-of-exit contingency: if any corridor blockage persists beyond 45 minutes, he coordinates diversion of overflow traffic to the next-nearest surviving exit. He also monitors real-time ashfall and air-quality data at T+6 h and confirms final shelter site selections with the Ashfall Officer before shelter activation begins.

Background Story: Lieutenant Colonel David Chen is a Montana National Guard officer with 20 years of experience in emergency operations and disaster logistics, currently stationed at Camp Ravenna outside Livingston, Montana. A graduate of the Army's Command and General Staff College, Chen has managed Guard response to the 2002 and 2007 Montana wildfires and the 2011 Missouri River floods. His assignment to the Livingston area, combined with his real-time visibility into the park's northern boundaries and his working relationships with Montana's highway patrol and county sheriffs, made him the ideal choice for the forward Boundary Coordination Officer role. Chen is known for staying calm under extreme time pressure and for his ability to translate orders from higher command into immediate field actions without bureaucratic delay. He has pre-existing satellite communication equipment and a tactical operations center at Camp Ravenna that can serve as the forward UC element nucleus.

Equipment Needs: Real-time interagency communications: primary satellite phone and backup encrypted radio (redundant systems), laptop with access to NPS incident-command net, state highway-patrol and National Guard radio channels, real-time traffic-sensor data from control points. Printed loss-of-exit contingency decision cards, traffic-diversion route maps (US-191/US-20 to US-89 to US-14/16/20), and authority-handoff protocol worksheets. Handheld GPS unit for position confirmation at the park boundary.

Facility Needs: Forward Unified Command element in Livingston, Montana (alternate: Bozeman), with direct line-of-sight or repeater access to Mammoth, Gardiner and Cody checkpoints. Tactical operations center equipped with 2-3 radio repeaters (VHF/UHF), satellite link to Denver RRCC and NPS incident commander, and a shared common operating picture display showing live traffic counts and shelter assignments. 24/7 staffing with cots for shift rest. Power backup (generator, fuel supply for 72 hours minimum). FAX and secure phone lines to state highway patrol dispatch centers.

4. Contraflow Operations and Traffic Control Manager

Contract Type: full_time_employee

Contract Type Justification: The Contraflow Operations and Traffic Control Manager directs the execution of the three-exit evacuation throughout the 72-hour window (Phase 1: T+0 to T+6 is peak intensity; Phase 2: T+6 to T+24 continues at elevated tempo). This core operational role requires continuous real-time throughput monitoring, load-balancing decisions, and coordination with tow/rockfall teams and the Boundary Coordinator. The role is the hub for traffic management and cannot be delegated to part-time or contracted personnel.

Explanation: This role manages the execution of contraflow operations on US-191/US-20 (West), US-89 (North), and US-14/16/20 (East) corridors, including the staging of traffic-control Rangers, state patrol and National Guard personnel at each checkpoint, sign placement, lane-reversal activation and real-time throughput monitoring. The manager owns the three-exit load split (West 50%, North 30%, East 20%), ensuring that vehicles are assigned to the correct corridor and do not cross the park interior to reach another gate. The role also manages the pre-positioned tow and rockfall-clearing teams, issues corridor-blockage diversion rules, and coordinates with the Boundary Coordinator to execute the loss-of-exit contingency (shelter-in-place after 6 hours if a corridor is not restored).

Consequences: Without centralized contraflow management, each corridor operates independently with no load balancing or real-time throughput optimization. A bottleneck at one exit (e.g., Gallatin Canyon) reduces capacity by 30–40%, and vehicles do not redirect to alternate routes, causing gridlock at the overloaded exit while other corridors remain underutilized. Estimated impact: 20–40% reduction in corridor throughput, adding 2–4 hours to peak evacuation, stranding 5,000–8,000 vehicles in ashfall zones, 10–20 preventable respiratory-distress casualties.

People Count: 1

Typical Activities: As the Contraflow Operations and Traffic Control Manager, Whitfield directs the execution of contraflow on all three corridors throughout the 72-hour window, with peak intensity during Phase 1 (T+0 to T+6 h). She stages traffic-control Rangers, state patrol and National Guard personnel at each checkpoint (Mammoth on US-89 North, Gallatin County line on US-191/US-20 West, Cody entrance on US-14/16/20 East), places and monitors contraflow signage, and activates lane reversals by T+1 h. Whitfield implements the three-exit load split (West 50%, North 30%, East 20%) and ensures vehicles are assigned to the correct corridor to prevent interior crossings. She monitors real-time throughput at each corridor—target 660 vehicles/hour per exit (estimate)—and communicates with the Boundary Coordination Officer if bottlenecks develop or if a blockage triggers the 45-minute diversion rule. Whitfield manages the pre-positioned tow and rockfall-clearing teams (at least 2 mobile crews with 15-minute reach times), authorizes their deployment if Gallatin Canyon or other key corridors are blocked, and executes the loss-of-exit contingency (shelter-in-place after 6 hours if a corridor is not restored). She also coordinates with the Contraflow Communications Coordinator to ensure HAR and VMS messages on all three routes are updated hourly with current travel times and shelter assignments.

Background Story: Captain Sarah Whitfield is a seasoned National Park Service traffic and emergency management specialist with 18 years at Yellowstone, having managed visitor evacuation drills, winter road closures, and post-earthquake stabilization operations. A native of Bozeman, Montana, Whitfield earned her degree in civil engineering from Montana State University and has deep knowledge of Yellowstone's road network, bottleneck history, and seasonal traffic patterns. She has worked closely with the NPS LE Rangers, tow contractors, and Montana-Dakota Utilities on infrastructure resilience planning. Her appointment as Contraflow Operations and Traffic Control Manager reflects her intimate familiarity with all three evacuation corridors (US-191, US-89, US-14/16/20) and her proven ability to coordinate ranger and state patrol personnel under time pressure. Whitfield also maintains relationships with the tow contractors and heavy-equipment operators who will staff the pre-positioned rockfall-clearing teams at Gallatin Canyon.

Equipment Needs: Real-time traffic monitoring: laptops linked to traffic sensors and cameras at each of the three contraflow checkpoints (Mammoth, Gallatin County line, Cody), live vehicle-count feeds, and GPS-tracked tow-team dispatch systems. Radio sets (primary and backup) for communication with checkpoint rangers and state patrol. Printed contraflow-activation checklist, load-split targets (West 50%, North 30%, East 20%) and corridor-blockage decision rules. Diversion-route maps with travel-time estimates for overflow traffic.

Facility Needs: Stationed at the forward element in Livingston or co-located with the NPS incident command post. Real-time access to traffic-sensor networks on US-191, US-20, US-89 and I-90 (via NOAA/state DOT networks). Satellite and radio links to each of the three contraflow control points and the tow/rockfall-clearing team staging depots (Mammoth, Spanish Creek). Access to pre-positioned tow-team equipment and mobilization authority. 24/7 ops center with large-format displays of all three corridors.

5. Communications and Public Alerting Coordinator

Contract Type: full_time_employee

Contract Type Justification: The Communications and Public Alerting Coordinator manages a 24/7 multilingual alerting stack (IPAWS, WEA, HAR, VMS, satellite radio, printed materials) throughout the 72-hour response and the hardening period (Months 1–3 = 2026-11-14 to 2027-01-14). The role owns message consistency, real-time updates coordinated with USGS/NOAA forecasts, responder-radio bridging, and media coordination. This is continuous, core-mission-critical work requiring a dedicated salaried position with no interruption risk.

Explanation: This role manages the layered communications stack—IPAWS/WEA, NOAA Weather Radio, Guard signal bridging, highway advisory radio (HAR), variable message signs (VMS), and printed route cards—ensuring consistent, multilingual evacuation messages reach drivers, responders and shelter occupants despite cell-network failure and ashfall. The Coordinator pre-produces all messages in English plus five visitor languages (Spanish, Japanese, German, Mandarin, French), activates Guard signal teams at contraflow checkpoints and the forward element, and maintains a 24/7 monitoring and update schedule coordinated with USGS/NOAA eruption and ashfall forecasts. The role also manages media coordination to prevent conflicting shelter-in-place and evacuation messages that would undermine public compliance.

Consequences: Without centralized alerting coordination, messages to drivers and evacuees are inconsistent, delayed or reach drivers after they have committed to wrong routes. An estimated 10–20% of drivers lack clear route instructions within the first 2 hours, taking unintended routes and adding 1–3 hours to their transit time. Foreign-language visitors (10,000–15,000 people estimate) do not receive instructions, leading to sheltering at wrong locations or stranding. Responder radios lose coordination when cell networks collapse, delaying patient transfers and traffic reroutes by 30 minutes to 2 hours each. Estimated impact: 2,000–5,000 evacuees experience 2–4 hour delays, 200–500 left behind or sheltered at wrong sites, 5–15 preventable casualties.

People Count: 1

Typical Activities: As the Communications and Public Alerting Coordinator, Patterson manages the layered communications stack—IPAWS/WEA, NOAA Weather Radio, Guard signal bridging, highway advisory radio (HAR), variable message signs (VMS), and printed route cards—from T-12 h through T+72 h and beyond. He pre-produces all evacuation messages in English plus five primary visitor languages (Spanish, Japanese, German, Mandarin, French) by Month -1 (2026-09-14), validates them for clarity with native speakers, and pre-records them in broadcast-ready format. Patterson activates Guard signal teams at each contraflow checkpoint and the forward element at T+0, maintains a 24/7 monitoring and update schedule coordinated with USGS/NOAA eruption and ashfall forecasts, and revises messages hourly during peak evacuation based on shelter assignments and corridor status updates. He manages media coordination with Reuters, AP, regional TV and radio stations to prevent conflicting shelter-in-place and evacuation messages that would undermine public compliance. Patterson also works with the Boundary Coordination Officer to ensure that WEA and HAR messages align with traffic reroute orders issued in real time, and he maintains a media hotline and briefing schedule to answer journalist questions and sustain institutional credibility throughout the 72-hour window.

Background Story: Dr. James Patterson is a communications and public-alerting specialist with 22 years in government emergency management, currently the Director of Emergency Communications for the Colorado Department of Public Safety. He holds a master's degree in public communications from the University of Colorado and has deployed to multiple disasters including Hurricanes Sandy and Irma, as well as large wildfires. Patterson is an expert in IPAWS messaging design, Wireless Emergency Alerts (WEA) distribution, highway advisory radio (HAR) network operations, and the psychological dynamics of public compliance during escalating threats. His experience managing multilingual alerts for Colorado's Hispanic population made him the natural choice to lead the Yellowstone communications stack. Patterson has pre-existing relationships with the USGS Public Affairs office and NOAA's National Weather Service, and he understands how to time and phrase eruption-trigger announcements to sustain public trust even when escalation reverses earlier shelter-in-place guidance.

Equipment Needs: Multilingual alerting infrastructure: access to IPAWS and WEA distribution systems, NOAA Weather Radio transmission protocols, Highway Advisory Radio (HAR) broadcast systems and Variable Message Sign (VMS) control networks on the three exit corridors. Laptops for message scheduling and distribution across multiple agencies. Pre-recorded message libraries in English plus five languages (Spanish, Japanese, German, Mandarin, French). Satellite phones and encrypted radios for secure media coordination and press briefing. Printed message templates and media-response scripts.

Facility Needs: Co-located at the Denver RRCC or forward element with direct links to IPAWS regional distribution office, NOAA Weather Service, and the FAA. Access to HAR network control centers for each corridor (West, North, East routes). Direct radio and phone lines to all three contraflow control points (Mammoth, Gardiner, Cody) for real-time message updates. Media center with secure phone lines, video-teleconference capability for remote briefings, and internet access for website and social-media updates. 24/7 staffing with backup communications operator.

6. Emergency Logistics and Supply-Chain Director

Contract Type: full_time_employee

Contract Type Justification: The Emergency Logistics and Supply-Chain Director manages the dispatch of water, N95, fuel and medical convoys from T+0 through at least T+72 hours and the hardening period. The role owns real-time tracking of all inbound shipments, prioritization of fuel and supplies to hospitals and shelters, authorization of helicopter resupply if ground routes fail, and procurement under FEMA contract vehicles. This is a continuous, mission-critical role requiring constant presence and decision authority. The workload is highest during T+0 to T+24 (convoy dispatch, receipt, distribution) but remains elevated through the full response window.

Explanation: This role plans and executes the supply-chain network for water, N95 respirators, generator fuel, shelter equipment and medical supplies, managing the dispatch of convoys from Salt Lake City (water, fuel), Billings/Salt Lake (N95 backup reserve), and pre-positioned forward depots at Bozeman and Idaho Falls. The Director owns the 12-hour dispatch target for water convoys, tracks all inbound shipments in real-time, and authorizes helicopter resupply if ground routes are blocked by ashfall or evacuation traffic. The role also maintains priority fuel allocation (hospitals > comms centers > shelter kitchens), pre-positions 72-hour reserves at receiving hospitals, and manages the procurement of shelter supplies, buses and equipment under existing FEMA contract vehicles to avoid 24–48 hour procurement delays.

Consequences: Without centralized logistics management, supplies arrive late or at wrong locations. Water convoys that should arrive by T+12 h (target) are delayed to T+18–T+30 h (estimate), leaving 10,000–20,000 evacuees without adequate water for 1–2 days. N95 respirator stock (100,000 user constraint) is not monitored for consumption rate, and a heavy ashfall that doubles use rate exhausts stock within 12–24 hours instead of 72 hours, leaving shelter occupants and hospitals unprotected. Generator fuel is not prioritized, so hospitals compete with shelters and comms centers for the same delivery slots, and one facility runs out of fuel before reserves arrive. Estimated impact: 1,000–3,000 evacuees without water for 12–24 hours; 5–15 respiratory-distress cases from inadequate N95 supply; 5–10 preventable hospital-patient deaths from power loss.

People Count: min 1, max 2, depending on supply complexity and convoy volume

Typical Activities: As the Emergency Logistics and Supply-Chain Director, Harkness plans and executes the supply-chain network for water, N95 respirators, generator fuel, shelter equipment and medical supplies from Month -1 (2026-09-14) through Month 3 (2027-01-14). He manages the dispatch of water convoys from Salt Lake City (I-15 northbound, reserved surge lane) by T+12 h, N95 backup reserves from Billings or Salt Lake City hubs, and generator fuel to receiving hospitals at Bozeman, Livingston and Idaho Falls. Harkness tracks all inbound shipments in real-time using GPS and radio updates, maintains a procurement checkpoint at the forward command with a tracking dashboard updated hourly, and alerts the UC Incident Commander if any convoy is delayed more than 4 hours beyond dispatch. He pre-positions 72-hour fuel reserves at receiving hospitals by Month -0.5 (2026-09-29) and maintains priority fuel allocation (hospitals > comms centers > shelter kitchens). Harkness also manages procurement under existing FEMA contract vehicles to avoid 24-48 hour procurement delays, establishes 12-hour dispatch clauses with water and fuel vendors, authorizes helicopter resupply if ground routes become blocked by ashfall, and conducts water-convoy exercises from Salt Lake City to Bozeman under simulated ashfall and congested-traffic conditions to validate actual transit times.

Background Story: Thomas "Tom" Harkness is an emergency logistics and supply-chain director with 25 years in military and federal disaster operations, most recently as the Director of FEMA Region VIII Emergency Logistics Network. Harkness earned his degree in supply-chain management from San Diego State University and spent 20 years in the U.S. Army Quartermaster Corps managing combat and humanitarian supply operations across three continents. He has directed logistics for Hurricane Katrina, the 2011 Joplin tornado, and multiple winter-emergency mobilizations. His reputation for delivering supplies on time under chaotic conditions, combined with his knowledge of water-distribution networks, N95 respirator supply chains, and generator-fuel delivery from Rocky Mountain refineries, made him indispensable for the Yellowstone response. Harkness maintains pre-existing contracts with bottled-water suppliers, fuel vendors and equipment distributors across the Mountain West and has the authority to activate FEMA contract vehicles with verbal orders.

Equipment Needs: Real-time supply-chain tracking: laptops with GPS and radio links to all water, N95 and fuel convoys in transit, inventory-management databases for forward depots at Bozeman and Idaho Falls, real-time consumption tracking at shelters and hospitals. Satellite phones and encrypted radios for convoy dispatch and rerouting. Printed procurement checklists, pre-authorized vendor contact lists (Salt Lake City water, Pocatello fuel, Billings N95 suppliers), and FEMA contract-vehicle activation forms. Priority-access codes for emergency-fuel networks and utility coordination.

Facility Needs: Procurement checkpoint at the forward element in Livingston with real-time tracking dashboard updated hourly. Secure phone lines to FEMA contract-vehicle coordinators, Salt Lake City distribution centers, and receiving-hospital logistics officers. 24/7 staffing to monitor all inbound shipments and authorize helicopter resupply if ground routes are blocked. Access to interstate fuel and water distribution networks (I-15, I-90 coordination). Standing agreements with utility and water-district dispatch centers for emergency access to reserves.

7. Responder Safety and Fatigue-Management Officer

Contract Type: full_time_employee

Contract Type Justification: The Responder Safety and Fatigue-Management Officer enforces exposure limits, tracks responder injury and fatigue, and coordinates the 30–50 person standby reserve throughout the 72-hour window and the hardening period. The role includes 24/7 monitoring of air-quality conditions at each post, authorization of responder withdrawal, and real-time relief scheduling. This is a continuous safety-critical position requiring constant vigilance. The role is especially intense during T+2 to T+8 (peak evacuation) when coverage gaps most threaten life safety.

Explanation: This role defines and enforces responder exposure limits (maximum 6-hour shifts at ash-exposed posts, 2-hour mandatory rest with N95 replacement, full withdrawal after 18 consecutive hours), tracks responder fatigue and injury, and coordinates the 30–50 person standby reserve from out-of-region agencies to maintain at least 50% coverage at traffic checkpoints and perimeter gates throughout the 72-hour window. The Officer manages separate N95 respirator counts for responders (not drawn from the 100,000 civilian stock), monitors air-quality conditions at each post and authorizes withdrawal if ash concentrations exceed agency standards. The role also pre-arranges rotational relief with Colorado Parks and Wildlife, Wyoming Game and Fish, and Fort Carson (National Guard) to ensure that the 100–150 NPS rangers are not consumed entirely during the T+2 to T+8 evacuation peak.

Consequences: Without explicit exposure limits and relief coordination, all 100–150 rangers are consumed during the T+2 to T+8 peak with zero relief depth. A single ranger injury, equipment failure, or ash exposure forcing withdrawal halts one checkpoint for 2–4 hours, stranding 500–2,000 vehicles and cascading delay through the entire evacuation. Responders work 16–24 hour shifts without rest, degrading judgment and increasing errors in traffic control and perimeter enforcement. Looting and unauthorized entries occur at 2–4 locations where checkpoints are unmanned. Estimated impact: 1–2 additional hours of evacuation delay, 500–2,000 stranded vehicles, 2–4 looting incidents, 5–10 preventable respiratory-injury casualties among responders.

People Count: 1

Typical Activities: As the Responder Safety and Fatigue-Management Officer, Torres defines and enforces responder exposure limits (maximum 6-hour shifts at ash-exposed posts, 2-hour mandatory rest with N95 replacement, full withdrawal after 18 consecutive hours) and tracks responder fatigue and injury throughout the 72-hour response. She manages separate N95 respirator counts for responders (not drawn from the 100,000 civilian stock), monitors air-quality conditions at each traffic checkpoint and perimeter gate, and authorizes withdrawal if PM10 concentrations exceed agency standards. Torres coordinates the 30-50 person standby reserve from out-of-region agencies (Colorado Parks and Wildlife, Wyoming Game and Fish, Idaho Department of Lands) to maintain at least 50% coverage at traffic checkpoints during the evacuation peak. She pre-arranges rotational relief with Fort Carson (Colorado National Guard) and Wyoming/Montana Guard Joint Task Force to ensure that the 100-150 NPS rangers are not consumed entirely during T+2 to T+8 h. Torres also develops fatigue-assessment checklists for on-site use, pre-authorizes ranger withdrawal from posts if fatigue exceeds safe limits, and conducts a 6-hour shift-rotation exercise at Mammoth or Gardiner checkpoint 30 days before the window to test relief handoff protocols and N95 replacement procedures under simulated ashfall.

Background Story: Dr. Rachel Torres is a occupational health and safety specialist with 16 years in emergency-response worker protection, currently the Chief of the CDC's Emergency Response and Recovery Branch. She holds a doctorate in public health from Johns Hopkins University and has deployed to Ebola, Zika, wildfire and hurricane responses, managing responder fatigue, illness prevention and safe-exposure protocols. Torres is an expert in respiratory protection standards, N95 mask fit-testing and replacement cycles, and the physiological signs of acute exhaustion and heat stress in emergency workers. Her experience managing responder rotations under extreme conditions and her collaborative relationships with state occupational safety agencies made her the ideal choice for the Yellowstone responder-safety role. Torres also has credibility with the National Guard and NPS LE personnel because of her prior work on wildfire responder health in the Pacific Northwest.

Equipment Needs: Real-time air-quality and fatigue monitoring: PM10/PM2.5 sensors and data loggers for deployment at each contraflow checkpoint and shelter site (estimate: 6-8 sensors minimum), visual ash-depth measurement stations. Laptops for processing hourly sensor data and comparing with OSHA/agency responder-exposure limits. Fatigue-assessment checklists and N95 fit-test kits. Printed shift-rotation schedules, responder rotation charts and mandatory-rest protocols. Separate inventory database for responder N95 respirators (not drawn from the 100,000 civilian stock).

Facility Needs: Stationed at the forward element with 24/7 monitoring access to air-quality data from USGS and NOAA ashfall models. Direct satellite and radio communication with each contraflow checkpoint and perimeter gate to authorize responder withdrawal if air quality exceeds thresholds. Medical resources on-site or immediately available (occupational health nurse, oxygen supply) for responder respiratory assistance. Secure phone lines to Fort Carson (Colorado National Guard), Wyoming and Montana Guard Joint Task Force, and Colorado Parks and Wildlife for standby-reserve mobilization authority.

8. Scenario Beta Secondary-Stage Destination Planner

Contract Type: full_time_employee

Contract Type Justification: The Scenario Beta Secondary-Stage Destination Planner develops and pre-authorizes the second-stage plan by Month 1 (2026-11-14), executes it on a Scenario Beta trigger (which may occur within the 72-hour window at T+0 to T+72), and refines it through Months 2–3 (2026-12-14 to 2027-01-14). Although the plan is primarily front-loaded (Months -2 to Month 1 = 2026-11-14 readiness activities), once the 72-hour response begins, the planner becomes the on-call decision authority for Scenario Beta escalation and the activation of secondary hubs and tiered messaging. If Scenario Beta triggers, this role transitions to continuous operations. Full-time employment ensures the planner is immediately available at the forward element or Denver RRCC if the trigger fires.

Explanation: This role develops and pre-authorizes the Scenario Beta secondary-stage evacuation plan for a VEI-7 eruption affecting 100,000–500,000+ additional evacuees beyond the initial 100 km zone. The Planner identifies 5–10 ranked shelter hubs outside the 500 km ring (Denver, Cheyenne prioritized; Salt Lake City, Billings and Bozeman excluded as inside-ring), secures signed MOUs from host counties confirming shelter capacity and medical staffing, pre-positions food, water and medical supplies at secondary hubs, coordinates bus fleets and rail corridors to move evacuees from primary shelters to secondary hubs, and develops tiered public messaging differentiating shelter-in-place zones (250–500 km), time-banded evacuation zones (100–250 km), and organized evacuation (Zone One). The role executes this plan on a Scenario Beta trigger, preventing uncontrolled shadow evacuation that would saturate I-15, I-80 and I-90 and strand Zone Zero evacuees.

Consequences: Without a defined Scenario Beta secondary-stage plan, a pre-authorized VEI-7 trigger will activate a 500 km evacuation order affecting tens of thousands to millions of additional people with no published destinations, causing chaotic, uncontrolled flight on all routes away from Yellowstone. I-15, I-80 and I-90 saturate within 2–4 hours of the trigger, preventing the organized Zone One evacuation of 35,800 park visitors and stranding ambulances and medical transport. The evacuation delay cascades by 4–8 additional hours, and uncontrolled evacuees compete with organized evacuees for the same water, fuel and shelter supplies, stranding both groups. Estimated impact: 4–8 hour evacuation delay for Zone Zero, 100,000–500,000 unplanned evacuees stranded without shelter or supplies, 20–50 preventable deaths from exposure, medical neglect or secondary accidents.

People Count: 1

Typical Activities: As the Scenario Beta Secondary-Stage Destination Planner, Carruthers develops and pre-authorizes the Scenario Beta secondary-stage evacuation plan for a VEI-7 eruption affecting 100,000 to potentially millions of additional evacuees beyond the initial 100 km zone. He identifies 5-10 ranked shelter hubs outside the 500 km ring (Denver and Cheyenne prioritized; Salt Lake City, Billings, Bozeman and Idaho Falls excluded as inside-ring), secures signed MOUs from host counties confirming shelter capacity, medical staffing and water/food supply commitments by Month 2 (2026-12-14). Carruthers coordinates with Denver, Cheyenne, Colorado Springs and Fort Collins emergency managers to pre-position food, water and medical supplies at secondary hubs by Month 1 (2026-11-14), arranges bus fleets and rail corridors to move evacuees from primary shelters to secondary hubs using lateral routes away from I-90, and develops tiered public messaging differentiating shelter-in-place zones (250-500 km, self-supplied residents), time-banded evacuation zones (100-250 km, pre-assigned by county), and organized evacuation (Zone One). If a Scenario Beta trigger fires during the 72-hour window, Carruthers activates secondary-hub onward transport and coordinated messaging, preventing uncontrolled shadow evacuation on I-15, I-80 and I-90. He also oversees a full-scale Scenario Beta exercise involving sample bus-fleet dispatch and shelter-intake registration 30 days before the eruption window (Month 3 = 2027-01-14).

Background Story: Dr. Michael Carruthers is a regional emergency management planner with 19 years in multi-state disaster preparedness, currently the Deputy Director of the Rocky Mountain Multi-State Emergency Management Consortium based in Denver. A graduate of Harvard Kennedy School with a master's in public administration, Carruthers has designed evacuation and shelter plans for the Three Rivers nuclear facility, Flaming Gorge dam failure scenarios, and major wildfire zones across Colorado, Utah and Wyoming. His experience securing signed MOUs from governors, negotiating mutual-aid agreements and hosting-community commitments, and designing tiered evacuation messaging for complex threat scenarios made him the obvious choice for Scenario Beta secondary-stage planning. Carruthers has working relationships with Denver, Cheyenne, Salt Lake City and Billings emergency management officials and has pre-existing familiarity with secondary shelter capacity in those cities. He is also skilled at negotiating host-community concerns about shelter burdens and at designing public-messaging strategies that sustain credibility when threat levels escalate or reverse.

Equipment Needs: Scenario Beta planning and execution infrastructure: laptops for secondary-hub outreach, pre-signed MOU templates for host counties outside the 500 km ring (Denver, Cheyenne, Colorado Springs, Fort Collins). Maps and distance-verification tools for confirming that hub candidates lie outside the ring. Tiered public-messaging templates differentiated by evacuation ring (0-100 km organized, 100-250 km time-banded, 250-500 km staged departure). Pre-authorized resource pre-positioning lists for secondary hubs (food, water, medical, shelter equipment quantities). Ranking criteria for hub selection and capacity-vetting worksheets.

Facility Needs: Stationed at the Denver RRCC with secure phone and video links to governors' offices in Colorado, Wyoming and Idaho and to emergency managers in Cheyenne, Denver and surrounding counties. Access to secondary-hub feasibility-assessment data (shelter capacity, water systems, medical-facility bed counts) for all candidate hubs. 24/7 coordination desk from T+0 through Month 3 (2027-01-14). Pre-event (Months -2 through Month 1 = 2026-11-14) office space for multi-state MOU negotiations and host-community coordination meetings. Capacity to conduct or observe a full-scale multi-state Scenario Beta exercise by Month 3 (2027-01-14).

9. Ashfall Forecasting and Dynamic Shelter-Siting Officer

Contract Type: full_time_employee

Contract Type Justification: The Ashfall Forecasting and Dynamic Shelter-Siting Officer maintains continuous ashfall monitoring at the forward command and all three shelter sites from T-12 hours through at least T+72 hours, with special intensity at T+6 hours when shelter sites are selected. The role involves real-time PM10/PM2.5 sensor monitoring, integration of USGS/NOAA forecast updates, and authority to trigger 4-hour shelter relocation if ashfall exceeds thresholds. This is a continuous, life-safety-critical role requiring constant presence at the forward element and shelter sites. The officer must be on-site and available without interruption to detect ashfall escalation and authorize relocation before shelter occupants suffer respiratory distress.

Explanation: This role maintains continuous ashfall and air-quality monitoring at the forward command element and all three shelter sites using real-time PM10/PM2.5 sensors and visual ash-depth markers, integrating updates from NOAA and USGS ashfall models. At T+6 hours when final shelter sites are selected, the Officer updates the selection based on the latest wind and plume forecast (not the T+0 forecast), identifies ranked second and third backup shelter locations 50+ km upwind, and maintains a dynamic 4-hour relocation protocol triggered if actual ashfall exceeds model predictions (threshold: PM10 >100 µg/m³ at primary sites). The Officer also manages the supplemental 100,000 N95 mask reserve at Billings or Salt Lake City and authorizes emergency relocation of 5,000–10,000 evacuees to backup shelters if primary sites fall in heavy ash, preventing shelter occupants from developing respiratory distress.

Consequences: Without dynamic shelter siting and ashfall monitoring, shelter locations are chosen at T+6 h using the T+0 forecast and are never updated. If actual ashfall shifts 50+ km from the forecast or doubles in intensity, 10,000–15,000 evacuees are sheltered in moderate-to-heavy ash for 12–24 hours before a relocation order is issued (if issued at all). The 100,000 N95 mask stock (user constraint) is exhausted within 12–24 hours if ashfall is 2–3 times heavier than forecast, leaving shelters without protection for the remaining 48–60 hours of operation. Relocation of 10,000+ evacuees mid-operation requires 3–6 hours of transport, additional buses and a second intake process, effectively delaying shelter operations by 6–12 hours and stranding evacuees in ashfall during the transition. Estimated impact: 500–2,000 evacuees develop respiratory distress within 6–24 hours; 5–10 die if medical care is delayed; 200–500 stranded during relocation.

People Count: 1

Typical Activities: As the Ashfall Forecasting and Dynamic Shelter-Siting Officer, Kwan maintains continuous ashfall and air-quality monitoring at the forward command element and all three shelter sites using real-time PM10/PM2.5 sensors, visual ash-depth measurement stations, and integrated updates from NOAA and USGS ashfall models starting at T-12 h. At T+6 h when final shelter sites are selected, she updates site selections based on the latest wind and plume forecast (not the T+0 forecast), identifies ranked second and third backup shelter locations 50+ km upwind and confirms their readiness. Kwan maintains a dynamic 4-hour relocation protocol triggered if actual ashfall exceeds model predictions (PM10 threshold >100 µg/m³ at primary sites), authorizes emergency relocation of 5,000-10,000 evacuees to backup shelters if ashfall is heavier or more extensive than forecast, and coordinates with the Logistics Director to authorize helicopter resupply of supplemental N95 masks (100,000 reserve) if ash consumption exceeds 20% of primary stock per day. She also produces hourly ashfall updates for the UC Incident Commander, the Boundary Coordination Officer and all shelter managers, and conducts an air-quality monitoring exercise with NOAA and shelter facility managers 30 days before the window to test real-time forecast updates and relocation-decision protocols.

Background Story: Dr. Susan Kwan is a volcanologist and ashfall-impact specialist with 14 years at the USGS Yellowstone Volcano Observatory, where she specializes in ash-dispersion modeling, air-quality monitoring and the behavior of volcanic ash in regional water systems. A PhD from Caltech in geology, Kwan has published extensively on the 1980 Mount St. Helens eruption's ashfall impacts and has collaborated with NOAA on volcanic ash advisory (VAAC) protocols. She is deeply familiar with the uncertainty ranges in ashfall forecasts from large eruptions and the practical challenges of sheltering populations in moderate to heavy ash. Her research on N95 mask efficacy in volcanic ash environments and the rate of ash-induced equipment degradation made her the ideal choice for dynamic shelter siting and ashfall monitoring during the Yellowstone response. Kwan maintains real-time connections to NOAA's Hazardous Weather Testbed and the National Weather Service and can access hourly ashfall model updates as they become available.

Equipment Needs: Continuous ashfall monitoring: real-time PM10/PM2.5 sensors and data loggers at forward command and all three shelter sites (estimate: 4-6 sensors minimum). Visual ash-depth measurement stations (scales, photographs) at each location. Laptops with real-time integration of USGS ashfall model outputs, NOAA forecast updates and local air-quality sensor feeds updated hourly. Printed shelter-siting decision cards with PM10 thresholds (relocation trigger >100 µg/m³ at primary sites). Maps showing backup shelter locations 50+ km upwind, confirmed daily from the latest wind forecast. Contact lists for shelter facility managers and logistics director for 4-hour relocation authorization.

Facility Needs: Primary station at the forward element in Livingston (or Bozeman) with continuous access to USGS Yellowstone Volcano Observatory ashfall models and NOAA Weather Service plume forecasts updated hourly from T-12 h onward. Direct satellite and radio communication with all three active shelter sites and the logistics director. Real-time air-quality data feeds integrated into the forward-element common operating picture. Standby 24/7 for emergency relocation decisions if actual ashfall exceeds model predictions. Coordination capability with secondary-hub facility managers if Scenario Beta triggers and evacuees must be moved onward from primary shelters.

Omissions

1. Scenario Beta Secondary-Stage Evacuation Plan and Destination List Missing

The plan pre-authorizes a Scenario Beta VEI-7 trigger ordering immediate 500 km radius evacuation affecting 100,000 to potentially millions of additional people beyond Zone One. No second-stage shelter hubs, host-community MOUs, onward transport routes, or supply-staging depots are defined. If the trigger fires, evacuees from 100–500 km radius will be ordered to leave with no published destinations, causing chaotic uncontrolled flight on I-15, I-80 and I-90 that saturates the very corridors needed for Zone Zero primary evacuation, adding 4–8 hours delay and stranding 35,800 tourists and staff in ashfall zones.

Recommendation: Develop and pre-authorize a written Scenario Beta Secondary-Stage Evacuation Plan by Month 1 (2026-11-14), specifying: (1) five to ten ranked shelter hubs outside the 500 km ring (Denver and Cheyenne prioritized; Salt Lake City, Billings, Bozeman, Idaho Falls excluded as inside-ring) with signed MOUs from host counties confirming shelter capacity; (2) tiered public messaging differentiating shelter-in-place zones (250–500 km, self-supplied), time-banded evacuation zones (100–250 km, pre-assigned by county) and organized evacuation (Zone One); (3) bus fleets and rail corridors moving evacuees from primary shelters to secondary hubs using lateral routes away from I-90; (4) food, water, medical supply pre-positioning at secondary hubs by Month 1 (2026-11-14). Conduct a multi-state Scenario Beta exercise involving sample bus dispatch and shelter intake 30 days before the eruption window (Month 3 = 2027-01-14).

2. Responder Exposure Limits and Relief Depth Undefined; Staffing Insufficient for 72-Hour Operations

The plan assumes 100–150 NPS rangers (estimate) with 1.5 relief ratio per post, leaving approximately 67–100 concurrent positions. At peak evacuation (T+2 to T+8 h), all ranger hours are consumed with zero relief cushion. A single ranger injury, equipment failure, or weather event at one critical checkpoint (e.g., Gallatin Canyon) halts traffic for 2–4 hours, stranding 500–2,000 vehicles and cascading 1–2 hours delay through the entire operation. The plan lists responder exposure limits as a secondary decision but specifies no shift lengths, withdrawal thresholds, or separate N95 inventory for responders (user constraint defines only 100,000 civilian stock).

Recommendation: Define concrete responder exposure limits in writing by Month -1: maximum 6-hour shifts at ash-exposed locations (contraflow checkpoints, perimeter gates), mandatory 2-hour rest with N95 replacement, complete withdrawal after 18 consecutive hours. Count responder N95 respirators separately from the 100,000 civilian stock, with 50% surge buffer (total 150,000–200,000 respirators). Pre-stage a 30–50 person standby reserve from outside the region (Colorado Parks and Wildlife, Wyoming Game and Fish, Idaho Department of Lands) at a depot outside the ash zone, ready to deploy within 4 hours if coverage falls below 50% at any checkpoint. Pre-authorize the forward command to request additional National Guard without supervisory approval. Conduct a 6-hour shift-rotation exercise at a key control point 30 days before the window, testing relief logistics, N95 replacement and fatigue protocols under simulated ashfall.

3. Ashfall Footprint Uncertainty and Dynamic Shelter-Siting Strategy Lack Real-Time Monitoring and Relocation Protocols

The plan selects final shelter sites at T+6 h from the NOAA/USGS plume forecast but does not specify real-time ashfall monitoring or relocation triggers if actual ashfall diverges from forecast. Volcanic ashfall from a VEI-6 eruption has never been directly observed in North America; grain-size distribution, settling rates and wind variability could shift the modeled footprint by 50–100+ km or intensify by 2–3x. If actual ashfall exceeds forecast by 50 km or doubles in intensity, 10,000–15,000 evacuees will be sheltered in moderate-to-heavy ash (PM10 > 100 µg/m³) for 12–24 hours before a relocation order is issued. The 100,000 N95 mask stock (user constraint) exhausts within 12–24 hours if ashfall is 2–3x heavier, leaving shelters without protection for the remaining 48–60 hours.

Recommendation: Establish continuous ashfall and air-quality monitoring at the forward command and all three shelter sites using real-time PM10/PM2.5 sensors and visual ash-depth markers, updated hourly from T-12 h onward. At T+6 h when final shelter sites are selected, update the selection based on the latest wind and plume forecast (not the T+0 forecast). Maintain a ranked second and third backup shelter for each primary site, located 50+ km upwind (confirmed daily from latest wind forecast), enabling rapid 4-hour relocation if ashfall exceeds thresholds (trigger: PM10 > 100 µg/m³ at primary sites). Pre-stage supplemental 100,000 N95 masks at a secondary hub (Billings or Salt Lake City) with standing agreement for daily resupply if ash consumption exceeds 20% of stock per day. Conduct an air-quality monitoring exercise with NOAA and shelter managers 30 days before the window, testing real-time forecast updates and relocation protocols.

4. Single-Point Road Chokepoint Vulnerability: Gallatin Canyon and Gardiner Lack Viable Bypass and Rapid-Clearance Capacity

The three exit corridors depend on narrow, two-lane mountain passes (Gallatin Canyon on US-191/US-20, Gardiner on US-89, Cody approach on US-14/16/20) with minimal shoulders, documented rockfall and secondary-slide hazard. A single breakdown, rockslide, or tremor-induced slide during peak evacuation (T+2 to T+8 h) could block an entire contraflow and strand 500–2,000 vehicles within 30 minutes. The plan mentions pre-positioned tow and rescue assets at chokepoints but does not specify equipment count, staging locations, or hard decision rules for diversion if clearance exceeds 45 minutes. The South Entrance remains landslide-blocked, eliminating a potential southern exit.

Recommendation: Pre-position at least two mobile heavy-equipment teams (wreckers, debris chippers, spotters) at Mammoth or Spanish Creek by Month -0.5, with 72-hour fuel and supplies, tasked to reach any Gallatin Canyon blockage within 15 minutes of dispatch. Establish live geotechnical monitoring along Gallatin Canyon and US-89 near Gardiner using motion sensors or drones at identified slide-prone zones, with automatic alerts to the forward command if incipient movement is detected. Conduct a geotechnical survey of the South Entrance landslide 60 days before the window; develop a time-boxed single-lane clearance plan (maximum 4 hours proposed threshold) and a longer-term bypass plan with hard abort triggers (M>4.0 renewed seismic activity, equipment breakdown). Issue written loss-of-exit contingency: if any primary corridor blockage persists beyond 45 minutes and cannot be restored, the forward command will trigger overflow diversion to the nearest surviving exit and issue shelter-in-place orders for queued vehicles in that sector.

5. Cross-Jurisdiction Authority Transfer and Command Gaps: NPS-to-State Handoff and FEMA Region 8/10 Seams Lack Explicit Protocols

The plan specifies authority transfer at the park boundary under written protocol, with NPS incident commander handing responsibility to state governors at defined checkpoints. However, contraflow traffic does not stop at jurisdictional lines; drivers cross from NPS to state control mid-queue, creating windows where no single authority owns traffic-reroute or shelter-assignment decisions. Idaho falls under FEMA Region 10 (Seattle) while Montana and Wyoming fall under Region 8 (Denver); the plan names only the Denver RRCC, leaving Region 10 mutual aid (Boise and Pocatello resources) uncoordinated and potentially delayed 1–2 hours. The plan does not specify written MOUs with the three governors confirming their acceptance of NPS incident command or their agreement to enforce unified messaging.

Recommendation: Establish a dedicated Boundary Coordination Officer at the forward element in Livingston with real-time voice and data links to the NPS incident commander and the three state on-scene commanders. Issue a written protocol specifying that the boundary officer controls traffic reroutes and initial shelter assignments during the corridor crossing, and that NPS care ends at a specific roadside checkpoint where state custody formally begins. Pre-authorize state on-scene commanders to issue temporary reroutes without requesting park ranger approval. Add an explicit FEMA Region 10 liaison call at T+0 hours from the Denver RRCC, with pre-agreed mutual aid arrangements (Boise and Pocatello fuel, water and medical resources) documented in signed MOUs by Month 1 (2026-11-14). Obtain written pre-event confirmation from governors of Montana, Wyoming and Idaho authorizing the Unified Command's Zone One and Scenario Beta orders, and enforce unified public messaging. Conduct a multi-state command-authority exercise 60 days before the window, testing the boundary handoff, Region 8/10 coordination and governor-to-FEMA hotline.

6. Communications Layer Fragility: Ash-Induced Cell-Network Collapse and Tremor Damage Leave IPAWS and Bridge Systems Untested

The plan relies on IPAWS and Wireless Emergency Alerts as the primary public channel, with National Guard signal bridging as the fallback for responder coordination. Ash-induced flashovers on transmission lines, tremor damage to cell towers, and silicate-ash clogging of repeater fans could collapse the local network faster than signal units can deploy. The plan does not specify the number of Guard signal units available, their staging locations, fuel pre-positioning, or testing protocols under simulated ashfall. Printed route cards and highway advisory radio are mentioned as fallbacks but are not pre-produced or validated for clarity and multilingual comprehension.

Recommendation: Deploy National Guard signal corps teams with satellite phones, portable repeaters and generator fuel to each contraflow control point and the forward command element at T-12 h, before ashfall onset. Pre-stage printed route cards and windshield placards at all park entrance stations and lodges by Month -1, in English and five primary visitor languages (Spanish, Japanese, German, Mandarin, French), with simple instructions (e.g., 'North Exit: Follow US-89 to Gardiner, then I-90 to Livingston') and shelter addresses and phone numbers. Activate all available highway advisory radio stations and variable message signs on US-191, US-20, US-89 and I-90 with pre-recorded messages updated hourly from the forward command. Conduct formal radio interoperability testing across all agencies 30 days before the window, confirming frequency coordination, call signs, encryption protocols and on-air checks from each control point. Test satellite and portable-repeater systems under simulated ashfall conditions, measuring radio propagation through ash, equipment overheating and 72-hour fuel adequacy.

7. International and Non-English-Speaking Visitor Notification: Language Access and Mobility-Assistance Gaps Unaddressed

The plan lists international visitor, language and access-needs notification pathways as a low-priority decision. Yellowstone hosted approximately 4 million visitors in 2023, with roughly 40% from outside the USA. During peak season, non-English speakers could comprise 30–40% of the 35,000 visitors in the park (estimate 10,000–15,000 evacuees), many arriving via tour buses or without personal vehicles. The plan does not specify how these populations will receive evacuation instructions, access contraflow lanes, or board priority evacuation shuttles. Visitors without vehicles and unclear instructions could delay departure, cluster at wrong shelters, or become stranded if buses are not pre-allocated.

Recommendation: Pre-produce IPAWS messages, radio broadcasts and digital alerts in five primary visitor languages (Spanish, Japanese, German, Mandarin, French) by Month -1, with simple phased messages validated for comprehension by native speakers. Coordinate with concessioner Xanterra Parks and Resorts to disseminate multilingual briefings to all guest rooms, tour buses and visitor centers at T+0. Pre-identify 20–50 multilingual volunteers from tour operators and position them at major lodges by T+0, with translation materials and communication devices. Establish a dedicated shuttle-bus evacuation plan for tour groups and lodge-based visitors, pre-assigning 4–6 buses per major lodge (estimated 20–30 buses total) with pre-briefed drivers and mobility-assistance attendants. At T-12 h, confirm lodge occupancy and create priority-transport staging areas with medical supplies. Pre-authorize a secondary protocol: if any lodge cannot evacuate within 3 hours, notify the forward command, which will dispatch helicopter support or ground rescue teams from the National Guard.

8. Hospital and Utility Power Grid Failure: No Explicit Fuel Pre-Positioning, Generator Startup Failures, and Cascade-Risk Management

The plan identifies grid failure as a contingency and directs fuel priority to hospitals and communications centers, but does not specify which hospitals are critical receivers, fuel pre-positioning timelines, or how many hospitals have adequate on-site reserves. Regional hospitals typically have 24–48-hour generator fuel on hand (estimate); simultaneous power loss across multiple substations due to ash-induced flashovers could occur within 4–8 hours of ashfall, faster than fuel convoys from distant depots can deliver. Hospitals often have single fueling ports and outdated generators with startup failures during high-stress events; a 4-hour outage before fuel arrives could force cancellation of 10–20 surgeries and loss of ventilator support. The plan does not coordinate with regional power utilities to identify critical transmission lines or single-point failures.

Recommendation: Pre-position 72-hour diesel and propane fuel reserves at the three largest receiving hospitals (Bozeman Deaconess Medical Center, Livingston HealthCare, Eastern Idaho Regional Medical Center) by Month -0.5, confirming tank capacity and fueling-port adequacy with each facility. Establish fuel-delivery contracts with local vendors requiring priority dispatch and arrival within 2 hours of a fuel request. Conduct a hospital power-failure exercise at each facility 30 days before the window, testing manual generator startup, fuel-transfer protocols and backup surgical protocols under ash-simulation conditions. Coordinate with Montana-Dakota Utilities, Pacific Power and Idaho Power 60 days before the window to identify critical transmission lines, substations and protective relays in evacuation and shelter zones. Request pre-deployment of mobile generator units and voltage-regulation equipment at the two largest substations serving Bozeman and Idaho Falls. Establish a 24/7 utility-operations hotline from the forward command to each regional dispatch center, and pre-authorize helicopter fuel caches at forward airfields (Gallatin County, Jackson Hole, Billings) for emergency medical supply delivery if ground routes are blocked.

Potential Improvements

1. Convoy Delivery Timeline Underestimated: Water Arrives Later Than T+12 h Target, Creating Shelter Supply Crisis

The plan states that bottled-water convoys will be 'mobilized within 12 hours' and deployed from Salt Lake City, with an implicit expectation of arrival at Bozeman and Idaho Falls by T+24 h (user constraint). However, the I-15 northbound route from Salt Lake to the shelters is the same corridor that out-of-state evacuees are likely to use if Scenario Beta triggers. Ashfall will degrade road surfaces, reduce visibility and slow all traffic. A realistic estimate under moderate ashfall and evacuation-related congestion is 18–30 hours delivery time (estimate), not 12 hours. If water convoys arrive at T+24 h or later, the shelters must sustain 10,000–20,000 people for 1–2 days on existing, likely inadequate supplies, creating a public-health crisis.

Recommendation: Pre-stage bottled water, N95 respirators and generator fuel at forward depots in Bozeman, Billings and Idaho Falls by Month -0.5, with a minimum of 10 days' supply for the planned shelter capacity (assume 15,000 at Bozeman, 10,000 at Idaho Falls). Establish a dedicated 'supply-surge' lane on I-15 northbound from T+0 to T+24, reserved exclusively for water and fuel convoys, enforced by National Guard escorts. Pre-authorize the forward command to halt non-essential evacuation traffic on I-15 for up to 30 minutes to allow high-priority water convoys to pass if the main route gridlocks. Coordinate with Utah and Wyoming departments of transportation and water authorities to identify additional water sources within 200 miles of the shelters and pre-arrange 24-hour access. Test a water-convoy exercise from Salt Lake City to Bozeman under simulated ashfall and congested-traffic conditions 30 days before the window, measuring actual travel time and identifying chokepoints.

2. Visitor Accountability and Backcountry Evacuation: 200–400 Backcountry Hikers Cannot Be Reliably Evacuated Within T+6 Hours

The plan lists a 'Visitor Headcount Reconciliation and Backcountry Sweep Protocol' but does not specify the number of active backcountry permits, the typical dispersal of permit-holders across 3,500 square miles, or how many ranger-hours and helicopter sorties are required to sweep all trailheads and camps within 6 hours. Yellowstone issues approximately 500–1,000 backcountry permits daily during peak season (estimate); locating and evacuating 300–500 scattered parties requires coordination across multiple ranger districts and helicopter support. If 50–100 backcountry parties (200–400 people estimate) cannot reach main roads within T+6 h, they may become trapped as ashfall intensifies and roads become impassable. On-foot evacuation during heavy ash exposure could require 12–24 additional hours and cause respiratory distress or hypothermia.

Recommendation: At T-24 h, issue an emergency permit cancellation and mandatory evacuation order to all outstanding backcountry permits, instructing holders to exit via designated ranger-escorted routes. Pre-position ranger teams at key backcountry junctions (Norris-to-Canyon trail, Lamar Valley research stations) by T-12 h, with satellite phones and emergency shelter supplies. Establish dynamic backcountry tracking using satellite messenger devices; at T+0, initiate hourly check-ins with all outstanding permit-holders and redirect non-responding parties to ranger-escort meeting points. Designate 2–3 last-resort wilderness shelters in areas outside the modeled ashfall footprint (e.g., South Entrance/Thorofare region), pre-stocked with food, water, first aid and N95 respirators. Coordinate with Wyoming Search and Rescue to stand by for ground-based extraction of stranded parties after the main evacuation window (T+6 h).

3. Public Compliance Risk: Conflicting Evacuation Orders and Shelter-in-Place Messaging Undermine Trust and Corridor Throughput

The plan specifies that outer-zone residents in Bozeman, Billings and Idaho Falls should be told to shelter in place or follow time-banded departure schedules (to prevent shadow evacuation). However, if a Scenario Beta trigger fires, these same populations must then evacuate immediately. This reversal could be perceived as government deception, eroding trust in official channels and causing chaotic, uncontrolled flight. If public trust collapses, uncontrolled evacuation of 50,000–200,000 outer-zone residents could begin within 2–4 hours of a Scenario Beta order, creating gridlock on I-15, I-80 and I-90 that prevents the organized Zone One evacuation and strands primary evacuees 4–8 additional hours in ash exposure.

Recommendation: Develop and pre-authorize an 'Adaptive Messaging Protocol' explaining the rationale for phased evacuation orders: initial shelter-in-place is based on current low-eruption probability; Scenario Beta escalation will be triggered by specific USGS indicators (to be published in advance); outer-zone residents should monitor official channels and expect possible reversal if indicators cross thresholds. Deliver this protocol to media outlets, emergency management offices and community leaders in Zone One communities 60 days before T+0, so the public understands the escalation logic. At T+0, rebroadcast the protocol on IPAWS and local media to reinforce the message. If a Scenario Beta trigger fires, issue separate messaging explaining the new indicator values and stating that the previous shelter-in-place order is superseded, effective immediately. Conduct a messaging credibility exercise with local government and media 60 days before the window, testing message clarity and anticipating public-response scenarios.

4. Procurement and Contracting Lead Times Not Addressed: Emergency Supply Dispatch Delayed 24–48 Hours Without Pre-Event Contracts

The plan assumes water convoys can be 'mobilized within 12 hours,' but sourcing, loading and dispatching a convoy of 20–40 water trucks requires coordination with suppliers, transportation contractors and state agencies. If contracts are not pre-positioned or suppliers are not pre-authorized, typical emergency procurement delays are 24–48 hours (estimate). A 24-hour delay in water-convoy dispatch means the convoy does not arrive at shelters until T+36 h instead of T+12 h, during which shelter occupancy could reach 15,000–20,000 people. Water shortages affecting thousands for 24+ hours increase risk of dehydration, medication non-compliance and secondary health emergencies.

Recommendation: Execute pre-event contracts with bottled-water suppliers, N95 respirator manufacturers, generator-fuel wholesalers and charter-bus operators by Month -1, with explicit 'surge-mobilization' clauses requiring 12-hour dispatch upon verbal activation by the forward command. Identify alternative suppliers (e.g., water distributors in Pocatello, ID and Butte, MT; N95 suppliers in Salt Lake City and Denver) and list them in a standby-supplier roster. Pre-authorize payment via emergency FEMA contract vehicles so suppliers can charge supplies immediately without normal competitive-bidding delays. Establish a procurement checkpoint at the forward command element tasked with tracking all inbound supply shipments and alerting the incident commander if any convoy is delayed more than 4 hours beyond dispatch.

5. FAA Airspace Grounding Coordination Incomplete: Medevac and Reconnaissance Capability Uncertain, Authority Gaps Exist

The plan states that a VEI-6 eruption will trigger grounding of FAA sectors ZLC (Salt Lake) and ZSE (Seattle) to prevent ash-engine encounters. However, the FAA operates independently and may not immediately coordinate grounding with the Unified Command's needs for medevac, reconnaissance or emergency airlift. The incident commander may want exceptions for critical patient transfers that the FAA blocks due to ash-concentration forecasts. Delays in grounding coordination could result in aircraft encountering ash within the first 2–4 hours of ashfall, adding a secondary emergency response load. Alternatively, rigid grounding without medevac exceptions could deny hospitals access to helicopter transport for critical patients, delaying transfers by 4–6 hours and causing preventable deaths.

Recommendation: Establish a pre-event coordination protocol with the FAA Regional Flight Service Stations (Salt Lake City and Seattle centers) and air-operations offices at mountain airports (Gallatin County, Jackson Hole, Billings) at least 60 days before T+0. Define an explicit trigger for airspace grounding (e.g., USGS detection of VEI-6 magma signatures, NOAA forecast of ash concentration >100 µg/m³ in flight corridors) and pre-authorize a narrow set of ash-model-cleared rotary-wing medevac and survey flight corridors below defined ash-concentration limits, approved by the Unified Command. Establish a 24/7 aviation-operations liaison at the forward command element with direct phone lines to the FAA regional desk and the military (Malmstrom AFB, Montana) to coordinate real-time flight requests and ash-model updates. Pre-authorize helicopter fuel caches at forward airfields (Gallatin County, Jackson Hole, Billings) to enable rapid deployment of medevac sorties if airspace restrictions are lifted temporarily.

6. Responder Fatigue Burnout Not Explicitly Tracked: No Fatigue-Assessment Checklists, Withdrawal Authority, or Air-Quality Monitoring at Posts

The plan specifies exposure limits and relief rotations but does not describe operational procedures for identifying responder fatigue, authorizing withdrawal from posts, or monitoring air-quality conditions at each checkpoint to trigger withdrawal thresholds. Responders working 6-hour shifts with 2-hour rest cycles may reach acute fatigue or ash-induced respiratory distress before they self-report. Without a dedicated fatigue-assessment and air-quality monitoring officer, checkpoint staffing decisions are made reactively rather than proactively, risking coverage gaps at the worst moment.

Recommendation: Assign a dedicated Responder Safety and Fatigue-Management Officer with real-time PM10/PM2.5 sensors at each traffic checkpoint and perimeter gate, updated hourly from T+0 through T+72 h. Develop fatigue-assessment checklists for on-site use, with clear withdrawal triggers (e.g., reaction-time degradation, difficulty concentrating, excessive fatigue self-reports). Pre-authorize ranger withdrawal from posts if fatigue exceeds safe limits or if air-quality readings exceed agency respiratory-protection standards. Conduct a 6-hour shift-rotation exercise at a key control point 30 days before the window, testing relief handoff protocols, N95 replacement procedures, fatigue-assessment accuracy and radio communication continuity under simulated ashfall.

7. Exclusion Perimeter and Re-Entry Access Control: Static Checkpoints Consume Guard Personnel Needed for Logistics and Shelter Security

The plan specifies a fixed checkpoint perimeter on all roads out of the evacuation zone to prevent looting and unauthorized entries. However, static checkpoints divert National Guard personnel from logistics convoy escorts and shelter security during the peak evacuation and ashfall phases. A hard perimeter with fully staffed checkpoints at every exit road requires an estimated 50–100 Guard personnel simultaneously, competing with the 30–50 person standby reserve and convoy-escort needs. The plan does not specify the trade-off between perimeter enforcement and other Guard missions.

Recommendation: Develop a tiered perimeter posture: at T+0 to T+24 (peak evacuation and ashfall onset), implement mobile roving patrols and drone surveillance in evacuated communities rather than static checkpoints, consuming fewer personnel while detecting unauthorized entries. Concentrate Guard personnel on logistics convoy escorts and shelter security during this critical phase. At T+24 onward (Phase 2 transition), if ashfall conditions permit, establish more robust static checkpoints. Pre-authorize escorted-return programs in later phases (T+48 h onward) for residents to retrieve documents, medications and animals, with responder escorts and pre-defined access windows. Conduct a perimeter-operations exercise 30 days before the window, testing mobile patrol coordination, drone deployment protocols and escorted-return logistics.

8. Zone One Resident Population Unquantified: Census Data Missing, Evacuation Timing Target May Be Infeasible

The plan specifies that Zone One (100 km radius including West Yellowstone, Gardiner and Cody) must be evacuated by T+24 h, but does not quantify the registered resident population in these communities. Without a population estimate, the plan cannot validate shelter capacity, water supply targets, bus fleet sizing, or overall corridor throughput. A shortfall in any of these could extend the Zone One clearance beyond T+24 h, into the period when ashfall may be intensifying.

Recommendation: Conduct a detailed census of registered Zone One residents (West Yellowstone, Gardiner, Cody and surrounding areas within 100 km) by Month -1, accounting for seasonal variation and summer tourism influx. Cross-reference with hotel and lodge occupancy data from concessioners and local visitor bureaus to estimate transient populations. Update shelter capacity and water-supply targets based on the actual Zone One census. Confirm that the three exit corridors (US-191/US-20 West, US-89 North, US-14/16/20 East) have sufficient throughput capacity to evacuate both Zone Zero (35,800) and Zone One residents within the T+24 h deadline, adjusting load-split percentages if needed. Conduct a full-scale Zone One evacuation drill 60 days before the window, involving local emergency management officials and concessioners.

9. Forward Command Element Location Selection Incomplete: Livingston vs. Bozeman Trade-Offs Not Analyzed

The plan names Livingston as the forward Unified Command element location with Bozeman as an alternate, but does not specify the criteria for choosing between them or document their respective advantages and disadvantages. Livingston is closer to the North Entrance (US-89) and has a preexisting National Guard tactical operations center at Camp Ravenna. Bozeman is larger, has more medical capacity and is the planned shelter site, but is 40+ miles southwest of the park. The choice affects command visibility, response latency, shelter coordination and access to backup facilities.

Recommendation: Analyze Livingston vs. Bozeman by Month -0.5 based on: (1) line-of-sight and satellite/radio coverage to all three exit corridors and shelter sites; (2) proximity to receiving hospitals (Bozeman, Livingston); (3) existing facility capacity (command ops center, power, security); (4) proximity to backup command sites (Fort Carson, Camp Ravenna); (5) local emergency management support and pre-existing coordination. Document the final choice and its rationale in a written decision memo, signed by the UC Incident Commander, by Month -0.5. If Bozeman is selected as the primary, confirm that a secondary command post is maintained at Livingston or another location with direct line-of-sight to the North Entrance corridor.

Critique and recommended actions from domain experts.

1 Expert: Volcanologist & USGS Hazard Forecaster

Knowledge: volcanic hazard assessment, eruption-probability modeling, VEI classifications, ashfall forecasting, USGS monitoring networks

Why: The Scenario Alpha/Beta trigger matrix (Section: Escalation Trigger decision, canonical facts) references a 40% VEI-6+ probability and pre-authorized threshold-based indicators, but the final USGS trigger values are listed as 'due by T+3h' with only a placeholder. This expert must harden the trigger matrix, validate the modeled ashfall footprint upon which shelter siting (T+6h) depends, and confirm the 500 km Scenario Beta ring adequacy.

What: Review and finalize the USGS trigger indicator thresholds (uplift rate, seismic magnitude, gas flux) that activate Zone One and Scenario Beta expansion by T+3h; validate the ashfall dispersion model confidence bounds (currently ±50 km) to certify the shelter-siting rule and real-time monitoring thresholds (50/100 µg/m³ PM10).

Skills: eruption probability estimation, ashfall transport modeling, seismic-swarm interpretation, real-time USGS data integration, multi-agency forecasting protocols

Search: USGS volcanologist eruption forecasting, Yellowstone hazard monitoring, ashfall dispersion modeling, VEI probability assessment

1.1 Primary Actions

1.2 Secondary Actions

1.3 Follow Up Consultation

At Month 1 (2026-11-14) review the three completed pre-authorization actions: Scenario Beta Secondary-Stage Plan (signed MOUs, hub capacity verified), Responder Exposure Protocol (relief reserve positioned, Guard reinforcement letters on file) and Ashfall Monitoring (sensor deployment confirmed, relocation protocols tested). Assess whether the plan's core bottlenecks (Gallatin Canyon, cell-tower failures, shelter siting) have been mitigated and whether hidden dependencies have emerged from exercises. Confirm that responder staffing depth is credible, that second-stage evacuation destinations are named and ready, and that the Unified Command's authority chain is unbroken from the forward element through Denver to governors. Prepare the after-action report framework and schedule the full-scale Beta exercise for Month 3 (2027-01-14). Flag any unresolved financing decisions (federal vs. state cost-share for hubs and shelter sites) for immediate senior-leadership escalation.

1.4.A Issue - Scenario Beta secondary-stage plan is a hollow pre-authorization with no executable destinations

The plan mandates a pre-authorized VEI-7 trigger that activates a 500 km evacuation order for millions of people, but names no destinations, capacity, or second-stage logistics. Denver and Cheyenne are candidates, but distances are unverified and host-community MOUs do not exist. Without a written, signed plan naming five to ten ranked hubs with bed counts and supply pre-positioning, issuing the 500 km order will trigger uncontrolled flight saturating I-15, I-80 and I-90, stranding the primary 35,800-person Zone Zero evacuation for 4–8 additional hours. This is the single largest residual risk.

1.4.B Tags

1.4.C Mitigation

Execute a written Scenario Beta Secondary-Stage Evacuation Plan by Month -2 (2026-08-14), naming at least five ranked shelter hubs outside the 500 km ring with signed host MOUs, bed counts, supply pre-positioning schedules and tiered public-messaging templates. Conduct a full-scale Beta routing and intake exercise by Month -0.5 (2026-09-29), testing bus dispatch, shelter registration and lateral-route traffic flow from each primary shelter to its secondary hub. Pre-authorize the UC to issue the 500 km order via a written trigger matrix by T+0, with the interim hub list published to the public by T+12 hours.

1.4.D Consequence

Without the secondary-stage plan, a VEI-7 trigger will activate an evacuation order for which evacuees have no published destinations. Shadow evacuation and panic will saturate the same corridors needed to clear Zone Zero, adding 4–8 hours of delay and enabling 5–20 preventable deaths. Shelters in Denver and Cheyenne will be overwhelmed without advance capacity planning, forcing emergency relocations and stranding 200–500 evacuees mid-operation.

1.4.E Root Cause

The plan was written under the constraint that pre-event lead times are unavailable and execution must begin at T+0. The decision to pre-authorize the 500 km trigger (user constraint) was made before a destination plan existed, creating a temporal mismatch: the trigger is ready to fire, but the execution plan does not exist. This is a process gap, not an operational oversight.

1.5.A Issue - Responder staffing is exhausted during peak evacuation with zero relief depth and no contingency for attrition

The plan budgets 100–150 NPS rangers at a 1.5 relief ratio, yielding 67–100 concurrent positions across three exits, perimeter gates, and comms posts during the T+2 to T+8 evacuation peak. A single injury, equipment failure, or traffic incident at a critical checkpoint (e.g., Mammoth or Gallatin Canyon) could remove 5–10 responders, leaving that post below safe staffing and halting traffic for 2–4 hours. The plan does not pre-position a standby reserve or define responder exposure limits (shift length, rest cycles, N95 allocation). Without explicit protection, responder illness from ash exposure will degrade the force just as the evacuation peaks.

1.5.B Tags

1.5.C Mitigation

Define a written Responder Exposure and Relief Protocol by Month -1 (2026-09-14) specifying 6-hour shifts at ash-exposed posts, mandatory 2-hour rest with N95 replacement, and full withdrawal after 18 consecutive hours. Pre-position a 30–50 person standby reserve from out-of-region agencies (Colorado Parks and Wildlife, Wyoming Game and Fish) at a logistics depot outside the ash zone by Month -0.5 (2026-09-29). Secure pre-event commitments from Fort Carson and state Guard Joint Task Force for reinforcement without state-level approval delays. Conduct a 6-hour shift-rotation exercise at a checkpoint 30 days before the window to test relief handoff and fatigue-assessment protocols.

1.5.D Consequence

All 100–150 rangers will be consumed during the T+2 to T+8 peak with no coverage cushion. A single traffic incident (vehicle breakdown, secondary slide) could halt one checkpoint for 2–4 hours, stranding 500–2,000 vehicles in ash and cascading 1–2 hours of delay to the entire evacuation. Responder respiratory illness will degrade the force at the peak moment, reducing traffic throughput by 20–40% and extending clearance by 2–4 additional hours.

1.5.E Root Cause

Responder staffing levels were estimated at 100–150 rangers based on park baseline. The plan does not account for the additional posts needed for a three-exit contraflow operation or for the fatigue and illness effects of working in ashfall. The 1.5 relief ratio is a standard assumption, but it is inadequate for a 72-hour sustained operation with zero pre-event lead time for recruiting or training reinforcements.

1.6.A Issue - Shelter siting based on a single T+6 forecast update ignores ashfall forecast uncertainty of ±50 km and masks clog rate

The plan selects final shelter sites at T+6 hours from the latest NOAA/USGS plume forecast. Ashfall modeling uncertainty is typically ±50 km or larger, and volcanic-ash forecasts from an unprecedented VEI-6 event have no ground-truth calibration. If actual ashfall diverges from the forecast by 50 km southward or doubles in intensity, shelter sites (e.g., Bozeman, Idaho Falls) could be placed in moderate-to-heavy ash within 4–6 hours of occupancy. The plan pre-stages only 100,000 N95 masks for 35,800 evacuees; assuming a 70% occupancy rate (25,060 people), masks clog after 6–8 hours in heavy ashfall and require replacement cycles not detailed in the plan. No real-time monitoring or relocation protocol exists.

1.6.B Tags

1.6.C Mitigation

Deploy continuous PM10/PM2.5 sensors and visual ash-depth stations at Bozeman, Idaho Falls and the forward command by Month -0.5 (2026-09-29), with automated hourly updates to USGS/NOAA liaisons and alert thresholds (PM10 >50 µg/m³ triggers forecast update; >100 µg/m³ triggers shelter-suitability review). Develop a ranked three-shelter backup system for each primary site by Month -1 (2026-09-14), identifying second and third locations 50+ km upwind with pre-authorized 4-hour relocation protocols. Pre-stage a supplemental 100,000 N95 masks at Billings or Salt Lake City hub by Month -0.5 (2026-09-29) with standing 8-hour ground-convoy or helicopter delivery agreements. Conduct a full shelter-siting and relocation exercise 30 days before the window (Month -0.5, 2026-09-29).

1.6.D Consequence

Ashfall diverging 50 km from forecast or doubling in intensity will place 10,000–15,000 evacuees in moderate-to-heavy ash within 4–6 hours, forcing emergency relocation mid-operation. Without relocation protocols and standby facilities, 200–500 people will be stranded or delayed by 4–8 hours. Mask clogging without replacement logistics will leave evacuees unprotected for 6–12 hours, causing respiratory distress in 500–1,000 people and forcing 100–200 hospital transfers, overwhelming receiving facilities.

1.6.E Root Cause

Ashfall forecasting for a VEI-6 event is unprecedented; model uncertainty ranges widely and is often not disclosed. The plan assumes a single forecast update at T+6 hours is sufficient for a 24-hour shelter occupancy. N95 clog rates in heavy ash (6–8 hours) are documented in industrial and wildfire contexts, but the plan does not specify replacement cycles or a supplemental reserve, treating the 100,000 stock as static.

2 Expert: Regional Emergency Management & Multi-Jurisdiction Coordination Director

Knowledge: NIMS/ICS, Unified Command structure, FEMA Region operations, cross-state EMAC mutual aid, governor authority transfer, incident command handoff protocols

Why: The Command Structure decision and canonical facts specify a forward UC element at Livingston, Region 10 liaison from T+0, and NPS-to-governor authority transfer at park boundaries, yet the implementation pathway from verbal authorization (T+6h) to signed MOUs (Month 1 = 2026-11-14) remains incomplete. This expert must operationalize the Unified Command, resolve the FEMA Region 8/10 seam, and certify that the Boundary Coordination Officer's delegated authority survives legal and jurisdictional challenge.

What: Design the Unified Command organizational chart, communication protocols and decision-authority matrix from T+0 through T+72h; produce a template NPS-to-governor handoff protocol and written EMAC mutual-aid activation language for Montana, Wyoming and Idaho by Month 0.5 (2026-10-29); confirm that the Boundary Coordination Officer's unilateral reroute and shelter-assignment authority (5-minute comms loss tolerance) is legally defensible under Stafford Act and state emergency powers.

Skills: incident command system operations, multi-state coordination, FEMA grant/reimbursement rules, emergency declarations and legal authority, interagency communications protocols

Search: FEMA Region 8 incident commander, Unified Command multi-state evacuation, EMAC mutual aid coordinator, emergency management legal authority

2.1 Primary Actions

2.2 Secondary Actions

2.3 Follow Up Consultation

At the next meeting, confirm: (1) Which federal agency (FEMA Region VIII, NPS or Denver RRCC) owns the Scenario Beta hub-site search, MOU signature authority and hub pre-positioning budget? (2) What is the written authority chain for the governors to approve the Unified Command's Zone One and Beta orders if pre-event MOUs are not signed? (3) Does the responder relief reserve (30–50 out-of-region staff) come from National Guard, state wildlife agencies or FEMA contracts, and who authorizes their deployment? (4) Will the plan include a written decision rule for whether shelter relocation (if ashfall exceeds forecast) triggers a shelter-in-place order for delayed evacuees or an extension of the T+24 h Phase 2 deadline? (5) Are water-convoy dispatch contracts with Salt Lake City distributors already in place for 12-hour verbal activation, or must they be negotiated in Months 1–3 (2026-11-14 to 2027-01-14)? (6) Who owns the ashfall forecast updates (NOAA, USGS, forward command?) and what is the decision cadence for triggering shelter suitability reviews and relocations?

2.4.A Issue - Scenario Beta destination plan is a placeholder, not an executable strategy

The plan mandates a pre-authorized VEI-7 order at T+0 that triggers a 500 km evacuation affecting millions of people, but names no specific secondary-stage hubs, no capacity commitments, and no signed MOUs from host counties. Denver and Cheyenne are candidates but distances are unverified; Salt Lake City, Billings and Bozeman are inside the ring and cannot serve. Without a written Beta destination plan by Month 1 (2026-11-14), the trigger is hollow—it activates an evacuation order for which evacuees have no published shelter addresses, causing chaotic uncontrolled flight that saturates I-15 and I-90, delays the primary Zone Zero evacuation by 4–8 hours, and strands 5,000–10,000 people in ash-exposed areas.

2.4.B Tags

2.4.C Mitigation

Execute a written Scenario Beta Secondary-Stage Evacuation Plan by Month 1 (2026-11-14) naming at least five ranked shelter hubs outside the 500 km ring (Denver, Cheyenne, Salida CO, Laramie WY, Ogden UT recommended; verify distances). Secure signed MOUs from each host county confirming bed capacity, medical staff, water and fuel availability for 100,000–500,000 evacuees on 48-hour notice. Publish tiered ring-based messaging (0–100 km organized, 100–250 km time-banded, 250–500 km staged) and conduct a full-scale Beta evacuation exercise with all states and hubs by Month 3 (2027-01-14).

2.4.D Consequence

Pre-authorized Beta order issued at T+12–24 h without destination clarity triggers tens of thousands of unordered departures from outer zones; I-15, I-90 and US-191 saturate within 4–6 hours; primary Zone Zero evacuation stalls as unordered traffic blocks exits; evacuation delay cascades by 4–8 hours; 5,000–10,000 people remain in ash-exposed areas when Scenario Alpha transitions to Beta; 20–50 preventable respiratory and trauma deaths; total cascade cost USD 200–500 million in additional response and recovery.

2.4.E Root Cause

Empty

2.5.A Issue - Responder staffing has zero relief depth during the T+2 to T+8 peak evacuation window

The plan budgets 100–150 NPS rangers at a 1.5 relief ratio, yielding only 67–100 concurrent positions across three exits, perimeters, comms sites and backcountry sweeps during the T+2 to T+8 evacuation peak when load is highest. A single traffic incident, equipment breakdown or injury at a critical checkpoint (Gallatin Canyon, Gardiner) will halt one corridor for 2–4 hours, stranding 500–2,000 vehicles in ash-heavy zones. Responder N95 stock is unsized and may be drawn from the 100,000 civilian reserve, eroding civilian protection. No written exposure limits or pre-positioned relief reserve exist.

2.5.B Tags

2.5.C Mitigation

Issue a written Responder Exposure and Relief Protocol by Month -1 (2026-09-14, simulated date; apply at Month 0 = 2026-10-14 T+0) specifying max 6-hour shifts at ash-exposed posts, 2-hour rest with N95 replacement, withdrawal after 18 consecutive hours. Pre-position a 30–50 person standby reserve from Colorado Parks and Wildlife, Wyoming Game and Fish, and Idaho Lands at a logistics depot in Billings by Month 0 (2026-10-14) T-12 h, trained and pre-authorized for 4-hour deployment dispatch. Size responder N95 respirators separately from the 100,000 civilian stock (recommend 150,000–200,000 total responder stock). Conduct a 6-hour shift-rotation exercise at Mammoth or Gardiner checkpoint Month 0 (2026-10-14) T-12 h.

2.5.D Consequence

Without relief depth, all responders are consumed during T+2 to T+8; a single 30-minute incident at Gallatin Canyon creates a 45-minute halt, stranding 500–2,000 vehicles; diversion adds 2–4 hours to their transit; total evacuation delay cascades by 1–3 hours; 10–20% of drivers take unintended routes; 200–500 evacuees remain in ash-exposed zones; 5–15 preventable respiratory injuries; evacuation cost increases by USD 50–100 million due to extended responder and shelter operations.

2.5.E Root Cause

Empty

2.6.A Issue - Shelter siting chosen only at T+6 hours leaves no margin for ashfall forecast error and relocation logistics

The plan defers final shelter-site selection to T+6 hours based on a single NOAA/USGS plume forecast update. Ashfall model uncertainty of ±50 km is documented in comparable eruptions; a 50 km southward shift or 2–3x intensity increase could place Bozeman or Idaho Falls directly in moderate-to-heavy ash at T+6–12 hours when 10,000–15,000 evacuees are already sheltered there. Relocation protocols and backup-site activation procedures do not exist. The 100,000 civilian N95 stock has no sizing basis and masks clog rapidly in heavy ash. If shelters must be evacuated mid-operation, transport buses and responders will be diverted from the primary evacuation.

2.6.B Tags

2.6.C Mitigation

Deploy real-time PM10 and PM2.5 sensors at each shelter and the forward command by Month 0 (2026-10-14) T+0, with automated hourly feeds to the forward command and USGS/NOAA liaison. Pre-identify and pre-survey ranked backup shelter locations 50+ km upwind of each primary site by Month 0 (2026-10-14) T-12 h. Issue a written 4-hour relocation protocol by Month 0 (2026-10-14) T-12 h with pre-authorized shelter-transfer authority, notification procedures via IPAWS/WEA, and pre-positioned buses for up to 10,000 evacuees. Pre-stage a supplemental 100,000 N95 respirators at Billings or Salt Lake City by Month 0 (2026-10-14) T-12 h with 8-hour ground-convoy delivery commitment. Conduct a shelter-siting and relocation exercise with NOAA, USGS and all three shelter operators Month 0 (2026-10-14) T-12 h.

2.6.D Consequence

Ashfall forecast error of ±50 km or 2–3x intensity error leaves shelters in moderate-to-heavy ash by T+12–18 hours; 10,000–15,000 evacuees require emergency relocation; buses and responders diverted from primary evacuation; relocation logistics consume 4–8 hours; 200–500 evacuees stranded during transfer; shelter-in-place order issued for delayed residents; 50–100 respiratory injuries; evacuee confidence in the response collapses; compliance with subsequent orders drops by 20–40%; cost of emergency relocation USD 20–50 million.

2.6.E Root Cause

Empty

3 Expert: Transportation Operations & Contraflow Specialist

Knowledge: contraflow operations, highway traffic engineering, capacity analysis, bottleneck mitigation, incident response routing, geotechnical road hazards

Why: The Egress Corridor decision specifies a 50/30/20% split across three exits and a 45-minute blockage diversion threshold, yet the plan names only a 2-team tow/rockfall asset and lacks quantified corridor capacity under ash (visibility, road surface degradation). This expert must validate the throughput model, size the pre-placed equipment and standby capacity, and certify that the diversion protocol avoids cascading secondary blockages.

What: Audit the 660 vehicles/hour per-exit throughput estimate against observed contraflow capacity on US-191, US-20 and US-89 under ashfall conditions; quantify the minimum tow/rockfall asset count needed to clear a typical Gallatin Canyon blockage within 15 minutes; design a Loss-of-Exit Contingency protocol that diverts overflow without overloading surviving corridors and specifies hard abort criteria for South Entrance clearance attempts (currently M4.0+ tremor).

Skills: contraflow setup and termini design, highway-capacity modeling, bottleneck analysis, equipment pre-positioning, ashfall-road interaction, incident traffic management

Search: contraflow traffic operations highway, Gallatin Canyon geotechnical hazards, mountain-pass evacuation routing, volcanic ashfall road impact, I-90 capacity analysis

3.1 Primary Actions

3.2 Secondary Actions

3.3 Follow Up Consultation

"In the next consultation, address: (1) the empirical contraflow termini design, including measured staging-lot capacity, turn-pocket geometry and validated throughput; (2) the Scenario Beta population census by ring and hub capacity commitments, with a published tier-assignment map and time-banded schedule; (3) the geotechnical findings on Gallatin Canyon clearance feasibility and secondary-slide risk, with revised thresholds for the 15-minute arrival and 45-minute diversion rules; (4) results of the contraflow terminus and supply-convoy exercises, with any required revisions to the exit split or routing strategy; (5) draft MOUs from hub emergency managers and utility operators confirming resource and logistics commitments; (6) the Corridor Capacity Operations Center design and integration with state traffic management; (7) updates from USGS on Scenario Beta population estimates and revised evacuation-ring geometry if applicable. Schedule a multi-state command-authority exercise by Month -1.5 (2026-08-29) testing the boundary handoff under escalation scenarios, and document any jurisdictional conflicts or communication gaps to be resolved by Month -1 (2026-09-14)."

3.4.A Issue - Contraflow Termini and Gateway Bottleneck Design Lacks Concrete Staging Geometry

The plan specifies three exits (West US-20/US-191, North US-89, East US-14/16/20) and a 50/30/20% split but provides no termini design: where do contraflow lanes end? How many turn pockets at Mammoth, Gardiner, West Yellowstone? What is the queuing buffer at each gate before vehicles are staged? Gallatin Canyon is cited as a blockage risk, but no capacity analysis shows whether the canyon itself is the bottleneck or the staging lot upstream. Without termini geometry, you cannot verify that 660 vehicles/hour per exit is achievable, and you risk gridlock at the staging lot rather than the road.

3.4.B Tags

3.4.C Mitigation

Commission a rapid-deployment engineer from USGS or state DOT to conduct a one-day site survey at each terminus (Mammoth, Gardiner staging, West Yellowstone staging, Cody entrance area) by Month -0.5 (2026-09-29). Measure: parking-lot footprint and current capacity; distance from lot exit to the contraflow begin line; turn-pocket dimensions; queue-storage length in vehicles; and the available staging buffer. Calculate: queue-storage duration at 660 veh/h inflow; bottleneck location (lot saturation vs. road capacity). If lot-saturation occurs before road-capacity saturation, revise the split or add temporary staging overflow (parking-lot chaining, nearby school parking). If the canyon itself is the bottleneck, model bypass or single-lane recovery protocols.

3.4.D Consequence

Without termini geometry validation, the plan assumes 660 veh/h is possible but may discover at T+2 h that the staging lot holds only 400 vehicles, causing queues to back up into the park interior, preventing the T+6 h clearance gate and stranding 2,000–5,000 vehicles inside the park when ash arrives. Gridlock at a terminus costs 3–6 hours of delay and invalidates the entire evacuation schedule.

3.4.E Root Cause

The plan adopts the three-exit split as a strategic decision but skips the tactical engineering step: measuring existing lot capacity, turn-radius constraints and queue storage. Contraflow design cannot proceed without this baseline. The 660 vehicles/hour throughput is stated as an average (estimate) but not validated against the physical termini.

3.5.A Issue - Geotechnical Road Hazard Clearance Strategy Assumes Optimistic Single-Team Timelines Without Empirical Basis

The plan pre-positions 'at least 2 tow/rockfall teams' to reach Gallatin Canyon within 15 minutes and sets a 45-minute blockage threshold before diversion. But the plan provides no geotechnical reconnaissance data: How unstable is Gallatin Canyon during a seismic swarm? What is the probability of a secondary slide during clearance? How long does single-lane debris removal actually take under ashfall conditions? The South Entrance landslide is ''written off'' with a 4-hour time-box, but no survey exists to quantify the debris volume or confirm that a bypass is feasible. Without empirical data, the 15-minute arrival and 45-minute diversion thresholds are guesses that may be impossible to meet.

3.5.B Tags

3.5.C Mitigation

Assign a structural geotechnical engineer from the USGS Volcano Disaster Assistance Program to conduct a rapid survey of Gallatin Canyon (10 km of highest-risk sections) and the South Entrance slide 60 days before T+0 (Month -1.5, 2026-08-29). Deliverables: (1) geotechnical log and slope-stability assessment under seismic-swarm conditions; (2) estimated debris-removal time per 10 m of blockage in wet and dry conditions; (3) secondary-slide probability during clearance; (4) a ranked list of safe turn-out and crew-staging zones; (5) South Entrance bypass feasibility or single-lane clearance volumetric estimate. Based on the survey, revise the 15-minute arrival and 45-minute diversion thresholds to match actual conditions. If secondary-slide risk exceeds 20% during work, write off Gallatin Canyon clearance and commit all load to the northern and eastern exits. Pre-position monitoring drones and motion sensors at incipient-failure zones with real-time alerts to crews.

3.5.D Consequence

If a rockfall clears in 30 minutes under ideal conditions but the plan assumes 45 minutes, the real throughput is higher and the diversion threshold is wasted conservatism. Conversely, if debris removal takes 90 minutes in ashfall with reduced visibility and equipment clogging, the 45-minute threshold fires too early, diverting traffic unnecessarily. Worse, if crews clear the first blockage but a secondary slide occurs during clearance, crews and equipment are lost, and the corridor remains closed for 6–12 hours while recovery machinery is mobilized. The plan's diversion rule then cascades 3,000–6,000 vehicles to the remaining exits, triggering the 2–4 hour delay that breaks the T+6 h gate.

3.5.E Root Cause

The plan specifies response actions (pre-position teams, 45-min threshold, tow assets) but does not ground them in geotechnical data. Contraflow under active seismic conditions is hazardous; crews working on unstable slopes during a magma-ascent swarm face a cumulative risk of entrapment or secondary slides that is not quantified. The plan treats Gallatin Canyon and the South Entrance as static blockage scenarios, not as dynamic hazard zones where the ground may fail again during clearance work.

3.6.A Issue - Scenario Beta 500 km Ring Capacity Gap and Unquantified External Population Create Cascade-Failure Risk at T+12 h Decision Point

The plan pre-authorizes a 500 km Scenario Beta evacuation order but names only two provisional hubs (Denver, Cheyenne) without verifying distances or capacities. The canonical facts note that ''millions of people'' lie in the 500 km ring, not quantified. When the Beta trigger fires at T+12 h (proposed), the UC will issue an evacuation order for an unquantified population with no published destinations, causing uncontrolled shadow evacuation from outer-zone residents (Bozeman, Billings, Idaho Falls) who will flee without waiting for assignments. This uncontrolled flight saturates I-15, I-80 and I-90 before the primary 35,800 Zone Zero evacuees clear, adding 4–8 hours to their transit and stranding them in ash for extended periods. The plan offers no queue-management strategy, no pre-positioned supply caches on the I-15/I-80/I-90 corridor outside the ash zone, and no time-banded execution that separates organized from shadow evacuation.

3.6.B Tags

3.6.C Mitigation

Before Month 0 (2026-10-14) (by 2026-10-14), commission a rapid census and capacity study: (1) quantify the population in each ring (0–100 km, 100–250 km, 250–500 km) down to county or community level, breaking out families, vehicle-less, and special-needs; (2) verify distances from the Yellowstone center to Denver, Cheyenne, Billings and any other candidate hub; (3) contact each hub's emergency management and shelter operators, obtaining written capacity estimates for 24-hour occupancy and 10-day sustained operations. (4) Develop a written Scenario Beta execution plan with three ring-based phases: immediate organized evacuation for Zone One (0–100 km, managed like Phase 2); time-banded evacuation for 100–250 km (assigned departure windows by county, released on published schedule); and staged departure for 250–500 km (self-evacuated, self-supplied, no shelter assignment). (5) Obtain signed MOUs from hub counties and facility operators confirming bed capacity and supply commitment. (6) Issue a public-facing ''Scenario Beta Tier System'' document (pre-event, published by Month 0 = 2026-10-14 start date) that names the hubs, specifies which zip codes are in each tier, and explains the time-banded schedule, so outer-zone residents know not to flee at T+12 h but to wait for their assigned window. (7) Pre-position 30 days before T+0 a 20,000-person emergency supply cache (water, food, N95, fuel, medical) at an intermediate location on I-80 or I-90 outside the ash footprint, accessible to any stranded outer-zone evacuees who do flee early.

3.6.D Consequence

If the Scenario Beta trigger fires at T+12 h with no hub destinations or time-banded schedule published, uncontrolled outer-zone evacuation begins immediately. An estimated 50,000–200,000 additional people (estimate) begin driving toward Salt Lake City, Denver and Cheyenne without assignments, saturating I-15 northbound and I-80 eastbound by T+14 h. The concurrent Zone Zero evacuees, still exiting through US-191 and I-90 toward Bozeman and Livingston, are forced to queue behind outer-zone traffic. Zone One residents (Gardiner, West Yellowstone, Cody) exit at T+6–T+24 h, finding I-90 and I-15 clogged with unmanaged outer-zone vehicles. The net effect: Zone Zero clearance slips from T+6 h target to T+10–T+12 h, Zone One clearance slips from T+24 h to T+30–T+36 h. Up to 5,000–10,000 Zone Zero and Zone One evacuees remain sheltered in areas expecting ashfall at T+8–T+16 h, and respiratory-injury rates spike by 20–50% due to extended exposure.

3.6.E Root Cause

The plan treats Scenario Beta as a binary decision (trigger fires, UC orders 500 km evacuation) but defers all second-stage execution planning to Month 1 (2026-11-14), after T+0 has begun. At T+12 h, when the trigger is expected to fire, the plan has no specific destinations, no capacity commitments, and no time-banded evacuation schedule published to the public. Uncontrolled flight is then inevitable, and the primary Zone Zero clearance fails because the corridors are clogged by unmanaged outer-zone residents.

4 Expert: Supply Chain & Logistical Resilience Strategist

Knowledge: supply-chain mapping, procurement lead times, fuel and water logistics, forward-depot siting, ashfall supply-chain disruption, FEMA contract vehicle activation

Why: The Ashfall Life-Support Supply decision and canonical facts require water delivery to shelters by T+24h but cite T+18–30h arrival time as an estimate, with forward depots and FEMA surge clauses as mitigation. The responder exposure limits assume a 30–50 person standby reserve by T+0.5, and the 100,000 civilian N95 stock lacks a replacement-cycle plan if consumption exceeds 20% per day. This expert must close the procurement timeline and size the pre-positioned supplies to make the T+24h water delivery and responder relief credible.

What: Map the complete water, fuel and N95 supply chain from T+0 to T+72h (source → forward depot → shelter), quantifying dispatch-to-arrival time under ashfall road congestion; size forward depots at Bozeman, Billings and Idaho Falls to deliver the 1.43 million liter water target by T+24h; develop a tiered responder N95 replacement protocol (consumption threshold, backup source, 48-hour resupply cycle) and secure written 12-hour dispatch commitments from Salt Lake City and regional distributors by Month 0 (2026-10-14).

Skills: supply-chain mapping and lead-time analysis, logistics network optimization, ashfall supply-chain contingency, FEMA contract vehicle leverage, forward-depot operations, fuel/water distribution

Search: FEMA logistics coordinator disaster supply chain, water convoys emergency operations, forward depot siting N95 PPE, Stafford Act procurement acceleration

4.1 Primary Actions

4.2 Secondary Actions

4.3 Follow Up Consultation

At Month 1 (2026-11-14): review completion of the written Scenario Beta plan, responder relief protocols, and ashfall monitoring infrastructure. Validate that governor MOUs and FEMA Region 10 liaison arrangements are in place. Confirm that at least 5 ranked hubs outside the 500 km ring have signed capacity commitments and pre-positioned supplies. Identify any gaps in responder standby-reserve activation authority or ashfall forecast accuracy that were not discovered during the pre-window exercises. Finalize the after-action report framework and schedule the post-Month 3 (2027-01-14) lessons-learned workshop.

4.4.A Issue - Scenario Beta Second-Stage Hub Plan Is Hollow Without Quantified Population and Destination Capacity

The plan pre-authorizes a Scenario Beta 500 km evacuation order but names no confirmed hubs, population estimates, or capacity commitments. Documents state millions of people at risk, but Denver and Cheyenne distances remain unverified. Without a written destination plan by T+12 hours, issuing the 500 km order will trigger uncontrolled flight saturating I-15, I-80 and I-90, adding 4–8 hours of delay to the primary Zone Zero evacuation and stranding 5,000–20,000 people in ashfall zones.

4.4.B Tags

4.4.C Mitigation

Execute a written Scenario Beta Secondary-Stage Evacuation Plan by Month -2 (2026-08-14), naming five to ten ranked hubs outside the 500 km ring with signed MOUs from host counties confirming bed and medical-staff capacity for 100,000–500,000 evacuees. Pre-stage water, N95 and food supplies at secondary hubs by Month -1 (2026-09-14). Issue interim ranked hub list by T+12 hours. Conduct a full-scale Scenario Beta exercise by Month 3 (2027-01-14), testing messaging, routing and shelter intake under congestion.

4.4.D Consequence

Without a destination plan, a pre-authorized Scenario Beta order will activate evacuation for millions of people with no published shelter addresses. Drivers will flee on their own to wherever maps suggest safety, saturating I-15 northbound and I-80 eastbound. The primary Zone Zero evacuation (35,000 park visitors) will be delayed 4–8 hours by shadow evacuation congestion. An estimated 5,000–20,000 evacuees will be stranded in moderate ashfall, increasing respiratory-injury hospitalizations by 30–50% and preventable deaths by 5–20.

4.4.E Root Cause

The plan conflates a pre-authorized trigger (issuing the 500 km order quickly) with an executable plan (telling evacuees where to go). The decision to pre-authorize the trigger was sound, but it was decoupled from the downstream logistics. No second-stage hub MOUs, population estimates or destination messaging were developed before Month 0 (2026-10-14), so execution is now blocked until Months 1–3 (2026-11-14 to 2027-01-14). The project start (Month 0 = 2026-10-14) was set without pre-event lead time for hub planning, forcing all hardening into post-event operations when no time remains.

4.5.A Issue - Responder Staffing Has Zero Relief Depth During the T+2 to T+8 Peak Evacuation

The plan budgets 100–150 NPS rangers with 1.5 relief ratio, yielding 67–100 concurrent positions across three contraflow checkpoints, perimeter gates and sweep teams during the T+2 to T+8 peak. A single traffic incident (vehicle breakdown, rockfall closure lasting 30+ minutes) at a checkpoint will consume all available coverage, halting one corridor for 2–4 hours. No separate responder N95 inventory is defined, so civilian mask depletion will deplete responder protection. No standby reserve is pre-positioned, so reinforcement will take 6–12 hours to arrive.

4.5.B Tags

4.5.C Mitigation

Issue a written Responder Exposure and Relief Protocol by Month -1 (2026-09-14), specifying max 6-hour shifts, 2-hour rest with N95 replacement, and full withdrawal after 18 hours. Pre-position a 30–50 person standby reserve from out-of-region agencies (Colorado Parks and Wildlife, Wyoming Game and Fish, Idaho Department of Lands) at a Billings or Cheyenne logistics depot by Month -0.5 (2026-09-29). Secure pre-event Guard reinforcement commitments. Size and pre-stage separate responder N95 inventory (estimated 150,000–200,000 additional to the 100,000 civilian stock). Conduct a shift-rotation exercise 30 days before the window.

4.5.D Consequence

Without explicit relief depth and standby reserves, all rangers will be at or beyond fatigue threshold by T+6 hours. A single 30-minute vehicle breakdown at a checkpoint during peak outflow will halt 500–2,000 vehicles because no relief operator can replace the post holder. Traffic will queue backward into the park interior or upstream highways, delaying evacuees 2–4 hours and trapping 500–2,000 people in ash-exposure zones during peak ashfall hours (T+8 to T+16 estimated). Respiratory injuries among delayed evacuees will increase 40–60%; preventable deaths from entrapment in heavy ashfall estimated 3–8.

4.5.E Root Cause

The responder staffing estimate was drawn from a generic evacuation baseline without accounting for the extreme conditions (ash, tremor, roadblocks, sweeps) and the compressed T+6 hour deadline. The plan did not size a separate responder N95 inventory or pre-position relief personnel outside the affected region, assuming that rangers could sustain 18–24 consecutive hours on a single shift. No relief-rotation exercise was planned before Month 0 (2026-10-14) to validate the 6-hour shift limit or discover equipment gaps.

4.6.A Issue - Ashfall Forecast Uncertainty of ±50 km and T+6 Hour Shelter Siting Creates Relocation Risk Mid-Operation

The plan selects final shelter sites at T+6 hours using a single NOAA/USGS plume forecast. Ashfall from a VEI-6 event has never been directly observed in North America; forecast uncertainty is estimated at ±50 km or more. A 50 km southward shift or doubling of ashfall intensity could place Bozeman or Idaho Falls shelters in moderate-to-heavy ash (>100 µg/m³ PM10). No real-time PM10 monitoring is planned at shelters; no relocation protocols exist. At T+24 hours or later, 10,000–15,000 evacuees would require emergency relocation, consuming responder hours needed to sustain shelter operations or prevent looting.

4.6.B Tags

4.6.C Mitigation

Deploy continuous PM10/PM2.5 sensors and ash-depth measurement at Bozeman, Idaho Falls and the forward command by Month -0.5 (2026-09-29), with hourly data feeds and alert thresholds (>50 µg/m³ triggers forecast update; >100 µg/m³ triggers shelter-suitability review). Develop and pre-authorize a ranked three-shelter backup system for each primary site by Month -1 (2026-09-14), with locations 50+ km upwind and 4-hour activation protocols. Pre-stage supplemental 100,000 N95 masks at Billings or Salt Lake City. Conduct an air-quality and shelter-relocation exercise 30 days before the window.

4.6.D Consequence

If actual ashfall differs from forecast by 50 km or exceeds intensity estimates by 2–3x, shelters will accumulate heavy ash after T+12 hours. At T+18–24 hours, evacuees will experience respiratory distress and demand relocation. Without pre-authorized backup sites and relocation protocols, shelter operators will face uncontrolled departures and uncoordinated movement to uncertain destinations. An estimated 200–500 evacuees will be stranded in moderate-to-heavy ash during relocation (48–72 hour exposure), increasing hospitalization for respiratory distress by 50–100% and preventable deaths by 5–15.

4.6.E Root Cause

The plan assumes that a T+6 hour forecast is reliable enough to siting decisions that will hold for 96+ hours of evacuation and shelter operations. Volcanic ashfall is a low-probability, high-uncertainty phenomenon; no North American precedent exists for VEI-6 ashfall plume forecasting accuracy. The plan did not allocate real-time PM10 monitoring or relocation protocols, treating shelter sites as fixed once selected. This underestimates both forecast error and the need for adaptive management during the operation.

5 Expert: Public Health & Mass-Casualty Medical Logistics Director

Knowledge: respiratory disease epidemiology, field triage systems, mass-casualty shelter protocols, hospital surge capacity, ashfall health impacts, emergency medical supply chain

Why: The Hospital Surge Dispersal decision and canonical facts cite respiratory distress cases and pre-staging N95s for 100,000 civilians, yet the plan names only three receiving hospitals and lacks a clinical surge protocol for the 10,000–20,000 additional respiratory cases (estimate) expected by T+24h. This expert must size hospital surge, validate the N95 consumption model, and certify that field triage and transfer protocols prevent hospital collapse during peak ashfall.

What: Design a hospital surge-capacity matrix for Bozeman, Livingston and Idaho Falls, quantifying bed availability by acuity tier and respiratory-case routing; validate the 100,000 N95 replacement-cycle plan against observed ashfall respiratory-case loads; produce a field-triage algorithm for shelter intake that identifies cases requiring hospital transport within 2 hours of arrival, and establish a mutual-aid protocol for transferring overflowing respiratory patients to Denver and Salt Lake City facilities by helicopter or ground ambulance.

Skills: epidemiologic modeling of ashfall health impacts, emergency-department surge protocols, respiratory-protection effectiveness validation, field-triage algorithm design, medical-supply consumption forecasting, inter-hospital patient-transfer logistics

Search: mass casualty surge capacity hospital, ashfall respiratory disease outbreak response, emergency medical triage field protocol, volcanic ash health impact epidemiology

5.1 Primary Actions

5.2 Secondary Actions

5.3 Follow Up Consultation

In the next consultation, confirm: (1) signed acceptance letters and capacity commitments from Denver, Cheyenne and backup hubs by Month 1 (2026-11-14); (2) completion of responder staffing, N95 sizing and relief-reserve pre-positioning by Month -0.5 (2026-09-29); (3) real-time ash monitoring installation and backup-shelter identification by Month -0.5 (2026-09-29); (4) results of three full-scale exercises (Beta routing, shift rotation, shelter relocation) conducted by Month -0.5 (2026-09-29). Discuss any shortfalls in hub validation, responder depth or monitoring deployment as blockers to T+0 activation. Review after-action reports from exercises to identify operational gaps in boundary coordination, fuel logistics and shelter-intake protocols. Establish metrics for Months 1–3 (2026-11-14 to 2027-01-14) to track MOU completion, final Beta plan signing and multi-state command-authority exercise results.

5.4.A Issue - Scenario Beta second-stage hub destinations are named but unvalidated; no capacity, distance or survivability data exists.

The plan states Denver and Cheyenne as Beta destinations outside the 500 km ring, but provides no written confirmation that these cities accept evacuees, have shelter capacity for 100,000–500,000 additional people, or lie outside the ashfall footprint. Distance to both hubs from Yellowstone is not verified. Without signed MOUs and pre-positioned supplies at each hub, a pre-authorized VEI-7 trigger that activates a 500 km order will release hundreds of thousands of people onto I-15, I-80 and I-90 with published destinations that may not have accepted them. This invalidates the trigger itself.

5.4.B Tags

5.4.C Mitigation

By Month -0.5 (2026-09-29): confirm written acceptance letters from Denver and Cheyenne city and county governments; measure distances; model ashfall at each hub using the USGS plume forecast. By Month 1 (2026-11-14): execute signed MOUs with each hub naming shelter capacity, medical-staff commitments and supply pre-positioning. Identify at least one additional ranked hub outside the ring (e.g., Rapid City, SD or Casper, WY) as backup. Conduct a tabletop exercise with all hubs to confirm routing and intake protocols.

5.4.D Consequence

Without validated hubs, the pre-authorized Beta trigger becomes an unfulfillable order. Evacuees will be directed to destinations that do not expect them, creating bottlenecks at interstates and exposing 100,000–500,000 people to unmanaged ashfall. Shadow evacuation will saturate I-90 and I-15, stranding the primary 35,800 Zone Zero evacuees for 4–8 additional hours and preventing hospital patient transfers. 5–20 preventable deaths will result from respiratory distress and delayed medical care.

5.4.E Root Cause

The documents name Beta hubs as examples ('e.g., Denver, Cheyenne') without conducting the validation work (distance, capacity, acceptance, ashfall risk) needed to turn naming into authorization. The plan assumes that pre-authorization of the trigger is independent of destination readiness, when in fact they are tightly coupled: a trigger without destinations is operationally meaningless.

5.5.A Issue - Responder staffing depth is inadequate and N95 inventory for responders is unsized; a single injury or checkpoint failure cascades into 2–4 hour evacuation delays.

The plan budgets 100–150 NPS rangers with a 1.5 relief ratio, yielding 67–100 concurrent positions across three corridors. During the T+2 to T+8 evacuation peak (when traffic is heaviest), all positions are consumed; no contingency exists if a ranger is injured, exposed to respiratory hazard or overwhelmed at a single checkpoint. Responder N95 respirators are not counted separately from the 100,000 civilian stock, so replacement protocols during the 6-hour shift limit are undefined. A vehicle breakdown or rockfall at Gallatin Canyon during peak flow—which would normally be managed by rotating a fresh team—instead halts traffic for 2–4 hours.

5.5.B Tags

5.5.C Mitigation

By Month -1 (2026-09-14): count responder N95 needs separately (recommend 150,000–200,000 total for responders alone based on typical use rates). Define a 6-hour shift limit with 2-hour rest and N95 replacement. By Month -0.5 (2026-09-29): pre-position a 30–50 person standby reserve from Colorado Parks and Wildlife, Wyoming Game and Fish and Idaho Department of Lands at a Billings or Cheyenne depot. Issue pre-authorization for the forward command to deploy this reserve within 4 hours if any primary checkpoint coverage falls below 50%. Conduct a shift-rotation exercise at Mammoth 30 days before the window.

5.5.D Consequence

Without relief depth, a single injury, respiratory exposure or equipment failure at a critical checkpoint halts traffic for 2–4 hours, stranding 500–2,000 vehicles in ash-exposed zones. Cumulative delay cascades: a 2-hour halt at Gallatin Canyon at T+3 hour pushes the T+6 gate closure back to T+8–10 hours, leaving 500–1,000 vehicles in the park during peak ashfall. Respiratory injury rates among responders rise 30–50%, and 5–10 preventable deaths occur due to delayed medical care for evacuees.

5.5.E Root Cause

The documents estimate responder headcount but do not model coverage loss from injury, exposure or fatigue during peak operations. They assume 100–150 rangers can staff three corridors simultaneously at 2,000 vehicles/hour without discussing what happens when a checkpoint is unmanned. Responder N95 sizing is conflated with the civilian 100,000-unit requirement, obscuring the true supply need.

5.6.A Issue - Ashfall forecast uncertainty of ±50 km and shelter sites chosen at T+6 hours with no real-time monitoring create risk of placing 10,000–15,000 evacuees in heavy ash; relocation protocols are absent.

The plan selects final shelter locations at T+6 hours based on a single NOAA/USGS plume forecast update. Ashfall forecasts for a VEI-6 eruption carry uncertainty of ±50 km or more; a wind-shift or forecast error could place Bozeman or Idaho Falls directly in the ashfall plume despite being selected as 'safe' sites. The plan stocks 100,000 N95 respirators for 35,800 people (2.8 masks per person for ~10 days); masks clog in heavy ash and require frequent replacement. No real-time ash-depth monitoring is mentioned, and relocation procedures for 10,000–15,000 evacuees mid-operation are not detailed. If shelter sites are rendered untenable by ashfall, evacuees cannot be relocated within the time window without consuming all available buses and adding 6–12 hours to transit.

5.6.B Tags

5.6.C Mitigation

By Month -0.5 (2026-09-29): deploy PM10/PM2.5 sensors at the forward command, Bozeman and Idaho Falls, with automated hourly feeds to USGS/NOAA. Set alert thresholds: >50 µg/m³ PM10 triggers forecast update; >100 µg/m³ triggers shelter-suitability review. Identify ranked backup shelter sites 50+ km upwind of each primary site, confirmed daily from the 00:00 UTC wind forecast. Pre-authorize 4-hour relocation procedures with bus and registration protocols. Stage a 100,000-unit supplemental N95 reserve at Billings. Conduct a shelter-relocation exercise 30 days before the window simulating a 50 km forecast error.

5.6.D Consequence

If actual ashfall diverges from forecast by 50+ km or doubles in intensity, primary shelters at Bozeman or Idaho Falls will become untenable within 12–24 hours of occupancy. Evacuees will experience respiratory distress, requiring medical intervention. Relocation of 10,000–15,000 people without pre-authorized backup sites and protocols will consume 8–12 hours and require diverting buses from other tasks, stranding 200–500 evacuees who cannot be moved. 10–30 preventable respiratory deaths will result from prolonged ash exposure during the gap.

5.6.E Root Cause

The documents assume ashfall forecasts are accurate enough for shelter siting but do not quantify forecast uncertainty or assign responsibility for monitoring actual conditions post-occupancy. They treat shelter selection as a one-time decision at T+6 hours rather than an ongoing adaptive process. The 100,000 N95 stock is pre-staged without calculating replacement cycles under different ashfall intensities.

6 Expert: Critical Infrastructure & Grid Resilience Engineer

Knowledge: electrical transmission systems, cascading blackout prevention, generator fuel logistics, emergency load shedding, telecommunications tower ash contamination, water-system contamination protocols

Why: The Ashfall Life-Support Supply decision and canonical facts specify 72-hour fuel reserves at hospitals and comms centers and a utility-operations coordination hotline, yet the plan does not quantify transmission-line flashover risk, backup-generator fuel consumption under continuous operation, or the cascading grid failure that could isolate shelters and hospitals from water and power within 4–8 hours if ash-induced outages occur faster than convoys arrive. This expert must harden the grid and utility plan to keep hospitals and comms functional through T+72h.

What: Model the transmission-line flashover probability under ashfall ash-conductivity conditions on the four critical substations serving Bozeman, Livingston and Idaho Falls; calculate 72-hour generator fuel consumption at continuous operation and recommend pre-positioned fuel tank sizes and resupply frequency; design an emergency load-shedding protocol for each utility that prioritizes hospitals and comms centers and specifies which neighborhoods or districts will be de-energized if cascading failure threatens a regional blackout; certify that each receiving hospital's backup-water supply (stored or on-site well) survives a simultaneous loss of grid power and incoming municipal water pressure for 8 hours.

Skills: power-systems modeling and cascading-failure analysis, generator fuel-consumption engineering, electrical transmission-line ashfall interaction, emergency load-shedding protocols, water-system backup design, utility coordination under emergency operations

Search: volcanic ashfall power grid transmission line flashover, cascading blackout prevention emergency, generator fuel consumption continuous operation, hospital water supply backup power loss

6.1 Primary Actions

6.2 Secondary Actions

6.3 Follow Up Consultation

"In the next consultation, address: (1) transmission-system load-shedding topology and critical-path sequence to preserve grid coherency during ashfall (relay-coordination and protective-device settings); (2) hospital fuel-consumption engineering and generator-load profiles under sustained ashfall conditions, including refrigeration, HVAC and surgical-suite demand curves; (3) water-system contamination response timelines, turbidity thresholds and backup groundwater activation protocols for Bozeman and Idaho Falls municipal systems; (4) realistic convoy routing and travel-time modeling under ashfall visibility reduction (50–100 meter sight distance) and evacuation-traffic saturation (25–40% I-15 congestion by Hour 8–12); (5) responder respiratory-protection protocols and separate N95 stock sizing from civilian allocation; (6) Scenario Beta secondary-stage destination capacity and financing ownership (federal vs. state/local/host); (7) escalation triggers for grid emergency load shedding and hospital backup-generator activation timelines relative to ashfall-onset modeling."

6.4.A Issue - Generator Fuel Logistics Absence Masks Cascading Power-Failure Risk

The plan names fuel as a 'tier-one priority' for hospitals and comms centers but provides no fuel-consumption model, pre-positioning schedule or tanker-dispatch protocol. A VEI-6 ashfall will trigger simultaneous transmission-line flashovers and equipment damage at multiple substations within 4–8 hours, faster than fuel convoys from Rock Springs, WY (200+ miles) can deliver. Hospital generators consume 20–30 gallons per hour at full load; a 4-hour outage drains 80–120 gallons per facility. The plan pre-stages '72-hour reserves' but does not specify tank capacity, refill frequency, ashfall-dust contamination protocols or backup-supplier naming. Without explicit fuel-consumption engineering and a tanker-positioned-at-dock commitment by T+0, hospitals will exhaust reserves by Hour 20–28, forcing critical-care evacuation or preventable deaths.

6.4.B Tags

6.4.C Mitigation

By Month -1 (2026-09-14): (1) Model hospital generator full-load consumption (20–30 gal/h), calculate ashfall-duration scenarios (12–48 h power loss), and size tank capacity as (peak consumption) × (expected outage hours) + 20% safety margin. (2) Contract with three suppliers (basin, billings, rock springs) with pre-authorized 4-hour dispatch and backup naming. (3) Arrange two pre-positioned tankers at each hospital by T+0, with refill triggers at 50% tank capacity and ashfall-dust filter protocols documented. (4) Pre-stage 500-gallon backup generator at Livingston hospital (estimate) as the forward-command lifeline. Test refueling under ash contamination 30 days before T+0.

6.4.D Consequence

Without fuel-consumption engineering and tanker pre-positioning, hospital generators fail at Hour 20–28, forcing: (1) critical-care evacuation under ashfall (5–20 preventable deaths estimated), (2) surgical-suite shutdown (10–20 cancelled procedures), (3) ventilator-dependent patient loss during manual-bagging transition (2–5 deaths), (4) forward-command comms loss if Livingston generator fails. Cascade: responder fatigue increases 40% without comms; reroute delays spike to 2–4 hours per incident; total evacuation delay: +4–8 hours, stranding 500–2,000 vehicles in ash.

6.4.E Root Cause

The plan treats fuel as a supply item rather than an engineering-constrained resource with load profiles, consumption curves and pre-positioned tanker commitments. It names '72-hour reserves' without verifying tank sizing, refill protocols or ashfall-contamination procedures. Fuel-logistics engineering was not integrated into the hospitalization surge and generator-load planning.

6.5.A Issue - Electrical Transmission-Line Ashfall Interaction Unquantified; Flashover Probability and Cascading Blackout Triggers Missing

The plan assumes 'ash-induced flashovers on transmission lines' will cause power loss but provides no model of ashfall silicate conductivity, voltage-threshold interactions, or timing. Electrical transmission lines (115–500 kV) in the region (Montana-Dakota Utilities, Pacific Power, Idaho Power) serve 2–4 million people. A VEI-6 ashfall (100–500 µm/kg) deposits conductive silicate particles on ceramic insulators, reducing surface resistance to 1–10 MΩ within hours. Flashover occurs when voltage exceeds approximately 100 kV per insulator stack; a simultaneous 3–5 phase-to-ground faults cascade to load-shedding protocols and blackout propagation. The plan names 'protective relays' and 'emergency load shedding' but lacks a transmission-specific failure model, substation-specific topologies or the critical-path sequence that preserves grid coherency during the 4–8 hour ashfall peak.

6.5.B Tags

6.5.C Mitigation

By Month -1 (2026-09-14): (1) Engage a transmission-systems engineer from WECC (Western Electricity Coordinating Council) or a regional utility to model ashfall conductivity (100–500 µm/kg) vs. insulator stack voltage (115–500 kV lines), calculate flashover probability and timing. (2) Map the critical transmission corridors (substations within 100 km of the evacuation routes) and identify 3–5 load-shedding 'islands' that preserve comms, hospitals and shelters while sacrificing non-essential load. (3) Pre-authorize emergency-voltage reduction (brownout) on non-critical substations at Hour 4–6 of ashfall to reduce flashover risk before peak ash accumulation. (4) Test load-shedding sequences at Bozeman or Livingston substation 30 days before T+0 under simulated ash conditions (recommend using ash-simulation powder on test insulators). Document relay-coordination changes required to prevent nuisance trips.

6.5.D Consequence

Without transmission ashfall modeling and load-shedding coordination: (1) simultaneous 3–5 substation flashovers at Hour 4–8 trigger cascading blackout across Montana, Wyoming and Idaho (2–4 million people affected), (2) loss of comms infrastructure (cell towers lose power; backhaul lines fail) within 4–6 hours, (3) hospital generator failure propagation (loss of cooling, HVAC, surgical-suite lighting) cascades across the region within 8–12 hours, (4) responder coordination collapses; estimated delay: +6–12 hours to evacuation and 10–30 preventable deaths from hospital failures and responder entrapment in ash-covered areas without navigation or comms.

6.5.E Root Cause

The plan addresses ashfall as a water-and-respiratory hazard but not as an electrical hazard to the transmission network. Transmission-line flashover thresholds, insulator silicate-conductivity interactions and cascading-failure topology were not analyzed. The utility-liaison requirement (Decision 6) names 'protective relays' and 'load shedding' without transmission-system expertise or relay-coordination analysis.

6.6.A Issue - Water-System Contamination Protocols for Ashfall Missing; Bottled-Water Convoy Realistic Arrival Estimate Unverified

The plan targets water arrival at shelters by T+24 h and names a '1.43 million liter' requirement but provides no water-system contamination assessment or convoy-routing validation under ashfall conditions. Municipal water systems serving Bozeman and Idaho Falls draw from surface reservoirs or groundwater that will be ash-contaminated within 4–6 hours of eruption; the plan names 'ashfall will contaminate open reservoirs' but does not specify: (1) treatment timelines for ash removal (settling, filtration, chlorination), (2) which water sources (municipal, well, potable-water tankers) are accessible at each shelter, (3) realistic convoy travel time from Salt Lake City under ashfall-reduced visibility (I-15 ashfall is worst-case 50+ km north) and evacuee-traffic congestion (estimate: 18–30 h, not 12 h dispatch). Without a validated water-supply chain from source to shelter and explicit contamination-response protocols, shelters risk 1–3 days of water rationing or non-potable water use, creating gastroenteritis outbreak risk in close-quarters shelter conditions.

6.6.B Tags

6.6.C Mitigation

By Month -1 (2026-09-14): (1) Engage a water-utility engineer to assess Bozeman and Idaho Falls municipal-supply sources (reservoirs, treatment plants, distribution) and specify ash-contamination response (settle time, filter requirements, turbidity thresholds for continued use). (2) Calculate convoy travel time under realistic ashfall conditions: assume I-15 ashfall visibility 50–100 meters, safe speed 10 mph (not 60 mph), evacuee traffic at 25–40% congestion by Hour 8–12, resulting in 18–30 hour travel time (not 12 h dispatch). (3) Pre-stage 200,000–300,000 liters of bottled water at Bozeman and Idaho Falls forward depots by T+0 (not dispatch from Salt Lake City), with 72-hour refill contracts pre-positioned for convoys arriving at Hour 18–24. (4) Arrange for groundwater tanker-fill stations at Bozeman and Livingston (if municipal sources are offline) as backup, with pre-tested pump and hose interfaces. (5) Test convoy timing from Salt Lake City to Bozeman under simulated ashfall (use fog machines or ash-simulation powder to reduce visibility, measure actual speeds and traffic interaction) 30 days before T+0.

6.6.D Consequence

Without validated water-supply chains and contamination protocols: (1) municipal water sources become non-potable at Hour 4–8, (2) bottled-water convoy realistically arrives Hour 20–30 (not Hour 12–24), leaving shelters with 18–30 hour water-rationing window, (3) improvised use of contaminated municipal water (if treatment fails or ash exceeds filter capacity) triggers gastroenteritis in 500–1,500 shelter residents (5–15% attack rate in close quarters estimated), (4) medical response overloads field-clinic and hospital diarrhea/dehydration wards, cascading to loss of surge capacity for respiratory cases, (5) estimated consequence: 10–30 preventable deaths from dehydration, electrolyte imbalance and secondary infection in weakened populations.

6.6.E Root Cause

The plan treats water as a generic '1.43 million liter' number without upstream source assessment or contamination-response protocols. Water-system backup design and contamination thresholds (turbidity, ash-particle concentration) were not analyzed. Convoy routing was assumed to deliver within 12 hours from Salt Lake City, but ashfall conditions (visibility <100 meters, 10 mph safe speeds on ash-covered I-15, evacuee traffic saturation) were not reflected in travel-time modeling.

7 Expert: Aviation Safety & Airspace Management Liaison

Knowledge: FAA airspace restrictions, rotary-wing medevac protocols, ash-ingestion engine risk, aircraft emergency procedures, volcanic-ash-dispersion forecast integration, military-civilian airlift coordination

Why: The Ash-Cloud Airspace Closure decision specifies indefinite grounding of ZLC/ZSE with narrow government rotary-wing exceptions, yet the plan lacks the FAA authority procedure, aircraft ash-encounter risk assessment, and the operational parameters for the exception window (e.g., maximum ashfall concentration, flight altitude, aircraft type). This expert must operationalize the airspace closure and define when medevac, supply and survey flights can operate safely without exposing crews and aircraft to catastrophic engine damage.

What: Develop a written FAA Section 29 Notice to Airmen (NOTAM) template authorizing the blanket ZLC/ZSE grounding at T+0 and specifying rollback criteria tied to USGS ashfall concentration forecasts; design a narrow rotary-wing medevac/survey flight corridor (time windows, altitude, aircraft type, ashfall concentration triggers) that the Unified Command can request from the FAA without requiring a full rule change; establish a coordination protocol between the forward UC element, USGS/NOAA ash forecasters and helicopter operators (Wyoming Guard, USCG, civilian medevac services) ensuring that flight-request decisions are made within 30 minutes of a medical or reconnaissance need, with ashfall data updated hourly.

Skills: FAA airspace regulation and NOTAM procedures, aircraft engine ash-ingestion vulnerability, rotary-wing medevac mission planning, volcanic-ash-concentration forecasting integration, military-civilian aircraft coordination, emergency flight operations under hazardous-weather restrictions

Search: FAA airspace closure volcanic ash NOTAM, helicopter medevac ash concentration limits, aircraft engine ash ingestion risk assessment, military-civilian emergency airlift coordination

7.1 Primary Actions

7.2 Secondary Actions

7.3 Follow Up Consultation

"At the next consultation, we will address: (1) finalization of ash-concentration thresholds from USGS and FAA technical working groups; (2) confirmation of military assets pre-positioning and Joint Task Force command authority; (3) integration of real-time air-quality monitoring into the Unified Command's common operating picture (COP); (4) FAA's approval process for rotary-wing flight corridors and medevac exceptions under Section 91.3 emergency authority; (5) inter-hospital patient-transfer protocols and backup ventilator supply for ground evacuation; and (6) post-event review of forecast accuracy and shelter-siting rule performance. We will also discuss whether civilian medical helicopters (air ambulances from Helena, Billings) should be pre-contracted as backup to military MEDEVAC, and how to manage volunteer or contracted rotary-wing assets that may arrive from outside the region without pre-authorization."

7.4.A Issue - FAA Airspace Grounding Lacks Medevac Exception Architecture and Ash-Concentration Decision Thresholds

The plan mandates 'indefinite grounding' of ZLC and ZSE but provides no operational criteria for rotary-wing medevac or survey flights. The statement 'narrow government rotary-wing medevac/survey exceptions requested by UC and authorized by FAA' is procedurally hollow: it does not specify ash-concentration limits, aircraft type restrictions, flight corridors, real-time monitoring triggers, or the operational timeline for FAA approval. A 'rotary-wing exception' without ash-concentration thresholds (e.g., <200 µg/m³ PM10 at 5,000 ft) risks engine ingestion and crew loss. The plan also conflates medevac (moving critical patients from hospitals) with evacuation flights (moving evacuees), which have different risk profiles and demand different approval paths.

7.4.B Tags

7.4.C Mitigation

By Month -1 (2026-09-14), execute a written Rotary-Wing Medevac Exception Protocol specifying: (1) ash-concentration thresholds from USGS forecasts and real-time VAAC updates (recommend <200 µg/m³ PM10 at rotor altitude); (2) approved flight corridors below the ash cloud (e.g., east or west bypass routes); (3) aircraft-type restrictions (single-engine helicopters prohibited; twin-engine, ash-tolerant airframes only); (4) real-time monitoring via air-quality sensors at staging airfields and hospitals; (5) FAA pre-authorization for UC to issue medevac flight approvals directly without 24-hour Section 91.3 waiver turnaround. Coordinate with FAA Alaskan Region (volcanic-ash experience) and Army Aeromedical Center. Schedule a 4-hour technical meeting with FAA Hazmat, USGS Volcano Disaster Assistance Program, and airframe OEMs (Bell, Sikorsky) to align ash-concentration limits with engine-inlet design specifications. Document in a Memorandum of Agreement (MOA) signed by FAA and UC by T+0.

7.4.D Consequence

Without ash-concentration thresholds and pre-authorized FAA approval, medevac flights will be grounded or delayed 2-4 hours per request during the 72-hour window. This will strand 5-10 critical-care patients at Zone One hospitals during ashfall, forcing manual ventilation by exhausted staff and increasing respiratory-death risk by 30-50% for dialysis-dependent or ventilator-bound patients. In Scenario Beta, the grounding persists longer, adding 20-30 preventable deaths across the multi-state evacuation zone. A single helicopter engine encounter with high-concentration ash could disable the aircraft and kill 3-4 crew members, triggering FAA investigation and a de facto total grounding for weeks.

7.4.E Root Cause

The plan treats aviation as a secondary concern and defers ash-concentration thresholds to 'USGS/NOAA liaison' without embedding those thresholds into the UC decision framework or the FAA Section 91.3 emergency authority process. The FAA requires explicit ash-concentration limits and flight-corridor definitions before authorizing any flight into a volcanic-ash environment. Without pre-negotiated thresholds (Module 1-2 weeks of technical coordination with FAA Hazmat Division, USGS, and aircraft OEMs), the UC will face 2-4 hour delays requesting approval for each medevac flight during the 72-hour window, or will fly without approval and risk catastrophic engine damage.

7.5.A Issue - Ash-Concentration Forecast Integration Absent; Shelter Siting Rule Depends on Unvalidated Dispersal Models

The plan states 'Select final shelter locations at T+6 hours from the forecast wind and plume model' and later 'ashfall forecast uncertainty of ±50 km' as a baseline risk, but it provides no mechanism for integrating real-time ash-concentration forecasts from USGS-operated volcano-ash transport (VAAT) or NOAA's Volcanic Ash Forecast Transport (VAFT) models into shelter-siting decisions. The canonical facts mention PM10 thresholds (50, 100 µg/m³) but do not specify which model provides those predictions, how often forecasts are updated, or which concentration level triggers shelter relocation. The plan also lacks an air-quality sensor network tied to the shelter-siting rule, so the '4-hour relocation' protocol cannot be executed: you cannot know whether to relocate until ash actually arrives, by which time 30 minutes to 2 hours have already passed without action.

7.5.B Tags

7.5.C Mitigation

By Month -1 (2026-09-14): (1) establish a written agreement with USGS Volcano Disaster Assistance Program and NOAA's National Weather Service Forecast Office (Billings or Riverton, WY) specifying that the Volcanic Ash Forecast Transport model will issue updates every 3 hours from T-24 h through T+72 h, with explicit concentration outputs at 1,000 ft, 5,000 ft and 10,000 ft above each shelter location (Bozeman, Idaho Falls, third site); (2) define a Shelter Siting Decision Rule: at T+6 h, choose primary shelter from among three ranked candidates based on which site has <50 µg/m³ PM10 at T+12 h (12-hour forecast lead time). If the latest VAFT update (every 3 h) predicts >100 µg/m³ at the primary site within 6 hours, trigger relocation to backup within 2 hours (revised from 4 hours); (3) deploy PM10 sensors and LIDAR backscatter systems at all three primary shelter sites and the forward command by Month -0.5 (2026-09-29 14:00), with automated alerts if measured PM10 exceeds forecast by >50% (indicating model error or plume intensification); (4) pre-position backup shelters 50-80 km upwind of each primary (not merely 50+ km), confirmed daily from the 00:00 UTC GFS wind forecast, with 2-hour occupancy-transfer capacity. Consult USGS Ash-Forecast Validation Team (Denver) on model skill for Yellowstone plume heights.

7.5.D Consequence

Without forecast integration and real-time air-quality sensors, the shelter-siting decision at T+6 h is blind: it relies on a forecast whose uncertainty exceeds the distance between Bozeman and the primary ashfall zone (roughly 80-120 km). If the actual ashfall arrives 30-50 km south of forecast (within ±50 km error bounds), Bozeman's shelter population of 15,000-20,000 will be exposed to 200-500 µg/m³ PM10, overwhelming respiratory capacity and forcing emergency relocation after occupants have already arrived. A 2-4 hour relocation of 15,000 people under ashfall requires buses, drivers and logistics that the evacuation phase will have already consumed. Failure to relocate results in 200-500 shelter residents with acute respiratory distress, requiring hospital transport during peak ashfall when roads are ash-clogged and visibility is <100 meters (estimate).

7.5.E Root Cause

The plan assumes USGS/NOAA forecasts will provide reliable ash-concentration predictions in real-time during an unprecedented event. In reality, the VAFT model (the operational tool) has a ±50 km spatial uncertainty at 24 hours and larger uncertainty in concentration magnitude. A VEI-6 eruption at Yellowstone has never been directly observed; the model ensemble's range is wide (e.g., 10 µg/m³ to 1,000 µg/m³ at Bozeman depending on plume height and wind). The plan conflates forecast availability (VAFT updates every 3 hours) with forecast reliability (±50 km error), and it does not name which forecast product drives the shelter-siting decision or specify decision rules for forecast mismatches (e.g., if the latest forecast shows ashfall shifting 50 km north of the previous forecast).

7.6.A Issue - Military-Civilian Airlift Coordination Absent; Rotary-Wing Medevac and Supply Chains Lack Pre-Event Authority Agreements

The plan names 'Army Aeromedical Center' and references 'military airlift windows' and 'helicopter resupply' but provides no operational agreements with Wyoming National Guard (Cheyenne), U.S. Air Force (Malmstrom AFB, Great Falls, MT) or Army Medical Evacuation (MEDEVAC) units. The canonical facts mention 'a standing airlift protocol with the Wyoming National Guard (Cheyenne-based aviation) and U.S. Air Force (Malmstrom AFB, Montana) for priority dispatch of fuel or medical supplies to isolated hospitals within 4 hours of request from T+0 to T+72 hours,' but this protocol is not defined in any document and there is no Military Liaison Officer (MLO) listed in the Unified Command structure. Without pre-signed Interagency Agreements (MOAs) with the National Guard Bureau and Air Force Pacific Air Forces, a request for military rotary-wing or cargo support will generate 24-48 hour approval delays through state adjutants general (MT, WY, ID) and NORTHCOM, not the promised 4-hour dispatch.

7.6.B Tags

7.6.C Mitigation

By Month -1 (2026-09-14): (1) Execute a signed Memorandum of Agreement (MOA) between FEMA Region VIII, the Wyoming, Montana and Idaho Army National Guard, the U.S. Air Force (21st Space Wing and 341st Missile Wing, Malmstrom AFB), and the Department of Defense specifying: (a) pre-positioned Army MEDEVAC helicopters (2-4 UH-60s with hoist and litter capability) stationed at Gallatin County Airport (Bozeman) or Jackson Hole Airport by T-48 h (Month -0.5, 2026-09-29 12:00 UTC), staffed and fueled for continuous 72-hour operations; (b) pre-cleared flight corridors into ZLC and ZSE airspace that bypass the ash cloud (negotiated with FAA beforehand, not ad-hoc); (c) four-hour dispatch of additional rotary-wing assets from Fort Carson (Colorado National Guard) or Malmstrom AFB if the pre-positioned asset is engaged >2 hours without recovery; (d) a Joint Task Force commander (active-duty Army or Guard colonel) integrated into the Unified Command structure from T-24 h through T+72 h with direct authority over military asset allocation, not request-response hierarchy through state adjutants general. (2) Assign a permanent Military Liaison Officer (O-4 rank) to the forward UC element (Livingston or Bozeman) by Month -0.5 (2026-09-29 06:00), with secure communication to NORTHCOM and 9th Medical Battalion. (3) Conduct a Joint Task Force activation and medevac-dispatch exercise at a Zone One hospital (e.g., Livingston HealthCare) 30 days before the window (Month -0.5, 2026-09-29 08:00 to 16:00), simulating a critical-care patient transfer under ashfall conditions, testing aircraft launch-to-landing times from Bozeman to a receiving hospital in Idaho Falls or Salt Lake City, and confirming that 'four-hour dispatch' includes actual patient loading and transport (not just aircraft wheels-up).

7.6.D Consequence

Without pre-positioned military assets and signed MOAs, medevac of critical-care patients will face 12-24 hour delays or will not occur. During the T+2 to T+8 evacuation peak, hospitals in Gardiner, West Yellowstone and Cody will have 5-10 dialysis-dependent or ventilator-bound patients who cannot be evacuated by ground ambulance if ashfall reduces visibility to <100 meters. Without rotary-wing medevac, these patients will be sheltered in hospitals that are ash-exposed and under-supplied with generator fuel for mechanical ventilation. A 6-12 hour loss of ventilator support due to power or fuel shortage will cause 2-5 preventable deaths. In Scenario Beta, the multi-state operation will have 50-100 similar patients trapped without air-evacuation capability, adding 20-50 preventable deaths.

7.6.E Root Cause

The plan assumes that military airlift will be available on-demand during a civilian disaster, but the National Guard requires gubernatorial request through the Adjutant General and federal activation requires Presidential authorization (Stafford Act) or Secretary of Defense/NORTHCOM approval. A 'standing airlift protocol' without a signed MOA is not a commitment; it is a hope. The Unified Command structure does not list a dedicated Military Liaison Officer or Joint Task Force commander, so there is no single point of authority to request military resources during the evacuation. Army MEDEVAC (9th Medical Battalion out of Fort Carson, CO or 111th Aviation Battalion, Montana Army National Guard) requires 12-24 hour notice for asset deployment and aircraft pre-positioning, not 0-hour notice for 'priority dispatch within 4 hours.'

8 Expert: Visitor Communication & Behavioral Compliance Strategist

Knowledge: emergency public messaging design, visitor notification systems, international-visitor language access, shadow-evacuation dynamics, message credibility and trust repair, multilingual alert distribution

Why: The Shadow Evacuation Suppression and International Visitor decisions and canonical facts require multilingual messaging in five languages and a published USGS trigger matrix to protect credibility, yet the plan lacks the specific message content, distribution testing, and the behavioral model for how unordered outer-zone residents will respond to shelter-in-place orders versus time-banded releases. This expert must design the complete messaging strategy, validate comprehension with foreign-language speakers, and certify that the trigger matrix and escalation messaging can be deployed without eroding public trust if Scenario Beta is later ordered.

What: Produce final IPAWS/WEA/HAR message content in English and the five specified languages (Spanish, Japanese, German, Mandarin, French) with comprehension-level validation testing by native speakers; design a Scenario Beta message sequence that transitions from shelter-in-place (if Beta is not triggered) to time-banded evacuation (if Beta is triggered at T+12h or later) without appearing to reverse a prior order, using consistent terminology and a published risk explanation; establish a visitor-needs data collection protocol at lodges and permit stations (language, vehicle, mobility-need, contact-info capture) from T-48h to T+0, enabling targeted notification of high-need visitors; conduct a message-credibility and behavior-response exercise with sample visitor and Zone One resident populations 30 days before the eruption window, documenting compliance rates under each message variant and identifying any cultural or language-specific communication barriers.

Skills: emergency-message design and testing, multilingual content development and validation, behavioral-response modeling in evacuation scenarios, public-trust restoration and credibility maintenance, visitor-needs population estimation, alert-distribution-channel effectiveness analysis

Search: emergency evacuation messaging design visitor compliance, multilingual IPAWS alert content testing, shadow evacuation suppression communication strategy, volcanic disaster public messaging credibility

8.1 Primary Actions

8.2 Secondary Actions

8.3 Follow Up Consultation

Next meeting should address: (1) Final Scenario Beta hub nominations and distance verification to confirm Denver and Cheyenne lie outside 500 km and capacity commitments; (2) responder mutual-aid MOUs with named personnel, pre-positioning depot and deployment authorization by Month -0.5; (3) sensor deployment authority and real-time data-feed protocols linking forward command to NOAA/USGS for continuous shelter-suitability monitoring; (4) governor pre-authorization pathway (verbal by T+6 h, signed MOUs by Month 1 = 2026-11-14); (5) Boundary Coordination Officer job description and interagency radio frequency allocation; (6) full-scale exercise schedule for Months 1–3 (2026-11-14 to 2027-01-14) including Beta multi-state routing, shift-rotation relief handoff, and water-convoy deployment under congestion. Financial responsibility split (federal vs. state/local) for shelters and secondary hubs must be resolved before Month 1 (2026-11-14).

8.4.A Issue - Scenario Beta second-stage hub plan is a hollow pre-authorization with no executable destinations

The plan pre-authorizes a UC order to evacuate 500 km with a 30-minute decision window, but names no specific hubs, capacity commitments, or supply staging. The canonical facts state 'Denver and Cheyenne qualify (distance not verified)' and 'millions of people (not quantified).' A 500 km radius from Yellowstone reaches ~8–12 million people. Issuing an evacuation order without published shelter addresses, registration sites, or supply depots will trigger chaotic uncontrolled flight that saturates I-15, I-80 and I-90, delays the primary 35,800-person Zone Zero evacuation by 4–8 hours, and strands vehicles in ash plumes. The order is pre-authorized but not pre-planned, making it operationally reckless.

8.4.B Tags

8.4.C Mitigation

By Month 1 (2026-11-14), name five to ten ranked Beta hubs outside 500 km: Denver, Cheyenne, and secondary sites (Albuquerque, Las Vegas candidates); confirm capacity MOUs from each host county for 100,000–500,000 additional beds, kitchens and medical triage. Stage a 20,000–30,000-person supply surge (water, N95s, food, fuel) at each hub by Month 2 (2026-12-14). Issue tiered public messaging specifying shelter-in-place zones (250–500 km, self-supplied), time-banded evacuation (100–250 km, assigned by county), and organized departure (Zone One). Execute a full multi-state exercise moving 5,000 vehicles from the Zone One boundary to beta hubs by Month 3 (2027-01-14).

8.4.D Consequence

Without executable Beta destinations, the pre-authorization becomes a hollow mandate that orders millions to flee with no published safe shelter. Uncontrolled flight cascades into I-15/I-80/I-90 gridlock, blocking the Zone Zero corridor. Delays to primary evacuees compound 4–8 hours, stranding vehicles in ash. Hospital and shelter intake systems overflow within 12 hours. 10,000–20,000 people cannot reach published shelters and become stranded. Preventable deaths from respiratory distress increase 20–50% over the baseline plan.

8.4.E Root Cause

Pre-authorization of Scenario Beta was treated as a decision isolated from downstream capacity and messaging planning. No host-hub engagement occurred before Month 0 (2026-10-14); no interstate MOUs bind hubs to accept millions of people. The plan conflates 'who decides to order evacuation' (UC authority) with 'where evacuees actually go' (second-stage capacity), leaving the latter undefined. The canonical facts acknowledge distance to Denver and Cheyenne are 'not verified,' suggesting the hubs were named without validation.

8.5.A Issue - Responder staffing depth is insufficient and responder N95 stocks are unsized and separate from civilian supply

The plan estimates 100–150 NPS rangers at a 1.5 relief ratio, yielding ~67–100 concurrent positions. Canonical facts propose 6-hour shifts, 2-hour rest, and 18-hour withdrawal limits, plus a 30–50 'standby reserve' from out-of-region. However: (1) all 67–100 ranger positions are consumed during T+2 to T+8 peak evacuation with zero cushion for injury, equipment failure, or scope creep; (2) responder N95s are 'counted separately, not drawn from the 100,000 civilian stock' (proposed threshold), but no responder headcount exists to size this separate stock; (3) a single traffic incident at Gallatin Canyon or a ranger injury during peak hours cannot be absorbed without halting one checkpoint, stranding 500–2,000 vehicles and cascading 2–4 hours delay. The 30–50 reserve exists only if it can be deployed within 4 hours; no mutual-aid agreement or pre-positioning is documented.

8.5.B Tags

8.5.C Mitigation

By Month -0.5 (2026-09-29, before T+0), secure written pre-event mutual-aid commitments from Colorado Parks and Wildlife, Wyoming Game and Fish, Idaho Department of Lands and Fort Carson (Colorado National Guard) for 50–100 out-of-region traffic-control and patrol personnel, pre-positioned at Billings or Cheyenne with 4-hour deployment authorization. Size responder N95s from confirmed responder headcount (rangers, highway patrol, Guard, utility crews estimated 300–500 total); estimate 2–3 respirators per responder over 72 hours = 600–1,500 total responder N95s. Pre-stage this stock separately at the forward command depot with dedicated replacement logistics. By Month 0 (2026-10-14) (T+6 hours), assess actual ranger availability and request additional Guard personnel if coverage at any checkpoint drops below 50%. Test shift-rotation and relief handoff at Gardiner checkpoint (Month -0.5, 6-hour exercise) to confirm 4-hour reserve-deployment time.

8.5.D Consequence

If responder depth is not increased and confirmed, peak-hour traffic control will fail. A single breakdown at Gallatin Canyon or ranger injury at T+4 hours cannot be absorbed. One checkpoint halts for 2–4 hours, queuing 500–2,000 vehicles in ash, adding 2–4 hours to their exit time and increasing respiratory-distress cases by 30%. Stranded vehicles may attempt uncontrolled departures on secondary roads, risking 5–10 additional collisions. Responder N95 supply exhaustion at T+36–48 hours forces withdrawal of traffic-control staff, leaving checkpoints unmanned and allowing looting in evacuated towns. Preventable respiratory deaths among responders increase 10–15%.

8.5.E Root Cause

Responder staffing was dimensioned against the 35,800-person Zone Zero evacuation in isolation, without modeling peak concurrent demand across traffic control, perimeter patrols, backcountry sweeps, medical transport, and comms maintenance. The 1.5 relief ratio is typical for planned operations, not crisis response with ash exposure and injury risk. Responder N95 sizing was deferred ('counted separately') without defining the responder population. No pre-event mutual-aid agreements or forward pre-positioning exist; the standby reserve is aspirational and depends on T+0 decisions and verbal authorization.

8.6.A Issue - Shelter siting at T+6 hours based on a single plume forecast with ±50 km uncertainty and inadequate real-time monitoring enables shelter placement in heavy ashfall

The plan chooses final shelter sites at T+6 hours using the latest NOAA/USGS plume forecast and proposes a 4-hour relocation rule if conditions worsen. However: (1) ashfall forecast uncertainty for a VEI-6 event is ±50 km or greater (unvalidated, never directly observed in North America); (2) PM10 sensors are 'at forward element and every shelter' (proposed threshold) but no sensor deployment timeline or communication protocol is documented; (3) a single forecast update at T+6 hours provides one snapshot; no continuous 4-hourly updates are guaranteed; (4) if actual ashfall exceeds forecast by 50 km or doubles in intensity, 10,000–15,000 evacuees sheltered at Bozeman or Idaho Falls sit in moderate-to-heavy ash (PM10 > 500 µg/m³ estimate), consuming N95s 3–5x faster than model estimates. A 4-hour relocation of 10,000 people requires ~20–30 buses and 4–6 hours actual transport time, not 4 hours decision-to-arrival. Shelters could be placed in the plume.

8.6.B Tags

8.6.C Mitigation

By Month 0 (2026-10-14) (T+0), deploy continuous PM10/PM2.5 sensors at Bozeman, Idaho Falls and the forward command with automated hourly data feeds to the forward command and USGS/NOAA. Set thresholds: >50 µg/m³ triggers immediate forecast update; >100 µg/m³ triggers shelter-suitability review. By Month -0.5 (2026-09-29), develop ranked three-shelter backup system for each primary site, identifying second and third locations 50+ km upwind of each primary, confirmed daily from 00:00 UTC wind forecast. Pre-authorize rapid occupancy-transfer protocols (4-hour decision-to-notification maximum). By Month 0 (2026-10-14) (T+6 hours), stage a supplemental 100,000 N95s at Billings or Salt Lake City hub with 8-hour ground-convoy or helicopter-transport agreement. Conduct an air-quality and shelter-siting exercise 30 days before eruption window (Month -0.5, 2026-09-29) simulating ashfall 50 km south of forecast, testing relocation decision and bus dispatch for 5,000–10,000 evacuees within 4 hours.

8.6.D Consequence

If shelter sites are placed 50 km downwind of forecast and ashfall exceeds model predictions, 10,000–15,000 evacuees shelter in moderate-to-heavy ash (PM10 > 500 µg/m³ estimate) with inadequate N95 supplies. Daily N95 consumption 3–5x exceeds model; stock depletes within 12–24 hours instead of 10 days. Respiratory distress cases increase 50–100% at receiving hospitals. A 4-hour relocation decision-to-movement window is unachievable; actual bus dispatch and transport require 6–12 hours, stranding evacuees in ash. 200–500 people cannot reach a second shelter before N95 supply fails. Pneumonia and acute respiratory failure cases increase 20–30%; preventable deaths increase 5–10 over baseline.

8.6.E Root Cause

Shelter siting was treated as a T+6-hour tactical decision, not a strategic design. The plan inherited plume-forecast uncertainty from NOAA/USGS without quantifying forecast error (±50 km is a reasonable estimate but unvalidated). PM10 sensors and continuous monitoring were specified as 'proposed thresholds' but no deployment authority, cost or timeline was documented. Real-time relocation was assumed to fit within 4 hours; actual bus dispatch and transit (6–12 hours estimated) makes this infeasible. The 100,000 N95 civilian stock was not stress-tested against 3–5x consumption in heavy ashfall. Backups and upwind sites were mentioned but not pre-surveyed or pre-authorized for rapid occupancy.

Level 1 Level 2 Level 3 Level 4 Task ID
Yellowstone Emergency Evacuation eaa51401-c883-43b8-a9f0-1fa468166d9b
Pre-Event Hardening and Authority Preparation eb96e1b9-0c83-4d47-b259-fba4f8e364a1
Obtain pre-event authorization letters from Montana, Wyoming and Idaho governors confirming Unified Command and Scenario Beta authority 2a1239b1-362f-431b-95d1-c48f4c0f7c59
Draft authorization package with legal language 802d6045-b779-4aba-a02a-66602697506c
Schedule governor briefing and signing meetings bb9f03ee-a300-4c69-b12e-708f9e9145b8
Obtain written pre-authorization confirmation letters 0ba21f81-dc58-4e8b-81af-12d3901ea6b6
Establish weekly executive steering updates cbd0d8fa-c597-4a0f-8cfe-acde33c23e4f
Designate primary and alternate signatories 922b5d02-4d85-4b5e-8498-95013ad5b20a
Execute signed MOUs with NPS, FEMA Regions VIII and X, state DOTs and highway patrol specifying boundary-transfer checkpoints and pre-authorized reroute protocols abada67d-9eb0-439e-ac84-336b59a5a16d
Draft unified MOU framework and boundary protocols 365525be-5ac3-4b3d-adbd-76a751c02587
Negotiate and resolve operational disagreements on boundary checkpoints and reroute authority 1905cbf3-7596-452b-8d1a-a1d6170e9e75
Obtain legal review and pre-clearance from state attorneys general and FEMA counsel 11a4d646-13c7-49e3-aab4-3925173e7255
Coordinate tiered signature process across six parties with direct executive outreach f26d168f-d30a-4037-8ffc-4d38f2085233
Finalize and distribute fully signed MOUs; brief all stakeholders on reroute and checkpoint protocols 88e18d44-485c-44be-a3a4-dd409b8d4ec3
Deploy PM10 sensors at Bozeman, Idaho Falls and forward command with satellite data transmission and validate ashfall forecasting integration with NOAA VAFT updates a6b1243f-890f-4b58-9068-580e83ecb247
Procure and stage PM10 sensors e71fcf3d-1a3b-4a64-8015-73a3705f042c
Deploy sensors at Bozeman, Idaho Falls, forward command 9a306d49-613c-426e-9753-d976fbc2d9dd
Integrate PM10 data feeds with NOAA VAFT forecasting system 90e52ac5-9fc3-4aff-b293-9a3a24075563
Validate NOAA 3-hourly VAFT forecast updates and concentration outputs a3389dd5-539c-4f97-9d7c-83268b6fb394
Conduct sensor accuracy and reliability testing under ashfall simulation dd0f14be-ac43-454b-b590-19fa8470eb89
Conduct geotechnical survey of Gallatin Canyon and South Entrance slide; validate single-lane clearance feasibility and abort triggers c9188125-67e2-46f9-9fe3-8901c63414d9
Survey Gallatin Canyon slopes and debris zones c8bb40b0-b794-48b1-adc4-1de618ea5ce3
Model single-lane clearance time feasibility e7f1f834-647d-496c-a9ca-f30afbe58b40
Identify bypass routes and temporary track designs 50fd4e30-9e6b-45e9-bb12-33e538110882
Validate abort triggers and secondary-slide risk 7cf2f676-ca6b-47c7-a1f2-6c97bfff0b1e
Conduct site survey and equipment-positioning exercise e039a488-c946-4b0a-9a44-2df8924c5602
Contract water-supply convoys from Salt Lake City, Pocatello and Butte with 12-hour dispatch clauses and pre-stage forward depots (Bozeman, Idaho Falls) b9ad860c-9484-495a-9e7c-70b3e8031e47
Issue RFP for water-supply convoys 81113121-8285-46b7-8a26-4465251f46c0
Negotiate 12-hour dispatch and resupply clauses 919143db-90bf-47cf-be57-5a1a275e6109
Identify and secure forward-depot sites a0fc3be4-af3e-4c95-8c3c-3031d99d2860
Contract water-storage and delivery logistics 8c89d342-a5f7-4552-b0e9-c276ee237f35
Conduct vendor readiness drills and route validation 8d1eebd9-7cf7-424c-8829-0f4e87c68b0e
Identify and validate ranked shelter hubs outside the 500 km Scenario Beta ring; secure host-community MOUs and supply pre-positioning commitments bb0cab85-ecec-43a4-a4d6-15800b4b59b9
Identify and distance-verify shelter hubs outside 500 km ring 61f2539a-bc31-4727-9b3b-da31eb405062
Assess hub capacity and secure host-community MOUs 67be6e6b-b188-46d5-9835-0982d842b5b1
Model supply pre-positioning and resupply logistics bb3daaee-64e2-4bd0-9a40-ba6023d43c1a
Develop tiered public messaging and ring-execution plan 129e7f38-69a6-40ab-a8ab-6024cb4f15c0
Unified Command Activation and Contraflow Setup (T+0 to T+1 hour) 70ca8781-806f-4b04-a990-8801442fe9c5
Activate Unified Command at FEMA Region VIII RRCC Denver with forward element at Livingston; confirm FEMA Region 10 liaison and Boundary Coordination Officer communications 038dddaa-7432-4f8d-9c00-5d29a8ed61f5
Establish Unified Command pre-coordination rosters and activation authority 1749e85d-4050-40d5-802d-8e168402054c
Deploy signal teams with satellite phones to forward element and control points bb6c9457-7621-4d28-af98-3cc20886592d
Establish dedicated satellite-phone lines and backup radio repeater network 45add2ac-64bc-4365-a81e-3829f3b47752
Confirm FEMA Region 10 liaison physical presence and succession plan d025c088-b97d-48c6-8ac2-aab3b0fc5984
Conduct activation simulation and UC communication readiness drill 9e00b94e-2561-4eef-a840-be3bb7bd0d18
Deploy National Guard signal teams with satellite phones and repeaters to each contraflow control point (Mammoth, Gardiner, West Yellowstone, Cody) fb04e4f8-ecbb-4809-a0a7-4becf94de504
Pre-position Guard signal equipment and personnel at regional staging hubs 86ef03a6-15c6-46a7-93b5-e5483d03cb70
Establish multi-agency radio-net coordination and commissioning protocol fc2d352f-58df-44a6-be1e-b5a61ded0b3a
Deploy dedicated satellite-phone lines and backup repeaters with independent power at each control point 29b80c9b-718c-4c47-9d2f-1a1b2379b086
Conduct equipment activation and interoperability drill at T−6 hours 5d139f63-a3f2-44b0-920e-1cd37fb27e85
Stage route-guidance materials and HAR/VMS broadcast coordination from control points 97d96365-09d5-4571-9d22-a26e165bdc83
Implement IPAWS/WEA public alert; broadcast route instructions via NOAA Weather Radio, highway advisory radio and variable message signs 121a1787-51cb-4869-b015-8463a4ec4191
Pre-draft and pre-approve alert message templates afeeaaa9-4de2-4536-ba40-6a69f31ca965
Program variable message signs with evacuation and route content 36837fba-e938-41ff-b117-bea492012d16
Establish direct IPAWS activation hotline and alert-routing protocol bc191dbb-a97f-40cc-9daf-f5220a326b7a
Deploy HAR repeater network and satellite phone commissioning 6292e896-fd09-4b9b-bce0-c3ac00cb736c
Print and stage route-instruction cards in English and five languages 83aeea5f-3f33-4cd4-9ed3-e922fed09292
Conduct full alert-cascade tabletop and deployment exercise 2f341066-18bd-4855-97c5-5ff0cbaa8528
Request FAA ZLC/ZSE airspace grounding and pre-authorize narrowly defined rotary-wing medevac and survey exceptions c1816f1c-ff9d-466b-bed1-ab25943fa6c4
Pre-coordinate with FAA facilities on emergency grounding protocol 9e971063-c3be-4ae0-8c3a-f9bd3d30b5d3
Draft emergency NOTAM templates for grounding and exceptions 32705d1b-a19a-48ad-b73b-a704a1093064
Brief FAA facility managers on exception rules and approval chain bda4bdb0-921b-4458-b7cb-7581a5463bde
Validate airspace closure and exception procedures via tabletop exercise f0c2ecd7-d080-4e87-9723-9a327bbe761d
Maintain 24/7 FAA duty-officer contact and activation authority at UC 6f6e9343-3927-4305-9f0d-91ccb40caba3
Position tow and rockfall teams (at least 2) with 15-minute reach to Gallatin Canyon; stage pre-positioned heavy equipment at Mammoth and Spanish Creek 1c0f8440-f0f9-4a1e-a441-b77e748a35d5
Survey staging sites for access and safety 90917123-9005-4f39-ad81-e29cae6ac3a4
Pre-contract tow and rockfall teams with 4-hour notice-to-deploy f8301b7e-2b7f-427a-9b41-e99f0a909493
Pre-position heavy equipment at Mammoth and Spanish Creek depots 6a68a785-5631-4db2-ba38-6ec130101278
Establish contractor communication protocols and activation procedures c2f5406b-b8a8-4212-b71e-c660f2e67e09
Conduct site-readiness and equipment-deployment exercises 62f560f5-bd3a-4888-b2b1-730abe99508a
Issue USGS trigger matrix and pre-authorize Scenario Beta 500 km order for UC issuance without further approval upon triggering e3b8d37e-4f47-4955-ab7c-2be3ecbadd2e
Draft quantified USGS trigger thresholds d8b7c266-bbd7-447d-be8d-ff52e23d293e
Validate trigger matrix with internal UC review ed5bee6c-9a94-4b72-a60b-7df428bb2100
Obtain legal clearance and pre-authorization language 8923d317-0d24-4e3d-817e-db71e37c2beb
Pre-draft and approve Scenario Beta public messaging dc83fb8d-f60a-4464-acb0-81483f0cf4a5
Establish UC trigger-response and 30-min activation SLA 5cd8a773-0870-4f38-b800-8fe4d9664c7d
Phase 1 Zone Zero Evacuation (T+0 to T+6 hours) a11e667c-cea0-46f8-822c-52ca7c4bb58e
Direct visitor and staff outflow across three exits (West 50%, North 30%, East 20%) via contraflow corridors; staff traffic-control points with ranger and highway-patrol teams 56aa0299-1bf0-4987-8a7a-043ed2ae296a
Activate contraflow corridors on three exits by T+1 hour 76cf5364-0676-452e-923f-d1925035d9a9
Staff traffic-control points at all three gates with ranger and patrol teams 9d16f0c1-4823-417f-8863-d2ca489d9bdc
Direct 50% visitor/staff load (17,900 people) westbound through US-20/US-191 to Bozeman 721ad316-6a60-483a-a589-55e812a9ccf1
Direct 30% visitor/staff load (10,740 people) northbound through US-89 to Livingston 079d6c29-f4a5-4856-9c8b-b7f572811f4b
Direct 20% visitor/staff load (7,160 people) eastbound via US-14/16/20 to Cody faf95cb9-0691-4c67-8d7c-31dedf4e8740
Monitor Gallatin Canyon and South Entrance for blockage; execute clearance attempt if <45 minutes or divert to nearest surviving exit 8d577bf8-de83-4754-af23-5e0edc12a32b
Pre-position tow/rockfall teams with 15-min reach 668d87e0-48e3-470d-8150-8c18c1cc679b
Establish real-time blockage detection at both corridors ea9c47fc-8fa8-4c98-9ec9-80dbabcb20db
Execute geotechnical feasibility study for single-lane clearance 54329d5c-2bf0-4e63-8f71-38847b4c51b5
Define clearance vs. diversion decision protocol 9cfbbb81-53f6-41ab-9b13-1a2af4b66502
Prepare contingency overflow diversion routes 088e7e06-e1a0-4afd-abd9-dd26f1132ed7
Deploy ranger-led sweep teams to trailheads, backcountry permit sites and thermal basins; reconcile gate counts with lodging and permit manifests 3005532e-0cbc-49e0-9553-76aacf450419
Pre-event backcountry permit registry and occupancy audit c6081fd1-f7a2-4a49-bfec-7147511f1cb6
Deploy ranger sweep teams to high-priority backcountry and thermal-basin sites by T+1 hour d8880c54-b42d-4601-bcd5-1ffcdf562234
Conduct mandatory hourly check-ins from all backcountry permit holders via satellite phone or radio from T+0 ca30f402-2ee9-4603-ac50-4f8439db09d0
Reconcile lodging manifests and permit databases against actual gate counts at T+3 and T+5.5 hours 7281eeed-74c6-468a-903b-86edc93f3da0
Conduct final Phase 1 sweep of unreached sites and shelter-in-place for backcountry stragglers at T+4 to T+6 hours 291c7b2e-2b88-49af-9af4-3d33ffd752b2
Maintain radio continuity and route guidance to drivers via IPAWS, HAR, printed cards in English and five languages 878bdac2-ce0e-44b9-bab6-33e760093f98
Pre-test IPAWS, HAR, VMS systems at T−6 h 2583fcaf-92a6-4dfa-8a3f-ad4c7cc36747
Pre-print route cards in six languages; stage at every exit gate by T−12 h 1e774de7-3033-40f0-a0c7-8f482f3b1c0b
Deploy Guard signal teams with satellite phones and repeaters to each control point from T+0 c25556e8-2a42-46e9-acb6-f8143f36c32c
Authorize fallback to printed cards if electronic systems fail during Phase 1 7cd9fbf1-d459-4035-9f44-e472dbd925a3
Establish multilingual messaging and periodic updates via IPAWS/HAR/VMS during Phase 1 146a7fc4-92da-4cdd-86f0-784b5d1e3be6
Gate G1 decision point at T+6: confirm ≥98% of 35,800 persons through exit counts; document remaining backcountry occupants under active sweep 431b0630-f720-4e2d-a4f8-227ffc1833d9
Reconcile exit-gate vehicle tallies with lodging and permit manifests f88b766f-b988-411a-a7f8-11a0d98219a0
Reconcile backcountry permit and trailhead sweep status by T+5.5 h a3f6bf69-0188-41ed-ade1-5a1c55d9f3ae
Calculate cumulative evacuation percentage and assess 98% threshold attainment 6df5e76e-a561-40ad-b6ef-3d5b39a3e32f
Issue Gate G1 go/no-go determination and public notification by T+6 h 1c1878a3-306b-4048-936c-3f4cc773f5ac
Phase 2 Zone One Evacuation and Shelter Reception (T+6 to T+24 hours) 7b1f950f-edc9-48e9-b96f-7a2cd283fd3f
Select final shelter sites at T+6 h from latest NOAA/USGS plume forecast; confirm intake capacity of at least 35,800 across Bozeman, Idaho Falls and third site 30f3af60-35c0-4cca-9654-d08b526732c6
Validate shelter-site capacity and infrastructure readiness bb604a3c-049f-47c3-a5a3-8201ffc5f6bf
Integrate real-time NOAA/USGS plume forecast at T+6 h 834922b1-9d6e-4702-841f-c8fe342fff54
Execute shelter-site ranking and UC decision authorization ee2bcce6-a720-4367-b845-baacd9718919
Activate shelter intake and triage operations d6d365ff-9a91-4be9-a31c-39479a9f8680
Maintain shelter-siting decision authority and relocation trigger readiness 2a7ecb65-b1c3-43e7-9c23-62741066589d
Establish triage, registration and family reunification operations at shelter reception centers; deploy medical and multilingual-interpreter staffing 82ead51b-5c94-497e-b4d1-ba5884ef37b7
Pre-contract medical teams and interpreter pools 6b47e72a-02ce-4e82-bc3f-5ae931017d54
Stage triage equipment and family reunification systems 7fae7971-dd74-460d-bc33-eeb187d81136
Develop shelter intake protocols and multilingual procedures 894eb6b3-4ac7-4b2f-abd4-a93bcf8effe9
Train shelter staff on triage, registration and family reunification 030b57ce-05a0-40e4-a39f-c621253de8c2
Establish family reunification database and notification protocols 7f24380b-6b71-4551-a589-fc485d6b0e63
Evacuate Zone One residents (West Yellowstone, Gardiner, Cody) with time-banded departure to maintain evacuation-corridor throughput; target ≥95% clearance by T+24 h 137897c8-4904-4a31-8012-dc12284d7dcf
Conduct Zone One resident census and registry 0b54fc0b-3240-4f1b-86c1-83bb79d5cf8b
Develop time-banded departure windows and corridor load-balancing plan 216d6c06-916d-4e39-9feb-f1005bfd2e16
Issue pre-authorized time-banding and messaging orders to Zone One municipalities 7b2c6620-c88a-4be5-ac3b-bbcd192515ca
Stage transportation and shelter-assignment logistics at departure points 25c598b0-b262-4de8-a1c1-7b00ef47c4d0
Deploy HAR, VMS and multilingual route-card distribution at departure points a3f1d270-892d-4de3-b666-1d8440cf4a17
Dispatch water convoys from Salt Lake City by T+12 h; target arrival by T+24 h via forward depots and resupply cycle management a3e2547d-2bba-42d6-9223-6420e0f1a783
Pre-stage forward-depot water inventory 16eb0196-76f3-4767-83d0-6f126dd945fd
Execute water-convoy routing exercise c1631e0e-95bd-430d-b587-d8e5db6ab266
Validate municipal-water system isolation protocols b20bc813-ce9a-402b-ab2f-d8f096887b49
Contract tiered water-supply resupply cycle 0a617763-c7fb-410b-87ad-94f5be7b3d45
Establish real-time water-consumption monitoring e5fe2840-e479-4a5e-86d8-cac875764ce7
Monitor ashfall PM10 concentrations at shelters; execute shelter relocation if measured ashfall exceeds forecast by >50% or PM10 >200 µg/m³ 980e5739-6eb9-4feb-b176-019fe5e507b2
Deploy PM10 sensors at shelter sites 7baf921d-6056-43f3-8509-3630ace36ffe
Integrate NOAA VAFT forecasts with real-time sensor data 7d4f7645-fc1b-46a5-8ae1-22204599b95b
Establish shelter relocation decision rule and protocols d0050352-ce3c-415a-a828-5814ee302230
Pre-identify and authorize backup shelter locations 009a9b16-3e91-407c-b41e-3473f5257ce0
Execute shelter relocation exercise and validate timelines d05607c0-fd9b-43f8-aef6-662b8c641a94
Gate G2 decision point at T+24: confirm ≥95% Zone One evacuation, perimeter security staffed, and Scenario Beta interim destination list issued to UC fb05cd99-70a6-4e97-aeaa-69b10bdee995
Develop ranked hub list and secure MOUs 5daee30b-2d9d-4aa4-9d83-a5ca75db1e7c
Model and validate tiered-ring evacuation messaging 51d4ac68-e1a8-4787-8da2-1e3f758fd863
Execute multi-state hub-feasibility tabletop exercise f7917ab2-51a9-45a4-b68a-2ad64d4de8b2
Pre-position supply estimates and stage contracts ea59709a-0908-42dc-a4c1-7b19af67b4b8
Validate interim hub list and issue by T+12 h 59018812-8a53-4798-989a-e8d96e84ca77
Responder Exposure Management and Relief Rotation 214640d3-f3f3-4e50-94f7-c6b8c5cd73d1
Enforce responder shift limits: maximum 6 hours at ash-exposed posts, mandatory 2-hour rest with N95 replacement, full withdrawal after 18 consecutive hours d8f99744-30dd-4504-95eb-bd357bac882d
Establish written shift-rotation schedule and color-coded team assignments by T+0 8606fad7-6033-4649-bae6-7a8b673eb8c8
Deploy Guard signal teams with satellite phones and repeaters to enable rotation orders and real-time communications during ashfall bae12cbe-21ef-434b-8343-6ea1e5f43ad2
Conduct fatigue-assessment training for checkpoint supervisors and validate assessment protocols af14801d-9aa1-4f4c-8f94-87bab760543d
Maintain centralized responder log synchronized across UC, Guard and state patrol to track shifts, rest cycles and withdrawals 338e32a2-54a4-47f5-8e7a-cba3cde26a3f
Request pre-authorized National Guard reinforcement if coverage falls below 50% at any post; document activation authority and 4-hour deployment timeline 2045f684-d4b2-4e4d-ae41-b39f654b01c9
Deploy standby reserve (30–50 out-of-region responders) to pre-positioned staging depots; activate reinforcement if coverage falls below 50% at any control point 338251fb-792b-4c85-83c2-16a32c8b78d9
Recruit and pre-contract 30–50 out-of-region responders 3221c900-7703-4e52-8d51-27aff895dc5a
Stage standby responders at three forward depots 635b0fc6-03c9-4460-a683-ae4dbb478dc0
Establish real-time staffing monitoring and 50% coverage alert triggers 6563b342-0b51-4f5a-925f-e0c52c75f65a
Execute standby reserve activation protocols and dispatch within 4 hours f1aaf16a-37ad-4ca4-8664-324a83d7e462
Request National Guard reinforcement if standby reserve is insufficient 3fcf9df3-b98d-4664-898f-90ee93df22c7
Pre-stage separate responder N95 inventory (150,000–200,000 units) at dedicated depot; contract 4-hour resupply cycles if consumption exceeds 20% of stock per day e0e3048f-ca8a-4306-9c00-2c44149acc00
Size responder N95 inventory and procurement timeline e308dd43-cd11-4079-b38c-f26296a923be
Pre-award N95 supply contracts with vendor capacity and 4-hour resupply clauses 6d6a3f36-58b3-4232-9c85-0592b153f000
Identify dedicated responder N95 depot location and stage initial inventory by T+0 3f9ce662-66fc-450a-95c5-128d3feef662
Establish responder N95 distribution and replacement protocols at field checkpoints 70696577-692f-49fd-930d-07b2f7104fb8
Contract and stage 4-hour resupply logistics; activate backup vendor if daily depletion exceeds 20% 16cca4a7-8a11-4ca3-a16c-e8444d808318
Conduct fatigue assessments at each checkpoint using validated protocols; document responder illness, injury or incapacity and trigger rotation or withdrawal 8808e295-0ac5-448c-a297-e955f4111d98
Develop and validate fatigue-assessment protocols 1c4b7b48-f40a-4f71-9243-0e1f6b3b3b2d
Establish centralized responder tracking log and rotation authority 9b800455-661b-410e-ab59-60ac0b3d70ac
Pre-position fatigue-assessment teams and supply responders at checkpoints 2f94ffe6-cfdb-46d9-8b80-db2410f77212
Conduct fatigue-assessment drills and integrate into shift-rotation exercise 1edeffa5-9cba-4bdc-8227-50c4e4073b13
Integrate fatigue assessment into daily UC briefings and staff accountability 17e3b364-74f4-4b49-b47d-76b4a01402ec
Request National Guard reinforcement via pre-authorized Stafford Act emergency delegation; maintain 24/7 staffing at critical traffic-control points through T+72 h 11907586-ef29-4bb6-a25e-e8fe1fc600b5
Obtain pre-signed Guard reinforcement activation authority from three state adjutants general 979907a6-42fd-4e28-b579-ea49d3d840e0
Establish 30–50 person standby reserve at pre-positioned forward staging depots 1fa46586-8e27-48f9-aa15-1c4df71c6c49
Contract out-of-region Guard unit reinforcement with fixed-cost and time-certain mobilization agreements 35c07a26-1998-4f6e-9d22-79fcf87c85b0
Establish UC reinforcement-request protocol and 24/7 Guard liaison seat at forward command cd79585d-d56c-4814-8f35-0731cbc82cdc
Conduct quarterly reinforcement-activation drills during Months 1–3 (2026-11-14 to 2027-01-14) hardening; validate 4-hour mobilization and UC coordination 322e3c6a-1bc6-4c31-a0b4-b68835c45e70
Scenario Beta Zone Expansion and Multi-Ring Evacuation (T+0 to T+72 hours, conditional on USGS trigger) 51a05feb-12ea-4135-9932-52080e15ae25
Monitor USGS indicators (uplift rate, tremor magnitude, gas flux) against pre-authorized trigger matrix; if criteria met, UC issues 500 km Scenario Beta order within 30 minutes without further approval d46f3bf2-6be1-48e6-bc0b-2007fbd36df1
Finalize USGS trigger matrix with quantified thresholds 8cfb56dd-8760-41f7-9b73-cdc04cc6991f
Pre-authorize UC issuance of Scenario Beta 500 km order 5d008e65-e29c-4a3c-af5f-173ebe42a92e
Position USGS volcanologist at UC command post from T+0 644cfa20-4a24-46eb-8ca6-7f2d31d94c26
Establish 30-minute decision interval from trigger confirmation to UC order broadcast 1a9d0615-6925-4c0a-ba48-d9c697c7a069
Execute UC trigger-response tabletop exercise by Month 2 (2026-12-14) 52ad2c48-0e1b-4db6-8e41-4e4bca5a3e51
Execute tiered Scenario Beta evacuation: 0–100 km organized, 100–250 km time-banded, 250–500 km staged departure; issue consistent public messaging via IPAWS and trusted local channels 107bf50e-78e9-453f-8ab5-637d8a8307c3
Design tiered-ring evacuation protocols f8e7c4a7-d8e5-4272-ac35-3a49c65cf22b
Pre-draft IPAWS and HAR messaging templates 449f31e6-d243-4297-9a3f-172518ad62ee
Coordinate with outer-zone municipalities on time-banded scheduling 5a6c5437-cb80-4eb7-a89e-36dc4bc58678
Stage HAR and VMS messaging at outer-zone departure points 24b4317f-8731-480d-b26e-769159bfc838
Establish Scenario Beta incident communications cell a42ace2b-25ac-480a-a51f-ec31f81cb79e
Activate ranked shelter hubs outside the 500 km ring (Denver, Cheyenne candidates); stage water, fuel and N95 supplies and coordinate host-community occupancy transfer de20c18c-531d-4e4a-a8d6-45636ad51fc2
Validate ranked hub list outside 500 km ring f92a58b3-9a76-4447-ac57-5fdd4f8a4ac3
Secure signed host-community MOUs by Month 2 (2026-12-14) d9b8153b-935a-4060-a1bc-5c0b786cb068
Pre-position water, fuel and N95 at forward depots fe2da8b2-9d84-4586-b93b-81c6d829456a
Establish UC-to-hub activation protocol and comms 374d25f4-48af-4543-8875-4aed9ec45bde
Conduct full-scale multi-state hub exercise by Month 3 (2027-01-14) 950c90d2-b6e0-414c-a0f4-c0b8a2b5a3a5
Deploy additional medical surge and field treatment sites at secondary hubs; route respiratory and trauma patients to receiving hospitals with bed-occupancy balancing 50445601-580b-4e83-88a3-1a0e5c18fbe9
Pre-authorize hospital surge protocols with three receiving hospitals 43672c4f-db12-4977-8dc6-c9f20c8e9f21
Stage medical supplies and field-treatment tent kits at secondary hubs cd975d55-1cbf-4f71-959e-03d42817ceb8
Deploy rapid-triage and point-of-care testing teams at shelters 504dffc8-9d88-4f1b-a4b3-ba124abde66b
Coordinate early transfer of high-acuity and fragile populations to receiving hospitals 05b11cbf-8f95-4631-a6b9-33840004db6f
Establish 24/7 hospital command liaison and bed-occupancy monitoring system f48f9eee-974d-4447-ae7b-f7900f6440d2
Manage shadow evacuation of outer-zone residents (Billings, Bozeman, Idaho Falls) via time-banded scheduling or secondary-route channeling to protect primary evacuation corridors 32049684-afd5-4f70-b301-9247a8174d79
Procure and stage 100,000 civilian N95s 62f613d1-be61-42f4-b634-c528c2c21bf2
Maintain 100,000-unit supplemental reserve 2d50f3af-e2ef-4c2f-97f1-949143370973
Distribute masks at shelter reception; train staff 095385c9-6696-41db-94ad-6b0bfa776492
Monitor and adjust replacement cycles by ashfall PM10 baa772f3-cc02-482f-b585-4f2eb17396a5
Separate responder N95s from civilian stock b1d50bb5-eb88-447d-b0f8-5ac337f8f6e2
Confirm Scenario Beta interim destination list and second-stage hub plan finalized and issued to all evacuees and shelters by T+12 h c73f9207-39a7-4125-ae41-cb0fb8a4f6e1
Finalize USGS trigger matrix and UC authority 4c17a651-eec8-47ce-9657-6a6be9dc7f32
Develop ranked hub list outside 500 km ring aefb029d-00dc-4fdc-8671-cb78be59ddcd
Pre-authorize tiered-ring evacuation messaging strategy f637f028-e857-4a14-a0f2-f9a99a8cdeff
Stage interim hub list for T+12 h activation and distribution bdeaff8c-ef3a-45f5-8e35-aee34a5ceb2a
Conduct multi-state trigger-response tabletop exercise 6f725ba0-7482-4f8b-81f6-160f5beb3252
Life-Support Continuity Under Ashfall (T+0 to T+72 hours and beyond) f6389dcc-5518-4fc1-9420-f7fff82f5b96
Tiered fuel allocation: priority 1 (hospitals, comms centers, shelter kitchens); maintain 72-hour reserves at three receiving hospitals and forward command f4e0a36f-4cee-4cca-8bb8-fd29e15476f9
Establish tiered fuel-allocation protocol and priority ranking 7f556707-d1f5-459e-bba9-56219e575e23
Pre-stage 72-hour fuel reserves at receiving hospitals and forward command 7a51b2c2-6da6-4c16-85e5-102c06e2eb66
Contract fuel-delivery convoys with 12-hour dispatch and redundant suppliers d2430474-0520-4c0a-a2cc-8446646ab3d4
Deploy fuel-inventory monitoring and trigger resupply cycles 6495e1ef-e65a-4bde-807a-1090943aeb96
Validate generator capacity and backup power for water and medical systems be373ab7-8e40-432e-ab08-34cde2a1a0e9
Manage water supply chain: forward depots, convoy resupply cycles, municipal-system isolation protocols and emergency groundwater/tanker-fill backup sources e12c6d62-6697-4bc8-8756-0a8f4822fa55
Pre-stage forward water depots 138258df-cc22-429a-95bb-28332c64313f
Contract water convoys with dispatch clauses 15bfc222-77ef-4341-80ae-62c50665c44f
Develop municipal-system isolation and emergency protocols 15bb5b72-8b6b-47b1-abb3-9872c5278ff3
Identify and validate groundwater/tanker-fill backup sources 878a4635-cfc0-4f91-ad87-016cd7919e35
Establish 4-hour resupply cycles and consumption monitoring eec377e8-347d-4d40-b077-d35ff643814a
Distribute 100,000 civilian N95 respirators and 100,000-unit reserve stock at shelters and reception centers; manage replacement cycles under ashfall intensity 3b705a5d-1c1c-4de9-9240-543290cf31e1
Pre-stage N95 inventory at shelter sites 6c5aa488-8772-4796-8cfa-7e2e55d362eb
Establish N95 distribution protocols at intake centers 8097be60-b9c0-4774-8610-4c28b557e78e
Monitor N95 consumption and trigger resupply bce665cb-001c-4aff-b19c-e135c4f66163
Adjust N95 allocation based on ashfall intensity 82d04dd0-9213-4231-a68a-4b9c86b087d7
Validate responder N95 inventory separation 4b3233a6-806f-489d-9380-1d72b62c6403
Pre-authorize hospital surge with regional receiving hospitals; coordinate patient dispersal, early transfer of fragile populations and field-treatment tents at shelters 235338b6-7962-4b0a-9cb3-b819a6bfb9c0
Pre-authorize hospital surge capacity with receiving hospitals 4f7e0a44-ec1b-4412-a418-681734b9aa3a
Coordinate patient-dispersal routing across multi-state receiving hospitals 94220658-9040-4b49-adbd-8b86e7a5b4c1
Deploy field-treatment tents and early-triage teams at shelter sites 829803b2-0850-410a-b02c-d458b7f533d4
Plan early transfer of fragile and critical-care populations 89571b77-4001-40ec-b20e-3b0b3c3229cc
Establish 24/7 hospital command liaison at UC and daily capacity-monitoring updates 26aac5b6-3eb4-4869-8262-c7c6efb59027
Maintain grid power and backup generation at hospitals, shelters and comms centers; contract fuel delivery and manage inventory under ashfall road closures 704c930f-adef-41fa-9db6-163d82a444b3
Pre-stage 72-hour fuel reserves at three receiving hospitals 9072d3a4-518a-43ae-a511-8ea67a749a88
Contract fuel delivery with 12-hour dispatch and dual suppliers 932240aa-5987-4f23-8b2f-20f5b365d5e3
Deploy PM10 sensors and ashfall forecasting; trigger convoy acceleration if demand surge detected 46380a42-947b-42e6-8141-dfec3b2bb36d
Establish tiered fuel-allocation priorities and inventory tracking 76a3cde8-f9b9-406c-a3d5-742a25521fb4
Validate generator operability and cross-train responders on emergency fuel-transfer procedures 200211d1-dfc0-4aac-b348-98ecc91dcaed
Monitor ashfall intensity, duration and ash-cloud progression; issue hourly updates to shelters and hospitals; trigger supply-convoy acceleration if demand surge detected bde0a98c-c5e6-494a-b2b0-196f7945ccd5
Deploy PM10 sensors with redundant satellite uplink 45f87d33-86f6-4b0d-b87d-de971df7f2af
Establish ashfall-update communication protocol 5c329cbf-3b30-4718-83ca-09ce31c5b80a
Validate ashfall-forecast model integration with real-time sensor data ad673592-4d41-4a20-9fe8-7bad7537c9ef
Develop supply-convoy acceleration triggers and monitoring system ff30b535-8db7-41dd-ad07-e992dd1177f9
Pre-stage backup shelter capacity and relocation logistics 5ea16d84-4728-4cb2-b850-e8fbecc07f67
Exclusion Perimeter Security and Re-Entry Planning (T+6 to T+72 hours and beyond) 5396bf1e-38af-4004-9645-3c3e799c9370
Establish fixed checkpoint perimeter on all roads exiting Zone Zero at park boundaries; admit only credentialed responders, utility crews and critical infrastructure staff f7fea251-52c2-419f-8cb0-c1034bba16af
Survey and pre-position checkpoint materials bc405559-92c1-40b3-acbd-62bf22463f6e
Develop credential-verification protocols and access-control procedures 8097da59-d755-4432-8479-2988ee526d75
Coordinate perimeter staffing and relief schedules 8d2e830b-5c6c-41da-a3e1-8c6f7a86547d
Establish communications and credential-verification linkage to forward UC b5525fac-18b8-4426-9987-a97eff4440cd
Execute checkpoint site-readiness drills and full-scale activation exercise c2679c40-ffbf-46b4-a855-d91df0cdf755
Deploy roving mobile patrols and drone surveillance in evacuated Zone One communities to deter looting and unauthorized re-entry 6d5a3adf-5ad3-4256-a5ce-63074dee6ea7
Procure and stage ash-tolerant drone platforms 5b4bc5f8-979d-4eb8-af1f-3e6d28051baa
Establish mobile patrol vehicle fleet and communication infrastructure ee6039c2-0d78-4d0d-94d6-5d1613eeae0d
Develop drone flight operations schedule and pilot roster 1f34c388-0142-40ef-a672-a9e6b5ab4da8
Integrate drone and mobile-patrol intelligence into forward UC situational awareness 588f84d5-2781-486f-8c72-228dfd339454
Establish escalation protocols for looting incidents and unauthorized re-entry be01f675-1710-45e1-a84d-811b1874232a
Develop and pre-authorize escorted-return program for residents with scheduled access windows to retrieve medications, documents and animals 1230ca39-6e3f-400b-8c1e-18e3b1878432
Define escorted-return eligibility and access criteria 0211cb56-e131-4a82-9093-51dab9583a23
Design and schedule return-trip windows and capacity planning 30e70e34-f513-4d5b-ad92-39e5025d6f8e
Contract escort vehicles and drivers; establish dispatch and safety protocols 9c0ef8b3-f7ba-42d9-9ce8-75f1e61dac2f
Conduct intake, vetting and request-scheduling tabletop exercise e0be5943-3fcf-4cac-88fc-053d59d55d21
Establish perimeter and zone-access protocols for escorted-return operations b3e1440f-f715-47f3-bd72-ac1739a007ca
Coordinate perimeter staffing with National Guard and state law enforcement; balance anti-looting enforcement against personnel demands for evacuation logistics 8916fd61-5ef5-40ff-8562-ca4db06bba73
Pre-position Guard and patrol liaison staff c13e45e8-c2bd-40bc-9871-d7b10b18c400
Develop perimeter staffing matrix and relief schedules 399309e6-cbbe-4eb2-83be-c4b956d182be
Establish daily UC briefings and looting-threat assessment updates aac9bfdc-8881-47e0-8892-9dbd3613bce2
Activate standby reserve and out-of-region Guard reinforcement 68e34c36-936b-4e4c-867e-3fc7a57b44cb
Manage competing evacuation and perimeter staffing demands 9c74be15-507a-4143-9238-a19c3c733ae7
Prepare Phase 3 re-entry planning and recovery operations documentation; coordinate with state emergency management and NPS for post-event park and Zone One reopening 8963425d-a4bf-46b9-b5c8-e3742da9d208
Draft Phase 3 re-entry framework and safety criteria a817047e-a057-401b-b816-b84ce964b49e
Establish multi-agency post-event UC working group 60a58b84-5404-4173-b6ed-ca7015c9d0a8
Conduct after-action review and institutional-memory capture e32721f7-470e-43d1-a32f-30df74840f20
Publish written Phase 3 re-entry and recovery plan 1244566d-fa2f-4c7b-819f-b6c226c0c08c
Execute full-scale Phase 3 re-entry and recovery exercise e21453e9-8063-4ba4-87a3-d1c63dc6fb3b

Review 1: Critical Issues

  1. Scenario Beta has no executable destinations, risking cascade failure of Zone Zero evacuation: a pre-authorized VEI-7 trigger will order millions to evacuate with no published shelter hubs, causing uncontrolled shadow evacuation on I-15/I-80/I-90 that saturates the same corridors needed for the 35,800-person Zone Zero clearance, adding an estimated 4–8 hours of delay and stranding 5,000–20,000 people in ashfall zones. The interim hub list is due T+12 hours, the written plan by Month 1 (2026-11-14), and signed MOUs by Month 2 (2026-12-14)—all post-event deadlines with no buffer for discovery of hub capacity shortfalls or distance mismatches (Denver and Cheyenne distances unverified).

  2. Responder staffing has zero relief depth and will collapse under the first incident: 100–150 rangers at 1.5 relief ratio yields only 67–100 concurrent positions, all consumed during the T+2 to T+8 evacuation peak, leaving no margin for injury, equipment failure or respiratory exposure. A single vehicle breakdown or traffic incident at Gallatin Canyon lasting 30+ minutes will halt a checkpoint for 2–4 hours, stranding 500–2,000 vehicles and cascading 1–3 hours of additional delay through the entire operation. The 30–50 standby reserve is not pre-positioned, pre-authorized or tied to a Guard reinforcement commitment.

  3. Shelter siting at T+6 hours based on a single forecast with ±50 km uncertainty and no real-time monitoring creates high risk of placing 10,000–15,000 evacuees in heavy ashfall: if actual ashfall diverges 50 km from forecast or doubles in intensity, Bozeman or Idaho Falls shelters become untenable within 12–24 hours, requiring emergency relocation of 10,000–15,000 people (order within 4 h of exceedance, move and occupy about 8 h)—impossible without pre-authorized backup sites 50+ km upwind, pre-staged buses and protocols. PM10 sensors and relocation protocols are proposed but no deployment timeline exists; real-time response to forecast error is unvalidated.

Review 2: Implementation Consequences

  1. Positive: Pre-authorized Scenario Beta trigger eliminates decision delays and enables rapid 500 km evacuation order within 30 minutes, saving an estimated 2–4 hours of decision latency versus discretionary approval chains. This coupled with a written trigger matrix published in advance (due T+3 h) restores public trust by making escalation criteria transparent. Interaction: Fast triggering only succeeds if second-stage hubs are named and MOUs signed by Month 2 (2026-12-14); without them, the speed advantage evaporates into uncontrolled shadow evacuation. Recommendation: Prioritize signed hub MOUs (5–10 hubs outside 500 km ring) as a blocking dependency for trigger pre-authorization; do not finalize the trigger matrix without simultaneous hub validation.

  2. Negative: Real-time ashfall monitoring and 4-hour shelter relocation protocols depend on PM10 sensors, NOAA VAFT updates every 3 hours, and pre-positioned buses—all requiring T+0 deployment and Months 1–3 (2026-11-14 to 2027-01-14) hardening exercises costing an estimated USD 5–8 million (sensors, exercises, backup shelters). Failure to deploy results in 10,000–15,000 evacuees sheltered in heavy ashfall, overwhelming hospitals with 50–100 additional respiratory cases and consuming USD 20–50 million in emergency relocation and medical surge. Interaction: Ashfall relocations divert buses from primary evacuation, cascading 6–12 hours delay to Zone One clearance and potentially extending overlap with peak ashfall. Recommendation: Treat ashfall monitoring as a pre-T+0 capital investment (not a post-event decision); validate sensor reliability and NOAA forecast latency in a Months 1–3 (2026-11-14 to 2027-01-14) exercise (simulated ashfall, 4-hour relocation drill).

  3. Negative: Responder staffing at 100–150 rangers with zero relief depth and a 30–50 standby reserve that is not pre-positioned or pre-authorized costs an estimated USD 3–5 million and remains opaque until Month 1 (2026-11-14). A single incident (vehicle breakdown, ranger injury, respiratory exposure) during peak evacuation (T+2 to T+8 h) will halt a checkpoint for 2–4 hours, stranding 500–2,000 vehicles and adding USD 50–100 million in indirect response costs and 5–10 preventable deaths. Interaction: Staffing shortfall cascades into longer evacuation time, increasing ashfall overlap; shortage also prevents real-time shelter relocation (buses and crews unavailable). Recommendation: Pre-authorize and seat the 30–50 standby reserve (deployable within 4 h) at T+0 at Billings or Cheyenne; sign Guard reinforcement commitment within Months 1–3 (2026-11-14 to 2027-01-14); conduct a 6-hour shift-rotation exercise at Gardiner checkpoint within Months 1–3 (2026-11-14 to 2027-01-14) to validate 4-hour reserve deployment time.

Review 3: Recommended Actions

  1. Use existing FEMA contract vehicles with verbal activation at T+0 and 12-hour dispatch clauses for water, fuel and N95 convoys, hardening contracts by Month 1 (2026-11-14); expected impact: eliminates 24–48 hour procurement delays, dispatching convoys by T+12 h with arrival T+24 h target (T+18–30 h estimate) versus T+36–72 h, saving USD 50–100 million in emergency-response overhead and preventing water-rationing crises affecting 10,000–20,000 evacuees. Priority: CRITICAL (blocking dependency for Phase 2 shelter operations). Implementation: activate existing contract vehicles verbally at T+0 h and finalize contract terms and vendor sign-off in Month 1 (2026-11-14); establish procurement checkpoint at forward command to track in-flight shipments and enforce 4-hour delay escalation.

  2. Secure written governor authorization letters from Montana, Wyoming and Idaho confirming UC authority over Zone One and Scenario Beta orders by T+6 h (verbal); execute signed MOUs and EMAC mutual-aid arrangements by Month 1 (2026-11-14); expected impact: prevents jurisdictional disputes that delay reroutes by 15–45 minutes per decision, saving an estimated 2–4 hours of total evacuation time and reducing authority-gap risk by 80–90%. Priority: CRITICAL (foundation for Boundary Coordination Officer authority). Implementation: distribute draft authorization package at T+0; schedule governor briefing calls by T+3 h; obtain verbal confirmation by T+6 h; assign legal counsel to lead MOU negotiation with state attorneys general from T+0; target all signatures by Month 1 (2026-11-14).

  3. Conduct geotechnical survey of Gallatin Canyon and South Entrance slide within Month 1 (2026-11-14); develop time-boxed single-lane clearance plan and hard abort triggers; expected impact: quantifies secondary-slide risk (if >20%, write off South Entrance clearance entirely), preventing crews from expending 6–12 hours on infeasible work and freeing heavy equipment for maintaining open corridors, saving USD 5–10 million in wasted clearing effort and 2–4 hours evacuation delay. Priority: HIGH (gates corridor management decisions). Implementation: engage USGS Volcano Disaster Assistance Program at T+0; deliver geotechnical report and bypass options within Month 1 (2026-11-14); pre-position tow teams at Mammoth and Spanish Creek by T+12 h with documented abort triggers (M>4.0 seismic event, >2 cm slope displacement, 30-minute equipment breakdown).

Review 4: Showstopper Risks

  1. Financing split for second-stage hubs and shelter sites remains open; if states/host communities refuse cost-sharing, federal envelope absorbs USD 20–40 million, which is a financing question only, since Beta hub pre-positioning sits inside the readiness package and is not counted again against the USD 30–35 million free contingency, so the buffer is preserved for for supply-chain disruptions or responder reinforcement surge (Likelihood: High). Hub pre-positioning and shelter setup are within the USD 200 million envelope only if cost-sharing is confirmed by Month 1 (2026-11-14); without pre-event clarity, negotiations cascade into Months 2–3 (2026-12-14 to 2027-01-14), delaying hub readiness and forcing makeshift shelter capacity at Scenario Beta trigger. Interaction: Financing delay compounds Scenario Beta hollowness: no hubs ready, no pre-positioned supplies, uncontrolled shadow evacuation. Recommendation: Resolve federal vs. state/local/host-community cost split by Month 1 (2026-11-14) via FEMA-governor MOU negotiations; document explicit cost-allocation line items and pre-approve state legislative authority for matching funds. Contingency: If states decline cost-share, hubs remain in the readiness package inside the USD 160 million base; shelter relocation (USD 5–10 million) stays the only identified draw on the USD 40 million contingency.

  2. FEMA Region 10 (Idaho) liaison seat at Denver RRCC from T+0 is a single point of failure for Idaho mutual aid; no written pre-authorization or resource-commitment MOU exists between FEMA Region 10 and Pocatello/Boise suppliers (Likelihood: Medium). If the Region 10 liaison is unavailable or communications with Idaho resources are delayed, water and fuel convoys experience 2–6 hour dispatch delays, pushing arrival at Idaho Falls shelter from T+24 h to T+30–36 h, leaving 10,000 evacuees on water rationing for 1–2 additional days and increasing dehydration/medical emergency risk by 20–30%. Interaction: Region 10 coordination failure cascades into shelter water-supply crisis, triggering early relocation or public-health incident. Recommendation: Execute a signed FEMA Region 8/10 coordination MOU by Month 1 (2026-11-14), with a verbal liaison seat at T+0, pre-authorizing Idaho mutual-aid resource commitments (100,000+ gallons water, 50,000 gallons fuel, portable generators) and naming Idaho State Emergency Management liaison with 24/7 availability; conduct a 2-hour tabletop Region 10 activation drill within Months 1–3 (2026-11-14 to 2027-01-14) to test dispatch speed. Contingency: Pre-position a 100,000-liter supplemental water reserve at Pocatello or Boise by T+12 h; if Region 10 liaison is unavailable, activate backup ground-convoy dispatch from Salt Lake City to Idaho Falls on parallel route (US-89 south via Arizona, estimated 36–48 h).

  3. Zone One resident population remains unquantified; census is not scheduled until T+6 h, leaving no time to pre-stage shelter capacity or transport before evacuees arrive (Likelihood: High). If Zone One population exceeds the census estimate by 20–30% (plausible during peak tourism season), shelter capacity shortfall of 5,000–10,000 people forces overflow to unsecured secondary venues or out-of-state hubs, delaying shelter registration by 4–6 hours and increasing family-reunification failure rate by 15–25%. Interaction: Population underestimate cascades into shelter-capacity crisis, which forces emergency Scenario Beta hub activation even if trigger has not fired, consuming contingency supplies and creating false alarm messaging credibility loss. Recommendation: Conduct Zone One resident and transient-visitor census by T+6 h (estimate), coordinate with concessioners (Xanterra manifests) and county visitor bureaus to obtain hotel/lodge/campground occupancy estimates; pre-stage to the canonical 35,800 and seek a proxy Zone One estimate by T+6 h. Contingency: If the census shows population materially above planned capacity, size and activate third-site shelter expansion and request additional buses from FEMA contract vehicle pool after the census; if capacity still insufficient, issue tiered public messaging advising outer-zone residents to self-supply lodging (hotels in non-evacuation zones) to reduce shelter load.

Review 5: Critical Assumptions

  1. Assumption: NOAA/USGS ashfall forecasts are accurate within ±50 km and can be updated every 3 hours with reliable PM10 concentration outputs. If forecast error exceeds ±50 km or updates become unavailable, shelter sites chosen at T+6 h will be placed in heavy ashfall; relocation of 10,000–15,000 evacuees within the 8 h move-and-occupy window is unvalidated, stranding 200–500 people in moderate-to-heavy ash (PM10 > 100 µg/m³, suitability review threshold) for 6–12 hours and increasing respiratory hospitalizations by 50–100% (cost impact: USD 20–50 million emergency relocation + medical surge). Interaction: Forecast failure cascades into early N95 depletion (consumption 3–5x model estimate), forcing rationing and protective-equipment shortages for responders. Recommendation: Validate NOAA VAFT model skill for Yellowstone by T+12 h through USGS consultation; deploy PM10 sensors at all shelters by T+0 with independent satellite uplink (not cell-dependent); conduct a Months 1–3 (2026-11-14 to 2027-01-14) shelter-relocation exercise (simulated 50 km forecast error, 4-hour bus dispatch) to expose real relocation latency and adjust decision rules accordingly.

  2. Assumption: Three receiving hospitals (Bozeman Deaconess, Livingston HealthCare, Eastern Idaho Regional Medical Center) have adequate generator fuel reserves (72 hours on-site) and can sustain continuous operations during 4–8 hour grid outages caused by ash-induced transmission-line flashovers. If generators lack fuel or fail to start under stress, hospitals lose power within 4–6 hours, forcing manual ventilation of 10–20 critical patients and canceling 10–20 surgeries; estimated cost: USD 50–100 million in emergency generator mobilization and 5–15 preventable hospital-related deaths. Interaction: Hospital power failure disables wound-transfer coordination, stranding ambulances en route and cascading medical transport delays by 2–4 hours. Recommendation: Pre-position 72-hour fuel reserves at all three hospitals by T+12 h, validate generator operability and cross-train responders on fuel-transfer procedures at Month 0 (2026-10-14); coordinate with utilities (Montana-Dakota, Pacific Power, Idaho Power) to pre-authorize emergency load-shedding sequences by Month 0 (2026-10-14) to prevent cascading blackout across the region.

  3. Assumption: Scenario Beta secondary-stage hubs (Denver, Cheyenne) lie outside the 500 km ring, have committed shelter capacity for 100,000–500,000 additional evacuees, and can be activated and supplied within 24–36 hours of trigger without requiring post-event MOU negotiations. If hubs are inside the ring, lack capacity commitment, or require state legislative approval to activate, Scenario Beta trigger becomes unexecutable; uncontrolled evacuation of 100,000+ unordered residents saturates I-15/I-80/I-90, preventing Zone Zero clearance and extending evacuation delay by 4–8 hours (cost impact: USD 200–500 million in cascade-failure response and 20–50 preventable deaths). Interaction: Hub validation failure directly undermines the pre-authorized trigger's credibility; if hubs cannot receive evacuees, published trigger matrix becomes hollow and erodes public trust in escalation messaging. Recommendation: Verify Denver and Cheyenne distances from Yellowstone center and distance from ashfall plume by T+12 h (desktop check); obtain written capacity confirmation (beds, kitchens, medical triage) from host counties by Month 1 (2026-11-14); execute signed MOUs documenting pre-authorization to activate within 24 h of UC request by Month 2 (2026-12-14); conduct a full multi-state Beta hub activation tabletop (including sample bus routing and intake registration) by Month 3 (2027-01-14).

Review 6: Key Performance Indicators

  1. KPI 1: Evacuation Throughput and Gate Clearance — Target: Gate G1 (T+6 h) ≥98% of 35,800 (at least 35,084 persons); Gate G2 (T+24 h) ≥95% of registered Zone One residents cleared; corridor blockage duration <45 minutes. Success metric: exit counts reconciled against lodging manifests and permits by T+6 h and T+24 h gates. If achieved, confirms contraflow design (about 660 veh/h per exit as fleet average; West requires about 994 veh/h, about 1,190 from T+1) and responder staffing are adequate. Interaction: Blockage delays compound ashfall overlap; shortfalls indicate tow-team positioning or diversion rules require revision. Monitoring: Track hourly vehicle counts at all three gates starting T+1 h; trigger real-time reroute if any exit cumulative count falls >10% below the load-split target; compare exit manifests with backcountry sweep status at T+5 h decision checkpoint.

  2. KPI 2: Shelter Occupancy and Relocation Readiness — Target: Primary shelters (Bozeman, Idaho Falls, third site) reach full planned capacity (15,000, 10,000, 10,800 estimate) by T+12 h with <2-hour intake processing; relocation order issued within 4 hours of an exceedance (200 µg/m³ or a failed suitability review at 100 µg/m³, proposed threshold). Success metric: <5% shelter-intake processing errors; zero evacuees left unplaced; sheltered exposure above 200 µg/m³ is minimized, with completion time set (estimate) after the relocation drill. Interaction: Relocation latency directly reduces responder relief-rotation time available elsewhere. Forecast error cascades into overflow; backup-site readiness is the containment lever. Monitoring: Deploy PM10 sensors at T+0 with hourly reporting to forward UC; establish shelter-occupancy dashboard updated every 2 hours; execute relocation drill (sample 1,000 evacuees moved to backup sites) within Months 1–3 (2026-11-14 to 2027-01-14) to validate the 4 h detection-to-order step, set move and occupy times (8 h stop rule) and identify bottlenecks.

  3. KPI 3: Supply-Chain Continuity and Responder Availability — Target: Water convoy arrival by T+24 h (or T+18–30 h via forward depots T+12 h); N95 consumption ≤20% of daily stock; responder coverage ≥50% at all traffic-control and perimeter posts through T+72 h; zero responder entrapment or respiratory-injury casualties. Success metric: all three receiving hospitals maintain generator fuel >24 hours on-site; fuel resupply convoys dispatched within 4 hours of low-fuel alert. Interaction: Supply failure cascades into shelter rations and responder withdrawal, which collapses traffic throughput and evacuation timeline. Low coverage (<50%) at one post halts a corridor 2–4 hours, stranding 500–2,000 evacuees. Monitoring: Establish 24/7 logistics checkpoint at forward command tracking water/fuel/N95 inventory in-flight and on-site; activate backup suppliers if convoy is delayed >4 hours beyond T+12 h dispatch; flag responder staffing falls below 50% coverage at any post within 30 minutes and request standby reserve deployment.

Review 7: Report Objectives

  1. Primary Objectives: Report documents a 72-hour Yellowstone evacuation plan for 35,800 Zone Zero evacuees (T+0 to T+6 h) and 100 km Zone One residents (T+6 to T+24 h), with pre-authorized Scenario Beta expansion to 500 km if USGS triggers fire. Intended audience: FEMA Regions VIII and X, state governors (MT, WY, ID), NPS, and multi-state UC stakeholders. Key decisions to be informed: (1) pre-authorization of UC trigger matrix and 500 km evacuation order within 30 minutes; (2) NPS-to-state boundary handoff and Boundary Coordination Officer authority; (3) Scenario Beta second-stage hub naming and signed MOUs by Month 2 (2026-12-14).

  2. Deliverables: Written Scenario Beta Secondary-Stage Evacuation Plan naming 5–10 ranked hubs outside 500 km ring with signed host MOUs by Month 2 (2026-12-14); interim ranked hub list by T+12 h; signed governor authorization and EMAC mutual-aid MOUs by Month 1 (2026-11-14); responder exposure limits and 30–50 standby reserve deployed by T+0; PM10 sensors and 4-hour relocation protocols at shelters by T+0; three full-scale exercises (Scenario Beta routing, shift rotation, water convoy) by Month 3 (2027-01-14); post-event after-action report and institutional-memory capture.

  3. Version 2 Differences: Version 1 treated Scenario Beta as a pre-authorized trigger with no executable second-stage plan; Version 2 must require signed hub MOUs and supply pre-positioning as blocking dependencies before trigger pre-authorization is finalized. Version 1 left responder staffing at 1.5 relief ratio with zero contingency; Version 2 must specify concrete 6-hour shift limits, separate N95 inventory sizing and 30–50 standby reserve pre-positioning by T+0. Version 1 deferred all ashfall monitoring and shelter relocation to post-event; Version 2 must mandate PM10 sensor deployment and real-time monitoring from T+0 to enable 4-hour relocation protocols.

Review 8: Data Quality Concerns

  1. Zone One resident population census is not quantified; baseline estimate lacks source and seasonal variation unknown. Critical because shelter capacity pre-staging (Bozeman 15,000, Idaho Falls 10,000 estimate) depends on it; if actual population is 20–30% higher during peak tourism, shelter shortfall of 5,000–10,000 forces overflow to unsecured secondary venues, delaying intake 4–6 hours and increasing registration failures by 15–25%. Recommendation: Execute census by T+6 h via concessioner manifests and county visitor-bureau surveys; validate against lodging occupancy and campground permits; pre-stage to the canonical 35,800 and size any added capacity after the census, seeking a proxy Zone One estimate (county, lodging manifests) by T+6 h.

  2. Scenario Beta hub distances from Yellowstone center to Denver and Cheyenne are not verified; canonical facts note 'distances not verified' yet designation assumes these hubs lie outside the 500 km ring. Critical because if either hub is actually inside the ring or ashfall reaches it under different wind scenarios, Scenario Beta destinations become untenable within 12–24 hours of occupancy, forcing emergency secondary relocations and cascading shelter crisis. Consequence: if relocation needed mid-operation, USD 20–50 million emergency transport cost and 4–8 hour evacuation delay. Recommendation: Map exact distances using geographic center of Yellowstone Caldera; model ashfall plume reach to each hub under USGS ensemble forecasts (10–20 wind/emissions scenarios); confirm final hub selection by Month 1 (2026-11-14) with ashfall survivability assessment.

  3. Water convoy realistic arrival time is T+18–30 h (estimate), not the T+12 h dispatch target; forward-depot pre-staging at Bozeman and Idaho Falls (quantity 200,000–300,000 liters estimate) is not specified with contract timelines or supplier naming. Critical because shelters must sustain 25,000–35,000 people with adequate water from T+6 h onward; if convoys arrive T+30 h and forward depots are not staged by T+0, shelters face 18–24 hour water rationing, increasing dehydration risk in 20–30% of occupants and forcing 100–200 emergency hospital transfers for electrolyte imbalance. Recommendation: Stock forward depots by T+12 h and finalize water-supply contracts naming delivery timelines and depot locations in Month 1 (2026-11-14); conduct a Salt Lake City to Bozeman convoy exercise under ashfall simulation and I-15 congestion conditions within Months 1–3 (2026-11-14 to 2027-01-14) to measure realistic travel time; keep the T+24 h arrival target (realistic T+18–30 h, estimate) with explicit backup supplier activation if arrival is delayed >4 hours.

Review 9: Stakeholder Feedback

  1. FEMA Region 10 and Idaho mutual-aid resource pre-authorization: Does Idaho State Emergency Management Agency confirm written commitment to dispatch 100,000+ gallons bottled water, 50,000 gallons fuel, and portable generators within 6 hours of UC request? Critical because Idaho Falls shelter (10,000 occupants) depends on Pocatello/Boise suppliers if Salt Lake City convoy is delayed; unconfirmed commitment risks 12–24 hour supply shortage affecting 10,000 evacuees and stranding USD 10–20 million in contingency. Recommendation: Obtain signed FEMA Region 10 MOU and Idaho State Emergency Management commitment by Month 1 (2026-11-14); conduct a 2-hour tabletop Region 10 activation drill within Months 1–3 (2026-11-14 to 2027-01-14) testing dispatch authorization and supply-order fulfillment; document backup supplier names and contact authority for fallback activation if primary commitment fails.

  2. Scenario Beta hub financing ownership and host-community pre-acceptance: Do Denver, Cheyenne, and any secondary hub counties formally accept the role of secondary shelter sites and agree to pre-position supplies (food, water, medical) on 48–72 hour notice without requiring post-event legislative approval or cost-reimbursement disputes? Critical because unsigned host MOUs leave hub pre-positioning undefined and delay activation beyond T+12 h interim list; cost uncertainty (federal vs. state vs. local share) defers spending decisions into Months 2–3 (2026-12-14 to 2027-01-14), delaying supply staging; hub pre-positioning stays inside the readiness package and is not a contingency draw. Recommendation: Initiate host-county outreach by Month 0 (2026-10-14); obtain written capacity confirmation and pre-acceptance letters by Month 1 (2026-11-14); execute fully signed MOUs with explicit federal cost-share percentages and supply pre-positioning schedules by Month 2 (2026-12-14).

  3. Contraflow corridor engineering validation and tow-team positioning: Can tow and rockfall teams realistically reach any Gallatin Canyon blockage within 15 minutes and clear single-lane debris within 4 hours under ashfall conditions, or must the 45-minute blockage diversion threshold be revised based on geotechnical feasibility? Critical because if clearance time exceeds 4 hours or secondary-slide risk during work exceeds 20%, tow-team deployment becomes a liability (crews entrapped), not an asset; diversion rule then becomes the only viable option, reducing effective exit capacity by 20–30% and cascading 3–6 hours evacuation delay. Recommendation: Deliver geotechnical survey of Gallatin Canyon (debris volume, slope stability, secondary-slide probability) by Month 1 (2026-11-14); execute tow-team mobilization and diversion exercise at Mammoth staging depot within Months 1–3 (2026-11-14 to 2027-01-14); validate 15-minute reach time and 4-hour clearance window under ashfall simulation; revise corridor management strategy and loss-of-exit contingency if empirical findings contradict assumptions.

Review 10: Changed Assumptions

  1. Assumption: 660 vehicles/hour per-exit throughput (3.0 persons/vehicle average, ~2,000 vehicles/hour total) is achievable on narrow two-lane mountain corridors (US-191, US-89, US-14/16/20) under ashfall visibility reduction (<100 meters) and evacuation-traffic chaos. If actual throughput drops 20–30% due to ashfall speed reduction (10 mph safe speed vs. 60 mph assumed) or staging-lot bottlenecks, evacuation extends from T+6 h to T+8–10 h, stranding 500–2,000 vehicles in peak ashfall and increasing respiratory-injury hospitalizations by 40–60% (cost impact: USD 20–50 million emergency medical surge). Version 1 assumed baseline traffic-engineering; Version 2 requires geotechnical and staging-capacity validation. Interaction: Reduced throughput cascades into responder fatigue (shifts lengthened 2–3 hours beyond 6 h limit) and shelter intake backlog. Recommendation: Validate contraflow termini capacity and throughput by measuring parking-lot staging dimensions, turn-pocket geometry and queue-storage length at Mammoth, Gardiner and West Yellowstone by Month 0 (2026-10-14); conduct a mock contraflow exercise under simulated ashfall conditions within Months 1–3 (2026-11-14 to 2027-01-14) to measure actual vehicle speeds and identify any lot-saturation chokepoints.

  2. Assumption: Scenario Beta secondary-stage hubs outside the 500 km ring (Denver, Cheyenne candidates) are survivable under ashfall and have zero ashfall overlap under any USGS ensemble forecast scenario. If modeling reveals that either hub experiences measurable ashfall (>50 µg/m³) under 10–20% of wind/emission scenarios, hub survivability assumption fails; designation as 'safe' destination becomes probabilistic, not deterministic. Consequence: evacuees routed to hubs may face unprotected ashfall within 12–24 hours of arrival, forcing emergency secondary relocation to tertiary hubs and cascading USD 50–100 million in unplanned transport (cost impact: 2–4 hour additional delay and 10–20 preventable respiratory deaths). Interaction: Hub ashfall risk compounds Scenario Beta triggering: if trigger fires and hubs are not ash-safe, the pre-authorized 500 km order becomes unexecutable. Recommendation: Run USGS ashfall ensemble forecasts (10–20 wind/emissions combinations) to all candidate hubs (Denver, Cheyenne, Albuquerque, Las Vegas) by Month 0 (2026-10-14); confirm zero ashfall above 20 µg/m³ for each hub in >90% of scenarios; designate only validated ash-safe hubs as Scenario Beta destinations in final MOU by Month 2 (2026-12-14).

  3. Assumption: Bottled-water supply chain from Salt Lake City, Pocatello and Butte can deliver water to shelters by T+24 h target (realistic T+18–30 h, estimate) via forward depots (T+12 h); the 1.43 million liters is the 10-day supply target without ashfall-road closures or evacuation-traffic congestion blocking I-15 and I-90 corridors. If ashfall visibility falls below 50 meters or I-15 congestion from unordered evacuees reaches 40%+ by Hour 8–12, convoy speeds drop from 60 mph to 10–15 mph and arrival time extends to T+36–48 h. Consequence: shelters must ration water for 18–24 hours; 10,000–20,000 evacuees experience dehydration risk and 5–10 preventable electrolyte-imbalance deaths (cost impact: USD 10–20 million emergency relocation and medical response). Version 1 assumed 12 h dispatch = T+24 h arrival; Version 2 must account for realistic ashfall delays. Interaction: Water shortage cascades into shelter-intake crisis and early Scenario Beta activation if Zone One population exceeds estimates. Recommendation: Conduct a water-convoy exercise from Salt Lake City to Bozeman under simulated ashfall (fog machines reducing visibility to 50–100 meters) and I-15 saturation (25–40% traffic) within Months 1–3 (2026-11-14 to 2027-01-14); measure actual transit time; if arrival is after T+30 h, pre-stage 300,000+ liters at forward depots by T+0 instead of relying on convoy arrival by T+24 h.

Review 11: Budget Clarifications

  1. Federal vs. state/local/host-community cost-share for shelter sites and Scenario Beta secondary hubs is unresolved; decision required by Month 0 (2026-10-14) to unlock spending authority. If states/host communities refuse cost-sharing, federal envelope absorbs USD 20–40 million (estimated Beta hub pre-positioning), but Beta hub pre-positioning is already inside the readiness package (USD 47.5–87 million within the USD 160 million base) and is not counted again; free contingency stays at USD 30–35 million. Recommendation: Obtain written cost-allocation confirmation from FEMA, Montana, Wyoming and Idaho emergency management by Month 0 (2026-10-14) documenting federal percentage, state match and host-community in-kind contributions; embed allocations in signed MOUs by Month 1 (2026-11-14).

  2. Water convoy pre-award contract language must specify 12-hour dispatch and 4-hour resupply-cycle performance targets; unclear if FEMA contract vehicles already include bottled-water and fuel convoy capacity or if new blanket purchase agreements are required. If existing contracts lack surge clauses, procurement delays revert to 24–48 hours, pushing water arrival to T+36–48 h instead of T+24 h and creating USD 10–20 million emergency replacement cost for supplemental depots and helicopter resupply. Recommendation: Audit current FEMA contract vehicle roster for water, fuel and N95 capacity by T+12 h; use existing FEMA vehicles with verbal activation at T+0 and dispatch by T+12 h; issue RFP for missing surge-capacity gaps with 12-hour dispatch performance targets as a separate Month 1 (2026-11-14) hardening item.

  3. Budget contingency allocation for Scenario Beta execution is ambiguous; if Beta trigger fires, does the USD 40 million contingency activate for second-stage hub supplies (food, water, medical) or is that cost absorbed by host communities or a separate federal appropriation? If contingency were consumed for other unfunded items, no reserve would remain for shelter relocation, hospital surge or supply-chain failures, forcing choices between competing priorities and risking USD 50–100 million emergency response cost overruns. Recommendation: Define explicit contingency-allocation tiers in the budget envelope by Month 0 (2026-10-14): shelter relocation USD 5–10 million (estimate) as the only identified contingency draw; Beta hub pre-positioning stays in the readiness package, and hub activation operating costs are a separate, unfunded item pending a Beta-specific appropriation or host in-kind contributions by Month 1 (2026-11-14).

Review 12: Role Definitions

  1. Boundary Coordination Officer (Forward UC Element): Requires explicit job description, interagency authority matrix, and 24/7 succession plan. Why essential: Officer holds pre-authorized decision authority over traffic reroutes and shelter assignments at NPS-to-state boundary during T+0 to T+24 h peak evacuation; if authority limits are undefined or succession is absent, reroute decisions cascade to higher command, adding 15–45 min delay per decision (estimated 2–4 h total evacuation delay and 500–2,000 stranded vehicles). Recommendation: Draft written Officer position description by T+0 specifying decision authority (reroutes without supervisory approval if comms lost >5 min), communications protocols (dedicated satellite phone to NPS incident commander, three state on-scene commanders, Denver RRCC), and succession roster (named primary, alternate, backup); confirm 24/7 availability and seat Officer at forward element at T+0.

  2. FEMA Region 10 Liaison (Denver RRCC Seat): Explicit mandate, resource-commitment authority, and 24/7 dispatch protocol for Idaho mutual aid required. Why essential: Liaison coordinates water, fuel and generator convoys from Pocatello and Boise for Idaho Falls shelter (10,000 occupants); if role lacks written authority to activate pre-authorized mutual-aid resources or liaison is unavailable, Idaho resource dispatch is delayed 6–12 h, pushing water arrival from T+24 h to T+30–36 h and leaving evacuees on ration for 1–2 days (estimated 10–20% dehydration-risk exposure, USD 10–20 million emergency resupply cost). Recommendation: Document Region 10 Liaison responsibilities in signed FEMA Region 8/10 MOU by Month 1 (2026-11-14); seat liaison at T+0; confirm 24/7 availability and pre-authorized dispatch authority for minimum 100,000 gallons water, 50,000 gallons fuel and portable generators on UC request; conduct activation drill at Month 0 (2026-10-14).

  3. Scenario Beta Secondary-Stage Hub Activator (Multi-State Coordination Role): Clarity on who authorizes hub occupancy, supply routing and time-banded evacuation schedules across Colorado, Wyoming, Idaho and Utah required. Why essential: If Scenario Beta triggers at T+12 h, interim hub list must be transmitted to evacuees with published occupancy assignments within 30 min; if no single named authority owns hub activation and supply coordination across state lines, decisions delay 2–4 h per hub or contradict each other, causing evacuees to queue at wrong destinations and stranding 10,000–20,000 people (estimated USD 50–100 million emergency reroute cost and 4–8 h additional delay). Recommendation: Designate a named Deputy UC (or FEMA Region 8 officer) as Scenario Beta Hub Activator by Month 1 (2026-11-14); grant explicit authority to issue hub-activation orders via IPAWS/WEA and coordinate with state emergency managers; pre-authorize pre-positioning of supplies at each hub by Month 2 (2026-12-14); test activation authority in a full multi-state tabletop exercise by Month 3 (2027-01-14).

Review 13: Timeline Dependencies

  1. Scenario Beta interim hub list (T+12 h) precedes signed host MOUs (Month 2 = 2026-12-14): If hubs cannot be named and published by T+12 h due to incomplete distance verification or capacity confirmation delays, Scenario Beta trigger becomes unexecutable at T+12–24 h, forcing uncontrolled outer-zone evacuation (estimated 50,000–200,000 additional evacuees) onto I-15/I-80/I-90, saturating primary Zone Zero corridors and delaying 35,800 park evacuees 4–8 additional hours. Interaction: Uncontrolled flight cascades into water/shelter shortages and extends ashfall overlap by 20–40%. Recommendation: Initiate hub distance verification and capacity surveys from T+0; obtain interim capacity confirmations (unsigned) from all 5–10 candidates by T+0 h to enable T+12 h interim list issuance; defer final signed MOUs to Month 2 (2026-12-14) without blocking interim publication.

  2. Responder exposure limits and standby reserve deployment must be confirmed and pre-positioned before T+0, but formal deployment authorization from state adjutants general may not arrive until T+24–48 h: If standby reserve is not seated at forward depot by T+12 h, a checkpoint incident at T+3–6 h cannot be covered within 4 h, halting one corridor and stranding 500–2,000 vehicles. Interaction: Staffing failure cascades into longer evacuation, increasing ashfall overlap and preventing real-time shelter relocation due to lack of available buses/crews. Recommendation: Secure written pre-event Guard reinforcement commitments from all three state adjutants general by Month 1 (2026-11-14), pre-positioning standby personnel at designated depots by T+12 h under a Stafford Act emergency-delegation clause (verbal activation authority at T+0, not subject to 24–48 h state approval delays).

  3. Water convoy dispatch T+12 h to shelters by T+24 h assumes realistic 12–30 h travel time (estimate) and no I-15 congestion from shadow evacuation; if Scenario Beta triggers before water arrives (T+12–18 h range), secondary hub activation will consume buses, extending water-transport logistics and cascading arrival to T+30–48 h. Interaction: Delayed water arrival leaves first 10,000 Zone Zero evacuees at Bozeman/Idaho Falls with 18–24 h ration shortfall; early Beta trigger also pulls forward-depot stock into secondary hubs. Recommendation: Pre-stage forward depots (Bozeman, Idaho Falls) with 200,000–300,000 liters by T+0 (not relying on Salt Lake City convoy for T+24 h arrival); sign all water-supply contracts with 4-hour resupply clauses and secondary-source names (Pocatello, Butte) by T+0 to enable rapid convoy re-dispatch if Scenario Beta consumes primary supply ahead of schedule.

Review 14: Financial Strategy

  1. Post-event cost-share and federal vs. state/local expense attribution for recovery and Phase 3 re-entry unspecified: if FEMA covers 100% of Scenario Alpha response but states claim 25–50% cost-share for Scenario Beta secondary hubs (estimated USD 20–40 million), the question is who finances these items; Beta hub pre-positioning is inside the readiness package and is not a second draw on the USD 200 million envelope. Interaction: Unresolved attribution delays federal reimbursement claims (12–24 months post-event), forcing state/local budget gaps and straining partner agencies' willingness to participate in future operations. Recommendation: Obtain written FEMA pre-event guidance on cost-share percentages for multi-state Scenario Beta operations by Month 1 (2026-11-14); embed federal reimbursement triggers and cost-allocation rules in signed MOUs with all states and host hubs; clarify whether pre-event hardening (readiness package, exercises) is 100% federally funded or requires state match.

  2. Long-term institutional sustainability: no budget line for annual maintenance, refreshment or re-validation of MOUs (currently estimated at USD 2–5 million/year for Months 4–60 = 2027-02-14 to 2031-10-14 and beyond); if Scenario Alpha does not occur, readiness assets (sensors, contracts, pre-positioned supplies) must be rotated, tested and renewed through ongoing appropriations. Interaction: Budget uncertainty for months 4–60 (2027-02-14 to 2031-10-14) leaves the plan at risk of lapsing if annual funding is not secured post-Month 3 (2027-01-14); standby responder contracts and pre-positioned supplies degrade without refreshment. Recommendation: Establish a dedicated Yellowstone Evacuation Readiness Fund with annual Congressional appropriation (proposed USD 2–5 million/year) by Month 2 (2026-12-14); include line items for equipment rotation, MOU renewal (every 2 years), responder reserve retainer and full-scale exercises every 18 months.

  3. Break-even or cost-avoidance threshold not quantified: no analysis of whether USD 200 million pre-event investment avoids more expensive post-event emergency response or whether a scaled-down readiness posture would reduce cost while accepting higher mortality/morbidity risk. Interaction: Without explicit cost-benefit analysis, decision-makers cannot justify the readiness budget to legislatures or compare it against alternative mitigation (e.g., pre-event visitor restrictions, park closure during eruption window). Recommendation: Commission a formal cost-benefit analysis by Month 2 (2026-12-14) comparing: (1) full readiness plan (USD 200 million pre-event) vs. baseline response (USD 500–800 million post-event emergency cost estimate + 20–50 preventable deaths); (2) scaled-down readiness (USD 100 million, forgoing Beta hubs and some supply pre-positioning) vs. full plan; publish findings to justify budget request and communicate risk-mitigation value to stakeholders and Congress.

Review 15: Motivation Factors

  1. Clear, measurable milestones with executive visibility and accountability: Gate G1 (T+6 h, ≥98% evacuation) and Gate G2 (T+24 h, ≥95% Zone One clearance) provide objective success criteria that sustain stakeholder confidence. If milestones slip (actual clearance <95% at T+24 h), motivation falters because ambiguity spreads about whether the plan is viable; estimated cost: USD 50–100 million in extended operations and 5–10 additional deaths from ashfall overlap. Interaction: Gate slippage cascades into Scenario Beta credibility loss (if Beta triggers before Zone One clears, public trust in escalation messaging collapses). Recommendation: Publish monthly progress reports (Months 1–3, 2026-11-14 to 2027-01-14) documenting readiness checkpoints (MOUs signed, exercises completed, sensors deployed) with explicit red/yellow/green status; brief governors and FEMA administrators monthly to sustain political commitment.

  2. Tangible pre-event hardening wins (signed MOUs, completed exercises, equipment deployed) by Month 1 (2026-11-14): if Month 1 (2026-11-14) deadline passes with unsigned hub MOUs or unexecuted shift-rotation exercises, urgency erodes and follow-on activities drift. Consequence: Scenario Beta plan remains hollow through T+0; if trigger fires and interim hub list cannot be published by T+12 h, uncontrolled shadow evacuation cascades (estimated 4–8 h evacuation delay and 5,000–20,000 stranded evacuees). Interaction: Unmet Month 1 (2026-11-14) targets signal that the plan is underfunded or politically unsustainable, undermining responder recruitment and multi-state partner engagement. Recommendation: Establish a Months 1–3 (2026-11-14 to 2027-01-14) Readiness Steering Committee (NPS, FEMA, governors, UC leadership) with monthly executive-level reviews; publish signed MOUs within 30 days of Month 1 (2026-11-14) and exercise completion dates within 60 days; tie responder recruitment and supply contracts to visible progress milestones.

  3. Sustained federal funding commitment through the 72-hour window and post-event cost-share clarity (federal vs. state/local/host): if appropriation lapses or cost-attribution disputes surface in Months 1–2 (2026-11-14 to 2026-12-14), stakeholders question whether readiness is credible. Consequence: state/local partners withdraw, supply contracts are delayed or cancelled, and responder reserve recruitment stalls; estimated cost: USD 50–100 million in emergency procurement premiums and 1–3 month plan readiness delays. Interaction: Funding uncertainty compounds Scenario Beta hub validation (if hubs cannot confirm pre-positioning costs are federally covered, they refuse to participate). Recommendation: Secure written FEMA pre-event guidance on cost-share percentages by Month 1 (2026-11-14); embed reimbursement triggers in all MOUs; obtain Congressional pre-appropriation of the USD 200 million envelope by Month 0 (2026-10-14) start and confirm no rescission risk through Month 3 (2027-01-14).

Review 16: Automation Opportunities

  1. Real-time evacuation-gate vehicle counting via automated traffic sensors and RFID windshield tags: Deploy sensors at all three exit checkpoints (Mammoth, Gardiner, West Yellowstone, Cody) at T+0 with real-time dashboard integration to forward UC. Expected savings: eliminates 30–60 minute manual gate-count reconciliation cycles (currently required at T+3, T+5.5, T+6 h decision points), enabling Gate G1 assessment 30 min earlier and accelerating any reroute decisions by 15–30 min per incident. Cost to deploy: USD 0.5–1 million (sensors, dashboard). Interaction: Faster gate-count feedback cascades into quicker diversion decisions if corridor blockages occur, reducing stranded-vehicle exposure by 200–500 people per incident. Recommendation: Procure RFID tag stock and deploy sensors by T+12 h; pre-stage tag distribution at all park entrance stations; test sensor accuracy and tag-reader latency in a Months 1–3 (2026-11-14 to 2027-01-14) contraflow exercise.

  2. Pre-programmed IPAWS/WEA alert templates and automated dispatch routing by shelter-intake status: Develop and pre-code all Zone One and Scenario Beta evacuation messages (English + five languages) with geographic targeting and time-triggered release logic by T+0. Expected savings: eliminates 15–30 min messaging delays at each decision point (T+0 public alert, T+6 h shelter-assignment broadcast, T+12 h Scenario Beta interim hub list), reducing driver uncertainty and uncontrolled departures by 10–20%. Cost to implement: USD 0.2–0.5 million (message development, IPAWS technical setup, testing). Interaction: Faster alert dispatch reduces shadow evacuation of outer-zone residents, preserving I-15/I-80/I-90 corridor capacity for primary evacuees. Recommendation: Finalize all message templates and geographic-targeting logic by T+0; conduct a Months 1–3 (2026-11-14 to 2027-01-14) full-cascade alert exercise (deploy all messages within 5 min of each trigger point); validate message clarity with native speakers (3–5 per language) by Month 0 (2026-10-14).

  3. Automated supply-chain inventory tracking and resupply-trigger algorithms: Deploy GPS-tracked convoy monitoring and automated alerts to forward UC when water/fuel/N95 inventory at shelters falls below consumption-rate thresholds (e.g., 20% of stock per day triggers backup-supplier activation). Expected savings: eliminates 4–8 h manual inventory audits and decision delays, enabling 4-hour resupply cycles versus current 8–12 h estimated lag. Cost to implement: USD 2–3 million (GPS/IoT sensors on trucks, inventory-management software, contracted monitoring staff). Interaction: Automated triggers accelerate N95 and fuel resupply before stock-outs cascade into respiratory-protection shortages or generator fuel failures, reducing emergency convoy surges and USD 20–50 million unplanned logistics costs. Recommendation: Select and pre-deploy inventory-tracking platform by T+12 h; test sensor-to-alert latency under ashfall simulation within Months 1–3 (2026-11-14 to 2027-01-14); pre-authorize backup suppliers to activate within 2 h of automated alert (not waiting for human decision).

Q1: What is the 'Scenario Beta' escalation trigger, and why does the plan pre-authorize it without a defined second-stage destination list?

A1: Scenario Beta is a pre-authorized order to expand evacuation from Zone One (100 km) to a 500 km radius affecting millions of people, triggered by USGS indicators (e.g., VEI-7 probability ≥20% remaining). The UC can issue this order within 30 minutes without further approval. However, no second-stage shelter hubs, host-community MOUs or supply pre-positioning exist yet. This creates a critical gap: the trigger is authorized but unexecutable, risking uncontrolled shadow evacuation that saturates I-15/I-80/I-90 and delays the primary 35,800-person Zone Zero evacuation by 4–8 hours.

Q2: Why does the plan state that water convoys will arrive by T+24 hours when realistic estimates are T+18–30 hours, and how does this gap affect shelter operations?

A2: The plan targets water dispatch by T+12 h from Salt Lake City, expecting arrival by T+24 h. However, ashfall reduces I-15 visibility to 50–100 meters, safe convoy speed drops to 10–15 mph, and evacuation-traffic congestion of 25–40% delays all northbound traffic. Realistic arrival is T+18–30 h. This 6–30 hour gap forces shelters to sustain 25,000–35,000 evacuees on rationing for 1–2 days, increasing dehydration risk and secondary health emergencies. The plan mitigates this by pre-staging forward depots at Bozeman and Idaho Falls by T+0, but depot capacity (200,000–300,000 liters estimate) and resupply schedules are not specified in detail.

Q3: What does 'responder exposure limits and relief rotation regime' mean, and why is the plan's specification of 100–150 rangers at 1.5 relief ratio insufficient?

A3: Responder exposure limits define maximum shift length (proposed: 6 hours at ash-exposed posts), mandatory rest cycles (proposed: 2-hour rest with N95 replacement), and full withdrawal thresholds (proposed: 18 consecutive hours). At 1.5 relief ratio, 100–150 rangers yield only 67–100 concurrent positions, all consumed during peak evacuation (T+2 to T+8 h) with zero cushion. A single traffic incident or ranger injury lasting 30+ minutes will halt a checkpoint for 2–4 hours, stranding 500–2,000 vehicles in ash. The plan proposes a 30–50 person standby reserve from out-of-region agencies, but it is not pre-positioned or pre-authorized, creating a single-point staffing failure.

Q4: How does the plan select final shelter sites at T+6 hours, and what risks does ashfall forecast uncertainty (±50 km) create for evacuation safety?

A4: At T+6 h, shelter sites are chosen from the latest NOAA/USGS plume forecast. The plan specifies PM10 thresholds (>50 µg/m³ triggers forecast update; >100 µg/m³ triggers shelter-suitability review) and proposes ranked backup shelters 50+ km upwind. However, ashfall forecast uncertainty for a VEI-6 event is ±50 km or greater (unvalidated, never directly observed in North America). If actual ashfall diverges 50 km from forecast or doubles in intensity, 10,000–15,000 evacuees will be sheltered in moderate-to-heavy ash within 12–24 hours, requiring emergency relocation. The plan proposes a 4-hour relocation protocol, but actual bus dispatch and transport require 6–12 hours, stranding 200–500 people in ash if conditions worsen.

Q5: What is the relationship between the pre-authorized Scenario Beta trigger and the three-exit contraflow design, and why do they create a cascade-failure risk if Scenario Beta fires during Zone Zero or Zone One evacuation?

A5: The plan's three-exit contraflow (West 50%, North 30%, East 20%) is designed to clear 35,800 Zone Zero evacuees by T+6 h and Zone One residents by T+24 h. Scenario Beta (500 km radius) is pre-authorized to trigger at T+12–24 h, ordering millions in outer zones to evacuate. If Scenario Beta fires before Zone One clearance (likely at T+12–24 h range), outer-zone residents (Bozeman, Billings, Idaho Falls) will attempt uncontrolled self-evacuation on the same I-15/I-80/I-90 corridors needed by Zone Zero and Zone One evacuees. This shadow evacuation of 50,000–200,000 unordered people saturates the corridors, reducing organized evacuation throughput by 30–50%, adding 4–8 hours to total evacuation time and stranding 5,000–20,000 people in ashfall zones.

Q6: The plan pre-authorizes a Scenario Beta 500 km evacuation order affecting 'millions of people' without quantifying the actual population in that ring or confirming that published destinations can absorb them. What are the ethical implications of issuing an evacuation order without knowing whether shelter exists for the evacuees?

A6: Scenario Beta pre-authorization prioritizes decision speed (30-minute trigger) over execution readiness, raising a core ethical tension: the UC can order millions to flee without confirmed shelter destinations, forcing evacuees into uncontrolled flight and potential stranding in ashfall zones. This violates the principle of duty of care—government cannot ethically order evacuation if it has not verified that refuge exists. The risk of false escalation (trigger fires but Beta destinations are overwhelmed or unreachable) also erodes public trust and may cause non-compliance with future orders, indirectly harming evacuees who ignore warnings. Mitigation requires signed hub MOUs and published destination lists by T+12 h, but this depends on post-event negotiation, not pre-event certainty.

Q7: The plan uses 'shelter-in-place' messaging in outer zones (250–500 km ring) early in the 72-hour window but then may reverse this order if Scenario Beta triggers. How does the plan protect against loss of public trust and non-compliance if escalation appears to reverse earlier guidance?

A7: The plan acknowledges this risk under 'Shadow Evacuation Suppression and Public Compliance Dynamics': early shelter-in-place messaging (if Beta does not trigger) is designed to prevent uncontrolled shadow evacuation, but if Beta later triggers and evacuees are told to leave, the reversal may be perceived as deception or government incompetence. Proposed mitigation is an 'Adaptive Messaging Protocol' published pre-event explaining that escalation logic is transparent (specific USGS thresholds trigger the reversal). However, the plan does not specify how to communicate this reversal credibly during the chaos of ashfall or confirm that local media and trusted voices will support the message. If compliance drops 20–40% due to trust loss, uncontrolled evacuation consumes the same corridors needed for organized Zone One clearance, cascading 4–8 hours of additional delay.

Q8: The plan prioritizes responder safety through exposure limits (6-hour shifts, 18-hour withdrawal) and separate N95 respirator stock, but these protections compete with evacuation throughput during the T+2 to T+8 peak. How does the plan balance responder protection against the risk that strict limits reduce traffic-control coverage and delay civilian evacuation?

A8: Responder exposure limits are ethically justified: responders should not sacrifice their health or lives for the response. However, enforcing 6-hour shifts and full withdrawal after 18 hours reduces concurrent traffic-control positions from the estimated 100–150 rangers to 67–100 during peak evacuation, with zero relief depth. A strict interpretation leaves checkpoints unmanned during critical hours, halting corridors and stranding 500–2,000 evacuees per incident. The plan proposes a 30–50 standby reserve to fill gaps, but if not pre-positioned and pre-authorized, the reserve is unavailable when needed. This creates a trilemma: (1) enforce limits and accept traffic delays that trap evacuees in ash, (2) waive limits and expose responders to preventable injury, or (3) invest heavily in pre-positioned relief to avoid choosing between the two. The plan implicitly assumes option 3 is feasible, but responder N95 stock is 'counted separately' without explicit sizing, and the standby reserve is not pre-authorized.

Q9: The plan pre-stages 100,000 civilian N95 respirators (user constraint) for 35,800 evacuees (about 2.8 masks per person over 10 days) but does not account for responder consumption or replacement cycles if ashfall is 2–3 times heavier than forecast. How does the plan handle N95 shortages if forecast error occurs, and what are the ethical implications of inadequate respiratory protection?

A9: The 100,000 civilian stock assumes ~2.8 masks per person for 10-day shelter occupancy and approximately 1-mask-per-person-per-day consumption in moderate ashfall. If ashfall is 2–3 times heavier than forecast, consumption rises to 2–3 masks per person per day, exhausting stock within 12–24 hours instead of 10 days. The plan proposes a supplemental 100,000 N95 reserve at Billings or Salt Lake City with 8-hour transport agreement, but deployment depends on real-time PM10 monitoring (not pre-deployed sensors) and rapid recognition of consumption surge. If the surge is not detected or transport is delayed, evacuees will lack respiratory protection during heavy ashfall, increasing respiratory-distress hospitalizations by 50–100% and preventable deaths by 5–10. Ethically, this represents a choice to accept mortality risk rather than pre-stage larger N95 reserves (estimated USD 5–10 million additional cost).

Q10: The plan specifies pre-authorized evacuation orders and trigger matrices published in advance to prevent hindsight blame on decision-makers, but this transparency also reveals the thresholds that enable judicial or political challenge post-event. How does pre-publishing USGS triggers affect legal liability if evacuation proves to have been unnecessary or if the triggers are deemed to have been too conservative or too aggressive?

A10: Publishing a pre-authorized trigger matrix (USGS indicators, thresholds, decision timeline) in advance protects decision-makers from hindsight blame by showing that escalation was rule-based, not arbitrary. However, it also creates a fixed target for post-event legal and political challenge: if the trigger fires and Scenario Beta evacuation occurs but the eruption does not materialize, evacuees or host communities may sue FEMA, USGS or the UC for 'unnecessary' evacuation, citing the published thresholds as evidence of over-caution. Conversely, if thresholds prove too aggressive (i.e., the trigger does not fire but a VEI-6 eruption occurs), beneficiaries of the timely evacuation may sue for claiming the thresholds were too conservative. This liability ambiguity is partially resolved by pre-event publication (demonstrating deliberation) and USGS science-based justification, but it is not eliminated. The plan does not address legal-defense strategy, post-event liability apportionment, or how to prove that triggers were 'correct' given the irreducible uncertainty of eruption forecasting.

A premortem assumes the project has failed and works backward to identify the most likely causes.

Assumptions to Kill

These foundational assumptions represent the project's key uncertainties. If proven false, they could lead to failure. Validate them immediately using the specified methods.

ID Assumption Validation Method Failure Trigger
A1 Hubs outside the 500 km ring (Denver, Cheyenne) exist with enough verified capacity and will accept evacuees on short notice; distances and capacity are not verified. Measure distances from the caldera to Denver and Cheyenne, and request written capacity and acceptance statements from both emergency managers within 7 days. Either hub lies inside 500 km, or combined confirmed capacity is below 50,000 beds, or neither commits to accept evacuees without legislative approval.
A2 Contracts, vendors and convoys can be activated verbally at T+0 and deliver water, fuel and N95 stock within the 12 h dispatch and T+24 h arrival targets without pre-awarded contracts. Audit existing FEMA contract vehicles for surge clauses and run a dry-run verbal activation with three vendors, timing dispatch. Any vendor needs more than 12 h to dispatch, or existing vehicles lack surge capacity, or Salt Lake City to Bozeman arrival falls after T+30 h (transit over 18 h) in the dry run (estimate).
A3 The public and outer-zone residents will follow staged instructions, and trust holds if shelter-in-place guidance is superseded by a 500 km order, so shadow evacuation stays manageable. Run a message-comprehension and compliance-intent pilot with 1,000 residents in Bozeman, Gardiner and Cody, using the reversal message sequence. Stated compliance with time-banded departure is below 70%, or recall of assignment logic is below 80%.
A4 Gallatin Canyon and Gardiner corridors can sustain about 660 vehicles/hour per exit as a fleet average only (estimate), with the West exit needing about 994 vehicles/hour (about 1,190 from T+1) (estimate) under ashfall and tremor, and blockages clear within the 45-minute diversion threshold (proposed threshold). Commission a rapid geotechnical and staging-lot survey of Gallatin Canyon, Mammoth and West Yellowstone, and time a tow-team dispatch drill to the canyon. Measured West throughput is below about 994 vehicles/hour (estimate), or North falls below about 600 vehicles/hour (about 716 from T+1) or East below about 400 vehicles/hour (estimate), tow reach time exceeds 15 minutes (proposed threshold), or clearance of a typical blockage exceeds 4 hours.
A5 Guard signal teams, IPAWS/WEA, HAR/VMS and satellite links will keep drivers and responders connected through ashfall and tremor from T+0, with interoperable radio nets across NPS, state patrol and Guard. Run an interoperability and ash-degradation test of Guard repeaters, satellite phones and HAR/VMS at three control points, confirming Guard signal unit count. Any agency pair cannot hold a two-way net at a control point, fewer than 4 signal teams are available by T+1 h, or message delivery to test drivers falls below 90%.
A6 Responder staffing of 100-150 NPS rangers (estimate) plus patrol and Guard, with a 30-50 person standby reserve deployable within 4 h (proposed threshold), can hold 6 h shift limits at every post through T+72 h. Obtain written headcounts by unit from NPS, state patrol and Guard, and obtain written commitments and mobilization times from the standby reserve agencies. Confirmed concurrent positions fall below 67, reserve commitments cover fewer than 30 people, or reserve mobilization time exceeds 4 h.
A7 The USD 200 million planning envelope (estimate) and USD 30-35 million free contingency (estimate) cover shelters, hubs and state costs, and the federal versus state/local/host split gets settled before spending is needed. Obtain written cost-share positions from FEMA and the MT, WY and ID emergency management agencies, and reconcile the readiness package (USD 47.5-87 million, estimate) against the base. Any state or host community declines cost-sharing, or unfunded items push committed draws above the USD 40 million contingency.
A8 Bozeman, Idaho Falls and the third site can be stocked and staffed, with a relocation order issued within 4 h (proposed threshold) of a PM10 exceedance, with buses, drivers and backups 50+ km upwind available when needed. Run a relocation drill of 1,000 volunteers from one shelter to a surveyed backup, timing decision, notification, bus dispatch and intake, and confirm bus and driver counts. Detection-to-order exceeds 4 h, completion of relocation (time to be set after the drill) (estimate) exceeds 8 h (estimate), or fewer than 20 buses are confirmed for relocation.
A9 Visitors, including non-English speakers, vehicle-less and mobility-limited guests, will reach the three exits and follow fixed district-to-gate assignments so that 98% of 35,800 are confirmed out by T+6 h. Obtain concessioner manifests and run a lodge-level sampling of language, vehicle and mobility shares, plus a gate-assignment comprehension test using route cards in six languages. Vehicle-less or mobility-limited visitors exceed the confirmed bus and shuttle capacity, or gate-assignment comprehension in the test is below 90%.

Failure Scenarios and Mitigation Plans

Each scenario below links to a root-cause assumption and includes a detailed failure story, early warning signs, measurable tripwires, a response playbook, and a stop rule to guide decision-making.

Summary of Failure Modes

ID Title Archetype Root Cause Owner Risk Level
FM1 The Verbal Order That Never Rolled Process/Financial A2 Emergency Logistics and Supply-Chain Director CRITICAL (16/25)
FM2 The Ring With No Landing Technical/Logistical A1 Scenario Beta Secondary-Stage Destination Planner CRITICAL (20/25)
FM3 The Reversal That Broke Trust Market/Human A3 Communications and Public Alerting Coordinator HIGH (12/25)
FM4 The Roster That Ran Dry Process/Financial A6 Responder Safety and Fatigue-Management Officer CRITICAL (16/25)
FM5 The Canyon That Closed Technical/Logistical A4 Contraflow Operations and Traffic Control Manager CRITICAL (15/25)
FM6 The Silent Drivers Market/Human A5 Communications and Public Alerting Coordinator CRITICAL (16/25)
FM7 The Envelope That Split Three Ways Process/Financial A7 FEMA Region VIII Finance and Grants Lead HIGH (12/25)
FM8 The Shelter Under the Plume Technical/Logistical A8 Ashfall Forecasting and Dynamic Shelter-Siting Officer CRITICAL (15/25)
FM9 The Guests Who Stayed Behind Market/Human A9 Communications and Public Alerting Coordinator HIGH (12/25)

Failure Modes

FM1 - The Verbal Order That Never Rolled

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If no signed surge-dispatch contract covers water and fuel by Month 1 (2026-11-14), halt shelter activation planning and escalate to a federal pre-positioning mandate.

FM2 - The Ring With No Landing

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If fewer than 5 verified hubs with signed MOUs exist by Month 2 (2026-12-14), suspend automatic 500 km authority and revert to a staged decision cell.

FM3 - The Reversal That Broke Trust

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If pilot compliance stays below 70% after two message revisions, abandon shelter-in-place messaging and use time-banded departures only.

FM4 - The Roster That Ran Dry

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If confirmed responder headcount is below 67 concurrent positions at T+0, treat Gate G1 as slipped and escalate to a different decision (two exits is not a G1-compliant fallback) until reserves are seated.

FM5 - The Canyon That Closed

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If the West exit is not restorable within 6 hours, shelter in place queued vehicles and cancel single-lane clearance attempts.

FM6 - The Silent Drivers

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If interoperable nets are not confirmed at all three gates by T+1 h, delay contraflow release and run staged departures by printed card.

FM7 - The Envelope That Split Three Ways

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If no cost-share agreement covers Beta hubs by Month 2 (2026-12-14), cancel hub-dependent automatic Beta authority and pivot to a staged decision cell.

FM8 - The Shelter Under the Plume

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If no backup site can accept at least 10,000 people within 8 h of an exceedance, halt new intake at the affected shelter and divert arrivals.

FM9 - The Guests Who Stayed Behind

Failure Story
Early Warning Signs
Tripwires
Response Playbook

STOP RULE: If more than about 716 visitors (including backcountry) remain unaccounted for at T+6 h, suspend Zone One phase start until a sweep plan is set.

Reality check: fix before go.

Summary

Level Count Explanation
🛑 High 13 Existential blocker without credible mitigation.
⚠️ Medium 6 Material risk with plausible path.
✅ Low 1 Minor/controlled risk.

Checklist

1. Violates Known Physics

Does the plan's success require breaking a known law of physics (e.g., thermodynamics, conservation of energy, speed-of-light limit, causality)?

Level: ✅ Low

Justification: This is a disaster-response logistics and operations plan grounded entirely in conventional engineering: traffic management, evacuation, shelter operations, supply dispatch, communications, and command-and-control. All causal mechanisms are physical—human decision and action directing material resources (vehicles, supplies, personnel, infrastructure) and information (alerts, orders, sensor data). The plan does not require breaking any law of physics or depend on non-physical causation for success.

Mitigation: No physics-related action required — the plan does not invoke physics-incompatible mechanisms.

2. No Real-World Proof

Does success depend on a technology or system that has not been proven in real projects at this scale or in this domain?

Level: 🛑 High

Justification: Rated HIGH because the plan hinges on a novel combination of contraflow under ashfall, real-time dynamic shelter relocation, and pre-authorized 500 km escalation without confirmed second-stage destinations. No comparable North American precedent exists for this system under a VEI-6 ashfall event. Gallatin Canyon clearance feasibility, ashfall forecast reliability for shelter-relocation decisions, and Scenario Beta destination verification are all unvalidated; failure in any critical track cascades into 4–8 hour evacuation delay and 5,000–20,000 stranded evacuees.

Mitigation: Run three parallel validation tracks by Month 3 (2027-01-14): (1) Geotechnical/Engineering: confirm Gallatin Canyon single-lane clearance feasibility within 4 hours and secondary-slide risk via USGS survey; conduct a tow-team mobilization drill to validate 15-minute reach time. (2) Technical/Environmental: validate NOAA ashfall forecast skill and PM10 sensor accuracy; conduct a shelter-relocation exercise moving 1,000 evacuees to backup sites under simulated 50 km forecast divergence, measuring move and occupy times (8 h stop rule) with the 4 h limit applying to the relocation order only. (3) Logistical/Legal: execute signed MOUs from at least 5 hubs outside the 500 km ring with capacity commitments (Month 2 = 2026-12-14) and pre-positioning timelines; conduct a multi-state Beta hub activation tabletop. Define two NO-GO gates: (A) If Gallatin Canyon clearance exceeds the 4-hour time-box for a single-lane clearance attempt or secondary-slide risk exceeds 20%, apply the loss-of-exit rule (exit not restorable within 6 hours: shelter in place, redirect to nearest surviving exit). (B) If fewer than 5 hubs are validated and signed by Month 2 (2026-12-14), suspend pre-authorized Scenario Beta and revert to a discretionary decision cell. Stop rule: if any critical track fails, the cascade-risk management protocol requires plan revision before T+0 activation.

3. Buzzwords

Does the plan use excessive buzzwords without evidence of knowledge?

Level: ⚠️ Medium

Justification: Rated MEDIUM because two critical strategic concepts—Scenario Beta second-stage hub destinations and Responder Exposure Limits—lack defined owners, quantified success metrics, and operational mechanisms. The Escalation Trigger defers USGS indicator values to T+3h, leaving pre-authorization hollow. Core evacuation mechanics (contraflow, command, comms) are well-defined with owners and measurable gates (G1 T+6h ≥98%, G2 T+24h ≥95%), but secondary strategies lack this rigor.

Mitigation: Draft one-pagers for Scenario Beta hubs (verify Denver/Cheyenne distances, confirm capacity and acceptance by Month 0 = 2026-10-14), Escalation Trigger (finalize USGS values by T+3h), and Responder Exposure Limits (name the Safety Officer by T+0 with explicit withdrawal authority) specifying owner, mechanism-of-action, and quantified success metrics. Publish Strategy Reference Guide to all stakeholders by Month 1 (2026-11-14).

4. Underestimating Risks

Does this plan grossly underestimate risks?

Level: 🛑 High

Justification: Rated HIGH because the plan pre-authorizes a Scenario Beta 500 km evacuation order without defining executable second-stage destinations, host-community capacity, or interim hub list before T+0. If the trigger fires (likely T+12–24 h), millions of outer-zone residents will lack published shelter addresses, causing uncontrolled shadow evacuation on I-15/I-80/I-90 that saturates the same corridors needed for organized Zone Zero evacuation, adding an estimated 4–8 hours delay and stranding 5,000–20,000 people in ashfall. Interim hub list is due T+12 h (post-event deliverable), written plan due Month 1 (2026-11-14), and signed MOUs due Month 2 (2026-12-14)—all blocking dependencies exist only after the trigger fires and cascades begin.

Mitigation: Scenario Beta Secondary-Stage Destination Planner: by Month 1 (2026-11-14), deliver written second-stage evacuation plan naming 5–10 ranked hubs outside the 500 km ring, with signed host MOUs by Month 2 (2026-12-14) confirming capacity and pre-positioning timelines; validate distances, model ashfall survivability at each hub, and pre-authorize tiered messaging. Conduct a full multi-state Beta hub activation and shelter-intake exercise by Month 3 (2027-01-14) to expose real relocation latency and confirm execute-ability before T+0.

5. Timeline Issues

Does the plan rely on unrealistic or internally inconsistent schedules?

Level: 🛑 High

Justification: Rated HIGH because the plan pre-authorizes a Scenario Beta VEI-7 trigger ordering immediate 500 km evacuation affecting millions of people without a defined, executable second-stage destination plan. The interim hub list is due T+12 hours (post-event, during active evacuation), written plan due Month 1 (2026-11-14), and signed host MOUs due Month 2 (2026-12-14)—all after the trigger fires. Without published shelter destinations by T+12 h, evacuees will lack assigned refuge addresses, triggering uncontrolled shadow evacuation of 50,000–200,000+ outer-zone residents onto I-15, I-80 and I-90 that saturates the same corridors needed to clear 35,800 Zone Zero evacuees. This cascade-failure coupling creates a critical single-point vulnerability: pre-authorization without pre-positioned capacity.

Mitigation: Scenario Beta Secondary-Stage Destination Planner: Execute written Scenario Beta Secondary-Stage Evacuation Plan by Month 1 (2026-11-14) naming five or more ranked shelter hubs outside the 500 km ring with signed host-community MOUs confirming capacity and 48-hour resource availability; validate Denver and Cheyenne distances from Yellowstone center and ashfall survivability under USGS ensemble forecast scenarios; pre-position 20,000–30,000 person equivalent food, water and N95 supplies at each hub; issue interim ranked hub list (at least five outside ring) by T+12 hours; conduct full-scale multi-state Beta hub activation exercise by Month 3 (2027-01-14).

6. Money Issues

Are there flaws in the financial model, funding plan, or cost realism?

Level: 🛑 High

Justification: Rated HIGH because committed funding sources for the USD 200 million planning envelope are not documented. The plan names "a federal emergency declaration (Stafford Act) plus pre-event contract vehicles" as the assumed funding source with "USD 150–250 million surge envelope" (estimate), but provides no signed appropriation, FEMA pre-award authority, or congressional allocation. No financing gates, covenants, or draw schedule are specified. The readiness package (USD 47.5–87 million estimate) lacks assigned funding owners (federal vs. state/local/host-community cost-share unresolved). Critical Scenario Beta second-stage hub pre-positioning (USD 20–40 million estimate) and shelter relocation contingency (USD 5–10 million estimate) have no secured funding. The "free contingency" of USD 30–35 million (estimate) is a theoretical buffer, not committed. Without signed appropriations, FEMA advance authorization, or explicit cost-allocation MOUs, the plan cannot execute beyond T+0 without financial bottlenecks cascading into supply delays, hub non-activation, and responder shortfalls.

Mitigation: FEMA Region VIII Finance Lead: By T+0, secure verbal activation of existing FEMA contract vehicles (dispatch by T+12 h); by Month 1 (2026-11-14), secure written FEMA pre-authorization for USD 200 million Stafford Act emergency declaration and harden the contract vehicles for water, fuel, N95 and bus supply. Obtain written federal vs. state/local/host-community cost-allocation confirmation from FEMA and governors specifying reimbursement percentages for shelters, hubs, and interstate support within 30 days; embed allocations in signed MOUs by Month 1 (2026-11-14). Define no-go financing gate: if USD 160 million base appropriation is not confirmed in writing by T+12h, halt all non-critical hardening and escalate to Congressional emergency session.

7. Budget Too Low

Is there a significant mismatch between the project's stated goals and the financial resources allocated, suggesting an unrealistic or inadequate budget?

Level: ⚠️ Medium

Justification: Rated MEDIUM because the USD 200 million budget (USD 160M base + USD 40M contingency at 20%) is stated without vendor quotes, cost-per-evacuee benchmarks, or scale-appropriate comparables. Plan scope is multi-state evacuation of 35,800 Zone Zero + unquantified Zone One + millions in Scenario Beta. No three quotes substantiate major costs (water convoys dispatched by T+12 h with T+24 h arrival target, N95 procurement, shelter operations, fuel reserves). No per-area normalization (cost per person-day, shelter bed, convoy ton-mile) provided. Hurricane Rita and Camp Fire case studies cited but not analyzed for comparable costs. Financing split (federal vs. state/local/host-community) unresolved, risking USD 20–40M exposure if states decline cost-share. Contingency adequacy depends on Zone One population census (unquantified) and Scenario Beta activation (probability triggers may be hollow without second-stage hub execution confirmed). 20% contingency meets the 10–20% rule by stated value, not validated necessity.

Mitigation: Emergency Logistics and Supply-Chain Director: Obtain three vendor quotes each for bottled-water convoys (Salt Lake City to Bozeman/Idaho Falls, dispatch by T+12 h, arrival T+24 h target, T+18–30 h estimate), N95 bulk purchase and resupply, diesel fuel pre-positioning and convoy, and shelter operational costs (food, water, medical, staff per person-day) from regional suppliers by Month 1 (2026-11-14). Normalize all costs per evacuee-day and per shelter bed; benchmark against Hurricane Rita (2005) and Camp Fire (2018) cost-per-evacuee data from FEMA HAZUS or state emergency management reports. Reconcile line-item readiness package (USD 47.5–87M) against quotes; revise contingency from assumed 20% to actual variance (±15–30% estimated) based on market data. Resolve federal vs. state/local cost-share allocation by written MOU with governors and FEMA by Month 1 (2026-11-14); quantify federal obligation ceiling and cost-shock threshold for contingency drawdown. Conduct a cost-sensitivity analysis showing whether USD 200M envelope survives Zone One population +20% variance, Scenario Beta hub pre-positioning acceleration, and shelter-relocation surge (USD 20–50M estimated). Document all benchmarks and quotes in a Cost Realism Validation Report due Month 1 (2026-11-14).

8. Overly Optimistic Projections

Does this plan grossly overestimate the likelihood of success, while neglecting potential setbacks, buffers, or contingency plans?

Level: 🛑 High

Justification: Rated HIGH because the plan states key projections (water arrival T+12 h dispatch/T+24 h target, 660 veh/h throughput per exit, 45-min blockage threshold, 4-h relocation order, 98% evacuation by T+6 h) as single numbers or fixed thresholds without ranges, confidence intervals or alternative scenarios. Canonical facts acknowledge "T+18–30 h realistic arrival" but do not integrate this into a sensitivity analysis or best/worst-case envelope. No best-case, base-case, or worst-case scenario table exists for the three critical projections (throughput, water arrival, responder availability). The plan lacks contingency logic tied to projection variance; contingency is financial (20% budget buffer) not operational (throughput/timing scenarios).

Mitigation: Emergency Logistics and Supply-Chain Director and Contraflow Operations Manager: By Month 1 (2026-11-14), deliver a Sensitivity Analysis Report for the three most critical projections: (1) Water convoy dispatch and arrival time under ashfall and evacuation-traffic congestion (base T+24 h, conservative T+36 h, optimistic T+18 h); (2) Contraflow throughput per exit (fleet average about 660 veh/h, West requirement about 994 veh/h, about 1,190 from T+1; best-case 800 veh/h if ashfall remains light, worst-case 400 veh/h if visibility <50 m); (3) Blockage clearance and diversion (base 45 min, conservative 120 min requiring full diversion, optimistic 20 min for minor debris). For each scenario, quantify the cascading impact on Gate G1 (T+6 h clearance) and Gate G2 (T+24 h Zone One clearance) attainment and document trigger points for contingency activation (e.g., if cumulative throughput delay exceeds 2 h by T+4 h, activate standby responder reserve).

9. Lacks Technical Depth

Does the plan omit critical technical details or engineering steps required to overcome foreseeable challenges, especially for complex components of the project?

Level: 🛑 High

Justification: Rated HIGH because the plan pre-authorizes a VEI-7 trigger that orders a 500 km evacuation affecting millions of people without confirmed second-stage shelter hubs, host-community MOUs, or interim destination lists prior to T+0. If the trigger fires during or immediately after Zone Zero evacuation (T+12–24 h range), evacuees will lack published shelter addresses, causing uncontrolled shadow evacuation of 50,000–200,000 outer-zone residents onto I-15, I-80 and I-90 that saturates the same corridors required for organized Zone Zero clearance. This cascades an estimated 4–8 hours of additional delay, stranding 5,000–20,000 evacuees in ashfall exposure zones. Interim hub list is a post-event deliverable (T+12 h), written plan is due Month 1 (2026-11-14), and signed host MOUs are due Month 2 (2026-12-14)—all blocking dependencies exist only after cascade effects begin.

Mitigation: Scenario Beta Secondary-Stage Destination Planner: By Month 1 (2026-11-14), execute a written Scenario Beta Secondary-Stage Evacuation Plan naming at least five ranked shelter hubs outside the 500 km ring (e.g., Denver, Cheyenne, candidate secondaries) with signed host-community MOUs confirming capacity and pre-positioning logistics. Validate distance from Yellowstone center to each hub and ashfall survivability under USGS ensemble forecast scenarios. Issue interim ranked hub list by T+12 hours; execute full multi-state Beta hub activation exercise by Month 3 (2027-01-14).

10. Assertions Without Evidence

Does each critical claim (excluding timeline and budget) include at least one verifiable piece of evidence?

Level: 🛑 High

Justification: Rated HIGH because the plan pre-authorizes a Scenario Beta 500 km evacuation order affecting millions of people without naming specific second-stage shelter hubs, confirming their distance outside the 500 km ring, obtaining signed host-community MOUs, or publishing an interim destination list prior to the 72-hour window. The interim hub list is due T+12 hours (post-event, during active evacuation), the written plan is due Month 1 (2026-11-14), and signed MOUs are due Month 2 (2026-12-14)—all blocking dependencies exist only after the trigger fires. Without executable destinations confirmed by T+0, a pre-authorized trigger is operationally reckless and creates cascade-failure risk.

Mitigation: Scenario Beta Secondary-Stage Destination Planner: By Month 1 (2026-11-14), execute a written Scenario Beta Secondary-Stage Evacuation Plan naming at least five ranked shelter hubs outside the 500 km ring with signed host-community MOUs confirming capacity, pre-positioning supplies, and 48-hour activation readiness. Validate distances from Yellowstone center and ashfall survivability under USGS ensemble forecasts by T+12 h (desktop check).

11. Unclear Deliverables

Are the project's final outputs or key milestones poorly defined, lacking specific criteria for completion, making success difficult to measure objectively?

Level: 🛑 High

Justification: Rated HIGH because major strategic deliverables (Scenario Beta Secondary-Stage Evacuation Plan, Responder Exposure Protocol, Ashfall Monitoring Relocation Protocols) are named but lack specific, measurable, verifiable acceptance criteria. Success metrics are absent: the Beta plan has no defined hub count, capacity threshold, or distance-from-ring criteria; responder protocol has no quantified relief depth or rotation timing; shelter relocation has no triggers or occupancy limits. These deliverables are critical for mitigating cascade risks (uncontrolled shadow evacuation, staff exhaustion, evacuees sheltered in heavy ash), yet their completion cannot be verified objectively. Absence of SMART criteria creates ambiguity about when readiness is achieved, preventing stakeholders from assessing whether the plan will actually execute.

Mitigation: Scenario Beta Secondary-Stage Destination Planner: By T+12 h, draft SMART acceptance criteria for all three unclear deliverables specifying measurable KPIs (e.g., Beta plan success = ≥5 hubs outside 500 km with signed MOUs and ≥250,000 confirmed beds); publish criteria to all stakeholders; track compliance monthly (Months 1-3, 2026-11-14 to 2027-01-14) against documented gates.

12. Gold Plating

Does the plan add unnecessary features, complexity, or cost beyond the core goal?

Level: 🛑 High

Justification: Rated HIGH because the Escorted-Return Program (Decision 10, option 3) adds USD 2–3 million in cost and diverts Guard and responder personnel from traffic control, logistics and shelter security during Phase 2 (T+6 to T+24 h), yet does not directly support the core project objectives of evacuating ≥98% of Zone Zero by T+6 h (Gate G1) or ≥95% of Zone One by T+24 h (Gate G2). The feature is Phase 3 (post-event re-entry) and is not binding under any legal or contractual requirement; anti-looting and perimeter security are managed via the fixed-checkpoint protocol (Decision 10, option 1). Responder hours consumed by escorted-return logistics directly compete with responder relief rotation needed to maintain 50%+ coverage at traffic-control checkpoints during peak evacuation (T+2 to T+8 h), where staffing is already at critical minimum. Mitigation is straightforward: eliminate the escorted-return program during Phases 1–2 and defer it to Phase 3 (post-ashfall) or cancel it entirely if responder depth remains inadequate.

Mitigation: Project Leadership: Conduct a Benefit Case Review within 7 days specifying: (1) whether escorted returns during Phase 2 (T+6 to T+24 h) are required by any state law, governor order, or legal precedent; (2) estimated responder hours diverted from traffic control, logistics or relief rotation; (3) quantified benefit (reduced looting incidents, resident complaints, post-event litigation risk) and assigned owner; (4) cost estimate including escort vehicles, drivers, request-processing staff and coordination overhead. If no binding requirement or demonstrated benefit justifies the cost during Phase 2, move escorted-return program to Phase 3 (post-ashfall, after ashfall onset is declared over) or cancel entirely; reallocate freed responder hours to traffic-control coverage and shelter-relocation support.

13. Staffing Fit & Rationale

Do the roles, capacity, and skills match the work, or is the plan under- or over-staffed?

Level: 🛑 High

Justification: Rated HIGH because the Ashfall Forecasting & Dynamic Shelter-Siting Officer is mission-critical (decision authority over real-time PM10 monitoring and 4-hour shelter relocation triggers) yet requires rare, combined expertise in volcanology, air-quality science, emergency operations, logistics, and real-time data systems. No single professional discipline typically carries all five competencies. Lead-time to recruit and integrate a qualified officer by T+0 is short; talent is concentrated in USGS and NOAA with limited availability.

Mitigation: FEMA Region VIII and UC Incident Commander: By T+0, identify and pre-authorize a named Ashfall Officer from USGS Volcano Disaster Assistance Program or a university volcanologist with ashfall-dispersion and emergency-operations experience. Execute a pre-event Interagency Agreement (IAA) granting the officer direct authority over PM10 sensor data, NOAA VAFT forecast integration, and relocation-trigger decisions. Confirm 24/7 availability and seat officer at forward element at T+0.

14. Legal Minefield

Does the plan involve activities with high legal, regulatory, or ethical exposure, such as potential lawsuits, corruption, illegal actions, or societal harm?

Level: ⚠️ Medium

Justification: Rated MEDIUM because legal pathways exist (Stafford Act, FEMA authority, FAA airspace procedures, state emergency powers, EMAC), but the plan lacks a regulatory matrix, fatal-flaw analysis, pre-event legal memoranda, signed MOUs with counsel review, or documented Stafford Act/FAA protocols. Controlling regimes: Stafford Act (42 U.S.C. § 5121), FAR Part 91 (airspace closure), State Emergency Management Acts, OSHA (respiratory protection), NIMS/ICS compliance. No unmapped showstoppers identified, but substantial documentation and pre-negotiation gaps remain.

Mitigation: FEMA Region VIII Legal Counsel and UC Incident Commander: By Month 1 (2026-11-14), execute a Fatal-Flaw Analysis reviewing Stafford Act emergency-declaration authority, FAA airspace-closure procedures, state governor activation requirements (MT, WY, ID statutes), and EMAC enforceability. Deliver a signed Regulatory Matrix (authority, artifact, lead time, predecessors) documenting Stafford Act declaration trigger, FAA NOTAM issuance protocol, governor pre-authorization letter template, and state mutual-aid legal enforceability. Obtain pre-event legal opinions on Scenario Beta trigger authority, Boundary Coordination Officer delegation validity, and government liability for unnecessary/unexecutable evacuation. Brief all state attorneys general and FAA counsel by Month 1 (2026-11-14).

15. Lacks Operational Sustainability

Even if the project is successfully completed, can it be sustained, maintained, and operated effectively over the long term without ongoing issues?

Level: 🛑 High

Justification: Rated HIGH because the plan prioritizes the 72-hour evacuation window (T+0 to T+72) but explicitly defers all post-event operations to "Phase 3 re-entry and recovery planning" with no defined funding, personnel, infrastructure maintenance, or long-term continuity mechanisms. Operational sustainability assessment reveals: (1) ongoing costs for responder reserves, equipment maintenance, and supply rotation through Month 60+ (estimated USD 2–5 million/year) lack annual appropriation authority; (2) specialized skills (USGS volcanology liaison, Guard signal operations, shelter management) required for sustained readiness have no retention or succession planning; (3) pre-positioned assets (sensors, tow equipment, generator fuel reserves) degrade without replacement cycles; (4) inter-agency MOUs expire unless renewed every 2 years; (5) no explicit plan for transitioning from emergency operations back to baseline readiness or for maintaining the forward UC element and Boundary Coordination Officer role beyond Month 3 (2027-01-14). The plan is designed as a 72-hour surge operation, not as a sustainable standby posture.

Mitigation: FEMA Region VIII and UC Director: Establish a Yellowstone Evacuation Readiness Sustainability Plan by Month 3 (2027-01-14) documenting: (1) annual operating budget (USD 2–5 million/year estimated) for asset maintenance, supply rotation, personnel retainer, and MOU renewal (every 2 years); (2) named sustainment owner (FEMA Region VIII Chief, or delegated permanent position) with 24/7 authority to activate the readiness posture if USGS eruption probability triggers above 10% in any 12-month window; (3) personnel succession and cross-training protocols for critical roles (USGS volcanologist liaison, Boundary Coordination Officer, Ashfall Forecasting Officer); (4) equipment lifecycle and replacement schedule (sensors every 3 years, tow assets every 5 years, generator fuel reserves refreshed annually); (5) annual tabletop exercise (Months 12, 24, 36 = 2027-10-14, 2028-10-14, 2029-10-14, etc.) to maintain multi-agency coordination and validate MOUs. Secure Congressional pre-appropriation authority for the annual sustainment budget by Month 6 (2027-04-14 + 3 months estimated) to avoid annual battle for funding and ensure continuity beyond Month 3 (2027-01-14).

16. Infeasible Constraints

Does the project depend on overcoming constraints that are practically insurmountable, such as obtaining permits that are almost certain to be denied?

Level: ⚠️ Medium

Justification: Rated MEDIUM because hard constraints (zoning, occupancy/egress, fire code, permits, structural limits) are acknowledged but treated as operational decisions (T+0 to T+6h shelter site selection) rather than pre-event validation tasks. Shelter sites Bozeman and Idaho Falls are named but no pre-event zoning confirmation, occupancy-permit application, or fire-egress compliance survey exists. Backup shelter sites are identified only as ranked upwind lists without structural-capacity or fire-code pre-surveying. Contraflow permits for temporary road closure/reversal are not documented as pre-authorized from state DOTs or NPS. If hard constraints are not cleared before T+0, shelter activation and relocation face 2–6 hour delays or site loss due to zoning/code violations. Viable alternatives exist (multiple candidate shelter locations, secondary routes), but feasibility is unvalidated.

Mitigation: Shelter Operations Coordinator (or designated Site Feasibility Lead): By Month 1 (2026-11-14), conduct a fatal-flaw screen with local planning and fire-marshal authorities at Bozeman, Idaho Falls, and each backup-site candidate. Obtain written confirmation that zoning permits emergency congregate shelter, occupancy is unbounded by code, fire egress meets or exceeds 35,000-person capacity, and temporary-use or emergency-occupancy permits can be expedited within 2 hours of activation request. Secure pre-signed occupancy authorizations from facility managers at Bozeman and Idaho Falls by Month 2 (2026-12-14). Define and document NO-GO thresholds: if zoning audit shows <2 sites (of Bozeman, Idaho Falls, third) are compliant, suspend shelter activation and activate Scenario Beta secondary-hub occupancy immediately. Coordinate with state DOTs (MT, WY, ID) to pre-authorize temporary contraflow permits and provide written delegation of activation authority to the UC by Month 1 (2026-11-14).

17. External Dependencies

Does the project depend on critical external factors, third parties, suppliers, or vendors that may fail, delay, or be unavailable when needed?

Level: ⚠️ Medium

Justification: Rated MEDIUM because the plan names pre-positioned tow and rockfall teams, forward water depots at Bozeman and Idaho Falls, Guard signal repeaters at control points, and fuel reserves at receiving hospitals as fallback assets, but lacks: (1) explicit single-point-of-failure analysis (e.g., what if Bozeman depot is ash-blocked and cannot resupply); (2) tested failover procedures (no documented exercise validating 4-hour water-resupply activation or tow-team diversion if primary supplier fails); (3) second-source vendor commitments for all critical supplies (water contracts from Salt Lake City only; no signed Pocatello/Butte backup pre-authorized for 6-hour dispatch). The plan specifies forward depots and Guard repeaters but does not confirm they are staged by T+12 h or that backup activation is pre-authorized. Regional utility grid resilience (transmission flashovers, cascading blackout) is identified as a risk but no load-shedding topology or substation pre-authorization exists to prevent it. Tested failover protocols for the three most critical single-point dependencies (water convoy, fuel delivery, communications) are absent.

Mitigation: Emergency Logistics and Supply-Chain Director and Critical Infrastructure Lead: (1) By Month 1 (2026-11-14), execute written pre-authorization agreements with Pocatello (Idaho) and Butte (Montana) water and fuel suppliers for 6-hour emergency dispatch at fixed surge rates, naming them as primary and secondary sources in the water and fuel contracts. (2) By T+12 h (depots stocked), stage 200,000–300,000 liters bottled water at Bozeman and Idaho Falls forward depots with confirmed tank capacity and resupply trigger (50% depletion = resupply order). (3) By Month 2 (2026-12-14), coordinate with Montana-Dakota Utilities, Pacific Power and Idaho Power to pre-authorize emergency transmission load-shedding and identify critical-path islands (hospitals, comms centers, shelters) that stay energized during regional blackout; test load-shedding topology at one substation. (4) By Month 3 (2027-01-14), execute a supply-chain failover exercise: simulate primary water-convoy delay, activate Pocatello backup within 6 hours, and validate secondary delivery timing to shelters.

18. Stakeholder Misalignment

Are there conflicting interests, misaligned incentives, or lack of genuine commitment from key stakeholders that could derail the project?

Level: ⚠️ Medium

Justification: Rated MEDIUM because two key stakeholder groups hold conflicting incentives that are unaddressed: (1) FEMA and governors are incentivized to authorize pre-positioned spending (USD 47.5–87 million estimate readiness package) now, accepting cascade-failure risk if Scenario Beta destinations fail; (2) host communities (Denver, Cheyenne, secondary hubs) are incentivized to minimize cost-share and pre-positioning commitments, preferring post-event federal coverage, creating latency if Beta triggers before MOUs are signed. The plan acknowledges the NPS-to-state authority handoff but does not resolve the underlying tension: federal speed (pre-authorize Scenario Beta immediately) versus state burden (absorb unquantified evacuees and costs). No shared OKR aligns both sides on a measurable success metric that balances evacuation speed against financial equity.

Mitigation: Unified Command Director: Within 14 days, convene a tri-party workshop (FEMA, governors MT/WY/ID, host emergency managers) to draft a signed Interagency Success Agreement specifying one shared OKR: "Evacuate 98% of 35,800 Zone Zero by T+6 h and 95% of Zone One by T+24 h with zero unplaced Scenario Beta evacuees if trigger fires before Month 2 (2026-12-14)." Embed cost-share tiers (federal covers pre-positioning; states match 10–20% ongoing costs) and tie federal reimbursement to on-time MOU signature and hub activation readiness by Month 1 (2026-11-14). Monthly scorecards track progress against the OKR; bonded incentives reward early MOU completion.

19. No Adaptive Framework

Does the plan lack a clear process for monitoring progress and managing changes, treating the initial plan as final?

Level: 🛑 High

Justification: Rated HIGH because the plan pre-authorizes a Scenario Beta VEI-7 trigger and names critical Phase 1 and Phase 2 gates (G1 T+6 h ≥98%, G2 T+24 h ≥95%) but provides no standing feedback loop: no KPI dashboard, no hourly review cadence, no named change-control decision owners, and no re-plan/stop thresholds that automatically trigger corrective authority. The Unified Command exists as a structure but no formal review schedule, escalation protocol, or real-time monitoring rules exist to detect when gates slip (e.g., if Gate G1 clearance falls to 95% by T+5 h) and execute corrective responses within the decision window. The plan states "hourly updates" for ashfall but does not define who owns the update decision, what measurement triggers a relocation order, or what authority can halt a phase if conditions diverge. This gap is critical because the three most time-sensitive decisions (Scenario Beta trigger at T+12–24 h, shelter relocation within 4 h of ashfall exceedance, loss-of-exit rule at 45 min blockage) depend on real-time feedback and pre-authorized decision authority that the plan does not document.

Mitigation: Unified Command Director: Establish and publish a Feedback Loop and Change-Control Framework within 7 days, specifying: (1) KPI Dashboard updated hourly from T+0 to T+72 h tracking Gate G1 (exit counts vs. 98%), Gate G2 (Zone One vs. 95%), shelter intake vs. 5,000 person/h, convoy status vs. delivery targets; (2) Standing review cadence at T+0, T+6, T+12, T+18, T+24, T+36, T+48, T+60, T+72 h with named UC officers, state commanders, Boundary Coordinator and Ashfall Officer; (3) Pre-authorized change-control thresholds: blockage >45 min triggers diversion (Boundary Officer authority), Gate G1 <95% by T+5 h triggers escalation (G1 stays fixed at T+6 h), PM10 above 50 ug/m3 triggers forecast update, above 100 ug/m3 triggers shelter-suitability review, and a failed review or PM10 above 200 ug/m3 (proposed threshold) triggers relocation order within 4 h (Ashfall Officer authority), free contingency <USD 20M (proposed threshold) triggers spending freeze; (4) Re-plan and stop rules: re-plan if evacuation delay >2 h by T+8 h or responder coverage <50% for >60 min; stop if three convoys delayed >6 h or shelters reach <24 h reserves at T+18 h.

20. Uncategorized Red Flags

Are there any other significant risks or major issues that are not covered by other items in this checklist but still threaten the project's viability?

Level: 🛑 High

Justification: Rated HIGH because the plan pre-authorizes a Scenario Beta 500 km evacuation order affecting millions of people without confirmed second-stage shelter hubs, host-community MOUs, or interim destination lists prior to T+0. If the trigger fires during Zone Zero or Zone One evacuation (T+12–24 h range), outer-zone residents will lack published shelter addresses, triggering uncontrolled shadow evacuation of 50,000–200,000+ people onto I-15, I-80 and I-90 that saturates the same corridors needed for organized Zone Zero clearance. This cascade couples with three additional high-risk nodes: (1) responder staffing exhaustion—all 67–100 concurrent positions consumed during T+2–T+8 h peak, zero relief depth, so a single traffic incident halts one corridor 2–4 hours, stranding 500–2,000 vehicles in ash; (2) ashfall forecast error—shelter sites chosen at T+6 h using a forecast with ±50 km uncertainty, so if actual ashfall diverges, 10,000–15,000 evacuees are sheltered in heavy ash, with a relocation order due within 4 hours of exceedance and move/occupy taking up to 8 hours (infeasible without pre-staged buses); (3) water convoy delay—realistic arrival T+18–30 h versus target T+24 h, forcing 18–24 hour water rationing at shelters. These four risks are tightly coupled: Beta trigger → shadow evacuation → corridor congestion → responder fatigue failure → stranded vehicles in ashfall overlap. The plan lacks a bow-tie or interdependency map showing these failure modes and no NO-GO thresholds exist to halt escalation if conditions diverge.

Mitigation: Owner: Unified Command Director. Deliverable: Execute an Interdependency Map and Bow-Tie/FTA Analysis by Month 1 (2026-11-14) identifying four primary failure cascades: (1) Scenario Beta trigger → uncontrolled shadow evacuation → corridor saturation → Zone Zero delay; (2) responder staffing gap → coverage failure at one checkpoint → blockage halt → cascading delay; (3) ashfall forecast error → shelter in heavy ash → relocation impossible → 4–8 hour evacuation delay; (4) water convoy delay → shelter rationing → secondary health crisis → hospital overflow. For each cascade, define NO-GO thresholds triggering plan halt or re-escalation: e.g., if fewer than 5 hubs are validated and signed by Month 2 (2026-12-14), suspend automatic Scenario Beta; if responder coverage <50% for >60 min, activate standby reserve; if blockage persists >45 min, execute loss-of-exit rule; if PM10 exceeds 200 ug/m3 (proposed threshold) or a suitability review fails, order relocation within 4 h. Include a combined heatmap showing coupling strength (high/medium/low) and interdependency criticality. Assign owners to each threshold trigger (Boundary Officer, Ashfall Officer, Logistics Director, Command) with pre-authorized authority to execute mitigation within the decision window. Conduct a tabletop exercise testing all four cascades by Month 3 (2027-01-14).

Part 3: Audit trail

What was checked, and how.

Check Method Covers Result
Against sources Web search Sections that searched: Premise Attack (11) 11 searches. Other real-world figures (prices, costs, market sizes, laws, precedents) were not verified.
Canonical facts Reconciled, then the table's own arithmetic re-checked 46 key numbers and dates 7 from your prompt, 11 decisions, 16 proposed thresholds, 12 estimates.
Internal consistency Lint against the canonical facts, then repair and re-lint Executive Summary, Pitch, Premortem, Project Plan, Review Plan, Self Audit and the assumptions (summary version) Before repair: 2 high / 7 medium. After: 1 high / 4 medium, plus 5 needing a decision (see Decisions Required).
Arithmetic Deterministic re-computation Every written calculation ("a x b = c") in 20 sections 13 checked, 0 wrong.
Calendar Deterministic Every "Month N" paired with a date Dates recomputed from the plan start (Month 0).
Schedule Deterministic Gantt and WBS Computed from the estimated durations and dependencies.

By section

Section Checks applied
Decisions Required derived from the consistency check
Canonical Facts reconciled across documents; own arithmetic re-checked; arithmetic (13 calculations, 0 wrong)
Executive Summary consistency lint and repair
Pitch consistency lint and repair
Project Plan consistency lint and repair
Strategic Decisions none
Scenarios none
Assumptions none
Governance none
Related Resources none
Data Collection none
Documents to Create and Find none
SWOT Analysis none
Team none
Expert Criticism none
Review Plan consistency lint and repair
Questions & Answers none
Premortem consistency lint and repair
Self Audit consistency lint and repair
Premise Attack web search (11 searches)

Contradictions between the core documents, after repair.

Consistency: first pass found 2 high / 7 medium / 0 low contradictions. Repair: round 1: 58 edits → 3 high / 6 medium; round 2: 36 edits → 2 high / 6 medium; round 3: 42 edits → 1 high / 4 medium. Published: round 3 (fewest high-severity issues). Shown below: the final check of the repaired documents (1 high / 4 medium / 2 low).

1. Scenario Beta described as pre-authorized and executable, but hubs, MOUs and the no-go gate close after the 72 h window (🔴 High) — needs a project decision

2. Hub count and capacity thresholds are not reconcilable with each other or with the ring population (🔴 High) — needs a project decision

3. "Pre-authorized" orders versus authority and trigger values that exist only at T+3 h and T+6 h (🔴 High) — needs a project decision

4. Pre-event validation and go/no-go inputs dated at or before T+0, or after the window (🔴 High)

5. Date, owner and content of the federal vs state/local/host cost-share decision (🟡 Medium) — needs a project decision

6. Zone One shelter and water demand is unplanned while Gate G2 depends on the unquantified count (🟡 Medium) — needs a project decision

7. Standby reserve, tow teams and key officers seated after the peak they cover (🟡 Medium)

8. Contract, depot and water timing disagree between documents (🟡 Medium)

9. USD 200 million treated as pre-event investment and as an appropriation to secure at Month 0 (🟡 Medium)

10. Signed hub MOUs attached to the Month 1 written plan (🟡 Medium)

11. Hospital generator fuel stated as existing, as a task, and as a 24 h floor (⚪ Low)

12. East exit throughput threshold below its load-split requirement (⚪ Low)

Summary

The plan is much more consistent than before. The Zone Zero numbers (35,800; G1 98% / about 35,084; G2 95%), the gate load split and throughput, the readiness-package arithmetic (47.5-87 million), the contingency treatment, the pitch trigger window and the water arrival range are now aligned with the canonical facts. The remaining problems are structural. The plan treats the 72 h window as the event but dates most of its validation, financing and commitment items before T+0 or after T+72 h, so Scenario Beta is called "pre-authorized" and "executable" while its authority, hubs, capacity and funding do not exist inside the window. Two decisions are still missing: what the UC does if Beta fires before the hubs are signed, and who finances shelters and hubs. The other remaining items are timing and threshold mismatches between documents that can be repaired by text edits.

How the canonical facts were reconciled

The cost chain double-counted Scenario Beta hub pre-positioning (USD 20-40 million) in both the readiness package and the contingency fallback; it now sits only in the base package, the contingency carries the USD 5-10 million relocation draw, and a free-contingency fact (USD 30-35 million) was added. The water target was sized to 25,000 occupants while shelter capacity totals 35,800; it was recomputed to about 1.43 million L, and the readiness low end was corrected from 48 to 47.5 million. The unsourced 12,000 Zone One population figure was removed (census still open), and per-gate vehicle rates were added to the 50/30/20 split since the even-split throughput understates the West gate. Other arithmetic (35,084/716 gate, 11,933 vehicles, 10,800 third site, 67-100 positions, 40/200 = 20%) was rechecked and left unchanged.

Initial Prompt

Plan:
**Context & Scenario**
Create a comprehensive strategic response plan for a "Red Warning" volcanic event at the Yellowstone Caldera. USGS sensors have confirmed rapid, unprecedented ground uplift (>20cm in 6 hours) at the Norris Geyser Basin and significant seismic swarm activity (Mag 4.5+ tremors) indicating magma ascension to shallow depths. A phreatic (steam) explosion has already compromised a section of the Grand Loop Road. A VEI-6 or higher eruption is modeled as "Scenario Alpha" with a 40% probability within the next 72 hours.

**Core Mission**
The primary objective is the preservation of life through the immediate evacuation of the "Zone Zero" (Park Interior) and "Zone One" (100km radius), followed by continuity of operations for regional infrastructure under heavy ashfall conditions.

**Detailed Requirements & Constraints**

1. **Phase 1: Zero-Hour Evacuation (T+0 to T+6 Hours)**
* **Target:** Evacuate approximately 35,000 tourists and 800 park staff from inside the park boundaries.
* **Constraint:** The South Entrance road (US-89/191/287) is blocked by a landslide triggered by tremors. Traffic must be rerouted north and west.
* **Action:** Detail the traffic control plan using "contraflow" (using all lanes for outbound traffic) on US-191 and US-20 towards West Yellowstone and US-89 towards Gardiner.
* **Assets:** Deploy National Park Service LE Rangers and request immediate Wyoming Highway Patrol assistance to clear bottlenecks.

2. **Phase 2: The Kill Zone & Ashfall (T+6 to T+24 Hours)**
* **Scope:** Expand evacuation to "Zone One" communities including West Yellowstone (MT), Gardiner (MT), and Cody (WY).
* **Aviation:** Immediate indefinite grounding of all commercial and private aviation in FAA sectors ZLC (Salt Lake) and ZSE (Seattle) due to silicate ash ingestion risks.
* **Shelter:** Establish mass casualty and refugee intake centers at safe distances: Boseman, MT (Field Report) and Idaho Falls, ID (Bonneville HS).

3. **Command & Control (C2)**
* **Structure:** Establish a Unified Command (UC) at the FEMA Region VIII Regional Response Coordination Center (RRCC) in Denver.
* **Jurisdiction:** Explicitly define the transfer of authority from NPS (Federal Land) to State Governors once evacuees cross park boundaries to avoid "turf wars."
* **Comms:** Plan for the failure of local cell towers due to ash/tremors. Activation of FEMA IPAWS for emergency broadcasting and deployment of National Guard signal corps for comms bridging.

4. **Logistics & Life Support**
* **Water:** Ashfall will contaminate open reservoirs. Mobilize bottled water convoys from Salt Lake City within 12 hours.
* **Medical:** Pre-stage respiratory protection (N95 minimum) for 100,000 people. Prepare for mass respiratory distress cases at regional hospitals.
* **Security:** Deploy National Guard to enforce the exclusion zone perimeter and prevent looting in evacuated towns.

5. **Contingencies (The "What Ifs")**
* **Scenario Beta:** If the eruption escalates to VEI-7 (Supereruption), the evacuation zone must expand to 500km immediately. Include a trigger point for this decision.
* **Grid Failure:** Plan for widespread power outages caused by ash-induced flashovers on transmission lines. Prioritize generator fuel for hospitals and comms centers.

**Output Format**
Please provide the plan with an Executive Summary, a Phased Gantt Chart (hourly for the first 24h), a Risk Register focusing on logistical bottlenecks, and a Resource Allocation Matrix. Avoid generic advice; be specific about routes (US-191, I-90), towns, and agencies (USGS, FEMA, NPS).

Today's date:
2026-Oct-14

Project start ASAP

Prompt Screening

Verdict: 🟢 USABLE

Rationale: The prompt describes a concrete emergency response planning project for a Yellowstone volcanic event, with specific phases, routes, agencies, locations, and deliverables. Although the scenario is hypothetical, it is set in real places with real agencies and can be planned around.

Redline Gate

Verdict: 🟢 ALLOW

Rationale: The prompt requests a defensive emergency evacuation and disaster response plan for a volcanic event, which is protective, standard public-safety planning with no meaningful capability uplift for harm.

Violation Details

Detail Value
Capability Uplift No

Premise Attack

Why this fails.

Premise Attack 1 — Integrity

Forensic audit of foundational soundness across axes.

[STRATEGIC] A 24-hour, radius-based evacuation plan keyed to an invented "40% in 72 hours" VEI-6 probability treats a wind-driven, multi-state, months-long ash disaster as a 100 km circle that can be emptied in a day, so the document would project precision that the hazard, the road network and the agencies cannot supply.

Bottom Line: REJECT: A single-day, circle-based evacuation and continuity plan built on an invented eruption probability, with shelters and supply depots that fall inside its own worst case, should not be written as an operational plan.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 2 — Accountability

Rights, oversight, jurisdiction-shopping, enforceability.

[STRATEGIC] — Counterfeit Countdown: the plan is built on a "40% within 72 hours" VEI-6 clock that no volcano observatory can issue, so every hour-by-hour task, contraflow lane and shelter assignment is choreography for a forecast that does not exist.

Bottom Line: REJECT: This plan is a Counterfeit Countdown, a detailed machine for acting on a probability that no scientist can honestly provide and a command structure that does not match the map. A premise that begins with an invented clock should not exist.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 3 — Spectrum

Enforced breadth: distinct reasons across ethical/feasibility/governance/societal axes.

[STRATEGIC] A six-hour, road-bound evacuation of 35,000 people through a blocked, two-lane network is fantasy dressed as doctrine, and its own safe havens sit inside its worst-case zone.

Bottom Line: REJECT: A plan that promises to empty a caldera in six hours down two-lane roads and shelters its evacuees inside its own 500 km kill radius must not be adopted.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 4 — Cascade

Tracks second/third-order effects and copycat propagation.

The plan treats a supereruption as a schedulable, circular, road-evacuable event with a known 72-hour clock, when the physics, the road network, and the jurisdictional map make that assumption false. It is a compliance document for a disaster that does not behave the way the document requires.

Bottom Line: Reject the premise of an evacuation plan driven by a short, probabilistic eruption clock, a circular zone and flipped lanes on two-lane roads. The flaw is the premise itself: it assumes certainty, road capacity and unified authority that do not exist, so no amount of Gantt-chart detail will fix it.

Reasons for Rejection

Second-Order Effects

Evidence

Premise Attack 5 — Escalation

Narrative of worsening failure from cracks → amplification → reckoning.

[STRATEGIC] — The Scripted Apocalypse Fallacy: the plan stakes 35,000 lives on a precisely timed hourly choreography for an event whose precursors, probabilities and hazard footprint no scientific body can state with the confidence the script assumes, so it would manufacture false certainty and send crowds down two-lane mountain roads on a schedule the volcano never agreed to.

Bottom Line: REJECT: A choreographed, hour-by-hour, probability-stamped evacuation of a caldera is a fantasy of control that would convert uncertainty into false confidence and a bottleneck into a death trap; the gate is closed.

Reasons for Rejection

Second-Order Effects

Evidence

Overall Adherence: 88%

IMPORTANCE_ADHERENCE_SUM = (5×5 + 5×5 + 5×4 + 5×4 + 4×5 + 5×3 + 4×5 + 4×5 + 4×4 + 4×4 + 4×4 + 4×5 + 3×4 + 5×5 + 5×4) = 290
IMPORTANCE_SUM = 5 + 5 + 5 + 5 + 4 + 5 + 4 + 4 + 4 + 4 + 4 + 4 + 3 + 5 + 5 = 66
OVERALL_ADHERENCE = IMPORTANCE_ADHERENCE_SUM / (IMPORTANCE_SUM × 5) = 290 / 330 = 88%

Summary

ID Directive Type Importance Adherence Category
1 Decision window: 72 hours (T+0 to T+72, Month 0 = 2026-10-14). Scenario Alpha VEI-6+ probability 40% within this window. Plan must address immediate actions (T+0 to T+12 h) and Months 1–3 (2026-11-14 to 2027-01-14) hardening. Constraint 5/5 5/5 Fully honored
2 Phase 1: Evacuate Zone Zero (park interior) — approximately 35,800 people (35,000 tourists + 800 staff) — within T+6 hours via three open corridors (West, North, East). South Entrance written off; one time-boxed 4-hour clearance attempt only. Requirement 5/5 5/5 Fully honored
3 Phase 2: Evacuate Zone One (100 km radius incl. West Yellowstone, Gardiner, Cody) by T+24 hours. Establish shelters at Bozeman (15,000 cap) and Idaho Falls (10,000 cap); third site selected at T+6 h based on NOAA/USGS plume forecast. Requirement 5/5 4/5 Partially honored
4 Command structure: Unified Command at FEMA Region VIII RRCC Denver from T+0. Authority transfers from NPS to state governors at park boundaries (West, North, East gates). Signed MOUs and EMAC by Month 1 (2026-11-14). Requirement 5/5 4/5 Partially honored
5 Contraflow on US-191, US-20, US-89 active by T+1 hour. Gate load split: West 50% (17,900), North 30% (10,740), East 20% (7,160). Blockage >45 min triggers diversion to nearest exit. Constraint 4/5 5/5 Fully honored
6 Scenario Beta trigger (VEI-7 escalation): Pre-authorized written USGS trigger matrix. If triggered, UC issues 500 km evacuation order within 30 min without further approval. Execute in rings: 0–100 km organized; 100–250 km time-banded; 250–500 km staged. Requirement 5/5 3/5 Partially honored
7 Aviation: Indefinite grounding of commercial and private aviation in FAA sectors ZLC (Salt Lake) and ZSE (Seattle). Narrow government rotary-wing medevac/survey exceptions only. Requirement 4/5 5/5 Fully honored
8 Pre-stage 100,000 N95 respirators (minimum) for civilians. Deploy supplemental 100,000-unit reserve at Billings or Salt Lake City. Responder N95s sized separately, not drawn from civilian stock. Requirement 4/5 5/5 Fully honored
9 Water: Mobilize bottled-water convoys from Salt Lake City by T+12 h. Arrival target T+24 h via forward depots. Minimum 1.43 million liters for 10 days at 35,800 shelter occupants (4 L/person/day). Requirement 4/5 4/5 Partially honored
10 Communications: IPAWS/WEA/NOAA Weather Radio primary. Guard signal teams with satellite phones and repeaters at each control point and forward element from T+0. HAR/VMS on US-191, US-20, US-89, I-90. Route cards in English plus 5 languages. Requirement 4/5 4/5 Partially honored
11 Power/fuel: Plan for widespread ash-induced grid failure. Prioritize generator fuel for hospitals, comms centers, shelter kitchens. 72-hour reserves at three receiving hospitals (Bozeman, Livingston, Idaho Falls). Requirement 4/5 4/5 Partially honored
12 Budget envelope: USD 200 million planning envelope (estimate USD 150–250 million) = USD 160 million base + USD 40 million contingency (20%). Readiness package USD 47.5–87 million. Financing source (federal vs. state/local) for shelters and secondary hubs is open decision. Constraint 4/5 5/5 Fully honored
13 Responder logistics: 100–150 NPS rangers (1.5 relief ratio ~67–100 concurrent). Max 6 h shift at ash-exposed posts + 2 h rest with N95 replacement; full withdrawal after 18 consecutive hours. Deploy 30–50 out-of-region reserves within 4 h if needed. Requirement 3/5 4/5 Partially honored
14 Current state (T+0): USGS confirms rapid ground uplift >20 cm in 6 h at Norris Geyser Basin. Seismic swarm (Mag 4.5+ tremors) indicates magma ascension. Phreatic explosion already compromised Grand Loop Road section. Stated fact 5/5 5/5 Fully honored
15 Preserve life is the primary objective. Execute the response plan immediately; this is not a feasibility study. Output must include Executive Summary, phased Gantt (hourly for first 24 h), Risk Register, and Resource Allocation Matrix with specific routes, towns, and agencies. Intent 5/5 4/5 Partially honored

Issues

Issue 6 - Scenario Beta trigger (VEI-7 escalation): Pre-authorized written USGS trigger matrix. If triggered, UC issues 500 km evacuation order within 30 min without further approval. Execute in rings: 0–100 km organized; 100–250 km time-banded; 250–500 km staged.

Issue 3 - Phase 2: Evacuate Zone One (100 km radius incl. West Yellowstone, Gardiner, Cody) by T+24 hours. Establish shelters at Bozeman (15,000 cap) and Idaho Falls (10,000 cap); third site selected at T+6 h based on NOAA/USGS plume forecast.

Issue 4 - Command structure: Unified Command at FEMA Region VIII RRCC Denver from T+0. Authority transfers from NPS to state governors at park boundaries (West, North, East gates). Signed MOUs and EMAC by Month 1 (2026-11-14).

Issue 15 - Preserve life is the primary objective. Execute the response plan immediately; this is not a feasibility study. Output must include Executive Summary, phased Gantt (hourly for first 24 h), Risk Register, and Resource Allocation Matrix with specific routes, towns, and agencies.

Issue 9 - Water: Mobilize bottled-water convoys from Salt Lake City by T+12 h. Arrival target T+24 h via forward depots. Minimum 1.43 million liters for 10 days at 35,800 shelter occupants (4 L/person/day).

Issue 10 - Communications: IPAWS/WEA/NOAA Weather Radio primary. Guard signal teams with satellite phones and repeaters at each control point and forward element from T+0. HAR/VMS on US-191, US-20, US-89, I-90. Route cards in English plus 5 languages.

Issue 11 - Power/fuel: Plan for widespread ash-induced grid failure. Prioritize generator fuel for hospitals, comms centers, shelter kitchens. 72-hour reserves at three receiving hospitals (Bozeman, Livingston, Idaho Falls).

Issue 13 - Responder logistics: 100–150 NPS rangers (1.5 relief ratio ~67–100 concurrent). Max 6 h shift at ash-exposed posts + 2 h rest with N95 replacement; full withdrawal after 18 consecutive hours. Deploy 30–50 out-of-region reserves within 4 h if needed.

Which generator version and models produced each part.

Generator

Stages

Stage Generated at Generator Models LLM calls
screen_planning_prompt 2026-10-14T21:21:08 v2.0.6 claude-sonnet-5-5 1
setup 2026-10-14T21:21:03 v2.0.6 - 0
extract_constraints 2026-10-14T21:21:16 v2.0.6 claude-sonnet-5-5 1
identify_purpose 2026-10-14T21:21:09 v2.0.6 claude-sonnet-5-5 1
premise_attack 2026-10-14T21:22:41 v2.0.6 claude-sonnet-5-5 5
redline_gate 2026-10-14T21:21:13 v2.0.6 claude-sonnet-5-5 1
classify_domain 2026-10-14T21:22:36 v2.0.6 claude-sonnet-5-5 4
plan_type 2026-10-14T21:22:41 v2.0.6 claude-sonnet-5-5 1
potential_levers 2026-10-14T21:27:00 v2.0.6 claude-sonnet-5-5 22
potential_levers_constraint 2026-10-14T21:27:31 v2.0.6 claude-sonnet-5-5 1
triage_levers 2026-10-14T21:27:24 v2.0.6 claude-sonnet-5-5 1
enrich_levers 2026-10-14T21:27:44 v2.0.6 claude-sonnet-5-5 3
triaged_levers_constraint 2026-10-14T21:27:57 v2.0.6 claude-sonnet-5-5 1
enriched_levers_constraint 2026-10-14T21:28:21 v2.0.6 claude-sonnet-5-5 1
focus_on_vital_few_levers 2026-10-14T21:28:05 v2.0.6 claude-sonnet-5-5 1
candidate_scenarios 2026-10-14T21:28:55 v2.0.6 claude-sonnet-5-5 1
strategic_decisions_markdown 2026-10-14T21:28:05 v2.0.6 - 0
vital_few_levers_constraint 2026-10-14T21:28:39 v2.0.6 claude-sonnet-5-5 1
candidate_scenarios_constraint 2026-10-14T21:29:35 v2.0.6 claude-sonnet-5-5 1
select_scenario 2026-10-14T21:29:18 v2.0.6 claude-sonnet-5-5 1
scenarios_markdown 2026-10-14T21:29:18 v2.0.6 - 0
selected_scenario_constraint 2026-10-14T21:29:45 v2.0.6 claude-sonnet-5-5 1
physical_locations 2026-10-14T21:29:30 v2.0.6 claude-sonnet-5-5 1
currency_strategy 2026-10-14T21:29:40 v2.0.6 claude-haiku-4-5-20251001 1
identify_risks 2026-10-14T21:31:41 v2.0.6 claude-haiku-4-5-20251001 1
make_assumptions 2026-10-14T21:32:04 v2.0.6 claude-sonnet-5-5 1
distill_assumptions 2026-10-14T21:32:12 v2.0.6 claude-sonnet-5-5 1
review_assumptions 2026-10-14T21:33:33 v2.0.6 claude-haiku-4-5-20251001 1
consolidate_assumptions_markdown 2026-10-14T21:35:47 v2.0.6 claude-haiku-4-5-20251001 9
pre_project_assessment 2026-10-14T21:37:31 v2.0.6 claude-haiku-4-5-20251001 1
canonical_facts 2026-10-14T21:41:20 v2.0.6 claude-sonnet-5-5 2
project_plan 2026-10-14T21:41:52 v2.0.6 claude-sonnet-5-5 1
create_wbs_level1 2026-10-14T21:41:56 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase1_audit 2026-10-14T21:42:26 v2.0.6 claude-haiku-4-5-20251001 1
related_resources 2026-10-14T21:42:18 v2.0.6 claude-sonnet-5-5 1
find_team_members 2026-10-14T21:43:05 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase2_bodies 2026-10-14T21:44:21 v2.0.6 claude-haiku-4-5-20251001 1
swot_analysis 2026-10-14T21:42:41 v2.0.6 claude-sonnet-5-5 1
enrich_team_members_with_contract_type 2026-10-14T21:43:24 v2.0.6 claude-haiku-4-5-20251001 1
expert_review 2026-10-14T21:47:31 v2.0.6 claude-haiku-4-5-20251001 10
governance_phase3_impl_plan 2026-10-14T21:48:59 v2.0.6 claude-haiku-4-5-20251001 1
enrich_team_members_with_background_story 2026-10-14T21:44:26 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase4_decision_escalation_matrix 2026-10-14T21:49:36 v2.0.6 claude-haiku-4-5-20251001 1
enrich_team_members_with_environment_info 2026-10-14T21:46:52 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase5_monitoring_progress 2026-10-14T21:50:53 v2.0.6 claude-haiku-4-5-20251001 1
governance_phase6_extra 2026-10-14T21:51:45 v2.0.6 claude-haiku-4-5-20251001 1
review_team 2026-10-14T21:48:38 v2.0.6 claude-haiku-4-5-20251001 1
consolidate_governance 2026-10-14T21:51:45 v2.0.6 - 0
team_markdown 2026-10-14T21:48:38 v2.0.6 - 0
data_collection 2026-10-14T21:54:08 v2.0.6 claude-haiku-4-5-20251001 1
identify_documents 2026-10-14T21:55:58 v2.0.6 claude-haiku-4-5-20251001 1
create_wbs_level2 2026-10-14T21:54:44 v2.0.6 claude-haiku-4-5-20251001 1
filter_documents_to_create 2026-10-14T21:56:57 v2.0.6 claude-sonnet-5-5 1
filter_documents_to_find 2026-10-14T21:58:05 v2.0.6 claude-haiku-4-5-20251001 1
draft_documents_to_create 2026-10-14T21:58:56 v2.0.6 claude-haiku-4-5-20251001 5
draft_documents_to_find 2026-10-14T22:02:17 v2.0.6 claude-haiku-4-5-20251001 13
identify_task_dependencies 2026-10-14T21:55:14 v2.0.6 claude-haiku-4-5-20251001 1
wbs_project_level1_and_level2 2026-10-14T21:54:44 v2.0.6 - 0
create_pitch 2026-10-14T21:55:13 v2.0.6 claude-haiku-4-5-20251001 1
estimate_task_durations 2026-10-14T21:56:34 v2.0.6 claude-haiku-4-5-20251001 18
markdown_with_documents_to_create_and_find 2026-10-14T22:02:17 v2.0.6 - 0
convert_pitch_to_markdown 2026-10-14T21:56:21 v2.0.6 claude-haiku-4-5-20251001 1
create_wbs_level3 2026-10-14T22:03:22 v2.0.6 claude-haiku-4-5-20251001 45
wbs_project_level1_and_level2_and_level3 2026-10-14T22:03:22 v2.0.6 - 0
create_schedule 2026-10-14T22:03:22 v2.0.6 - 0
review_plan 2026-10-14T22:08:03 v2.0.6 claude-haiku-4-5-20251001 16
executive_summary 2026-10-14T22:08:28 v2.0.6 claude-haiku-4-5-20251001 1
questions_and_answers 2026-10-14T22:10:07 v2.0.6 claude-haiku-4-5-20251001 2
premortem 2026-10-14T22:11:14 v2.0.6 claude-sonnet-5-5 3
prompt_adherence 2026-10-14T22:09:23 v2.0.6 claude-haiku-4-5-20251001 2
self_audit 2026-10-14T22:17:47 v2.0.6 claude-haiku-4-5-20251001 20
consistency_review 2026-10-14T22:20:00 v2.0.6 claude-sonnet-5-5 1
consistency_repair 2026-10-14T22:31:17 v2.0.6 claude-sonnet-5-5 17
decision_register 2026-10-14T22:31:42 v2.0.6 claude-sonnet-5-5 1
arithmetic_check 2026-10-14T22:31:42 v2.0.6 - 0