🧠 AI Learning Hub

Hub › Lessons › Client onboarding, lesson 6

Lesson 6 · AI for client onboardingAbout 10 minutes

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)

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.

Prompt: meeting notes to actions
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)

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)

Sample input
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.

Actions 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

Watch out for

Next step

How we checked this lesson