How to Write a Follow-Up Email After a Meeting (With Examples)
A good meeting follow-up email does three things: it thanks people briefly, states what was decided, and lists who is doing what by when. Send it within a few hours of the meeting, keep the subject line searchable, and put the actions near the top rather than buried under a long recap. Most follow-up emails fail in predictable ways. They arrive two days late, summarise everything and commit to nothing, or they are so long that recipients skim them and miss the one task with their name on it. This guide gives you a structure that avoids all three failures, plus examples you can adapt for team, client and sales meetings.
The structure of a follow-up email that works
Open with one line of thanks and one line of purpose, for example: Thanks for your time today, here is what we agreed and the next steps. Then give the decisions as short bullet points, written as statements, not discussion summaries. Anyone who was in the meeting should be able to verify them in seconds, and anyone who was not should understand them without asking for background.
Follow decisions with the action list, each item carrying a task, a named owner and a date. End with the next meeting date if one exists, and where the full notes live. That is the whole structure. Background, context and long explanations belong in the attached or linked notes, not in the email body, because the email is the document people will search for and forward.
Timing and subject lines
Send the email the same day, ideally within two to four hours. Memory is fresh, mistakes in the summary get corrected immediately, and the actions land while the conversation still feels current. A follow-up sent next week is not a follow-up; it is an archaeology report, and it usually needs a second meeting to re-agree what the first one decided.
Write subject lines for search, not cleverness. Use the meeting name, the date and the words follow-up or actions, such as: Website Redesign, Client Review 12 Nov, Decisions and Actions. Weeks later, people find emails by searching the project name, and a clear subject line is the difference between a thirty-second lookup and a request for you to resend everything.
Example: internal team meeting follow-up
Subject: Product Weekly, 12 Nov, Decisions and Actions. Body: Thanks all for today. Decisions: we launch the beta to the waiting list on Monday, and the pricing page update moves to next sprint. Actions: Sara to send beta invites by Friday. Tom to confirm support cover for launch day by Thursday. I will update the project plan today. Full notes are linked below. Short, complete and every commitment has a name and a day attached.
Notice what this example leaves out. There is no recap of the debate about launch timing, no list of ideas that were rejected, and no attendance list. Those details live in the meeting notes for anyone who needs them. The email respects the reader time while still creating a written record that can settle a disagreement about what was agreed.
Example: client and sales follow-ups
Client follow-ups add one element: reassurance. After the decisions and actions, confirm the deliverable and date the client cares about most, in their terms, for example: You will receive the first design concepts by Tuesday 19 November. If anything in the summary does not match their understanding, invite correction explicitly. It is far cheaper to be corrected by reply today than to discover a misunderstanding at delivery.
Sales follow-ups should lead with the prospect problem in their own words, then what you agreed to do next. For example: You mentioned reporting takes your team half a day each week. As agreed, I will send the two-page summary and we will run a working session with your operations lead on Thursday. Avoid attaching heavy decks to a first follow-up; a short, accurate email with a dated next step outperforms a glossy one with none.
Letting AI draft it without sounding automated
Drafting this email from your meeting notes takes minutes with a follow-up email generator or the AIMeetingNotes app, which builds the draft from the actual summary, decisions and action items. The draft gives you the correct structure and content instantly, including owners and dates from the meeting itself, rather than from your tired end-of-day memory of who promised what.
Always personalise before sending. Add one genuine line, such as thanks for a specific contribution or a reference to something the recipient said, and read the draft once for tone. Check every date against the calendar, because an AI draft can faithfully reproduce a date that was spoken wrongly in the meeting. Ninety seconds of editing turns a generated draft into an email that sounds like you on a good day, which is exactly the standard to aim for.
Frequently asked questions
The same day, ideally within a few hours. Recipients can correct errors while memory is fresh, and actions feel current. Next-day is acceptable; next-week usually means the meeting needs to happen again.
A brief thank-you, the decisions as clear bullet points, action items with owners and dates, the next meeting if agreed, and a link to the full notes. Keep background and debate in the notes, not the email.
If the informal meeting produced decisions or commitments, yes, but keep it proportional: two or three lines confirming what was agreed is enough. If nothing was decided, no email is needed.
Related pages
Try AIMeetingNotes free
Start on the Free plan with 300 minutes every month. Upload a recording and see your first AI meeting notes in minutes — no meeting bot required, no card needed.