Emergency Operations Planning, NIMS/ICS & NWS StormReady Program

Emergency Operations Planning, NIMS/ICS & NWS StormReady Program

Emergency preparedness is a January 1, 2026 ASFPM CFM exam category that tests whether floodplain managers understand how flood risk reduction connects to real-time warning, multi-agency incident management, and post-event recovery systems. You are not expected to replace the emergency manager. You are expected to know how floodplain management products—FIRMs, depth grids, critical-facility inventories, substantial-damage procedures, and building-permit rules—feed Emergency Operations Plans (EOPs), National Incident Management System (NIMS) practices, Incident Command System (ICS) operations, NWS StormReady recognition, and Community Rating System (CRS) flood-warning credit.

Emergency Operations Planning for Floods

A local Emergency Operations Plan (EOP) is the community’s pre-scripted playbook for hazards. Flood-specific content usually appears as a hazard annex or functional annex covering warning, evacuation, sheltering, search and rescue, public information, mass care, and reentry. Effective flood annexes answer operational questions, not abstract goals:

• Who monitors river gauges, NWS products, and local rainfall?
• What stage, rainfall, or forecast product triggers sirens, reverse-911, door-to-door warning, or evacuation orders?
• Which routes, shelters, and special-needs facilities are in the SFHA or residual levee risk area?
• How do public works, law enforcement, fire, health, schools, utilities, and the floodplain administrator coordinate under one incident structure?
• How will the community document decisions for after-action reports and future CRS or mitigation grant applications?

CFM contribution to the EOP. Floodplain managers typically supply or maintain: effective FIRMs and FIS profiles; approximate depth/velocity awareness for major streams; inventories of critical facilities and repetitive-loss clusters; elevation certificate and lowest-floor data for key structures; ordinance rules that will govern reentry permitting and substantial-damage determinations; and contact procedures for state NFIP coordinators and FEMA region staff. When the EOP is silent on who issues stop-work orders, who leads damage assessments, or how temporary housing sites are reviewed against SFHA rules, recovery becomes chaotic. Plan those handoffs in peacetime.

NIMS Principles Every CFM Should Know

The National Incident Management System (NIMS) is the national framework for managing incidents of any size. FEMA and DHS expect state and local agencies that seek preparedness funding and multi-agency interoperability to adopt NIMS. Core NIMS concepts tested at CFM overview level include:

1. Common terminology — shared words for organizational functions, resource types, and incident facilities so “Operations Section” or “staging area” mean the same thing across agencies.
2. Modular organization — the command structure expands or contracts with incident complexity; a small creek flood may need only an Incident Commander, while a multi-county river flood may activate full sections and Unified Command.
3. Management by objectives — leaders set measurable objectives for operational periods (for example, “complete primary search of Zone 3 by 1800” or “open debris staging site B before reentry”).
4. Incident Action Planning — written or verbal Incident Action Plans (IAPs) communicate objectives, assignments, and safety messages for each operational period.
5. Integrated communications and resource management — common radio plans, resource typing, and mutual-aid systems prevent freelancing.
6. Unity of command / chain of command — each person reports to one supervisor within the incident organization (with Unified Command addressing multi-jurisdiction authority at the top).

NIMS is not a substitute for floodplain ordinance enforcement. It is the operating system that lets floodplain staff plug into a disaster without inventing a parallel command structure.

ICS Structure: Command Staff and General Staff

The Incident Command System (ICS) is the on-scene management model used under NIMS. At the top is the Incident Commander (IC)—or a Unified Command when multiple agencies with jurisdictional authority share leadership. Command Staff report to the IC:

• Public Information Officer (PIO) — official incident messaging; often works through a Joint Information Center.
• Safety Officer — hazard identification for responders and reentry teams (swift water, contaminated mud, structural collapse, carbon monoxide from generators).
• Liaison Officer — point of contact for assisting and cooperating agencies (state NFIP office, Corps of Engineers, utility cooperatives, voluntary organizations).

