Summary of a meeting: what it is and what makes one good

A summary of a meeting is a short, structured record of what the meeting changed: the decisions that were made, the work people now own, and the questions left open. That is the whole job. It is not a transcript and it is not your live notes. A transcript captures every word; a summary captures the handful of things someone needs to know or do because the meeting happened.

The reason most meeting summaries get ignored is that they confuse those two documents. People write a play-by-play of who said what, the summary balloons to a page and a half, and by the following Tuesday nobody reopens it because reading it costs almost as much as having been in the room. A good summary inverts that. It is shorter than the conversation by design, and its value is precisely the stuff it leaves out. This guide covers what a summary is for, the anatomy of a strong one, a before-and-after example, and the three honest ways to produce one.

What a summary of a meeting actually is

A summary serves two readers, and they want the same thing. The first is the person who was not in the room (a stakeholder, your boss, a teammate on PTO) who needs the outcome without the forty-five minutes. The second is the future version of you who has forgotten everything by next week. Both want the result, fast, with no decoding required.

That goal rules out a lot. It rules out narration ("Sarah raised the budget, then Tom pushed back"). It rules out filler ("we had a good discussion about timelines"). It rules out anything that does not point to a decision, an action, an open question, or context someone will genuinely need later. If a line survives that test, keep it. If it does not, the transcript already has it.

It also helps to know where a summary sits relative to the documents people confuse it with.

Document	What it captures	When you reach for it
Transcript	Every word, verbatim	"What exactly did they say," legal, research
Summary of a meeting	Decisions, owners, key points, open questions	The default for almost every meeting
Recap	The same outcomes, written to be sent	The note you fire off in email or Slack after
Meeting minutes	A formal record with attendance, motions, votes	Boards, nonprofits, governance

A summary lives in your team's notes. A recap of a meeting is that summary packaged as a message you actually send to people. If you need the formal version with attendance and a quorum, that is meeting minutes, a different and more rigid document.

The anatomy of a good meeting summary

A strong summary has four working parts and one header. The header is plumbing: meeting name, date, attendees, and who took the notes, so a reader can file it and know whose call to make if something is unclear. The four parts below are the substance, and the order is deliberate. Lead with what people most need.

1. 1

   Decisions

   What got settled, in one line each. Add the reason in parentheses only when it will matter later. This is the section people open the doc to find.

2. 2

   Action items

   Owner, verb-led task, due date. One human owner per item, never a team. If there is no owner and no date, it is not an action item, it is a wish.

3. 3

   Key discussion points

   The takeaway from each topic, not the back-and-forth. Two or three bullets. If a point led to a decision, it belongs above, not here.

4. 4

   Open questions

   What is still unresolved and who needs to chase it. Naming these is what stops the same debate from reopening next week.

A few rules separate a summary that gets used from one that decays:

• Write decisions in the past tense, as settled facts. "Decided to ship the v2 onboarding behind a flag" reads as final. "We talked about whether to flag v2" reads as a topic, and topics invite relitigation.
• Every action item gets one owner and a date. "The team will follow up" is the single most common reason action items die. Assign a person. If nobody owns it in the room, that is itself an open question, so write it as one.
• Cut quotes unless the exact wording is load-bearing. A client's precise phrasing on scope can matter; almost nothing else does.
• Keep it scannable. Bullets, not paragraphs. A reader should get the decisions in five seconds and the actions in ten.

For the full copy-paste version of this structure with fill-in fields for syncs, client calls, and one-on-ones, use the meeting summary template. For the underlying skill of writing notes that only state what was actually said and decided, see how to take better meeting notes.

Before and after: the same meeting, summarized two ways

Here is a thirty-minute project sync written the wrong way, then the right way. The content is identical. The difference is what each version asks of the reader.

The narration version, which is what most people produce:

PROJECT SYNC - notes

We started by going over the launch timeline. Priya said
engineering was behind on the API work and there was a long
discussion about whether to cut the reporting feature. Devon
felt strongly we should keep it. We went back and forth and
eventually agreed to push the launch. Then we talked about
the client demo and whether it should happen before or after
launch. Marketing had some concerns about the messaging. We
also touched on the budget but ran out of time.

You cannot act on that. There is no clear decision, no owner, no date, and "we also touched on the budget" leaves a live thread dangling with no marker. Now the same meeting as a summary:

PROJECT SYNC SUMMARY
Date:      2026-06-13
Attendees: Priya, Devon, Marketing (Lena), you
Note-taker: you

