Crisis Management Plan Contents: What to Include, With a Sample Outline

crisis management plan contents

Most crisis management plans fail the same way: they are too long, written for the wrong reader, and duplicated across departments. A good crisis management plan is one short, all-hazards document that tells your crisis team and your executives who decides what, how bad it is, and what happens next, plus a few short annexes for the situations you’re most likely to face.

That’s the whole idea. Everything below is how to build it.

I’ll cover what belongs in the plan, a sample outline you can work from, what your executives actually want from it, and how to keep it from becoming another binder on a shelf.

Old View New View
A separate plan for every kind of crisis One all-hazards plan, with short annexes that plug into it
A thorough plan is a long plan A useful plan is one a tired person can use at the worst possible moment
The plan tells people what to do in every scenario The plan tells people how to decide, especially in the scenario nobody wrote down
Executives will figure out their role when it happens Executives’ decision rights are written down and exercised in advance
The plan is done when it’s approved The plan is done when it has survived an exercise

What a Crisis Management Plan Is (and Isn’t)

A crisis management plan is the document that tells your organization how it will make, communicate, and carry out decisions when something threatens its people, operations, reputation, or survival. It sits on top of your crisis management framework, which is your philosophy for how crises get handled, and turns that framework into roles, triggers, and checklists. If you haven’t built the framework yet, start with How to Craft Your Crisis Management Framework.

It is not your business continuity plan, which recovers specific processes. It is not your IT disaster recovery plan or your cyber incident response plan, which restore systems and contain attacks. It is not your emergency response plan, which gets people out of a burning building. All of those run underneath the crisis management plan. The crisis plan is where the decisions that cut across all of them get made.

And it is not a script. Dutch Leonard at the Harvard Kennedy School makes the point that there is no comprehensive, executable plan for a novel situation. Routine emergencies follow the checklist. True crises break it. Your plan has to work for both, which is why the decision process matters more than the scenario detail. I wrote about that distinction in Crisis Leadership When the Playbook Fails.

One All-Hazards Crisis Management Plan, Not Five

A crisis is a crisis. A data breach, a hurricane, a product recall, and an executive scandal start in different places, but once they cross your crisis threshold, the work is the same: get the right people in the room, assess, decide, communicate, and track what you decided. The incident-specific actions differ. The process doesn’t.

So build one plan. Security can keep its incident process, IT can keep its outage process, and communications can keep its media process. Siloed incident processes are fine. Siloed crisis processes are the problem. When they collide, your CEO gets two differently formatted, uncoordinated updates and doesn’t know which team to listen to.

We see this constantly. One healthcare client came to us with two crisis teams with overlapping responsibilities, confusing severity levels, and two separate crisis management plan documents. Nobody could say which one governed. A multi-campus university client had a crisis process built only around an active shooter. When a hurricane closed most of its campuses for about two days, there was no process to account for people or recover facilities, and the team made it up as it went.

One-scenario plans fail. Build the process once, then layer the scenarios on top as annexes.

Crisis Management Plan Contents: A Sample Outline

Here is the outline we use as a starting point. Your plan should fit your organization, but if one of these sections is missing, you’ll find out during the event.

  1. Purpose, scope, and assumptions. What the plan covers (all locations? subsidiaries? international operations?), and what you’re assuming about the people and resources you’ll have.
  2. Activation. What triggers the plan, who has the authority to activate it, how the team assembles, and where it meets, including an alternate location and a standing virtual bridge. Make activation automatic for some events (for example, any breach of customer data).
  3. Severity levels and escalation. A short, shared definition of how bad things are. We use four levels: routine event, escalating incident (mandatory notification, so leadership never learns about it from the news), crisis, and critical disruption. Include a one-page escalation diagram. For how to define the levels, see If Your Team Debates the Severity Level, Your Crisis Severity Levels Are Broken. It doesn’t matter what you call the levels. It matters that IT, security, and the crisis team all use the same ones.
  4. Roles and decision rights. The crisis management team (CMT) by role, with a named primary and backup for each. The crisis leader, who runs the process. The responsible executive, who makes or confirms the decisions. Then write down what the CMT decides, what is reserved to executives (major spending, reputation strategy, external messaging), and what goes to the board.
  5. The crisis lifecycle and checklists. Monitor, assess, activate or escalate, manage, and close, each linked to a short checklist so people can jump straight to what they need.
  6. Battle rhythm. The schedule of CMT meetings, a standard agenda, and a situation report (SITREP) format, so updates keep moving when the situation changes by the hour.
  7. Communications. Audiences (employees first, then customers, regulators, partners, media), channels, who approves what, and prepared holding statements. Employees should never learn about your crisis from the news.
  8. Legal, financial, and records. When to bring in counsel and how to protect privilege, a project code for tracking crisis costs, insurance notification, and a decision log: what was decided, by whom, when, and why.
  9. People. Employee accountability, family notification, and aftermath care (an employee assistance or counseling vendor, time off, accommodations), lined up in advance.
  10. Contacts and resources. Team contacts, key vendors, outside counsel, crisis communications support, and local responders.
  11. Training, exercises, and after-action. The commitment to train every role, exercise the plan at least annually, and run an After-Action Report (AAR) after every exercise and every real activation.
  12. Annexes. Short, scenario-specific add-ons (see below).

