On-Call Handoff Templates
On-call rotation handoff notes and incident status templates.
Basic Version
Hi {{cursor}},
I hope this message finds you well. I wanted to share an update about basic version.
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.
I look forward to hearing from you. Feel free to reply to this message or schedule a call.
Best regardsAdvanced Response
Advanced Response
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of advanced response]
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]Urgent Update
Hi {{cursor}},
Quick update on urgent update:
[Key information]
Let me know if you have any questions.
BestRoutine Template
Routine Template
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of routine template]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Personalized Notification
Hi {{cursor}},
Thank you for reaching out regarding personalized notification.
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.
I look forward to hearing from you. Feel free to reply to this message or schedule a call.
Best regardsFinal Request
Final Request
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of final request]
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]Updated Summary
Hi {{cursor}},
Quick update on updated summary:
[Key information]
Let me know if you have any questions.
BestRevised Alert
Revised Alert
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of revised alert]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Initial Note
Hi {{cursor}},
Thank you for your patience while we reviewed initial note.
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.
I am happy to discuss this further at your convenience. Please do not hesitate to reach out if you need anything else.
Best regardsFollow-Up Memo
Follow-Up Memo
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of follow-up memo]
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]When to use this template
- End-of-rotation handoff to the next on-call engineer covering active incidents, suppressed alerts, and recent system changes.
- Mid-rotation backup handoff when something forces a temporary swap (illness, conflicts, planned absences).
- Post-rotation summary of the issues and patterns from the last week — useful for retros and SLO conversations.
Customize for your workflow
- Lead with anything still open. The next on-call needs to triage active issues first, not read about closed tickets.
- Include 'watch for' items even if not yet incidents. Patterns worth monitoring deserve a line.
Common questions
Verbal or written handoff?
Both for serious operations. Written for the record, verbal for context that doesn't fit in bullets. The pre-handoff verbal sync is what makes the written summary navigable.
What if my rotation was uneventful?
Send the handoff anyway. 'Quiet rotation, all systems green' confirms you were paying attention. Silent rotations make the next engineer nervous.
Related reading
More Software Development Templates
Code Review Comments
Constructive code review feedback templates for common issues.
12 snippetsPull Request Templates
PR description formats with context, testing, and review guidance.
9 snippetsBug Report Templates
Structured bug report formats with reproduction steps and environment details.
8 snippetsTechnical Documentation
API documentation, README templates, and architecture decision records.
10 snippetsGit Commit Messages
Conventional commit message templates for features, fixes, and refactors.
11 snippetsRelease Notes Templates
Changelog and release announcement formats for software updates.
8 snippetsCode Comment Standards
Documentation comment templates for functions, classes, and modules.
9 snippetsTechnical RFC Templates
Request for comments templates for proposing technical changes.
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.