Meeting Follow-Up Email Templates

The goal is a shared reference point, something people can return to when questions come up two weeks later.

A strong meeting recap covers what was decided, who owns what next, and anything still unresolved. Here's what that looks like in practice:

"Hi team, quick recap from today's call. We agreed to move the launch date to June 15. [Name] owns the updated landing page copy by Friday. [Name] will confirm the paid budget by EOD Tuesday. Still open: whether we run the webinar before or after the Product Hunt launch. [Name], can you confirm by next Wednesday?"

That email takes two minutes to write and saves five rounds of "wait, what did we decide?" over the next two weeks. For client meetings, copy anyone who was in the room but not on the original invite so nothing falls between teams. Link or attach any slides or documents discussed, so the recap is the single place someone goes to reconstruct what happened.

Send the recap the same day the meeting ends. A few hours after is ideal, but if it ran late in the afternoon, first thing the next morning is fine. Waiting longer risks the follow-up feeling like a formality rather than a working document.

For client meetings, turnaround time matters more. A same-day recap signals that the conversation was taken seriously and gives the client something to act on before their attention shifts elsewhere. Internal meeting recaps have slightly more tolerance for a next-morning send, especially when the action items aren't time-sensitive.

"Recap: [Meeting Name], [Date]" is clean, searchable, and does the job. "Next steps from our [Date] call" works well when the meeting was primarily a decision-making session with clear outputs.

Avoid vague subject lines like "Following up on our conversation." Six months from now, neither you nor the recipient will know which meeting that refers to. The subject line should work as an archive label, specific enough to find quickly and descriptive enough to tell you what is inside before you open it.

For group meeting recaps, reply to the calendar invite thread or the email thread that set up the meeting so every attendee is automatically included. If the meeting was informal with no prior thread, send the recap to all attendees directly or as a group, depending on whether you want full transparency.

In client-facing group meetings, consider sending the primary note to your main contact and copying others rather than addressing the full group at once. This keeps the main relationship channel clear and avoids a reply-all thread that fills up with individual acknowledgments.

Yes, if no one else does. The value of a meeting recap is in having one at all. Who sends it matters less than whether it exists. If you're an attendee and the organizer hasn't followed up within a few hours, send a brief note yourself. Frame it as a shared resource rather than a correction: "Wanted to capture what we discussed while it's fresh" lands better than anything that implies the organizer dropped the ball.

For recurring meetings where recap responsibilities are shared or rotating, it's worth agreeing upfront who owns it each session. That's a cleaner system than someone stepping in after the fact every time.

A meeting recap focuses on what was decided and what happens next. A thank-you email focuses on the relationship and the interaction itself. They serve different purposes and fit different types of meetings.

Recaps work best for working sessions, client calls, project reviews, and any meeting where decisions were made and tasks were assigned. Thank-you emails are better suited to first introductions, job interviews, sales discovery calls, or any meeting where the relationship itself is the main outcome.

For most professional meetings, a recap with a brief note of appreciation at the top is more useful than a standalone thank-you. The recap gives the reader something to act on; a standalone thank-you doesn't.