How to Write a Meeting Summary: Examples and Template [2026]

Most meeting summaries fail because they are either too long to read or too vague to act on. This 2026 guide solves both with a simple 5-step framework for writing a summary people actually use.

In less than 20 minutes, you will get:

A checklist of critical items to include
A copy-and-paste meeting summary template
Two real-world examples to model your recaps after

Before you start: meeting notes are what you capture during a session, whereas a meeting summary is what you send afterward. If you are currently mid-meeting, check out our guide on how to take meeting notes instead.

What Is a Meeting Summary?

A meeting summary is a short written record of what was discussed, decided, and assigned during a meeting. It is different from a transcript in that it condenses key takeaways rather than providing a word-for-word account of the conversation. This high-level record is shared with attendees after the call to confirm alignment and make action items visible. See how it compares to meeting minutes in terms of scope, format, and purpose.

Meeting Summary vs. Meeting Minutes: What Is the Difference?

The main difference between a meeting summary and meeting minutes comes down to formality. Meeting minutes act as a formal and comprehensive record of your session, serving as an official document for compliance and legal tracking. A meeting summary, on the other hand, is a brief and informal overview designed to quickly align your team, highlight key takeaways, and confirm immediate next steps.

What Should a Meeting Summary Include?

As your meeting summary is meant to be a quick reference sheet, you'll want to keep it brief and focused on the facts. Here is exactly what to include in a meeting summary.

(Optional) For long or complex sessions, add a single-sentence overview at the top summarizing the biggest takeaway from the entire meeting.

Date: Write down the calendar date so you can track your timeline later.
Time: Note the start and end times for an accurate record of the meeting's length.
Attendees: List everyone who joined, plus any key people who missed it.
Meeting objective: State the main goal of the meeting in one simple sentence.
Key discussion points: Summarize each agenda topic in exactly one concise sentence.
Decisions made: Write down the final choices or policy updates so nobody leaves guessing.
Action items: List clear tasks with a specific owner and a firm due date attached. See our guide on action items for how to assign these well.
Next meeting date: Add the date for your next follow-up if your team needs one.

How to Write a Meeting Summary in 5 Steps

Drafting a meeting summary doesn't have to be overwhelming or overly complicated. Just follow these five steps to keep things simple and your team aligned.

Start during the meeting, not after. Jot down decisions and action items as they happen, don't wait until the call ends. Waiting makes it much harder to remember the details your team needs.
Write within 24 hours while context is fresh. Draft your summary while the conversation is still top of mind. Delays cause important details to fade, which leads to misalignment and forgotten tasks.
Lead with decisions and action items. Put the most important outcomes at the top of your summary, not buried in the middle. Your team's first question is always "what do I need to do," not "what did we talk about."
Be specific with your tasks. Every assignment needs a named owner and a firm due date. A vague task like "follow up with client" tends to get ignored, while "@Marcus: Email proposal by Friday" makes it clear who owns it.
Send it to the right people. Send the summary to everyone who attended, and loop in any absent stakeholders who now own an action item.

Meeting Summary Examples

Looking at a blank page is the hardest way to start writing. To make things easy, we put together two realistic, real-world examples that you can copy, paste, and tweak for your own team. Notice how the format changes depending on whether you are running an internal project sync or an external sales call.

Example 1: Project Status Update Summary

Date: June 22, 2026

Attendees: Marcus (Product), Sarah (Design), Dave (Dev), Elena (Marketing)

Meeting Objective: Finalize homepage wireframes and lock down the engineering timeline for the website redesign.

Decisions Made:

Approved the "Option B" homepage hero layout because it creates a cleaner experience for mobile users.
Postponed the resource-heavy blog page redesign to Phase 2 to guarantee the core checkout flow launches on schedule.

Action Items:

@Sarah: Export final Figma assets for the homepage and hand them off to development by June 25.
@Elena: Draft three copy variations for the main hero header button by June 24.
@Dave: Set up the staging environment and send access links to the team by June 29.

Key Discussion Points:

The team reviewed mobile user testing data which showed a noticeable conversion lift on the simplified navigation menu.
Dave raised concerns about engineering capacity, leading to the decision to defer the blog layout updates.
Elena highlighted the need for tighter headline copy to match the sleek design of the new header block.

Next Meeting Date: July 6, 2026, at 10:00 AM EST.

Example 2: Sales Call Summary

Date: June 23, 2026

Prospect Name: Apex Logistics (Point of Contact: Jim Vance, Operations Director)

Attendees: Chloe (Account Executive), Sam (Technical Sales Specialist)

Call Objective: Demonstrate the automated dispatch module and address enterprise pricing tiers for a 50-driver fleet.

Decisions / Outcomes:

Apex confirmed that our routing automation matches their exact technical requirements and solves their main operational bottleneck.
Jim agreed to bypass a second demo and move straight to a security review if the custom pricing proposal fits their quarterly budget.

Key Topics Discussed:

