A practical crisis-communication toolkit with stakeholder matrix, initial holding statement, SITREP, approval matrix, fallback-channel design and communication log.
Crisis communication is an operational control: it reduces uncertainty, directs safe behaviour and preserves trust while facts are changing. The template below separates audience, message objective, approval, channel, fallback and cadence so that communication can continue even if a normal platform is unavailable.
Stakeholder communication matrix
Audience
Needs
Owner/approver
Primary / fallback
Trigger or cadence
Employees
Safety, work location, what to do/not do, escalation route
Incident lead / HR or communications
Collaboration/email / SMS-hotline
Activation, material change, stand-down
Customers/users
Service impact, safe alternatives, expected next update
Service owner + communications
Status page/app/email / call-centre script
Material service impact
Regulator/authority
Facts required by applicable obligation, impact, controls, recovery status
Compliance/legal
Regulatory channel / approved alternate
As required by applicable rule; validate deadline
Supplier
Priority, incident reference, requested action, ETA and next checkpoint
Verified facts, public safety/service guidance, spokesperson
Communications lead
Website/media statement / alternate channel
When public interest or misinformation requires it
Initial holding statement template
What we know: We are experiencing disruption affecting [service/channel] from approximately [time]. What customers should do: [safe action or alternate route]. What we are doing: Our response teams are working to restore service and protect [relevant priority]. What we do not yet know: [avoid speculation]. Next update: We will provide another update by [time/channel], or sooner if there is a material change.
SITREP template
Field
Content
As of
Exact time/time zone and reporting period
Situation
Verified facts only; what changed since previous update
Business impact
Services, customers/locations, volume/backlog, MBCO/RTO status
Technology / facilities / supplier status
Key recovery workstreams and blockers
Actions completed
What has actually been done
Decisions required
Decision, options, owner and latest useful decision time
Risks / assumptions
Unverified or changing factors
Communications
Messages issued, audiences, next planned update
Next milestones
Expected checkpoints rather than unsupported restoration promises
Next SITREP
Time and owner
Approval matrix
Message type
Draft owner
Required review
Speed design
Employee operational instruction
Response/HR
Safety/HR/incident lead as relevant
Pre-approved templates for first notification
Customer service status
Service + communications
Service owner; legal/compliance when needed
Pre-approved factual structure, variable fields
Regulatory notification
Compliance/legal
Designated accountable owner
Obligation-specific process and evidence
Media statement
Communications
Executive/legal as required
Named spokesperson and alternate
Common communication failures
Promising a restoration time before recovery teams have enough evidence.
Using different facts across status page, call centre and internal messages.
Failing to time-stamp messages, so old screenshots continue circulating.
No fallback when email/collaboration/identity is part of the outage.
Mixing confirmed facts with assumptions.
Ignoring accessibility, language or vulnerable-customer needs.
Failing to record what was sent, approved and when.
Leaving the audience without a next-update time even when restoration ETA is unknown.
Communication log
Time
Audience
Channel
Message/version
Approved by
Outcome/questions
09:20
Employees
Emergency notification
EMP-01
Incident lead
92% acknowledgement; alternates called
09:30
Customers
Status page
CUS-01
Service owner
High traffic; FAQ updated
09:45
Executives
SITREP
SIT-01
Incident commander
Decision on capacity prioritisation approved
Crisis message approval matrix
Audience
Message owner
Approver
Target cadence
Fallback channel
Employees
HR / incident communications
Incident lead
At activation + material change
SMS / emergency notification
Customers
Service/customer communications
Business executive + legal/compliance as needed
Initial acknowledgement + ETA cadence
Status page / SMS / call centre script
Regulators / authorities
Compliance / legal
Named accountable executive
Per applicable requirement
Approved alternate contact route
Suppliers
Supplier owner
Operations lead
At dependency impact + recovery changes
Emergency phone / alternate email
Media / public
Corporate communications
Authorized spokesperson
As approved
Pre-approved holding channel
SITREP data fields
Incident name, severity, start time and current phase.
Services/locations/customers affected and what is not affected.
Current minimum service / workaround capacity compared with required MBCO.
RTO/impact-tolerance clock and recovery estimate confidence.
Technology, supplier, workforce and facility dependencies blocking recovery.
Safety, legal, regulatory, privacy or financial consequences.
Decisions made, owner and timestamp.
Actions due before next update.
Next SITREP time and approved distribution list.
Holding statement drafting checklist
State only facts that have been verified.
Acknowledge impact without speculating on cause when investigation is incomplete.
Explain what customers/employees should do now, if anything.
Give the next update time rather than an unverified recovery promise.
Route safety, legal, privacy, regulatory and market-sensitive language through the correct approval path.
Keep internal operational detail out of public statements unless there is a clear reason to disclose it.
Maintain one source of truth so web, call-centre, social and executive messages do not contradict each other.
Communication log fields
Field
Example
Time
10:35 local
Audience
Priority customers
Channel
Status page + email
Message version
v2 approved
Approved by
Incident lead / legal as applicable
Key statement
Service degraded; priority transactions available through alternate route