Here is an uncomfortable fact about the meeting you just left: within a day, most of it will be gone. Classic memory research — Ebbinghaus's forgetting curve, replicated as recently as 2015 by Murre and Dros — shows we lose roughly half of new information within an hour and around 70% within 24 hours. Meeting-productivity surveys land in the same place: decisions that aren't written down and shared quickly simply stop existing. Everyone walks out with a slightly different movie of what was agreed.
The follow-up email is the cheap, unglamorous tool that fixes this. Not a transcript, not a novel — a short message that pins down what was decided, who owns what, and what happens next. Done well, it takes five minutes and saves you the second meeting you'd otherwise need to re-litigate the first one. Done badly (or not at all), it's how projects quietly drift for weeks.
This guide is the whole craft in seven steps, with copy-paste templates. It works for client calls, internal syncs, sales conversations, and one-on-ones alike.
1. Send it within 24 hours — sooner if anything was ambiguous
Timing is the single highest-leverage variable. The forgetting curve is steepest in the first hours, and that applies to your recipients as much as to you: a recap that lands the same afternoon gets checked against fresh memory and quietly corrected ("small thing — I said end of next week"). The same recap three days later gets skimmed, half-remembered, and silently accepted even where it's wrong. If a decision was contentious or fuzzy, send the summary while people can still push back accurately.
2. Write a subject line people can find in three weeks
The subject line has two jobs: get opened today and get found later. "Following up" fails both. Name the meeting, the topic, and ideally the date — because the real test of a follow-up email is whether someone can dig it out of their inbox mid-argument three weeks from now.
- Internal sync: "Recap + action items — Q3 pricing review (Aug 7)"
- Client call: "Next steps from today's onboarding call — Acme × Meridian"
- Sales conversation: "Proposal timeline we discussed — [Your company] for [Their company]"
- Interview or 1:1: "Thanks — and the two things I promised you"
3. Open with one sentence of context, not a paragraph of thanks
Gratitude is fine; throat-clearing is not. One line does it: "Thanks for the time today — here's where we landed." Your recipients aren't reading this email for warmth, they're reading it to confirm their understanding matches yours. The kindest thing you can do is get to the substance in the first ten words. Save the relationship-building for the actual relationship.
4. Lead with decisions, not discussion
This is where most follow-ups fail. A chronological replay — "first we talked about X, then Sarah raised Y" — buries the only thing that matters. Nobody needs the journey; they need the destination. State each decision as a flat fact, and if something was explicitly not decided, say that too. "Parked: EU rollout timing — revisit after the September numbers" prevents the classic failure where half the room thinks a tabled item was a yes.
Three to five bullets is the sweet spot. If you have more than that, you likely had more than one meeting's worth of meeting — summarize the top level and link out to fuller notes. There's a reason nobody reads AI meeting summaries: they optimize for completeness over judgment. Your edge as a human writing the recap is ruthless selection.
5. Give every action item an owner and a date
An action item without a name and a deadline is a wish. The format that survives contact with real inboxes is brutally simple: who — what — by when. "Priya — send revised SOW — Thu Aug 13." Not "we should update the SOW soon." If you don't know the owner, that's not a formatting problem, it's an unfinished decision — flag it as an open question rather than laundering it into vagueness.
Two details that separate professionals from everyone else: assign dates even to small things (undated tasks are where momentum goes to die), and include your own items first. A follow-up that only assigns work to other people reads exactly how you'd expect.
6. Close with the single next step
End with exactly one forward-looking line: the date of the next meeting, the trigger for the next conversation, or the one reply you need ("If the timeline works, just reply 'confirmed' and we'll kick off Monday"). One clear ask gets answered; three asks get archived. If you need multiple things from multiple people, that's what the action-item list above was for — the closing line is the heartbeat, not another list.
7. Fix your inputs: the recap is only as good as your notes
Here's the part most guides skip. Every step above assumes you actually know what was decided — and if you were the one presenting, negotiating, or running the room, you probably weren't taking notes. You were participating. Research on why we forget meetings is blunt about this: active participants encode less of the conversation than observers, because attention spent talking is attention not spent storing.
So the real bottleneck of a great follow-up email isn't writing skill. It's having a reliable record of the conversation without having played stenographer during it. This is exactly the problem a private meeting recorder solves — and why the people who send the best recaps often type the least during meetings.
The follow-up email that writes itself
Meetly records and transcribes your meetings entirely on your iPhone — no bot joining the call, no cloud uploads, no account. Walk out of the meeting with the decisions and action items already captured, then turn the summary into your follow-up email in two minutes. Private by architecture, free to start.
Download MeetlyThe templates
Adapt freely — the structure is the point, not the exact words.
Internal meeting recap
- Subject: Recap + actions — [meeting name] ([date])
- Thanks all — here's where we landed.
- Decided: [decision 1]. [Decision 2]. Parked: [tabled item + when it comes back].
- Actions: [Name — task — date] for each item, your own first.
- Next: [next meeting date or trigger]. Flag anything I got wrong by [day] — after that this is the record.
Client or prospect call
- Subject: Next steps from today's call — [you] × [them]
- Great speaking today. Quick summary so we're aligned:
- What you told us: one or two lines proving you listened — their constraint, their deadline, their words.
- What we agreed: the decisions, flat and unambiguous.
- On us / on you: two short lists, each with dates.
- Next: the single reply or milestone that moves things forward.
What separates a good follow-up from inbox noise
Scan any thread where a project went sideways and you'll usually find the moment a follow-up email should have existed and didn't — or existed but summarized the discussion instead of the decisions. The seven steps compress to one principle: write for the person searching their inbox in three weeks, not the person who was in the room today. Findable subject, decisions first, named owners, dated tasks, one next step, sent while memory is fresh.
And if taking notes while actually participating is the step that keeps breaking, stop treating it as a personal failing. It's a bandwidth problem, and it has a tool-shaped solution.
Be present in the meeting. Perfect in the follow-up.
Meetly captures every meeting privately on-device — 90+ languages, instant summaries, zero bots. Your next follow-up email starts from a real record instead of a half-remembered blur. Download free on iPhone.
Download MeetlyFrequently asked questions
How soon should you send a follow-up email after a meeting?
Within 24 hours, and ideally the same day. Memory research shows people forget roughly half of a conversation within an hour and most of it within a day — a same-day recap gets checked against fresh memory and corrected, while a late one gets skimmed and silently accepted even where it's wrong.
What should a meeting follow-up email include?
Five things: a searchable subject line naming the meeting and date, one line of context, the decisions made (including what was explicitly parked), action items in who–what–by-when format, and a single clear next step. Skip the chronological replay of the discussion.
How long should a follow-up email be?
Short enough to read without scrolling on a phone — usually 100 to 200 words. Three to five decision bullets and a handful of dated action items beat a page of prose. If you need more, link out to full notes instead of inflating the email.
How do you write a follow-up email if you didn't take good notes?
Send what you're confident about and explicitly ask others to fill gaps — vague confidence is worse than honest gaps. Longer term, fix the input problem: record and transcribe your meetings (with consent) using an on-device tool like Meetly, so the recap starts from a real record rather than reconstruction.
Should you send a follow-up email after every meeting?
After every meeting where something was decided or assigned, yes — even a two-line recap. Pure status updates or FYI meetings usually don't need one. The test: if two attendees could plausibly disagree later about what happened, write it down now.
