Back to Prompts
Content Generationgpt-4o-mini
Write Meeting Follow-Up Email
Prompt
You are a professional communicator writing meeting follow-up emails. Create clear recaps that drive action.
**Meeting Details:**
{{meeting_details}}
**Key Discussions:**
{{discussions}}
**Decisions & Action Items:**
{{action_items}}
**Tone:**
{{tone}}
Write a meeting follow-up email:
---
## Email
**Subject:** [Meeting Name] Recap — [Key Outcome or Date]
**To:** [Attendees]
**CC:** [Stakeholders who should know]
---
Hi team,
Thanks for [meeting context — "joining today's sprint planning" / "making time for our quarterly review"]. Here's a quick recap of what we covered and what's next.
---
**Key Takeaways**
[3-5 bullet points of the most important things discussed or decided]
• [Takeaway 1]
• [Takeaway 2]
• [Takeaway 3]
---
**Decisions Made**
• ✅ [Decision 1] — [Brief context if needed]
• ✅ [Decision 2] — [Brief context if needed]
---
**Action Items**
| Action | Owner | Due |
|--------|-------|-----|
| [Task] | [Name] | [Date] |
| [Task] | [Name] | [Date] |
| [Task] | [Name] | [Date] |
---
**Next Steps**
[What happens next — next meeting, check-in point, or how to follow up]
---
**Parking Lot** (for future discussion)
• [Topic we didn't get to]
• [Open question to address later]
---
Let me know if I missed anything or if you remember things differently.
[Sign-off]
[Your name]
---
**Attachments:** [List any shared documents, slides, or recordings]
---
## Email Alternatives
### Shorter Version (for quick syncs)
```
Quick recap from [meeting]:
✅ Decided: [Key decision]
📋 Actions:
- [Name]: [Task] by [Date]
- [Name]: [Task] by [Date]
Next: [What's happening next]
Ping me with questions.
[Name]
```
### Executive Version (for leadership)
```
[Focus on outcomes and decisions, minimize detail]
```
---
## Best Practices Applied
- ✓ Sent within 24 hours
- ✓ Clear subject line
- ✓ Action items have owners and dates
- ✓ Easy to scan (bullets, tables)
- ✓ Invites correction
Send quickly. Action items without dates don't get done. Make it skimmable.Example
Input
Meeting: Weekly product sync, Jan 15, with PM, 3 engineers, designer Discussions: Sprint review (8 of 10 stories done), Q1 roadmap priorities, tech debt discussion Actions: Sarah to finalize roadmap by Friday, Mike to estimate tech debt project Tone: Casual team
Output
**Subject:** Product Sync Recap — Jan 15 Hey team, Nice work on sprint 23—we hit 8 of 10 stories. Here's the recap: **Key Takeaways** • Sprint velocity is on track despite holiday week • Roadmap priorities for Q1 are locked: onboarding > API > mobile • Tech debt backlog needs sizing before we can commit to sprint allocation...