Meeting recaps that make decisions stick

A recap that makes decisions stick names what got decided, who owns each piece, the dates attached, and what is still open, and it reaches people before they have left the meeting behind. That is the whole job. Not a transcript. A short record clear enough that nobody can quietly remember it differently next week.

Most meetings end and then slowly come undone. Everyone nodded. Everyone left with a slightly different version of what they nodded at. Three days later two people are building against each other and neither one knows why.

The recap is the thing that stops the unravelling. It is also the least glamorous writing you will do all week, which is exactly why almost nobody does it well.

Why raw notes fail and a decision log works

Raw notes fail because they record what was said; a decision log records what was settled, and only the second one survives contact with next week.

Verbatim notes are close to worthless. They record the back and forth and every side road it wandered down, then bury the one line that mattered under two hundred that did not. Nobody rereads them. I have never once gone back to a wall of meeting notes to settle an argument.

A decision log does the opposite. It throws away the debate and keeps the conclusion. "We ship the beta to the waitlist on the 30th, not the whole list. Marcus owns the send." One line. It reads like a court record, not a diary.

The test is simple. Could someone who missed the meeting act on your recap without asking a single follow-up question? If yes, it is a decision log. If they would have to reply "wait, are we doing X or Y?", you wrote notes.

Capture four things, in this order

Capture the decisions, the owners, the dates, and the open questions, in that order, and leave nearly everything else out.

Order matters because people read the top and skim the rest. Put the decisions first, where a phone screen shows them without scrolling.

• The decisions, each written as a flat statement of what will happen, not what was discussed.
• The owners, one name against each decision, never a team, because a team owns nothing.
• The dates, a real date rather than "next week" or "soon", so nobody can stretch the meaning later.
• The open questions, the things you did not settle, named plainly, with who will settle them.

The open questions section is the one people skip, and it is the one that saves you. An unresolved thing you wrote down is a task. An unresolved thing you left out is a landmine that goes off in a month when someone assumed it was handled.

One name per decision is the rule I will defend hardest. "The team will look into it" is how work quietly dies. Somebody specific, by name, or it did not get assigned.

Send it within the hour, keep it to one screen

Send the recap within the hour and keep it to a single screen, because a recap that arrives tomorrow is arguing against memories that have already set.

Memory of a meeting is sharpest in the first hour and mostly gone by the next morning. Send while everyone can still check your version against their own. I learned this the slow way, from a recap I sent the morning after, when two people had already hardened opposite versions of the same date in their heads. My clean summary read to them like I was reopening a closed question, and we spent most of a call working out what "the 30th" had even meant. Wait a day and you are no longer recording the meeting, you are proposing a new one, and people push back on proposals.

Length is the other half. If the recap runs past one screen, nobody reads to the bottom, which is where the open questions live. Cut until it fits. A recap you can take in at a glance gets read, and a thorough one that needs scrolling gets archived unread, and archived unread is the same as never sent.

This is where I stopped trusting my own first draft. My raw recap comes out either too clipped, so it reads as cold and bossy, or padded with hedges that blur the very decisions I am trying to pin down. These days I type the blunt version straight into the email and let Unvent even out the tone before it goes, so the record stays firm without reading like an order.

Make silence count as agreement

Silence after a meeting is ambiguous by default, so hand it a meaning. Say plainly that if nobody corrects the record by a stated time, it stands, and the room's quiet nods become an agreement you can point back to.

Add one line at the bottom: "If I got any of this wrong, reply by end of day tomorrow. Otherwise I will treat this as what we agreed." Then honor it.

This does two things. It gives the people who half disagreed in the room a cheap, low drama way to speak up in writing. And it shuts the door, so the decision cannot be reopened in three weeks with "I never actually agreed to that."

Some people find that closing line pushy. I think it is the opposite of pushy. It is the one move that lets a quiet person object without having to interrupt a room, and it protects everyone from the slow rewrite of memory that follows every meeting. You are not forcing agreement. You are giving disagreement a deadline.

How to recap a meeting you did not run

You can recap a meeting you did not run by writing it as a summary offered for correction, not a ruling handed down, so it reads as helpful rather than as a grab for control.

Recapping someone else's meeting is a favor that can look like a takeover if you word it wrong. The fix is framing. You are not declaring the outcome. You are writing down what you heard and inviting the actual owner to fix it.

A few things keep it clean:

• Open by naming why you are the one writing, something like "Jotting this down while it is fresh, correct anything I missed."
• Attribute the decisions to the group or the lead, never to yourself.
• Send it to the person who ran the meeting first, or at least copy them, so it never looks like you went around them.

Done that way, the person who ran the meeting is usually relieved rather than threatened. You did the tedious part they were quietly dreading, and they still hold the pen on anything you got wrong. A recap offered like that is a shared favor, not a flag you planted.

Write the recap for the version of your team that has already forgotten the meeting, because that version is the one that will read it. Everyone remembers the room they were in. Nobody remembers it the same way. The recap is the only copy you all share.