What should a meeting summary include?

The outcome, the decisions, the top actions with owners and dates, the open questions, and the next meeting or checkpoint, plus a link to the full notes. Leave out who said what.

How long should a meeting summary be?

Five lines, about 125 words at most, readable in 30 seconds. Extra detail belongs in the minutes or the action items list, linked from the summary.

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

Minutes are the formal record of a meeting, often approved at the next one. A meeting summary is an informal digest of the result for people who need to act on it today. Many teams send both.

How do you write a meeting summary email?

Use the meeting name and date as the subject. Put the five lines at the top, then a link to the full notes. Send it within an hour to everyone who attended and anyone affected who didn't.

Who should write the meeting summary?

Whoever runs the meeting, or a note-taker named at the start. The writer reads the summary back in the last minutes so the group can correct it.

Meeting Summary Template in Five Lines

"So what happened in there?"

Priya's director missed the Tuesday planning meeting. Priya had two pages of notes, so she sent them. The director replied an hour later: "Thanks. What did we decide?" (Priya is a composite, not a real person.)

The notes were complete. They weren't a summary. Two pages answer "what was said," and the reader wanted to know what changed.

It's a common struggle. In Microsoft's 2023 Work Trend Index survey of 31,000 workers, 56% said it's hard to summarize what happens in virtual meetings.

This guide gives you a meeting summary template with five lines: Outcome, Decided, Actions, Open, and Next. You'll get a worked example, three more examples, a cut test, and a five-minute routine.

Want a first draft without writing it from scratch? Try ParrotNotes free: record the meeting on your phone and turn the AI summary into your five lines.

