emergency-management-continuity-method

# Emergency Management and Continuity Method ## Freeze scope and authority Record organization, jurisdiction, facilities/populations, approved Emergency Operations Plan and continuity-plan versions, planning horizon, evidence cutoff, Authority Having Jurisdiction, accountable owners, data classification and explicit non-live status. Assign stable scenario, assumption, function, dependency, resource, message, exercise, observation, action and decision IDs. ## Build scenarios and continuity evidence 1. Define dated all-hazards scenarios by initiating condition, footprint, duration, warning time, affected populations, impact dimensions and uncertainty in [the hazard register](assets/hazard-impact-planning-assumption-register.md). Scenarios are planning inputs, not forecasts. 2. Map each essential function to minimum service, disruption impact, maximum tolerable disruption, Recovery Time Objective, Recovery Point Objective, staff/facility/system/data/record/supplier dependencies and shared failure domains in [the BIA register](assets/essential-function-dependency-bia-register.md). 3. Test objective feasibility against dependency evidence. Record succession, delegations, alternate facilities, remote/manual work, communications, essential records, devolution and reconstitution in [the strategy plan](assets/continuity-strategy-recovery-objective-plan.md). ## Map coordination and improvement 1. Trace approved Incident Command System, Emergency Operations Center, Multiagency Coordination and Joint Information System interfaces; resource typing/inventory; mutual aid; ordering-to-demobilization; and accessible multilingual communications in [the coordination matrix](assets/incident-resource-communications-coordination-matrix.md). 2. Trace exercise objective → observable task → criterion → evidence → finding → corrective action → owner/due date → retest in [the improvement register](assets/exercise-aar-improvement-action-register.md). 3. Keep approved plan statements, planning assumptions, exercise observations, analyst findings and authorized decisions separate. ## Test cross-branch feasibility Build a dependency chain from each scenario impact to an essential function, its minimum service, the time objective, the enabling people/facility/technology/information/supplier dependencies, and the documented continuity strategy. For every claimed strategy, test whether its activation prerequisite, capacity, duration, accessibility, communications path and restoration handoff are supported by dated evidence. Link resource needs to an approved type or local specification, quantity and unit, readiness timestamp, ordering authority, sourcing route, lead time, staging constraint and demobilization owner. Do not count an unverified memorandum, contact, roster, alternate site or supplier as available capacity. Cross-check exercise observations against the exact objective, capability target and evaluation record. An improvement action is not closed merely because its due date passed or a document changed: require owner disposition, completion evidence, effect on the relevant plan version and a retest or other authorized verification. At the join, preserve scenario-to-function-to-resource-to-action traceability, expose shared dependencies and single points of failure, and distinguish evidence currency from professional readiness judgment. If time objectives conflict with resource lead times, communications accessibility is untested, or a corrective action changes an approved plan, record a qualified-review decision instead of silently selecting a preferred answer. ## Authority and stop boundary Never forecast an incident; declare or activate; issue evacuation, shelter, warning or life-safety advice; command, dispatch, credential or order resources; send public messages; change plans, contacts or systems; close corrective actions; or certify readiness/compliance. Stop if a live incident may exist, current plans or authority are unclear, sensitive data are unauthorized, or output could be mistaken for an order. Require the Authority Having Jurisdiction and qualified emergency, continuity, incident-command, public-information, accessibility, safety, medical, facilities, IT, records, privacy, finance, executive and legal review. ## Provenance Read [source provenance](references/source-provenance.md) before changing this clean-room method. No rejected remote Skill text was copied.