Meeting recap format: the structure that gets read and acted on

A meeting recap is not meeting minutes, and treating it like minutes is why most recaps go unread. A recap exists to do exactly two jobs: remind people what was decided, and tell each person what they now owe and by when. Everything that does not serve those two jobs is noise, and noise is what gets your recap skimmed and closed.

So the format is short. The best meeting recap leads with decisions and action items, names one owner and one date per task, and lands in inboxes within 24 hours while the meeting is still warm. A recap that is comprehensive but arrives three days later has already failed. Speed and structure beat completeness every time.

This guide gives you the exact format, copy-paste templates for the meetings you actually run (client check-ins, internal standups, project syncs, sales calls), the pitfalls that quietly kill recaps, and a faster way to produce them.

What goes in a meeting recap (and what does not)

A recap has a fixed skeleton. Use these sections, in this order, every time:

1. One-line summary. What the meeting was for and the single biggest outcome. This is the only part some people will read, so make it count.
2. Decisions. What the group agreed to. State the decision, not the debate.
3. Action items. Each one owned by exactly one person, with a verb and a due date.
4. Next steps / next meeting. What happens next and when you reconvene.
5. Notes (optional). Context, open questions, or blockers worth keeping. Short.

That is it. Notice what is missing: a play-by-play transcript, a list of who said what, and a paragraph of throat-clearing before the substance. Those belong in a transcript or meeting summary, not a recap. A recap is the action layer that sits on top.

The single most common mistake is burying the action items. People write a faithful chronological summary, then tack a thin "next steps" line at the bottom. By then the reader is gone. Decisions and action items go near the top, where attention is.

The core meeting recap template

Here is the format you can paste into email, Slack, Notion, or a Google Doc and fill in right now. It works for most meetings.

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

Quick summary: We met to [purpose]. Headline: [the one 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 trigger or date]
- 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 rules make this template actually work. First, every action item starts with a verb (send, draft, confirm, schedule), names one person, and ends with a real calendar date, never "next week." Second, the recap goes out fast. If you want the deeper logic behind owned, dated tasks, see the action items template; for the language to use, the meeting action items template has phrasing examples.

Match the format to the meeting type

The skeleton stays the same. What you emphasize changes with the room. Here is how the same five sections flex across the meetings most teams run.

Client recap

The client recap is also a record. It manages expectations and protects you when scope gets fuzzy later, so it leans harder on decisions and confirmed scope. Keep the tone polished and skip internal grumbling.

Hi [Client name],

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

What we decided:
- [Scope / direction decision]
- [Budget or timeline decision]

What happens next:
- [Us]: [deliverable] (by [date])
- [You]: [what we need from the client] (by [date])

Open items:
- [Anything still pending a decision]

Next check-in: [date]. Let me know if I have any of this wrong.

Best, [Name]

Note the "what we need from you" line. Client recaps fail when they only list your team's tasks and leave the client's dependencies implicit. Spell out the client's homework. For the broader playbook on this, see client meeting notes template and how to manage client expectations. If your follow-up needs to be more of a polished email than a bare recap, the after-meeting email guide covers tone.

Internal sync, standup, or project recap

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

Sync recap, [date]

Decided: [the one or two real decisions, if any]

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

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

Next sync: Mon, same time.

For recurring project meetings, your recap doubles as a status pulse. A project status report example shows how to roll several of these into a weekly view.

Sales call recap

A sales recap confirms what the prospect agreed to and sets the next concrete step. The next step is the most important line in the whole email; a recap with no clear next step is how deals stall.

Hi [Name],

Great talking today. To recap what we covered:

- Your main goal: [the problem they want solved]
- What I shared: [the relevant capability or proof point]
- We agreed: [next step, e.g. a trial / a proposal / a follow-up demo]

Next step: I will [send the proposal / set up the trial] by [date]. Could you [their action, e.g. loop in your VP] before then?

Talk soon, [Name]

For more on this, the sales follow-up email templates cover the full sequence after the call.

Client / sales

• Lead with: decisions and confirmed scope
• Always include: what you need from them, by when
• Tone: polished, record-keeping
• Critical line: the next concrete step and date

Internal / project

• Lead with: action items and blockers
• Always include: owners with @-handles, hard dates
• Tone: blunt, fast to skim
• Critical line: the loudest current blocker

The format rule that matters most: speed

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

1. 1

   Capture during the meeting

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

2. 2

   Draft from the structure, not memory

   Fill the five sections: summary, decisions, action items, next steps, notes. Pull owners and dates straight from what was said.

3. 3

   Tighten and verify owners

   Every action item: one name, one verb, one date. Cut anything that is not a decision or a task.

4. 4

   Send within hours

   Email or Slack the same day. Ask people to reply if you missed or misstated anything; that reply becomes the correction record.

The biggest reason recaps go out late is that writing them from scratch is tedious, especially if you were also running the meeting. That is the real bottleneck, and it is the one worth fixing.

Produce the recap automatically

If you are typing recaps from memory after every call, you are paying a tax twice: once in attention during the meeting, and again in the 30 minutes after. An AI meeting notetaker removes both costs. It records and transcribes the call, then drafts a summary with decisions and action items already pulled out, so your job shrinks to editing and sending.

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 format above, then copy into email or Slack. For teams that also meet on Zoom or Microsoft Teams, Scribbl for teams extends the same workflow across platforms.

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

Pitfalls that quietly kill recaps

• No owner, or two owners. Covered above, and it is the number one failure. One named person per task.
• 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.
• 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. Use the five headings every time so the reader can find their own action item in two seconds.

Frequently asked questions

What is the difference between a meeting recap and meeting minutes?

Minutes are a formal, often near-complete record of a meeting: attendance, motions, discussion, and decisions, kept for the record (think board meetings and governance). A recap is shorter and action-oriented; it captures decisions and who-owns-what so people can move, and it skips the detailed narrative. If you need the formal version, see meeting minutes format with action items. For most working meetings, a recap is what you actually want.

How long should a meeting recap be?

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

When should I send the 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 compete for attention they have already spent.

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 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. Think of it as starting from a filled draft instead of a blank page, not as hands-off automation.

The short version

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. Use the meeting type to decide what to emphasize, not to change the skeleton. And 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.