Business Continuity

Emergency Operations Center Maturity in Practice

Five operating disciplines for public agencies that keep essential services running.

By Jeff Crow, CBCP · October 28, 2026

Executive Summary

Water and wastewater utilities, public power providers, transit agencies and public health departments face a readiness problem that police, fire and emergency management agencies usually do not. Their people are experts in running a system, not in running an emergency. Their Emergency Operations Center (EOC) is staffed by engineers, operators, communicators, attorneys and finance staff who take on incident roles as a secondary duty, often with long gaps between real activations.

Most of these agencies already have plans, and many are required to. Community water systems serving more than 3,300 people must prepare and periodically review emergency response plans under America’s Water Infrastructure Act, [1] and rail transit agencies must include emergency preparedness and response procedures in their safety plans. [2] What is often missing is the operating discipline that turns a plan into a fast, consistent first decision when something goes wrong.

Drawing on public doctrine and on Teleion’s recent work helping an essential-services public agency design, test and begin to own its EOC operating model, this paper recommends five operating disciplines:

Common incident terminology grounded in National Incident Management System (NIMS) titles and plain-language definitions.
Life-safety-first escalation, so that calling for emergency help never waits on internal coordination.
Communications assigned by purpose, with one predetermined, tested primary method for each purpose and defined fallbacks.
Short, embedded calibration and practice owned by the functions that run operations.
A predefined, delegated and practiced initial activation decision.

Each discipline can be started with existing staff and existing tools. Together they address the conditions Teleion most often finds in agencies where incident response is everyone’s second job.

The Readiness Gap in Essential-Service Agencies

Agencies that deliver water, power, transportation and public health services run complex physical and digital systems around the clock. Their operators handle abnormal conditions every day. That creates a subtle risk: the line between a routine alarm and the start of an emergency is blurred, and the decision to escalate is left to individual judgment.

In discovery work with one such agency, Teleion held cross-functional breakout sessions with leaders from operations, engineering, maintenance, technology, communications, safety, legal, finance and supply chain. Each group rated its own readiness on a simple maturity scale and described where decisions slowed down. The same themes surfaced across nearly every function:

Activation triggers and decision authority were not consistently defined or applied. This was the most significant single gap.
Response depended on a small number of long-tenured individuals rather than on defined roles.
Notifications were often treated as informational rather than as calls to action, and several channels were used at once, adding to confusion and fatigue.
Procedures existed but were extensive, siloed by department and hard to use under pressure.
Formal exercises had lapsed, although appetite for practical training was strong.
Early incidents with an uncertain cause, such as an equipment failure that might be a cyber intrusion, had no clear decision path between operational technology teams and the EOC.

Senior leaders asked a pointed question during the same discovery: why had earlier efforts to stand up an EOC not lasted? The answer shaped the engagement. Readiness in these agencies depends less on a better plan than on a small set of habits that are defined clearly, practiced often and owned by the people who run operations.

Discipline 1: Use Common Incident Terminology

NIMS defines three EOC activation levels and states that EOC personnel “should use the standard NIMS activation level titles” for communication outside their jurisdiction or organization. When numbers are used, NIMS recommends that they descend, so that Level 1 means full activation. [3]

Agencies may keep internal numbering or color schemes, but public examples show that numbering direction, tier counts and the meaning of the lowest tier vary widely. A level number alone does not travel well between an agency, its partners and its regulators.

Exhibit 1. NIMS standard EOC activation levels

Level	NIMS title	What it signals
1	Full Activation	All or most EOC functions staffed; enterprise-wide coordination.
2	Enhanced Steady-State / Partial Activation	Selected functions activated to coordinate a developing or contained incident.
3	Normal Operations / Steady State	Routine monitoring; no EOC activation.

Source: FEMA, National Incident Management System, Third Edition (2017), Table 2. Higher activation is shown at top; numbers descend as activation increases.

