How to write a meeting recap email

A fifty-minute demo ends on a Tuesday afternoon. Four people were on the call: an operations manager, two future users, and a finance lead who joined in the last ten minutes. The rep closes the window and sends a two-line note thanking everyone for their time. Ten days later the deal has not moved. When a call finally happens, the finance lead asks whether the vendor was going to handle the data migration. It was discussed. A clear answer was given. Nobody can recall what it was. The deal slips a quarter, not because of a technical obstacle but because of one sentence that never made it into writing.

A meeting recap email closes exactly that gap: it turns what was said, what was decided and who owes what into a single text everyone can correct. What follows covers how a recap differs from a courtesy note, the blocks it has to carry, how to build the subject line, why separating decisions from assumptions is an expensive distinction to get wrong, when to send it, the reader who was not in the room, the three parts of an action item, the meetings that deserve no recap at all, how the record attaches to the CRM, and what changes by meeting type.

1Meeting2Raw notes3Triage4Recap5Confirm6Follow-up

A recap is a record, not a courtesy

A thank-you note protects the relationship. A recap moves the deal. The difference is that the thank-you note changes nothing, while the recap lifts the outcome of the meeting out of spoken memory and into a text that can be corrected. That transfer is a quality check in itself. Sit down to write and you discover which topics never actually closed: of the three things you were sure about walking out, two turn vague the moment you try to write them down.

The second effect is quieter. A written summary gives the other side a chance to object, and most people will not stay silent about being misremembered. When a correction arrives, you win, because you learn about the faulty assumption in week one rather than mid-project. When no correction arrives, you are left with a text both sides have seen. Do not treat that as legal weight. In a working relationship, a sentence that exists in writing is simply a sentence that gets remembered.

The blocks a recap has to carry

Within fifteen seconds of opening the email, the reader should know where things stand. What makes that possible is not length but order: state of play first, commitments second, detail last. The block list below works for almost any meeting type. Its real benefit is diagnostic — you notice the missing block while writing, and if you catch it early enough, you can still ask before the meeting ends.

• Context: Which meeting, which date, who attended and what question you met to answer, in one line. This is also what makes the email findable in a mailbox search three months later.
• Decisions: The topics that actually closed. Each sentence should name what closed and who closed it — not we discussed, but it was agreed to proceed this way.
• Assumptions: Items that were never settled but that you are proceeding on. Writing these under their own heading, openly inviting correction, is the single most valuable part of a recap.
• Open questions: Things without an answer yet, each with the person it is owed by. A question with no name attached is a question nobody asked.
• Actions: Items written as owner, date and output. Put your own side first.
• Next step: The date, format and purpose of the next contact. A dateless we will be in touch cools a deal down.
• Attachments: Deck, document, recording link. Attachments come last, and the body must make sense even if none of them are opened.

What the list leaves out matters just as much. A recap is not a continuation of the pitch: no product praise, no new argument, no feature you forgot to mention in the room. The text draws its power from looking neutral. The moment it turns into a sales message, the reader stops treating it as a document and starts treating it as an ad — and stops forwarding it.

The subject line does its work in three seconds

The most-read part of a recap is not the body but the subject line, because this email is not read once and archived; it is searched for again for months. A good subject line carries three facts: that this is a summary, which company it concerns and which date it belongs to. Company name and date are the two keys someone digs with half a year later. We cover how the subject line and preview text work together in our piece on subject lines and preview text.

The first three lines matter almost as much, since that is what shows in a phone notification. Do not spend them on pleasantries. Lead with where the work stands: what was decided, what comes next, what is expected from the reader. If a thank-you belongs anywhere, it belongs at the bottom.

A skeleton, not a template

Templating the recap is tempting and partly right: the order of blocks should be fixed. But fix the sentences too and the email becomes instantly recognizable, at which point readers stop scanning it. The distinction is clean — the skeleton repeats, the content does not. Let your saved-text library supply the headings and the block order, never the sentences.

Separate decisions, assumptions and open questions

Most recaps fail for one reason: three different kinds of information get mixed into the same paragraph. A decision is settled, an assumption is fragile, an open question has no answer yet. Written in the same tone, the reader cannot tell which to trust, and the most dangerous outcome follows — an assumption read as a decision. The split below gives you a small set of sentence patterns you can use directly.

Block	Sentence pattern	If it blurs
Decision	It was agreed to proceed this way, with the decision maker named	A later argument over what was said
Assumption	Unless we hear otherwise, we are assuming	A wrong assumption surfaces mid-project
Open question	This is still unresolved; who answers it	The question goes unowned and unanswered
Action	Who delivers what, by which date	Everyone's job becomes nobody's job
Next step	Date and purpose in the same sentence	The calendar empties and the deal cools

The assumption pattern is the strongest of these, because it converts silence into information. It also has a limit. Writing something as an assumption when it was never discussed is manipulative, and once noticed it costs more trust than the clause was ever worth. Assumptions belong to topics that were raised but not resolved. Anything never raised belongs in open questions.

How fast should you send it?

