Meeting Notes to Action-Oriented Recap

What it does

Takes your raw meeting notes — bullet points, transcript snippets, or even a voice-to-text dump — and produces a professional recap that captures what was decided, who’s doing what by when, and what’s still unresolved. The key value: it separates decisions from discussion, which is where most meeting notes fail.

The Prompt

Convert these meeting notes into a structured recap.

Meeting context:
- Meeting: [NAME OR PURPOSE — "Weekly product sync" / "Q2 planning kickoff" / "Client review with Acme"]
- Date: [DATE]
- Attendees: [LIST OF ATTENDEES or "internal team" if you don't want to list]
- Duration: [APPROXIMATE — "30 min" / "1 hour"]

Raw notes:
[PASTE YOUR NOTES — bullet points, transcript, voice notes transcription, whatever you have. Don't clean them up.]

Generate a recap with these sections:

## TL;DR
2-3 sentences maximum. What was this meeting about and what's the one thing someone who wasn't there needs to know?

## Decisions Made
Numbered list. For each decision:
- The decision (stated clearly, not ambiguously)
- Context: what options were considered (one line)
- Who made/approved the decision

If no clear decisions were made, write: "No formal decisions. The following were discussed but need follow-up: [list]."

## Action Items
Table format:
| # | Action | Owner | Deadline | Notes |
For each action item:
- Action: specific, completable task (not "think about X" — that's not an action)
- Owner: one person (not "the team")
- Deadline: specific date, or "by next meeting [DATE]" if no date was set
- Notes: any context or dependencies

If an action item was mentioned but no owner was assigned, flag it: "Owner: [UNASSIGNED — needs follow-up]"

## Open Questions / Parking Lot
Items that came up but weren't resolved. For each:
- The question or topic
- Who raised it
- Suggested next step to resolve it

## Key Discussion Points
Brief summary of major topics discussed (3-5 bullets). Include enough context that someone who missed the meeting can follow the action items. This section is supplementary — the decisions and actions above are what matter.

Rules:
- Be precise about who said/decided what. Don't attribute decisions to "the group" if one person drove it.
- If the notes are ambiguous about whether something was decided or just discussed, classify it as "discussed" and flag it for confirmation.
- Skip pleasantries, tangents, and social conversation from the notes.
- Action items must be actionable. "Explore options for X" is not an action. "Draft a comparison of 3 options for X and share by Friday" is.

Usage Notes

• This works surprisingly well with voice-to-text transcriptions, even messy ones. The prompt handles redundancy and filler words.
• Send the recap to attendees within 2 hours of the meeting. A recap sent 3 days later is a historical document, not an action driver.
• The “decisions vs. discussion” separation is the most valuable part. Most meetings suffer from ambiguity about what was actually decided.
• For recurring meetings (standups, weeklies), save the output format as a template and only paste new notes each time.
• If you use a meeting recorder (Otter, Fireflies, etc.), paste the raw transcript. The prompt handles long, repetitive input well.