Three people working at desks in a county emergency operations center on the second day of an incident, with a regional zone map on the wall display and handwritten resource numbers on a whiteboard.

Emergency Management

The emergency is not only what is happening. It is everything the incident is disrupting.

An incident that runs for days is a different problem from one that runs for hours. Emergency management technology is mostly about holding a shared picture across agencies that do not share systems, tracking requests and resources at a scale no whiteboard holds, and producing the record that pays for the recovery afterwards. It also has to keep working when the building it normally runs from has been evacuated.

A fire is managed in hours. A disaster may have to be managed for days, weeks, months or years — and somewhere in that stretch the problem stops being the hazard and becomes everything the hazard has broken.

As an incident grows, the work changes shape. It becomes coordination between agencies that do not share systems, information that has to mean the same thing in two rooms, prioritization when everything is urgent, logistics, resource management, public communication, keeping the organization itself running, money, and eventually recovery.

This is a field guide to that work, and to where technology helps with it. It is written from the fire service's point of view, on the understanding that emergency management is never one agency's job.

Where to start

Emergency Management covers more ground than one page can hold. Each part below stands on its own - read the one that answers your question, in whatever order suits you.

Part 1Foundations of Emergency ManagementThe six-phase cycle, the five FEMA mission areas, and the risk assessment that decides what a jurisdiction actually needs. Start here if you are new to the field or building the case for a program.Read this part →Part 2Incident Command & EOC OperationsHow incident command differs from EOC operations, how information moves between the layers, and the test a common operating picture has to pass. For anyone who coordinates across agencies or is buying software that claims to do it.Read this part →Part 3Community Impact & Public WarningThe eight community lifelines, public warning as a behavioral problem rather than a broadcast one, and an interactive readiness snapshot you can build in a few minutes. For emergency managers and PIOs preparing for a specific incident type.Read this part →Part 4System Resilience & Technology EvaluationContinuity planning, the operational gaps technology is asked to close, and evaluation criteria across interoperability, operations, resilience, security and public information. For anyone in a procurement, on either side of it.Read this part →Part 5Learning, Exercises & DocumentationExercise methodology, corrective action tracking, and the documentation that decides what a jurisdiction can recover afterwards. For anyone who runs a preparedness program or writes what happens after the incident.Read this part →Part 6Resources & Getting StartedCase studies, a filterable library of research and professional resources, a standard to hold your program and your vendors to, and a first step that costs nothing. For anyone moving from reading to doing.Read this part →