The EOC is About Bureaucracy, not Response

Take a deep breath. It’s going to be OK. Really.

The National Incident Management System (NIMS) gives us the definition of an Emergency Operations Center (EOC) as “locations where staff from multiple agencies typically come together to address imminent threats and hazards and to provide coordinated support to incident command, on-scene personnel, and/or other EOCs.”

I’ll agree with this, but I’ll also suggest this isn’t a complete definition.

EOCs are really about building a bridge between emergency needs and our daily bureaucracy. In the context of response, we have a given set of agencies and organizations, such as first responders and others, that operate in that arena almost exclusively. Their bureaucracies are actually built around their response missions. They are generally built for speed and are supported by procedures and policies to support this. But during a large emergency or disaster, the needs of the incident exceed the capabilities of these response forces, requiring other, less traditional, agencies and organizations to not only provide support, but services as well. While we have seen an increase in these ‘non-traditional’ responders becoming involved, it doesn’t occur with enough frequency to make it a standard of practice. Rather, the focus in these agencies and organizations is still their daily missions, of which the vast majority is not disaster related. Their bureaucracies are built for the day-to-day, not for speed. This is all OK. Bureaucracy isn’t a four-letter word, but in the world of emergency and disaster management we need to understand why certain bureaucracies are built the way they are and figure out how to flex them to shorten reaction time.

Enter the EOC – a room (physical, virtual, in hybrid) where the intent is for bureaucracy and speed to awkwardly coexist. While our traditional response agencies and their counterparts (often at higher levels of government) will always be needed to contribute, the EOC isn’t built just for them. The EOC is also built for those who don’t respond with lights and sirens, but are just as important to supporting our communities during times of disaster.

We need to consider that disasters offer extraordinary circumstances with problems that can’t be solved by traditional means. We need to be creative. We also need to recognize how interconnected all facets of our community lifelines are. In order to conquer the extraordinary, we need everyone. We need to identify the capabilities and capacities held by agencies and organizations we might not typically see involved in an incident. Take a look through the list of departments your own city, village, or county has. The Clerk’s Office? The Planning Department? The Purchasing Department? The Office for Mental Health? The IT Department? Office for the Aging? Child and Family Services? Human Resources? Weights and Measures? There are so many more.

The intent of the EOC is to bring together representatives of these agencies and organizations to help streamline their assistance and support. The EOC should cut the proverbial red tape, but key to that is ensuring that each organization is properly represented. With no disrespect intended toward middle managers, as they often are the ones who really run an organization, EOCs require representation from executive-level leadership of these agencies and organizations. The EOC needs the people who have authority to cut through red tape when required.

So how do we approach this in emergency management: APOETE.

Assessing – Seek first to understand. Identify what agencies and organizations may be needed and when. What do they have? What can they do? What are their limitations?

Planning – Integrate them into emergency planning and encourage them to develop their own emergency plans that address they can work within their own bureaucracies.

Organizing – Meet with them and meet collectively. Bring representatives onto working groups that work in preparedness, response, and/or recovery (consider the Community Lifelines as a place to start). This promotes mutual understanding and inclusiveness.

Equipping and Systems – Ensure that all partners have access to the systems used to support incident management.

Training and Exercises – Broaden the invite lists for training and exercises to help these partners gain knowledge and become more involved.

In the end, it’s about working together toward a common cause, aka unity of effort. To maximize the utility of our EOCs, we need to stop looking at an EOC through the lens of the first responder. Flip that perspective and begin looking at the EOC through the lens of government bureaucracy. Consider what these partners need to be successful. How and when can we streamline? Don’t try to turn them into first responders – that’s the wrong expectation. Rather, we need to meet them where they are, respect what they do, and understand why they have certain protocols in place. That will give us a foundation of understanding to work from.

End note: I’ll also suggest that this reality is another reason why ICS-based organizational models for EOCs are less than effective. The organization of an EOC needs to serve a different purpose than what we often try to force it into. Check out the Incident Support Model as a great alternative.

© 2025 Tim Riecker, CEDP

