How to write a meeting summary with templates and examples

A meeting summary answers three questions for whoever opens it: what you discussed, what you decided, and who does what next. Anything past those three answers costs your reader time, and it doesn't buy them a thing.

This guide covers the seven steps, a template you can paste into a doc or an email, three worked examples, four email formats, the line between a summary and minutes, and where AI takes over. If you'd rather grab the template first and read the method after, the picker above hands it to you.

How to write a meeting summary?

Seven steps, ten to fifteen minutes of work. Most of that time goes on deciding what to leave out, because you're recording an outcome rather than replaying a conversation. Senior executives already sit through close to 23 hours of meetings a week, up from under 10 hours in the 1960s, Harvard Business Review reports. Fifteen minutes of writing protects the hour everyone's already spent.

Step 1: Start with the meeting objective

Open with one sentence on why the meeting happened. It gives every line under it a reason to exist, and it lets anyone who skipped the call decide in two seconds whether they need the rest. Write the objective the meeting turned out to have, not the one that sat on the invite. Half the time they aren't the same thing, and the second one matters more.

Step 2: Capture the key discussion points

Write down what changes what happens next, and leave the rest in the room. A transcript holds every sentence, and nobody opens a transcript twice. Three to five lines carry a one-hour meeting. If you're writing more than that, you're transcribing rather than choosing.

WeakThe team discussed the launch date.

StrongMarketing pushed for July 1. Engineering flagged two weeks of QA on checkout. The room landed on July 15, with QA intact.

Step 3: Write down the decisions

Give decisions their own block and their own lines. A decision buried in a paragraph reads like an opinion, and somebody reopens it three weeks later. Name the decision, name the person who made it, then move on. If the room didn't decide, say so on its own line, because "we didn't settle this" is worth as much to your reader as a decision.

WeakWe talked about the budget and everyone seemed comfortable with the numbers.

StrongDecision. Ana locked the Q3 budget at $35,000, and she signs the purchase order on Friday.

Step 4: Turn commitments into action items

Somebody says "we should probably ping legal". That sentence hides a real task behind a hedge. Rewrite it with a verb at the front and the object right after, so whoever reads it knows what to do without asking you first. If you can't put a verb at the front, you haven't got an action item yet.

WeakSomeone should check with legal about the contract wording.

StrongSend the indemnity clause to legal, for review, before Thursday.

Step 5: Assign an owner and a deadline

Every meaningful action gets a name, and it gets a date whenever a date exists. A task with two owners has no owner, so pick one person and let the second one help. When the room ducks the question, put your own name down, and let somebody correct you. That's quicker than a second meeting about who owns what.

Step 6: Cut everything the reader does not need

Read your draft once with the delete key ready. Small talk goes, the tangent about the office move goes, and the slide nobody discussed goes with them. Ask one thing of every line: does this change what a colleague knows, or what a colleague does? If the answer's no, the line goes too.

Step 7: Send it quickly

Send it the same day, inside the hour when you can. Memory fades fast, and so does the sense of obligation people carry about what they said out loud. A rough summary at 3pm beats a polished one on Thursday, because by Thursday half the room has moved on and the other half doesn't trust its own memory.

What should a meeting summary include?

Eleven parts, in the order a reader wants them.

• 📝Meeting title. Something searchable, because a colleague will hunt for it six months from now.
• 📅Date and time. Both, because "the Tuesday call" ages badly.
• 👥Attendees. Who came, and who the team expected and did without.
• 🎯Objective. Why the meeting happened, in one sentence.
• 💬Key discussion points. Three to five lines, chosen for what they change.
• 🔖Decisions made. One line each, with the name of whoever made the call.
• 📌Action items. A verb at the front, every single time.
• 🤝Owners. One name per task, and no shared credit.
• 🔔Deadlines. A real date, because "end of week" means nothing by Wednesday.
• 🔎Open questions. What the room parked, and who chases the answer.
• 🚀Next steps. The next meeting or the next deliverable, with its date.

Not every meeting earns all eleven. A fifteen-minute standup needs the decisions and the action items, and nothing more. A quarterly client review takes the full set. The test holds everywhere, and it's a blunt one: drop any line that leaves your reader no better informed and no better equipped.

Meeting summary vs meeting notes vs meeting minutes

