Crisis Response Plan (Prepared, Not Panicked)

Create a crisis response plan for {CRISIS_TYPE}.

Input:
- Crisis type: {CRISIS_TYPE}
- Potential triggers: {TRIGGERS}
- Stakeholders affected: {STAKEHOLDERS}
- Current capabilities: {CAPABILITIES}

Rules:
- Define specific severity levels
- Assign clear roles with backups
- Create step-by-step protocols
- Prepare communication templates
- Make it accessible during crisis

Output format:

CRISIS SCENARIOS

Scenario: {CRISIS_TYPE}
Potential triggers:
- [Trigger 1]
- [Trigger 2]

Severity levels:
- SEV-1 (Critical): [Definition and impact]
- SEV-2 (High): [Definition and impact]
- SEV-3 (Medium): [Definition and impact]

RESPONSE TEAM

Incident Commander: [Name, backup]
Role: [Overall decision authority, coordinates response]
Contact: [Phone, email, backup channel]

Communications Lead: [Name, backup]
Role: [All stakeholder communications]
Contact: [Phone, email]

Technical Lead: [Name, backup]
Role: [Handles technical resolution]
Contact: [Phone, email]

[Additional roles...]

RESPONSE PROTOCOL (SEV-1)

Within 15 minutes:
1. Incident Commander confirms severity
2. Communications Lead notifies response team
3. Technical Lead begins assessment

Within 30 minutes:
1. Team convenes on [platform]
2. Communications Lead sends initial holding statement
3. Technical Lead provides situation assessment

Within 1 hour:
1. Incident Commander makes go/no-go decisions
2. Communications Lead updates stakeholders
3. Technical Lead implements immediate mitigation

Ongoing:
- Status updates every [frequency]
- Stakeholder communication every [frequency]
- Leadership briefings every [frequency]

DECISION AUTHORITY

Incident Commander can:
- [Decision type 1]
- [Decision type 2]

Requires executive approval:
- [Decision requiring escalation]
- [Financial threshold: $X]

COMMUNICATION TEMPLATES

Internal Alert:
"[SEVERITY] [CRISIS TYPE] detected at [TIME]
Impact: [Description]
Response team: Convene immediately on [platform]
Status updates: Every [frequency] on [channel]"

Customer Communication:
"We're aware of [issue] affecting [scope]
Current status: [What we know]
Impact: [What customers experience]
Next update: [Timeline]
How to get help: [Support channel]"

Executive Briefing:
"Situation: [What happened]
Impact: [Scope and severity]
Response: [What we're doing]
Timeline: [Expected resolution]
Decision needed: [If any]"

ESCALATION PATHS

If [condition], escalate to [role]
If [condition], notify [external party]
If unresolved after [timeframe], escalate to [executive]

POST-CRISIS PROTOCOL

Within 24 hours:
- Send all-clear communication
- Begin postmortem documentation

Within 1 week:
- Complete postmortem
- Identify process improvements
- Update crisis plan

DRILL SCHEDULE
- Tabletop exercise: Quarterly
- Full simulation: Annually
- Plan review: Every 6 months
- Contact list update: Monthly

QUICK REFERENCE

Emergency contacts: [Link or embedded list]
Communication channels: [Platforms]
Runbook location: [Where to find detailed procedures]
Backup procedures: [If primary systems are down]

Crisis type: {CRISIS_TYPE}
Triggers: {TRIGGERS}