Meeting Summary Template and Generator

How to write a meeting summary

A good summary covers five things, in this order: context, decisions, action items with owners, open questions and next steps. Each step says how to write the part and where the generator above helps.

• Open with contextIn a sentence or two, say why the meeting happened and who was there. In the generator, that is the Purpose field: the line that lets someone who was not in the room decide whether the rest is relevant to them.
• List the decisionsState each decision so that someone scanning only this part understands what was agreed. Add the two or three key points that led to it, and skip the play-by-play of who said what. The Key Points and Decisions fields keep the two apart.
• Add action items with ownersGive every task a name and, where you can, a due date, formatted the same way each time. Each action item in the generator has its own task, owner and due date, so none of them hides inside a paragraph.
• Note open questionsCall out anything that was raised but not resolved, so it does not quietly disappear. The generator has no separate field for this: write each open question as a line in Key Points, starting with "Open:".
• Close with next stepsSay when the group meets again and what has to happen before then. Fill in the Next Meeting field, then copy the summary or download it as Markdown.

Meeting summary example

A filled meeting summary for a pricing review — purpose first, discussion left out, outcomes reported.

Meeting summary templates by meeting type

Meetings serve different purposes and have different readers, so one template fits none of them well: a retro produces process fixes, a sales call produces intelligence about a prospect, a 1:1 produces commitments and feedback. For why generic formats go unread, see why nobody reads meeting notes .

Done since the last stand-up
- [Team member]: Completed [task]. Merged [feature or PR].
- [Team member]: Finished review of [item]. Started on [next task].

Planned for today
- [Team member]: Working on [task]. Expected completion: [date].
- [Team member]: Starting [new task]. Blocked until [dependency] is resolved.

Blockers and dependencies
- [Blocker] - Owner: [name], needs [what] from [whom]
- [Dependency] - Status: [waiting / in progress / resolved]

Check-in
- General sentiment, energy, any personal context shared

Discussion topics
- [Topic 1]: What was discussed, any decisions or change of direction
- [Topic 2]: Key points and context

Feedback exchanged
- From manager: [Specific feedback, positive and constructive]
- From report: [Concerns raised, requests made, feedback on team or process]

Action items
- [Name]: [Action] - by [date]
- [Name]: [Action] - by [date]

Career development and growth notes
- Goals discussed, progress on development areas, upcoming opportunities

Call overview
- Prospect: [Company / name], Stage: [Discovery / Demo / Negotiation]
- Attendees: [Names and roles]

Pain points identified
- [Pain point 1]: How it was described, severity, current workaround
- [Pain point 2]: Context and impact on their business

Product fit signals
- Features that resonated: [list]
- Features that did not land: [list]
- Competitor mentions: [Competitor - what was said]

Objections raised
- [Objection]: How it was addressed, whether it was resolved

Budget and timeline signals
- Budget: [What was mentioned or implied]
- Timeline: [Decision timeline, procurement process, key dates]
- Decision makers: [Who approves, who influences]

Next steps
- [Action]: Owner [name], by [date]
- Follow-up meeting: [date / topic]

Meeting overview
- Client: [Name], Project: [Name / phase]
- Attendees: [Client side and internal]

Decisions made
- [Decision 1]: What was agreed, any conditions
- [Decision 2]: Changes to scope, timeline or deliverables

Action items
- Client: [Action] - by [date]
- Internal: [Action] - owner [name], by [date]

Key discussion points
- [Topic]: What was discussed and any change of direction

Risks and concerns raised
- [Risk]: Who raised it, current status, mitigation plan

Next meeting
- Date: [date], agenda items: [list]

--- Internal only, do not share with the client ---

Relationship signals
- Client satisfaction: [Assessment]
- Escalation risks: [Any tension or concern]
- Expansion opportunities: [Signals observed]

What went well
- [Item 1]: Why it worked, how to preserve it
- [Item 2]: Specific examples and contributing factors

What did not go well
- [Item 1]: Root cause, impact on the sprint
- [Item 2]: What contributed, how it affected delivery

Improvement actions
- [Action]: Owner [name], implement by [sprint / date]
- [Action]: Owner [name], check the result by [date]

Patterns from previous retros
- Recurring themes: [Items that came up before]
- Progress on earlier actions: [What was addressed, what was not]

Team sentiment
- Overall energy: [High / Medium / Low]
- Biggest concern: [What the team worries about most]

Meeting summary vs meeting recap

These are the same document with two different names. Both describe a short write-up of purpose, key points, decisions, and action items for people who were not in the meeting. Some teams say "summary", others say "recap" — the structure on this page and in the generator above works for either word.

Once a summary is written, the decisions inside it are often worth tracking beyond this one meeting — see the decision log template for a running record of decisions with the alternatives that were rejected along the way.

Why a meeting summary leads with purpose, not discussion

A meeting summary is written for someone who was not in the room. That reader needs to know, in one sentence, why the meeting happened before deciding whether the rest is relevant to them. Reporting the back-and-forth of who said what belongs in meeting notes taken during the call, not in a summary written afterward — see the meeting notes template for that working record, or the meeting minutes template when the meeting needs a formal, approved record instead.

Common meeting summary mistakes

Even with a good structure, a few patterns undermine a summary.

• Writing too much. The goal is a page someone can scan in a couple of minutes, not a transcript. Cut discussion that did not change the outcome.
• Burying action items in paragraphs. Make them visually distinct, each with a name. Buried tasks get missed, and missed action items compound across a week of meetings.
• Vague language. "We discussed the budget" tells the reader nothing. "Approved the Q3 campaign budget, pending VP sign-off" is a summary. If you write "discussed" or "reviewed" with no outcome, you are writing notes.
• Writing it late. Memory fades fast. The sooner after the call you write it, the fewer owners and deadlines you have to reconstruct from fragments.
• Giving everything equal weight. A tangent does not belong next to the roadmap decision. Edit for the reader: what do they need to do their job?
• Implying closure. Open questions are the part that slips most often, and decisions that were never written down are among the first things lost after a meeting. Name what is still unresolved.

Writing a meeting summary for different audiences

One summary does not always serve everyone. Adjust the same facts to the reader.

• Your team. Keep it direct and specific: implementation decisions, blockers and dependencies. Skip context they already have.
• Leadership. Lead with outcomes and decisions, then timeline impact, budget and risk. Leave out implementation detail.
• Stakeholders who were not there. Add a little more context on what was discussed and why, so bare action items make sense to them.
• Clients. Use a professional tone focused on shared commitments and next steps, with clear ownership on both sides. Keep internal-only observations out of the shared document.

Why use this free meeting summary generator?

• Free meeting summary generator — no account, no login, no watermarks
• Built for readers who were not in the meeting — purpose first, discussion left out
• Action items with owner and due date keep follow-through visible at a glance
• Live preview updates as you type — see the formatted summary before exporting
• Copy to clipboard or download as Markdown in one click
• Entirely client-side — your meeting content never leaves your browser
• Also answers to "meeting recap template" — same document, different name

Frequently Asked Questions