Terminology also matters inside the agency. In the engagement, Teleion and the agency defined every level against the same four attributes: status and trigger, staffing, primary communication, and decision authority. Writing all four for every level exposed gaps that a list of level names hides, such as a level with a clear trigger but no named decision-maker.

Calibration sessions (described under Discipline 4) showed where definitions were still too soft. Different functions read the same scenario differently: one function treated a reputational event as a single notice, while another wanted to convene the EOC before communicating. Definitions built on adjectives such as significant or minor invited that scatter. Observable tests gave the group a shared basis for the call: Is damage visible? Is service affected? Is the public or media aware? The agency added an explicit test to its first active level, whether the incident has the potential to reach the public, and noted the need for a rule on when reputational exposure alone can raise a level.

NIMS also directs that incident communication use “plain language and clear text, not codes.” [3] For secondary-duty staff, that means level titles, triggers and instructions written in words a new team member can act on without translation.

Discipline 2: Protect Life While Coordination Begins

The Incident Command System sets objectives in priority order: life safety first, then incident stabilization, then property preservation. [4] Few agencies would dispute this. The risk is structural. When an organization builds escalation chains, call trees and approval steps, it can unintentionally place them between an employee and an emergency call.

Public rules point the other way. Under Kari’s Law, covered multi-line telephone systems must allow direct 911 dialing, and any internal notification “must not delay the call to 911.” [5] Where an Occupational Safety and Health Administration (OSHA) standard requires an emergency action plan, that plan must include procedures for reporting emergencies. [6] Healthcare research, a useful analog rather than EOC evidence, finds that staff delay escalation while they seek further justification or anticipate how others will react. [7]

The practical answer is two parallel lanes with no approval gate between them. In the life-safety lane, anyone who sees a hazard protects people and calls 911 directly. In the coordination lane, the same report moves against predefined criteria to an authorized official, who decides whether to activate. The agency in the engagement formalized a 911-first rule for life-safety events and issued incident-reporting guidance for employees outside the EOC, so that people with no EOC role know what to do in the first minutes and whom to tell next.

For staff with secondary EOC duties

You are not expected to be an emergency manager. You are expected to know four things cold: which life-safety actions come before any internal call; the plain-language name of each activation level and what it asks of you; the one channel you watch for mobilization; and who you report to once the EOC convenes. When you are unsure which level applies, say so. Uncertainty raised early is useful information; uncertainty held back is how the first call gets delayed.

Discipline 3: Assign Communications by Purpose

Discovery interviews described a communications swirl: chat, text and email used at the same time, alerts read as for-information-only, and no shared sense of where decisions were being made. Public guidance offers a simpler structure. The Federal Emergency Management Agency (FEMA) advises that “the primary method of communication should be predetermined and tested.” [8] The Emergency Management Accreditation Program (EMAP) standard distinguishes coordination with stakeholders, notification of decision-makers and emergency personnel, and public alerts and warnings, and requires alternatives if a primary system fails. [9] The Cybersecurity and Infrastructure Security Agency (CISA) recommends a Primary, Alternate, Contingency, Emergency (PACE) plan that is “as simple as possible” and practiced. [10]

Exhibit 2. Communication purposes and a PACE plan (illustrative)

Purpose	Primary	Alternate	Contingency	Emergency
Coordination among stakeholders	Designated, tested method	Defined fallback	Defined fallback	Defined fallback
Notification of decision-makers and emergency personnel	Designated, tested method	Defined fallback	Defined fallback	Defined fallback
Public and occupant warning	Multiple warning channels used at the same time, each with its own fallback.

Original synthesis of EMAP EMS 5-2022, CISA PACE guidance (2024) and NIST TN 1827. Cells are placeholders, not prescribed tools.

In the engagement, the agency settled on three tools with three distinct jobs. Mass notification mobilized the EOC team and pointed them to a single live coordination bridge; it was not used to brief leadership. The bridge was where decisions were made and logged. A structured situation report then created the record, with a separate, shorter summary for senior leadership. Each message had a named drafter, approver and sender. Practice quickly exposed what the design had missed, including the need for a backup approver for the leadership summary and gaps in the notification roster that had to be closed before the next exercise.

