Meeting Summary Template
A meeting summary is a short write-up for people who weren’t there and need the outcome, not the details: what the meeting was about, what was decided and who does what next. This template keeps it to one page of 150–350 words, so it can be read in a minute.
Dalm builds this document from your meeting. Switch on the draft mark, and the document carries a watermark saying a model put it together and it does not replace the official record.
Free. No sign-up.
Rather not take notes by hand? Dalm is a Mac app that records the meeting — a call or a room — and drafts the notes from the transcript. Get early access
What to include in a meeting summary
The template has seven parts, in this order:
- Meeting, date, attendees — the header, so the summary still makes sense when it is forwarded.
- In short — two or three sentences: what the meeting was about and the main outcome.
- Key points — three to five, one line each.
- Decisions — what was agreed, as it was agreed.
- Action items — action, owner, due date.
- Open questions — what the meeting did not settle.
- Next meeting — when the group meets again, if it does.
Meeting summary example
Example (fictional). Names and events are invented.
| Meeting | Sprint review |
| Date | Thursday |
| Attendees | Ilya, Nastya, Dmitry (team); Marina, A. Romanov (stakeholders) |
In short. The team showed the full invitation flow and the stakeholders accepted it. The role-management screen was sent back for rework.
Key points
- Invitation flow shown end to end: email, acceptance, first sign-in, expired link screen.
- Role-management screen has too many options on one screen to show to users yet.
- Stakeholders asked about inviting people as a list — not planned so far.
Decisions
- Invitation flow accepted.
- Role-management screen goes back to design.
Action items
- Add bulk invitation to the backlog — Marina — not set
Next meeting. Next sprint review in two weeks.
The example has no open questions, so that section is dropped rather than left empty — the same rule the template gives below.
How to write a meeting summary
Write the summary for the person who missed the meeting and will read only the first lines. Start with the outcome, keep the rest to a short list, and stop: this template keeps it to 150–350 words, which is a rule of this template rather than an industry standard. Anything that needs a paragraph of explanation belongs in the full notes, and the summary can point to them. Six rules from the template:
- Lead with the outcome. “In short” must make sense on its own if nobody reads further.
- Three to five key points, one line each. If a point needs a paragraph, it belongs in full notes, not in a summary.
- No fact twice. An action item isn’t repeated as a key point.
- Owners and dates only if named. Otherwise write “not set”.
- Neutral tone. No opinions about people; describe what was agreed.
- Drop empty sections.
Meeting notes vs summary vs recap email
| You need | Use | What it is |
|---|---|---|
| A full record of the meeting | Meeting minutes and notes template | Everything discussed, decided and assigned, kept as the record |
| The outcome on one page | This meeting summary template | 150–350 words for people who need the result, not the details |
| A one-page brief for leadership | Executive meeting summary template | The bottom line, decisions, requests with a recommendation and key numbers |
| A message to a person after the meeting | Meeting recap email template | An email with what was agreed and the next steps for that reader |
If you would rather not take notes
Dalm is a Mac app that records the meeting, a call or a room, and writes a review of it with sections: decisions, action items with an owner and a due date, risks and next steps. Each line shows the minute it was said.
What each plan includes is on the pricing page. How meeting notes are written by software rather than by hand is covered on the AI note taker page.
Questions
- How long should a meeting summary be?
- This template keeps it to 150–350 words, so it can be read in about a minute. If a point needs a paragraph of its own, it belongs in the full notes or minutes, and the summary links to them instead.
- What should I leave out of a meeting summary?
- Leave out the discussion itself, who said what, and opinions about people. Keep the outcome, three to five key points, the decisions, the action items and the questions still open. Drop any section that would be empty.
- Who sends the meeting summary?
- Usually whoever ran the meeting or took the notes. What matters more than the role is that one named person sends it, so nobody assumes someone else already did. Agree who it is before the meeting ends, and say where the summary will go — the team chat, an email to the attendees and the people who missed it, or the project page — so everyone knows where to look for it next time.
- When should a meeting summary be sent?
- The same day, while people still remember the meeting and before the first deadline on the action list. A summary sent a week later mostly records what has already been forgotten, and any action item due in the meantime has no written owner. If something is still unclear, send the summary anyway and put the question under Open questions rather than waiting for an answer.
- Is the meeting summary template free?
- Yes. The meeting summary template is free to download in Word and PDF, with no sign-up and no e-mail address asked. The files are in English and carry no product name or branding, so you can add your own logo, rename the sections or delete the ones you never use. The filled-in example on this page is free to copy as well.