Erik Lindqvist

Turn Messy Meeting Notes Into Decisions, Owners and Deadlines

Paste raw meeting notes and get decisions, actions with owners and dates, open questions and a ready-to-send recap, without invented commitments.

At a glance

Best for: Whoever got stuck taking notes and needs to send a recap that makes ownership explicit, without guessing who agreed to what.
Tested on: Claude · Opus 5.5
You fill in: meeting_nameraw_notes
You get: Decisions Annual plan discount is 15%, provisional, to be revisited once Q4 data is in. Depends on: someone owning that revisit (not assigned).… (full result below)

meetings

productivity

product-management

Prompt

Turn these raw meeting notes into a clear record. The notes are messy; don't tidy away the ambiguity.

Meeting: {{meeting_name}}
Raw notes: {{raw_notes}}

Rules:

• Only record what the notes support. Never invent an owner, a date or a decision.

• If an action has no clear owner, write "NO OWNER". If it has no date, write "NO DATE". If someone only said "maybe", mark it "tentative".

• Keep decisions (settled) separate from open questions (discussed, not settled).

• Convert relative dates ("end of week", "Thu") to real dates using the meeting date.

Output:

1. Decisions: each with anything it depends on.

1. Actions: a table with columns Owner | Action | Due | Status (confirmed / tentative / NO OWNER / NO DATE).

1. Open questions: each with who is best placed to answer it, marked as a suggestion.

1. Risks to the timeline: at most 3.

1. Recap message: under 150 words, ready to paste into Slack or email. It should ask the people named in NO OWNER or tentative items to confirm.

End with a line listing anything in the notes you couldn't interpret.

Fill in

{{meeting_name}}: Meeting title and date.e.g. Pricing sync, Wed 23 Sep 2026
{{raw_notes}}: Your notes exactly as typed, fragments and all.e.g. Annual discount: Tom 20%, Priya 15%. went w/ 15%...

Example input

meeting_name: Pricing sync, Wednesday 23 Sep 2026. Attendees: Priya (Product), Tom (Growth), Dan (Eng), Alex (me, Ops)

raw_notes:
- annual plan discount: Tom wants 20%, Priya 15%. went w/ 15% for now, revisit after Q4 data
- someone needs to update pricing page before launch. Dan? he said maybe after the checkout bug
- launch still 7 Oct? Priya thinks legal review of new ToS might slip it
- Tom to ask legal re timeline
- free tier: kill the 3-project limit? no decision, need usage data. who pulls it??
- enterprise tier: Priya drafting one-pager, end of week
- checkout bug is blocking, Dan says fixed by Thu
- Alex: send notes (lol)

2.4k0

Generated Outputs (1)

2 hours ago

Claude

Opus 5.5

2 hours ago

Generated Output

1. Decisions

• Annual plan discount is 15%, provisional, to be revisited once Q4 data is in. Depends on: someone owning that revisit (not assigned).

2. Actions

| Owner | Action | Due | Status |
|---|---|---|---|
| Dan | Fix checkout bug (blocking launch) | Thu 25 Sep | confirmed |
| Tom | Ask legal for the ToS review timeline | NO DATE | confirmed owner |
| Priya | Draft enterprise tier one-pager | Fri 26 Sep | confirmed |
| Dan | Update pricing page before launch | NO DATE | tentative ("maybe, after the bug") |
| NO OWNER | Pull free-tier usage data for the 3-project-limit decision | NO DATE | NO OWNER |
| Alex | Send meeting notes | Wed 23 Sep | confirmed |

3. Open questions

• Is launch still Wed 7 Oct? Depends on the legal ToS review. Tom is best placed to answer once he hears back (suggestion).

• Should the free tier drop the 3-project limit? Needs usage data first. Priya or Tom could own it (suggestion).

• When is the 15% discount revisited, and by whom? Not discussed.

4. Risks to the timeline

1. Legal review of the ToS may slip the 7 Oct launch, and nobody has asked yet.

1. The pricing page is queued behind the checkout bug. If the bug slips past Thursday, the page may not be ready.

1. The pricing page has to show the 15% annual discount, so it needs updating whatever happens with the free tier.

5. Recap message

Pricing sync recap (23 Sep)

Decided: annual discount goes to 15% for now; we'll revisit with Q4 data.

Actions: Dan, checkout bug fix by Thu 25 Sep. Priya, enterprise one-pager by Fri 26 Sep. Tom, ask legal about the ToS review timeline.

Need confirmation:

- @Dan, can you own the pricing page update, and by what date?

- Who can pull free-tier usage data so we can decide on the 3-project limit? @Priya @Tom

- @Tom, could you share legal's answer here so we know if 7 Oct holds?

Reply here if I've got anything wrong.

Couldn't interpret: nothing major. "Revisit after Q4 data" has no date; I left it off the action list rather than guess.

Why it works

The expensive failure in meeting summaries is invented certainty: the model tidies "Dan? maybe" into "Dan will update the pricing page", and now Dan owns something he never agreed to. The explicit NO OWNER / NO DATE / tentative labels keep that ambiguity visible, and the recap is told to chase exactly those items.

Separating decisions from open questions stops "we discussed killing the free-tier limit" from being read as "we decided". Converting relative dates against the meeting date turns "end of week" into something a calendar understands. The closing "couldn't interpret" line gives you a place to fix the notes before anything gets sent.

When not to use it

If you have a full transcript, use it rather than notes; this prompt is built for fragments. Don't use it to settle a genuine dispute about what was agreed, because the model only sees your notes, not the room. Be careful pasting notes from confidential HR, legal or customer meetings into a tool your company hasn't approved.

Comments (0)

No comments yet. Be the first to share your thoughts!