Template

Client Meeting Notes Template

Client meetings live or die on the follow-up. This template separates what the client asked for from what you actually committed to, so the recap you send is accurate and defensible.

When to use this template

  • • Recurring account check-ins and delivery reviews.
  • • Scope or change-request conversations.
  • • Any meeting where commitments, dates, or budget are discussed.

The template

**Client:** [Company]
**Meeting:** [Purpose]
**Date & time:** [YYYY-MM-DD, HH:MM]
**Attendees (client):** [Names + roles]
**Attendees (us):** [Names + roles]

**1. Objective for this meeting**
[One sentence]

**2. Status update**
- [Workstream] — [status] — [on track / at risk]

**3. Client priorities & feedback**
- [What the client said, in their words]

**4. New requests**
- [Request] — Desired outcome: [x] — Impact to assess: [scope/timeline/cost]

**5. Decisions made**
- [Decision] — Agreed by: [names]

**6. Risks & open questions**
- [Item] — Owner: [name] — Needed by: [date]

**7. Next steps**
- [ ] Owner — Commitment — Due date

**8. Next meeting**
[Date, time, format]

Copy the block above and paste it into your notes app.

Filled-in example

**Client:** Harbor Logistics
**Meeting:** Q3 delivery review
**Date & time:** 2026-06-18, 14:00
**Attendees (client):** Maria Cruz (Ops Director), Tom Reid (IT)
**Attendees (us):** Alex Nguyen (account lead), Priya Shah (delivery)

**1. Objective for this meeting**
Confirm Q3 rollout plan and resolve the data migration blocker.

**2. Status update**
- Driver app rollout — 60% of depots live — on track
- Data migration — paused pending IT access — at risk

**3. Client priorities & feedback**
- Maria: "Depot managers need the shift report before anything else."

**4. New requests**
- Weekly shift report export — Desired outcome: CSV emailed Mondays — Impact to assess: 2 dev days

**5. Decisions made**
- Migration window moved to the July 4 weekend — Agreed by: Maria, Tom, Priya

**6. Risks & open questions**
- VPN access for our engineers — Owner: Tom — Needed by: Jun 25

**7. Next steps**
- [ ] Priya — Send migration runbook — Jun 22
- [ ] Alex — Quote the shift report export — Jun 24

**8. Next meeting**
2026-07-09, 14:00, Teams.

Tips that make it work

  • • Quote the client directly on priorities — paraphrasing loses nuance.
  • • Never agree to a new request in the room; log it and return with impact.
  • • Send the recap within 24 hours and ask for a correction if anything is wrong.
  • • Track at-risk items in the same place every meeting so trends are visible.

FAQ

What should client meeting notes always capture?

The client's stated priorities, any new requests, decisions made, commitments with dates, and open questions. Requests and commitments are what protect you later.

Should I send notes to the client?

Yes. A short recap within a day confirms scope, prevents misremembered promises, and makes the next meeting shorter.

How do I handle new requests in the meeting?

Write them down verbatim, confirm the desired outcome, and say you'll come back with impact on timeline and cost rather than agreeing in the room.

Related reading