The meeting recap email template, with a filled example

The meeting recap email template

This is the full template, in the order it is sent. Copy it, replace everything in square brackets, and delete any section that is genuinely empty. Do not keep an empty heading with "N/A" under it.

Subject: Recap: [meeting name], [date]

To: [everyone who attended] · Cc: [people who need the record but were not there]

Hi all,

Why we met: [one sentence, the purpose in plain words. Example: to decide whether the Starter tier price changes before renewals open.]

Date and attendees: [date and time] · [names of who was there] · [names of who sent apologies]

Decisions made

1. [Decision, written as a finished thing, not a discussion. Include the number, date or name that makes it real.]

2. [Second decision.]

3. [Third decision.]

Action items

1. [What has to be done, starting with a verb] · Owner: [one person's name, never a team] · Due: [a calendar date, never "next week"] · Status: [Not started / In progress]

2. [Second action] · Owner: [name] · Due: [date] · Status: [Not started / In progress]

3. [Third action] · Owner: [name] · Due: [date] · Status: [Not started / In progress]

Still open

1. [Question nobody could answer, and who is going to answer it, by when.]

2. [Second open question.]

Next meeting: [date, time, and the one thing that meeting has to settle.]

Anything wrong here? Reply by [date, usually 24 to 48 hours] and I will correct the record.

[Your name]

That is the whole thing. The rest of this page is what goes in each slot, a filled example, and two variants for clients and for meetings that need a written record.

The four columns in an action item

The action items are the only part of a recap that create work for other people, so they are the part worth getting exactly right. Four pieces per line, always in the same order: what, who, when, where it stands.

Written out, one action reads: verb first, then the single person who owes it, then a date on a calendar, then its status on the day you send the email.

• If two people genuinely share an action, split it into two lines with two owners and two dates. Shared ownership is how an action quietly becomes nobody's.
• If an action has no date yet, it is not an action item. Put it under Still open with the name of whoever will set the date.
• Keep the wording identical from one recap to the next, so an item that is still open in three weeks is obvious at a glance.

A recap is not a follow-up. Send the right one.

People use the two words for the same email, and that is why so many of these emails do two jobs badly. Keep them apart.

A recap is a record. It says what was decided and who owes what. It goes to everyone who was in the meeting, plus anyone who should have been. Its job is to be correct and findable six weeks later when somebody asks "who agreed to that?".

A follow-up is a relationship email. It goes to one person or one company, it thanks them, and it pushes one next step. Sales calls, interviews, and first client meetings usually need a follow-up. If that is what you are writing, use the follow-up email after a meeting template instead.

Some meetings need both. Send the recap to the group, then a short personal follow-up to the one person you want to move forward with.

• Recap = what happened, sent to the group, written to be re-read later.
• Follow-up = what happens next between you and one person, written to get a reply.
• Minutes = the formal, complete version for governance. If your meeting needs a signature or a motion, use the meeting minutes template.
• If you cannot decide, ask yourself who reads it in a month. Nobody re-reads a follow-up. People re-read recaps constantly.

The subject line formula

The subject line has one job: let a person find this email in six weeks by searching one word they remember. Not "Great meeting today!" That word does not exist in anyone's memory.

The formula is Recap: [meeting name], [date]. Meeting name first because that is what people search for. Date second because there is usually more than one of these meetings.

If a decision was the whole point of the meeting, put the decision in the subject instead of the topic. A subject line that says the answer saves people from opening the email at all.

• Recap: Q4 pricing review, 8 Sep. Plain, searchable, and a good default.
• Recap + 3 actions: Onboarding redesign kickoff, 8 Sep. Tells people there is something waiting for them inside.
• Decision: Starter tier moves to $24 in January (pricing review recap). Use this when the decision matters more than the meeting itself.

A filled example: internal team recap

Here is the same template with a real meeting in it. Notice how specific the decisions are. Every one of them has a number, a name or a date attached, so there is nothing left to interpret later.

Subject: Recap: Q4 pricing review, 8 Sep

To: Maya Okonkwo, Daniel Reis, Priya Nair, Tom Alvarez · Cc: Sofia Bergman (finance)

Hi all,

Why we met: to decide whether the Starter tier price changes before renewals open on 2 January.

Date and attendees: Tuesday 8 September, 10:00 to 10:45. Maya, Daniel, Priya, Tom. Sofia sent apologies and gave her numbers by email beforehand.

Decisions made

1. Starter moves from $19 to $24 per month on 6 January. Annual Starter moves from $190 to $240 on the same day.

2. The 412 accounts that signed up before 1 June keep $19 until 1 July. They get a separate email, not the general announcement.

3. Pro and Team prices do not change this cycle. We revisit in April.

4. We announce on 2 December, five weeks before the change, not two. Daniel pushed for the longer notice and nobody objected.

Action items

1. Rebuild the churn model at $24 with the 412 accounts excluded · Sofia Bergman · Fri 18 Sep · Not started

2. Draft the 2 December announcement email, one general version and one for grandfathered accounts · Daniel Reis · Fri 18 Sep · Not started

3. Update pricing page copy and the in-app upgrade screen in staging · Tom Alvarez · Mon 5 Oct · Not started

4. Confirm with support how many refund requests we should staff for in January · Maya Okonkwo · Fri 25 Sep · In progress

5. Answer the upgrade-then-downgrade billing question · Sofia Bergman · Fri 11 Sep · Not started

Still open

1. Do the 412 grandfathered accounts keep the old price if they upgrade to Pro and later downgrade? Sofia is checking what billing can actually do and will answer by Friday 11 September.

2. Nobody knows whether the reseller contracts in Germany have a price-change notice clause. Tom is pulling the two contracts.

Next meeting: Tuesday 22 September, 10:00. One job: approve the announcement email and the grandfathering email as final copy.

Anything wrong here? Reply by Thursday 10 September and I will correct the record.

Priya

That email is just over 300 words, a little longer than a normal internal recap because the pricing decision carries numbers and one exception. It took about ten minutes to write, because the decisions were captured while the meeting was still running instead of being reconstructed at 5pm. Every date in it is a real date on a real calendar, which is the only way the "never next week" rule survives contact with a busy week.

Each block of the recap, and the mistake that kills it

Most bad recap emails fail in the same five places. Here is what each field is for and the mistake to avoid.

• Why we met. One sentence, in the words a person outside the meeting would use. The mistake is copying the calendar invite title back at people. "Q4 sync" tells a reader nothing. "To decide whether Starter changes price before renewals" tells them everything.
• Attendees. Names, plus who was missing. The mistake is leaving out the apologies. Six weeks later, the person who was not there is the one who wants to argue with a decision, and the record should already say they were absent.
• Decisions. Write each one as a finished thing with a number, a name or a date in it. The mistake is writing the discussion instead of the outcome: "we talked about raising prices and Daniel had concerns" is not a decision. If the meeting genuinely decided nothing, write "No decisions. We meet again on the 22nd to decide X." That is a useful sentence.
• Action items. One owner per action, a real calendar date, and a verb at the front. The mistake is a team name in the owner column. "Marketing" will not do it. A person will. The second mistake is "next week", which means nothing by the time anyone reads it. If pulling these out by hand is the part you hate, there is a whole guide on getting action items automatically.
• Still open. Every unanswered question gets a name and a date too, otherwise it is not open, it is forgotten. The mistake is dropping this section because it looks like a failure. It is the opposite. A recap that admits two things are unresolved is trusted more than one that pretends everything was settled.
• Next meeting. Date, time, and the one thing it has to settle. The mistake is "we'll schedule something". Nobody schedules something.
• The correction line. Give people a short window to fix the record. This turns your email from one person's version into an agreed record. Almost nobody replies, and that silence is exactly what makes it useful later.

Variant 1: the client recap

Same skeleton, three changes. A client recap is read by people who were not all in the call, sometimes by someone senior who never joins these meetings at all. Write it so a stranger can follow it. If you send one after every session, how consultants run the loop from client call to recap covers the rest of the routine.

Split the action items into two lists, ours and yours. A single mixed list lets the client's items quietly become your problem. Two lists make the split visible without you having to say anything awkward.

Restate anything that touches money, scope or dates in full, even if it was obvious in the call. "As agreed, the extra two locales are in scope at no change to the 14 November delivery date" is the sentence that saves the project in December.

Keep the tone warm and the content dry. No adjectives on the decisions.

• Purpose line stays, but written for someone who was not there.
• Decisions become What we agreed, and every scope, price or date change is spelled out in full.
• Action items split into On our side and On your side, each with a name and a date.
• Still open becomes What we need from you, which is where you put the things blocking you.
• Next meeting stays, and add the one input you need before it.
• Add one line at the end: "If anything here does not match your understanding, let me know by [date]." That is your paper trail, and it sounds like courtesy.

Variant 2: the recap that has to double as a written record

Sometimes the recap is the only document that will ever exist. Board-adjacent meetings, contractor and vendor calls, HR conversations, anything where a decision might be questioned later. In that case, tighten four things.

First, put the exact start and end time in, not just the date. Second, name who proposed each decision and note whether anyone disagreed. A recorded objection protects both people. Third, avoid summarising anyone's reasoning in your own words. Quote a short phrase or leave it out.

Fourth, say where the fuller record lives. If you have a recording or a transcript, one line pointing to it is worth more than three extra paragraphs of your memory. If the meeting is formal enough to need motions and votes, stop using a recap email and switch to proper minutes or the board minutes format.

One warning. If you are going to record the meeting to build this record, tell people at the start. In many places that is the law, not a courtesy, and consent rules vary a lot by country.

• Exact times, start and end, plus who joined late or left early.
• Attribution on decisions: who proposed it, who agreed, who objected and on what grounds.
• No paraphrasing of positions. Short direct quotes, or nothing.
• A pointer to the full record, for example "full transcript on file, available on request".
• Distribution list, so it is clear who received the record and when.
• Announce recording at the start, and note that you did. The rules are covered in do you have to tell people you're recording a meeting.

What to leave out

The blow-by-blow is the enemy. A recap that walks through the meeting in order, saying who spoke and what they thought, is a transcript with worse formatting, and nobody reads it. Your reader wants the result.

Cut all of this:

• The chronology. "We started by reviewing last week's numbers, then Maya raised..." Nobody needs the order things happened in.
• Discussion that led nowhere. If an idea was raised and dropped, it does not go in. If it was raised and parked, it goes under Still open, in one line.
• Who said what, unless attribution changes the meaning or you are writing the written-record variant.
• Praise and mood. "Great energy in the room today." Say that in person.
• Your own commentary on whether a decision was right. The recap records the decision. Argue somewhere else.
• Attachments nobody asked for. A 40-slide deck at the bottom of a recap guarantees the recap goes unread. Link it, do not attach it.
• The full transcript. Even when you have one, paste the summary and keep the transcript on file for the person who asks.

How long it should be, and when to send it

Short. A recap for a 45-minute internal meeting fits on one phone screen, roughly 150 to 250 words. If yours runs past 400 words, you are writing the chronology again.

Send it the same day, ideally within two or three hours. There are two reasons and neither is about being impressive. Your memory of who agreed to what starts going soft after about a day. And an action item that lands while people still feel the meeting gets started; one that lands on Thursday for a Monday meeting is already dead.

Use this as a rough guide.

If you would rather not write it from memory

Everything above works with nothing but a notepad. The reason people stop sending recaps is not that the format is hard. It is that at 5pm you cannot remember whether Sofia said the 12th or the 19th, so you write something vague, and a vague recap is worse than none.

If you record the meeting, that problem goes away. Noter AI has an Email output style that takes a recording and writes it out in this shape: purpose, decisions, action items with owners and dates, open questions. You record the meeting from your phone on the table, or send a bot into the Zoom, Teams, Meet or Webex call, and the draft is waiting a few minutes after you stop: processing runs at roughly two minutes per hour of recording, plus however long the audio takes to upload. Switch to the Minutes of meeting style when you need the fuller written record from the same recording, or the To-do list style when all you want to send is the action list. There is also a Custom instruction style where you describe the tone you want, so the email does not read like a machine wrote it.

Two details that matter for recaps specifically. Speaker labels mean the draft can say who committed to what instead of guessing, and every line carries a timestamp, so if someone disputes a date you tap the line and hear that exact moment. And the transcript is editable: fix a misheard name or a product term, re-run the summary, and the corrected version flows through. More on that in editing an AI transcript and re-running the summary.

If your meetings are not in English, or not only in English, this is the part where most tools fall over. Noter AI transcribes 60+ languages and detects the language automatically, so nobody has to choose one before recording, and a sentence carrying two languages survives with both halves readable, rather than the second one arriving as phonetic nonsense. A finished recap can then be translated into 18 languages, which is how a meeting held in Arabic or Spanish reaches a head office that reads English. That is covered properly on the multilingual meeting transcription page.

The plan is $9.99 monthly or $49.99 annually, charged per person rather than per seat. Recaps are the kind of habit that spreads sideways: one person starts sending them, it becomes the norm, and six months later half the department writes them. With a seat licence that spread is a budget conversation, because the per-user rate steps up. Here each new person buys their own subscription at the same $9.99, so the total rises in small predictable steps. It is not a team account, though: no shared workspace, no admin console, no single invoice. Test it on one real meeting and judge one thing only: whether the draft it hands you is closer to sendable than what you would have typed at 6pm. Free trial on iPhone and iPad and on Android.

Whatever you use, send the recap. The format on this page is the whole trick, and it works just as well typed by hand.