Most meetings end with a reasonable shared understanding of what was discussed. A week later, that understanding has fractured. One person thought the deadline was Friday. Another thought it was still being decided. Someone else did not realize they owned anything at all.
A meeting summary fixes this, but only if it is written clearly and reaches the right people quickly. Research from Zoom found that 54% of employees want post-meeting summaries and action items, but only 39% report receiving them. The intention is there; the follow-through usually is not.
A good meeting summary does not need to be long. It needs to capture what was decided, who is doing what, and anything that was left unresolved. Below is a template you can copy immediately, followed by guidance on writing summaries that get used.
Ready to use meeting summary template
This template works across meeting types: project kick-offs, client calls, team syncs, strategy sessions, and one-to-ones. Adjust the fields that don’t apply.
Meeting details:
Date:
Time:
Location / platform:
Meeting type: [Team sync / Client call / Project review / Strategy / One-to-one / Other]
Facilitator:
Note-taker:
Attendees;
Absent / to be looped in:
Meeting objective:
[One sentence: what this meeting was trying to achieve or decide]
Summary of discussion:
[Key points raised, in order. Focus on substance rather than who said what, unless attribution matters. Two to five sentences per topic is usually enough.]
Decisions made:
[Decision — be specific enough that there’s no ambiguity about what was agreed]
Action items:
[Action] — [Owner] — [Due date]
Items deferred or tabled:
[Topic] — [Reason deferred] — [When it will be revisited]
Questions outstanding:
[Question] — [Who is finding the answer] — [By when]
Next meeting:
Date / time:
Purpose:
Who needs to attend:
Summary distributed to:
[Names / distribution list] — [Date sent]
The deferred items and outstanding questions sections are ones that teams consistently skip. Decisions that nearly got made but didn’t tend to reappear in the next meeting without context, which wastes time. Questions that were raised but not answered often get forgotten entirely. Capturing them explicitly keeps things moving even when the meeting itself didn’t fully resolve them.
How to write action items that get followed up
The action items section is the part of a meeting summary that determines whether the meeting had any lasting effect. Vague action items are the most common reason things do not get followed up. "Chase the supplier" is not an action item. "Jamila to contact the supplier by Thursday to confirm the revised delivery date and share an update in the project channel" is.
Every action item needs three things: a clear description of what needs to happen, a named owner (a person, not a team), and a deadline. If the deadline is not specific, use a day of the week rather than "end of week" or "soon," which different people read differently.
It also helps to note what the action connects to. If an action is blocking something else, say so. "Finn to confirm budget sign-off by Tuesday, required before the design brief can be finalized" gives the owner context that makes the deadline feel real rather than arbitrary.
After the meeting, the action items in the summary are only useful if they reach the right people. For guidance on writing follow-up messages that get read, see our piece on how to write a follow-up email that gets a response.
What a meeting summary is, and what it isn't
A meeting summary is not a transcript. You're not trying to record every word spoken or every tangent explored. The goal is to document what was decided, what needs to happen next, and anything that needs to be communicated to people who were not in the room.
It is also not a minutes document in the formal sense, unless your organization or context requires that. Formal minutes, with a verbatim or near-verbatim record of discussion, formal motions, seconders, and voting outcomes, are used in board meetings, governance contexts, and some formal committee settings. For most working meetings, a clear and practical summary is more useful and more likely to be read.
The distinction that matters most is between a description of what happened and a record of what was agreed. A summary that says "The team discussed the timeline" is not actionable. "The timeline was revised: Phase 2 now starts on 14 April. Sam to update the project board and notify the client by end of day Friday" is.
How long should a meeting summary be?
Short enough that people read it. That usually means under one page for a working meeting. For a longer strategy session or a significant client call, two pages is reasonable. More than that, and you are writing a document rather than a summary.
A useful rule: if someone cannot read the summary in under three minutes, it is too long. The people who need to act on the outcomes do not have time to excavate the decisions from several paragraphs of discussion summary. Lead with decisions and actions, and put the discussion context below that for anyone who needs it.
If the meeting was especially complex and the discussion context is important, consider a two-section format: a short executive summary at the top (decisions, actions, next steps, under half a page) followed by a fuller discussion record for reference. Most people will only read the first section most of the time.
Meeting summary vs meeting notes: the practical difference
Meeting notes and meeting summaries are often used interchangeably, but they serve slightly different purposes. Notes are usually a live capture during the meeting: rough, chronological, and unfiltered. A summary is what you produce after the meeting, having filtered the notes into what matters.
If you are the note-taker, the practical workflow is: capture notes during the meeting without worrying too much about structure, then spend 10 to 15 minutes afterward turning those notes into a clean summary using the template above. The notes become your working document; the summary is what gets distributed.
For meetings that benefit from richer, structured notes during the session itself, such as one-to-ones, check-ins, and performance conversations, our 1-2-1 meeting notes template covers that format in detail.
Adapting the template for different meeting types
No two meetings need the exact same summary. A client call calls for more polish than a quick team sync, and a strategy session needs room for open questions that a status update doesn't. Use the template as your starting point, then adjust the emphasis based on who's reading it and what they need to walk away knowing.
Client and external meetings
For client meetings, the summary often serves as the formal record of what was agreed, which makes accuracy and clarity especially important. Decisions about scope, timelines, or deliverables should be captured with precision, not approximation. It is good practice to share the summary with the client and ask them to confirm if anything looks incorrect. Asking them to confirm keeps both sides working from the same understanding of what was agreed.
For client summaries, the tone should be professional and readable by someone outside your team. Avoid internal shorthand, jargon, or references that require background knowledge the client does not have. The summary may be forwarded to stakeholders who were not on the call.
Project reviews and status meetings
Project review summaries benefit from a consistent structure across meetings, so that progress and blockers can be tracked over time. Including a "status since last meeting" section at the top gives context before moving into new decisions and actions. Flagging items that have moved from "in progress" to "complete" is worth doing explicitly, because it makes the meeting feel productive even when there are also things still stuck.
If your team also sends a regular weekly progress update to stakeholders, the project review summary is a natural source for that. A consistent format across both makes the information easy to absorb and compare week on week.
Strategy and planning sessions
Strategy sessions produce a lot of discussion and relatively few firm decisions, which makes the summary harder to write but more important to get right. The deferred items and outstanding questions sections are especially valuable here: many strategic conversations produce a list of things that still need to be worked out rather than conclusions. Capturing those explicitly, with owners and deadlines, is what turns a good discussion into progress.
For longer planning sessions, it helps to identify which decisions were made definitively, which are provisional pending further information, and which are still open. Conflating these three categories is a common source of confusion when people come back to the summary later.
Team syncs and internal meetings
For regular internal meetings, the summary does not need to be elaborate. A short list of what was discussed, what was decided, and what the actions are is enough. The purpose is mainly to give absent team members context and to create a record of action items that can be checked at the next meeting.
The most useful thing you can do for recurring internal meetings is to use the same template every time and keep a running archive. When you need to understand why a decision was made three months ago, or track how long a particular issue has been on the agenda, a consistent archive saves a significant amount of reconstructive effort.
Where to store and share your meeting summaries
Meeting summaries that sit in the note-taker's inbox are not doing their job. They need to reach everyone who needs them, promptly, and in a place they can be found later.
For internal meetings, the summary should go to all attendees plus anyone who was absent but needs to be kept informed. A short message in your team's shared channel, with the full summary linked or pasted, works well. If you are working in a project management tool, attaching the summary to the relevant project or ticket keeps it where the work lives.
For client meetings, email is usually more appropriate than a shared channel. Send the summary as a follow-up email within 24 hours, ideally the same day. Waiting longer reduces its usefulness and can give the impression that the meeting was not taken seriously.
Wherever you store summaries, naming conventions matter. "Meeting notes" is not a useful file name when you have 40 of them. "2026-03-26 Quarterly planning: decisions and actions" is. Consistent naming makes retrieval fast and makes the archive useful rather than just a storage problem.
If the follow-up email itself is adding to your post-meeting workload, Fyxer's AI email assistant can draft it for you, using context from the meeting and your inbox, so the summary gets distributed without eating into the rest of your day.
Why meeting summaries affect outcomes beyond the meeting itself
A 2023 evidence review by the Chartered Institute of Personnel and Development synthesized the research on what makes meetings effective. Clarity on what was decided and who does what next is among the factors tied to whether a meeting translates into action. Meetings that end with clear, shared written records of decisions and responsibilities are more likely to produce the outcomes they were called to achieve.
This matters beyond individual meetings. Teams that document meetings consistently make faster decisions over time, because they are not relitigating things that were already resolved. They also onboard new members more easily, because the decision history exists somewhere accessible rather than in the memory of whoever has been around longest.
For a broader view of how meeting and communication overhead affects day-to-day productivity, our piece on how hidden admin affects business growth covers it in more depth.
Using AI to produce meeting summaries
AI meeting tools have made the note-taking step much faster for a lot of teams. An AI notetaker can join a call, produce a transcript, and generate a structured summary in the time it would take a person to open a blank document. Fyxer's AI meeting notetaker does this, separating decisions, action items, and next steps into the structure the template above lays out.
There are a few practical considerations before you rely on one fully. AI-generated summaries are good at capturing what was said, but less reliable at distinguishing what was important. A summary that logs everything equally is not much more useful than a transcript. The template above gives you a structure to edit AI output against, so the final summary reflects judgment rather than coverage alone.
Practitioners who manage this work make the same point. Gemma Osula, managing director of executive support agency Pickle, sees AI as a way to take the first pass, turning "rough notes into a clear follow-up," while cautioning that people can "mistake a first pass for a finished output, and that is where things become risky." The judgment stays human.
Action items are the most important thing to verify in any AI-generated summary. AI tools can misattribute ownership, miss implicit commitments, or capture the discussion of an action without recording that it was agreed. A quick review of the action items section before distributing a summary is non-negotiable regardless of how the summary was produced.
For guidance on capturing in-person meetings specifically, where AI tools have their own practical constraints, see our post on using an AI notetaker in in-person meetings.