Product Fit: The prospect loved the real-time driver tracking dashboard and confirmed it resolves their current communication delays.
Pricing Structure: Jim raised questions about volume discounts for seasonal contract drivers who only need system access for three months out of the year.
Objections Raised: The prospect expressed concern about the system migration downtime, but Sam reassured them with our weekend data-transfer protocol.

Next Steps:

@Chloe: Send a customized enterprise pricing proposal reflecting the requested seasonal driver discounts by June 24.
@Sam: Email our standard IT security questionnaire and data compliance packet directly to Jim's infrastructure team by June 25.
@Chloe: Follow up with Jim via phone to schedule the contract review session on June 30.

Free Meeting Summary Template (Copy and Paste)

If you are tired of formatting your notes from scratch every week, copy and paste this meeting summary template directly into your docs or email. Just fill in the blanks right after your next session ends.

[Meeting Title]

Date: [Insert Date]

Attendees: [List everyone present]

Meeting Objective: [State the primary goal of the session in one clear sentence]

Key Discussion Points

[Agenda Item 1]: [Summarize the discussion on this topic in a single sentence]
[Agenda Item 2]: [Summarize the discussion on this topic in a single sentence]

Decisions Made

[List the first major conclusion or official decision agreed upon by the team]
[List the second major conclusion or official decision agreed upon by the team]

Action Items

Task	Owner	Due Date
[Insert a specific, clear task]	[Name]	[Date]
[Insert a specific, clear task]	[Name]	[Date]

Next Steps

[Note any immediate follow-up or next meeting date]

💡A quick note on tailoring your summary: you can adapt this base template to fit different meeting types without needing a separate file. For sales calls, add a section below decisions for Objections Raised and Next Commercial Steps. For internal project meetings, add a section tracking Blockers and Risks to flag problems before they stall your timeline.

Want Fireflies to generate this automatically? It joins your call, captures everything, and sends the summary straight to your inbox. See how it works

How AI Writes Your Meeting Summary Automatically

Everything we have covered so far assumes that you or someone on your team is writing these recaps manually. If you are running back-to-back sessions all day, finding the time to stop, synthesize your thoughts, and format a clean document is incredibly difficult.

To see how you can hand this entire process over to automation, look at what an automated summary looks like for the exact same Apex Logistics sales call from our earlier example.

Fireflies Automated Output: Apex Logistics Sales Call

Meeting Overview: Chloe and Sam met with Jim Vance from Apex Logistics to demonstrate the automated dispatch module for their 50-driver fleet. Jim confirmed the system resolves their core routing bottlenecks and real-time tracking issues. He expressed interest in moving directly to a contract and security review, provided the customized volume pricing tier accommodates their seasonal contract drivers.

Key Decisions Made:

Apex Logistics will bypass a secondary platform demonstration to fast-track implementation.
Jim Vance agreed to initiate an infrastructure security review once the custom quote is delivered.

Action Items:

@Chloe: Send enterprise pricing proposal with seasonal driver discounts. Due: June 24.
@Sam: Email IT security questionnaire and compliance packet to Jim's team. Due: June 25.
@Chloe: Call Jim to confirm security docs and schedule contract review. Due: June 30.

That entire summary was generated automatically. Fireflies joined the call, transcribed the conversation, and produced this output without anyone on the call taking a single note. No one had to stop participating to write anything down, and no one had to spend time after the call piecing it together.

Fireflies joins your meeting, transcribes every word, and delivers a structured summary with decisions, action items, and owners before you even close your laptop. It routes that summary straight to Slack, your inbox, or your CRM, so the right people see it automatically. Free plan available.

Try Fireflies for Free

Frequently Asked Questions

How long should a meeting summary be?

Keep your standard meeting summaries around 150 to 300 words. That's short enough for your team to read in under two minutes. For big or complex project syncs, cap it at 500 words maximum.

Skip the play-by-play and focus on core decisions, next milestones, and clear action items with a specific owner and deadline attached. If your summary keeps creeping past that 500-word mark, you are likely capturing the discussion instead of the decisions.

How do you send a meeting summary after a meeting?

Send it within 24 hours, while the discussion is still fresh, to everyone who attended plus anyone assigned an action item, even if they missed the meeting.

A few quick rules for the actual send:

Channel: Email is the default, though Slack or a shared doc works fine for informal internal teams.
Subject line: Name the meeting and date, like "Summary: Q2 Planning Meeting, April 2," so people can find it later.
Format: Keep your meeting summary email easy to scan, with the recap and action items visible without scrolling.

Can AI write a meeting summary automatically?

Yes. Fireflies joins your meeting, transcribes the conversation, and generates a structured summary with decisions and action items as soon as the call ends. No manual notes or post-meeting write-up needed. See the "How AI Writes Your Meeting Summary Automatically" section above for what this looks like in practice.

The Recap That Actually Gets Read

A great meeting summary is short, specific, and sent quickly. With the five-step process, the copy-paste template, and the worked examples in this guide, you now have everything you need to keep your team aligned. If you would rather skip the manual writing altogether, that is exactly what Fireflies is built for.

Try Fireflies for free and let it handle the next recap for you.