Emergency Operations Plans that work when it matters

Built for how your organization actually operates

We interview the people who would actually run your response, not just leadership, so the plan captures the informal habits and workarounds that make real response work.

Every EOP is written to be usable in a crisis: clear roles, plain language, and quick-reference sections your team can find under pressure. We also make sure the plan is defensible to auditors, grantors, and accreditors.

Whether you're building your first plan or modernizing one that no longer fits, we meet you where you are and lighten the load on your team.

Standards & frameworks we work in

What goes into an EOP that works

FEMA's Comprehensive Preparedness Guide 101 is the reference standard for emergency operations planning, and it is refreshingly clear on one point: the planning process matters more than the document. A plan produced by one person and handed to an organization is a document. A plan built with the people who will execute it is a capability.

That said, the document has a structure worth knowing.

The base plan sets purpose and scope, describes the situation and the assumptions you are planning against, defines the concept of operations, assigns responsibilities by role rather than by name, and explains how the plan is maintained. It should be readable in one sitting by someone joining your organization tomorrow.

Functional annexes cover the capabilities you need regardless of what happened — communications, evacuation, sheltering, resource management, continuity, public information. This is where most of the operational detail lives, and where a plan earns its keep.

Hazard-specific annexes address the threats your risk assessment ranked highest, and only those. A plan with a detailed annex for every conceivable hazard is a plan nobody reads.

Supporting material — contact rosters, resource inventories, maps, forms, mutual aid agreements. These decay fastest and need an owner and a review cadence.

The planning process we use

We follow the CPG 101 process because it works and because it is what reviewers expect to see. In practice: form a planning team that includes the people who will actually execute; understand the situation through a documented hazard analysis; determine goals and objectives; develop the plan around courses of action; write, review, and approve it; then implement it through training and exercises, and maintain it on a schedule.

The parts organizations most often skip are the first and the last. Skipping the planning team produces a plan nobody feels ownership of. Skipping maintenance produces a plan that was accurate the day it was signed.

Signs your existing plan needs work

You do not always need a new plan. Some reliable indicators that you need something: the plan names people who no longer work there; it references agencies, systems, or facilities that have changed; the last review date is more than a year old; nobody outside the person who wrote it can find their role in it; it was adopted from a template and still contains language that does not describe your organization; or you have had a real incident and the plan was not opened.

That last one is the most telling. If people did not reach for the plan during an actual event, the problem is usually usability rather than content.

Standards we build to

Plans are grounded in FEMA CPG 101 and structured for NIMS and ICS compatibility, so your plan works when you are coordinating with agencies who use the same framework. Where you are subject to a specific standard — the CMS Emergency Preparedness Rule for healthcare, EMAP for accredited agencies, OSHA emergency action plan requirements for employers — the plan is structured to evidence compliance without becoming a compliance artifact that nobody can use operationally. Those two goals are compatible more often than people expect, but only if you plan for both from the start.

How the document is put together

CPG 101 describes a plan in layers. Knowing which layer a piece of information belongs in is most of what keeps a plan usable — detail in the wrong place is the main reason plans go unread.