Emergency Planning & Preparedness

Emergency Planning & Preparedness

Domain 7's second task area shifts from identifying threats and setting recovery objectives to the practical work of getting ready: securing outside resources before a crisis, building planning documents that will actually work under pressure, organizing effort using the recognized four-phase emergency management model, and standing up the two field disciplines — triage and damage assessment — that determine what happens in the first hours of a response.

Resource Management: Mutual Aid and MOUs

No single organization owns enough personnel, equipment, or specialized capability to handle every plausible crisis alone. Mutual aid agreements (MAAs) are pre-arranged commitments between organizations, facilities, or jurisdictions to share personnel, equipment, and expertise when a crisis exceeds one party's own capacity. Mutual aid can be structured locally between neighboring facilities, regionally, or at a broader scale — the U.S. Emergency Management Assistance Compact (EMAC) is the model for interstate mutual aid, and equivalent private-sector mutual aid networks exist within industries such as utilities and hospitality.

A Memorandum of Understanding (MOU) formalizes the terms of that resource-sharing relationship: who can request what, activation triggers, command relationships once resources arrive, liability and insurance responsibility, and cost-reimbursement terms. The defining feature of a usable MOU is that it is negotiated and signed before the crisis, not improvised during one — waiting until an emergency to establish terms wastes the exact hours a mutual-aid relationship exists to save. Effective resource management also depends on resource typing: classifying personnel and equipment by capability and capacity using a common standard, so that a request for "an ambulance strike team" or "a generator crew" means the same thing to every agency that might respond to it, keeping the exchange interoperable rather than improvised.

Mutual aid agreements and their underlying MOUs are not "set and forget" documents. Contact lists, capabilities, and legal or regulatory requirements all change over time, so mature programs review and re-test each agreement on a defined cycle, confirming that the partner organization can still deliver what the paperwork promises before an actual emergency puts that promise to the test.

Emergency Planning Techniques

Good emergency plans are built, not inherited. Planning starts from the risk assessment and BIA developed in Domain 7's first task area, translating identified threats and recovery priorities into documented, actionable procedures. Effective planning techniques share several features:

• Scalable — a small incident and a catastrophic one use the same plan structure, just at different activation levels
• All-hazards at the core, with hazard-specific annexes layered on top only where truly needed
• Built with the people who will execute them, not imposed from above, which improves both plan quality and the odds staff actually follow it
• Hierarchical — a strategic emergency plan (overall authority, policy, organizational structure) flows down through functional annexes (communications, evacuation, resource management) to hazard-specific procedures (fire, active assailant, severe weather)

Cross-departmental involvement in the drafting process, not just security, improves plan quality and buy-in when the plan must be executed under pressure.

Plans are living documents rather than one-time deliverables. Effective programs review and update the emergency plan on a defined cycle — typically annually, or immediately after any exercise or real event exposes a gap — and version-control every change so the field copy in a responder's hands always matches the current authorized plan rather than an outdated draft.

The Four Phases of Emergency Management

The CPP body of knowledge organizes emergency management activity into four recognized phases:

These phases are commonly drawn as a cycle rather than a straight line, because recovery from one event feeds mitigation for the next, and because the phases overlap in practice — response actions can begin recovery-oriented work, such as initial damage assessment, even before the event has fully concluded. Recognizing which phase a given activity belongs to is a frequent exam pattern: installing storm shutters is mitigation; stocking a 72-hour supply kit is preparedness; evacuating a building is response; restoring the data center is recovery.

Triage and Damage Assessment

When a crisis produces casualties, responders use triage to prioritize care under conditions where demand exceeds immediately available resources. The most widely taught model is START (Simple Triage and Rapid Treatment), which sorts victims into four categories:

• Immediate (red) — life-threatening injury requiring care within minutes
• Delayed (yellow) — serious injury that can tolerate a delay in treatment
• Minor (green) — walking wounded, minimal injury
• Deceased/expectant (black) — no signs of life, or injuries incompatible with survival given available resources

Alongside triage, damage assessment systematically evaluates the physical, operational, and safety impact of the event. It typically proceeds in two stages: a rapid initial assessment focused on life safety and immediate hazards (structural stability, utility hazards, access routes), followed by a more detailed assessment that quantifies property damage, operational downtime, and financial impact to inform recovery priorities and resource allocation. Damage assessment findings feed directly into the recovery strategies covered later in this chapter, and accurate, early assessment is consistently what separates an organization that recovers within its BIA-defined recovery time objectives from one that does not.