Post-Mortem Templates
Project retrospective and lessons learned documentation.
Final Report
Hi {{cursor}},
I wanted to bring something important to your attention regarding final report.
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 regardsUpdated Guide
Updated Guide
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of updated guide]
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]Revised Brief
Hi {{cursor}},
Quick update on revised brief:
[Key information]
Let me know if you have any questions.
BestInitial Draft
Initial Draft
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of initial draft]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Follow-Up Format
Hi {{cursor}},
I am writing to update you on follow-up format.
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.
Thank you for your time and attention. I will follow up if I do not hear back by [date].
Best regardsStandard Notice
Standard Notice
Date: {{date}}
Prepared by: {{cursor}}
Summary:
[Brief overview of standard notice]
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]Formal Message
Hi {{cursor}},
Quick update on formal message:
[Key information]
Let me know if you have any questions.
BestFriendly Communication
Friendly Communication
Date: {{date}}
Status: [Active/Pending/Complete]
Owner: {{cursor}}
Description:
[Detailed description of friendly communication]
Key Points:
- [Point 1]
- [Point 2]
- [Point 3]
Timeline:
- Start: [Date]
- Milestone 1: [Date]
- Completion: [Date]
Notes:
[Additional information]Brief Reminder
Hi {{cursor}},
I wanted to follow up with you about brief reminder.
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 regardsWhen to use this template
- Project completion retrospective covering what went well, what didn't, and what changes for next time.
- Incident post-mortem after a production issue. Timeline, root cause, customer impact, action items to prevent recurrence.
- Quarterly team retrospective when no single project triggered it but accumulated issues need surfacing.
Customize for your workflow
- Stay blameless in writing. 'X engineer caused the outage' is wrong wording even when factually accurate. 'A deploy without canary checks led to the outage' captures the same fact while focusing on the system.
- Include action items with owners and dates. Post-mortems without owned actions are documentation theater.
Common questions
Should post-mortems be public?
Yes for incidents that affected customers — published post-mortems build trust faster than support emails. Internal-only retros for everyday project work are fine.
How quickly after the project should the retro happen?
Within a week. Beyond two weeks and people forget the specifics; a month later you're writing fiction.
Related reading
More Project Management Templates
Status Update Templates
Weekly and daily project status report formats.
10 snippetsMeeting Notes Templates
Structured meeting minutes and action item tracking formats.
9 snippetsSprint Planning Templates
Agile sprint planning, retrospective, and standup templates.
11 snippetsRisk Assessment Templates
Project risk identification and mitigation plan formats.
8 snippetsStakeholder Updates
Executive-level project updates for stakeholders and sponsors.
9 snippetsProject Kickoff Templates
Project initiation documents and kickoff meeting agendas.
10 snippetsChange Request Templates
Scope change documentation and approval request formats.
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.