Browse
Productivity

Meeting notes to decisions and owners

Turn messy notes or a transcript into decisions, a task table with owners and dates, the open questions, and a message for the team channel.

No votes yet this week
Output
Text
Written with
Claude Fable 5.1
Added
Updated

The prompt

These are my raw notes from a meeting. Turn them into something the team can act on.

Meeting: [NAME OR PURPOSE]
Date: [DATE]
Who was there: [NAMES]

<notes>
[PASTE NOTES OR TRANSCRIPT]
</notes>

I need, in this order:
1. A summary, two sentences at most.
2. The decisions. Only things that were actually agreed.
3. A task table with Task, Owner, Due and Depends on. If nobody took a task or no date came up, write UNASSIGNED or NO DATE. Never make one up.
4. Open questions: what came up but wasn't settled, and who should answer it.
5. Any risks someone mentioned.
6. A short message I can paste into the team channel.

Stick to what's in the notes. If something is unclear, put it under open questions.
  • meetings
  • summaries
  • project-management

What it generates

Example

NoteThis is an example. Results change between runs and model versions. Claude Prompts is a fan project and is not affiliated with Anthropic.

Getting the most from this prompt

Best right after the meeting

Run it while you can still spot mistakes. Weekly syncs, kick-offs, client calls, retros. It copes with scrappy bullet notes just as well as with an automatic transcript from Zoom, Meet or Teams.

Make it fit your team

  • List who was in the room. Without names, Claude can't tell an owner from somebody who was only mentioned.
  • For a recurring meeting, paste last week's task table first and ask which items are still open.
  • Change the last step to wherever you actually post: a Slack message, an email to the client, a ticket.

Why the UNASSIGNED rule matters

It's the whole point of the prompt. Left alone, a model will happily fill a gap with a plausible name or date, and one invented deadline in a recap costs you more trust than an empty cell ever would. Read the decisions before you send them, too. Something nobody objected to isn't always something that was decided.

How to use this prompt

  1. [01] Copy

    Copy the prompt

    Use the copy button above. The full text is included, nothing is cut off.

  2. [02] Fill in

    Replace the yellow parts

    Everything highlighted in yellow is a placeholder. Swap it for your own topic, audience or data.

  3. [03] Vote

    Run it in Claude and vote

    If the result helped, press the heart. Votes decide which prompts make the weekly top 10.

More like this

All productivity prompts
Text output

Prices Fact Detail Source Unit price EUR 4.20 per unit for the first 10,000 units Section 3.1, "Pricing" Volume discount EUR 3.85 per unit above 10,000 units in a calendar year Section 3.1, "Pricing" Setup fee EUR 1,500...

Pull the facts out of this document

Turn a long report, contract or transcript into a structured list of facts, numbers and dates, each with a pointer back to where it came from.

Text output

Everything fits except the conference talk outline, which I've pushed to the following week (see the note at the end). Monday Morning (your best hours) 8:30 to 10:00 write the Q4 proposal draft. 10:15 to 11:00 keep going, or...

Plan my week around energy, not just time

Give Claude your tasks, your fixed appointments and when you actually have energy, and get a week plan that puts hard work where you can do it.

Learn the technique

All articles
2 min read

How the weekly ranking works

One vote per prompt, a fresh count every Monday, and a simple tie-break. Everything about how prompts reach the top three, in plain words.

2 min read

How to use XML tags in Claude prompts

Wrapping parts of your prompt in simple tags is one of the easiest ways to get more reliable answers from Claude. A practical guide with examples.