Your crisis communications plan may name the right people. A test asks whether they can actually reach one another, agree on the facts, and release a useful message under pressure.
Set the testing schedule around those decisions, not the age of the document. Make room for a full-team rehearsal, smaller drills between rehearsals, and a new test when a change affects the response.
How often should a crisis communications plan be tested?
Use one full-team exercise each year and short, focused drills each quarter as a starting schedule. Retest affected parts after leadership changes, new channels, a real incident, or a failed exercise. This is a planning recommendation, not a compliance standard; set the final cadence with your risk and legal teams.
What should your testing calendar include?
Give each session a different job. Use the annual rehearsal to test the whole response, a quarterly drill to test one dependency, and a change-triggered test to check something that has just moved.
| When | Exercise | What to test |
|---|---|---|
| Once each year | Full-team rehearsal | Work through escalation, fact checks, message approval, stakeholder updates, and media response together. |
| Each quarter | Focused drill | Choose one task: reaching backups, approving a holding statement, accessing publishing tools, or handling a reporter inquiry. |
| After a material change | Targeted retest | Check the changed role, channel, supplier, location, or approval route before relying on it. |
| After an incident or failed exercise | Corrective retest | Repeat the task that failed after assigning and completing the repair. |
Put an owner and a purpose beside each date. Instead of booking a vague crisis meeting, schedule a drill to approve an employee update while the usual approver is unavailable. That gives the team a specific task to perform and evidence to review.
Is one annual test enough?
Do not make that decision from the calendar alone. Ask what has changed since the last rehearsal and which tasks remain untested. If you have replaced your spokesperson, added a customer channel, or changed who can publish a statement, test those changes rather than waiting for the annual session.
For a small team, keep the quarterly work narrow. You could test the contact tree in one session and backup website access in another. For a larger organization, rotate teams and locations so the same confident group does not carry every rehearsal.
Have the people responsible for risk and legal obligations set any required frequency. Treat this schedule as an operating proposal, not a substitute for that assessment.
Why is reviewing the plan different from testing it?
A review checks the document. An exercise asks people to use it. Keep both on the schedule, but record them separately.
During a review, check names, phone numbers, roles, access instructions, and approval rules. During an exercise, ask the backup approver to make a decision, ask the channel owner to prepare an update, and ask the spokesperson to handle a simulated question.
Use the crisis response plan as a working reference, not a memory test. Let participants look things up. Record where the instructions are missing, hard to find, or open to different interpretations.
If the team must invent an approval route during the rehearsal, write down the route it chose. Then have the responsible leaders decide whether that route belongs in the plan.
Which changes should trigger an earlier test?
Retest when a change affects who decides, what the team knows, or how it communicates. Start with these triggers:
- People: A new executive, spokesperson, legal contact, agency partner, or backup takes on a response role.
- Channels: You add a status page, customer messaging tool, social account, or employee communication channel.
- Operations: A launch, acquisition, new location, or supplier change introduces a response task the team has not practiced.
- Access: Permissions, sign-in methods, or publishing responsibilities change.
- Learning: An incident or exercise exposes a missed audience, disputed approval, or failed handoff.
Match the retest to the change. A new spokesperson calls for a media-response rehearsal. A new publishing system calls for an access and draft-publication check. Neither automatically requires repeating every part of the annual exercise.
Record what was tested, who took part, and what remains open. Keep the distinction between completing a session and fixing the problem it exposed.
How do you run a useful communications exercise?
Build the rehearsal around a decision your team must make with incomplete information. Choose a scenario relevant to the business, but use fictional names and details. Keep all messages in a sandbox and label them as exercise material. Do not send test statements to real customers or journalists.
Start with a clear situation and limited facts
Try this fictional scenario: a customer-facing service stops working, employees are asking what to say, and a reporter requests a comment. The technical team has confirmed the outage but has not confirmed its cause or recovery time.
Give participants that information—and no hidden answer sheet. Ask them to identify the response lead, the source of operational facts, the message approver, and the person responsible for each audience.
Set a time budget for the exercise. Make clear that it is a rehearsal target, not a legal notification deadline or a promise about real response times.
Require a message, not just a discussion
Ask the team to draft a short initial statement. It should distinguish known facts from open questions, explain where affected people can get updates, and state when the team intends to provide another update.
Then ask for separate employee and customer versions. Keep the underlying facts consistent while making the instructions relevant to each audience. Have the designated approvers review the drafts through the process written in the plan.
For media response, assign someone to play the reporter. Ask follow-up questions about cause, impact, and recovery. Let the spokesperson practice saying what is known without guessing at answers the team does not have.
Change one condition during the rehearsal
Make the usual approver unavailable. Or tell the team that its normal internal messaging tool cannot be used. Choose one disruption so you can see which backup process participants follow.
Observe the handoff. Who notices the problem? Who has authority to use the alternative? Can the team find the approved fallback without asking the facilitator to solve it?
Do not score participants on how confidently they speak. Record the decisions, drafts, access checks, and handoffs they complete.
Finish with a repair and a retest date
Debrief while the choices are fresh. Separate missing instructions from access problems, skill gaps, and unresolved leadership decisions. Assign each repair to one owner with a completion date.
For every failed task, name the evidence that will show it has been fixed. Then schedule the smallest retest that can produce that evidence.
How should you measure whether the plan works?
Set pass criteria before the exercise. Use measures tied to the work, not a single score that hides a failed approval or an unreached audience.
| Task | Evidence to capture | Question to resolve |
|---|---|---|
| Activate the team | A contact log showing acknowledgments, missed contacts, and backup use. | Did every required role have someone available to act? |
| Approve the message | A draft history and decision log, including elapsed time. | Was approval clear, and did it meet the target set before the exercise? |
| Maintain accuracy | The fact list compared with each approved draft. | Did any message introduce an unsupported cause, impact figure, or recovery promise? |
| Reach each audience | Prepared channel-specific updates and sandbox access checks. | Was an owner able to prepare an update for every audience in scope? |
| Close the gaps | An action log with owners, deadlines, and retest results. | Did the repair work when the team repeated the failed task? |
Review speed alongside accuracy. Do not reward a fast draft that guesses at the cause or makes a promise the operations team has not supported. Likewise, examine a careful statement that gets stuck because nobody knows who can approve it.
Compare repeated tests only when the task and conditions are comparable. Keep the scenario, participants, constraints, and target beside the result so leaders can understand what was actually tested.
What mistakes should leaders avoid?
Testing only when everyone is available. Include a backup decision-maker in the rehearsal and give that person real authority within the exercise. Do not let the usual executive quietly make every decision from the sidelines.
Letting the facilitator rescue every handoff. Record confusion before explaining the intended process. Otherwise, you are testing the facilitator's knowledge rather than the team's use of the plan.
Treating public relations as the whole response. Give operations responsibility for operational facts, legal responsibility for legal decisions, and communications responsibility for preparing and coordinating messages. Have leadership settle disputed boundaries before the next test.
Closing the exercise without closing the work. A revised paragraph is not enough evidence that an approval or access problem has been solved. Repeat the affected task and keep the result with the action log.
When should you involve a crisis communications agency?
Consider outside support when your team needs an exercise facilitator, additional media-response practice, or help coordinating responsibilities across internal teams. Define the gap before choosing a firm.
Use this guide to what a crisis communications agency does to frame the role you want evaluated. For a testing engagement, ask who will design the scenario, who will observe decisions, what records you will receive, and whether the scope includes a corrective retest.
When comparing crisis management firms, separate rehearsal support from incident-response support. Ask which internal and external communication tasks are included. Do not assume that a broad crisis management PR scope answers every question about employee updates, customer notices, or publishing access.
For Percepture's service context, review crisis communications services. Bring a concrete brief to any provider discussion: the scenario to test, the roles involved, the last exercise date, and the open tasks you want examined.
Start your next rehearsal with one question: what must this team demonstrate that it has not demonstrated yet? Put that task on the calendar, capture the evidence, and retest the repair—not just the document.
About Bob Generale
Bob Generale is President of Percepture.
