How to Write a Meeting Recap Email

A meeting recap should contain decisions, actions with named owners and dates, and open questions. Not a transcript, not a summary of the discussion, and not a list of topics covered. If it is longer than the meeting was useful, nobody reads it and you have wasted the writing time too.

Send it within an hour. A recap that arrives the next morning has already lost most of its value, because people have re-formed their own version of what was agreed and the divergence has started.

The Format

Recap: pricing review, 24 July

Decisions

• Moving to three tiers instead of four. The Starter tier is being removed.
• Annual discount stays at 20%, not increasing to 25%.
• New pricing goes live 1 October.

Actions

• Priya: migration plan for the 84 accounts on Starter, by 7 August.
• Tom: update pricing page copy, by 15 August.
• Me: draft the customer announcement, by 8 August, for Priya and Tom to review.

Open

• Whether existing Starter customers keep their price permanently or for 12 months. Sara is deciding by 31 July.

Not discussed

• Enterprise pricing. Deferred to the August review.

Shout if any of this does not match what you heard.

Decisions first, because that is what people forget and dispute. Actions with a name and a date on every single line. Open items so nothing dangles invisibly. And a “not discussed” section, which is unusual and worth adding, because it prevents someone assuming their topic was covered.

Every Action Needs a Name and a Date

An action item without an owner does not exist. “We should look at the migration path” will not be done by anyone, and three weeks later everyone will assume someone else picked it up.

“We” is the most dangerous word in a recap. Replace every instance with a person’s name. If you cannot assign a name, that is not an action, it is an open question, and it belongs in a different section.

Dates matter equally. “Soon” and “next sprint” are not dates. If the date is genuinely unknown, write “Priya to confirm a date by Friday,” which is itself a dated action.

Write Decisions as Decisions

The most common weakness is recording discussion instead of outcome.

Before:

We had a good discussion about the pricing tiers and there were a lot of different views. Some people felt four tiers was confusing while others thought it gave customers more choice. We also talked about the annual discount and whether it should increase. Overall a productive conversation and we will continue to think about it.

After:

Decision: moving to three tiers. Starter is removed. The annual discount stays at 20%.

The first version is a record that a meeting happened. The second is a record of what is now true. Only the second one is useful in September when someone asks why Starter disappeared.

If something genuinely was not decided, say so explicitly and name who decides and by when. “Not decided” is a legitimate outcome; “we discussed it” is not an outcome at all.

Send It to Everyone Who Is Affected

Not just attendees. The recap is often the only communication that reaches people whose work depends on the decision.

Keep the distribution honest though. Adding twelve people who do not need it trains everyone to ignore your recaps.

Invite Correction

One line at the end: “Shout if this does not match what you heard.”

This does real work. Meetings routinely end with two people holding different understandings of the same decision, and the recap is the cheapest place to discover it. Someone replying “actually I thought we said October, not September” three hours after the meeting is a saved week.

It also makes the recap authoritative. Once sent and uncorrected, it is the record.

Writing It Fast

The reason recaps do not get sent is that the meeting ran to the hour and the next one starts now.

A Wrivio Context for this could say:

Rewrite these notes as a meeting recap with the headings Decisions, Actions, Open, and Not discussed. Every action must have a named owner and a date. Convert discussion into outcomes: state what was decided rather than what was said. Neutral professional register, bullet points, no filler. Keep every name, date, figure, and decision exactly as written, and do not invent owners, dates, or decisions that are not in my notes. If an action has no owner or date in the notes, list it under Open instead.

Press Ctrl+Shift+Space, paste your scribbled notes, and run it. That final rule is the valuable one: you want unowned actions surfaced as gaps, not quietly assigned to a plausible-looking person. An invented owner in a recap creates a real accountability problem.

If the meeting covered customer names, salaries, or commercial terms, run it in Local mode so the notes stay on your machine.

Common Questions

Who should write it?

Whoever called the meeting. If that is unclear, name a recap owner at the start rather than hoping.

What about AI meeting transcription?

Useful for capture, poor at deciding what mattered. Transcripts record everything said, which is close to useless as a record of what was agreed. A human still has to pick out the decisions.

How long should it be?

Under 200 words for a typical meeting. If it needs more, the meeting had too many topics.

Do I need one for every meeting?

Any meeting with a decision or an action. A pure discussion or a social catch-up does not need one.

Download Wrivio for Windows to turn scrappy meeting notes into a recap you can send before the next meeting starts.