Two cautions apply. First, public and occupant warnings are different: guidance from the National Institute of Standards and Technology (NIST) supports using multiple channels at the same time so that people can confirm a warning quickly. [11] A single-primary rule applies to internal coordination, not to warning the public. Second, every situation report should separate what is confirmed from what is not. The Centers for Disease Control and Prevention (CDC) advises communicators to share “what is known, what is not known, and what is being done to fill in the gaps.” [12]

Discipline 4: Keep Calibration and Practice Short, Embedded and Owned

Large annual exercises remain valuable, but on their own they leave long gaps for secondary-duty staff. The Homeland Security Exercise and Evaluation Program (HSEEP) describes a progressive approach in which exercise complexity increases over time, and it recognizes drills with a narrow focus and immediate feedback. [13] Teleion uses two short formats within that progression: calibration sessions and micro-simulations.

Calibration: finding where judgment diverges

In a calibration session, each participant independently classifies a set of brief, realistic scenarios against the draft activation levels and rates their confidence. The group then compares results and discusses where and why judgments diverged. Participants come from every function that would touch an incident, so differences between functions surface in the room rather than during a live event.

In the engagement, calibration confirmed that the draft level structure was broadly sound and showed that disagreement clustered at the boundaries, above all between normal operations and the first active level. Pairs of scenarios from the same hazard class that had been drafted two levels apart prompted useful debate about whether the difference was real. The exercise also surfaced two unwritten rules the model needed: how reputational exposure should affect a level, and who owns the severity call. Confidence ratings proved a practical diagnostic. People generally knew when they were guessing, so asking where they felt least sure pointed directly to the criteria that needed rewriting.

Three limits keep calibration honest. Agreement shows consistency, not correctness. Research cautions that confidence tracks consensus rather than accuracy. [14] And a discussion-based session does not validate that the EOC can actually mobilize; that requires drills and exercises.

Micro-simulations: frequent repetitions that change the plan

A micro-simulation is a short, scenario-based exercise that tests one or two critical decisions and immediately converts them into operational actions using the agency’s own plans. In the engagement, leadership protected a 15-minute window each month inside existing staff meetings, so practice required no work stoppage.

Exhibit 3. Anatomy of a 15 to 20 minute micro-simulation

Step	Time	What happens
1. Set the stage	2 min	One-paragraph inject written from the receiving team’s view: what they know, what they don’t and what decision is due.
2. Decide	6 to 8 min	One or two forced choices; assumptions captured.
3. Operationalize	6 to 8 min	Plan and trigger invoked; owners, next actions, communications and dependencies named.
4. Capture and close	2 min	Three to five commitments; gaps assigned owners and due dates.

Teleion method. Minimum capture: plan invoked, trigger, decisions, owners, next 30/60/120-minute actions, notifications and message owner, dependencies, gaps and due dates.

Every micro-simulation should force a decision, impose a time limit, work with imperfect information, require a handoff and produce a tangible output. Teleion’s rule of thumb is simple: if it does not end with an action owner, it was not a micro-simulation. The facilitator’s standing question is: what happens in the next 30 minutes, who does it, and where is it logged? The team updates at least one artifact the same day, such as trigger language, a call tree or a message template.

The series built in steps. An early session walked the core EOC team through a routine alarm that escalated to partial activation, ending only when the alert had been sent, the coordination bridge was open and ownership of the situation report was confirmed. A later, longer session focused on running the EOC meeting itself. Each function received private information by email, and the debrief asked what people knew that the meeting never asked about. Research on group decisions shows why this matters: groups tend to discuss information everyone already shares and underuse what only one member knows. [15]

Ownership is built in from the start. Internal facilitators follow a progression: shadow two or three sessions, co-facilitate one segment, lead a full session with a template and scribe, review results with peers, then rotate across functions. HSEEP’s guidance that participants decide “in a no-fault environment” [13] and research linking psychological safety to team learning [16] both support keeping these sessions non-evaluative.

