Summarize Meeting Notes Into Action Items
Turn messy meeting notes into a clean summary with decisions, owners, and follow-ups.
This prompt converts a wall of raw meeting notes into a tight three-part brief: decisions, action items with owners, and open questions. It's the one to reach for right after a call when you have scattered shorthand and need something you can paste into Slack or email before everyone forgets who agreed to what. The 250-word cap and the instruction to strip filler are deliberate — they force the model to triage rather than just reformat your text.
You are an executive assistant. Below are raw meeting notes. Produce a clean summary with three sections: (1) Key Decisions (bulleted), (2) Action Items (each with owner and due date if mentioned), (3) Open Questions to Follow Up. Keep it under 250 words total. Remove filler and tangents. NOTES: [PASTE NOTES]
What you can expect back
Key Decisions - Search will be the first feature shipped in Q3 (most-requested by users). - CSV export is cut from Q3 scope due to low usage. Action Items - Ramesh: scope the search work — due Friday. - Maya: ask legal whether data-retention changes need review before launch. Open Questions to Follow Up - Will the vector database meaningfully raise infra costs? (Tom's concern — needs a number.) - Do we hire a second backend engineer for Q3? (Raised, not decided.)
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Paste names exactly as they appear in your notes so the model can attribute action items correctly — if you only wrote initials, add a quick legend like 'M=Maya, T=Tom' before the notes.
- 02If a decision and an action are tangled in one sentence, the model sometimes lists it twice; add 'each item appears in only one section' to the instructions to dedupe.
- 03When due dates are vague ('by end of week'), ask it to convert them to an actual date by giving it today's date in the notes header.
- 04For recurring meetings, keep the same output format and paste last week's summary above the new notes so it can flag which open questions are now resolved.
Adapt it for your case
Insert a section (0) before Key Decisions asking for a single sentence summarizing the meeting's outcome.
Ask it to label each action item with the owning team (Eng, Design, Legal) so you can route the summary to multiple channels.
Add a fourth section, 'Risks & Blockers,' to surface anything that could derail the listed action items.
Common questions
What if no owners or due dates were mentioned in my notes?
The model will list the action item and mark the owner or date as 'unassigned' or 'TBD.' Review those — they're usually the items that quietly fall through.
Can I feed it a raw transcript instead of notes?
Yes, but transcripts are noisy, so the filler-removal instruction matters more. For very long transcripts, summarize in two passes or raise the word limit.
Why cap it at 250 words?
The cap forces prioritization — the model has to decide what actually mattered rather than echo everything. Raise it if your meeting genuinely covered many distinct decisions.
You may also need
Script a Difficult Feedback Conversation
Script a difficult feedback conversation using the SBI model with a collaborative, direct tone.
Facilitate a Sprint Retrospective
Plan a full sprint retrospective with agenda, prompts, and action-item templates.
Summarize a Sprint Retro Into Themes and Owned Actions
Clusters messy retro notes into themes with root causes and a table of owned, dated actions.
Write Quarterly OKRs for a Team
Generate outcome-focused quarterly OKRs with confidence scores and risk notes.