How to Prepare a Crisis Communication Plan Before You Need One

Writing a crisis statement from a blank page, under real pressure, with people already upset, is the worst possible condition to write clearly in. Most of what makes a good crisis response can be prepared well before any actual crisis happens.

Define who actually has authority to respond

A crisis where nobody knows who's allowed to post the statement loses critical hours to internal confusion. Deciding in advance who drafts, who approves, and who has final sign-off removes that bottleneck when speed actually matters.

Build a decision tree for severity

Not every issue needs a public statement — some need a quiet fix, some need a comment reply, some need a full post. A simple framework for triaging severity in advance prevents both overreacting to minor issues and underreacting to serious ones.

Draft a flexible template, not a fixed script

A reusable structure — acknowledge, take ownership, state what changes — that can be filled in quickly with situation-specific detail moves much faster than starting from zero, without producing the generic, hollow feeling of an obviously pre-written statement.

Identify your monitoring channels in advance

Knowing where a crisis is most likely to surface first — a specific platform, a review site, a community forum — means you're watching the right place instead of finding out about a building issue secondhand, hours after it started.

Run a tabletop exercise once a year

Walking through a hypothetical crisis scenario with the actual response team — who drafts, who approves, how fast can a statement realistically go out — surfaces gaps in the plan while there's no real pressure, which is a much cheaper place to find them.