The recap that reads like a story
Here’s a recap that showed up in a lot of inboxes this week, in one form or another:
Today we had our weekly sync about the Q3 launch. First, Anna walked us through the two landing page designs. Then we talked about the copy, and Diego mentioned that the headline felt too long. After that, we discussed the launch date, and there was a question about whether legal needs to review the page. In the end, we agreed to move forward with option B.
Nothing in that paragraph is wrong. The grammar is fine, the vocabulary is fine, and it’s an honest account of what happened. The problem is what it asks of the reader: they have to read the whole thing, hold it in their head, and mentally sort it into “so what actually got decided” and “so what do I need to do.” Most people won’t do that work. They’ll skim the first two lines, feel vaguely informed, and miss that they were supposed to send something by Wednesday.
This chronological, “first we did X, then Y happened” structure is a very natural way to write a recap — it mirrors how you experienced the meeting, and in many languages it’s the default way to report on an event. But a recap isn’t a story about the meeting. It’s a tool the reader uses instead of having been in the meeting. Those are different jobs, and they need a different shape.
The three things a reader actually needs
Nobody rereads a recap for the pleasure of it. They open it to answer one of three questions: What did we decide? What do I need to do? What’s still unresolved? A recap that’s organized around those three questions gets read in fifteen seconds. One organized around the order things were said gets read never, and then re-asked about on Slack the next day.
That means every recap you write should sort what happened into:
- Decisions — things the group agreed on and won’t be revisited
- Action items — who does what, by when
- Open questions — things still unresolved, ideally with an owner for the follow-up too
If a topic doesn’t produce a decision, an action item, or an open question, it usually doesn’t belong in the recap at all — it was just conversation, and conversation isn’t what people need to catch up on.
From narrative to skimmable
Take the paragraph from the top and sort it into that structure:
Decisions Landing page: going with design option B.
Action items
- Diego — shorten the headline, send revised copy by Wed, Jul 30
- Anna — finalize option B in Figma by Fri, Aug 1
Open questions
- Does legal need to review the page before launch? (Priya to confirm by Mon)
Same meeting, same facts, roughly the same word count — but now someone can find their name and their deadline without reading a single full sentence. That’s the actual test for a good recap: can a busy person find what applies to them by scanning, not reading.
Say which one it is: decided, or just discussed
A pattern I see often, especially from writers translating directly from languages that use one verb for both: everything in the recap gets described as “discussed,” even things the group actually decided. “We discussed the budget” could mean the budget is settled, or it could mean four people disagreed and nothing was resolved — the reader can’t tell which from that sentence.
Keep the two apart on purpose. Decided means it’s final and people should act on it. Discussed means there’s no outcome yet — and if that’s the case, say what needs to happen next, even if the next step is just “revisit next week.” A line like “Discussed the hiring budget — no agreement yet, revisiting Thursday” is more useful than “Discussed the hiring budget,” because it tells the reader not to assume anything got settled.
Action items need an owner and a date, not just a task
“Someone should follow up with the vendor” isn’t an action item — it’s a wish. An action item has three parts: a name, a task stated as a clear verb, and a real date. Not “soon,” not “next week” — an actual day. “Diego — send revised copy by Wednesday, July 30” will get done. “We should probably get updated copy soon” will get done by nobody, because it isn’t clear whose job it was in the first place.
A short recap, start to finish
Subject: Growth sync recap — Jul 28
Decisions
- Keeping Q3 marketing budget flat at $40K — no increase this quarter.
Action items
- Sarah — send updated project timeline by Fri, Jul 31
- Marcus — get two more freelance quotes by Wed, Aug 5
Open questions
- Do we need a fourth headcount this quarter, or can the freelance quotes cover it? (Revisiting once Marcus’s quotes are in.)
That’s the whole email. No greeting paragraph, no “as discussed in today’s meeting,” no closing recap of the recap. People who were in the meeting skim it to confirm their memory matches. People who weren’t get everything they need in under a minute.
Send it the same day, ideally within an hour — the value of a recap drops fast once people have moved on to their next three meetings and started to misremember what was agreed.
One practical note if you’re used to taking notes in your own language during the call and then converting them to English afterward: that conversion step is exactly where the narrative pattern tends to creep back in, since it’s easier to translate sentence-by-sentence than to restructure while translating. If you’re using Copynote for that rewrite, it works from your intended meaning rather than translating line by line — a bulleted draft is a good starting point either way, and worth reading over once before you hit send.