Notes serve the person who took them. Minutes serve the record, and in a board or a works council setting they follow a format somebody else fixed years ago. A summary serves the people who act next, which is why it's happy to drop so much of what the other two keep.

People also say meeting recap, and the two words do the same job. "Recap" carries a lighter register, so it fits the Slack message you fire off after a standup, while "summary" fits the document you send a client. Same content, different clothes. Pick the word your team already uses, stay with it, and don't let both float around, because two names for one artifact means people hunt in two places.

How long should a meeting summary be?

Short enough to read in two minutes. No word count survives contact with a real calendar, so let the meeting set the length. You'll land on a line for each decision, a line for each action item, and one sentence of context above them.

Four things stretch it. More decisions, more action items, more technical detail your reader can't rebuild alone, and a wider audience each add lines. Microsoft found that only about one person in three believes the room would miss them in most of their meetings, according to its Work Trend Index. Write for the two who showed up and skimmed, and the length takes care of itself.

How to make your meeting summary get read

• 🧭Put decisions near the top. That's the question people opened the message for, so answer it early.
• 📤Put action items where the eye lands. Top third of the message, above any background.
• 🧩Use bullets rather than blocks. A wall of prose reads like homework, and people treat it like homework.
• 💡Bold the owners and the deadlines. Those two words, in bold, carry the whole email.
• 🧵Keep one idea per bullet. Two ideas in one line, and the second one disappears.
• 🔁Cut repetition. Say it twice, and you halve the weight of both mentions.
• 📈Lead with what changed. The parts that stayed the same, your reader already knows.
• 🔧Drop the background nobody asked for. Context belongs at the bottom, or nowhere at all.
• 📨Send it quickly. Two days late, and it competes with everything else in the inbox.

Atlassian put a number on the cost of getting this wrong: inside organizations with poor meeting habits, people spend 50% more time in unnecessary meetings than on their highest-priority work, its State of Teams research found. A summary people read is the cheapest way to cancel the meeting that would've followed.

How AI can write a meeting summary

The chain runs in six moves. You hold the meeting, a tool captures the audio or your notes, the model drafts a summary, you lift the decisions and the action items to the top, you check the draft, and you send it. AI saves you real time on the first draft, and none at all on the last read. That last step isn't optional.

Check six things every single time: the decisions, the names, the owners, the deadlines, the numbers, and anything a lawyer would care about. A model invents a plausible deadline the same way it invents a plausible citation, and from the outside your reader can't tell the two apart.

• 🎧Zoom AI Companion. Strong when your meetings already live in Zoom, thin outside it.
• 📚Otter. Good transcripts, plus search across a back catalog of calls.
• 🔬Fathom. Fast recaps and clip sharing, built around sales calls.
• 🌍Fireflies. Wide integration coverage, and a searchable archive of past meetings.

All four stop at the document. They tell you what happened in a meeting you already had, and they do it well enough that drafting the first version by hand now looks like a choice you're making on purpose.

Gojiberry works on the other side of the calendar. It tracks more than 30 buying signals across the socials and the web, surfaces the accounts moving right now, and runs personalized outreach across several channels. Note-takers handle the summary. A different kind of tool decides who you meet in the first place. A rep who runs sales calls needs both, and neither one covers for the other.

How to summarize a meeting quickly

Five minutes, six moves, in this order.

• 🔍Write the objective. One sentence, from memory, before you open your notes.
• 🔒Pull out the decisions. Scan for the moments the room stopped arguing, and stop there.
• 🧰List the action items. Verb first, every time.
• 📁Add owners and deadlines. One name, one date, one line.
• 🧮Delete everything else. The tangents, the repetition, the slide nobody used.
• 📬Send it. Same thread, same day.

The order does more work than the speed. Writing the objective first tells you which discussion points survive, and deleting last means you'll never spend a minute polishing a sentence you were about to cut.

Meeting takeaways vs meeting summary

A takeaway captures one insight worth carrying out of the room. "Enterprise buyers ask about SSO before they ask about reporting" is a takeaway. A summary gives that insight its surroundings: who said it, what the room decided because of it, and who acts on it by when. You can't run a project off takeaways alone. Takeaways travel well in a Slack message. Summaries do the work that stops the next meeting from happening.

FAQ