That is the core. Keep it short enough to read on a phone, with the detail in linked checklists and annexes. The framework and plan section of our Ultimate Guide to Crisis Management goes deeper on each element.

What Your Executives Want From a Crisis Management Plan

Executives are the readers most plans get wrong. What they’re not looking for, as I said on the podcast, is “100, 150 pages of theory or background or governance information or 10,000 checklists.” They want six things:

  1. A focused plan in the format they actually use. Short, graphical, and readable on a phone or tablet, stored somewhere they can reach when your systems are down.
  2. A picture of where they fit. One page showing the executive team, the CMT, and how the two connect.
  3. Clear decision boundaries. What the CMT handles and what escalates to them.
  4. A severity tool. Just how bad is this, and is it getting better or worse?
  5. Time-phased considerations. What to think about at 4, 8, 16, 24, 48, and 72 hours. Life safety and asset protection first, then widening to customers, operations, reputation, and recovery.
  6. The communications and after-action process. How messages get approved and how the lessons will be captured.

This matters because of what happens without it. In exercises, executive teams almost always make up the process as they go. They usually do fine, but they miss things, and they end up doing the CMT’s job instead of their own. Your executives are there to support the crisis team and to make the decisions that escalate to them.

If your executives push back on the plan, don’t conclude they don’t want one. Conclude that it was built for someone else, and rebuild it. I talked through all six on Managing Uncertainty, Episode 93: What Your Executives Want.

Scenario Annexes: Short, Few, and Connected

Annexes add the scenario-specific detail the all-hazards plan leaves out. They don’t replace it. Each one should hold three things: role-specific checklists, the assessment questions for that scenario, and the strategies you’d consider. That’s it.

Keep them short. We once reviewed a 170-page annex for a single scenario that was about three times longer than it needed to be. Over-built annexes break the moment reality differs from the script, and you may need two or three at once, so they have to work together.

Plan for impact, not motive. A terrorism annex and a mass-casualty annex are the same response for most companies.

Which annexes to write first:

  • The obvious, recurring risks, and anything you recently handled badly.
  • The scenarios a regulator or customer contract requires.
  • Then the next-most-likely risks, working outward in rings.

Don’t spend months on heat maps to choose. Typical first annexes: cyberattack and data breach, severe weather, loss of a critical facility or technology, active assailant, protest or activism, and product or service failure. The scenario annexes section of the Ultimate Guide lists the ones we see most.

How the Plan Connects to Your Other Plans

The crisis management plan is the top layer. Write down how the others plug into it:

  • Incident response plans (cyber, IT, physical security) define the triggers that escalate an incident to the CMT.
  • Business continuity plans recover the critical processes your business impact analysis identified. The CMT decides priorities when more than one is competing for the same resources.
  • IT disaster recovery plans restore the systems. The CMT needs realistic recovery times from them, not hopeful ones.
  • Emergency response plans protect people at a site. The CMT supports the site and handles everything outside the building.
  • The crisis communications plan carries the messages the CMT approves.

The handoffs are where plans fail. Test them.

Keep the Plan Alive

A plan nobody has exercised is a hypothesis. Run a tabletop exercise against it at least once a year, and use it for real events you can see coming, like incoming severe weather. Many organizations have a solid crisis process they almost never use because they save it for the catastrophe. Activate early: over-respond, don’t overreact. Why It’s So Hard to Activate a Crisis Management Process covers why teams hesitate.

After every exercise and every activation, run a hot wash before people go home and write the AAR. Then update the plan. Our guide to conducting an effective after-action process walks through it.

Review the whole plan at least annually and after any material change: a reorganization, an acquisition, a new executive team, or a major new risk. Check the contacts every quarter. Nothing ages faster.

Crisis Management Plan FAQ

What should a crisis management plan include?
At minimum: scope, activation criteria and authority, severity levels, roles and decision rights, a crisis lifecycle with checklists, a meeting rhythm, communications, legal and financial procedures, people care, contacts, and a commitment to exercise and learn. The sample outline above covers each.

How long should a crisis management plan be?
As short as you can make it while still answering who decides, how bad it is, and what happens next. The core plan should be readable on a phone. Push the detail into linked checklists and annexes.

What’s the difference between a crisis management plan and a business continuity plan?
The crisis management plan governs how the organization decides and communicates in a crisis. A business continuity plan recovers a specific process or team. In a real event you’ll use both, with the crisis plan on top.

Is there a crisis management plan template or example?
Yes. Our Crisis Management Plan Templates include a crisis management plan, team roles, an initial assessment worksheet, an executive SITREP, communications templates, and a post-incident review. The free Bryghtpath Crisis Management Framework is a four-page starting point.

Is there a standard for crisis management plans?
ISO 22361:2022, Security and resilience: Crisis management guidelines, is the international guidance for crisis management. It’s the standard we align crisis programs to.

A crisis management plan doesn’t need to predict the crisis. It needs to make sure that when the crisis arrives, everyone already knows how the decisions get made.

Keep Going

A few ways to go deeper if this was useful.

Bryan Strawser Avatar

About the author

Let’s build your Resilience Roadmap

Our team has spent two decades helping the world’s leading organizations prepare for and navigate disruption. We’ll bring that experience to yours.