Meeting Summary Template for Client Calls

The five minutes after a client call are worth more than the call's last twenty. A short written summary turns a friendly conversation into a shared record: what was decided, who does what, and what happens next.

Below you will find a template you can copy, a filled-in example, and the small mistakes that make clients stop reading recaps.

Why send a summary at all

Clients rarely remember a call the way you do. They talk to many people, and the details blur within a day. A written summary:

• Creates agreement. If something in the recap is wrong, the client will tell you now, not after you have built the wrong thing.
• Documents scope. New requests are on record, with a date. That matters when you invoice.
• Makes you look organized. Most clients do not get recaps from their other vendors. You will be the one they remember.

When to send it

The same day, ideally within an hour. The longer you wait, the more a recap feels like homework to both sides, and the more likely it is that someone has already acted on a different memory of the call.

If you use AI meeting notes, the first draft is ready when you hang up. Your job is to check it and cut it down.

The five parts of a good client summary

1. One line of context. Which call, which project. Clients have many threads.
2. Decisions. What is now settled. Write them as statements, not as discussion.
3. Action items. One per line, each with an owner and a date. Include the client's items, not just yours.
4. Open questions. What still needs an answer, and from whom.
5. Next step. The next meeting, delivery or checkpoint.

Everything else (the discussion, the options you considered, the jokes) stays in your notes.

The template

Copy this into your email client or notes app:

Subject: Recap of [Project] call on [date]

Hi [Name],

thanks for the call today. Here is a short summary so we are on the same page.

Decisions
- [Decision 1]
- [Decision 2]

Action items
- [Owner]: [task] by [date]
- [Owner]: [task] by [date]

Open questions
- [Question] ([who answers])

Changes to scope
- [New / removed deliverable, and what it means for timeline or budget]

Next step
[Next meeting / delivery] on [date].

If anything here does not match your notes, just reply. Happy to adjust.

Best,
[Your name]

Delete any section that is empty. A recap with three lines is better than a recap with five empty headings.

A filled-in example

Here is what it looks like for a fictional branding project:

Subject: Recap of the Acme Studio brand refresh call on 21 Jul

Hi Maria,

thanks for the call today. Here is a short summary so we are on the same page.

Decisions
- We continue with moodboard direction B ("warm editorial").
- Launch moves to the second week of October.
- Print collateral is out of scope for this phase.

Action items
- Me: revised moodboards incl. typography options by Friday
- Jonas: send the current product photography by Wednesday
- Maria: confirm the October launch date with the board by next Monday

Open questions
- Do we need a German version of the guidelines? (Maria)

Changes to scope
- Added: social media templates (3 formats). I will send an updated
  estimate with the moodboards.

Next step
Review call next Tuesday, 10:00.

If anything here does not match your notes, just reply. Happy to adjust.

Best,
Alex

Subject lines that get opened

The subject should make the email findable later. Include the project and the date:

• "Recap: Acme brand refresh, call on 21 Jul"
• "Summary & next steps: website relaunch kick-off"
• "Notes from today: Q4 campaign planning"

Avoid "Follow-up" or "Quick recap" on their own. In a month, nobody can tell those emails apart.

Mistakes to avoid

• Sending the transcript. A transcript is a record, not a summary. Keep it for yourself and send the five parts above.
• Vague action items. "We will look into hosting" has no owner and no date, so it will not happen.
• Only listing your own tasks. If the client owes you feedback or assets, write it down with a date. It is the best way to prevent delays that end up on your plate.
• Hiding scope changes. Put them in their own section. Clients rarely object when you are upfront; they object when the invoice surprises them.
• Waiting three days. By then it is not a recap; it is a history lesson.

Scope changes: put them in writing, kindly

Scope creep is rarely malicious. It usually starts with "while you're at it…". The summary is the friendliest place to address it, because you are just writing down what was said. Useful phrasing:

• "Added to scope: social media templates. I will send an updated estimate by Friday."
• "This moves the delivery to the 20th. Let me know if that does not work."
• "Happy to include this in the next phase so the current timeline stays as planned."

If you track your time per client, you will also know quickly whether a small addition was really small.

Let the first draft write itself

Winnie records the call, transcribes it and drafts a summary with overview, decisions and open points, plus action items with owners where they were mentioned. You review it, trim it into the template above and send it. The protocol stays attached to the client, next to your tracked time. See the meeting protocol in action.