Hub › Lessons › Client onboarding, lesson 6
Turn messy meeting notes into actions with an owner and a date, using AI
After a client call your notes say things like "domain login: needs checking" and "next call next week". Nobody owns those lines, so they slip. This lesson gives you a tested prompt that turns your notes into a short table of actions. Each action gets the owner and date your notes give, a quote of the note it came from, and an [ASK] where the notes name no one. It also writes a recap you can send.
What you will be able to do: turn ten minutes of messy notes into a list of who does what by when, see at a glance which tasks have no owner, and send a recap that promises nothing nobody agreed.
Step 1: Get your notes ready (2 minutes)
- Add the date and the people. Write the meeting date and who was there, with each person's role. The prompt uses only these names as owners.
- Leave the notes messy. Short lines and abbreviations are fine. Do not tidy them first: the prompt quotes your own words back to you, so you can see where each action came from.
- One task, one date, if you can. "Aisyah writes the text, Faizal approves, by 25 Nov" has one date for two tasks. In our test the AI read it in two different ways (see below). Writing "Faizal approves by 27 Nov" avoids the guess.
Step 2: The actions prompt
Fill in the first three lines, paste your notes under "My notes:", then paste the whole prompt into your AI tool.
Turn my meeting notes into a list of actions. Use only what is in the notes. Do not add owners, dates or tasks that the notes do not state. Meeting date: People in the meeting: My notes: Do this: 1. Actions: a table with columns #, Action, Owner, Due, From the notes. One row per task someone agreed to do. - Owner: the person the notes name for it. If no one is named, write [ASK: who]. - Due: the date or day exactly as written in the notes. If there is none, write [ASK: when]. If it is a relative day such as "Friday", "tomorrow" or "next week", copy it and add "(check date)". - From the notes: quote the words from my notes that the action comes from, word for word, in quotation marks. 2. Check: list every [ASK] from the table, one per line. Then, under "Not agreed, so not listed", list any idea in the notes that was mentioned but not agreed. 3. Recap: a short message I can send to the people in the meeting, under 120 words, listing each action with its owner and due date as in the table. Leave out rows that still have an [ASK] and say those will follow. Rules: - Ideas, maybes and things someone "might" do are not actions. - A decision is not an action unless someone agreed to do something about it. - Plain English. No praise, no sales language. - If my notes are missing, ask me for them and stop.
Step 3: Check the list before you send the recap (5 minutes)
- Read the [ASK] lines first. Each one is a task with no owner or no date in your notes. Decide who and when, or ask in the recap, then add it to the table.
- Turn relative days into dates. "Tomorrow (check date)" means the prompt copied your word and did not work out the date. Write the real date before you send, because the client reads the recap on a different day.
- Check each quote against your notes. If an action has no quote, or the quote is not in your notes, delete the row.
- Look at "Not agreed". Ideas and maybes are listed there, not as actions. If one was in fact agreed, add it yourself with an owner and a date.
- Read the recap as the client. Fix the greeting and sign-off, and remove anything you would not say.
Worked example
This continues the made-up web designer from lesson 5. After she replied to Faizal's change requests, she had a short call with him and his shop manager. These are her notes, as typed. The business, people, prices and dates are illustrative.
Input (illustrative)
Meeting date: 14 Nov 2026 People in the meeting: Mei (me, web designer), Faizal (owner, Haji Lane Barbers), Aisyah (shop manager) My notes: - launch still 2 Feb 2027, ok - Faizal sends logo files + 10 shop photos by Wed 18 Nov - Aisyah to write Services page text, Faizal approves. by 25 Nov - gallery page confirmed (S$250, per my email) - Mei to send updated invoice tomorrow - domain login: no one sure who has it. needs checking - Mei: first homepage draft for review 2 Dec - Faizal wondering about Instagram feed on homepage, maybe later, not now - next call next week, time tbc
Output (as returned)
Shown word for word from our first test run with Claude, in the Markdown it returned.
## 1. Actions
| # | Action | Owner | Due | From the notes |
|---|---|---|---|---|
| 1 | Send logo files and 10 shop photos | Faizal | Wed 18 Nov | "Faizal sends logo files + 10 shop photos by Wed 18 Nov" |
| 2 | Write Services page text | Aisyah | by 25 Nov | "Aisyah to write Services page text, Faizal approves. by 25 Nov" |
| 3 | Approve Services page text | Faizal | [ASK: when] | "Aisyah to write Services page text, Faizal approves. by 25 Nov" |
| 4 | Send updated invoice for the gallery page | Mei | tomorrow (check date) | "gallery page confirmed (S$250, per my email) - Mei to send updated invoice tomorrow" |
| 5 | Check who has the domain login | [ASK: who] | [ASK: when] | "domain login: no one sure who has it. needs checking" |
| 6 | Send first homepage draft for review | Mei | 2 Dec | "Mei: first homepage draft for review 2 Dec" |
| 7 | Confirm the time for next week's call | [ASK: who] | [ASK: when] | "next call next week, time tbc" |
## 2. Check
- Row 3: [ASK: when]. Your notes don't say whether "by 25 Nov" covers only Aisyah's draft or Faizal's approval too.
- Row 5: [ASK: who]
- Row 5: [ASK: when]
- Row 7: [ASK: who]
- Row 7: [ASK: when]. The call itself is "next week", but the notes don't give a date for confirming the time.
**Not agreed, so not listed**
- Instagram feed on the homepage ("maybe later, not now")
Two decisions were made but need no action: the launch stays 2 Feb 2027, and the gallery page is confirmed at S$250. The invoice for the gallery page is row 4.
## 3. Recap
> Hi Faizal and Aisyah,
>
> Here are the actions from our call on 14 Nov:
>
> - Faizal: send logo files and 10 shop photos by Wed 18 Nov
> - Aisyah: write the Services page text by 25 Nov
> - Mei: send the updated invoice for the gallery page tomorrow
> - Mei: send the first homepage draft for review on 2 Dec
>
> Launch is still 2 Feb 2027.
>
> I'll follow up separately on approving the Services text, checking the domain login and the time for next week's call.
>
> Mei
(73 words.) The recap says "tomorrow" for the invoice. If you send it on a later day, change that to the actual date.
What the test showed
- No invented owners or dates. In all eight runs with real notes, every owner was a person named in the notes or an [ASK], and every date in the output was in the notes or was the meeting date. Checked by script.
- Every action was traced to a note. Each row's quote matched the notes word for word, in all eight runs.
- The task nobody owned was flagged. "Domain login: needs checking" became "[ASK: who]" in five of five web designer runs.
- Relative days were not turned into dates. "Tomorrow" and "today" were copied with "(check date)" every time. No run worked out 15 Nov on its own.
- Maybes stayed out. The Instagram idea was never an action (5 of 5). For a made-up bookkeeper, "payroll help, maybe in the new year, nothing agreed" and "GST: tax agent handles, not us" were never actions (3 of 3), and "send Oct P&L once receipts in" got [ASK: when] instead of a guessed date (3 of 3).
- Shared dates were read in two ways. "Aisyah to write Services page text, Faizal approves. by 25 Nov": three runs gave Faizal's approval the same 25 Nov, and two marked it [ASK: when]. That is why step 1 suggests one date per task.
- "Next call next week, time tbc" varied. Three of five runs listed "confirm the call time" as an action with [ASK: who]. Two kept it out of the table and mentioned it in the check or the recap. Either is reasonable; decide who sets the time.
Watch out for
- It only knows what you wrote. If an action was agreed but not noted, it will not appear. Skim your memory of the call against the table.
- Notes about other people can be personal. Leave out anything you would not want in a recap, such as health or family details, before you paste.
- The recap is a draft. It lists only actions with an owner and a date. Add the missing ones once you have decided them.
Next step
Put your actions in your tracker
Copy each of your own actions, with its date, into your Notion client tracker, so it shows in the "Due in the next 7 days" view.
Go to lesson 3Next: a client handover checklist
Lesson 7 builds a checklist for the end of a project: files, logins and what the client needs to know, plus the handover message.
Go to lesson 7How we checked this lesson
- On 15 Nov 2026 (Singapore time) we ran the prompt with Claude Code 2.1.325 in print mode on four illustrative inputs: the web designer's call notes (five runs), a bookkeeper's monthly call notes (three runs), catch-up notes with no tasks agreed (two runs), and no notes at all (two runs). The output above is from the first web designer run.
- A separate script checked every output: each owner is a person named in the input or an [ASK]; every date in the output appears in the notes or is the meeting date; each row quotes the notes word for word; relative days carry "(check date)"; the recap is under 120 words and has no [ASK]; for the web designer, the domain login task has [ASK: who], "Wed 18 Nov" is kept and the Instagram idea is not an action; for the bookkeeper, payroll and GST are not actions and Lina's receipts are due Fri 20 Nov; with no tasks agreed, the table has no actions; with no notes, it asks for them and makes no table. 12 of 12 runs passed. We checked the script by feeding it an altered output with an invented owner, date and quote; it failed all three. We also read every output.
- We did not change the prompt after testing: the first version passed, so this is it.
- We tested one assistant on made-up notes. AI output varies by tool, model and input, so run the step 3 check each time.
- Last reviewed: 15 November 2026.