Creating a Crisis Communication Plan Before the Story Moves

Public relations works best when the difficult decisions are made before pressure arrives. A fast-moving story can move through journalists, social feeds, employees, customers, and partners within minutes. Without agreed roles and routes, teams pause to ask who can speak, what is known, and who must approve a reply. That hesitation becomes part of the story.

This guide explains how to prepare a clear operating system for communications: who does what, what a holding statement contains, and how an approval path keeps decisions fast without making them careless. It also sets out practical steps to create a crisis communication plan for a small team that has limited time and no large press office.

Start with a shared definition of a crisis

A crisis is not simply a problem. It is an issue that creates material risk to people, operations, reputation, or trust, and that requires coordinated action under time pressure. A product safety concern, a data incident, a serious allegation, a workplace event, or a sudden service outage can all qualify. The threshold should be written down so people do not waste time debating labels.

Define three levels of response. A monitoring level means the team watches a developing issue and keeps basic facts current. An active response level means external interest is growing, and the organization needs a named lead, regular updates, and prepared statements. A major incident level means leadership must meet frequently, legal or regulatory duties may apply, and communication must be tightly coordinated with operational response.

Include a short list of triggers: media inquiries about a sensitive topic, misinformation spreading at speed, a service failure affecting many customers, or a credible safety concern. Triggers are not predictions. They are cues to activate the plan early.

Define roles before the first inquiry

Small teams often assume everyone will simply help. In practice, unclear ownership creates duplicated work and contradictory messages. Assign named roles, with a deputy for each critical position.

• Response lead: coordinates the plan, convenes updates, and keeps actions moving.
• Message owner: drafts the holding statement, key facts, and question-and-answer guidance.
• Approval path owner: confirms who must review and sign off at each level.
• Media and channel owner: handles inquiries, publishes updates, and monitors coverage.
• Internal liaison: briefs employees and managers, collects questions, and flags concerns.
• Fact checker: verifies names, times, numbers, and claims before release.

Write down contact details, working hours, and backup arrangements. Decide who can act when the primary approver is unavailable. If legal or regulatory advice is needed, identify how that person will be reached and what decisions require their input.

Build a holding statement that buys time honestly

A holding statement is a short, early message used when facts are incomplete. Its purpose is not to explain everything. Its purpose is to show that the organization is aware, taking the issue seriously, and working to establish what happened.

A useful structure is simple:

• Acknowledge the concern without speculation.
• State what the organization is doing now.
• Give a next update time or a clear route for further information.
• Provide a contact for urgent questions.

For example: “We are aware of reports concerning [issue] and are gathering verified information. Our priority is [people, safety, service continuity]. We have activated our response team and will provide a further update by [time]. Media questions can be sent to [contact].”

Keep a template library for likely scenarios, but never publish a scenario template as if it were a confirmed account of events. Replace placeholders only with verified facts. Avoid blame, jokes, defensive language, and promises that cannot be kept. If the organization made an error, say so plainly once the facts support it.

Map the approval path for speed and control

Approvals should be designed, not improvised. For each response level, list who must review the message, in what order, and within what time target. A practical path for a small team might be: response lead confirms facts, message owner drafts, fact checker reviews, designated leader approves, and channel owner publishes. Legal or regulatory review is added when the issue involves liability, privacy, safety, employment, or reporting obligations.

Set time limits for each review. If an approver does not respond within the agreed window, define who may escalate or proceed. Record the final wording, approver, and publication time so the team can avoid accidental contradictions later.

Separate operational decisions from communication decisions, but keep them connected. Communications should not promise actions that operations cannot deliver, and operations should know what has already been said. Schedule short, regular updates: for example, every 30 minutes during a fast-moving incident, then less frequently as facts stabilize.

Create steps to create a crisis communication plan for a small team

Use a focused process that can be completed in a few working sessions.

• List likely scenarios. Consider service failures, safety issues, data concerns, allegations, employee matters, and external events that could affect the organization.
• Set response levels and triggers. Decide what activates monitoring, active response, and major incident procedures.
• Assign roles and deputies. Name people, not job titles alone, and confirm contact details.
• Prepare holding statements. Draft short templates with placeholders and clear instructions for verification.
• Map approvals. Write the review order, time targets, escalation route, and exceptions.
• Build channel lists. Identify the website, email, social accounts, employee channels, media contacts, and customer support routes that will be used.
• Create a fact log. Track confirmed information, source, timestamp, owner, and any corrections.
• Agree on internal updates. Decide how employees hear news before or at the same time as the public, where appropriate.

Keep the plan in a place everyone can access, including a printed copy. Make it short enough to use under stress, with links to longer guidance rather than dense paragraphs.

Practice, review, and improve

A plan is only credible if people have used it. Run a short tabletop exercise with a realistic timeline. Give the team a new fact every few minutes and ask them to produce a holding statement, choose an approval route, and brief employees. Notice where questions cluster: unclear ownership, missing contacts, slow approvals, or unverified numbers.

After each real incident or drill, record what worked, what delayed the response, and what information was missing. Update templates, role lists, and escalation times. Review the plan after major organizational changes, such as new products, new markets, leadership changes, or revised legal obligations.

When a story breaks, calm communication comes from preparation. Define the roles, write the holding statement, and settle the approval path while the day is still quiet. That preparation gives a small team the confidence to respond quickly, accurately, and with respect for the people affected.