DECISIONS
- Launch moved to July 14 (API work is two weeks behind).
- Reporting feature stays in scope for v1 (Devon: it is the
  client's top-asked feature).

ACTION ITEMS
- Priya: send revised eng timeline to the channel (due Mon 6/16).
- Lena: rewrite launch messaging for the new date (due 6/18).
- You: book the client demo for the week of 7/7, pre-launch.

KEY DISCUSSION POINTS
- Demo lands before launch so the client sees it live, not in a deck.

OPEN QUESTIONS
- Does the new date affect the Q3 budget? Owner: you to confirm
  with finance by Friday.

The second version is shorter, and it does more. The decisions are settled facts. Every action has a name and a date. The budget thread that got dropped in the meeting is now a tracked open question instead of a forgotten one. That is the entire point: the summary does not record the meeting, it records what to do next because of it.

Three ways to produce a summary, and when to use each

You have three real options for getting from a meeting to a summary. None is best in every case. Pick by the meeting.

1. Write it yourself

The default for short, low-stakes, internal meetings. You stay present, you make judgment calls about what mattered, and the summary reflects your understanding rather than a machine's guess. The cost is attention: you are documenting instead of fully participating, and you will miss exact figures or wording. For a fifteen-minute standup, that trade is fine. For a client call where the details bind you, it is risky.

2. Google Meet's built-in "Take notes for me"

If your organization is on an eligible Google Workspace plan, Gemini can generate a summary for you. You turn it on from the meeting controls and Gemini produces a Google Doc with a summary, decisions, and suggested next steps shortly after the call. The doc lands in the meeting organizer's Drive folder and attaches to the calendar event (as of June 2026, per Google's support documentation).

It is genuinely useful inside the Google ecosystem, with two honest caveats. It requires a paid Workspace edition with Gemini; it is not available on free Google accounts. And it currently handles one language per meeting (English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish, as of June 2026), so mixed-language calls are out. For a deeper walkthrough, see our Google Meet AI note taker guide.

3. A dedicated AI notetaker

A purpose-built tool records, transcribes, and summarizes every meeting automatically, and keeps the transcript searchable so you can verify any line of the summary against what was actually said. This is the right call when you have meetings constantly, when you need the summary in seconds rather than after manual cleanup, or when "what exactly did they commit to" has to be answerable later.

Here is where I will name Scribbl, because it solves the two things the native option does not. It works on a free individual Google account, no paid Workspace edition required, and it runs as a browser extension with no bot joining the call. That second point matters more than it sounds: a notetaker that does not appear as a participant means no awkward "who is the notetaker?" moment and no recording-bot icon on a client call. Scribbl records, transcribes, and generates the structured summary (decisions, action items, key points) the moment the meeting ends. Pro removes meeting limits, and the Team plan extends the same workflow to Zoom and Microsoft Teams. See pricing for what each tier includes.

Gemini in Google Meet

• Best for: teams already on paid Google Workspace with Gemini
• Requires an eligible paid Workspace edition
• Summary saved to the organizer's Drive and the calendar event
• One language per meeting

Dedicated AI notetaker (Scribbl)

• Best for: anyone, including free Google accounts
• No paid Workspace plan needed; free for individuals
• No bot joins the meeting; runs in the browser
• Searchable transcript so you can verify every summary line

How to send the summary so it gets read

Writing a good summary is half the job. The other half is delivery, because a summary nobody opens is a summary that does not exist.

• Send it within the hour. The value decays fast. A perfect summary two days later loses to a rough one sent before people leave their desks.
• Put the action items in the body of the message, not behind a link. If you are emailing it, the owners and due dates go in the email itself. A link is a second click, and a second click is where follow-through dies. For the wording, how to write a follow-up email covers the templates.
• Tag owners directly. In Slack or your project tool, @mention each person next to their item. A summary addressed to everyone is owned by no one.
• Keep one home for all of them. A summary in a thread is gone in a week. Drop them in a shared, searchable place so anyone can find "the call where we decided X" three months from now.

Frequently asked questions

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

A summary is the practical default: decisions, action items, key points, and open questions, written to be useful, with flexible structure. Minutes are a formal record with a fixed format, including attendance, motions, seconds, and votes, used for boards and governance where the document is a legal artifact. Most meetings need a summary. Reach for minutes only when a body requires the formal record. See meeting minutes example.

How long should a summary of a meeting be?

As short as it can be while still carrying every decision, owner, and open question. For most meetings that is well under a page: a few bullets of decisions, a short action list, two or three takeaways, and any open threads. If your summary approaches the length of the transcript, you are narrating, not summarizing.

Can Google Meet summarize a meeting automatically?

Yes, if you are on an eligible paid Google Workspace plan with Gemini. The "Take notes for me" feature generates a summary in a Google Doc and saves it to the organizer's Drive and the calendar event (as of June 2026). It is not available on free Google accounts and handles one language per meeting. A dedicated tool like Scribbl works on free accounts and adds a searchable transcript you can check the summary against.

Should I write the summary or let AI do it?

Write it yourself for short, internal, low-stakes meetings where staying present matters more than the record. Use AI for meetings you have constantly, calls where exact details bind you, or any time you need the summary in seconds. Either way, the human reviews the action items and owners before sending. The AI drafts; you sign off.

Where should I store meeting summaries so people can find them?

In one shared, searchable place: a team wiki, a Notion or Drive folder, or your meeting tool's library. The failure mode is leaving them scattered across email threads and DMs. The test is whether a teammate can find "the call where we decided X" in under a minute, three months later, without asking you.