Meeting recap email template: five you can send today

A recap email is a record you are asking someone to correct, not a summary you are asking them to admire. That single framing changes the structure: decisions first, actions with owners and dates second, and an explicit invitation to correct it by a date. Send it the same day. A recap sent within hours is the agreed account of the meeting; the same words sent on Thursday are one person’s recollection of Tuesday, and they get argued with. Five templates below, by meeting type.

The five templates

Subject lines included, because the subject line decides whether the rest is read. Replace the brackets and delete what does not apply.

The rule for all five

Open with the decision, not with thanks. Thanks for your time today is a line the reader has seen ten thousand times and it trains them to skim. Decided today: we go with the 12-month term. is read. Put the thanks at the end if you want it there.

1 — Internal decision meeting

Subject: Decided: [the decision] — actions below
Decided: [what]. Not decided: [what, and when it returns]. Actions: [name] to [do what] by [date]. Parked: [items]. Corrections to me by [date] — after that I will treat this as what we agreed unless I hear otherwise.

2 — Client meeting

Subject: [Client] — [date] — what we agreed
What you asked for: [in their words]. What we agreed: [what]. What we owe you: [item] by [date]. What we need from you: [item] by [date]. Anything I have got wrong here, tell me and I will correct it.

3 — Sales meeting

Subject: [Their problem, in their words]
You said [problem, quoted]. [One sentence on what you would do about it.] You wanted to know [their question] — [answer or when you will have it]. Next: [specific next step] on [date]. Nothing else attached.

4 — Interview or candidate conversation

Subject: [Role] — next steps
Thank you for the time. Next step: [what], by [when], run by [who]. What we will assess: [what]. What I said I would send: [what]. If anything changes on your side, tell me — it does not count against you.

5 — The one-liner

Subject: One thing from earlier
Short version: [decision]. [Name] owns [action] by [date]. Shout if that is wrong. Use this for most meetings. A three-line recap that gets sent beats a thorough one that does not, and most meetings do not merit more than three lines.

What to leave out

The narrative of the discussion. Attachments nobody asked for. Anything you would not want forwarded. Recaps get forwarded — that is most of what they are for — and sometimes to the person you were most careful not to name.

When you are not sure what was agreed

Say so rather than papering over it. I think we agreed [x] — if that is not right, say so before [date] and I will reissue. A recap that overstates agreement is worse than no recap, because it manufactures a decision nobody made and then makes it hard to unmake.

Questions

What should a meeting recap email include?

The decisions, what was explicitly not decided, actions with owners and dates on both sides, and an invitation to correct it by a stated date. Context goes last or not at all — the recipients were in the meeting.

How soon should you send a recap?

The same day. A recap sent within hours becomes the agreed record; one sent days later is a recollection, and recollections get disputed rather than corrected.

How long should a recap email be?

Usually three to six lines. Most meetings need a decision, an owner and a date. Long recaps are read less, which defeats the purpose of writing one.

Should I send a recap after every meeting?

After any meeting where something was decided or someone owes something. A recurring meeting where nothing was agreed does not need one, and sending an empty recap devalues the ones that matter.

What if someone disagrees with my recap?

That is the recap working. Correct it and reissue rather than arguing in a thread — you wanted the disagreement surfaced now, which is precisely why the correction invitation is in the template.

Should I use AI to write meeting recaps?

As a first draft from what was actually said, yes — it is faster and more complete than memory. Read and edit it before sending: a summary is a claim about what people agreed, and sending one unread is how a wrong decision enters the record with your name on it.

Same-day is the rule and it is the rule that breaks first, because the person who ran the meeting is the person with no notes. Five minutes of writing immediately afterwards fixes it for most people; working from a recording is the other option, and it is the one we sell. Scriben is recording people know about. You say what the pen is and what it does, they agree, and then it stays out of the way for the rest of the conversation — that second half is the product, and it only works after the first. Recording law varies by jurisdiction and by profession: see recording people lawfully before you start.