OperationsSaves about 20 minutes per meetingTested on Claude Sonnet 5.5, GPT-6 and Gemini 4, Nov 2026

Turn meeting notes into an action list

What this does

This playbook turns meeting notes or a transcript into a clear record: decisions, actions with an owner and due date, open questions and a short message for attendees. It is for managers who spend time after each meeting writing it up. You paste the notes and attendee list into ChatGPT, Claude or Gemini and get a draft to check in a few minutes. Where no owner was named, it says so.

Fill in your detailsDownload skill
On this page

Before and after

Before

  • Someone is asked to write up the meeting from their own notes and memory.
  • It takes a while and gets done late in the day or the next morning.
  • Actions often go out with no clear owner or date, and people then remember the meeting differently.

After

  • The notes go into the prompt straight after the meeting and a structured draft comes back in a few minutes.
  • The manager checks decisions, owners and dates against the notes, settles the open items, and sends the message the same day.

Saves about 20 minutes per meeting

From my practice

The list is only as good as the notes, so I ask teams to write down who said they would do each thing as well as what was discussed. The usual failure is an action everyone agrees with and nobody owns. I would rather see 'owner not named' on the page than a guess. The person who ran the meeting should read the draft before it goes out.
· AI workflow and adoption consultant

What to have ready

  • The notes or transcript from the meeting, even if they are rough or in short lines.
  • The attendee list with full names and job titles, so the model can match first names correctly.
  • The meeting name and the exact date, because phrases like 'by Friday' need a date to work from.
  • Who will send the follow-up message, and on which channel (email, WhatsApp group, Slack).
  • Anything the notes cannot show, such as who is allowed to approve spending or overtime.

Build your prompt

  1. 1. Gather your inputsHave the items above to hand.
  2. 2. Fill in the formYour prompt updates as you type.
  3. 3. Copy or open in your AIClaude, ChatGPT or Gemini.
  4. 4. Review before you sendCheck it against your notes.
Fill in your details

Fill these in. Your prompt updates as you type, and stays in this browser tab.

Your prompt · 0 of 6 filled

You are helping an operations manager turn raw meeting notes into a clear record that people can act on. Use only what is in the notes. Do not add actions, owners or dates that the notes do not support. Meeting: The name or purpose of the meeting, held on The date the meeting was held. Attendees: Everyone who attended, with full name and role The follow-up will be sent by The person who will send the follow-up on Where the follow-up will be sent. Notes or transcript: Paste the notes or transcript as they are Produce the following, in this order. 1. Decisions. List only points where the notes show people agreed or someone with authority decided. One line each. If a decision depends on a condition, state the condition. Do not list plain discussion as a decision. 2. Actions. A table with the columns Action, Owner, Due date, Where in the notes. Start each action with a verb. 3. Open questions. Anything raised but not settled, plus every action with no named owner or no date, with the question needed to close it. 4. Message. A short message from The person who will send the follow-up, written for Where the follow-up will be sent, under 150 words. It lists the decisions and the actions with owner and date, and asks attendees to reply with any corrections. 5. Flags. List every assumption, every name in the notes that is not on the attendee list, and any part of the notes that was unclear. Rules: - Name an owner only if the notes say who will do the work. 'We', 'someone' and 'the team' are not owners. Write 'Owner not named' and add the item to the open questions. Never choose an owner because the task seems to fit their role. - If two attendees share a first name and the notes do not make clear which one is meant, write 'Owner unclear' and flag it. - Give a due date only if the notes state one. If the notes say a day such as 'by Friday', convert it to a calendar date using the meeting date and show both. If no date was agreed, write 'no date agreed'. - Keep names, amounts, quantities and place names exactly as written in the notes. - Mark any assumption you had to make with 'Assumed:'. Before you answer, check each action and decision against the notes and delete any you cannot trace to a line.
Open in
Open in Claude (opens in a new tab)Open in ChatGPT (opens in a new tab)

Gemini cannot be filled from a link, so the prompt is copied first. Paste it with Ctrl+V or Cmd+V.

Use it as a skill

Add this playbook to your assistant once, then ask for it by name.

Download skill for ClaudeView SKILL.md (opens in a new tab)
How to install
  1. Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
  2. Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
  3. Ask for the playbook by its task, and give it your details when it asks.

The skill is plain text with no scripts, links or commands. Read SKILL.md before you install it, and use a company-approved AI workspace. Need help setting it up? Book a call.

