Skip to content
subtl

How to Write a Meeting Summary Email (Templates Included)

Learn how to write a clear meeting recap email in English. Our guide provides the structure, templates, and phrases to summarise decisions and action items.

· 8 min read

A professional working from their home office is writing a meeting summary on their laptop after a call.

A productive meeting doesn't end when the video call disconnects. The conversation is just the first step; the real work begins afterwards. A clear, concise meeting summary is the bridge between discussion and action, ensuring everyone leaves with the same understanding of what was decided and what happens next.

For those of us working in a second language, a written summary is even more critical. It confirms understanding, clarifies any nuances that might have been lost in a fast-paced conversation, and creates a reliable record for everyone to refer back to. This simple document is one of the most powerful tools for effective collaboration.

Why a Meeting Recap Email Matters

Sending a recap email after a meeting might feel like an extra administrative task, but its value is immense. It’s a habit that signals professionalism and builds trust within your team and with clients.

  • It creates a single source of truth. Memories are unreliable. A written summary captures decisions and commitments, preventing the classic "I thought you were going to do that" problem later on.
  • It prevents misunderstandings. In multilingual and multicultural teams, different communication styles can lead to confusion. A written summary, using simple and direct language, ensures everyone is on the same page, regardless of their native language or location. This is especially important for distributed teams working across time zones.
  • It drives accountability. When tasks, owners, and deadlines are clearly listed, it’s easy for everyone to see who is responsible for what. This public commitment encourages people to follow through on their promises.
  • It includes those who couldn't attend. A good summary allows absent team members to catch up quickly on the important outcomes without having to watch a full recording or read a lengthy transcript.

The Anatomy of an Effective Meeting Summary

A great meeting summary is not a word-for-word transcript. It's a concise executive summary focused on outcomes. Here are the essential components to include.

Subject Line: Clear and Searchable

The subject line should make the email easy to find later. Include the project name, the meeting topic, and the date.

  • Good: Meeting Recap: Project Nova Website Launch (24 July 2024)
  • Avoid: Meeting follow-up

Opening: Quick Context

Start with a brief, warm opening. Thank the attendees for their time and state the meeting's date and primary goal in one or two sentences.

  • Example: Hi team, Thanks for your time and input during our call today (24 July) about the Project Nova website launch. This email summarises the key decisions and our next steps.

Key Decisions Made

This is the core of your summary. Use a bulleted list to outline the most important conclusions and agreements reached during the meeting. Be specific and unambiguous.

  • Example:
    • The official launch date for the Project Nova website is confirmed for Monday, 15 August 2024.
    • We will proceed with Design Mockup B for the homepage.
    • The marketing budget for the launch campaign is approved at $10,000.

Action Items: The Engine of Progress

This section turns decisions into action. For maximum clarity, list each action item with a clearly assigned owner and a specific due date. A simple table or a structured list works best.

Action Item Owner(s) Due Date
Finalise homepage copy based on Mockup B. Maria 29 July 2024
Set up social media ad campaigns. David 5 August 2024
Perform final quality assurance (QA) testing. Jin 12 August 2024

If you prefer not to use a table, a list format is also effective:

  • Finalise homepage copy (Owner: Maria, Due: 29 July)
  • Set up ad campaigns (Owner: David, Due: 5 August)
  • Perform final QA testing (Owner: Jin, Due: 12 August)

Open Questions or Parking Lot

Sometimes, important topics are raised that can't be resolved during the meeting. Acknowledge these by listing them in a separate section. This shows you were listening and ensures they won't be forgotten.

  • Example: We also discussed the possibility of adding a German translation post-launch. We will revisit this in our Q4 planning meeting.

Closing and Attachments

End the email with a brief closing statement. Mention the date of the next meeting if it's scheduled. If you shared any documents, like a presentation or a report, link to them here.

  • Example: Please review these points and let me know if I've missed anything. Our next check-in is scheduled for Friday at 10:00 AM. You can find the presentation slides attached.

Templates You Can Use Today

Starting from a template saves time and ensures you don't miss any key components. Here are two templates you can adapt.

Template 1: General Project Meeting Recap

Subject: Meeting Recap: [Project Name] - [Meeting Topic] ([Date])

Hi team,

Thanks for the productive discussion today, [Date], about [Meeting Goal].

Here is a summary of our decisions and next steps.

**Decisions Made:**
*   [Decision 1]
*   [Decision 2]
*   [Decision 3]

