Recap of a meeting: how to write one that gets acted on

A recap of a meeting is not a transcript and it is not minutes. It is the thin action layer that sits on top of both: a short message that tells everyone what was decided and what each person now owes, by when. If a line does not serve one of those two jobs, it does not belong in the recap.

That single idea is what separates a recap people act on from one they skim and close. The recaps that work are short, lead with decisions and owned action items, and land in inboxes within 24 hours while the meeting is still warm. A recap that is thorough but arrives three days late has already failed, because by then everyone has re-prioritized and your action items are competing for attention people have already spent.

This guide covers what a recap actually is, how it differs from a summary and from minutes, exactly how to write one (with copy-paste examples), the pitfalls that quietly kill recaps, and how to stop writing them from a blank page.

What a recap of a meeting actually is

A recap is a brief, action-oriented message sent after a meeting. Its only purpose is to convert a conversation into commitments people can act on. It answers two questions for every reader:

1. What did we decide?
2. What do I personally owe, and by when?

Everything else is optional context. A recap is not the place for a play-by-play of who said what, the full discussion, or three sentences of throat-clearing before the substance. That material lives in the transcript or the longer meeting summary. The recap pulls the commitments to the top and cuts the narrative away.

People confuse three things constantly, so it is worth pinning down the differences.

Recap

• Job: drive action this week
• Length: under a minute to read
• Leads with: decisions and owned tasks
• Sent: same day, by email or Slack

Summary / minutes

• Job: create a record
• Length: as long as needed for completeness
• Includes: discussion, context, attendance
• Sent / stored: in a doc, for reference later

A meeting summary captures what happened, including the reasoning and discussion. Meeting minutes are the formal record, often with attendance and motions, kept for governance. A recap is the most stripped-down of the three: just decisions and action items, sent fast. For most working meetings, a recap is the only one of the three you actually need to write.

The five sections every recap needs

A recap has a fixed skeleton. Use these sections, in this order, every time. The order matters as much as the content, because the reader's attention is highest at the top.

1. One-line summary. What the meeting was for and the single biggest outcome. Some people will read only this line, so make it carry weight.
2. Decisions. What the group agreed to. State the settled choice, not the debate that got you there.
3. Action items. Each one owned by exactly one person, with a verb and a real due date.
4. Next steps / next meeting. What happens next and when you reconvene.
5. Notes (optional). Open questions, blockers, or context worth keeping. Keep it short.

Notice what is deliberately missing: the chronological story, the list of who said what, and the throat-clearing. The single most common mistake is burying the action items under a faithful play-by-play and then tacking a thin "next steps" line at the bottom, by which point the reader is gone. Decisions and action items go near the top, where the attention is.

For a deeper breakdown of how each section flexes by meeting type, the meeting recap format guide is the companion to this one; this page is the why and the how, that one is the structural reference.

How to write the recap, step by step

The work splits into four steps. The whole thing should take ten to fifteen minutes if you captured anything at all during the meeting, and far less if a notetaker did the capturing for you.

1. 1

   Capture during the meeting

   Note decisions and action items as they land, or let a notetaker transcribe so you are not splitting attention between talking and typing.

2. 2

   Draft from the structure, not memory

   Fill the five sections in order. Pull owners and dates straight from what was said, not from what you assume people will do.

3. 3

   Tighten owners and dates

   Every action item gets one name, one verb, and one calendar date. Split any shared task into separate lines. Cut anything that is not a decision or a task.

4. 4

   Send within hours

   Email or Slack the same day. End with an invitation to correct you; that reply becomes your record that people saw and agreed.

The hardest of the four is step three, because it is where most recaps go soft. "The design team will update the mockups" is not an action item, it is a hope. Assign one named person. "Soon" and "ASAP" are not deadlines; use a date. The discipline here is what makes the difference between a recap that moves work and one that documents intentions nobody is on the hook for.

A copy-paste recap template

Here is the core format. Paste it into email, Slack, or a doc and fill in the brackets. It works for most meetings.

Subject: Recap: [Meeting name], [Date]

Quick summary: We met to [purpose]. Headline: [the single biggest outcome].

DECISIONS
- [Decision 1, stated as a settled choice]
- [Decision 2]

ACTION ITEMS
- [Owner]: [verb-led task] (due [specific date])
- [Owner]: [verb-led task] (due [specific date])

NEXT STEPS
- [What happens next, and the date or trigger]
- Next meeting: [date / time], or "none scheduled"

NOTES (optional)
- [Open question, blocker, or context worth keeping]

Reply if I missed or misstated anything. Thanks, [Your name].

Two worked examples

Templates are easier to trust when you see them filled in. Same skeleton, different rooms.

A client check-in. The client recap doubles as a record, so it leans on decisions and confirmed scope, and it always spells out what you need from the client. The biggest failure here is listing only your team's tasks and leaving the client's homework implicit.

Hi Dana,

Thanks for the time today. Quick recap so we are aligned.

What we decided:
- Launch the new landing page on the revised, not the original, layout
- Push the go-live date to Jun 30 to fit the extra design round

What happens next:
- Us (Priya): deliver the revised mockups (by Jun 18)
- You (Dana): confirm final copy for the hero section (by Jun 20)

Open items:
- Whether to keep the testimonial carousel; deciding next call

