⚡ Promptolis Original · Writing & Copywriting
📋 Meeting Follow-Up Synthesizer — Actions, Owners, Timelines
Convert meeting chaos into a crisp follow-up email. Decisions made, actions owned, deadlines set. What everyone needs after they leave the room (or close…
Why this is epic
Meeting follow-ups are the unsung hero of organizational effectiveness. A crisp follow-up within 2 hours of a meeting doubles the chance action items happen. A vague 'thanks everyone' email doesn't count. This prompt converts meeting notes + your memory into structured follow-up: decisions, actions (with owners + deadlines), open questions, next touchpoint.
Handles 4 meeting types with different structures: (1) Status meetings (what's the current state, what's next), (2) Decision meetings (what got decided, what didn't, why), (3) Problem-solving meetings (hypotheses, path forward, owners), (4) Kickoff meetings (scope alignment, roles, success criteria). Each has different information to capture.
Respects the reality that you're writing this email tired after the meeting, often before your next meeting. Fast template structure; low cognitive overhead. Over 100+ meetings per year, this email saves hours.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
<meeting-type>Decision meeting</meeting-type> <attendees>Alex (CEO), Priya (Head of Product), Dev (Head of Engineering), Maria (CMO), Me (COO)</attendees> <topic>Q3 Roadmap Prioritization — which of 7 candidate features to build</topic> <key-discussions>- Reviewed all 7 candidate features with engineering estimates + business case - Debated Feature C (checkout redesign) vs Feature F (new reporting dashboard) — both high-value - Dev raised concerns about engineering capacity — team of 8 can't do all 7 - Priya presented user research supporting Feature A (onboarding improvements) - Maria pushed for Feature B (referral program) based on growth targets - Extensive discussion about whether to cut Feature E (admin permissions) despite customer requests</key-discussions> <decisions-made>- GO: Feature A (onboarding), B (referrals), C (checkout redesign) - DEFER to Q4: Feature F (reporting dashboard) - CUT: Feature E (admin permissions) — low enough priority that we'll revisit next year - Still undecided: Feature D (mobile app improvements), Feature G (analytics integrations)</decisions-made> <action-items>- Priya: revise Q3 roadmap doc with 3 approved features + rationale, by end of week - Dev: share updated engineering capacity breakdown by next Monday, including Feature D/G options - Maria: meet with growth team to finalize referral program design by Friday - Alex: communicate Feature E cut to customers who requested it — needs careful messaging - Me (COO): schedule follow-up meeting next Tuesday to decide Feature D vs G</action-items> <open-questions>- Feature D vs G — which serves Q3 customer goals better? Need Dev's capacity info + Priya's user research to decide - How to handle Feature E communication — who owns the customer conversations? (Alex has action but needs support) - Budget for contract engineering help to expand capacity? Table for next leadership meeting</open-questions> <next-touchpoint>Tuesday next week for Feature D/G decision; Friday this week internal growth alignment</next-touchpoint>
Subject Line
Re: Q3 Roadmap Prioritization — Decisions + Next Steps
Email Body
Attendees: Alex (CEO), Priya (Head of Product), Dev (Head of Engineering), Maria (CMO), [Your Name] (COO)
Meeting Summary
We reviewed all 7 candidate features for Q3 against engineering capacity + business priorities. Reached clear decisions on 4 of 7, with 2 requiring additional info before deciding.
---
Decisions Made:
- ✅ GO — Feature A (Onboarding Improvements): User research shows activation gap; high confidence ROI
- ✅ GO — Feature B (Referral Program): Aligned to growth targets; Maria owns design
- ✅ GO — Feature C (Checkout Redesign): Revenue impact analysis supports prioritization over Feature F
- 🔄 DEFER to Q4 — Feature F (Reporting Dashboard): Still valuable, just not Q3
- ❌ CUT — Feature E (Admin Permissions): Lower priority than current options; will revisit in 2027 planning
- ⏸️ PENDING — Feature D (Mobile) + Feature G (Analytics): Need capacity clarity + user research input
---
Action Items:
| Owner | Action | Deadline |
|---|---|---|
| Priya | Revise Q3 roadmap doc with 3 approved features + rationale | End of week (Friday) |
| Dev | Share updated engineering capacity breakdown including Feature D/G tradeoffs | Monday next week |
| Maria | Meet with growth team to finalize referral program design | Friday |
| Alex | Communicate Feature E cut to customers who requested it (needs careful messaging — let's align before sending) | Alex to propose timing |
| [Me] | Schedule follow-up meeting for Feature D vs G decision | Tuesday next week |
---
Open Questions (for next meeting):
- Feature D vs G decision — depends on Dev's capacity info (Monday) + Priya's user research (she's pulling). Decision Tuesday.
- Feature E customer communication — Alex owns, but may want Priya or Maria to draft customer-facing language given customer-experience context. Align by Friday.
- Contract engineering capacity — whether to expand via contractors to cover Feature D/G. Tabled for next leadership meeting.
---
Next Touchpoints:
- Friday this week: Maria internal growth alignment
- Tuesday next week: Leadership meeting — Feature D vs G decision + Feature E communication plan
---
If I missed any decisions or action items, please reply or Slack me within 24h so I can update the record. Thanks for the thorough conversation — getting 4 of 7 decided in one meeting is strong signal of alignment.
Best,
[You]
Optional Additional Sections
Resources referenced during meeting (worth bookmarking):
- Priya's user research deck on onboarding gaps (linked in her response)
- Dev's engineering capacity spreadsheet (to be shared Monday)
- Maria's growth targets + referral program benchmarks (can share if relevant)
Risk flags:
- Feature E customer communication could create retention risk if not messaged well. Recommend Alex + Priya co-draft the customer message.
- Engineering capacity remains the constraining factor; Feature D and G both sizeable commitments. Worth considering contractor augmentation if both deferred would delay broader roadmap.
Common use cases
- Weekly status meetings that need written accountability
- Cross-functional decision meetings where attendees left with different interpretations
- Problem-solving sessions where next steps need capturing
- Client meetings where scope / decisions / timelines need written record
- Kickoff meetings establishing project scope + roles
- Board / leadership meetings with strategic decisions needing distribution
- Vendor / contractor meetings with deliverables + deadlines
- Interview debriefs where hiring decisions need alignment
Best AI model for this
Sonnet 4.5 or GPT-5 — speed matters. You want this email done in 3 minutes, not 15.
Pro tips
- Send within 2 hours. Same day max. Delay past 24 hours = memory fades = incorrect synthesis.
- Subject line = 'Re: [Meeting Name] — actions + decisions.' Direct, scannable, searchable later.
- Bullet points over paragraphs. Attendees will skim not read.
- Named owners + specific deadlines. 'Marketing will follow up' is useless. '[Name] to send revised deck by Thu 5pm PST' is actionable.
- Capture decisions explicitly, even if you think they were obvious in the room. 'We decided X' prevents 'wait, I thought we decided Y' later.
- Open questions section matters. Not everything resolves in one meeting; naming open questions prevents orphaning.
- For recurring meetings: reuse template structure. Attendees come to expect + rely on the format.
Customization tips
- For client meetings (not internal): subject line different — '[Client project] — today's meeting summary + next steps.' Structure same but tone more formal.
- For recurring status meetings: use same template every week. Attendees stop needing to parse the structure; they just read the content. Consistency > novelty.
- For very large meetings (8+ attendees): list attendees at BOTTOM, not top. Keeps the email scannable for action items at the top.
- For decision meetings where recordings exist: mention 'recording available at [link]' rather than trying to recreate every discussion thread. Written follow-up is for actions + decisions; record is for context.
- For board / executive meetings: may need separate 'executive summary' version (2-3 sentences at top) AND detailed version. Execs want the headline; staff want the details.
- For async-first teams (remote, time-zone distributed): follow-up email IS often the meeting for some attendees who couldn't join. More context needed; less 'you heard this in the room' assumption.
- For meetings where decisions are contested: capture MAJORITY decision + DISSENT. 'Decision: X (by majority consensus; [Name] had concerns about Y which will be monitored)' is fair and transparent.
Variants
Status Meeting Follow-Up
Weekly or recurring status — what's moving, what's blocked
Decision Meeting Follow-Up
Decisions made + not made, rationale if relevant
Problem-Solving Follow-Up
Hypotheses + next experiments + owners
Kickoff Meeting Follow-Up
Scope + roles + success criteria + next milestones
Interview Debrief Follow-Up
Hiring team alignment on candidate + next steps
Frequently asked questions
How do I use the Meeting Follow-Up Synthesizer — Actions, Owners, Timelines prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Meeting Follow-Up Synthesizer — Actions, Owners, Timelines?
Sonnet 4.5 or GPT-5 — speed matters. You want this email done in 3 minutes, not 15.
Can I customize the Meeting Follow-Up Synthesizer — Actions, Owners, Timelines prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: Send within 2 hours. Same day max. Delay past 24 hours = memory fades = incorrect synthesis.; Subject line = 'Re: [Meeting Name] — actions + decisions.' Direct, scannable, searchable later.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals