How to Write a Meeting Recap Email (With Template)

A meeting recap email has three required parts: decisions made, actions assigned (with owners and deadlines), and any open issues that need follow-up. Keep it under 300 words for most meetings. Send it within two hours of the meeting ending, while context is fresh. Skip the meeting summary narrative — your colleagues were there. Get directly to what was decided and what happens next.

Why the Meeting Recap Matters

Most meetings end without a clear record of what was decided. Three days later, two people remember the outcome differently. A week later, the action item that no one wrote down hasn’t happened. A month later, the same conversation happens again.

A meeting recap email fixes this. It creates a written record that everyone can refer back to and holds action item owners accountable without anyone having to play memory games.

For non-native English speakers, the meeting recap is also a chance to demonstrate professional communication at its clearest. A well-structured recap shows that you understood the meeting, can extract the key points, and communicate them in a way that’s useful to your team.

The Template

Subject: Recap — [Meeting Name], [Date]

Hi everyone,

Quick recap from today's meeting.

**Decisions:**
- [Decision 1 — be specific. "We will use Vendor A" not "we discussed vendors"]
- [Decision 2]

**Actions:**
- [Action 1] — Owner: [Name] — Due: [Date]
- [Action 2] — Owner: [Name] — Due: [Date]
- [Action 3] — Owner: [Name] — Due: [Date]

**Open items (need resolution before next meeting):**
- [Question or blocker] — [who is responsible for resolving it]

Next meeting: [date and time, or "TBD"]

Let me know if I missed anything.

[Your name]

Send this within two hours of the meeting. The faster you send it, the more accurate it is and the more useful it is for accountability.

What to Include (And What to Leave Out)

Include:

• Every decision made, stated clearly. Not the discussion — just the conclusion.
• Every action item with a named owner and a specific deadline. “Someone will look into this by next week” is useless — “Priya will research vendor pricing by Friday 5pm” is actionable.
• Open issues that weren’t resolved and need follow-up. Flag who owns the resolution.

Leave out:

• A summary of what was discussed. Your colleagues were there. If someone missed the meeting, they can schedule a catch-up.
• Meeting notes in prose form. Paragraphs are harder to scan than bullet points.
• Attribution for who said what. Decisions and actions are collective; tracking who said what creates political friction for no benefit.
• Filler phrases like “As discussed,” “Per our conversation,” “As mentioned in the meeting.” Get to the content directly.

Before and After Examples

Before (common non-native speaker draft): “Dear team, I would like to take this opportunity to share with you a summary of our meeting that took place this afternoon regarding the Q2 launch. During the meeting we discussed many important topics including the timeline and also the responsibilities of each team member. It was decided that we need to proceed with the original plan.”

After:

Subject: Recap — Q2 Launch Planning, April 14

Hi team,

**Decisions:**
- Proceed with original June 3 launch date (not delayed)

**Actions:**
- Creative brief final draft — Owner: Marcos — Due: April 18
- Vendor shortlist (3 options) — Owner: Yuna — Due: April 19
- Stakeholder presentation deck — Owner: Bryan — Due: April 22

**Open items:**
- Budget approval still pending with Finance. Marcos to follow up with CFO by April 16.

Next meeting: April 23, 10am CET

[Name]

The second version takes 20 seconds to read and everyone knows exactly what they need to do. The first version takes two minutes and tells you almost nothing actionable.

Adapting the Template for Different Meeting Types

Standup or Quick Check-in (under 15 minutes)

Skip the formal structure. A two-line Slack message or email works: “Quick recap: [what’s complete], [what’s in progress], [what’s blocked]. [Name] to resolve [blocker] by [date].”

Client Meeting

Add a preamble that confirms the relationship context and cc the right people. Keep the same structure, but phrase decisions as “agreed” rather than internal directives:

Subject: Meeting Recap — [Client Name] x [Your Company], [Date]

Hi [Client Name],

Thanks for the time today. Quick recap for our records.

**Agreed:**
- [Decision framed as mutual agreement, not instruction]

**Actions — Our side:**
- [Item] — Owner: [Your team member] — Due: [Date]

**Actions — Your side:**
- [Item] — Owner: [Client contact] — Due: [Date]

Please let us know if anything differs from your understanding.

[Your name]

The “please let us know if anything differs” line is important. It invites the client to flag discrepancies while there’s still time to address them.

All-Hands or Town Hall

Don’t write a full recap for every all-hands. A brief “Key takeaways” summary posted to the team channel is more appropriate — three to five bullet points covering the announcements that require action or follow-up.

Who Should Write It

The meeting owner (the person who called the meeting) is the natural owner of the recap. But in practice, the person who took notes during the meeting — or the most junior person in the meeting if that’s your team’s convention — often handles it.

If you weren’t explicitly assigned the recap and no one else has sent one within an hour of the meeting ending, send it. Being the person who writes meeting recaps consistently is a simple, undervalued way to demonstrate organizational reliability and communication clarity.

For more on structuring professional communication around meetings, see our guide on how to run a meeting recap email and meeting notes best practices.

FAQ

How long should a meeting recap email be?

For a 30-60 minute meeting, aim for under 300 words. For a 90-minute working session with complex outcomes, up to 500 words is reasonable. If you’re writing more than 500 words, consider whether you’re including narrative that could be cut.

Should I send the recap to everyone in the meeting or a wider group?

Start with everyone in the meeting plus anyone who was invited but couldn’t attend. For decisions that affect a wider team, consider a brief second message to the wider group with just the decisions and actions that affect them — not the full recap.

What if someone disagrees with the recap?

This happens. The standard response is to update the recap with the correction: “Update — [Name] has noted that the deadline for [item] is actually [corrected date].” Treat disagreements as helpful corrections, not challenges.

Can I use AI tools to write meeting recaps?

Yes. Tools like Otter.ai and Fireflies transcribe meetings automatically and generate draft summaries. You still need to review and edit — automated summaries often include noise and miss the most important decisions. Use them as a starting draft, not a finished product.

Is it acceptable to write a meeting recap in bullet points only?

Yes, and for most meetings it’s preferable. Bullet points are faster to read, easier to scan for action items, and less likely to bury important decisions inside narrative sentences.