Next check-in: Jun 23, 10am. Let me know if I have any of this wrong.

Best, Priya

An internal sync. Internal recaps can be blunt. Drop the pleasantries, lead with action items, and surface blockers loudly so they get unstuck before the next meeting.

Sync recap, Jun 13

Decided: ship the API change behind a flag, not to all users at once.

Action items:
- @maria: finalize the Q3 forecast (due Thu Jun 19)
- @james: unblock the staging deploy (due Wed Jun 18)
- @priya: send the vendor the signed SOW (due Fri Jun 20)

Blockers:
- Staging deploy waiting on infra approval (owner: @james)

Next sync: Mon, same time.

For client work specifically, the client meeting notes template and the broader after-meeting email guide cover tone and the longer follow-up when a bare recap is not enough.

The format rule that matters most: speed

You can have a perfect template and still fail on timing. A recap's value decays by the hour. People forget the nuance of a decision within a day, and the action items they agreed to start to feel optional once a late recap finally arrives. Aim to send within a few hours, and treat 24 hours as the hard ceiling.

The reason recaps go out late is almost never that people do not know the format. It is that writing one from scratch is tedious, especially if you were also the one running the meeting. You spent the call splitting attention between facilitating and scribbling, and now you owe everyone a clean writeup. That tax, paid twice, is the real bottleneck. It is the part worth removing.

Stop writing recaps from a blank page

If you are typing recaps from memory after every call, an AI notetaker removes both costs at once: the attention you spend taking notes during the meeting, and the half hour you spend reconstructing them after. It records and transcribes the call, then drafts a summary with decisions and action items already pulled out, so your job shrinks from writing to editing.

Scribbl does this for Google Meet from the browser, with no bot joining the call. It is free for individuals, and Pro adds unlimited meetings. It produces the transcript and an AI summary you can shape into the recap format above, then copy into email or Slack. Teams that also meet on Zoom or Microsoft Teams can extend the same workflow with Scribbl for teams. For agencies running back-to-back client calls, where a slow or missing recap is a direct billing and trust risk, see AI tools for marketing agencies.

To be honest about the line: the AI gets you a strong first draft fast, but you still own the final recap. It will not know that a casual "yeah, we should probably do that" was a firm decision, or that an action item needs a tighter deadline than the one said out loud. Read it, fix the owners and dates, then send. The point is not to skip the judgment, it is to skip the transcription and the blank page.

A note on Google Meet's own built-in option, since it comes up. Google Meet has a "take notes for me" feature powered by Gemini, but it is gated to paid Workspace editions (Business Standard, Business Plus, Enterprise Standard, and Enterprise Plus as of early 2026), not free accounts or Business Starter, and access is set by the meeting organizer's plan, not yours. If you do not have an eligible Workspace edition, a browser-based notetaker is the simpler path. For more on the native feature, see the Google Meet AI note taker overview.

Pitfalls that quietly kill recaps

• No owner, or two owners. The number one failure. One named person per task, always.
• Vague dates. "Soon," "next week," and "ASAP" are not deadlines. Use a calendar date.
• Recap as transcript. If your recap reads like a chronological story, you wrote a summary, not a recap. Cut to decisions and actions and move the rest down.
• Sent too late. A recap that arrives after people have moved on is a filing exercise, not a tool. Same-day, or it loses most of its value.
• No correction path. Always end with "reply if I missed anything." It catches errors and creates a record that people saw the recap.
• One giant blob. No sections, no bolding, no line breaks means nobody can find their own action item. Use the headings every time.

Frequently asked questions

What is the difference between a recap and a summary of a meeting?

A summary captures what happened, including the discussion and reasoning, so a reader who missed the meeting can understand it. A recap is narrower: it captures only the decisions and the owned action items, so people who were there know exactly what to do next. A recap is, in effect, a summary with the narrative removed and the commitments pulled to the top. If you need the fuller version, the meeting summary template covers it.

How long should a recap of a meeting be?

Short enough to read in under a minute. For a typical 30 to 60 minute meeting, that is a one-line summary, two or three decisions, three to six action items, and a next step. If your recap runs past a single screen, you are almost certainly including narrative that belongs in the summary, not the recap.

When should I send a meeting recap?

The same day, ideally within a few hours while the discussion is fresh. Treat 24 hours as the hard limit. After that, people have re-prioritized and your action items have to fight for attention they have already committed elsewhere.

Should the recap go in the email body or as an attachment?

In the body, almost always. An attachment is one extra click that drops your open rate and hides the action items. Paste the recap directly into the email or Slack message so it is the first thing the reader sees. Attach the transcript or recording separately if anyone needs the full detail.

Can AI write the recap for me?

It can write a strong first draft. A notetaker transcribes the call and pulls out decisions and action items, which removes the slow part. You still verify the owners and dates and cut anything that is not a decision or a task before sending. Treat it as starting from a filled-in draft instead of a blank page, not as hands-off automation.

The short version

A recap of a meeting is the action layer, not the record. Lead with decisions and action items. Give every task one owner, one verb, and one real date. Keep it to a screen. Send it the same day, and end with "reply if I missed anything." If the writing is what makes you send recaps late, let a notetaker draft it for you so the only work left is the part that needs your judgment.