Meeting Notes Summarizer
Turns a raw meeting transcript into structured notes: decisions, action items with owners, open questions, and quotes worth saving.
The prompt
I'll paste a meeting transcript. Turn it into structured notes with this exact format: **Decisions made** - Bulleted list of things that got decided. One line each. Name the decision, not the discussion. **Action items** - [ ] Task — Owner — Due date - Only include items with an owner. If nobody was assigned, put it under "Open questions" instead. **Open questions** - Things raised but not resolved. Include who needs to answer if named. **Quotes worth saving** - Verbatim quotes that capture the spirit of the meeting (customer language, key objections, memorable phrases). Attribute if the speaker is clear. **What I might be missing** - 1-2 things where the transcript is ambiguous or where I'd want to double-check with an attendee. Rules: - Never invent an owner or due date. If unclear, mark as "unassigned" or "TBD." - Never paraphrase into jargon. "The thing is slow" stays as "the thing is slow," not "performance concerns." - If someone contradicted themselves, note both positions. - Skip the intro chitchat and closing pleasantries. ## How to use it Paste this prompt, then paste your transcript (from Otter, Fathom, Zoom, Google Meet, or manual notes). The output is copy-ready for a project doc or Slack summary. ## Why it works Most meeting summaries fail because they paraphrase into blandness. Preserving verbatim quotes and refusing to invent owners keeps the notes useful when someone questions "did we actually decide X?"
How to use it
I’ll paste a meeting transcript. Turn it into structured notes with this exact format:
Decisions made
- Bulleted list of things that got decided. One line each. Name the decision, not the discussion.
Action items
- Task — Owner — Due date
- Only include items with an owner. If nobody was assigned, put it under “Open questions” instead.
Open questions
- Things raised but not resolved. Include who needs to answer if named.
Quotes worth saving
- Verbatim quotes that capture the spirit of the meeting (customer language, key objections, memorable phrases). Attribute if the speaker is clear.
What I might be missing
- 1-2 things where the transcript is ambiguous or where I’d want to double-check with an attendee.
Rules:
- Never invent an owner or due date. If unclear, mark as “unassigned” or “TBD.”
- Never paraphrase into jargon. “The thing is slow” stays as “the thing is slow,” not “performance concerns.”
- If someone contradicted themselves, note both positions.
- Skip the intro chitchat and closing pleasantries.
How to use it
Paste this prompt, then paste your transcript (from Otter, Fathom, Zoom, Google Meet, or manual notes). The output is copy-ready for a project doc or Slack summary.
Why it works
Most meeting summaries fail because they paraphrase into blandness. Preserving verbatim quotes and refusing to invent owners keeps the notes useful when someone questions “did we actually decide X?”
✦ More like this
Related prompts
Book Recommender (Honest)
Recommends 3-5 books based on what you actually liked before. No 'Sapiens for the 400th time.' Includes honest reasons and what NOT to expect.
Chart Type Chooser
Given the data you have and the question you're answering, picks the right chart type and explains what to avoid. No dual-axis, no pie chart traps.
Code Refactor Helper
Refactors a function or file without changing behavior. Explains what changed and why, and flags any behavior it wasn't sure about.