A meeting ends and everyone leaves with a slightly different understanding of what was decided. The recap email is what prevents that from becoming a problem three weeks later.
A good meeting recap is not a transcript of the conversation. It is a short, clear record of the decisions made, the actions assigned, and when things are due. It takes 10 minutes to write and saves hours of follow-up confusion.
What a Good Meeting Recap Email Includes
The goal is to leave every participant with the same clear picture of what happened and what is expected of them next.
Required elements:
- Decisions made. Any question that was resolved in the meeting. Not everything discussed — just what was actually decided.
- Action items. Each with a specific owner and a specific date. "TBD" and "someone will handle it" are not action items.
- Open questions. Things raised but not resolved. Who is responsible for getting an answer and by when.
- Next meeting or next step. If there is a follow-up meeting, include the date. If there is not, say so.
What to leave out:
- Lengthy summaries of what was discussed but not decided
- Who said what (unless attribution matters for accountability)
- Your personal commentary on how the meeting went
- Filler like "great discussion today" or "it was productive as always"
Meeting Recap Templates
Short and informal — internal team
For recurring internal meetings, standups, or any meeting where the relationship is close and the stakes are low.
Subject: [Meeting name] — recap [date]
Decisions:
- [Decision 1]
- [Decision 2]
Actions:
- [Name]: [task] by [date]
- [Name]: [task] by [date]
Open: [anything unresolved and who is handling it]
Next up: [next meeting or next milestone]
No greeting, no pleasantries, no sign-off required for an internal standing meeting. The faster someone can extract the action items, the more likely they are to actually read the email.
Standard professional recap
For client-facing meetings, cross-team meetings, or any context where a slightly more formal record is appropriate.
Subject: Recap — [Meeting topic] — [Date]
Hi [Name / All],
Thanks for the time today. A few things to document from the conversation:
Decisions
- [Decision 1]
- [Decision 2]
Action items
- [Name]: [task] — due [date]
- [Name]: [task] — due [date]
Open items
- [Question or topic]: [Name] will follow up by [date]
Next steps [Next meeting date, or what triggers the next conversation]
Let me know if I missed anything or if there are corrections.
[Your name]
The closing line is useful. It signals that the recap is a working document, not a verdict — which encourages people to speak up if something is wrong rather than letting an error compound.
Client-facing recap after a project meeting
For external stakeholders where the recap also serves as a record of understanding and agreement.
Subject: Notes from our [project] meeting — [date]
Hi [Client name],
Thanks for the time today. Here is a summary of where things landed:
Agreed decisions
- [Decision 1, with enough detail that context is clear]
- [Decision 2]
Next actions
Owner Task Due [Client] [What they agreed to do] [Date] [You/Your team] [What you agreed to do] [Date] Open items
- [Item]: we agreed to revisit this on [date / at the next meeting]
Next meeting [Date and time, or: we will schedule once [trigger occurs]]
Please let me know if anything looks different from your recollection.
[Your name]
The table format for action items works especially well in client-facing recaps because it makes ownership unambiguous. No one can later say "I thought that was your responsibility."
Recap after a sales or discovery call
For post-call follow-ups where the goal is to move the relationship forward, not just document.
Subject: Good talking today — a few things from our call
Hi [Name],
Good talking today. Here is what I took away:
What we covered
- [Key topic or problem discussed]
- [Their stated need or challenge]
What I will send you
- [Resource, proposal, or information you committed to]
- By: [date]
What I heard you want to figure out
- [Their open question or next step on their side]
Let me know if that lines up with your takeaways. Looking forward to talking again on [date / once you have reviewed].
[Your name]
This version doubles as a recap and a soft advance. It shows you were listening, documents your commitments, and gives them a clear reason to reply.
Follow-up email after a meeting when no further meeting was scheduled
For one-off meetings or project check-ins where there is no standing next meeting to anchor the follow-up.
Subject: Notes from [meeting topic] — [date]
Hi [Name],
Here is a quick summary for the record:
- [Decision or outcome 1]
- [Decision or outcome 2]
- [Your action item and deadline]
Let me know if you have questions or if I got anything wrong.
[Your name]
Subject Line for a Meeting Recap Email
The subject line should be specific enough that the recipient immediately knows which meeting this is about. Especially important when they attend many meetings.
Effective formats:
- "Recap — [Project/Topic] — [Date]"
- "Notes from [Meeting name] — [Date]"
- "[Project] meeting — summary and actions"
- "Follow-up: [Meeting topic]"
Avoid:
- "Meeting notes" (too vague if they have multiple meetings)
- "Following up" (could be about anything)
- "Important" (overused)
If you send the recap within a few hours of the meeting, replying to the original calendar invite thread is an option — it keeps context and prevents inbox clutter.
When to Send a Meeting Recap
Same day, ideally within a few hours. The sooner the recap goes out, the more useful it is. Action items are clearer when they are fresh, and corrections surface faster.
Exceptions: If you need more than 24 hours to write a useful recap, something went wrong — either the meeting lacked clarity or the recap is being asked to do more work than it should. A recap of a well-run meeting should take 10-15 minutes.
Common Mistakes in Meeting Recap Emails
Writing a summary instead of a record. A recap is not a narrative of what happened. It is a structured list of decisions and actions. If your recap uses full paragraphs to describe the discussion, it is doing the wrong thing.
Vague action items. "We will look into this" is not an action item. "Sarah will send the vendor comparison to the team by Friday" is.
Missing deadlines. Every action item without a deadline is an action item that will be deferred indefinitely. If no deadline was set in the meeting, set one in the recap.
Sending it too late. A recap sent three days later is a recap people will not read. If you cannot send it same-day, send it first thing the next morning.
Recapping what you discussed rather than what you decided. The purpose of a meeting is decisions, not conversation. The purpose of a recap is to record those decisions.
The Voice of a Recap Email
Meeting recaps are functional documents, but they still carry your voice. A recap that reads like a legal brief is harder to act on than one that reads like a clear message from a person. The best recaps are direct and precise without being terse, and they leave no ambiguity about who owns what.
If you run a lot of meetings and send a lot of recaps, the cumulative effect of your recap style matters. It shapes how your team experiences your communication and whether they trust the written record. A consistently clear, accurate, quick recap is one of the quieter signals of strong professional communication.
Generate a persona prompt for drafting clear, direct meeting recaps →