A vendor and a client leave the same call with two different ideas of what was agreed, and three weeks later there is a dispute about scope. Minutes of meeting for client meetings exist to stop exactly this, and they need a different shape from the minutes you write for your own internal project review. One document faces outward and has to survive being read by someone who was not in the room and does not trust you by default. The other faces inward and exists mainly to track work between people who already agree on the basics. This guide gives you a template for each, a worked example with an Indian agency and client, and the mistakes that turn ordinary minutes into a dispute later.
Why client minutes and project minutes are not the same document
Most teams write one kind of note and send it everywhere, which is where the trouble starts. A note written for a teammate who already has context reads very differently from one a client's finance head will scan six months from now, possibly during a billing argument. A client meeting record has to stand on its own: it needs to state what was agreed, what was explicitly not agreed, and who confirmed it, because it may be the only evidence either side has later.
An internal project meeting record has a different job. Nobody outside the team reads it carefully, so it can be shorter and more technical. It exists to carry blockers and owners from one stand-up or review to the next, not to protect anyone from a dispute. Treating both the same way usually means the client version is too thin to help if things go wrong, and the internal version is bloated with disclaimers nobody on the team needed.
What actually changes between the two
The content overlaps, but the emphasis is different in six specific places. Use this as a quick check before you send either one.
| What changes | Client meeting minutes | Project meeting minutes |
|---|---|---|
| Audience | Someone outside your company, often not in every call | Your own team, already familiar with the project |
| Tone | Formal, no internal shorthand or jokes | Can be terse, bullet points are fine |
| Scope language | States what is in scope and what is explicitly out, in plain words | Rarely needed, scope is already understood |
| Decisions | Written so a decision cannot be read two ways later | Written quickly, clarified in the next call if needed |
| Sign-off | Usually sent for confirmation before anyone acts on it | Shared, rarely needs a reply |
| Where it lives | Email thread or a shared folder the client can find again | Project tool or team channel |
A client meeting minutes template
Copy this for any call where someone outside your company was on the line, whether it is a kickoff, a review, or a renewal conversation.
Client Meeting Minutes
Project: [project or account name]
Date and time: [date], [start] to [end]
Attendees: [your company's names and roles], [client's names and roles]
Absent: [anyone expected who missed the call]
Agenda covered
[one line per topic actually discussed, not the planned agenda]
Decisions confirmed
- [decision 1, written so it cannot be read two ways]
- [decision 2]
Scope note
[state plainly what this covers and what it does not, if scope came up at all]
Action items
- [task], owner: [name, your side or client side], due: [date]
Open questions
[anything raised but not settled, and who is expected to answer it]
Next meeting
[date, or "to be scheduled"]
A project meeting minutes template
Use this shorter version for internal stand-ups, sprint reviews and planning calls where everyone already has context.
Project Meeting Minutes
Project: [name]
Date: [date]
Attendees: [team names]
Progress since last meeting
- [milestone or task], status: [on track, delayed, done]
Blockers
- [blocker], owner to resolve: [name]
Decisions
- [decision], decided by: [name]
Action items
- [task], owner: [name], due: [date]
Risks to flag upward
[anything that might need the client or leadership to know, even if it is not a problem yet]
A worked example: a vendor and a client
Kavya Designs is a Bengaluru studio redesigning the website for Meridian Retail, a client based in Mumbai. Rohan Mehta is Meridian's marketing head. Here is what the client meeting minutes look like after their monthly review call.
Client Meeting Minutes
Project: Meridian Retail website redesign
Date and time: 10 October 2026, 11:00 to 11:45
Attendees: Kavya Rao (Kavya Designs, project lead), Arjun Nair (Kavya Designs, designer), Rohan Mehta (Meridian Retail, marketing head)
Absent: Sanjana Iyer (Meridian Retail, finance), informed by email
Agenda covered
Review of the homepage design, timeline for the product pages, and a request for a regional language version.
Decisions confirmed
- Rohan approved the homepage design shown on the call, with the hero banner image to be replaced before launch.
- Product pages will use the same layout as the homepage, not a separate design round.
Scope note
The regional language version Rohan asked about is not part of the current scope. Kavya Designs will send a separate estimate for it as additional work.
Action items
- Send three hero banner options, owner: Arjun Nair, due: 14 October
- Send estimate for regional language version, owner: Kavya Rao, due: 17 October
- Share final product copy, owner: Rohan Mehta, due: 16 October
Open questions
Whether the regional language version is needed before launch or after. Rohan to confirm by the next call.
Next meeting
24 October 2026
Notice the scope note. It took one sentence, and it is the line most likely to get pulled up again if Meridian later asks why the language version was not included for free. Written down and sent the same day, it is a record. Mentioned only on the call and never written, it is an argument waiting to happen.
Mistakes that turn minutes into a dispute
These are the gaps that look harmless at the time and expensive later.
- No scope language at all. If scope came up, even casually, write one line about what is and is not included. Silence gets read as agreement.
- Sending minutes a week later. By then the client's own memory of the call has settled into a different version, and your minutes read as a correction rather than a record.
- Decisions written in a way that supports two readings. "We discussed the timeline" is not a decision. "The launch date moves to 20 November, agreed by Rohan" is.
- Mixing internal notes into the client version. A line like "client is being difficult about the budget" has no business in a document the client might eventually see forwarded to them.
- No owner on an action item. An action item without a name attached to it belongs to nobody, and everybody assumes someone else is doing it.
- Treating project minutes as unimportant. They feel low stakes because nobody outside the team reads them, but they are usually the only record of why a decision was made when someone asks three months later.
Doing this with an AI meeting notetaker
Writing two versions of every meeting's minutes by hand, one for the client and one for the team, is exactly the kind of repetitive writing that an AI meeting notetaker like Zrec is built to take off your plate. Zrec records the call from your own computer, with no bot joining and appearing in the client's participant list, and writes the minutes afterward with a summary, decisions and action items with owners and due dates. Each decision links back to the exact moment it was said, so if a client questions what was agreed, you can point to the recording instead of relying on memory. Zrec also understands meetings that mix Hindi and English, which matters when an internal review with your own team slides into Hinglish halfway through, and for sensitive client calls you can send a one-click recording notice and delete the audio automatically after a set number of days.
For more on the format itself, see our guide to the minutes of meeting (MOM) format, and for keeping the action items in this guide from being forgotten, see how to make sure action items from meetings get done.
If you only have time to fix one thing today, fix the scope note. A single sentence stating what a client meeting did and did not agree to is the cheapest insurance you will ever write.