Back to Engineering
Incident Response Runbook
Create a structured incident response process with runbooks.
🛠️ EngineeringadvancedSRE/DevOps Engineer✓ Free
The Prompt
You are an SRE lead. Create an incident response framework. System: [SYSTEM/PRODUCT] Team: [SIZE] Current on-call: [DESCRIBE] SLA: [UPTIME TARGET] Common incidents: [DESCRIBE TYPES] 1. Severity Levels: - SEV1 (Critical): criteria, response time, team mobilized - SEV2 (Major): criteria, response time, team - SEV3 (Minor): criteria, response time - SEV4 (Low): criteria, handling 2. Response Process: - Detection: monitoring alerts, customer reports, automated checks - Triage: severity assessment, incident commander assignment, channel creation - Response: diagnosis steps, communication cadence, escalation triggers - Resolution: fix verification, monitoring period, all-clear criteria - Post-Incident: timeline, 5-whys analysis, action items 3. Communication Templates: internal status, customer notification, status page updates, post-mortem 4. Runbooks for Common Incidents: database overload, API errors, deployment rollback, third-party outage, security breach 5. On-Call: rotation schedule, escalation path, handoff process, burnout prevention 6. Metrics: MTTD, MTTR, incident frequency, SLA compliance
💡 Tip: Replace all [bracketed text] with your specific details before pasting into your AI model.
AI Model Compatibility
ChatGPT (GPT-4)
5/5 compatibility
Claude
5/5 compatibility
Gemini
4/5 compatibility
Tags
incident responsesredevopsreliabilityrunbook
More Engineering Prompts
View all →Advanced
Architecture Decision Record
Document an architectural decision with rationale.
Advanced
Incident Postmortem Template
Write a blameless postmortem that prevents recurrence.
Intermediate
Technical Documentation Writer
Write clear technical documentation.
Advanced
Security Assessment Checklist
Create a security assessment checklist.