Follow-Up Email After Meeting: 10 Templates That Work

The follow-up email after a meeting is one of the most consistently under-invested pieces of work in most organizations. Meetings themselves get calendar blocks, agenda docs, and post-meeting drinks. The follow-up gets whatever attention is left, which is often none.

For Virtual Assistants and Executive Assistants, this is upside. A well-written follow-up email dramatically raises how the entire meeting is perceived by attendees, without any change to the meeting itself. It is one of the highest-impact writing tasks a VA or EA does.

This guide is part of our broader coverage of client communication for Virtual Assistants and Executive Assistants.

Anatomy of a strong follow-up email

Every good follow-up email has five components in this order:

1. Subject. Reference the meeting name and date. "Follow-up: [Meeting name]: [Date]" or "Notes from our [topic] call."
2. Opening. One line acknowledging the meeting happened. Not "Thanks for your time" (filler). Something concrete: "Great to align on the Q4 roadmap this morning."
3. Decisions section. What was decided, in bullets. If nothing was decided, say so.
4. Action items. Every action item has three parts: what, who, when. Missing any of the three and it is not an action item.
5. Next meeting or checkpoint. When the group reconvenes, or the next milestone date.

Length: 150-250 words in most cases. Recipients read the first three lines and scan the rest.

Send in the same email thread as the original calendar invite when possible. This keeps the meeting context one click away for anyone who wants to reference back.

The 10 templates

1. Client discovery call

Subject: Follow-up: [Company] intro call, [Date]

Great to connect this morning and hear more about the [company]'s goals for [topic]. Sharing a summary of what we discussed and next steps.

What we discussed:

• Current state of [area they described]
• Main challenges: [top 2-3 they named]
• Ideal outcome in the next 90 days: [what they said]

Next steps:

• I'll send a written proposal by [date]
• We'll reconnect on [date] to review and decide

Looking forward to next week.

2. Internal team sync

Subject: Team sync notes, [Date]

Notes from today's sync, action items highlighted.

Decisions:

• [Topic A]: going with option 2. Owner: name.
• [Topic B]: deferred one week. We'll revisit at next sync.

Action items:

• Name to send [deliverable] by [date]
• Name to loop in [person] about [topic] by [date]

Next sync: [day], [time].

3. Vendor pitch (from the client side)

Subject: Follow-up on [Vendor] discussion

Thanks for walking us through the [product/service] this morning. Recapping what we heard and next steps on our side.

What resonated:

• [Specific feature or capability that matters to us]
• [Specific commercial term worth exploring]

What we still need:

• Case studies from companies in our stage
• Reference contact we can speak with
• Pricing model detail for [specific configuration]

We'll circle back by [date] with our internal decision. Feel free to send along the above materials in the meantime.

4. Sales call (from the vendor side)

Subject: [Product] follow-up, as discussed

Great connecting today. Sharing the key details we discussed so you have them in one place.

How [Product] fits your team:

• [Specific pain they mentioned] solved by [feature]
• Expected time savings based on their usage: [rough estimate]

Attached / linked:

• Case study from [comparable company]
• Pricing summary tailored to their team size

Next step:

• [Their proposed action, e.g., internal review by [date]]

Happy to answer any questions before then.

5. Board or investor update meeting

Subject: [Company] board update, [Date] notes

Recap of today's board meeting for anyone who couldn't join and for reference going forward.

Key updates presented:

• [Metric 1] up X% since last meeting
• [Metric 2] flat, plan to address in Q4
• [Major initiative] on track for [milestone]

Board input:

• [Board member] recommended [action]
• [Board member] flagged concern about [topic]

Next board meeting: [date]

6. One-on-one (manager to direct report)

Subject: Our 1:1 today

Great catchup this morning. Sharing the notes from my side so we're aligned on next steps.

What you're focused on:

• [Priority they named]
• [Second priority]

Where I'll help:

• Unblock [thing] by [date]
• Intro to [person] this week

Next 1:1: [date]

7. Project kickoff

Subject: [Project name] kickoff notes

Notes from today's kickoff. Sharing so everyone starts week one aligned.

Project goal: [one sentence]

Team and roles:

First-week milestones:

• [Deliverable] by [date], owner name
• [Deliverable] by [date], owner name

Weekly sync: [day], [time], starting [date]

8. Weekly status meeting

Subject: Weekly status, [Date]

This week's roundup.

Shipped:

• [Deliverable A]
• [Deliverable B]

In flight:

• [Item]: on track for [date]
• [Item]: at risk, need input from [person]

Blocked:

• [Item]: waiting on [person/decision]

Let me know if I missed anything.

9. External partner check-in

Subject: [Partner name] check-in, notes

Good catching up today. A quick summary for our records and to keep the momentum.

What we agreed:

• [Topic]: moving forward with [option]
• [Topic]: pausing until [date/condition]

Follow-ups:

• Our side: [action, owner, date]
• Your side: [action, owner, date]

Next touch: [date]

10. Quick informal check-in

Subject: Quick recap

Good catching up. Two things from the call worth flagging:

1. [Thing 1]: we agreed [what]
2. [Thing 2]: I'll [action] by [date]

Let me know if I missed anything.

Common mistakes VAs and EAs make on follow-ups

Leading with the pleasantry. "Thanks so much for taking the time this morning" as line one is filler. Skip it or move it to the end. Recipients care about the decisions, not the gratitude.

Vague action items. "We'll circle back on this soon" is not an action item. "I'll send the revised proposal by Friday" is.

Sending from your own email when it should come from the client. If you sit in a meeting as an EA and the follow-up should come from your executive, send it from their account (via Gmail delegate access or send-as). Sending from your own address confuses attendees about ownership.

Waiting too long. Anything past 24 hours reads as an afterthought. Set a habit: draft the follow-up within an hour of the meeting ending, send by end of day.

Related reading

For the sign-off you use on these follow-ups, see How to End an Email Professionally. For follow-ups on unanswered emails (a different pattern), see Follow-Up Email Templates. The broader question of client writing is covered in our communication pillar.

Automating recurring meeting follow-ups

For weekly or recurring meetings, drafting the follow-up email each time is unnecessary work. Two automation patterns most working VAs and EAs adopt within their first six months.

Zapier / Make with Fireflies or Otter. Set the meeting-notes AI (Fireflies, Otter, Fathom) to generate an automated summary at meeting end. Zapier or Make can then trigger a drafted email to a Gmail or Outlook drafts folder using the summary as the body. Review, edit for tone, send. The blank-page cost drops to zero and the review-to-send time is under 90 seconds.

Template-based recurring follow-ups. For meetings with the same structure every time (weekly team sync, monthly board update, quarterly investor call), build a template in your email client and duplicate it for each instance. Only the decisions and action-items sections change. Everything else (subject format, opening line, sign-off, distribution list) stays constant.

The rule of thumb: any meeting that happens more than twice with the same participants should have a repeatable follow-up template. Any meeting that happens more than four times should have automated generation via meeting-notes AI. This scales from a nice-to-have to a workflow necessity as you take on more clients.