What a meeting summary is (and what it isn't)

A meeting summary is a short digest of a meeting for people who need the result, not the conversation: the outcome, the decisions, the actions, what's still open, and what happens next. It fits in a chat message, and anyone can read it in 30 seconds.

Each document a meeting produces has a different job:

Document	What it records	Who reads it	Length
Meeting notes	What was said, while it was said	Mostly the note-taker	As long as the meeting
Meeting minutes	The formal record, approved later	The group, auditors, the board	One to several pages
Action items list	Every task with an owner and a due date	The people doing the work	One row per task
Decision log	Decisions across many meetings, with reasons	Anyone checking later	One row per decision
Meeting summary	The result of one meeting	People who weren't there, and busy people who were	Five lines

The summary points to the others. For the full record, our meeting minutes template covers formal minutes, and the meeting notes template covers capture during the meeting.

The five-line meeting summary template (copy this)

Put the meeting name and date in the subject line or the first line of the message. Then write these five lines:

[Meeting name], [date]

Outcome: [the one thing someone who missed it must know]
Decided: [each decision, as "We will..."]
Actions: [owner: task by date; top three only]
Open: [what's unresolved, and who is holding it]
Next: [next meeting or checkpoint, and what it needs]

Full notes / minutes: [link]

That's the whole meeting summary template. The skill is in what you leave out.

What goes on each line

Outcome. The bottom line, in one sentence: "Launch moves to November 12." If the reader stops here, they still know what matters. Write it last.

Decided. Every decision, each written as "We will..." If you can't write it that way, it wasn't a decision. Lasting decisions also go in a decision log with the reasons.

Actions. The top three as "Name: task by date," with a link to the full list. Our action items template has a seven-field format for that list.

Open. Questions the meeting didn't settle, each with the person holding it. It stops people assuming something was agreed.

Next. When the group meets again, or the next checkpoint, and what has to be ready by then.

Rules that keep it to five lines

Bottom line first. The US Army's writing rules, Army Regulation 25-50 (paragraph 1-38), list putting "the main point at the beginning of the correspondence (bottom line up front)" as one of two essential requirements. The Outcome line is your bottom line.
25 words per line, at most. If a line runs over, you're explaining, and that belongs in the minutes.
Never delete a line. If nothing was decided, write "Decided: None."
Names, not teams. "Marketing will look into it" has no owner. "Jo: draft the brief by Friday" does.

Meeting summary example: 40 minutes of notes into five lines

Dana runs facilities for a 120-person office (a composite, like the names below). Her Thursday meeting planned the third-floor team's move to the fifth floor. Her raw notes from 40 minutes:

Reviewed floor plan v3, Ken still unhappy with window seats
Movers quoted two weekends, Oct 24 or Nov 7
IT needs 10 working days for network drops on 5
Long debate about the kitchen, parked
Budget: furniture within the $18,000 already approved
Agreed: Nov 7 weekend
Ken to confirm final seating chart
Sam to book movers once date is final
IT (Rhea) to schedule drops
Who pays for new signage? Nobody knew
Fire warden list needs updating after the move
Next check-in Oct 16

Here's the meeting summary Dana sent:

Floor move planning, October 1

Outcome: The third-floor team moves to the fifth floor on the weekend of November 7, within the approved $18,000 furniture budget.

Decided: We will use the November 7 movers' slot. We will keep furniture spend inside the existing budget.

Actions: Ken: final seating chart by October 9. Sam: book movers by October 10. Rhea: schedule network drops by October 17.

Open: Who pays for new signage (Dana to ask Finance). Fire warden list update after the move.

Next: Check-in October 16; seating chart and mover booking confirmed by then.

That's under 100 words, down from a page of notes.

What was cut, and why

"Ken still unhappy with window seats." Discussion, not a result. His seating chart action covers it.
The kitchen debate. Nothing decided, nobody owns it. Dana judged it could wait; otherwise it would be an Open item with a name.
"Movers quoted two weekends." The decision replaces it.
"IT needs 10 working days." A reason, not a result. It stays in the full notes.

Dana's director answered with one word: "Great." Nobody asked her for the notes.

Three more meeting summary examples

The same five lines work for almost any meeting. These three are illustrations.

Weekly team meeting

Customer support team meeting, October 6

Outcome: Response times are back under four hours; the weekend schedule changes from October 17.

Decided: We will move to a two-person weekend schedule.

Actions: Lena: publish the new schedule by October 10. Marco: update the auto-reply by October 13.

Open: Whether holiday weekends need a third person (Lena to check volumes).

Next: Team meeting October 13.

Client meeting

Kickoff with Northgate Logistics, October 7

Outcome: The client approved phase one; work starts October 20.

Decided: We will deliver phase one in three weekly releases.

Actions: Ana: send the statement of work by October 9. Client (Raj): name a day-to-day contact by October 10.

Open: Whether training is in scope (Raj to confirm).

Next: Weekly status call every Tuesday at 10:00, starting October 27.

Send client summaries to the client too: it puts both sides' promises in writing.

Vendor review

Quarterly review with our cleaning contractor, October 8

Outcome: Service is on target except the weekend restroom checks, which the vendor will fix this month.

Decided: None.

Actions: Vendor (Luis): add a Saturday check by October 15. Tom: share the complaint log by October 10.

Open: Contract renewal terms (Tom to bring options to the December review).

Next: Quarterly review, January 14.

A review meeting often decides nothing. "Decided: None" says so.

How to summarize a meeting in five minutes

A meeting summary is easiest to write in the last five minutes, while everyone is still in the room:

Read back before you close (one minute). "Here's what I'm writing down. We decided X. Jo has Y by Friday. Z is still open. Did I miss anything?"
Fill in Decided, Actions, Open, and Next (two minutes) from the read-back.
Write the Outcome line last (one minute). If your director reads one sentence, what should it say?
Run the cut test (one minute). See below.
Send within the hour. Post it where the group already talks, and link the full minutes underneath. In a recap email, the five lines go at the top: most people read only that part.

The cut test

Before you send, check every line against these six questions:

Does it say what changed, or only what was discussed?
Could someone who wasn't there act on it?
Does every action have one name and one date?
Is any line over 25 words?
Is there an opinion, adjective, or "who said what" in it?
Would the reader need to open the full notes to understand it?

Any wrong answer means rewrite or cut. The detail isn't lost; it lives in the notes you link.

Let a recording fill in your meeting summary template

The hard part isn't the template. It's running the meeting and tracking what changed at the same time. ParrotNotes takes the second job.

Put your phone on the table, with everyone's agreement to record, and start recording. No meeting bot joins anything. Recording works offline; transcription and AI run once you're connected.

Afterwards you get a transcript, an AI summary, key points, and action items. For the five lines, open the chat for that recording and paste this prompt:

Summarize this meeting in five lines: Outcome, Decided, Actions, Open, Next.
Outcome is the one thing someone who missed the meeting must know.
Write decisions as "We will...". Write actions as "Name: task by date", top three only.
Keep each line under 25 words. If nothing was decided, write "Decided: None."

Check the draft against the transcript before you send it. You know the context; the AI knows what was said.

Tomás, an office manager in a law firm (a composite), used to write up the monthly partners' meeting the next morning. Now he records it, runs the prompt in the parking lot, and checks the Open line against the transcript. The summary goes out before he's back at his desk.

The free plan includes 100 minutes of recording a month, an AI summary on every recording, and 5 AI-powered recordings a month. Download ParrotNotes free and record your next meeting.

Pro (US$19.99 a month, or US$14.99 a month billed annually) adds 3,000 minutes a month, all AI features on every recording, and speaker identification. Have a short recording already? The free audio summarizer summarizes a file of up to 10 minutes.

Five lines after every meeting

A meeting summary template only works if the summary stays short:

Five lines: Outcome, Decided, Actions, Open, Next.
Bottom line first, under 25 words a line.
"None" instead of a deleted line.
Read it back before the meeting ends; send it within the hour.
Link the full notes instead of pasting them in.

Priya's next summary was five lines, and her director had no questions. Try it after your next meeting. Try ParrotNotes free.

Meeting Summary Template: How to Summarize a Meeting in Five Lines

Table of Contents