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 role-based coordination template for incidents that require operational facts, leadership decisions, and consistent communication with external and internal audiences. It includes role slots for an Incident Executive, Crisis Communications Lead, Incident Commander or Security Lead, General Counsel or Legal Lead, Public Relations Lead, Customer Success Lead, and employee or executive communications. Cloning teams assign people to these roles; the template does not prescribe named individuals.
Its task lists follow the response lifecycle: Stage 1 — Stabilize and Establish Facts, Stage 2 — Prepare and Approve Messaging, Stage 3 — Release and Monitor, and Stage 4 — Resolve and Close Out. A separate Priority Triage list uses RICE scoring to help compare response work. Milestones mark the first fact base, approved holding statement, audience readiness, coordinated update, stabilization assessment, and closure retrospective. The active response pulse is every four hours, alongside an executive review and a one-time retrospective after stabilization.
Use this workspace when multiple functions need shared ownership and an explicit approval path during a high-impact event. It is not a substitute for an incident-management system, legal counsel, a security runbook, or an emergency notification service. Before use, tailor the roles, decision rights, and check-in cadence to the incident; do not release unverified facts or assume that completing a milestone satisfies a regulatory duty.
Standards & compliance context
- Have General Counsel or the designated Legal Lead assess applicable notification duties, timelines, and jurisdictional requirements for each incident; this workspace does not establish compliance.
- Follow organizational policies for preserving incident records and approvals, and use approved systems for any evidence or sensitive material that should not be stored in a general workspace.
- Review default visibility before adding customer, employee, security, or legal information, and limit workspace details to the audience authorized to access them.
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 member slots clarify who leads, approves, advises, and communicates without tying the reusable 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
Check ins
Defined check-in cadence gives responders and executives predictable moments to review facts, decisions, and blockers.
- Active response pulse — Every 4 hours
- Executive decision review — Weekly Mondays
- Response retrospective — One-time after stabilization
Milestones
Milestones show whether the response has established facts, prepared audiences, released updates, and reached a documented closeout.
-
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.
To-do lists
Stage-based task lists organize work from fact-finding through approval, release, resolution, and priority triage.
-
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 helps the team make progress and remaining uncertainty visible as the incident evolves.
-
Crisis response trajectory
Track whether each workstream is still discovering the problem or is executing a known response toward stabilization and closure.
How to use this template
- Clone the workspace and tailor role slots to the functions needed for this incident, keeping roles as placeholders until the responding people are assigned.
- Confirm the Incident Commander, executive decision owner, message approvers, default visibility, and escalation path before adding sensitive incident details.
- Work through Stage 1 to establish a shared fact base, label assumptions for validation, and assign a DRI and due point to each open action.
- Draft audience-specific messaging in Stage 2 and obtain the required Legal, executive, and communications approvals before moving release work into Stage 3.
- Run the active response pulse every four hours, update milestones and the crisis response trajectory, and record decisions and blockers on the message board.
- After stabilization, complete the closure tasks, hold the one-time retrospective, and assign DRIs to follow-up actions with clear next steps.
Best practices
- Assign each task a single DRI and make the approving decision-maker explicit when the task involves a public or employee statement.
- Separate confirmed facts from assumptions and give each unresolved fact an owner and a validation action.
- Use the every-four-hours pulse for status, blockers, and decisions, and change the cadence deliberately when incident tempo shifts.
- Keep the first holding statement narrow, factual, and approved; do not imply certainty about impact or cause before verification.
- Use RICE as a triage aid, but let incident leadership account for safety, legal deadlines, and time-critical risk when ranking work.
- Set default visibility deliberately and avoid placing sensitive personal, security, or legal details where the full workspace audience can see them.
- Update milestones and the hill chart at each pulse so leaders can distinguish progress from unresolved risk.
- Use the retrospective to turn response gaps into assigned follow-up tasks rather than leaving lessons as unowned notes.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What kinds of incidents is this workspace designed for?
It is structured for high-impact events that need coordinated communications, such as a data breach, executive departure, or public-facing service failure. The role slots and stages help bring legal, incident leadership, PR, customer success, and employee communications into one response. Adapt the task lists and audiences to the incident rather than treating every crisis as the same.
How often should the crisis response check-ins run?
The active response pulse is set to every four hours, which gives the team a defined cadence for sharing confirmed facts, blockers, and decisions while the situation is moving quickly. The executive decision review is scheduled for Mondays and can be adjusted if the incident needs a different leadership cadence. The retrospective is a one-time check-in after stabilization.
Who should run this workspace?
The Crisis Communications Lead can maintain the workspace and check-in cadence, while the Incident Commander or Security Lead owns operational facts and response status. The Incident Executive is accountable for major decisions, with Legal, PR, Customer Success, and Employee Communications contributing to their respective audiences. Confirm the DRI for each task and the approval authority for each message before publishing.
Does this template ensure regulatory compliance during an incident?
No; it provides coordination structure, not legal advice or a compliance determination. General Counsel or the designated Legal Lead should assess applicable notification duties, deadlines, preservation requirements, and jurisdiction-specific rules for each event. Record the decision owner and approved next steps in the workspace without treating a template milestone as proof that a legal obligation has been met.
What is a common pitfall when using this crisis workspace?
A frequent failure is drafting external messaging before the team has established a shared, verified fact base. Keep confirmed facts distinct from assumptions, assign an owner to validate uncertain information, and route statements through the agreed approval path. Also avoid leaving tasks without a DRI or allowing the message board to go quiet between check-ins.
Can we customize the roles, stages, and priorities?
Yes; replace role slots with the functions needed for your incident, while keeping placeholders role-based so each cloned workspace can assign the people on duty. Adjust stage task lists and milestones to match your decision and communications workflow. The Priority Triage list uses RICE scoring as a starting point, but incident leaders should adapt scoring criteria to urgency, risk, and response constraints.
Does the template connect to incident or communications tools?
The workspace template defines the structure created when a workspace is cloned: members, task lists, milestones, custom fields, check-ins, hill charts, risks, and a welcome post on the message board. It does not create integrations or chat channels. Use your organization’s approved incident systems separately and record the relevant status or decision in this workspace.
How should we roll this out during an active crisis?
Clone the workspace, assign role slots to the available responders, and confirm the Incident Commander, executive decision owner, and communications approvers. Establish the fact base and the first check-in before drafting audience-specific statements. Then work through the milestones in sequence, updating owners and decisions as the response changes.
How is this better than coordinating in an ad-hoc document or email thread?
The template makes stages, role ownership, milestones, and check-in cadence visible in a shared workspace instead of scattering them across separate conversations. That helps responders see what is confirmed, what is awaiting approval, and who owns the next action. It still depends on disciplined updates; a workspace does not replace direct escalation for urgent decisions.
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...
-
Learn how connecting knowledge workers, crowdsourcing ideas, and unifying project collaboration on one platform drives measurable business value for your...
-
The 10 requirements a frontline employee app must meet before you see a demo: offline access, translation at publish, site targeting, acknowledgment, and more.
-
MangoApps search is 5x faster with AI image search and smarter news feed updates for a more relevant modern intranet.
-
Build the business case for frontline communication with a model you can run on your own numbers: turnover, supervisor time, and duplicate software costs.
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.