**Action Items:**
*   [Task 1] - **Owner:** [Name], **Due:** [Date]
*   [Task 2] - **Owner:** [Name], **Due:** [Date]
*   [Task 3] - **Owner:** [Name], **Due:** [Date]

**Open Questions:**
*   [Question or topic to be discussed later]

Our next meeting is on [Date]. Please let me know if anything is unclear or missing from this summary.

Best regards,

[Your Name]

Template 2: Client Meeting Recap

Subject: Summary of our discussion on [Date]

Hi [Client Name],

Thank you for your time today. It was great to discuss [Meeting Topic] and align on the path forward.

To ensure we are on the same page, here is a brief summary of what we agreed upon:

**Key Understandings:**
*   [Summary of client's need or goal]
*   [Key decision or agreement 1]
*   [Key decision or agreement 2]

**Next Steps (Our Team):**
*   [Action item 1] - **Due:** [Date]
*   [Action item 2] - **Due:** [Date]

**Next Steps (Your Team):**
*   [Action item you need from the client, e.g., 'Provide access to analytics'] - **By:** [Date]

We look forward to our next call on [Date]. In the meantime, please don't hesitate to reach out if you have any questions.

Best,

[Your Name]

Tips for Non-Native English Speakers

Writing a summary in English can feel daunting, but your goal is clarity, not literary perfection.

  • Keep sentences short and simple. Use direct language. Instead of "It was determined that we should endeavor to proceed with...", write "We decided to...".
  • Use templates. They provide a solid structure, so you can focus on filling in the details accurately.
  • Don't be afraid to ask for clarification. If you're writing the summary, it's perfectly acceptable to say at the end of the meeting, "Just to confirm my notes, we decided on X, and Maria will handle Y. Is that correct?"
  • Leverage technology. During a call, having a live transcript can be a great way to catch names, dates, and specific terms you might otherwise miss. After the call, an AI-powered notes feature, like the one in Subtl, can provide a solid first draft of the summary and action items. You can then edit and refine it in your own words before sending.
  • Remember consent. If you use any tool to transcribe or record a call to help with your notes, remember that in many places you need to get consent from everyone first. You can learn more about the specific requirements in our guide on call recording laws.

Even if you're not the designated note-taker, feeling confident enough to speak up in meetings to confirm a point is a valuable skill.

Common Mistakes to Avoid

  • Delaying the send. Send the recap within a few hours, or at the latest, by the end of the business day. The longer you wait, the less impact it has.
  • Being too detailed. The summary is not a transcript. Focus only on the outcomes and actions. No one has time to read a multi-page essay.
  • Using vague language. Avoid phrases like "We'll look into it" or "Someone will follow up." Assign a specific owner to every action item.
  • Forgetting to proofread. A quick read-through can catch typos or unclear sentences that might cause confusion.
  • Assuming silence is agreement. End your email with an invitation for corrections, such as "Please let me know if I've missed anything." This gives people a clear opportunity to correct the record.

Writing a clear, actionable meeting summary is a skill that demonstrates reliability and helps everyone work more effectively. It turns conversation into progress, one email at a time.

By following a clear structure and focusing on outcomes, you can master this essential professional skill. Tools like Subtl can assist by automatically generating a summary and list of action items right after your call, making the process faster and more accurate. This allows you to focus on the conversation, confident that the key points are being captured for your recap later. Learn more about how to get better meeting notes.

meetingscommunicationemailtemplatesenglish

Questions

How soon after a meeting should I send the summary email?

It's best to send it within a few hours, and no later than 24 hours after the meeting. This ensures the details are fresh in everyone's mind and maintains the project's momentum.

What is the difference between meeting minutes and a meeting summary?

Meeting minutes are a formal, detailed, and often official record of proceedings. A meeting summary, or recap email, is an informal, concise overview of key decisions and action items designed to ensure alignment and drive action.

Who is responsible for sending the meeting recap?

Typically, the person who organized or led the meeting sends the summary. However, this role can be delegated or rotated among team members to share the responsibility and develop skills.

Should I ask people to confirm they have read the summary?

It's not usually necessary. A better approach is to end your email with a phrase like, "Please let me know if I've missed or misstated anything." This invites corrections and assumes readership.

How long should a meeting summary email be?

As short as possible while still being clear and comprehensive. Use bullet points and focus only on decisions, action items, and unresolved questions. Aim for something that can be scanned in under two minutes.

How Subtl helps with this

Try it on your next call

40 minutes a month free, no card. macOS 13 or newer.

Read next