How to write a meeting follow-up email
Dylan de Heer
The meeting ended with three people agreeing to do things. By Thursday, some of them will remember it differently, and someone will not remember it at all.
The follow-up email is what stops that. Not a courtesy, not a thank-you note. A short written record of what was agreed, sent while everyone still recognises it as true.
Send it the same day
The value decays fast. Send it within a few hours and it reads as a summary of a conversation everyone remembers. Send it three days later and it reads as a document, which invites people to negotiate with it.
If you cannot send it the same day, send a shorter one. A two-line email today beats a thorough one on Friday.
What a follow-up email actually needs
Four things, in this order:
What the meeting was about, in one line, so it can be found later by searching
What was decided, if anything was
Who is doing what, by when, with names, not "we"
What happens next, or when you will speak again
That is the whole structure. Everything else is optional and most of it is padding.
Two things worth leaving out. The blow-by-blow of the discussion, because once a decision is made the route to it stops mattering. And your own interpretation of what someone meant, because if it needs interpreting it needs asking instead.
Name people, not the room
The most common failure in follow-up emails is the passive voice.
"The pricing will be reviewed" commits nobody. "Sam is reviewing pricing by Friday" commits Sam, and Sam can correct it if that is wrong. That correction is the point. An email that nobody can disagree with is an email that has not said anything.
Use the person's name even when it is you.
Four templates
Copy these and cut what you do not need.
After an internal meeting
After a client call
After a first sales conversation
After a meeting where nothing was decided
That last one matters more than it looks. Meetings that end without a decision are the ones most likely to be quietly forgotten, and writing down that nothing was decided is what stops the same meeting happening again in three weeks.
The subject line does the filing
Put the project or company name first, then what the email is. "Acme, decisions and next steps" is findable in eight months. "Following up" is not.
Avoid "quick question" and "touching base" as subject lines for a follow-up. They are not accurate and they train people to skim.
Send it to the people who were there, and one more
Everyone in the meeting, plus anyone who owns something that came out of it. Not a wider list. A follow-up email that goes to twelve people who were not in the room becomes a status update, and status updates get ignored.
If someone missed the meeting and needs the full picture, that is a meeting summary rather than a follow-up email. They are different documents doing different jobs.
Writing it faster
Most of the effort in a follow-up email is remembering, not typing. If you took notes during the meeting with actions marked as you went, the email is mostly assembly.
If you record instead, the summary and the action list already exist by the time the call ends, and the email becomes an edit rather than a reconstruction. Where the recording gets processed is worth deciding before you press record, particularly for client conversations: most tools send the audio to a server, which means a recording of that conversation now sits on infrastructure you do not control.
Weeve records and writes the summary on your Mac, with no upload step. The free Starter plan covers 10 recordings a month. It is Mac only and needs Apple Silicon with macOS 14 or later.
One caution either way. An AI writes down what it heard, and a follow-up email commits you to things. Read it before you send it.
FAQ
How long should a follow-up email be?
Short enough to read on a phone without scrolling twice. If the actions do not fit, the meeting probably produced too many, which is worth noticing.
Should I say thank you?
One line, if it is genuine. A paragraph of gratitude before the content buries the part that matters, and people skim to the bullets anyway.
What if I disagree with what was decided?
The follow-up email is not the place to reopen it. Record what was agreed accurately, then raise the disagreement separately. Using the record to relitigate the decision makes the record untrustworthy.
Do I need to send one after every meeting?
No. Send one when something was decided, someone committed to something, or the meeting was with a client. A recurring internal catch-up where nothing changed does not need an email, and sending one anyway teaches people to ignore them.
What if nobody replies?
Silence is not agreement, but it is usually acceptance. If something in it was load-bearing, say so explicitly: ask for a yes rather than assuming one. For anything that carries real consequence, the minutes are the right instrument, not an email.
