Crisis Management & Contingency Planning Framework
Create crisis management playbooks for likely scenarios covering response, communication, and recovery. Run simulations to prepare your organization.
Use This When
SOPs, task systems, delegation, automation mapping.
Inputs Needed
Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules.
Expected Output
Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence.
The Workflow Prompt
You are a operations consultant and productivity systems designer. Objective: Crisis Management & Contingency Planning Framework Context: Create crisis management playbooks for likely scenarios covering response, communication, and recovery. Run simulations to prepare your organization. Original task: **Act as a risk management and crisis response specialist. I want to prepare for potential crises that could impact [BUSINESS/AREA]. Likely scenarios include:[LIST SCENARIOS].Create a comprehensive crisis management system including:(1) A scenario assessment of likelihood and impact for 5-10 potential crises(2) A crisis response playbook for each scenario showing decision trees and escalation(3) A crisis communication framework—internal and external messaging(4) Designated crisis leadership and decision-making authority(5) A crisis timeline showing key milestones and decisions(6) Recovery and business continuity protocols(7) A post-crisis review process capturing lessons learned(8) Regular crisis simulation and team training. Include templates for crisis communication, decision logs, and stakeholder updates. Make this actionable and specific to your industry and organization.** Inputs I may provide: Current workflow, tools, people involved, bottleneck, desired output, frequency, approval rules. Operating instructions: - First, restate the objective in one clear sentence. - If critical information is missing, ask up to 5 focused questions. If there is enough information to proceed, make practical assumptions and label them. - Use a Exhaustive response style. - Be specific to the business, audience, channel, and constraints provided. - Avoid generic AI advice. Give concrete recommendations, examples, templates, copy, or steps I can use. - When current facts, competitors, laws, prices, policies, or market claims matter, use current research and cite sources. - Do not expose hidden chain-of-thought. Provide a concise rationale or decision summary instead. - End with a short QA checklist that helps me verify the output. Required output: Workflow map, SOP, automation opportunities, owner/RACI, tools, checklist, maintenance cadence. Caution: Avoid generic output; require concrete examples, assumptions, and next steps.
QA Follow-Up Checklist
After the AI returns its output, verify against:
- Output is specific to the provided business/context.
- Assumptions are clearly labeled.
- No unsupported claims without source checks.
- Next actions are clear and usable.
Follow-Up Prompt
Now turn the result for 'Crisis Management & Contingency Planning Framework' into a client-ready version: tighten wording, remove fluff, add missing assumptions, and provide the next 3 actions.
Avoid / Cautions
Avoid generic output; require concrete examples, assumptions, and next steps.
How Different Verticals Use This Workflow
Restaurant & Hospitality
A 4-location restaurant group builds a crisis playbook for: food safety incident, viral negative review going regional, a key chef quitting publicly, POS system down on a Friday night, and city health inspection failure. Each scenario has decision authority, comms templates, and an annual simulation. Used for real during a 2026 food safety scare, contained reputational damage to one location.
Retail & E-commerce
A DTC brand builds crisis playbooks for: site outage during sale, Shopify/Klaviyo data breach, founder's old tweet resurfacing, a viral product defect, and 3PL warehouse fire. Each playbook has a named owner and a 4-hour activation drill. Tested twice/yr. When their 3PL had a flood, recovery took 6 days instead of expected 4 weeks.
Professional Services & B2B
A 24-person consulting firm builds playbooks for: client confidentiality breach, partner public conflict, ransomware attack, key client lost mid-engagement, and a referenceable founder client publicly criticizing the firm. Each scenario has comms, legal, and operational protocols. Annual tabletop simulation.
Beauty & Personal Care
A medspa chain builds playbooks for: adverse treatment outcome with social media spread, OHA inspection failure, ransomware on patient records, key injector quitting, and Botox supply shortage. Each has medical director protocols, legal templates, and PR scripts. Used 3 times in 2 years, contained each incident.
Local & Trade Services
A residential GC builds playbooks for: jobsite injury, customer threatening lawsuit, subcontractor walking off mid-project, ransomware on Jobber data, and a viral negative review during selling season. Each scenario has insurance contact info, legal counsel on retainer, and tested comms templates.
Frequently Asked
What inputs actually move the needle for a real crisis playbook vs a binder nobody opens?
Three things: 5-10 specific scenarios scored by likelihood and impact (data breach, founder PR crisis, key employee departure, supply chain disruption — not 'a crisis'), named decision-makers per scenario with backup authority, and a simulation cadence (twice/year minimum). Crisis playbooks fail when stored as PDFs that nobody knows exist. They work when teams have rehearsed the playbook recently enough to find the relevant section in under 60 seconds during real chaos.
What's the most common failure mode for crisis planning?
Planning for the wrong crises. Companies spend 200 hours mapping a hurricane response when their actual likely crisis is a key engineer quitting, a viral PR moment from a tweet, or a SaaS outage that takes the product down for 6 hours. The fix: list crises by probability for YOUR business, not generic templates. A SaaS company doesn't need a hurricane plan; it needs a runbook for when AWS us-east-1 goes down at 3am. Specificity beats comprehensiveness.
When is this the wrong tool to reach for?
Skip formal crisis planning if you have under 5 employees — the planning overhead exceeds the value, and informal response is fast enough. Skip if you've never had a crisis or near-miss to learn from — you'll plan for imagined scenarios. Skip if you can't commit to twice-yearly simulations. Build crisis frameworks for companies with 15+ employees, regulated industries, public-facing brands, and any business where a single bad incident can cost more than $200K.
Is this safe to use without legal/PR/compliance review?
No for the final playbook. Yes for the draft. AI can generate the structure, decision trees, communication templates, and simulation scenarios fast. But the actual playbook needs legal review (especially for breach notification and regulated industries), PR review (for external statements), and compliance review (if you're in finance, healthcare, education). Use AI to get to a 70% draft in 2 days; spend 3 weeks getting the right humans to validate before storing as canon.