A meeting recap is a short written summary of what happened in a meeting: the decisions made, the action items assigned, and the points that still need an answer. You send it to attendees so everyone leaves with the same version of events, and to people who missed the meeting so nobody has to repeat it for them.
The short version: a good recap has five parts, takes ten minutes to write by hand, and should go out the same day. Below you will find the steps, three copy-paste templates, and a filled-in example. At the end, a faster option: sharing the recap as a link instead of writing an email at all.
Why meeting recaps matter
Most meetings produce decisions that live in one person’s head. Two weeks later, three people remember three different outcomes. A recap fixes that for the price of a few paragraphs.
Recaps also cut down on repeat meetings. When someone misses a call, the usual fix is a second call to catch them up. A recap they can read in two minutes replaces that meeting entirely.
How to write a meeting recap in 5 steps
-
Start with the outcome, not the agenda. Open with the one or two decisions that matter. Nobody reads a recap to relive the meeting in order.
-
List decisions as statements, not discussion. Write “We are moving the launch to March 4” rather than “We discussed the launch date.” If something was debated but not decided, put it in a separate open questions section.
-
Assign every action item to a name and a date. An action item without an owner is a suggestion. Use a simple format: task, owner, due date.
-
Note open questions. Anything unresolved goes in its own short list. This is what the next meeting’s agenda comes from.
-
Send it the same day. A recap sent three days later gets skimmed. A recap sent within the hour gets read, because the meeting is still fresh and people want to confirm their action items.
Keep the whole thing under 200 words if you can. If your recap needs scrolling, it is a document, not a recap.
Meeting recap templates
Three templates you can copy and fill in. Swap the sections you do not need.
Template 1: general meeting recap email
Subject: Recap: [meeting name], [date]
Hi all,
Quick recap of today's meeting.
Decisions:
- [Decision 1]
- [Decision 2]
Action items:
- [Task] - [Owner] - [Due date]
- [Task] - [Owner] - [Due date]
Open questions:
- [Question, and who is finding the answer]
Next meeting: [date and purpose, if any]
Reply if I got anything wrong.
[Your name]Template 2: quick Slack-style recap
Recap from [meeting name]:
Decided: [one line]
Doing: [name] handles [task] by [date], [name] handles [task] by [date]
Still open: [question]
Full notes here: [link]Template 3: client call recap
Subject: Notes from our call, [date]
Hi [name],
Thanks for the time today. Here is what I took away.
What you need:
- [Requirement or goal in the client's words]
What we agreed:
- [Commitment 1, with date]
- [Commitment 2, with date]
Next steps on our side:
- [Task and date]
Next steps on your side:
- [Task and date]
If I misread anything, tell me and I will correct it.
[Your name]Meeting recap example
Here is Template 1 filled in, from a product planning meeting:
Subject: Recap: Q2 planning, April 3
Hi all,
Quick recap of today's meeting.
Decisions:
- Onboarding redesign ships in Q2. The referral program moves to Q3.
- We are hiring one more mobile engineer instead of two backend engineers.
Action items:
- Draft the onboarding spec - Maya - April 10
- Post the mobile role - Tom - April 5
- Update the Q2 roadmap doc - Priya - April 4
Open questions:
- Do we keep the old onboarding flow as a fallback? Maya checks the numbers.
Next meeting: April 17, spec review.
Reply if I got anything wrong.
SamNotice what is missing: no attendance list, no minute-by-minute account, no “we then discussed.” Decisions, owners, dates, questions. That is the whole job.
How to write a meeting summary vs a recap
The terms overlap, but a summary usually means a fuller account: the main points of discussion, the reasoning behind decisions, sometimes close to minutes. A recap is the compressed version built for action.
If you need both, write the summary first and pull the recap out of it. The recap goes in the email body. The summary gets linked underneath for anyone who wants the detail.
How to send a meeting recap
Email works, and the templates above are built for it. But email has two problems. Writing the recap takes time you rarely have between meetings, and once sent, it is frozen. If you correct a date or add an action item, you are sending a follow-up email to fix the first one.
The alternative is sending a link instead of a document. This is how we built it at Fieldy. Fieldy is a wearable that records your conversations, including the in-person ones that Zoom and Teams tools never see, and writes the summary for you. When the meeting ends, the recap already exists.
To share it, you tap Share on the conversation and send the link. The person on the other end sees the summary, can switch to the full transcript if they want the detail, and can copy either. If they have a question the summary does not answer, they ask it in chat on the page and get an answer drawn from that conversation. No second meeting, no “quick question about Tuesday’s call” thread.
Every conversation has one stable link. You can make it private at any time, and if you share it again later, the same link works. So the recap you send is never frozen: it is a live page you control.
Meeting recap FAQ
What should a meeting recap include? Decisions made, action items with owners and due dates, open questions, and the date of the next meeting if one is planned. Keep it under 200 words.
How soon after a meeting should you send a recap? The same day, ideally within an hour. The longer you wait, the less it gets read and the more the details drift.
What is the difference between a meeting recap and meeting minutes? Minutes are a formal, chronological record of everything discussed, often required for board or legal contexts. A recap is a short, action-focused summary written for speed of reading.
How do you recap a meeting you did not attend? Ask for the recording or transcript rather than a verbal retelling. With a shared Fieldy link you can read the summary, check the transcript, and ask questions about what was said without booking time with anyone.
Should you send a recap for every meeting? Send one for any meeting that produced a decision or an action item. Skip it for standing check-ins where nothing changed.
Your next recap can write itself. Fieldy records the meeting, summarizes it, and gives you one link to share. See how it works at fieldy.ai. Comparing recorders first? Start with the Plaud alternatives guide.
