Short answer: To write a meeting summary, open with one or two sentences on the meeting's purpose and outcome, then list the decisions, the action items (each with an owner and due date), and any open questions — in that order. Keep it under a page, lead with what changed, and send it within the hour while the meeting is fresh. A good summary is not a transcript; it is the five things a busy person needs to know without having been there.
This guide shows you exactly what to include, gives you two full examples you can copy, and covers the mistakes that make most summaries go unread — plus how to generate one automatically from a recording.
What is a meeting summary?
A meeting summary is a short written recap of what happened in a meeting: the purpose, the key points, the decisions made, and the next steps. It's the document you send afterward so people who attended remember what they agreed, and people who missed it can catch up in a minute.
It is deliberately not the same as meeting notes taken live, and it is definitely not a transcript. Notes are your raw capture during the meeting; a transcript is the full word-for-word record; the summary is the distilled version you actually share. If you send people the raw notes or the transcript and call it a summary, you've handed them your work instead of doing it.
What to include in a meeting summary
A summary that gets read has a predictable shape. Use the same sections every time so readers know exactly where to look.
1. Meeting basics
One line of context: the meeting name, date, and who was there. Add a single sentence on why the meeting existed. This orients anyone reading it later.
2. A one- or two-sentence overview
Lead with the outcome, not the agenda. "We agreed to ship two pricing tiers and pushed the enterprise plan to Q4" tells the reader more than "We discussed pricing." This is the part most people will actually read, so put the real news first.
3. Key decisions
List what was decided, one bullet each. Where the reason matters, add it in a few words. Decisions are the highest-value thing a meeting produces — never bury them inside a paragraph.
4. Action items with owners and due dates
Every next step gets a single owner and a real date. "Someone will follow up" is how action items get lost. Name the person and the deadline, no exceptions.
5. Open questions
Anything raised but not resolved, plus who will chase it. This stops the same unanswered question from reappearing three meetings in a row.
6. Next steps or next meeting
If there's a follow-up meeting or a clear "what happens now," state it in one line so nobody has to ask.
How to write a meeting summary, step by step
You can write a solid summary in five to ten minutes if you work in order.
- Start from your notes or the transcript. Don't summarize from memory — you'll drop details. Work from what was actually captured.
- Write the outcome first. Before anything else, answer: what changed because this meeting happened? That sentence becomes your overview.
- Pull out the decisions. Scan for every point where the group agreed on something and list it plainly.
- Extract the action items. For each one, confirm the owner and the due date. If either is missing, that's your cue to go back and pin it down.
- Note the open questions. Anything left hanging goes here, with a name attached.
- Cut everything else. The discussion, the tangents, the play-by-play — leave it out. If a line isn't a decision, an action, or a question, ask whether the reader needs it.
- Send it fast. A good-enough summary in an hour beats a perfect one in three days. Speed is what gets it read.
Meeting summary example 1: a project kickoff
Here's what the finished product looks like for a short internal meeting.
Project Atlas — Kickoff
Date: Jul 3 · Attendees: Priya, Marco, Dana, You
Purpose: Align on scope and timeline for the Atlas launch.
Overview: We locked the launch scope to the mobile flow only and set
a target date of Sep 15. The web version moves to a fast-follow.
Decisions
- Launch mobile-first; web ships as a fast-follow after Sep 15.
- Drop the in-app tutorial from v1 to protect the date.
Action items
- [ ] Priya — finalize the mobile spec — due Jul 10
- [ ] Marco — set up the staging environment — due Jul 12
- [ ] Dana — draft the launch comms plan — due Jul 18
Open questions
- Do we need legal review for the new data screen? (Dana to check)
Next: Review progress at next Thursday's standup.
Notice how someone who missed the meeting understands it from the overview and decisions alone. The detail is there for anyone who needs it, but it never gets in the way.
Meeting summary example 2: a client call
The same structure works for external meetings — it just gets a touch more formal.
Acme Corp — Discovery Call
Date: Jul 3 · Attendees: J. Rivera (Acme), You
Overview: Acme wants to consolidate three note-taking tools into one
by end of quarter. Budget is approved; the decision-maker is their
COO, who wasn't on this call.
Decisions
- Acme will pilot with the Operations team (12 users) first.
Action items
- [ ] You — send pricing for the 12-user pilot — due Jul 5
- [ ] You — share the security overview PDF — due Jul 5
- [ ] J. Rivera — introduce us to the COO — due Jul 11
Open questions
- Does Acme's security team require SOC 2 before a pilot? (Rivera to confirm)
Next: Follow-up call once the COO intro is made.
For client-facing summaries, being explicit about owners and dates does double duty: it keeps the deal moving and creates a shared record of what each side committed to.
A copy-paste meeting summary template
Strip the examples down and you get a reusable template. Copy it, fill it in, delete what doesn't apply.
[Meeting name] — [Date]
Attendees: [names]
Purpose: [one sentence]
Overview
[1–2 sentences: what happened and what changed.]
Decisions
- [Decision] — [reason, if it matters]
Action items
- [ ] [Task] — @owner — due [date]
Open questions
- [Question] — [who will chase it]
Next: [next step or next meeting]
Common mistakes that make summaries useless
Avoid these and you're ahead of most people writing summaries.
- Summarizing the discussion instead of the outcome. Nobody needs a play-by-play. They need what was decided.
- Action items with no owner or date. This is the number-one reason follow-ups die. One name, one date, every time.
- Sending it days later. By then everyone's moved on and the summary is archaeology, not action.
- Making it too long. If it's more than a page, it's notes, not a summary. Cut harder.
- Burying the important part. Lead with the overview and decisions. Don't make people scroll to find the point.
How to generate a meeting summary automatically
Writing summaries is a skill, but it's also a chore — and the chore is what most people skip when they're busy, which is exactly when a summary matters most. This is where recording plus AI changes the equation.
meaty is built for this, especially for in-person meetings where nobody is going to type up notes afterward. You record the meeting from your phone, and meaty transcribes it with speaker labels, then produces a title, a summary, and action items with owners automatically — the same structure as the examples above, drawn straight from what was actually said.
You still review it, fix an owner, and send it around. But you start from a complete, structured draft instead of a blank page and a fading memory. The honest pitch isn't "never write a summary again" — it's that the boring first draft is done the moment you stop recording, so you can be present in the room instead of transcribing it.
Frequently asked questions
How long should a meeting summary be?
As short as it can be while still covering the decisions, action items, and open questions — usually well under a page. If it runs longer, you're probably summarizing the discussion instead of the outcome. Cut anything that isn't a decision, an action, or an unresolved question.
What's the difference between meeting minutes and a meeting summary?
Minutes are a more formal, often complete record of a meeting — attendance, motions, votes — common in boards and formal governance. A summary is the lighter, action-focused recap most teams actually need day to day. If you need the formal version, see our guide to meeting minutes templates.
When should I send a meeting summary?
Within the hour, while the meeting is fresh. Speed beats polish: a good-enough summary sent immediately gets read and acted on; a perfect one sent three days later gets ignored.
Should the summary include the full transcript?
No. Keep the transcript as a reference you can link to, but the summary itself should be the distilled version. Put the summary and action items in the message body; link the transcript for anyone who wants the exact wording.
The bottom line
A meeting summary is not a transcript and not your raw notes — it's the short, structured recap that tells a busy person what was decided and what happens next. Lead with the outcome, list decisions and action items with owners and dates, keep it under a page, and send it fast.
Do that consistently and your summaries stop being a formality nobody reads and start being the thing that actually moves work forward.
Try meaty free — record your next meeting from your phone and get a structured summary and action items back the moment you stop.