For operations leads

You own the triggers. Write them as conditions an operator can observe, not adjectives. Bring your hardest boundary cases to calibration, especially incidents whose cause is unclear in the first minutes, and agree in advance who declares when operational data can no longer be trusted. Host a micro-simulation in your own staff meeting each month, and leave every session with one changed artifact and one named owner.

Discipline 5: Delegate and Practice the Initial Activation Decision

The hardest call in most agencies is the first one: the decision to depart from normal operations. NIMS lists circumstances that might trigger activation, including threshold events described in the emergency operations plan. [3] FEMA advises that activation procedures list at least three officials with the authority to activate, identified by title rather than by name, and suggests testing whether they can activate the EOC for a surprise exercise. [8] FEMA planning guidance adds at least two alternates for each key position. [17]

In the engagement, leadership was asked to ratify who recommends and who approves each activation level, and to name an interim program owner while a permanent owner was being established. Writing authority by title made it possible to practice the call with whoever was on duty, rather than with the one person who usually made it.

Calibration also revealed a design flaw worth checking in any agency. The first active level automatically sent a single notice to both the EOC team and senior leadership. Several participants admitted they hesitated to declare that level because of who would read the message. Rules that make the first call socially expensive slow it down. The team weighed options: separating the EOC notice from the leadership notice; confirming first how often leaders already ask EOC members about developing incidents; and the risk that a forwarded message informs one executive while others remain unaware. The goal was the same in each option: make the first call a documented, practiced habit, never a judgment one person makes alone under pressure.

Delegation does not mean consensus. Function-specific information should reach the authorized official quickly, but activation should not wait for a meeting or a vote. Authority stays with the named official; the discipline is making sure that official hears what each function knows.

For executives

Three decisions sit with you. Ratify activation authority by title, with alternates, so the first call never depends on one person being reachable. Name an accountable program owner and a cross-functional working group that will outlast any consultant. Protect a small, recurring block of time for practice. Then make it safe to call the first level early: an activation that is later stood down is the system working, not a false alarm.

From Built to Owned: Sustaining the Capability

Senior leaders’ question about why earlier efforts had not lasted is common, and research on program sustainment explains it: implemented programs are often only partly sustained, with outcomes shaped by organizational context, capacity and processes. [18] The engagement therefore treated ownership as a deliverable rather than an afterthought.

The agency chartered a cross-functional EOC working group spanning operations, communications, safety, technology, legal and procurement. It began replacing extensive, siloed procedures with scenario-indexed playbooks and one- to two-page checklists for the first 15, 30 and 60 minutes. It adopted a standard after-action template that feeds procedure updates, consistent with NIMS guidance that deactivation planning include after-action review and improvement planning [3] and with EMAP’s expectation that activation and deactivation procedures be tested on an established schedule. [9]

The next phase moves the model from consultant-supported to agency-owned: EOC policy and procedures integrated into the emergency operations plan; editable training content transferred to the agency’s learning team with a train-the-trainer session; role-based NIMS and Incident Command System (ICS) training; a standing meeting cadence and published exercise calendar; and a named owner for every artifact. Teleion tracks progress with a maturity scale based on observable behaviors rather than tools. Maturity models differ in their number and definition of levels, so the scale is a management aid, not an industry standard.

Where to Start

Leaders can test their current position with three questions:

Could three officials, identified by title, make the first activation call tonight using written, observable criteria?
Does each communication purpose have one tested primary method and a defined fallback, with public warnings sent through multiple channels?
When did the EOC team last make a time-pressured decision together, and what changed in the plan afterward?

Teleion helps essential-service agencies answer those questions and act on the answers:

EOC readiness assessment. Cross-functional discovery, activation framework review, role and authority mapping, and a prioritized roadmap.
Micro-simulation program. Calibration sessions, monthly micro-simulations embedded in existing meetings, and train-the-trainer support so internal facilitators sustain the program.
Crisis communications planning. Communication purposes, primary methods and fallbacks, message ownership and approval, and situation report and leadership summary templates.

