# How to write and send a meeting recap email (with templates)

> Source: <https://www.granola.ai/blog/how-to-write-and-send-a-meeting-recap-email-with-templates>
> Published: 2026-06-05 00:00:00+00:00

# How to write and send a meeting recap email (with templates)

June 5

TL;DR:A meeting recap email documents decisions, assigns owners to action items, and sets deadlines. Without one, action items and commitments get lost before anyone acts on them. Send the recap within 24 hours while details are still fresh and participants share the same understanding of what was discussed. Structure beats volume: clear decisions, named owners, and firm deadlines are easier to act on than a long transcript. Granola's AI notepad enhances your rough notes into a structured recap the moment the meeting ends: You jot what matters and Granola fills in the context.

Most professionals focus on their performance inside the meeting and underinvest in the follow-up that actually turns discussions into decisions. A meeting without a documented recap is just a conversation, and this guide gives you the exact 6-step workflow and three copy-paste templates to send a polished recap email in minutes, plus a look at how an AI notepad like [Granola](https://granola.ai/) enhances your rough notes into a structured recap the moment your meeting ends.

## Why meeting recap emails matter

Professionals often use "meeting recap email" and "meeting follow-up email" interchangeably, but a functional distinction matters. A follow-up email is a broad category that includes thank-you notes, feedback requests, and "great to connect" messages. A meeting recap documents what was decided, names owners, and sets deadlines. Think of it as the formal minutes for modern work.

Done well, recap emails do three things that no amount of good intentions inside the meeting room can replicate.

### Alignment across teams and stakeholders

The moment a meeting ends, interpretations start to drift. One person leaves thinking the launch date is Q3, another is certain you agreed on Q4. A recap sent the same day gives everyone a single, searchable source of truth. This matters especially when you share meeting notes across distributed teams where people in different time zones missed the session entirely. When everyone reads the same documented version of what was decided, you close that gap before it becomes a conflict.

### Accountability for action items

Without written owners and deadlines, tasks evaporate. "Follow up on the proposal" is not an action item. "Sarah: Send revised proposal to legal by Friday, June 1" is. The recap forces that specificity, and once someone's name is attached to a deadline in writing, the social contract around delivery becomes real.

### Paper trail for decisions

Teams revisit strategic decisions constantly. Six months after committing to a pricing model or a go-to-market motion, someone will ask why. The recap is your answer. It preserves the rationale, the alternatives considered, and the people in the room when the decision was made. For teams building institutional memory as they grow, this context survives employee departures rather than walking out the door with whoever held it.

## The 6-step workflow for writing recap emails

Most of the hard work happens before you open your email client. Capture the right structure during the meeting and the email practically writes itself. Use this checklist as a reference before you hit send:

- Clear, specific subject line (includes meeting name and date)
- One-sentence purpose summary
- Decisions made (stated as complete outcomes, not topics)
- Action items with named owner and deadline for each
- Open questions or blockers still outstanding
- Next meeting date, time, and platform

### 1. Capture key points during the meeting

You do not need to transcribe every word. Jot the things only you would know to flag: The number the CFO confirmed, the objection the prospect raised, the decision that surprised everyone. Keep your in-meeting notes to decisions, numbers, names, and commitments. Stay present in the conversation rather than producing a word-for-word record. Your notes guide the recap rather than drafting it. That is the same philosophy behind Granola's [AI-enhanced notes workflow](https://docs.granola.ai/help-center/taking-notes/ai-enhanced-notes): You write what matters, and the AI fills in context from the transcript afterward.

### 2. Structure your notes after

Group your bullet points into logical categories (decisions, actions, open questions) before you draft a single sentence of the email. Avoid sending a raw, unedited brain dump straight from your notebook to the recipient's inbox. If your recap runs several hundred words, you have already lost the room. This transition from rough notes to organized categories is where clarity gets created or destroyed.

### 3. Draft the recap email

Keep it short and use bullet points. The three templates in the next sections give you the exact format for internal, sales, and client contexts. List each decision as a complete statement rather than a topic. "Approved Q3 budget for content campaign" is a decision. "Budget discussion" is a topic. One can be acted on without a follow-up question. The other cannot.

### 4. Review for accuracy and clarity

Run through the checklist above before sending. Confirm every action item has a named owner and a specific date. Check that the tone matches your audience and that no sensitive internal details appear in an external recap. One quick read-through prevents the errors that require a follow-up to the follow-up.

### 5. Personalize for your audience

A project status update reads differently from other decision memos. People who were in the room need the short version. People who were not need just enough background to act on their piece. The [automated meeting summaries guide](https://granola.ai/blog/automated-meeting-summaries) covers how audience-specific output can be built directly from your notes with a single prompt.

### 6. Send within 24 hours

Memories fade quickly after a meeting ends, and waiting longer than 24 hours means you are no longer reinforcing shared understanding. You are trying to reconstruct it. For high-stakes calls (investor pitches, client kick-offs), same-day sends are the standard and the clearest signal that you treat follow-through seriously.

## Template 1: Internal team recap

Use this for standups, roadmap sessions, all-hands check-ins, and any meeting where the primary audience is your own team. The goal is speed and clarity. Frame it as the group equivalent of one-on-one meeting notes and keep it scannable.

**Subject:** Recap: [Meeting Name] ([Date]): decisions + next steps

Hi team,

Here is a quick recap from today's [Meeting Name].**Decisions made:**

- [Decision 1: state as a complete outcome, not a topic]
- [Decision 2

**Action items:**

- [Owner first name]: [Specific action] by [Due Date]
- [Owner first name]: [Specific action] by [Due Date]

**Open questions:**

- [Any unresolved item that needs follow-up]

**Next meeting:** [Date] at [Time] on [Platform/Location]

Please reply by [Date] if anything above is inaccurate or missing.

[Your name]

Bold the owner's name and due date inside each action item bullet. When a recipient scans the email and sees their name in bold next to a deadline, they know exactly what they owe. For next meeting details, one line covering date, time, and platform is enough. If you are sharing notes alongside the invite, the [how to share meeting notes guide](https://granola.ai/blog/how-to-share-meeting-notes) covers the cleanest way to do this without cluttering the calendar event.

## Template 2: Sales follow-up recap

Use this after discovery calls, demos, and check-ins with active prospects. The priority is momentum and clear next steps. The sales call summary and CRM guide covers structuring the underlying notes before the email end-to-end, and Granola's [sales manager coaching playbook](https://granola.ai/blog/sales-manager-coaching-playbook-ai-meeting-notes) shows how teams use AI-enhanced notes to drive pipeline accuracy.

**Subject:** Next steps: [Your Company] + [Prospect Company], [Date]

Hi [First Name],

Great speaking today. Here is a quick summary of what we covered and where we go from here.**Objective:** [One sentence on the meeting purpose]**Pain points confirmed:**

- [Challenge 1 they raised, in their language]
- [Challenge 2 they raised, in their language]

**What we are exploring together:**

- [Relevant capability 1]
- [Relevant capability 2]

**Next steps:**

- You: [Specific action] by [Date]
- Me: [Specific action] by [Date]

**Attachments:**

- [Link or file name]

Looking forward to [next milestone].

[Your name]

Keep the objective concise. Use the prospect's exact language in the pain points section rather than your interpretation of what they meant. It shows you were listening and builds trust before the next call. Ensure every next step is assigned to a named person with a specific date, and link directly to any case studies, pricing decks, or product one-pagers. Do not make them hunt for materials.

## Template 3: Client and external recap

Use this after project kick-offs, quarterly business reviews, or any external meeting where both sides need a shared record of what was agreed and who owns what next. For participant privacy considerations when capturing these meetings, Granola's [AI notetaker participant privacy guide](https://granola.ai/blog/ai-notetaker-participant-privacy-consent) is worth reading before your next external call.

**Subject:** [Project Name] meeting recap, [Date]

Hi [Client Name],

Thank you for the time today. Here is a summary of what we covered and what happens next.**Meeting overview:** [Date] | Attendees: [Names] | Project: [Name]**Key decisions made:**

- [Decision 1]
- [Decision 2]

**Deliverables agreed:**

- [Deliverable]: Owner: [Your Company] | Due: [Date]
- [Deliverable]: Owner: [Client Company] | Due: [Date]

**Dependencies and blockers:**

- [Open item or blocker requiring resolution]

**Next session:** [Date/Time], [Calendar link]

Please let me know if anything above needs correcting.

Best, [Your name]

External recaps carry a different register than internal ones: more precise in how deliverables and ownership are attributed, and more careful about which internal context reaches the client. When working with external stakeholders, document decisions in terms both sides can act on, with clear attribution of who committed to what. Assign deliverables clearly and identify any blockers that may affect timelines. Include a direct booking link for the next session to reduce scheduling friction.

## Subject line patterns that get opened

The subject line determines whether the recap gets opened immediately or buried. It also determines whether the recipient can find it three months later when they need it. Both matter.

| What works | What gets ignored |
|---|---|
| Recap: Q3 roadmap sync, June 1 | Following up |
| Next steps: [Client] kick-off, May 25 | Meeting notes |
| Action items: hiring loop sync, May 24 | Quick question |
| Recap + decisions: meeting prep May 20 | Checking in |

### What works: Specific and actionable

The strongest subject lines share three qualities: they name the meeting, include the date, and signal whether action is required. A consistent format such as "Recap: [Meeting Name], [Date]" is searchable, scannable, and immediately tells the recipient why this email deserves their attention. "Next Steps: [Topic]" performs well in sales contexts because it signals progress rather than administration. Keeping the subject line under 50 characters improves mobile readability, where most recipients triage email first.

### What gets ignored: Vague and generic

"Following up" is the most common subject line and the least effective. It tells the recipient nothing about the content, the urgency, or whether they need to act. "Meeting notes" is slightly better but still generic. Any subject line that could apply to any meeting from any sender is a subject line that gets skipped during inbox triage.

## The AI shortcut: Enhance rough notes into a recap with Granola

The 6-step workflow above is sound practice regardless of what tools you use. But steps 2 through 4 (structuring, drafting, and reviewing) take meaningful time when done manually after every meeting.

### How Granola captures meeting content

We built Granola to capture audio directly from your device, transcribe in real time, and delete the audio. No bot joins your video call, no "recording started" announcement appears, and the call looks exactly as it did before. This matters most for the meetings where documentation is most critical: executive recruiting, investor pitches, and client kick-offs where a visible participant would change the dynamic entirely. Granola works across any platform (Zoom, Meet, Teams, Slack huddles) because it captures system audio rather than integrating with the call platform itself.

"It listens directly from my device audio no bots joining calls and produces clean, structured summaries with decisions, action items, and key points." -[Brahmatheja Reddy M. on G2]

### From notes to structured recap

When the meeting ends, click "Enhance notes." Granola analyzes the full transcript using your rough notes as a guide. Write "pricing objections" during the call and Granola finds every pricing discussion in the transcript and adds the relevant context. Leave the notepad blank and it still produces a structured summary. Granola keeps your notes in black text and shows AI additions in gray, so you always control what stays and what gets deleted. We built this human-in-the-loop approach specifically to prevent the generic summaries that make professionals nervous about sending AI output directly to clients.

Granola also includes [customizable templates](https://docs.granola.ai/help-center/taking-notes/customise-notes-with-templates) for specific meeting types (sales calls, 1-on-1s, discovery sessions, hiring loops) so the structure of the recap is already set before the meeting starts. Recipes give you reusable prompts for recurring workflows, like turning raw notes into a follow-up email draft. You can also [chat with your meetings](https://docs.granola.ai/help-center/getting-more-from-your-notes/chatting-with-your-meetings) to ask "What were the three commitments the prospect made?" and get source-linked answers to paste directly.

"Granola nails exactly what I need: clean, reliable meeting transcripts and smart follow-up summaries without any fluff. I use it for nearly every call to stay focused on the conversation instead of scribbling notes. Huge time saver." -[Verified user on G2]

### Copy, paste, edit, and send

Once Granola enhances your notes, the recap is ready to use. Copy the structured output, paste it into your email client, adjust the opening line for the recipient's context, and send. The Granola [Zapier integration](https://docs.granola.ai/help-center/sharing/integrations/zapier) pushes the structured recap directly to Slack, Notion, HubSpot, or any of 8,000+ connected tools without leaving the app, so the follow-up reaches the right people through the channel they already monitor.

"I love that you can blend shorthand with AI notes. It's also super intuitive and super easy to use. The interface is clean and simple. I use this nearly every day for work." -[Mason K. on G2]

Try Granola for free. [Download](https://www.granola.ai/) the Mac, Windows, or iPhone app, connect your calendar, and use it to capture and generate the recap for your next meeting.

## FAQs

**What is the difference between a meeting recap email and a meeting follow-up email?**

A follow-up email is a broad category that includes thank-you notes, feedback requests, and interest in reconnecting. A meeting recap email is a specific type of follow-up that documents what was decided, who owns each action item, and what the deadlines are.

**How soon after a meeting should you send the recap?**

Send it within 24 hours, with same-day being the standard for high-stakes meetings. Interpretation drift starts the moment a meeting ends, so the sooner the recap lands, the less work it has to do.

**What should always be included in a meeting recap email?**

A strong recap typically includes decisions stated as complete outcomes, action items with a named owner and specific deadline for each, open questions still outstanding, and next meeting details including date, time, and platform.

**Does Granola join my Zoom call as a visible participant?**

No. Granola captures audio directly from your device and transcribes in real time, then deletes the audio. Granola shows no participant in your call's participant list and makes no recording announcement.

**Can I use Granola to generate recap emails automatically?**

Yes. After a meeting, clicking "Enhance notes" generates a structured summary using your rough notes as a guide. Recipes let you convert that summary into a formatted follow-up email in one step, which you can copy, edit lightly, and send.

**Is Granola secure enough for confidential meetings?**

Granola is SOC 2 Type 2 compliant and GDPR compliant. Audio is deleted after transcription, and third-party AI providers are contractually prohibited from training on your data. Enterprise plans include a model training opt-out by default for the entire organization.

## Key terms glossary

**Meeting recap email:** A structured post-meeting communication documenting decisions made, action items with owners and deadlines, and next steps. Distinct from a general follow-up email in its specificity and accountability function.

**Action item:** A specific, assigned task with a named owner and a deadline. "Review the proposal" is not an action item. "Marcus: review the revised proposal and send feedback by June 3" is.

**Human-in-the-loop AI enhancement:** A workflow where the user's rough notes guide AI output, producing focused summaries rather than generic transcripts. Granola's core approach to note enhancement.

**Device audio capture:** Granola's method of transcribing meetings by capturing audio directly from your computer's system output, without joining the call as a visible participant.

**Institutional memory:** The accumulated knowledge of decisions, rationale, and context that an organization holds. Meeting recap emails and AI-searchable note archives are the primary tools for building it.
