Client meeting notes template (Word, free)

What’s in the template

The minutes open with these details:

• Client
• Project or account
• Date
• Time
• Location (or video platform)
• Client attendees (name, role)
• Our attendees (name, role)
• Notes taken by
• Meeting type (kickoff / review / status / escalation)

Then the body follows the meeting in this order:

1. 1. Objectives for this meeting — What both sides wanted out of it. One or two lines.
2. 2. Status since last meeting — What was delivered, what slipped, in plain terms. Agreed with the client in the room.
3. 3. What the client said — Their words, lightly tidied. Keep needs, concerns and constraints apart; they lead to different actions.Needs and requests: · Concerns: · Constraints (budget, dates, approvals, internal politics):
4. 4. What we committed to — Only things you actually said you would do, with a date. If you said "we will look into it", write that, not "we will do it".Commitment: · By: · Owner on our side:
5. 5. What the client committed to — Content, approvals, access, payments. Projects slip here more than anywhere.Commitment: · By: · Owner on their side:
6. 6. Changes to scope, budget or timeline — State the change and whether it is agreed, proposed, or needs a written change order. Nothing in this section should be new to the client when they read the notes.Change: · Effect on budget: · Effect on timeline: · Status: agreed / proposed / change order needed
7. 7. Risks and dependencies — What could delay or derail the work, and who owns watching it.
8. 8. Decisions — Each one on its own line, with who on the client side made it.
9. 9. Next meeting — Date, attendees, and what each side brings.

At the end: action items and decisions and scope changes, as tables you can keep across meetings.

The template

Download it as a Word file, or copy the text version into your own document.

Client Meeting Notes

Client: 
Project or account: 
Date: 
Time: 
Location (or video platform): 
Client attendees (name, role): 
Our attendees (name, role): 
Notes taken by: 
Meeting type (kickoff / review / status / escalation): 

1. Objectives for this meeting
   [What both sides wanted out of it. One or two lines.]

2. Status since last meeting
   [What was delivered, what slipped, in plain terms. Agreed with the client in the room.]

3. What the client said
   [Their words, lightly tidied. Keep needs, concerns and constraints apart; they lead to different actions.]
   Needs and requests:
   Concerns:
   Constraints (budget, dates, approvals, internal politics):

4. What we committed to
   [Only things you actually said you would do, with a date. If you said "we will look into it", write that, not "we will do it".]
   Commitment:
   By:
   Owner on our side:

5. What the client committed to
   [Content, approvals, access, payments. Projects slip here more than anywhere.]
   Commitment:
   By:
   Owner on their side:

6. Changes to scope, budget or timeline
   [State the change and whether it is agreed, proposed, or needs a written change order. Nothing in this section should be new to the client when they read the notes.]
   Change:
   Effect on budget:
   Effect on timeline:
   Status: agreed / proposed / change order needed

7. Risks and dependencies
   [What could delay or derail the work, and who owns watching it.]

8. Decisions
   [Each one on its own line, with who on the client side made it.]

9. Next meeting
   [Date, attendees, and what each side brings.]

Action items
No. | Action | Owner (side) | Due | Status

Decisions and scope changes
No. | Decision or change | Agreed by (client) | Date

Example: filled-in client meeting notes

What the template looks like once it’s been used. The organisation and people are made up.

Decisions and scope changes

Action items

Tips for client meeting notes

• Write the client's requests in their words, then your interpretation underneath if the two differ. The gap is where scope disputes start.
• Give every client commitment a date and a name on their side. "The client will send the content" slips; "Helen, by the 22nd" tends not to.
• If a change to scope comes up, say the words "that would be a change" in the meeting and write them in the notes. Do not let it be discovered in an invoice.
• Send the notes to everyone who attended on the client side, not just your main contact.
• Keep a separate internal note for margin, staffing and your own assessment. Never mix the two documents.
• Note who holds approval authority. Projects stall when the person in the meeting cannot say yes.

Related templates

• Sales meeting notes template — Discovery and sales call notes laid out in the fields a CRM wants: situation, pain, decision process, budget, competition, next step.
• Project meeting minutes template — The weekly status record: where each workstream stands, which milestones moved, what changed on the risk log and what was decided.
• Meeting summary template — The short recap you send after a meeting: decisions, actions and open questions, written to be read in two minutes.
• Project kickoff meeting template — The one meeting where scope, roles and how the project will communicate are written down before anyone starts work.
• All meeting minutes templates

Or let the notes write themselves

A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.