See a real result

Sample input: Weekly operations review, Sharma Packaging, Pune · Monday, 9 November 2026 · Rakesh Sharma (Managing Director), Anita Desai (Production…

Sample output from Claude Sonnet 5.5, run 14 Nov 2026
1. Decisions
  • Stay with the current corrugation supplier for November orders. Rakesh approved. (Notes, line 3)
  • Saturday overtime for Line 1 is approved, on the condition that the Gujarat order is confirmed. (Notes, line 7. The notes do not say who approved it. See Flags.)
2. Actions

| Action | Owner | Due date | Where in the notes | |---|---|---|---| | Share the rejection report | Anita Desai | Friday (Assumed: Friday 13 November 2026) | Line 1: "Anita to share rejection report by Friday" | | Compare rates from two other suppliers | Owner not named | no date agreed | Line 4: "Someone should compare rates from two other suppliers" | | Call the transporter about the three delayed dispatches to Nashik | Priya Nair | Tomorrow (Assumed: Tuesday 10 November 2026) | Line 5: "Priya will call the transporter tomorrow" |

3. Open questions
  • Rate comparison: Who will compare rates from two other suppliers, and by what date?
  • Pending payment to the transporter: Vikram asked and got no answer. The notes say "discuss next week". Who will bring the answer, and on what date is the discussion?
  • Gujarat order: Who will confirm whether the order is confirmed, and by when? Saturday overtime for Line 1 depends on it.
  • Overtime date: Which Saturday is the Line 1 overtime for?
  • Rejection report: Who should receive it? The notes do not say.
4. Message

Hi all, summary of Monday 9 Nov 2026 ops review.

Decisions

  1. We stay with the current corrugation supplier for November orders.
  2. Saturday overtime for Line 1 is approved if the Gujarat order is confirmed.

Actions

  • Anita: share the rejection report by Fri 13 Nov 2026.
  • Priya: call the transporter about the three delayed Nashik dispatches on Tue 10 Nov 2026.
  • Compare rates from two other suppliers: owner and date not yet agreed.

Vikram's question on the pending transporter payment will be discussed next week.

Please reply with any corrections.

Rakesh

5. Flags

Assumptions

  • Assumed: "Friday" means Friday 13 November 2026, and "tomorrow" means Tuesday 10 November 2026, both counted from the meeting date of Monday 9 November 2026.
  • Assumed: "the transporter" Priya will call is the one handling the delayed Nashik dispatches. The notes do not name the transporter.

Names not on the attendee list

  • None. Gujarat and Nashik are place names, not people.

Unclear parts of the notes

  • The notes do not say who approved the Line 1 Saturday overtime, which Saturday it covers, or who will confirm the Gujarat order.
  • The notes do not give the new rates, the supplier's name, or the size of the corrugation rate increase.
  • The notes do not say whether the transporter whose payment is pending is the same one Priya will call.
  • "Discuss next week" for Vikram's question has no owner and no date.
  • The notes do not say who receives the rejection report, or whether it covers Line 2 only. The line before it mentions Line 2 rejections, but the action does not name a line.
  • "Line 2 rejections still high" is discussion only, so it is not listed as a decision.

Was this playbook helpful?

Want this set up for your team?

I can fit this playbook into your CRM, helpdesk or inbox and train your team to use it.

Book a 30-minute review

Review before you send

Check the result

Watch out for

  • Auto-generated transcripts mishear names and numbers. Check amounts, quantities and names against your own memory before sending.

  • The model may smooth over a vague moment and call it a decision. It may also treat an approval as settled when the notes do not say who approved it. Read the decisions list with the person who ran the meeting and strike anything that was only discussed.

  • An action sent to the wrong person causes confusion and some embarrassment. When the draft says 'Owner not named', ask in the group who will take it. Do not fill the gap by guessing.

  • The model can turn 'next week' into a precise date that nobody agreed. A message that goes out unchecked can then commit people to deadlines they never set. Read it once, edit it, and send it yourself.

Tips for your industry

This playbook works for any business. These notes help you adapt it.

Production reviews often end with actions on suppliers, rejections and dispatch. A written owner and date for each one makes the next review quicker. Conditional approvals, such as overtime, are recorded with their condition.

Questions people ask

Yes. Paste it as it is. Long transcripts work better if you remove small talk and any personal or confidential parts first. Check names and numbers afterwards, because transcripts often mishear them.

Last checked · Updated