The practical measure is before you leave your desk. Detail is still sharp in the first hour or two; a recap postponed to the evening arrives visibly thinner. Speed also reads as seriousness. For a buyer talking to several vendors, the gap between a summary that arrives the same day and one that arrives three days later gets discussed internally more often than any product difference.

Here is where the usual advice stops working. If the meeting produced a request you cannot answer, do not hold the recap hostage to that answer, and do not invent one. Split them: the summary goes out today, the technical answer follows in its own message on the date you promised. Sitting on a recap for three days while chasing one open item costs far more clarity than it buys.

The outcome of a meeting is not decided in the meeting but in the two hours after it, and a decision not written down in those two hours is not a decision.

Your real reader was not in the room

A recap earns its keep when it reaches the person who was not there. In a committee purchase, most of the people who influence the outcome never attend the demo; they meet you through an email forwarded internally. So write it to be forwarded: expand the acronyms, put roles next to names, and keep the in-jokes and half-finished sentences of the call out of the text entirely.

In practice that means one line of context at the top: who met whom, about what. We go into how buying committees are worked in our article on multi-threaded selling, and the recap is the cheapest instrument in that strategy. One email introduces you to three people you have never spoken to.

An action item is an owner, a date and an output

An action item has three parts and all three are mandatory. The owner is a person, not a department; IT will look into it binds nobody. The date is a day, not next week. The output is something you can name: a document, an approval, a test account. Miss any one of the three and the line stops being an action and becomes a wish.

Putting your own side's items at the top of the list is a small move with an outsized effect. Saying what you will deliver before saying what you expect changes the register of the whole email; it reads as a shared plan rather than a list of demands. To keep those items from evaporating after the call, the record-keeping approach in meeting notes and action tracking does most of the work for you.

As deals grow, the recap alone stops being enough. In a five- or six-step purchase touching several departments, the summary email naturally turns into a schedule. That is the moment to build a mutual action plan and treat each recap as its weekly update, so no single email has to rebuild the context from scratch.

Not every meeting deserves a recap

This advice has a boundary. Daily team standups, fifteen-minute check-ins and warm calls with a customer you have worked with for years need no recap. Sending a block-structured summary after a conversation like that formalizes a relationship that did not ask to be formalized, and leaves the other side feeling logged. Tone carries as much information as content does.

Use a simple threshold instead: write a recap if a decision was made, if someone now owes something, or if a person who matters to the outcome was absent. If none of the three is true, two sentences will do. Teams without that threshold turn recaps into ritual within a quarter — everyone writes them, nobody reads them, and the habit quietly dies.

Put the recap on the record, not in an outbox

An email in one person's sent folder is not company memory. When that rep goes on leave or leaves the company, the meeting looks as though it never happened. A recap filed against the opportunity lets whoever prepares the next call pick up the context in five minutes. Having meeting and call notes written into the CRM automatically takes this step out of the realm of personal discipline.

Automatic note-taking and transcription help here, but they also breed a misconception: a raw transcript is not a recap. The full text of a fifty-minute call tells you nothing, because nobody reads it. The value of a recap comes from what you remove, not from what you add. Throwing away most of the conversation and leaving the decision behind is human work, not tool work — a good summary is judged by what it leaves out.

Keeping the pre-meeting preparation and the post-meeting summary on the same record pays off too. When the briefing written before the call sits next to the summary written after it, the agenda for the next meeting assembles itself: what did we assume last time, what do we verify this time. We cover the preparation side in pre-meeting account briefings.

What changes by meeting type

The skeleton stays; the center of gravity moves. After a discovery call, the most important section is not the decisions but the problem as the customer described it. Resist the urge to rewrite it in your own vocabulary and quote it as closely as you can, because that is the only proof that you understood. Which questions produce that raw material is covered in discovery call questions.

After a demo the weight shifts elsewhere: what was shown, what was not shown, and which technical question is still open. Writing down what you did not show is unusual and unusually effective. The buyer is already wondering about it, and seeing that you know it and are not hiding it builds more confidence than any of the screens you did show.

In a periodic review with an existing customer, the recap moves closer to a performance document: commitments made last period, where things stand now, the target for the next one. We describe how that meeting is structured in our piece on the customer business review; its agenda converts directly into the recap's block order, and over time the two become a single series.

When no one replies, the recap works a second time

Silence after a recap is not bad news. Most of the time it means nobody saw anything wrong. What matters is what you do next. In deals that go quiet, the recap hands you ready-made ground: instead of inventing a new argument, you touch one of the items already agreed and ask where it stands. We look at why that silence happens and how to read it in our article on ghosting in sales.

The rhythm of follow-up comes out of the recap as well. The dates in the action list are natural reminder points, and completing your own item gives you something concrete to write about, so you never need the phrase just checking in. We collected ways to build that rhythm in sales follow-up strategy. To start, do one thing: for two weeks, write a recap after customer meetings only, and count how many items come back corrected. That number tells you how much you were previously misremembering.

For a recap to last, it has to land on the deal record rather than in an inbox. Rocketly keeps meeting notes, action tasks and reminders on the customer's own record — open a free account and build your summary and follow-up flow there.