Meeting Recap Template: How to Write One People Actually Read
A meeting recap is only useful if people act on it. Here's a simple, reusable template and the four things every recap must include — written in under five minutes.
A meeting recap is not a summary of what was said. It is a record of what was decided and what happens next. The distinction matters because the second type drives action and the first type gets archived.
This guide gives you a template you can use immediately, explains the principles behind it, and covers the common mistakes that turn useful recaps into documents nobody opens.
What a meeting recap is for
The purpose of a meeting recap is to close three loops:
-
Ensure everyone agrees on what was decided. Decisions made verbally in a room are fuzzy. Written decisions are precise. The act of writing "we decided to proceed with vendor A" gives everyone a chance to say "actually, I thought we were still evaluating."
-
Assign accountability. A commitment made in conversation has no owner until someone writes down a name. "Someone will follow up with legal" produces no follow-up. "Priya to follow up with legal by Friday" produces a result.
-
Create a retrievable record. When the same topic comes back in three weeks, the recap is what lets you say "we covered this on the 9th, here's what we decided" rather than starting the conversation over.
The template
Here is a template that works for most meetings. Copy it, adapt it, use it as-is.
MEETING RECAP [Meeting name] Date: [Date] Attendees: [Names or roles]
DECISIONS
- [Decision 1 — stated as a fact, not as discussion]
- [Decision 2]
- [Decision 3]
ACTION ITEMS
| What | Who | By when |
|---|---|---|
| [Task] | [Name] | [Date] |
| [Task] | [Name] | [Date] |
NEXT MEETING Date: [Date and time] Purpose: [One sentence on what this meeting needs to resolve]
OPEN ITEMS / PARKED TOPICS
- [Topic that came up but wasn't resolved — add to next agenda]
That's the whole template. You don't need more sections than this for most professional meetings. Adding fields for "discussion notes," "background," or "context" tends to bury the decisions and actions under prose that no one reads.
How to fill it in without writing an essay
Decisions: Write each one as a single sentence in the past tense. "Agreed to move the deadline to the 20th." "Decided not to proceed with the API integration until Q1." Each decision should be understandable to someone who wasn't in the meeting. If a decision requires two sentences of context to make sense, add one sentence of context — but no more.
Action items: Three columns, one row per task. If a task doesn't have a name in the "who" column, it won't happen. If it doesn't have a date in the "by when" column, it will happen after the next meeting asks about it. Both fields are mandatory. If you don't know the deadline, put a question mark and send a follow-up message to agree on one.
Next meeting: One line on date and time, and one sentence on the one thing that must be resolved before that meeting makes sense. "What to do about the pricing strategy" is a topic. "Decide whether to reduce the enterprise tier price before the October proposal" is a purpose.
Open items: Anything that came up but wasn't resolved. Write it down here rather than leaving it in someone's head. These automatically become agenda items for the next meeting.
The four things every recap must have
You can cut the template down further if the meeting was short. But these four things survive any simplification:
1. A decision or outcome. If the meeting produced no decisions and no actions, the recap should say that. "This meeting was exploratory — no decisions made. Next session will focus on X" is a valid recap. It prevents people from wondering what they missed.
2. A name next to every task. Not "the team," not "we." A single person's name. Groups do not own tasks. People do.
3. A date next to every task. Open-ended commitments expire in people's minds the moment the meeting ends.
4. Where to find the recap. Email, shared doc, or a meeting tool like Meetings Brief that creates a shareable link. The recap is useless if no one can find it.
When to send it
Within an hour of the meeting ending, if possible. Same day is the hard floor. A recap sent the next morning is still useful. A recap sent three days later is mostly archaeology.
The reason speed matters: the conversation is still live in people's heads for a few hours after a meeting. A recap sent quickly confirms the shared understanding while it can still be corrected. A recap sent days later asks people to reconstruct a context they've half-forgotten.
If you use AI to generate a summary from a transcript or voice note, review it against the source before sending. Check decisions, task owners and stated dates; mark missing details as unconfirmed and ask the participants. Review time depends on the length and quality of the source, and AI can omit or misattribute commitments.
Common mistakes
Writing it as narrative prose. "The team came together to discuss the roadmap and after some back and forth agreed that the timeline needed revisiting" is three times longer than "agreed to revisit the timeline." Bullet points and tables are your friend.
Including everything that was said. The purpose of a recap is not to recreate the meeting for people who weren't there. It's to capture what changes as a result of the meeting. Discussion context that didn't produce a decision or action doesn't belong in the recap.
Sending it to everyone when only some people need it. A recap to twenty people for a meeting that involved four of them creates noise. Send it to attendees and anyone directly affected by the action items. Let them forward it if others need to know.
Using it as a way to reopen decisions. The recap captures what was decided, not what you wish had been decided. If you disagree with an outcome, address that separately — not by writing a recap that softens the decision.
Adapting the template for different meeting types
Weekly team standup: Cut to actions only. No decisions section. No table — just a bulleted list of "[Name]: [what they'll do before next week]."
Client call: Add a "key information shared" section above decisions. Clients sometimes need to know what information was exchanged, not just what was decided. Keep decisions and actions as the last two sections.
Board or governance meeting: Use the full template, add a "resolutions passed" section above decisions, and treat the minutes format requirements of your organization as overriding this guide.
Sales discovery call: Rename "decisions" to "next steps agreed" and "action items" to "commitments." The template structure is identical; the vocabulary fits the context.
Using AI to generate the recap
AI meeting tools — including Meetings Brief's free meeting summary generator — can generate a draft recap automatically from a transcript or a set of notes. Treat the output as a draft to check against the source, not a finished document ready to send.
What AI can help with: drafting sections for explicit decisions, stated action items and open questions. Check that each extracted item is supported by the source.
What still needs a human: checking that implicit agreements were captured ("everyone nodded at that" is invisible to a transcript), confirming that task owners are correct, and making sure the tone fits the relationship (a recap to a client reads differently to a recap to your team).
The practical workflow: generate the AI draft, verify decisions and actions, ask participants to confirm missing deadlines, then send. The time needed depends on the meeting and the corrections required.
FAQ
How long should a meeting recap be? For most meetings, one page or less. A two-hour strategic planning session might produce a longer recap, but the decisions and action items section should still fit on one page. If the recap is longer than that, you're probably including discussion that doesn't belong there.
Who should write the recap? Usually the meeting organizer or the designated note-taker. For recurring meetings, rotating the responsibility keeps one person from burning out on it.
Do I need a specific tool to send meeting recaps? No. Email works fine. A shared doc with a comment thread works. A dedicated meeting tool like Meetings Brief creates a shareable link with the summary formatted and ready to send. The tool matters less than the habit of sending quickly and consistently.
What if attendees disagree with the recap? That's exactly what it's for. A written recap surfaces disagreements that would otherwise sit in people's heads for weeks. Treat a correction as a success — it means the recap did its job of making the shared understanding explicit.
Should I include who said what? Usually not. The recap is about what was decided and who owns what — not who made which argument. Attribution in the decisions section ("Priya suggested option B and the team agreed") is occasionally useful in a contentious context, but as a default, keep the decisions section factual and attribution-free.
Meetings Brief's meeting summary generator turns notes or a transcript, long ones included, into one of four kinds of summary. Free, no account required.