Response Guide

How to Build a Communication Preparedness Plan Before You Need One

Ninety-five percent of communication readiness is preparation. The five percent that everyone sees, the response, the statement, the interview, is the easy part if you have done the work in advance. The plan is what turns the worst day of your year into a sequence you have already rehearsed.

Why preparation beats response, every time

Under time pressure, the parts of your brain that write careful language do not work the way they normally do. The approval chain that usually takes a week has to happen in an hour. Mistakes that would be obvious on any other day become invisible. This is true for restaurant owners, hospital administrators, and four-star generals alike.

The fix is to make the decisions before you are under pressure. The language is pre-approved. The notification order is already decided. The contact channels are already open. When the situation lands, you are not writing, you are deploying.

What goes into a real plan

A communication preparedness plan is not a contact list and it is not an org chart. It is a document that holds all of the decisions you do not want to be making at 2am.

  • Pre-approved holding statements for every situation type you can reasonably anticipate, reviewed by counsel where appropriate.
  • A notification order: who hears it first, who hears it next, who hears it last. Employees before customers before media is the default in most cases.
  • Audience-specific messages, the customer version, the team version, the press version, the social version. The substance is the same, the language and length are tuned to each audience.
  • A list of the 10 to 15 questions you are most likely to be asked, with a prepared bridging answer for each.
  • A pre-decided spokesperson for each situation type, with a named backup. Two people authorized to speak. Everyone else points reporters to them.
  • A monitoring channel for each platform where the situation is most likely to surface, Google reviews, the specific Facebook page, your inbox.
  • A contact card with legal counsel, your PR support if you have one, and the platform support lines you may need.
  • A simple post-situation review template, so the next plan is sharper than the last.

The situations to plan for

You cannot plan for everything. You can plan for the predictable 95 percent. For most organizations, that includes:

  • A negative review on a public platform that starts attracting other comments.
  • A customer complaint that moves from email to social media.
  • An employee incident, an arrest, public misconduct, or a viral video involving someone on your team.
  • A leadership transition, departure, or unexpected absence at a sensitive moment.
  • A product or service failure that affects multiple customers at once.
  • A media inquiry from a local outlet about something happening at or near your organization.
  • A personal moment involving the owner or executive that becomes public.
  • A vendor, supplier, or partner that fails in a way that affects your customers.

What most plans miss

  • A clear "who is allowed to speak" rule. When everyone might be a spokesperson, no one is, and the messaging fractures the moment a reporter calls.
  • A backup person if the primary spokesperson is unreachable. Plans built around one person fail when that person is on a plane.
  • A line for "we are still gathering facts." Most plans have a response for confirmed situations but no language for the first hour of a developing one.
  • A defined trigger for activating the plan. Without one, the plan sits in a drawer while the team debates whether the moment qualifies.
  • A post-situation review. The plan that does not get sharper after each real-world test is the same plan that fails the same way twice.
  • A version-controlled location for the document. Plans saved as "FINAL_v3_actually_final.docx" are not deployable in a crisis.

Frequently asked questions

What is a communication preparedness plan?

A communication preparedness plan is a written document that holds your pre-approved language, your notification order, and your audience-specific messages for every situation you can reasonably anticipate. It is built during quiet periods so that when a situation lands, you are deploying language you have already vetted instead of writing from a panic.

What situations should the plan cover?

Cover what you can predict. For most organizations that means a bad review, a customer complaint going public, an employee incident, a leadership transition, a product or service failure, a media inquiry, and a personal moment involving the owner or executive that becomes public. You can anticipate roughly 95 percent of what will come at you. Plan for the predictable 95, not the unknowable 5.

How often should I update the plan?

Quarterly at minimum, and any time you have a real-world situation worth learning from. Plans go stale when contact lists, team roles, brand voice, or the legal landscape change. A plan that has not been touched in 18 months is almost certainly wrong somewhere.

Who needs a copy of the plan?

Your immediate response team, your legal counsel, and one designated backup person who can access it if the primary owner is unreachable. Do not put the full plan on a shared drive everyone can edit, pre-approved language gets diluted when too many hands edit it. One owner, named in writing.

What is the single most common mistake in these plans?

Confusing a contact list with a plan. A list of phone numbers is not preparedness. The plan is the language you will use, the order you will reach people in, and the decisions you have made in advance about who can speak and what they are authorized to say. The contact list is one appendix in that larger document, not the document itself.

Ready to respond with control?

Tell Steady what is happening. She will help you know what to say next.

Your conversations are private and never sold or shared with third parties. Anonymized data may be used internally to make Steady smarter over time. You can opt out in your account settings.