How to Write a Meeting Recap Email People Actually Read

A meeting ends, everyone nods, and three days later two people are doing the same task while nobody is doing the one that mattered. A short meeting recap email is the cheapest fix for that problem, but most recaps are either a wall of notes nobody reads or a vague "thanks all, great chat" that records nothing.

This guide shows what a useful recap contains, a template you can copy, how fast to send it, and where the usual advice about recaps goes wrong.

What a meeting recap email is for

A recap has one job: to turn what people said into what people will do. It is not minutes. Minutes record the discussion. A recap records the outcome.

That difference changes everything about length. Minutes for a 60 minute meeting can run to two pages. A good recap for the same meeting usually fits in 120 to 200 words, because it only holds three things:

• Decisions that were made, stated as settled facts.
• Actions, each with one owner and one date.
• Open questions that still need an answer, and who is chasing them.

Anything else, such as background, the debate that led to a decision, or a slide deck, goes in a link or attachment at the bottom for the people who want it.

A meeting recap email template you can copy

Here is a structure that works for most internal meetings. Replace the bracketed parts and delete any section that is empty.

Subject: Recap: Q1 newsletter plan, 3 decisions and 4 actions

Hi all, here is where we landed on Tuesday.

Decided: (1) The newsletter moves from weekly to every two weeks, starting 6 January. (2) Lena owns the editorial calendar. (3) We drop the events section for now.

Actions: Lena drafts the January calendar by Friday 11 December. Omar exports subscriber data for the last 6 months by Monday 14 December. Priya asks legal about the new signup wording by Wednesday 16 December. I book the follow up for the week of 6 January, today.

Still open: Whether the sales team gets its own section. Omar is checking with Daniel.

If I got anything wrong, reply by Thursday noon and I will correct it for everyone.

Notice the subject line. It tells people what is inside before they open it, which is the same principle covered in our guide on how to write an email subject line colleagues open. A subject that just says "Meeting notes" sinks into an inbox of 80 other messages.

How to write each part well

Write decisions as statements, not summaries

"We discussed the newsletter frequency" is a summary. "The newsletter moves to every two weeks from 6 January" is a decision. If you cannot write a sentence that plain, the group did not actually decide, and you should list it under open questions instead. That honesty saves a lot of confusion later.

Give every action one name and one date

"Marketing to look into it" means nobody will. Each action needs a single person, even if a team supports them, and a calendar date rather than "next week" or "ASAP". Dates written as "Friday 11 December" are clearer across time zones and cultures than "11/12" or "12/11".

Lead with the outcome, not the meeting

Skip opening lines like "Thanks everyone for a productive session today, it was great to see so much energy." The reader opens the email to find out what they owe. Put that in the first five lines. If you want to thank people, one short sentence at the end is enough.

Format for a phone screen

Many people read recaps on a phone between meetings. Use short labeled blocks, numbered decisions, and no tables wider than three columns. If someone has to scroll sideways, they will stop reading.

When to send it and who to include

Send the recap within two hours of the meeting ending, and never later than the end of the same working day. After 24 hours, people have already formed their own version of what was agreed, and your email starts to look like a correction rather than a record.

A practical trick is to write the decisions and actions in the last five minutes of the meeting itself, out loud. Say, "Here is what I am going to send, does anyone disagree?" This catches misunderstandings while everyone is still in the room, and it cuts your writing time afterward to about five minutes.

For the recipient list, include everyone who attended plus anyone who owns an action but missed the meeting. Do not copy in managers by default. If a manager needs to know a decision, send them a separate two line note. A recap copied to senior people tends to get longer and more defensive.

Why "send detailed notes" is the wrong advice

A lot of workplace guides tell you to capture everything so nothing is lost. The intention is good, but the result is worse than a short recap.

Long notes bury actions. When an email is 900 words long, readers skim, and skimming eyes skip the one line that says "Omar to export the data by Monday". In teams I have worked with, recaps over 400 words got noticeably more "sorry, what was I meant to do?" messages than recaps under 200 words.

Detailed notes also invite reopening. If you record every argument made against a decision, someone will reply to relitigate it by email. A recap that states the decision plainly closes the topic, and anyone with a serious objection can still raise it.

If your organization needs a full record for compliance or board purposes, keep it. Just keep it in a shared document and link to it. The email itself stays short. Our piece on the email that gets answered in one reply uses the same idea: the message carries the ask, and the detail lives one click away.

Handling replies and corrections

Sometimes someone replies, "That is not what we agreed." Treat this as the recap doing its job. It surfaced a disagreement in hours instead of weeks.

• If the correction is small, reply all with the fix in one line and update the shared document.
• If it changes a decision, do not settle it in a long email thread. Book a 15 minute call with the people involved, then send a short updated recap.
• If nobody replies by your stated deadline, the recap stands. Mention that deadline in the email so silence has a clear meaning.

If you notice recaps going unanswered week after week, read why some emails get ignored. The usual causes are a vague subject, a buried ask, or a sender who emails so often that people stop opening.

Frequently asked questions

How long should a meeting recap email be?

For most meetings, 120 to 200 words is enough. It should list decisions, actions with owners and dates, and open questions. Anything longer belongs in a linked document so the email stays quick to scan.

Who should send the meeting recap?

The person who ran the meeting usually sends it, but any attendee can do it as long as the group knows who is responsible. Agree on that before the meeting ends. Two people sending competing recaps creates more confusion than none.

Should a recap email go to people who missed the meeting?

Yes, if they own an action or are directly affected by a decision. Add a single line at the top so they know why they are receiving it. People with no stake can usually find the shared notes if they need them.