Crisis and Risk Communications: Building a Message Cadence That Holds Up Across a Multi-Day Incident
The first statement in a crisis matters. But when disruption lasts for days, or one problem triggers another, people need more than a strong opening message. They need reliable updates, clear instructions, and a way to understand what has changed.
For corporate organizations and academic institutions, that takes a communications process built to continue across audiences, channels, and shifts. A dependable cadence does not mean promising constant updates. It means setting realistic expectations, sharing verified information consistently, and having a clear process for the next message, even when key people are unavailable.
Start by separating audiences and information needs
A single incident can create different questions for employees, students, customers, families, media, and community members. They may need related facts, but they do not all need the same message.
Internal workforce messages should help employees, faculty, and staff understand what to do and how the incident affects their work. Depending on the situation, that could include protective actions, facility or service status, work arrangements, manager instructions, and where to get help.
External messages should address the needs of the people outside the organization who are affected or seeking information. Students, customers, families, community members, media, and other stakeholders may need to know whether a service is available, what action they should take, where to find assistance, and when another update is expected.
The underlying facts should remain consistent, but the level of detail and the call to action may differ. A staff notice might explain internal procedures. A public update might focus on service status and practical guidance. Media communications may require a designated spokesperson and a concise summary of verified information.
The CDC’s guidance on messages and audiences emphasizes understanding audiences’ different relationships to an emergency, communication needs, and access requirements. Segmenting audiences before an incident helps teams prepare messages that are relevant without creating conflicting versions of events.
Set an update rhythm without promising what you cannot deliver
People need to know when to look for new information. But a rigid promise, such as an update every hour, can become unrealistic when facts are difficult to verify, operations are stretched, or there is no meaningful change to report.
Instead, define a planned update cadence and event-based triggers. The planned cadence gives people predictable check-in times. Event-based triggers prompt a message sooner when a material change occurs, such as a new safety instruction, a significant change in service availability, or a correction to previously shared information.
A practical cadence might look like this:
During the initial response: Publish a holding statement once essential facts and immediate instructions are verified. State what is known, what remains uncertain, what the organization is doing, and when the next update is expected.
During active disruption: Set scheduled update windows appropriate to the pace and impact of the incident. If there is no substantive change, say so briefly and confirm the next planned update.
As the situation stabilizes: Move to less frequent, predictable updates while continuing to communicate significant changes promptly.
During recovery: Explain which services or activities are returning, what remains disrupted, where to find support, and when updates will transition or conclude.
These are planning principles, not a universal timetable. The interval should reflect the incident, the audience’s needs, and the organization’s ability to verify information. Avoid estimates that depend on unresolved decisions. If the timing is uncertain, say that it is being assessed and provide a specific time for the next update, not a speculative estimate for full restoration.
A holding statement is useful when important details are still being confirmed. It should not become a substitute for meaningful follow-up. When the next update arrives, clearly identify what is new, what is unchanged, and what people should do now.
Build a spokesperson bench and approval process
A communications plan that depends on one spokesperson or one executive is vulnerable to absence, fatigue, and competing responsibilities. Identify a primary spokesperson and trained alternates, and specify who may speak to which topics. For example, operational updates, academic or workforce impacts, and technical issues may require different subject-matter support.
The approval process also needs to work outside normal business hours and across shift changes. Define:
Who drafts: A designated communications lead or team member.
Who verifies: The operational or subject-matter owner responsible for confirming facts and instructions.
Who approves: The authorized decision-maker, or approved alternate, under the organization’s plan.
Who publishes and monitors: The person responsible for releasing messages across channels and tracking questions or corrections.
Use pre-approved templates for routine updates, with additional review when a message raises sensitive legal, privacy, security, or regulatory issues. The aim is not to bypass appropriate review; it is to avoid sending every routine status note through an unclear chain of approvals.
At each shift handoff, transfer the current situation summary, verified and unverified information, pending decisions, messages already released, inquiries requiring follow-up, and the next update deadline. A handoff should also identify who now owns drafting, approval, spokesperson duties, and publication.
Use more than one channel, and make messages accessible
A message posted on one website or sent through one system may not reach everyone. Technical outages, power loss, connectivity problems, and differences in communication access can all affect delivery. Plan a small number of complementary channels, with a clear source of truth, such as an incident or status page, and a process for distributing matching updates through other channels.
Depending on the audience and incident, channels may include email, text or emergency notification systems, an intranet, a public website, social platforms, a hotline, recorded messages, briefings, or printed notices. FEMA’s PIO guidance describes coordinated public information, multiple dissemination methods, and planning for the duration of communications operations.
Accessibility should be part of message preparation, not an afterthought. Consider plain language, translation needs, screen-reader-compatible formats, readable contrast, captions and transcripts, and alternative ways to receive urgent information. Provide a non-digital option when practical, such as a staffed phone line or posted notices at a designated location. The right mix will depend on the people affected and the channels available to them.
Consistency does not mean copying the exact same text everywhere. It means maintaining the same verified facts, instructions, and next-update expectation while adapting length and format to the channel and audience.
Keep a record of what was communicated and when
A message record helps teams coordinate their response, answer follow-up questions, correct errors, and review what happened afterward. It is not a guarantee of legal protection, but a clear record can support accountability and a more reliable after-action review.
For each communication, record the incident or situation, date and time with time zone, intended audience, channel, message owner, approver, version, release time, and where the message appeared. Keep the exact text or a link to it. Note what facts informed the message, what remained uncertain, any accessibility or language versions, and when the next update was due.
Do not overwrite an earlier message when a correction or new version is issued. Preserve the sequence and label updates clearly so readers and staff can tell which information is current. Keep records in an approved location and follow organizational policies for sensitive or personal information.
Practice the process across multiple operational periods
A one-time media statement exercise cannot show whether a communications system will hold up over several days. Practice the cadence, handoffs, approval workflow, spokesperson alternates, accessible formats, and recordkeeping together.
A tabletop or simulation can begin with incomplete information, then introduce changing operational impacts, a shift change, an unavailable approver, a rumor, a request from families or media, and a need to correct earlier information. Ask participants to produce distinct internal and external updates and document who verified, approved, and released each one.
Evaluate more than the wording. Did the team meet its promised update time? Were facts consistent across channels? Could an alternate take over? Did the message reach people who needed an accessible format? Could the team find the exact version that was sent? Did people know when to expect the next update?
These are practical objectives for a crisis exercise. Alpha Research Group’s article on designing corporate crisis exercise simulations discusses setting clear learning objectives, observing performance, and turning findings into corrective actions. Repeating the communications process in exercises helps teams identify gaps before the pressure of a real incident.
A strong multi-day communications plan is not measured by how often it publishes. It is measured by whether people receive accurate, useful updates through a process that can continue as conditions and personnel change.
To develop practical crisis and risk communications capabilities for your organization, visit Alpha Research Group.
Comments