Client Meeting Notes Template
The one document your client actually re-reads is not the proposal or the deck. It's the meeting note. Three weeks after the call, when they need to remember whether they approved the new timeline or just talked about it, they open the note. If it reads like a transcript, they scroll. If it reads like decisions, they act.
A client meeting note is not internal minutes. Internal minutes are for your team. Client notes go to the other side, so they double as a relationship record and an accountability record: the thing your client re-reads to remember what was agreed, what they owe you, and what happens next.
That means the note has to lead with the four things a client looks for: decisions, action items with owners and dates, open questions, and scope. And it has to be written like a commitment, not a topic. "Discussed pricing options" is a topic. "Approved the onboarding package, invoice to follow Friday" is a decision. One is useful. One is not.
The template
Copy this into any doc, Notion page, or email body. Fill the brackets. Leave nothing blank; "unconfirmed" is a valid answer, and it becomes the first item on your next call.
Header
- Client: [name]
- Your team: [names]
- Date: [YYYY-MM-DD]
- Duration: [00:00]
- Purpose: [one sentence on why we met]
- Recording: [yes / no, consent confirmed at start]
Decisions made
Write each decision verbatim, not as a topic.
- [e.g. "Approved Q4 timeline; launch moved to Nov 12"]
- [e.g. "Added scope approved; client to confirm by Friday"]
Action items
Every item needs three things: what, who, and when. Split owners by side so the client sees their own list clearly.
| What | Owner | Due | Status |
|---|---|---|---|
| Send v2 mockups | [name] (us) | Fri | Open |
| Approve copy deck | [name] (client) | Mon | Open |
| Book QA window | [name] (us) | Wed | Open |
Open questions and risks
- [Unresolved item that becomes next meeting's agenda]
- [Risk or blocker, and who is chasing it]
Scope and next meeting
- In scope from today: [items]
- Out of scope: [items]
- Next meeting: [date / time], agenda seed: [open questions above]
That's the whole artifact. There's no "discussion" section and no transcript. A client note is decisions plus next steps, not a play-by-play.
Four rules that make the template work
The template is the easy part. Filling it well is where teams slip.
Record decisions verbatim. A decision is a commitment, so write the commitment, not the topic. "Timeline discussed" is a diary entry. "Launch pushed to Nov 12, client approved" is something the client can hold you to, and you can hold them to. When the direction changes three months later, the verbatim line is the difference between a dispute and a clean reference.
Give every action item what, who, and when. "Send mockups" is not an action item; nobody owns it and it's never late. "Send v2 mockups, [name] owns it, due Friday" is. Split owners by side so the client can see their own list at a glance.
Use open questions as the next agenda. Anything unresolved goes in the open-questions section, and it seeds the agenda for the follow-up. Yesterday's open questions are today's agenda. Nothing drops because it was parked in the last five minutes of a call.
Send same day, and keep two versions. The client-facing note goes out the same day, decisions and action items up top. The internal version, the longer record with context and your read on the relationship, stays on your side. The client note is a deliverable, not a dump.
The part that's actually hard: capture
The reason most client notes are weak isn't the template. It's that you're trying to type them while you're in the conversation. You're half present, and the person across the table can tell. The precise sentence the client said, the one that later settles an argument about scope, is exactly the sentence you miss while you're writing the one before it.
That's the case for splitting capture from formatting. Let a notetaker get the verbatim record while you stay in the conversation, then drop the record into the template afterward. A 45-minute call is roughly 6,000 words; nobody types 6,000 words and stays present.
Meetbook does this without a bot in the call. The Chrome extension records the meeting tab, the transcript is live in about 50 languages, and every point in the summary carries the quote, speaker, and timestamp it came from. When the client says "we never agreed to that," the note points back to minute 34, in their own words. That's the whole point of a client note: proof of what was agreed.