Crisis Communications
Crisis Communications is a ready-to-clone workspace for coordinating facts, decisions, approvals, stakeholder updates, and external messaging during an active incident.
Every employee gets a seat — priced per employee in AI Productivity, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Technology And Saas · Financial Services · Healthcare And Life Sciences · Retail And Consumer Services · Public Sector And Education
Overview
The Crisis Communications workspace is a staged command center for an active incident that requires one coordinated fact base, clear decision ownership, and controlled messaging. It brings legal, PR, communications, customer success, incident response, and executive roles into channels that follow the actual crisis workflow: kickoff triage, day-to-day operations, decisions and approvals, external messaging, internal stakeholder updates, and retrospective closeout.
Its task lists move the response from stabilization and fact gathering through message approval, release and monitoring, resolution, and closure. The Priority Triage list uses RICE scoring to help compare competing communication tasks when time and attention are limited. Milestones mark concrete outcomes such as establishing the first fact base, approving a holding statement, preparing customer and employee responses, releasing a coordinated update, and completing the retrospective. The Crisis response trajectory hill chart shows whether the team is progressing toward stabilization.
Use this template when an incident has cross-functional consequences or public, customer, employee, executive, or regulatory audiences. Do not use it as the sole system for physical emergencies, technical incident execution, legal advice, or confidential investigations. Keep technical event data in the incident management platform and apply a restricted visibility model to privileged, personal, and security-sensitive information.
Standards & compliance context
- Use the workspace to document approvals and communication timelines, while legal and compliance owners determine whether privacy, breach notification, securities, employment, or sector-specific obligations apply.
- Keep privileged legal advice and regulated personal information in approved restricted systems, and configure workspace visibility and retention according to organizational policy.
- Preserve the decision and approval log and approved message register when organizational policy or applicable law requires an auditable incident communication record.
- Coordinate public statements with the designated legal, security, investor relations, and regulatory contacts before release when the incident may trigger formal disclosure duties.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Members
Role-based members establish the RACI structure for crisis ownership without tying the template to specific people.
- Incident Executive
- Crisis Communications Lead
- Incident Commander or Security Lead
- General Counsel or Legal Lead
- Public Relations Lead
- Customer Success Lead
- Executive Communications Lead
- Employee Communications or HR Lead
- Support Operations Lead
- Compliance or Privacy Lead
- Executive Assistant or Workspace Coordinator
- Subject Matter Expert
Channels
Workflow-specific channels separate triage, operations, approvals, external messaging, internal updates, and closeout so information reaches the right audience.
-
kickoff-triage
Initial incident framing, severity assessment, known facts, unknowns, and immediate assignments.
-
day-to-day-operations
Live coordination of workstream updates, blockers, dependencies, and next actions.
-
decisions-approvals
Record decision requests, approval status, final calls, and rationale.
-
external-messaging
Draft and approve media statements, customer notices, partner updates, regulator responses, and social copy.
-
internal-stakeholder-updates
Coordinate employee, board, leadership, support, sales, and account-team updates.
-
retrospective-closeout
Capture response lessons, unresolved commitments, follow-up actions, and closure communications.
Check ins
Defined cadences create a reliable operating rhythm for fast-changing facts, executive decisions, and post-incident learning.
- Active response pulse — Every 4 hours
- Executive decision review — Weekly Mondays
- Response retrospective — One-time after stabilization
Milestones
Outcome-based milestones show whether the response has moved from fact gathering to approved communication, stabilization, and closure.
-
Command structure and first fact base established
Incident Executive, Communications Lead, workstream DRIs, severity, known facts, unknowns, and next-update time are documented.
-
First holding statement approved
Initial audience-specific holding language has completed required legal and executive review.
-
Customer and employee response ready
Customer-facing and internal teams have approved talking points, escalation routes, and release timing.
-
First coordinated external update released
Approved communications are published through the selected external channels and logged.
-
Stabilization assessment completed
Technical and operational leads confirm current status, residual risk, and whether the response can move toward closure.
-
Closure communication and retrospective completed
Closure or next-phase messaging is approved, the retrospective is recorded, and corrective actions have owners.
Task lists
Stage-based task lists turn the response into assignable work, while RICE Scoring helps prioritize competing communication needs.
-
Stage 1 — Stabilize and Establish Facts
Create a reliable incident picture, assign RACI roles, secure evidence, and set the communication rhythm. The Incident Commander is the primary DRI.
-
Stage 2 — Prepare and Approve Messaging
Develop channel-specific messaging from the approved fact base and route it through documented review. The Crisis Communications Lead is the primary DRI.
-
Stage 3 — Release and Monitor
Distribute approved communications, monitor response, correct misinformation, and maintain an auditable activity log. The Public Relations Lead is the primary DRI.
-
Stage 4 — Resolve and Close Out
Confirm stabilization, communicate closure appropriately, and turn response observations into owned improvements. The Crisis Communications Lead is the primary DRI.
-
Priority Triage — RICE Scoring
Use RICE to prioritize response actions when multiple requests compete: Reach, Impact, Confidence, and Effort. The Crisis Communications Lead maintains the queue; each item has one DRI.
Hill charts
The Crisis response trajectory hill chart shows whether uncertainty is declining and the team is moving toward stabilization.
-
Crisis response trajectory
Track whether each workstream is still discovering the problem or is executing a known response toward stabilization and closure.
Default apps
Default apps provide the working surfaces for conversations, tasks, documents, and response records without requiring a new structure.
Integrations
Integration touchpoints connect operational facts, controlled documents, monitoring signals, customer feedback, and executive scheduling.
- Incident management platform
- Document and knowledge repository
- Media and social monitoring
- Customer support platform
- Email and calendar
Pinned resources
Pinned resources keep the current facts, approvals, message register, audience map, and working agreements visible at the point of action.
- Current situation summary
- Decision and approval log
- Approved message register
- Stakeholder and audience map
- Crisis communications working agreements
How to use this template
- Clone the workspace, replace member placeholders with role-based assignments, set default visibility, and connect the incident, document, monitoring, support, and calendar systems.
- Appoint the Crisis Response Lead and Scribe, publish the Current situation summary, and use kickoff-triage to record known facts, unknowns, assumptions, and immediate risks.
- Assign Stage 1 tasks to named DRIs, map each decision and audience to the appropriate RACI roles, and run the Active response pulse every 4 hours while the situation is changing.
- Draft the holding statement and audience-specific messages in external-messaging, route them through decisions-approvals, and record the final wording and approver in the Approved message register.
- Release approved updates through the appropriate channels, monitor media, social, customer support, and stakeholder signals, and update tasks when new facts change the response.
- After stabilization, complete the stabilization assessment, send closure communications, hold the one-time Response retrospective, and document actions, owners, and due dates in retrospective-closeout.
Best practices
- Use role-based member labels such as Legal Counsel, PR Lead, and Customer Success Lead so the cloned workspace can be reassigned without rebuilding its structure.
- Treat the Current situation summary as the source of verified facts and label unconfirmed reports, hypotheses, and pending approvals separately.
- Keep decisions-approvals focused on consequential choices, with a clear Accountable executive, Consulted specialists, decision deadline, and written outcome.
- Use the external-messaging channel only for draft and approved audience-facing content, never as a substitute for the approved message register.
- Run the four-hour pulse with a fixed format covering new facts, impact, decisions needed, messages due, monitoring signals, and next update time.
- Apply RICE scoring to prioritize communication tasks, then assign every selected task to one DRI with a stage, audience, dependency, and completion condition.
- Restrict default visibility for legal advice, personal information, security details, and employee matters, and share only the minimum necessary context with broader audiences.
- Close every milestone with an artifact such as a fact summary, approved statement, released update, stabilization assessment, or retrospective action list.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What types of crises is this workspace designed for?
Use it for data breaches, executive departures, public-facing failures, major service incidents, and other events requiring coordinated legal, PR, communications, customer success, and leadership work. The channels and milestones support both internal response and external messaging. It is not a substitute for an incident command system, legal advice, or a safety emergency protocol.
Who should run the Crisis Communications workspace?
Assign a Crisis Response Lead or Communications Lead as the DRI for workspace coordination. Map members to roles such as Executive Sponsor, Legal Counsel, PR Lead, Internal Communications Lead, Customer Success Lead, Incident Commander, and Scribe rather than naming individuals. Use a RACI matrix to distinguish who is Responsible, Accountable, Consulted, and Informed for each decision.
How often should the crisis check-ins occur?
The Active response pulse runs every 4 hours while facts and stakeholder impact are changing quickly. The Executive decision review runs Weekly Mondays for ongoing governance, but the response lead can add an ad hoc review when a material decision is blocked. Run the Response retrospective once after stabilization and before closure.
Can this template support regulated incidents?
It can organize evidence, approvals, timelines, and communications for incidents subject to privacy, security, employment, or sector-specific requirements. Legal and compliance owners must determine notification duties, retention requirements, privilege boundaries, and disclosure timing. Do not treat the workspace as a legal determination or as a replacement for an approved incident response policy.
What is the common pitfall when using a crisis communications workspace?
The most common pitfall is publishing an unverified fact or allowing multiple channels to become competing sources of truth. Keep the Current situation summary and Approved message register current, label assumptions clearly, and route public claims through the decisions-approvals channel. Avoid copying sensitive details into broad-visibility channels.
How should we customize the workspace for our organization?
Replace role placeholders with your crisis roster, set default visibility for legal and personnel-sensitive work, and update integrations for your incident management, support, monitoring, and document systems. Tailor the stakeholder and audience map to your customers, employees, regulators, partners, media, and executives. Keep the stage-based task lists, four-hour response pulse, and approval record unless your incident policy specifies a different cadence.
Which tools can this workspace connect to?
The template includes integration touchpoints for an incident management platform, document and knowledge repository, media and social monitoring, customer support platform, and email and calendar. Use the incident platform for technical status, the repository for controlled documents, monitoring for external signals, and support systems for customer impact. Confirm access permissions so integrations do not expose confidential response material.
How does this compare with coordinating a crisis in ad hoc chat?
Ad hoc chat can move quickly but often loses decision ownership, approval history, source facts, and the latest approved wording. This workspace separates kickoff triage, day-to-day operations, decisions and approvals, external messaging, internal updates, and retrospective closeout. It provides a repeatable operating structure while leaving room for incident-specific channels and tasks.
How should we roll it out during an already active crisis?
Clone the template, appoint the Crisis Response Lead, restrict default visibility, and post the current situation summary before inviting the full response group. Establish the first fact base, decision log, audience map, and four-hour pulse immediately. Then assign stage-one tasks before drafting or approving any external statement.
Related templates
Go deeper on the topic
-
Internal communications is how a company talks to itself: news, announcements, leadership messages, safety alerts, and the daily hum of "what's happening...
-
An internal newsletter is a regularly cadenced digest of organizational updates — business news, people news, policy changes, culture moments — sent to the...
-
Frontline communication is how a company reaches the 80% of its people who don't live in email. It's targeted, mobile-first, often bilingual or multilingual,...
-
Enterprise search with RAG (retrieval-augmented generation) answers questions by fetching the company's own content first, then asking a model to summarize...
-
Employee app buyers want less tool sprawl. See why unified platforms that combine communication, tasks, HR, and AI are winning.
-
Learn how connecting knowledge workers, crowdsourcing ideas, and unifying project collaboration on one platform drives measurable business value for your...
-
Discover how MangoApps 19.0 upgrades employee communication with custom push notifications, AI-personalized news feeds, and dynamic audience targeting.
-
Use a frontline intranet buyer’s framework to evaluate mobile access, no-email login, adoption, and operational fit before you buy.
Ready to use this template?
Every employee gets a seat. Request pricing for AI Productivity and we quote into a workspace with Crisis Communications ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
