Client Meeting Notes Template

A client meeting notes template for check-ins and reviews with an existing client: their goals in their words, concerns, agreements and next steps on both sides. Download it free in Word or PDF, with no sign-up, and see an example below.

Download .docx Download .pdf

Free. No sign-up.

Dalm is a Mac app that records a meeting — a call or a room — and drafts notes from the transcript. Get early access

A meeting with a client you already work with is not a sales call: the deal is signed, and what matters now is whether they are getting what they came for. The notes are for your own side. They keep the client’s goals and complaints in the client’s words, name who said each piece of feedback, split the next steps into what you owe and what the client owes, and write down the quiet signals — a budget question, a champion who seems to be leaving — that decide whether the account renews. The email the client receives is written from these notes later.

What’s in the template

The file follows the order of a client meeting, from who was in the room to what is still open:

• Header — client or company, date, client attendees with name and role, your attendees, and the meeting type: check-in, review, project, renewal or other.
• Summary — two or three sentences on what the meeting changed.
• Client goals and needs — in the client’s own words where possible.
• Concerns and complaints — a list, written as they were said.
• Feedback on our work or product — a table of feedback and who said it.
• Agreements — what both sides accepted in the meeting.
• Next steps — our side — action, owner and due date.
• Next steps — client side — the same table for what the client does.
• Risks to the relationship — signals of dissatisfaction, budget changes, a champion leaving, a competitor mentioned.
• Open questions — what nobody could answer yet.

The template opens with one line on its purpose: an internal document, with the recap email as the version the client sees.

Client meeting notes example

Example (fictional). Names and events are invented.

Client / company	Greenfield Foods
Date	23 October
Client attendees	Olga Petrova (Head of Operations), Ivan Zuev (IT)
Our attendees	Dmitry (CSM), Ilya (engineering)
Meeting type	check-in

Summary
Pilot in two warehouses is running for a week. Shift leads use it daily, but IT is worried about where data is stored. Agreed to send a security overview before expanding.

Client goals and needs

• “Handover should take five minutes, not thirty.”
• Roll out to all six warehouses by year end.

Concerns and complaints

• Ivan: “We can’t expand until security signs off on where recordings are kept.”
• Two shift leads find the export button hard to find.

Feedback

Feedback	Who said it
Handover notes are clearer than before	Olga

Agreements

• Expansion decision after the security review.

Next steps — our side

Action	Owner	Due date
Send the security overview to Ivan	Ilya	27 Oct
Show shift leads where export is	Dmitry	not set

Next steps — client side

Action	Owner	Due date
Run the security review	Ivan Zuev	not set

Risks to the relationship
Expansion is blocked by security; if the review drags past December, the year-end rollout goal is at risk.

Two details are worth copying. Ivan’s concern is quoted, not retold as “IT has questions”, so whoever sends the security overview knows exactly what has to be answered. And the client side has its own step even without a date: the expansion waits on the client’s review, and the notes make that visible before anyone asks why the rollout has stalled.

How to fill it in

Client notes go wrong in two directions: they turn the client’s words into your own language, or they record a friendlier meeting than the one that happened. The template carries five rules against both. They keep the client’s problem recognisable to the client, the complaints at their real weight, both sides’ tasks on the page, the risks written down while you still remember the tone, and nothing in the notes that nobody actually promised.

1. Client’s words for client’s problems. Don’t translate their pain into your jargon.
2. Don’t soften complaints. Record them as they were said.
3. Client tasks matter as much as yours. Most delays come from the client side.
4. Risks read between the lines. A polite “we’ll see” about renewal is a risk — note it.
5. No promises that weren’t made. Prices, dates and scope only as agreed.

Turn these notes into a recap email

The notes stay with your team; the client gets a short email the same day. Take the agreements and both lists of next steps as they are, open with the client’s goal in their own words, and leave out the risks and anything unsoftened. The meeting recap email template has the email ready to fill in, with an example.

Notes, recap or client summary

• These client meeting notes — internal, after a check-in, review or project meeting with an existing client; long enough to hold concerns, feedback and risks.
• Meeting recap email template — what the client receives: what was agreed and the next steps on both sides, under 200 words.
• Client recap from a recorded call — what a client can read after a meeting that was recorded.
• Discovery call notes template — before they were a client: the first call with a prospect, with pains, qualification and one next step.
• Sales meeting summary template — before they signed: the internal deal record after a demo or negotiation, with objections and deal risks.
• Meeting minutes and meeting notes templates — general notes for any meeting, internal or not, in Word and PDF.

A one-page form for notes by hand at the table is on the printable template; every other template is on the templates page.

If you would rather not take notes at all

You can fill in this template by hand. If you would rather not take notes at all, Dalm is a Mac app that records the meeting — a call, or a conversation in the room through the Mac’s microphone — and drafts notes from the transcript to start from. The draft is its own document rather than this template filled in: you correct it line by line and save it as PDF, Word (.docx) or Markdown, next to the rest of the client’s files.

See plans