Client Meeting Notes Template
The meeting happened twice: once in the room, once in memory
Ask an agency and its client to describe the same meeting a week later and you'll get two different projects. The agency remembers "the client approved the direction"; the client remembers "we said we'd think about it." A request the client made firmly ("legal needs that claim gone") comes back softened into a suggestion. Nobody is lying — both sides simply left with the version that suited them, because nothing was written down while the words were still shared.
Client meeting notes fix this only if they are built as a shared record, not as the agency's diary. This template is designed for that job: status stated plainly, client requests kept in the client's own words, approvals attached to a name, commitments listed for both sides — because client-side commitments (assets, feedback, sign-offs) are where timelines actually die — and risks paired with the date a decision is needed by. Copy it, fill it in during or right after the meeting, and send it the same day.
The client meeting notes template (copy and paste)
Blank template
# Client Meeting Notes — [Client] · [Project] **Date:** **Meeting type:** status / review / kickoff / escalation **Prepared by:** **Distribution:** who receives these notes **Confirmation:** sent [date]; corrections requested by [date/time] ## Attendees - Client: [name — role], … - Agency / our side: [name — role], … ## Project status snapshot - **Overall:** on track / at risk / blocked - **Milestone reached this period:** - **Next milestone & date:** ## What we reported or showed - ## Client requests & feedback (verbatim where it matters) - [00:00:00] "[Client's words]" — [name] | Priority as stated: … ## Decisions & approvals - Decision / approval: … | Approved by (client): … | Date: … ## Commitments | Commitment | Side (us / client) | Owner | Due | |------------|--------------------|-------|-----| | | | | | ## Risks & issues - Risk: … | Impact on timeline / budget: … | Mitigation: … | Decision needed from client by: … ## Open items awaiting the client - Material / feedback / sign-off needed: … | Needed by: … ## Next meeting **Date / time:** **Agenda carried over:**
The two design choices worth understanding: requests are quoted, not summarized — a request is the one thing that must survive the meeting word-for-word, because scope, fees, and blame are all argued from it later. And commitments run in both directions. An agency-only commitment list quietly teaches everyone that delays are always the agency's fault; a two-sided table makes the real critical path visible, politely and permanently.
Example: filled in for an agency–client status meeting
Filled example
# Client Meeting Notes — Cascade Outdoor · E-commerce Redesign (Week 6) **Date:** Thursday, Oct 16 **Meeting type:** status **Prepared by:** Tom (Account Lead, Brightline Studio) **Distribution:** all attendees + Cascade brand team channel **Confirmation:** sent Oct 16; corrections requested by EOD Oct 17 ## Attendees - Client: Melissa Grant — Marketing Director; Rob Chen — E-commerce Manager - Agency: Tom — Account Lead; Ana — Design Lead ## Project status snapshot - **Overall:** at risk - **Milestone reached this period:** checkout prototype tested (8 users, 7 completed checkout in under 3 minutes) - **Next milestone & date:** homepage design approval — Oct 23 ## What we reported or showed - Checkout prototype results and the two friction points found (address form, gift options) - Revised homepage comp, v3 - Photography tracker: 60% of SKUs shot, remainder two weeks behind the original plan ## Client requests & feedback (verbatim where it matters) - [00:12:41] "Legal flagged the sustainability page — we need the 'carbon neutral' claim out until the audit is done. That's not negotiable." — Melissa | Priority as stated: immediate - [00:19:05] "Can the store locator show real stock? Our support team gets killed on that every weekend." — Rob | Priority as stated: wants feasibility answer before committing budget ## Decisions & approvals - Homepage design direction (comp v3) approved, subject to the claims change below | Approved by: Melissa Grant | Oct 16 - "Carbon neutral" claim to be removed sitewide until the audit concludes | Approved by: Melissa, on legal's instruction | Oct 16 ## Commitments | Commitment | Side | Owner | Due | |------------|------|-------|-----| | Revised homepage comp with claim removed | Us | Ana | Fri Oct 22 | | Store-locator live-stock feasibility note | Us | Tom | Thu Oct 24 | | Legal sign-off on revised claims copy | Client | Melissa | Mon Oct 27 | | Final product photography (remaining SKUs) | Client | Rob | Wed Oct 29 | ## Risks & issues - Risk: photography is already 2 weeks behind and due Oct 29 | Impact: launch (Nov 20) collides with the client's Black Friday code freeze starting Nov 15 | Mitigation: launch locator feature in phase 2, or move the launch date | Decision needed from client by: Oct 24 ## Open items awaiting the client - Final product photography | Needed by: Oct 29 - Legal sign-off on claims copy | Needed by: Oct 27 ## Next meeting **Date / time:** Thursday, Oct 23, 11:00 **Agenda carried over:** launch scope decision (locator phase 2 vs. date move); photography checkpoint
Read the commitments table again: of the four rows, two belong to the client — and one of them is the item the whole launch now depends on. That is normal, and it is exactly what disappears from memory when notes only track what the agency owes.
How to use this template well
- Send the notes the same business day, with the confirmation line filled in. The line "corrections requested by EOD tomorrow" is what converts your notes into the record: silence after that deadline reasonably means agreement. Notes sent three days later are just your version, arriving after everyone else's memory has set.
- Send them to everyone in the room — and to the person who wasn't. The stakeholder who skips the meeting and asks "wait, we agreed to what?" in week nine is the one the notes are really for.
- Quote requests and approvals; summarize everything else. Verbatim is a scalpel, not a style. If every line is a quote, none of them carry weight; when the three lines that matter are quoted with a name attached, disputes end quickly.
- Carry open client items forward visibly. The "awaiting the client" section should reappear in the next meeting's notes until it's empty. Items don't get nagged about — they get carried, in writing, which is politer and works better.
- Keep status honest in the snapshot. "At risk" written in week 6 is professionalism; "on track" repeated until week 11 and then a crisis is how accounts are lost. The snapshot line gives you a low-drama way to say it early.
Why the record has to come from the conversation itself
Notes this specific are hard to write from memory at 6 p.m. — the exact wording of a legal-driven request is precisely the detail that fades. That's the case for recording client meetings (with permission): with CoHear, the meeting records on your iPhone — nothing joins the client's video call as a bot participant, which many clients won't allow on their own tenant, and it works the same in their office or walking their store. The transcript keeps each request tied to its timestamp, and the organized summary arrives in about 65 seconds for a one-hour meeting, so the same-day send rule is realistic even on a full calendar. Sessions run 4+ hours, covering a half-day on-site workshop in one recording.
The point isn't surveillance — it's that when a client later says "we never asked for that," both sides can check the moment together instead of arguing from memory. Always ask before recording, note the consent, and follow the client's own policy if they have one; some prohibit recording entirely, and then this template simply gets filled in live.
For the broader set of situations this record-keeping serves, see CoHear use cases. For internal team meetings rather than client ones, the meeting notes template is the lighter-weight version of the same structure.
FAQ
How soon should client meeting notes be sent?
The same business day, while the meeting is still the most recent version of events in everyone's head. Same-day notes with a stated correction deadline become the shared record both sides work from; notes sent days later compete with memories that have already hardened, and every discrepancy becomes a negotiation.
What if the client disagrees with something in the notes?
That's the system working, not failing. Thank them, correct the note, and reissue it with the change visible — the corrected version is now doubly confirmed. The meeting where a disagreement surfaces in writing within 24 hours is a success; the expensive version is the disagreement that surfaces at launch, from memory, with no record to check.
What is the difference between a status report and client meeting notes?
A status report is a broadcast: progress against plan, sent one-way, usually by the agency. Meeting notes are the record of a specific conversation — what the client asked for, what was approved, what each side committed to, and what is still owed. Reports describe the project; notes create the agreements the project runs on. Most teams need both, and confusing them is how approvals get "remembered" that were only ever reported.
Should client meetings be recorded?
When the client agrees, yes — a recording makes the requests and approvals in your notes checkable rather than contestable, which protects the client as much as the agency. Ask explicitly, note the consent in the notes header, and respect a no without argument: some industries and some clients prohibit recording by policy. This is general practice, not legal advice; consent requirements vary by jurisdiction.
