After a client call, put three things in writing: what you agreed, who accepted each next step, and what still needs confirmation. A meeting recap email template helps you keep those details together so you and the client can check the same version.
For a freelancer, consultant or solo founder, this is also a chance to review commitments before starting work. A target date, an idea mentioned in passing and an approved addition to the project each need wording that reflects their actual status.
Use the meeting recap email template below, then adapt one of the four client examples to your situation.
On this page
Copy this meeting recap email template
Replace the brackets and remove sections you do not need.
Subject: [Project] — decisions and next steps — [Meeting date]Hi [Name],Here's where we landed on [topic].Confirmed- [Decision, including any condition attached to it.]Next steps- [Person who accepted the task]: [deliverable] — [agreed date/time and time zone].- [Person who accepted the task]: [deliverable] — [agreed date/time and time zone].Please confirm- [Unresolved detail, conflicting information, or missing owner/date.]- [Any additional request still awaiting a quote or approval.][Next checkpoint, if agreed.]Please confirm the open points and flag anything I've captured incorrectly.Thanks,[Your name]
Use Next steps for work someone actually accepted. If the owner or deadline is missing, state the gap under Please confirm. You can propose a person or a date for discussion, provided it is clearly labeled as a proposal.
Keep what the recipient needs to act. You do not need a transcript of the whole conversation or an audio attachment in every recap.
Example 1 — Unclear notes from a client call: Lumen
Suppose Jules writes landing-page copy for Robin. Robin has named Casey as the final copy approver.
Lumen, the people and all the details below are fictional examples created by SoloAnvil. This is an editorial worked example you can inspect, not a real client call or the result of testing a meeting recorder.
The source notes
The call takes place on October 28, 2026. Explicit times in this example use UTC.
| Note | What the record says |
|---|---|
| Scope | One English landing page and one revision round. Both sides choose headline A. |
| Product facts | Robin will send verified facts by October 29, 2026, at 12:00 UTC. |
| First draft | Jules will send it by November 2, 2026, at 16:00 UTC if the facts arrive by that cutoff. Late inputs require the draft date to be reconfirmed. |
| Review | Robin first says November 4 at 16:00 UTC, then suggests November 5. The call ends without resolving the final date or time. |
| Analytics | The form-submission event needs checking. No one accepts ownership or agrees a deadline. |
| Extra request | Robin asks about two ad variants for next month. They need a separate quote and have not been ordered. Jules will send the quote by October 30 at 12:00 UTC. |
| Approval | Casey is absent. No final copy has been approved. |
| Launch | November 9 is a target, conditional on Casey’s approval and completion of the analytics check. |
| Private note | Jules has an internal margin estimate of 45%, which was not discussed with the client. |
A quick skim could produce a decisive-sounding email that accepts extra work, chooses an unresolved deadline or announces approval that never happened.
Seven wording mistakes to correct
The incorrect lines below were deliberately written to illustrate mistakes. They are not observed outputs from an AI product.
| Wording to avoid | Problem | Correction |
|---|---|---|
| “The package includes the page and two ad variants.” | Treats an additional question as purchased work. | Keep the original scope; separate the quote and unapproved request. |
| “I’ll send the draft on November 2.” | Drops the input condition. | Put the condition beside the date. |
| “You’ll review on November 4.” | Chooses one of two unresolved dates. | Ask for the final date and time. |
| “Robin will check analytics by October 30.” | Invents an owner and deadline. | State that both are unassigned. |
| “Casey has approved the copy.” | Confuses the named approver with an approval that occurred. | Keep the copy awaiting approval. |
| “We launch on November 9.” | Turns a conditional target into a firm date. | Retain the target status and both conditions. |
| “My margin is 45%.” | Exposes an unnecessary internal note. | Leave it out of the client email. |

The three accepted actions
Only three actions have an accepted owner:
| Owner | Deliverable | Deadline and condition |
|---|---|---|
| Robin | Send verified product facts. | October 29, 2026, at 12:00 UTC. |
| Jules | Send the first copy draft. | November 2, 2026, at 16:00 UTC if facts arrive by the cutoff; otherwise reconfirm the date. |
| Jules | Send a separate quote for two ad variants. | October 30, 2026, at 12:00 UTC; do not start the extra work yet. |
The review deadline, analytics ownership and launch date still have unresolved details. Keeping them under open points reflects what both sides currently know.
The checked meeting recap email sample

Subject: Lumen — recap and confirmations — October 28, 2026Hi Robin,We chose headline A. Our current brief remains one English landing page and one revision round.Next steps — all times below are UTC:- You: send the verified product facts by October 29, 12:00.- Me: send the first draft by November 2, 16:00, provided the facts arrive by that cutoff. If they arrive late, we'll reconfirm the draft date.- Me: send a separate quote for two ad variants by October 30, 12:00. That extra work has not been approved.Please confirm:- Review deadline: November 4, 16:00 was mentioned, then November 5. The final date and time remain unresolved.- The form-submission analytics check has no accepted owner or deadline.- Casey has not approved the final copy. November 9 is a launch target, conditional on her approval and completion of the analytics check.Please confirm the review date/time and who will accept the analytics check, with a deadline.Thanks,Jules
This email preserves accepted actions and gives Robin specific questions to answer. You can send a recap while some questions remain open, as long as their status is clear.
Check the notes before you send

