Meeting Notes → Decisions & Actions
Turn a raw transcript into decisions, action items with owners, and open questions.
Paste any meeting transcript or raw notes and get back a structured summary: decisions made, action items with owners and deadlines, open questions, and a two-sentence TL;DR — formatted to paste directly into Slack or your ticket system.
The prompt
Variables to fill in: {{transcript}}
Summarize the meeting transcript below into exactly this format:
**TL;DR** — 2 sentences max.
**Decisions** — every decision actually made (not discussed — made). If none, write "No decisions made."
**Action items** — table with columns: Owner | Task | Due. Extract owners and dates only when stated; use "?" when unclear rather than inventing them.
**Open questions** — questions raised but not resolved.
**Parking lot** — topics deferred to later.
Rules: never invent owners, dates, or decisions that aren't in the transcript. Quote ambiguous statements rather than interpreting them. Keep the whole output under 300 words.
Transcript:
{{transcript}}How to use
- 1Paste the raw transcript from Zoom/Meet/Otter — no cleanup needed, speaker labels help but aren't required.
- 2Check the '?' entries in the action table — those are genuinely unassigned items worth chasing.
- 3For recurring meetings, append last week's action table and ask it to mark carried-over items.
Examples
Weekly product sync
Input
A 40-minute product sync transcript covering a launch delay discussion and Q3 planning.
Output
**TL;DR** — Launch moved to July 22 due to the billing migration; Q3 planning kickoff assigned to Maya... **Action items** — Maya | Draft Q3 planning doc | Fri · Jordan | Confirm billing cutover date | ? ...
Pro tips
- Run it during the meeting on partial transcripts to catch unassigned actions before people leave.
Frequently asked questions
How long can the transcript be?+
Claude and Gemini handle 1–2 hour transcripts in one shot. For longer sessions, split by agenda topic and merge the outputs — accuracy of the action table degrades on very long inputs.
Why does it use '?' instead of guessing owners?+
Invented owners are the most damaging failure mode of meeting summarizers — someone gets assigned work they never agreed to. The '?' rule makes gaps visible instead of hallucinated.