Follow-Up Email After a Client Meeting: 3 Templates and Examples

A client meeting follow-up email should make four things easy to find: what was agreed, who will act, which dates are confirmed, and what still needs a decision. Add a clear request when you need approval. A recap should not turn an idea, a proposed deadline or a client's silence into a commitment.

Use the templates below for discovery, project updates and approval requests. For internal meetings and recurring team follow-ups, use the broader meeting follow-up guide.

Choose the right client follow-up

Do not add every template section to every email. If there were no decisions, say so. If a date is missing, mark it unconfirmed instead of filling the gap.

Turn meeting notes into an accurate client record

Before writing, sort each important note into one of these categories:

• Agreed: a decision the relevant people actually confirmed.
• Action: a specific task someone accepted, with its agreed deadline if there is one.
• Proposed: an option, estimate or date that still needs agreement.
• Open: a question or dependency that has not been resolved.

Then separate client-facing information from internal material. Your internal margin estimate, negotiation strategy, personnel discussion or private assessment of the account does not belong in the recap. Check linked documents and attachments as carefully as the email body.

Worked example: do not convert a request into a promise

The following is a fictional project example.

Rough notes: “Client likes option B. Asked about a Friday launch. Priya checks accessibility. Need their approved logo. Budget not discussed.”

Misleading recap: “Option B is approved and we will launch Friday.”

Accurate recap:

You preferred option B; final approval is still needed. Priya will review the accessibility requirements. A Friday launch was requested, but the delivery date remains unconfirmed while we check the work and await your approved logo. No budget change was agreed.

The accurate version preserves the request without claiming approval or a deadline. Before sending it, confirm that Priya accepted the review action; if she did not, label it as a proposed action too.

Template 1: follow-up after a discovery meeting

Subject: [Client / project] — discovery recap and next steps, [meeting date]

Hi [Name],

Thank you for explaining [specific goal or problem]. My understanding is that you need [short description], with [important constraint] to consider.

What we confirmed

• [Verified need or decision. If none, say no project decision has been made yet.]

Next steps

• [Your name]: [accepted action], by [agreed date / date to confirm].
• [Client name]: [accepted input or action], by [agreed date / date to confirm].

Still open: [Scope, budget, approval process or other unresolved point].

I will [agreed next contact]. Please correct anything I have misunderstood.

[Your name]

This email records discovery. If you have not agreed a scope, fee or delivery date, do not imply that the project is already commissioned. Put a proposal in the agreed document or approval process.

Template 2: follow-up after a project update

Subject: [Project] — decisions, actions and open items from [date]

Hi [Name],

Here is the outcome of today's [project] review.

Agreed decisions

• [Decision and its scope.]
• [Decision, or omit if there is only one.]

Actions

• [Name, your team]: [task] by [confirmed date].
• [Name, client team]: [input or decision] by [confirmed date / to be confirmed].

Dependency: [What depends on what, without presenting an estimate as a commitment.]

Still open: [Question and who will clarify it, if agreed].

Our next agreed contact is [date or trigger]. Please let me know if the record needs correcting.

[Your name]

If the meeting discussed a change to scope, show its status explicitly: “Change requested; impact assessment pending” or “Change approved through [agreed process].” A discussion alone should not silently change the project baseline.

Template 3: request approval after a review meeting

Subject: Approval requested — [deliverable and version]

Hi [Name],

Thank you for reviewing [deliverable] today. The version for your decision is [version / dated link].

Please confirm one of these outcomes

• Approved for [specific next action].
• Approved subject to [listed conditions].
• Changes required: [please list them].

Items still open: [Any excluded page, outstanding check or unresolved condition].

Please reply by [agreed decision date / proposed date, clearly labelled]. Once I have your confirmation and [any other required checks] are complete, I will [next step]. The work requiring approval will wait for that confirmation.

[Your name]

Use the approval mechanism already agreed for the project. Do not describe an item as signed off while asking for its first approval, and do not write “we will proceed unless you object” as a substitute for a required decision.

When to send the recap

Aim to send it while the meeting is still fresh, usually the same working day. Treat that as a useful working habit rather than a universal one-hour or 24-hour rule. If a figure, date or decision needs checking, say when the checked recap will arrive. A promised delivery time matters more than an arbitrary timing claim.

Keep the subject specific enough to find later: project name, outcome and meeting date. Use the existing thread when it keeps the project context together; start a new one if the audience or subject has materially changed.

If the client does not reply

First distinguish a recap from an approval request. Not every informational recap needs a response. If you need an input or decision before work can continue, follow up on that item rather than forwarding the whole discussion again.

Subject: [Project] — [input / decision] needed for [next step]

Hi [Name],

Following our [date] meeting, I am still waiting for [specific input or approval]. This is needed before [affected next step]. Could you confirm [one clear question] by [agreed date / proposed date]?

The delivery timing for that step remains unconfirmed until [dependency]. Please let me know if someone else should review it.

[Your name]

If the deadline was never agreed, do not present it as overdue. If a commitment has changed, explain the effect and agree the revised plan. Keep corrections visible in the thread instead of leaving contradictory versions in circulation.

Draft the email from your notes with Meetings Brief

The free follow-up email generator takes pasted notes or a .vtt, .srt or .txt transcript file. Under Who is it for?, choose A client; then select Friendly or Formal under Tone. Review the subject, decisions, names, figures, dates and private information before using the draft.

Copy email copies the message. Open in my email app fills in your own email program; you choose the recipients and send it yourself. This generator does not send the client email. It is separate from optional delivery of a meeting brief to your own confirmed address in the live transcription workflow.

The generator sends supplied text to Anthropic to write the draft and has daily AI limits. Check your client's confidentiality requirements before supplying notes, and read the privacy policy for processing and temporary retention details. You can also use the manual templates above without submitting text to an AI service.

Before you press Send

• The To and Cc fields contain only the intended people.
• Every decision is supported by the meeting record.
• Proposed dates and unresolved scope are labelled clearly.
• Each action has an accepted owner; missing dates remain unconfirmed.
• Approval requests state the exact deliverable and version.
• Attachments and links have the intended access and contain no private internal notes.
• The client can see the next step and whether a reply is needed.

Frequently asked questions

How long should the email be?

Long enough to record the outcome and required action without retelling the discussion. For a complex review, put the detailed record in an approved shared document and make the email a short guide to the decisions, actions and link. There is no word count that fits every client meeting.

Should I attach the full transcript?

Only when it is appropriate and authorised for those recipients. A transcript can contain private discussion, errors or information outside the client's needs. A reviewed recap is often the more useful output; check both content and access before sharing either format.

What if the client disagrees with my notes?

Identify the exact disputed item, check the available record and confirm the corrected or still-open position. Do not silently overwrite an important commitment or treat an unverified recollection as settled fact.

Does no reply mean the client approved?

Do not use silence as your operational approval rule. If the project requires explicit approval, obtain it through the agreed process before taking that step. This guide is a communication aid; it does not determine the legal effect of a message or replace contractual advice.

Sources and further reading

The templates and fictional example above are original working examples. Microsoft's documented post-meeting email workflow also separates drafting, reviewing and sending. For the wider customer-meeting process, see HubSpot's customer meeting guide. Product instructions were checked against Meetings Brief's generator and privacy documentation for this revision.