Before sending, compare your completed meeting recap email template with the notes or relevant recording excerpt. Check each line containing a decision, owner, date, quantity or condition.
Ask three questions:
- Where is the evidence? Find the statement where someone accepted the task or both sides agreed. If you cannot find it, ask or mark it unconfirmed.
- Did the certainty change? Preserve the meaning of “might,” “target” and “if the facts arrive on time.”
- Does this recipient need the detail? Keep relevant deliverables and conditions; remove private notes and unrelated project information.
If two sources give different deadlines, ask about the conflict instead of choosing the more plausible date. To suggest a new deadline, write: “I propose feedback by [date/time]; can you confirm whether that works?”
Flownote’s recap review guide also discusses checking commitments against the source and distinguishing agreed dates from proposed dates.
Three more meeting recap email examples for clients

These are also fictional examples written by SoloAnvil. Together with Lumen, they give you four complete situations: uncertain notes, project kickoff, blocked progress and approval.
Example 2 — Kick off a logo-design project
Situation: Tess is refreshing Avery’s logo. The agreed package contains one final primary logo, one color palette and one revision round. Avery will supply the brand materials; the date for two preliminary design directions depends on those inputs arriving on time.
Subject: Nori — scope and kickoff steps — October 28, 2026Hi Avery,We agreed to refresh one primary logo and one color palette, with one revision round.Next steps — all times below are UTC:- You: send the existing logo and brand materials by October 30, 15:00.- Me: send two preliminary design directions for you to choose from by November 3, 15:00, if the complete materials arrive by that cutoff. If they arrive late, I'll discuss a revised date with you.The two preliminary directions are the step toward choosing one final primary logo, rather than two complete logo packages. No additional design deliverables were agreed on this call.Please flag anything I've captured incorrectly about the scope or inputs.Thanks,Tess
Keep intact: the input condition and the distinction between preliminary options and final deliverables.
Example 3 — Update a video project waiting for an input
Situation: Noah has video cut v1 ready for Mira. Both sides agree to keep its layout. The music remains unresolved, and the final-delivery date is waiting on the incoming file check.
Subject: Oak video — progress and pending input — October 28, 2026Hi Mira,We agreed to keep the current layout of cut v1. The final video is not approved, and the music remains pending.Next steps — the time below is UTC:- You: send the permitted music file and its accompanying usage information by October 30, 12:00.- Me: after receiving and checking the file, propose a revised completion schedule for your confirmation.We have not agreed a final-delivery date. Accepting the layout of v1 does not approve the whole video.Please let me know if the music input changes so I can adjust the proposed schedule accordingly.Thanks,Noah
Keep intact: what was agreed, what is blocked and which input must arrive before a new delivery date can be proposed.
Example 4 — Request approval of a translation version
Situation: Aya has sent Morgan an eight-page translation, version v2. Two flagged terms still need Morgan’s decision. A feedback deadline is agreed, but final approval has not been given.
Subject: Translation v2 — approval points — October 28, 2026Hi Morgan,The eight-page translation v2 is ready for your review. The two flagged terms still need your final wording decision.As agreed, please send approval or revisions by November 4 at 16:00 UTC, together with confirmation of those two terms.I'll prepare the handoff files after receiving approval of v2 and confirmation of the terminology. The final version is currently awaiting approval.Please keep feedback on v2 so we both work from the same version.Thanks,Aya
Keep intact: the version, reviewer and requested decisions. Sending something for approval does not mean it has been approved.
If you use AI to draft the email
You can begin with manual notes; you do not need a paid meeting assistant to use this template.
Prepare the checked decisions, accepted actions and open questions first. Only put information into an AI tool when you are permitted to process it with that tool.
A suggested prompt:
Use the checked notes below to draft a clear, polite client recap email.Use only information in the notes.Preserve owners, quantities, dates/times, time zones and every condition.Do not turn ideas, additional questions or targets into confirmed decisions.Do not invent owners, deadlines or approvals.Put missing or conflicting information under "Please confirm."Leave notes marked internal out of the client email.Return:1. A subject line and email.2. A separate list of details I must check or clarify.Notes:[Paste permitted notes]
This is a suggested prompt, not a multi-model error-rate test. A fluent draft still needs a sender’s check against every commitment in the source. Ynteractive’s worked prompt guidance likewise asks readers to check names, dates and promises before using a draft.
In Lumen, a check that finds all three action dates still does not establish the email’s meaning. You must also preserve the draft’s input condition and the unresolved review date.
Frequently asked questions
What if an owner or deadline is missing?
State the gap, for example: “Form-submission check — owner and deadline unconfirmed.” Ask someone who can resolve it. A person you propose is not yet an accepted owner.
Do I need to send the full notes or recording?
Include enough decisions, actions and questions in the email for the recipient to understand the next step. Share fuller records only when needed and when the intended recipients can access them. Check shared links using the client’s permissions.
When should I send the recap?
Aim to send it while the meeting is easy to check, often that working day if the important details are verified. If a key figure still needs checking, say what is pending and agree a suitable time to follow up. This is a suggested working habit, rather than a deadline for every type of meeting.
What if the client does not reply?
Decide whether the email actually requires a response or is informational. If an input or approval is blocking work, follow up on that specific point, explain the affected next step and ask for confirmation. Keep it pending until there is evidence to change the status.
How do I correct a recap already sent?
Identify the incorrect line, send the corrected detail to the relevant people and update the source notes. For example: “Correction: product facts are due October 29 at 12:00 UTC, replacing October 30 in my previous email.” Take the corrected date from verified information.
Choose your next step
Copy the meeting recap email template, fill in confirmed decisions and accepted actions, and put unresolved details under Please confirm.
For help choosing software to capture and revisit calls, see our AI meeting-assistant comparison for solo founders and small teams. To connect the recap with intake, production and handoff, see our five-step service-delivery workflow.
