In short
Client meeting notes have a different job from internal ones. They are the record you will reach for when an invoice is questioned, when a deliverable is not what the client expected, or when someone new joins the account and asks "why did we do it this way?"
So they need to capture four things precisely: what was decided, what changed in scope, what the client asked for, and where you and the client did not agree.
This guide gives a template for consultants and agencies, explains each section, shows a fictional example, and covers what to send the client afterwards.
What makes client notes different
Internal meeting notes can be loose because the people who read them were mostly in the room. Client notes are read later, by people who were not, and sometimes in a dispute. Four things follow:
- Scope is the section that costs money. A request agreed in passing ("could you also look at the pricing page?") is work. If it is not written down with what you said about cost and timing, it becomes free work or an argument.
- The client's words matter. "We need it simpler" and "we need fewer steps in checkout" lead to different work. Write what they said, not your translation of it.
- Disagreement is information. A client who pushed back on a recommendation and then said "fine, go ahead" may raise it again when the result disappoints. A line in the notes saying where you differed and how it ended protects both sides.
- Actions run in both directions. Consultants often write down their own tasks and forget the client's — the data export, the access request, the sign-off — which are usually what delays the project.
The template
# [Client] — [meeting purpose] — [date]
Attendees (client): [names, roles]
Attendees (us): [names]
Engagement / project: [name or reference]
Recorded: [no / yes — client agreed at the start]
## Decisions
- [decision] — agreed by [name]
## Scope, cost and dates
- Change requested: [what, in their words] — by [name]
Our response: [what we said about cost or timing]
Status: [agreed / to be quoted / declined / open]
## What the client asked for
- "[their words]" — [name]
## Where we differed
- Topic: [what]
We said: [our position]
They said: [their position]
Outcome: [agreed to their approach / ours / left open]
## Action items
| Owner | Action | Due |
| ------------- | ------ | --- |
| [client name] | | |
| [our name] | | |
## Open questions
- [question] — who will answer, by when
## Internal only
- [our read of the room, risks, relationship notes — never sent]The Internal only section is deliberately separate. It is where you note that the sponsor seemed distracted, or that the finance contact was hearing about the timeline for the first time. It must never end up in the version the client sees, so keep it at the bottom where it is easy to cut.
Section by section
Decisions
One line per decision, with the name of the person on the client side who made or agreed it. "Agreed to launch in two phases — Marc Dubois" is a decision. "Discussed launch options" is not; if nothing was decided, write that.
Scope, cost and dates
This is the section to be most careful with. For each change, note the request in the client's words, what you said in response, and its status. "To be quoted" is a perfectly good status; it tells everyone the request exists and is not yet agreed.
What the client asked for
Requests that are not scope changes still matter: a preference for how reports are formatted, a stakeholder they want included, a concern about a supplier. Quote them.
Where we differed
Write both positions fairly, as if the client might read it. That discipline keeps the note accurate. The outcome line matters most: "Client chose their approach after hearing ours" is a very different record from "left open".
Action items
Owner, verb, deliverable, date — and at least as many rows for the client as for you, if that is how the work splits.
A fictional example
Northwind is an invented customer; the people are invented too.
# Northwind — pricing page review — 24 September 2026
Attendees (client): Marc Dubois (head of marketing), Priya Shah (finance)
Attendees (us): Ana Ruiz, Tom Becker
Engagement: Northwind website refresh, phase 2
Recorded: yes — Marc agreed at the start
## Decisions
- Launch price holds for the first quarter — Priya Shah
- Pricing page will list what the free tier includes — Marc Dubois
## Scope, cost and dates
- Change requested: "a comparison table against the two competitors" — Marc
Our response: outside the phase 2 scope; about three days' work; can quote
Status: to be quoted
## What the client asked for
- "Keep the annual price visible without a toggle." — Marc
## Where we differed
- Topic: showing monthly prices by default
We said: annual by default, as tested in phase 1
They said: monthly by default, because sales quote monthly
Outcome: client chose monthly; we will revisit after launch data
## Action items
| Owner | Action | Due |
| ----------- | -------------------------------------- | ------ |
| Priya Shah | Confirm the annual price with finance | 26 Sep |
| Marc Dubois | Send the free tier feature list | 27 Sep |
| Ana Ruiz | Quote the comparison table | 27 Sep |
| Tom Becker | Update the page draft to monthly-first | 30 Sep |
## Open questions
- Does the free tier include exports? — Marc, with the feature list
## Internal only
- Priya had not seen the phase 2 timeline before; send it to her directly.What to send the client
The same day, send a short version: decisions, scope changes with their status, actions on both sides, open questions. Leave out "where we differed" unless the outcome needs confirming, and always leave out the internal section. Ask them to reply if anything is wrong; silence is not agreement, but a correction received today is far cheaper than one received at invoice time.
How to write a follow-up email after a meeting has a client template you can adapt. For the questions worth going back with, see the questions to ask after a meeting. The general structure behind this template is in the meeting notes template.
Writing client notes from a recording with Notey
When the client has agreed to a recording, Notey records the call on your Mac without anything joining it — which matters when a client's IT blocks meeting bots. Your microphone and the call's audio are kept on two separate tracks, so the transcript knows your side from theirs. The audio is transcribed on your Mac and stays on your disk.
Two of Notey's note kinds map onto the harder sections of this template. Where you differed lists each point the two sides did not agree on, what each said and how it ended. Follow-up email drafts a message confirming what was agreed and asking for what is still open. Both are written only when you ask, from the transcript's text, and both are labelled as AI-generated — check them against the transcript before they go anywhere, and write the scope section yourself. The workflow around this, from arming a call to sending the follow-up, is in AI meeting notes for consultants.
Checklist
- Ask before recording; note the answer.
- Decisions with the name of who agreed.
- Every scope change with your response and its status.
- The client's requests in their words.
- Where you differed, and how it ended.
- Actions for both sides.
- A short version to the client the same day; the internal section stays internal.
Frequently asked questions
What should client meeting notes include?
Decisions, anything that changes scope, cost or dates, what the client asked for in their words, points where you and the client disagreed, and action items with owners on both sides.
Should I share my client meeting notes with the client?
Share a short version — decisions, scope changes and actions — in a follow-up email the same day. Keep your fuller internal notes, including where you differed and your own read of the room, to yourself or your team.
How do I record a scope change in meeting notes?
Write what was asked for, who asked, what you said about cost or timing, and whether it was agreed or left open. Then confirm it in writing to the client, because the notes alone are only your record.
Is it all right to record client calls?
Ask the client first, check their policy and your contract, and follow the law where you both are. Many clients agree when told why and what happens to the recording; some will say no, and that answer stands.