General Staff sections (the classic ICS “four sections”) are:

Unified Command is used when, for example, a city, county, state highway agency, and federal partners all have statutory roles on the same river flood. Leaders jointly set objectives and speak with one coordinated voice while retaining agency authorities. CFMs should know where they report—often through Planning (technical specialists / damage assessment) or Operations (permit/field inspection strike teams)—rather than operating as an unsupervised side channel.

CFM role scenarios under ICS. After a major flood, the Planning Section may task the floodplain administrator to produce maps of likely substantial-damage clusters, prioritize inspection routes, and brief the IC on ordinance timelines. Operations may attach building officials and CFMs to windshield survey teams. Finance/Admin will later need documentation of staff hours and contracts—habits that also support DRRA Section 1206 reimbursement (covered in Section 3).

NWS StormReady Program

StormReady is a National Weather Service (NWS) voluntary recognition program that verifies a community (or county, university, tribe, or military installation) has the infrastructure and procedures to receive NWS warnings and deliver timely local alerts. It is not flood insurance, not a CRS class by itself, and not a substitute for structural mitigation. It is a preparedness credential that strengthens warning systems—especially valuable for flash flood and tropical cyclone communities.

Typical StormReady expectations (overview level for CFMs) include:

• A 24-hour warning point and Emergency Operations Center (EOC) capability, or documented equivalent arrangements.
• Multiple ways to receive NWS watches/warnings (NOAA Weather Radio, internet/data feeds, emergency management networks).
• Multiple ways to disseminate warnings locally (sirens, IPAWS/WEA, reverse notification, cable override, social media, door-to-door plans for vulnerable areas).
• Weather monitoring capability and local spotter or observation support where appropriate.
• Community preparedness: public education on flood and severe-weather safety.
• Exercises/drills and written procedures that are reviewed and updated.

For CFMs, StormReady intersects floodplain management when inundation maps, “turn around don’t drown” messaging, campground/RV park warning procedures, and residual risk behind levees are incorporated into warning products. A community can be StormReady yet still fail CRS flood-warning credit if documentation, annual exercises, or critical-facility warning procedures do not meet CRS Activity 610 criteria—so align the programs deliberately.

CRS Activity 610 Concepts: Flood Warning and Response

Under the Community Rating System, Activity 610 – Flood Warning and Response (and related warning/response elements in CRS guidance) credits communities that maintain documented flood threat recognition, emergency warning dissemination, response operations, and critical-facility planning. At CFM exam depth, remember the logic chain:

1. Threat recognition — how the community knows a flood is coming (gauges, forecasts, residual levee monitoring).
2. Emergency warning — how the public and facilities are notified with enough lead time for protective action.
3. Response operations — written procedures for sandbagging, evacuations, traffic control, and flood-fight actions tied to forecast stages.
4. Critical facilities — facilities with special warning and protection plans (hospitals, water treatment, emergency services, schools, hazardous materials sites).
5. Implementation and maintenance — training, drills, after-action improvements, and annual reviews.

CRS credit rewards capability that is written, exercised, and maintained, not aspirational language in a brochure. Floodplain managers often co-author the technical pieces (inundation mapping, facility elevation data) while emergency management owns operational command. Joint ownership is a feature, not a bug: the same procedures that earn CRS discount also save lives during the next flash flood watch.

Putting It Together: CFM Support Before the Water Rises

A prepared CFM does not wait for the declaration. In the quiet season you should:

• Confirm your contact role in the EOP and EOC directory.
• Keep GIS layers for SFHA, depth, critical facilities, and past damage ready for Planning Section use.
• Pre-stage substantial-damage inspection forms, team assignments, and mutual-aid building-official contacts.
• Coordinate with emergency management on StormReady renewal evidence and CRS Activity 610 documentation.
• Brief elected officials that “response success” without code-compliant recovery will recreate the same risk—and that permit surge and temporary housing siting will demand staff capacity.

When the river crests, those peacetime relationships determine whether floodplain management is integrated into ICS or left outside the fence line.