How to Write a County Emergency Operations Plan (CPG 101 Guide)

Most county Emergency Operations Plans fail the same way. Not in a disaster, where the failure would at least be visible, but quietly: the plan is adopted, filed, and never opened again until the next five-year update, at which point someone changes the dates and the phone numbers and the cycle repeats.

That is not a knock on the people who wrote them. County emergency managers are usually one or two people carrying planning, training, exercises, grants, public education, and actual response for an entire jurisdiction. Writing a plan that a hundred people across a dozen departments will genuinely use is a large job, and it competes with everything else.

This guide walks through how to do it anyway, using FEMA's Comprehensive Preparedness Guide 101 as the framework, with an emphasis on the decisions that determine whether the finished plan is usable or shelf-ware.

What a county EOP is actually for

An Emergency Operations Plan describes how a jurisdiction organizes itself to prevent, protect against, mitigate, respond to, and recover from emergencies. It assigns responsibility, establishes lines of authority, and describes how resources get requested, tracked, and paid for.

What it is not is a procedures manual. A good EOP answers "who is in charge of what, and how do we make decisions together." The step-by-step detail belongs in standard operating procedures and job aids that sit underneath the plan and change far more often.

Getting that distinction right is most of the battle. When operational detail creeps into the base plan, the plan becomes long, goes out of date quickly, and stops being read. When the base plan stays at the level of roles, authorities, and coordination, it stays true for years and people can find what they need in it.

Step 1: Build a planning team that includes the doers

CPG 101 opens with forming a collaborative planning team, and it is the step most often shortcut. The temptation, especially with a deliverable date attached to grant funding, is to write the plan in the EM office and circulate it for comment. Plans written that way get polite approval and no ownership.

A workable county planning team usually includes:

• The EM office, as convener and plan owner.
• Operational department leads: sheriff or police, fire, EMS, public works, public health, and the school district.
• Support functions: finance, human resources, IT, county attorney, and public information.
• The people who would actually staff the EOC, which is often not the department head. If a deputy runs the desk during an activation, the deputy belongs on the planning team.
• External partners: hospitals, utilities, volunteer organizations active in disaster, neighboring jurisdictions, and your state EM regional coordinator.

Meet on a schedule and keep the meetings short and decision-focused. A monthly ninety-minute working session over six to nine months produces a better plan than a two-day retreat followed by silence.

Step 2: Ground the plan in a documented risk picture

Everything downstream should trace back to a risk assessment. If your county has completed a Threat and Hazard Identification and Risk Assessment (THIRA), that is your starting point. If not, your Hazard Mitigation Plan almost certainly contains a hazard identification and vulnerability analysis you can build from, and using it has the useful side effect of aligning two plans that are often written in separate silos.

For each credible hazard, you want to be able to state:

• How likely it is, and what history exists in the jurisdiction.
• What the consequences would be to people, property, the environment, and continuity of government.
• What capability gap it exposes, meaning what you would need and would not have.

That last bullet is what turns a hazard list into a planning document. A county that identifies "severe winter weather" as a hazard has described the weather. A county that identifies "a multi-day ice storm would exceed our shelter capacity by roughly 400 people and our generator inventory by six units" has identified a planning problem, and the plan can now say something specific about it.

Step 3: Choose a structure and stick to it

CPG 101 describes three common formats. Pick one deliberately rather than inheriting whatever the previous version used.

Whichever you choose, apply it consistently. Mixed-format plans, where three annexes are functional and two are departmental, are the ones people get lost in.

Step 4: Write the basic plan

The basic plan is the part elected officials adopt and the part outside partners read. It should be readable in one sitting. In most well-built county plans it runs roughly forty to sixty pages, and it covers:

• Purpose, scope, situation, and assumptions. What the plan covers, what it does not, and what conditions it assumes. Write assumptions honestly. "Mutual aid will be available" is an assumption worth stating precisely because in a regional event it may not hold.
• Concept of operations. How the jurisdiction moves from normal operations through activation levels, who has authority to activate, how the EOC relates to incident command in the field, and how coordination with the state works. This is the heart of the plan.
• Organization and assignment of responsibilities. Who does what, by position rather than by name.
• Direction, control, and coordination. Command structure, delegation of authority, and succession.
• Information collection, analysis, and dissemination. What information decision-makers need, who gathers it, and how situational awareness reaches the state and the public.
• Communications. Interoperability, primary and alternate paths, and what happens when the primary path fails.
• Administration, finance, and logistics. Documentation for reimbursement, emergency procurement authority, and resource tracking. Counties that skip this section discover its importance during their first FEMA Public Assistance cycle.
• Plan development and maintenance. Who owns the plan, on what cycle it is reviewed, and how changes are approved.
• Authorities and references. The state statutes, local ordinances, and mutual aid agreements the plan rests on.

