Meeting summary template (email and Word, free)
Last updated
This meeting summary template is built to be sent, not filed. It opens with why the meeting happened, lists the decisions and action items first, and keeps the discussion to a handful of key points. Most people only read the first screen of a recap email, so the template puts what they must know there.
Download it as a Word file, paste the plain-text version into an email, or read the filled-in example of a product roadmap review to see the length to aim for.
Word file (.docx), free and without signing up. Opens in Google Docs and Pages too.
What’s in the template
The minutes open with these details:
- Meeting
- Date
- Time
- Location (or video platform)
- Organiser
- Summary written by
- Attendees
- Sent to (including people who were not there)
Then the body follows the meeting in this order:
- 1. Purpose — One sentence: what the meeting was called to decide or resolve.
- 2. Decisions — Each decision on its own line, stated as a fact. If something was explicitly not decided, say so here.Decision: · Decided by / agreed by:
- 3. Action items — Verb first, one owner, a real date. These also go in the table below so people can scan them.Action: · Owner: · Due:
- 4. Key points — Three to six bullets of what was discussed, in the order it matters, not the order it happened.
- 5. Open questions — What was raised and not answered, and who is finding out.
- 6. Risks or concerns raised — Only if someone flagged one. Name the risk, not the person.
- 7. Next steps — What happens before the next meeting and when that meeting is.
- 8. Attachments and links — Slides, documents, the recording if there is one.
At the end: action items and decisions, as tables you can keep across meetings.
The template
Download it as a Word file, or copy the text version into your own document.
Meeting Summary Meeting: Date: Time: Location (or video platform): Organiser: Summary written by: Attendees: Sent to (including people who were not there): 1. Purpose [One sentence: what the meeting was called to decide or resolve.] 2. Decisions [Each decision on its own line, stated as a fact. If something was explicitly not decided, say so here.] Decision: Decided by / agreed by: 3. Action items [Verb first, one owner, a real date. These also go in the table below so people can scan them.] Action: Owner: Due: 4. Key points [Three to six bullets of what was discussed, in the order it matters, not the order it happened.] 5. Open questions [What was raised and not answered, and who is finding out.] 6. Risks or concerns raised [Only if someone flagged one. Name the risk, not the person.] 7. Next steps [What happens before the next meeting and when that meeting is.] 8. Attachments and links [Slides, documents, the recording if there is one.] Action items No. | Action | Owner | Due | Status Decisions No. | Decision | Agreed by
What a meeting summary must record
A summary is for two readers: the people who were in the room and need to remember what they agreed, and the people who were not and need to know what changed. Both groups want the same three things first: what was decided, who is doing what by when, and what is still open. Everything else is context.
Write decisions as finished sentences. "Launch moves to 3 March" is a decision. "Discussed the launch date" is not, and a reader who was not there will have to ask.
- Purpose: why the meeting was held, so the decisions make sense on their own.
- Decisions: each one on its own line, including decisions not to do something.
- Action items: verb, owner, date. One owner per action, even if several people will help.
- Open questions: so they are not mistaken for decisions, and someone is named to resolve them.
Writing it as an email
Put the meeting name and date in the subject line, for example "Summary: Q1 roadmap review, 12 October". Start the body with decisions and actions; put key points below them. Keep the whole thing under a screen on a phone if you can, and link to slides or documents rather than attaching them. If you also keep a longer record, link to that too, but do not paste it into the email.
Address the people who have actions by name in the action list, and copy anyone who was invited but did not attend. They are the readers who gain most from a summary.
How long it should be
For an hour-long meeting, 150 to 300 words is usual. If the summary is longer than the meeting agenda, it is drifting towards minutes. The test is whether someone who skipped the meeting can act on the summary without asking a follow-up question, not whether every topic is represented.
Send it within 24 hours
A summary sent the same day gets read and corrected. One sent a week later gets ignored, and the actions in it start late. If you cannot write the full summary straight away, send the decisions and actions within the hour and follow up with key points later. Invite corrections with a deadline: "Reply by Thursday if anything here is wrong" and treat silence as agreement.
Common mistakes
- Summarising in meeting order. Readers want decisions first, not a replay.
- Actions without a date, or with "ASAP". Pick a date; it can be changed.
- Attributing opinions. "Sam thinks the design is wrong" belongs in nobody's inbox. Write the concern, not the person.
- Repeating the slides. Link to them and say what changed because of the discussion.
- Writing "no decisions were made" when in fact something was deferred. Say what was deferred, to when, and why.
Example: filled-in meeting summary
What the template looks like once it’s been used. The organisation and people are made up.
Summary: Q1 2027 product roadmap review, Harbourline Software
Date: Monday 12 October 2026
Time: 2:00 pm to 3:10 pm
Location: Video call
Organiser: Ines Castellanos, Product Manager
Summary written by: Ines Castellanos
Attendees: Ines Castellanos, Rafael Duarte (Engineering Lead), Mei-Ling Chau (Design Lead), Oscar Lindqvist (CEO), Tanya Brooks (Support Lead)
Sent to: Attendees, plus the product and engineering channels
1. Purpose
To agree which three items from the Q1 candidate list go into the Q1 2027 roadmap, and to settle the launch date for the shared workspaces feature.
2. Decisions
Shared workspaces launches on Tuesday 3 March 2027, two weeks later than planned, so the permissions model can be finished first. Agreed by Oscar Lindqvist and Rafael Duarte.
Q1 roadmap: shared workspaces, the new billing page, and export to PDF. The mobile redesign moves to Q2.
Not decided: whether PDF export ships with a watermark on the free plan. Ines Castellanos will bring usage data to the next review.
3. Action items
Rafael Duarte: publish the revised shared workspaces schedule with the permissions milestone by 16 October.
Mei-Ling Chau: share the billing page prototype with Tanya Brooks's team for review by 23 October.
Ines Castellanos: pull free-plan export usage for the last 90 days before 26 October.
4. Key points
Support has 41 open tickets that mention workspaces or sharing, the most of any theme this quarter; this is the main reason the feature keeps its place.
The billing page is mostly a design and copy problem; engineering estimates two weeks.
The mobile redesign is wanted but has no customer commitments tied to it, so it moves to Q2 without changing any sales promises.
5. Open questions
Whether the free plan gets watermarked PDF export (data from Ines Castellanos by 26 October).
Whether the 3 March date is announced to customers now or after the beta (Oscar Lindqvist to decide by 20 October).
6. Risks raised
If the permissions work takes longer than two weeks, shared workspaces and the billing page compete for the same two engineers in February.
7. Next steps
Next roadmap review: Monday 26 October 2026, 2:00 pm. Rafael Duarte's revised schedule is the first item.
8. Links
Q1 candidate list (shared document), roadmap review slides, meeting recording.
Decisions
| No. | Decision | Outcome |
|---|---|---|
| 1 | Shared workspaces launch moves to 3 March 2027 | Oscar Lindqvist, Rafael Duarte |
| 2 | Q1 roadmap: shared workspaces, billing page, PDF export; mobile redesign to Q2 | All attendees |
Action items
| No. | Action | Owner | Due |
|---|---|---|---|
| 1 | Publish revised shared workspaces schedule with permissions milestone | Rafael Duarte | 16 October 2026 |
| 2 | Share billing page prototype with the support team | Mei-Ling Chau | 23 October 2026 |
| 3 | Pull 90-day free-plan export usage | Ines Castellanos | 26 October 2026 |
| 4 | Decide whether to announce the 3 March date now | Oscar Lindqvist | 20 October 2026 |
Tips for meeting summary
- Write the decisions and actions during the meeting, in the last five minutes, and read them aloud. The summary is then half done before anyone leaves.
- Lead the subject line with the word "Summary" so it can be searched for later.
- If a decision reverses an earlier one, say which one. "Replaces the 14 February date agreed on 28 September" saves a confused reply.
- Keep key points to things that changed someone's understanding. If a point would not surprise anyone, cut it.
- Send the same summary to everyone. Separate versions for different audiences drift and create two records.
Related templates
- Meeting notes with action items template — Notes built around a running action register, for recurring meetings where last week's actions are this week's first agenda item.
- Team meeting minutes template — The weekly meeting of one team: last week's numbers, blockers, decisions and this week's priorities.
- Staff meeting minutes template — The regular all-staff meeting of an office, clinic or branch: updates, policy changes, schedules and recognition.
- Project meeting minutes template — The weekly status record: where each workstream stands, which milestones moved, what changed on the risk log and what was decided.
- All meeting minutes templates
Or let the notes write themselves
A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.
Questions
What should a meeting summary include?
The purpose of the meeting, the decisions made, the action items with an owner and a date each, the main points of discussion, and any open questions. Add the date, attendees and links to any documents. A summary does not need the order of discussion or who said what; that is what minutes are for.
How do you write a meeting summary email?
Put the meeting name and date in the subject line. Open with one line on the purpose, then list decisions, then action items with names and dates, then three to six key points. Finish with open questions and the next meeting. Keep it under a screen on a phone and link to slides rather than attaching them.
What is the difference between a meeting summary and meeting minutes?
Minutes are a formal record kept in meeting order, often approved at the next meeting and sometimes required by bylaws or law. A summary is informal, ordered by importance, sent soon after the meeting, and exists so people act on what was agreed. Many teams keep both: minutes for the file and a summary for the inbox.
How long should a meeting summary be?
Usually 150 to 300 words for a one-hour meeting. The length depends on how many decisions and actions there were, not how long the meeting was. If someone who missed the meeting could act on your summary without asking a question, it is long enough.
When should you send a meeting summary?
Within 24 hours, and ideally the same day. People correct a summary they receive while the meeting is fresh and ignore one that arrives a week later. If the full write-up will take time, send the decisions and actions first and the rest later.
Can an AI note taker write a meeting summary?
It can produce a first draft of the discussion points and a list of actions, which is a reasonable starting point. A person still needs to check that the decisions are worded as decided, that each action has the right owner and date, and that nothing confidential is being sent to the wrong list. Tell attendees if a meeting is being recorded.