A meeting recap email after a client call should go out the same day, while the details are still clear. It lists the decisions made, each action item with an owner and a deadline, what the client agreed to do, and a clear request for the client to confirm or correct. Before you send it, remove anything the client should not see and mark anything not yet agreed as open.
What belongs in a client call recap email?
A client call recap email lists thanks, the decisions made, each action item with an owner and deadline, the client's own commitments, open items, and a request to confirm. Write each part in the client's own terms, using the names and dates they heard on the call, so both sides can check the record against what was said.
- Thank-you line: "Thank you for your time on [date] about [project name]."
- Decisions: "We agreed to [decision, in the client's words]."
- Action items: owner, task, and deadline.
- Client commitments: what the client said they would do, and by when.
- Open items: anything the call did not settle, with the date it will be settled.
- Request: "Please reply by [date] to confirm this record, or tell me what to correct."
HeroThemes advises matching each action item to a clear owner and deadline.
How soon after the call should you send it?
Send the client recap the same day, while your notes still match what was said. HeroThemes suggests a window of 30 minutes to 2 hours after the meeting. If notes are incomplete, send the parts you can check and mark the rest as open rather than holding the email for a complete record.
While the call is fresh, sort your notes into these lists: decided, to do, client commitments, and to confirm. Anything you are unsure about goes in the last list.
What is safe for a client to see?
Send a client only what was agreed in front of them and what you have checked against the call. Keep out internal strategy, internal debate, costs or margins that are not for the client, and any decision that was not confirmed. Check each line of the recap against your notes first.
Run this check before you send:
- For each decision, ask whether the client was on the call when it was made and agreed to it. If not, move it to open items.
- Delete internal discussion, including comments about team members, options your team has not agreed on, and internal pricing.
- Check each owner name and date against your notes. Where no date was given, write "deadline to be confirmed" and name the date you will confirm it by.
- Confirm that every link and attachment is one the client is allowed to open.
- Ask a colleague who was on the call to read the draft against their own memory.
Should you share notes, transcripts, or recordings?
Share a recording or transcript only when the client knows it exists and has agreed to receive it. Otherwise send the written recap and offer the rest on request. Check your company policy and your client agreement first, since those decide what you may share.
- At the start of the call, say that it is being recorded or transcribed, and ask whether anyone objects.
- In the recap, name only what exists: "A recording of the call is available if you would like it."
- Before sending a link, check its sharing setting so that only the people the client named can open it.
How should action items and commitments be written?
Write each action item as owner, task, deadline, in that order, so nobody has to guess who acts next. An item with no deadline still goes in the recap, marked with the date it will be confirmed. Name the person, the task, and the date in the recap itself.
Illustrative example, with placeholders for every name and date:
- [Owner name] will [task] by [date].
- [Client contact name] will [client task] by [date].
- Deadline to be confirmed for [item]. We will confirm it by [date].
Avoid phrasing such as "we will look into this soon." If no owner can be named yet, the item stays open, and naming the person who will decide the owner becomes the next step in the recap.
How do you keep one record both sides use?
Store the sent recap with its date in the project record, and check each action item and open item at the next client or sponsor meeting, so both sides work from the same record. Treat only the version the client confirmed as the agreed record.
Before each meeting, reread the confirmed version and list any open item that is past its date. Raise those items first, so the record does not depend on a reply.
What does a copy-ready client recap look like?
The recap below puts the thanks, decisions, action items, open items, and request to confirm in one email. Replace each bracketed placeholder, then check every line against your notes before you send. Keep the subject line to the project name and the call date, so the thread is easy to find later.
Subject: [Project name]: recap and next steps from [date] call
Hi [client contact name],
Thank you for your time on [date] about [project name]. Here is what we covered and what happens next.
Decisions
- We agreed to [decision, in the client's words].
- We agreed to [decision].
Action items
- [Owner name] will [task] by [date].
- [Client contact name] will [client task] by [date].
- Deadline to be confirmed for [item]. We will confirm it by [date].
Open items
- [Item the call did not settle], to be decided at [next meeting or date].
Please reply by [date] to confirm this record, or tell me what to correct.
Thank you,
[Your name]
[Your role]
What do you do when the client disputes a point?
Reply in the same thread, thank the client for the correction, restate only the item that changed, and send the updated record. If the disagreement is bigger than a wording issue, offer a short call instead of continuing the argument by email.
Subject: Re: [Project name]: recap and next steps
Thank you for the correction on [item]. Here is the updated version: [owner name] will [task] by [date]. The rest of the recap stands as sent. Please reply by [date] if anything else needs changing.
Save the version the client confirmed in your project record, with the date it was confirmed.