You get back from a week off, or you surface from three days heads-down, and the dread is always the same shape: dozens of meetings happened without you, threads moved, decisions got made, and somewhere in all of it are the two or three things that now actually need you. The catching-up tax can eat a whole morning.
Here’s the thing — almost all of that morning is wasted, because you’re answering the wrong question. You’re trying to learn what happened. What you actually need is what changed.
Summaries answer “what happened.” You need the delta.
A meeting summary is complete and per-event: here’s everything that occurred in this one call. Read ten of them and you’ve reconstructed ten meetings — most of which didn’t change anything you care about.
A delta is selective and cross-event: here’s what’s different now versus the last time you checked. It throws away the unchanged and surfaces only the movement. That’s the format that lets you re-enter fast, because re-entry is fundamentally about diffing your stale mental model against current reality — not re-reading the world.
The shift is the same one that runs through all of meeting-series memory: organize around the continuous thread, then report on how it moved, rather than dumping every isolated event.
What a good catch-up actually contains
When you come back, four things matter and almost nothing else does:
- Decisions made while you were out. The calls that got taken without you — these are the highest-stakes items, because they’re already settled and you need to know before you act on a stale assumption.
- New commitments and open items. What got promised, by whom — especially anything now waiting on you.
- Threads that moved. The projects and topics where direction shifted, sped up, or stalled.
- Questions now pointed at you. The things people raised that need your input to unblock.
Notice what’s not on the list: the full content of meetings that simply happened and changed nothing. A good catch-up is mostly an exercise in leaving things out.
Re-entry isn’t reading everything that happened. It’s diffing your last known state against now — and being handed only the difference.
How to get a delta instead of a pile
You can approximate this by hand. Before logging off, jot down the open state of your key threads. When you’re back, walk each one forward: what’s new since that snapshot? It works, but it’s tedious, and it depends on you having taken the snapshot in the first place — which, the one time you most need it, you usually didn’t.
The reliable version is to have the memory track the deltas for you. Because series memory already holds the state of each recurring thread, it can tell you what changed since you last looked — per person, per topic, per series — without you pre-registering anything. That’s the delta surface: what changed while you were away, written up before you ask, scoped to the threads you actually own.
Where transcript tools fall short here
Tools that record and transcribe everything are, ironically, the worst fit for catching up — because they give you more to read, not less. After a week away, a folder of twenty fresh transcripts is a bigger problem than a smaller one. The value isn’t in the completeness of the record; it’s in the ruthlessness of the filter.
If you’re comparing tools on re-entry specifically, it’s worth seeing how a change-oriented memory compares to Otter and Fireflies — both excellent at capturing the full record, both leaving the job of figuring out what moved to you.
Coming back should take minutes, not a morning. The trick is to stop asking what happened and start asking what’s different now.