29 August 2026
A good recap has four moves, always in this order: what was decided, who owns it, what's still open, and what changes for the person reading it. Chronology — what happened first, second, third — belongs in the transcript, not the recap, because nobody who missed the call cares in what order you argued about the vendor.
Most recaps fail because they're written like a story: we started with X, then discussed Y, then Priya raised a point about Z. That's the order the meeting happened in, and it's the wrong order to read in, because the reader is scanning for one thing — what do I need to do — and a chronological recap makes them read the whole thing to find it.
The fix is a fixed structure, applied every time regardless of what the meeting was about: decided, owned, open, changes for you. Four short blocks. If a meeting produced nothing under one of them, that block says 'none' — it does not get skipped, because a reader scanning for 'what's open' needs to know the answer is genuinely nothing, not that you forgot to check.
A transcript is a record of what was said. A recap is a claim about what it meant. Those are different documents and confusing them is the second most common way recaps fail — someone pastes the AI-generated transcript, or a wall of bullet points that mirror it turn by turn, and calls that the recap.
The transcript has no opinion about which fifteen seconds mattered. It gives the disagreement about the vendor contract the same weight as someone saying 'can everyone hear me okay.' Writing the recap is the act of deciding what mattered and discarding the rest — which is exactly the part a transcript, however accurate, cannot do for you. AVAY's meeting transcript and its notes are two separate objects for this reason: the transcript stays complete and searchable, the notes are what someone actually edits down into the message that goes out.
Take a real fifteen-minute call about renewing a vendor contract. Three people, one decision, one open question, one deadline.
Bad version, chronological: 'We started by reviewing last year's contract terms. Dorian raised the point about the 12% price increase. Mei asked whether we'd looked at alternatives. We discussed Vendly and two other options briefly. Priya mentioned the renewal deadline is coming up. We agreed to revisit pricing with the vendor before signing anything, and Mei will draft a comparison by Friday.' That is fair, accurate, and useless to skim — the deadline is buried in the fourth sentence and the reader has to read the whole thing to find the one action item.
Good version, four moves: 'Decided: we're not signing the renewal at the current 12% increase; we'll go back to the vendor with a counter first. Owned: Mei — vendor comparison by Friday; Dorian — sends the counter-offer email Monday. Open: whether Vendly's pricing actually beats a renegotiated rate — nobody's checked yet. Changes for you: nothing signs until the comparison lands, so hold off telling finance the number is final.' Same meeting, same facts, a third of the reading time, and the one thing each reader needs is in a fixed place every time.
A recap for a fifteen-minute meeting should fit on one screen without scrolling — roughly 80 to 150 words across the four blocks. A recap that runs longer than the meeting itself has stopped summarizing and started transcribing again, just with line breaks added. If a block genuinely needs more than three lines, that's usually a sign the meeting covered two topics that should have had two recaps, not that the writing needs more room.
Length should scale with decisions made, not with time spent talking. A ninety-minute meeting that produced one decision and no open questions gets a shorter recap than a fifteen-minute one that produced three. Word count tracking the clock instead of the content is the third common failure — people pad the recap to look thorough.
The recap should go out within the hour, while the decision still matches what people remember agreeing to. Wait a day and you're reconstructing intent from memory, which is how 'we'll revisit pricing' quietly becomes 'we agreed to the renewal' in someone's head by Thursday.
Whoever runs the meeting is the default owner of the recap, but the actual writing is faster when it starts from something that already has the decisions pulled out rather than a blank page and a memory of the call. AVAY keeps notes and decisions current as the meeting happens, and can answer a direct question mid-call — 'what did we land on for the vendor number' — which means the recap draft on the other end is editing, not recalling.
| Chronological | Four moves | |
|---|---|---|
| What's first | Whatever happened first on the call | The decision, regardless of when it was made |
| Finding an action item | Read the whole thing | Fixed position, second block |
| Typical length | Tracks the meeting's runtime | Tracks the decisions made |
| What's missing gets noticed | No — it's just absent | Yes — the block says 'none' |
No, unless attribution changes what the reader does with the information — for example, naming who owns an action item. Otherwise a recap that credits every remark reads like minutes, not a recap, and minutes and recaps solve different problems.
Minutes are a formal, often required record of a meeting, usually chronological and comprehensive because they may be audited or referenced later. A recap is a short, structured message meant to be read in under a minute by someone deciding what to do next — it's written for action, not for the record.
Send it to everyone invited, plus anyone whose work the decisions affect, whether or not they attended. The people who missed the call are the exact audience the recap exists for; the people who were there already know what happened.
Write the recap anyway and say so plainly — 'no decisions this call' — under the decided block, then let the open block carry the weight. A meeting that produced only open questions is still worth a two-line message so those questions don't get lost between now and the next call.
A recap is four fixed moves — decided, owned, open, changes for you — not a shorter version of the transcript, and it should be short enough to read on one screen within the hour the call ends.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.