Emergency Preparedness Solutions, LLC®

Revisiting POETE

One of my most popular posts has been my original post on POETE from July 2014. In the 11+ years has passed since that post, I continue leveraging the concept in every way I can. In case you’ve not heard of the concept, I certainly urge you to click the link above and read my original post. Briefly, POETE stands for Planning, Organizing, Equipping, Training, and Exercises. These are collectively known as the elements of preparedness. POETE is more than a checklist to me. It’s a strategic lens for realistically building and sustaining capabilities. Whether you are building a new emergency operations plan, launching a new public health preparedness initiative, or refining multiagency coordination activities, POETE offers a structured way to think through what takes to help ensure these endeavors are implementation-ready.

While I’ve written on these in the past, my continued and diverse application of POETE has broadened my perspective on application, so here are some fresh thoughts.

Assessing – On occasion, I throw an A in front of the acronym for Assessing. While assessments are an early activity of Planning, there are also plenty of stand-alone assessment activities which should be regarded of their own accord. Assessments can and should inform everything else we do in preparedness. Good assessments can provide us with justification for certain activities and investments and can often give us a data-driven approach. Along with many of the risk assessments common across emergency management, like the Threat, Hazard Identification, and Risk Assessment (THIRA), I’d also suggest that (well written) after-action reports (AARs) can also do the job. A well-developed AAR for an incident, event, or exercise can provide objective analysis of observed activities or discussions. When writing an AAR, we should always keep in mind that part of achieving the goal of improvement may involve requests and justifications for funding.

Planning – I’ve written a lot on the topic of emergency planning through the years. Overall, my take on most emergency plans is that they suck. Horribly. They aren’t worth the time, money, or effort invested in writing them. So many people go about it wrong. A true plan needs to be a blueprint for action. Good plans are operationally-focused, guiding decisions and actions. They should not just be theory and policy, as so many are. At best, I’d call something like that a framework, but it’s certainly not a plan.

Organizing – Organizing is largely about structure, roles, and responsibilities, but you can’t even get there without first building relationships and partnerships. Everything we do in emergency management is about relationships. It’s about knowing who has the thing you need – be it a physical resource, specialized knowledge, or specific authority. Last week I wrote a new piece on Community Lifelines. The central activity of doing anything with Community Lifelines is building relationships. Once those relationships are in place, then other activities will follow.

Equipping – I’ve always been very big on tools matching the mission. Equipment in this context means any and all resources available to us. The key aspect of this is alignment. Are the tools we use matching up to our threats, our people, and our procedures? While it’s understandable to have to update procedures to match a new resource, we should be very cautious about the resource dictating procedure. Our resources need to work for us, not the other way around.

Training – I feel like we have been gradually moving away from compliance being the center of the training universe. Yes, there is still plenty of training that is required for various purposes – there should be and there will always be. But I’ve been getting more requests from clients to develop custom training because they realize that little to no training exists to meet their needs. More people are realizing, for example, that ICS training is absolutely not the fit for EOC staff. Similarly, they are realizing that existing EOC training might begin to approach their needs, but the implementation of their specific EOC model really requires customized training. Overall, training needs to be role-based. We need to be training people what we want them to do. We need to give them the knowledge to succeed, not just generalized training for a broad group hoping that people will be able to ascertain what pertains to them and what does not. We also need to realize that, since most training in emergency management is response-oriented, the things they are being trained to do are things they don’t do often and/or don’t do them under pressure. So frequency of training and job aids are essential to their success.

Exercises – The thing I do the highest volume of. Luckily, I love to do them! Exercises are about testing our plans and capabilities before they are tested for real. Pay attention to good exercise design and never forget that the end product is a worthwhile AAR. I still see so many softball AARs out there. AARs that pat people on the back for a job well done while only acknowledging the superficial opportunities to improve – often times because they don’t want to hurt anyone’s feelings. I don’t ever write an AAR for the purpose of offending anyone, but if we don’t expose what doesn’t work, the chances of it ever being addressed are so much lower than if we had documented it.