A Note on Evidence

The five disciplines are Teleion’s recommendation, not a validated maturity model. Their individual components rest on the public doctrine, regulation and research cited below. Healthcare, workplace and laboratory studies are cited as analogs, not as evidence of EOC effectiveness. Engagement examples are anonymized, described qualitatively and included with the client’s approval; they illustrate how the disciplines were applied, not measured outcomes. Regulatory references describe requirements only within their stated scope and do not establish compliance for any reader.

For more information about how Teleion can help build your EOC operating model, please visit Security, Risk and Compliance.

Notes

U.S. Environmental Protection Agency. AWIA Section 2013 / SDWA Section 1433: Risk and Resilience Assessments and Emergency Response Plans. Last updated May 14, 2026. epa.gov
49 CFR 673.11(a)(6), Public Transportation Agency Safety Plans (applies to rail transit agencies). eCFR, current as of October 21, 2026. ecfr.gov
Federal Emergency Management Agency (FEMA). National Incident Management System, Third Edition. October 2017. fema.gov
FEMA Emergency Management Institute. IS-200.c, Incident Priorities lesson. emilms.fema.gov
47 CFR 9.16, Multi-line telephone system requirements (Kari’s Law); applies to covered systems manufactured or installed after February 16, 2020. ecfr.gov
29 CFR 1910.38, Emergency action plans; applies where an OSHA standard requires an emergency action plan. ecfr.gov
Chua, W.L., et al. “Factors influencing the activation of the rapid response system for clinically deteriorating patients by frontline ward clinicians.” International Journal for Quality in Health Care, 2017 (healthcare analog). pmc.ncbi.nlm.nih.gov
FEMA. NIMS EOC How-To Quick Reference Guide. October 2022. fema.gov
Emergency Management Accreditation Program. ANSI/EMAP EMS 5-2022, Emergency Management Standard, Standards 4.8.1, 4.8.2 and 4.9.2. emap.org. EMAP has announced an updated standard (EMS 5-2026) for publication in January 2027.
Cybersecurity and Infrastructure Security Agency. Leveraging PACE Plans into Emergency Communications Ecosystems. October 2024. cisa.gov
National Institute of Standards and Technology. Technical Note 1827, General Guidance on Emergency Communication Strategies for Buildings, 2nd Edition. February 2014. nvlpubs.nist.gov
Centers for Disease Control and Prevention. Crisis and Emergency Risk Communication: Introduction, 2018 Update. cdc.gov
FEMA. Homeland Security Exercise and Evaluation Program (HSEEP) Doctrine. January 2020. fema.gov
Koriat, A. “Subjective confidence in one’s answers: The consensuality principle.” Journal of Experimental Psychology: Learning, Memory, and Cognition 34(4), 2008. iipdm.haifa.ac.il
Stasser, G., and Titus, W. “Pooling of unshared information in group decision making.” Journal of Personality and Social Psychology 48(6), 1985 (laboratory research).
Edmondson, A. “Psychological Safety and Learning Behavior in Work Teams.” Administrative Science Quarterly 44(2), June 1999 (manufacturing teams).
FEMA. Comprehensive Preparedness Guide (CPG) 101, Version 3.1. May 2025. fema.gov
Wiltsey Stirman, S., et al. “The sustainability of new programs and innovations: a review of the empirical literature and recommendations for future research.” Implementation Science 7:17, 2012 (health and social programs). implementationscience.biomedcentral.com

About the author

Jeff Crow, CBCP

Jeff Crow is a Practice Director at Teleion and a Certified Business Continuity Professional. He leads Teleion's business continuity and emergency operations work, including EOC design and activation frameworks, business impact analysis and continuity planning, crisis communications planning, and exercise programs built on short, frequent practice. His engagement experience spans health systems, public utilities, global technology companies, and large mission-driven enterprises.

Have a challenge worth tackling?

Let's talk!