Confirming What You Just Agreed

Half of the arguments at work start the same way: two people leave a meeting sure that they agreed on different things. The fix is cheap. Send a short recap email while everyone still remembers the room. A recap is not a transcript. It records what was decided, who is doing what, and by when. Write it within an hour, before memory softens.

Subject: Recap — pricing review, 27 July Hi all, Thanks for the call. Here is what we agreed. Decisions: we keep the current price until October, and we drop the student plan. Actions: Wei sends the new price sheet by Wednesday. Anna updates the website by 5 August. Open: we still need legal to check the refund wording. If I got anything wrong, reply and correct me by tomorrow. Best, Wei

The subject line does real work. Start it with the word Recap, then add the topic and the date. Six months later somebody will search for this email, and they will search for the topic, not for your name. A dated subject also stops the thread from being confused with the next pricing discussion, which is coming sooner than you think.

Keep decisions separate from discussion. Nobody needs to relive the debate. Write only the outcome, in the shortest sentence you can manage. "We keep the current price until October" is a decision. "We talked about pricing and most people leaned towards keeping it" is a summary of a conversation, and it will not settle anything when the question comes back in September.

Every action needs one name and one date. Not two names — one. When an action says "the team will update the website," nobody updates the website. Write "Anna updates the website by 5 August." If you do not know the owner, that is useful information too. Write "Owner: to be confirmed" and the hole becomes a visible gap instead of a silent one.

The open section is the part most people skip, and it is worth more than the rest. Meetings rarely end clean. Something is always waiting on legal, on a number, or on a person who was not in the room. Listing those items stops them from quietly disappearing. It also protects you, because it shows you knew the work was not finished.

End with an invitation to correct you. One line is enough: "If I got anything wrong, reply and correct me by tomorrow." This does two things. It gives people a fair chance to push back, and it sets a quiet deadline. After that deadline, silence will count as agreement, and your recap becomes the version everyone works from.

Two limits are worth naming. First, keep it under two hundred words; people skim a long recap and nothing lands. Second, a recap is not a weapon. Do not use it to quietly add a task nobody agreed to, because people notice within a week and then they stop trusting your emails. Write what happened, send it fast, and let the record do the work.