Write in plain language and in the active voice. "The Public Works Director assigns debris monitors" is clearer and more accountable than "debris monitors will be assigned as appropriate."

Step 5: Write annexes people can act from

Annexes are where the plan earns its keep. A functional annex should tell the assigned lead what they own, who supports them, what decisions they can make without asking, and what the first hours look like.

The annexes most counties need first:

• Warning and public information. How alerts get issued and who is authorized to issue them, including IPAWS access and backup.
• Evacuation and transportation. Routes, populations needing assistance, and coordination with the state DOT.
• Mass care and sheltering. Facilities, agreements, and the functional and access needs requirements that come with them.
• Resource management. How a request moves from a field supervisor to the EOC to the state, and how it gets tracked and documented.
• Damage assessment. Teams, forms, thresholds, and timelines, because the first 72 hours drive the disaster declaration process.
• Debris management. Frequently its own standalone plan, and a prerequisite for some reimbursement categories.
• Continuity of operations. How the county keeps delivering essential services while it responds. See our COOP planning page for how that plan interlocks with the EOP.

Hazard-specific annexes come after functional ones, and only where a hazard genuinely demands unique actions. A county does not need a separate annex for every hazard in the mitigation plan. It needs functional annexes that work regardless of cause, plus a short hazard annex where the response really is different, such as a dam failure with a defined inundation zone or a fixed chemical facility with an off-site consequence area.

Step 6: Review, exercise, and revise

CPG 101 treats planning as a cycle, not a project. In practice, that means three commitments:

1. An annual review of contact information, agreements, resource inventories, and any change in facilities, personnel, or authorities. This is a half-day of work if it is done every year and a month of work if it is done every five.
2. A full revision cycle, typically every four to five years or after a significant incident, a major organizational change, or a change in state requirements.
3. Validation by exercise. A plan that has never been tested is a hypothesis. A tabletop that walks the EOC team through an activation will surface more problems in three hours than another round of document review ever will. Our guide to running a tabletop exercise that finds real gaps covers how to design one around your plan.

Findings from exercises and real incidents belong in an improvement plan with owners and due dates, and those items are what drive the next revision. That loop is the difference between a plan that improves and a plan that ages.

Seven mistakes that get plans sent back

1. Named individuals instead of positions. Every retirement invalidates the plan. Assign by title and keep names in a roster appendix.
2. Procedures in the base plan. Radio channel programming steps and software logins belong in job aids, not in an adopted document.
3. No traceable risk basis. Contents that cannot be tied back to an assessment read as a borrowed template.
4. Untested assumptions. Assuming mutual aid, generator availability, or staff reporting rates without saying so, and without a fallback.
5. Silent on finance. No emergency procurement authority, no documentation standard, no cost tracking. This surfaces painfully during reimbursement.
6. Annexes with no lead. A function everyone supports and nobody owns will not get done under pressure.
7. An improvement plan with no owners or dates. Open findings that roll forward year after year are the single most common state review observation.

Common questions

How long should a county EOP be?

There is no required length, but a basic plan that runs beyond roughly sixty pages usually contains material that belongs in an annex or an SOP. Length is a symptom, not a target. The right question is whether an EOC team member can find what they need in under a minute.

How often does a county EOP need to be updated?

Requirements vary by state, so check your state emergency management agency's guidance first. As a general practice, review annually and revise fully every four to five years, or sooner after a major incident, a significant reorganization, or a change in law. Some grant programs and accreditation standards impose their own cycles.

Can we adapt another county's plan?

You can use one as a structural reference, and looking at how a comparable jurisdiction organized its annexes is genuinely useful. What does not transfer is the content: their risk basis, their agreements, their department structure, and their authorities are not yours. Plans that are adopted with another jurisdiction's substance intact are easy for reviewers to spot and harder for your own people to use.

What is the difference between an EOP and a COOP plan?

An EOP describes how the jurisdiction responds to an emergency affecting the community. A Continuity of Operations plan describes how the government keeps delivering its own essential services when its people, facilities, or systems are disrupted. Counties need both, and they should reference each other.

Do we need an EOP to receive grant funding?

Requirements differ by program, but a current, adopted, NIMS-consistent plan is a common condition or scoring factor for preparedness grants, and several programs require planning deliverables that flow directly from it. Check the notice of funding opportunity for the specific program.