Incident Response Templates
Incident declaration, updates, and post-incident review formats.
Formal Notice
Hi {{cursor}},
I wanted to bring something important to your attention regarding formal notice.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
If you need any clarification, I am available to chat anytime this week.
Best regardsFriendly Message
Friendly Message
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of friendly message]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Brief Communication
Hi {{cursor}},
Quick update on brief communication:
[Key information]
Let me know if you have any questions.
BestDetailed Reminder
Detailed Reminder
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of detailed reminder]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Professional Confirmation
Hi {{cursor}},
Thank you for your patience while we reviewed professional confirmation.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
Please let me know if you have any questions or if there is anything else I can help with.
Best regardsQuick Report
Quick Report
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of quick report]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Comprehensive Guide
Hi {{cursor}},
Quick update on comprehensive guide:
[Key information]
Let me know if you have any questions.
BestCustomized Brief
Customized Brief
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of customized brief]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Template Draft
Hi {{cursor}},
I am writing to update you on template draft.
Here are the key details:
- [Detail 1]: [Specific information]
- [Detail 2]: [Specific information]
- [Detail 3]: [Specific information]
Please review the above and let me know if you have any questions or need additional information.
Please let me know if you have any questions or if there is anything else I can help with.
Best regardsBasic Format
Basic Format
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of basic format]
Details:
1. [Key point or finding]
2. [Key point or finding]
3. [Key point or finding]
Action Items:
- [Action item 1] - Due: [Date]
- [Action item 2] - Due: [Date]
- [Action item 3] - Due: [Date]
Next Steps:
[Description of what happens next]
Notes:
[Additional context or considerations]Personalized Request
Hi {{cursor}},
Quick update on personalized request:
[Key information]
Let me know if you have any questions.
BestWhen to use this template
- Declaring an incident when something user-facing breaks. Severity, scope, who's responding, and where to follow updates.
- Mid-incident updates every 30 minutes during active investigation, even if the update is 'still investigating'.
- Post-incident review (PIR / blameless post-mortem) with timeline, root cause, customer impact, and action items.
Customize for your workflow
- Map incident severity to a clear ladder (P0 = total outage, P1 = major degradation, etc). Vague severity = inconsistent response.
- Always assign an incident commander. Without single ownership, response devolves into multiple people doing overlapping work.
Common questions
Public post-mortem or internal only?
Public for customer-facing incidents — published post-mortems build trust faster than support emails. Internal-only for issues that didn't reach customers.
How blameless is too blameless?
Blameless about people; specific about systems and decisions. 'A deploy without canary checks led to the outage' is fair; 'someone made a mistake' isn't useful.
Related reading
More DevOps & Infrastructure Templates
Deployment Notifications
Pre and post-deployment communication templates.
9 snippetsInfrastructure Change Requests
Change advisory board submissions and approval request templates.
8 snippetsMonitoring Alert Templates
Alert configuration descriptions and escalation procedures.
9 snippetsRunbook Templates
Operational runbook formats for common infrastructure tasks.
10 snippetsCapacity Planning Reports
Resource utilization reports and scaling recommendation formats.
8 snippetsSecurity Patch Notices
Security update notifications and patch schedule communications.
8 snippetsUse these snippets in TypeFire
Download the template pack, drop the .md files into your TypeFire snippets folder, and start expanding with abbreviations instantly.