While we have the acronym of (A)POETE, it’s important to keep in mind that it’s not intended to be a linear process. It’s iterative and constantly in need of attention. Each component is informed by the others. While I generally believe that Planning is still the foundation of preparedness and it should heavily influence all other elements, those other elements can still influence Planning. POETE activities should be used to build our capabilities. These activities help us prepare with purpose, focus, and intent.

© 2025 Tim Riecker, CEDP

Emergency Preparedness Solutions, LLC®

Replacing ESFs with Community Lifelines

I’ve written previously about my concerns with using Emergency Support Functions in many state, local, territorial, and tribal (SLTT) emergency operations centers. The ESF structure was never intended for SLTT use, and while it may have some successes with the largest of the states and metropolitan areas, it’s generally not a good fit.

I’ve also written previously about Community Lifelines and the benefits thereof. Consider, however, that Community Lifelines, while designed originally for the organization of information by FEMA regional offices when they monitor a disaster, can have much broader applicability. We can and should be using Community Lifelines across every phase / mission area of Emergency Management.

Lately I’ve been having more and more conversations about Community Lifelines with clients, at conferences, and with others who are interested in learning more about them and how to use them. Across emergency management we often find or are provided with approaches to problems that are single-use. We should regularly explore opportunities to expand those single-use applications, increasing the utility of the concept at hand. Given the shortcomings of ESFs for most jurisdictions and the much broader applicability of Community Lifelines for every jurisdiction under the sun, I suggest that Community Lifelines cannot only be operationalized to be a viable replacement for ESFs, they can do so much more. Here are my arguments in support of replacing ESFs with a Community Lifelines – driven organization in SLTT EOCs as well as emergency management programs as a whole:

  1. Community Lifelines are community-focused and more comprehensive of the needs of a community, whereas ESFs are driven by functions which may have limited capabilities or capacities in any given jurisdiction.
  2. Community Lifelines can be operationalized just like ESFs, with primary and support agencies and organizations.
  3. Community Lifelines are focused on stabilizing critical services with built-in mechanisms for assessing impacts and establishing priorities.
  4. Community Lifelines more directly support the inclusion of the private sector, along with government, NGOs, and quasi-government owners/operators.
  5. Community Lifelines provide better preparedness and resilience initiatives.
  6. Community Lifelines provide us with a basis for measuring progress across all phases or mission areas. The only thing we can measure in an ESF is what we might have available to leverage in a response.
  7. Community Lifelines connect resilience, response, and recovery since they are the focal point. While the National Response Framework and National Recovery Framework still have national relevance, the transition from ESFs to Recovery Support Functions (RSFs) is challenging at best.
  8. The inclusion of Community Lifelines in our EOC structure is easy and agnostic to the organizational model used in the EOC. ESFs include functions that are part of the typical overhead management of an EOC, such as ESF 5 (Information and Planning), ESF 7 (Logistics), and ESF 15 (External Affairs), which is an awkward integration.
  9. Community Lifelines lend to better partnerships and preparedness. The ESF plans of most jurisdictions are truly little more than a general scope of the ESF with a list of participating agencies and organizations.

We need to change our mindset of emergency management being centered on response. Yes, response is the big shiny thing. It’s the thing we practice for and anticipate. A more wholistic and comprehensive approach is available to us, however, by using Community Lifelines as the foundation of our work. I suggest that jurisdictions develop Community Lifeline Implementation Plans, which are fundamentally strategic plans identifying how Community Lifelines can be used in Prevention/Protection/Mitigation, Preparedness, Response, and Recovery. Consider how the relationships forged with the owners/operators of Community Lifeline partners can support each of those phases and activities, increasing the resiliency of our community as a whole by making each partner more resilient; and by understanding and preparing for the response and recovery needs of our community through the collective effort of Community Lifeline partners.

Emergency management is more than response. It is a comprehensive effort to support our communities before, during, and after disaster.

© 2025 Tim Riecker, CEDP

Emergency Preparedness Solutions, LLC®