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.
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.
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. Gather your inputsHave the items above to hand.
- 2. Fill in the formYour prompt updates as you type.
- 3. Copy or open in your AIClaude, ChatGPT or Gemini.
- 4. Review before you sendCheck it against your notes.
Your prompt · 0 of 6 filled
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.
How to install
- Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
- Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
- 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…
- 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.)
| 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.
5. FlagsHi all, summary of Monday 9 Nov 2026 ops review.
Decisions
- We stay with the current corrugation supplier for November orders.
- 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
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.
- Stay with the current corrugation supplier for November orders; Rakesh approved.
- Saturday overtime for Line 1 is approved if the Gujarat order is confirmed.
| Action | Owner | Due date | Where in the notes | |---|---|---|---| | Share the rejection report. | Anita | By Friday, 13 November 2026 | “Anita to share rejection report by Friday.” | | Compare rates from two other suppliers. | Owner not named | no date agreed | “Someone should compare rates from two other suppliers.” | | Call the transporter. | Priya | Tomorrow, 10 November 2026 | “Priya will call the transporter tomorrow.” | | Discuss the pending payment to the transporter. | Owner not named | Next week; exact date not stated | “Vikram asked about the pending payment to the transporter. No answer, discuss next week.” |
3. Open questions- Supplier comparison: Who will compare rates from two other suppliers, and by when?
- Transporter payment: What is the status of the pending payment? Who will lead the discussion next week, and on which date?
- Line 2 rejections: How will the continuing high rejections be resolved?
- Delayed dispatches: How will the truck shortage affecting the three dispatches to Nashik be resolved?
- Conditional overtime: Is the Gujarat order confirmed, and which Saturday does the overtime approval cover?
Team, key points from our 9 November 2026 operations review:
Decisions
- Stay with the current corrugation supplier for November orders; I approved this.
- Saturday overtime for Line 1 is approved if the Gujarat order is confirmed.
Actions
- Anita: Share the rejection report by Friday, 13 November 2026.
- Priya: Call the transporter tomorrow, 10 November 2026.
- Compare rates from two other suppliers — Owner not named; no date agreed.
- Discuss the pending payment to the transporter next week — Owner not named; exact date not stated.
Please confirm the missing owners and dates, and reply with any corrections.
— Rakesh Sharma
5. Flags- Assumptions: None. “Friday” and “tomorrow” were converted using the meeting date.
- Names not on the attendee list: None.
- The supplier-rate comparison has no named owner or agreed date.
- The transporter-payment question received no answer. Its follow-up has no named owner, and “next week” gives no exact date.
- “Line 2 rejections still high” gives no rejection figures or benchmark.
- The notes do not confirm whether the truck shortage or delayed dispatches have been resolved.
- The overtime approval does not identify the Saturday or the approver, and the Gujarat order’s confirmation status is not recorded.
1. Decisions
- Stay with the current corrugation supplier for November orders (approved by Rakesh).
- Saturday overtime for Line 1 is approved, on the condition that the Gujarat order is confirmed.
2. Actions
| Action | Owner | Due date | Where in the notes | | :--- | :--- | :--- | :--- | | Share Line 2 rejection report | Anita Desai | By Friday (13 November 2026) | "Line 2 rejections still high. Anita to share rejection report by Friday." | | Compare rates from two other suppliers | Owner not named | no date agreed | "Someone should compare rates from two other suppliers." | | Call the transporter regarding the three delayed dispatches to Nashik | Priya Nair | Tomorrow (Tuesday, 10 November 2026) | "Priya: three dispatches to Nashik delayed, truck shortage. Priya will call the transporter tomorrow." | | Discuss the pending payment to the transporter | Owner not named | Next week (Assumed: Monday, 16 November 2026) | "Vikram asked about the pending payment to the transporter. No answer, discuss next week." |
3. Open questions
- Comparing rates from two other suppliers: Who will own this action, and by what date should it be completed?
- Pending payment to the transporter: What is the status of this payment, who is responsible for leading the discussion next week, and on what exact date will it be discussed?
- Saturday overtime for Line 1: Is the Gujarat order confirmed, and who is responsible for confirming it?
4. Message Hi everyone, here is the summary from today's weekly operations review (9 Nov).
Decisions:
- Stay with the current corrugation supplier for November orders.
- Saturday overtime for Line 1 is approved if the Gujarat order is confirmed.
Actions:
- Anita: Share Line 2 rejection report by Friday (13 Nov).
- Priya: Call the transporter tomorrow (10 Nov) regarding the three delayed Nashik dispatches.
- Compare rates from two other suppliers (Owner not named, no date agreed).
- Discuss pending payment to the transporter (Owner not named, due next week).
Please reply here with any corrections, and let us know who will take on the unassigned actions.
– Rakesh
5. Flags
- Assumptions:
- Assumed: "By Friday" means Friday, 13 November 2026, based on the meeting date of Monday, 9 November 2026.
- Assumed: "Tomorrow" means Tuesday, 10 November 2026, based on the meeting date of Monday, 9 November 2026.
- Assumed: "Next week" refers to the next weekly operations review on Monday, 16 November 2026.
- Assumed: "Saturday overtime" refers to the upcoming Saturday, 14 November 2026.
- Assumed: In the line "Someone should compare rates from two other suppliers", the suppliers are corrugation suppliers, as it directly follows the note about the corrugation supplier raising rates.
- Names not on the attendee list: None. All names in the notes (Anita, Imran, Rakesh, Priya, Vikram) match the attendee list.
- Unclear parts of the notes:
- No owner or due date was given for comparing rates from two other suppliers.
- No owner was given for following up on Vikram's question about the pending payment to the transporter next week.
- It is unclear who is tracking the confirmation of the Gujarat order to trigger the Saturday overtime for Line 1.
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 reviewReview before you send
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.
Client calls and internal reviews produce commitments that are easy to forget. Separating agreed actions from discussion helps a firm avoid promising a client something nobody owns.
Site visits and sales huddles involve many follow-ups with buyers, builders and banks. Listing each follow-up with a named owner keeps leads from being dropped between team members.
Dispatch and fleet meetings cover delays, vehicles and payments to transporters. The open questions list shows which issues were raised but not settled, so they come back at the next meeting.
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.
The draft should show 'Owner not named' and list the item under open questions. That is the correct result. Use the message to ask who will take it, or decide with the meeting lead before sending.
It depends on what the notes contain and which workspace you use. Use an approved business account, remove customer or staff personal data that is not needed, and keep sensitive HR or legal discussions out. This is practical guidance and not legal advice.
Yes, once you have the text. Type or transcribe the key points, add the people on the call as attendees, and run the same prompt. Short calls usually give a short list of decisions and actions.
Last checked · Updated