A catch-up digest is one written report on the days you weren’t reading. It’s produced once, so a return costs twenty minutes instead of a morning. This guide is about the document itself. What a good one holds, the order to read its parts in, and the mistake that turns a twenty-minute read into a lost day.
- A digest covers a stretch of days, and its blocks are ordered by what’s still costing you something. Arrival order is the one order that never works.
- On a nine-day absence, a third of what matters is usually something that didn’t happen. A notice window closing, an agreement still unsigned, a client who stopped replying on day three.
- The block people read fastest is the one about decisions taken without them. It’s normally the block that changes their week.
- The page waits for you. Read all of it, mark as you go, and save every answer for the end. The first quick thing you answer is where the morning goes.
- The report lands before the return day starts, because the return day is already booked.
How long a window to set, and what has to have been running while you were gone for the report to be possible, is the absence side of this. That’s taken on its own in the days you were gone, in one catch-up read. What follows assumes the digest is in front of you at eight in the morning, and asks what to do with it.
Nine days, written out
Most descriptions of this stop at the idea. Here’s the object, for a three-person consulting practice coming back on a Monday after nine days out.
Nine days, the 20th to this morning. 412 conversations. 14 are on this page; the other 398 closed or need nothing.
Today is 4 hours 15 minutes of meetings. Three of them were booked while you were out.
Dated, and still moving The Marchetti master agreement renews on its own on the 8th unless notice goes in. Today is the last business day that notice can be sent. The Latham phase-two report was promised for the 4th and hasn’t gone. Their steering committee meets Wednesday. Bellweather’s August invoice went past terms on the 1st. Two reminders, no reply.
Settled without you Priya gave Kestrel a two-week extension on the data pull. The delivery date you’re carrying in your head is wrong. Marchetti’s CFO answered the scope question you raised on the 19th by dropping the second workshop. The Latham kickoff moved from the 11th to the 15th.
Waiting on a decision from you Hollis Partners asked for a proposal on the 24th and want it Friday. Ferris asked twice, on the 25th and the 30th, whether you’ll take a second engagement in the fall.
Went quiet Doyle stopped replying on the 23rd, after you asked for their redlines. The subcontractor agreement Amara was sent on the 21st is still unsigned.
Expired Four meeting proposals for days that have already gone, two of them from Hollis.
Nothing in the other 398 carries a date this week.
Look at what leads. The Marchetti renewal is at the top because a clock has been running on it for nine days and stops today. Nothing about that clock is visible anywhere else on the page.
Then look at what the top block is made of. Two of its three lines describe things that didn’t happen. Your arriving mail has no account of those, which is why a record of what you are owed is worth having before an absence.
Now the second block, because the rest of this guide keeps coming back to it. Nothing in there asks anything of you. Every line changes what one of the other lines means.
The order a catch-up read has to come in
Three orders are on offer for a return morning. Two of them are habits carried over from a different task.
By arrival. This is the default in every mailbox, and it’s a fact about other people’s Tuesdays. The renewal notice that has to go out today came in on day one, so it sits at the bottom of nine days of mail, no closer to the top than a receipt. Sorting by time answers one question. When did this reach me. Across a nine-day period, every other question matters more.
By sender. The most widely repeated advice for a return morning puts mail from leadership and stakeholders at the front of the queue. Backlog newsletters go, and so does any thread whose decision has already been taken. A two-minute rule runs over whatever is quick. A pass over the calendar finishes it, for the meetings that need preparing. Those are sound rules for working a pile you’re holding, and that’s a real job. Past about a week, the item that costs you most is usually from nobody in particular. A renewal is triggered by a contracts mailbox. An unsigned agreement is from nobody at all, because it’s the absence of a signature.
By what is still moving. This is the order a report can be written in, and it’s four blocks.
- Dated, and still moving. Anything with a clock on it that hasn’t stopped. Deadlines inside the next week, notice windows, filings, invoices past terms, work you promised for a date that’s gone. This block leads because the cost of not reading it is still going up while you read. Some of it can only be answered today.
- Settled without you. What got decided, agreed, moved or conceded while you were away. There’s nothing here to reply to. It goes second because it changes what the other three blocks mean. Read it after them and you read some of them twice.
- Waiting on a decision from you. Open, addressed to you, and stalled until you say something. These go third. You can decide them once you know what the week already holds and what was agreed while you were gone.
- Went quiet, and expired. Threads that stopped, and items whose moment has passed. These go last, because they need judgment rather than speed. A returning person makes bad judgment calls in the first ten minutes.
Two rules hold inside the blocks as well. Order by date, so the block reads as a countdown and you can stop when you reach next month. And keep the expired items on their own. Four dead meeting proposals are four pieces of pure admin. Mixed into a list of live decisions, they make the list look twice as heavy as it is. Threads that stopped without an ending are worth more attention than their length suggests, and that pattern shows up away from return days too, as unanswered emails.
The block everyone skims
Decisions taken without you read like history. Nothing in there asks for anything, so a returning person moving fast gives the whole block eight seconds. It’s the most expensive eight seconds of the morning.
Three things are in there, and none of them announces itself.
Dates you’re carrying that are now wrong. Priya’s two-week extension on the Kestrel data pull is news about the four other things you scheduled around that delivery. One of those you’ve already promised to somebody else. Nothing in the Kestrel thread mentions the four, because the person who granted the extension doesn’t know about them.
Positions you’ll state that are no longer yours. Marchetti’s CFO dropped the second workshop while you were out. Miss that on the Monday and it surfaces in a meeting three weeks later, when you refer to a workshop everybody else knows was canceled. Nobody corrects you at the time. They just adjust what they think you know.
Reasons the urgent block is urgent. The renewal at the top of the page and the dropped workshop in the middle are the same negotiation. Read the first line without the second, and a defensible-looking decision about the notice comes out exactly backwards.
That last one is the argument for reading the whole page before you act on any of it. It’s also why this block sits second. On an absence of a few days you can usually work down the page as you read it. Past a week the lines have started to depend on each other.
One question does the work here, and it takes about two seconds. Does this change a date, a number, or something I’ve already told somebody? If the answer is yes, that line is a task with no message attached to it. It won’t come back around on its own.
One pass, and nothing acted on
The digest is a fixed-length document. What it asks of you runs as long as you let it. That’s how a twenty-minute read turns into a lost morning, and it happens in a completely ordinary way. You reach the Hollis proposal request in the third block. You know roughly what to say, so you open a draft. Forty minutes later the draft is decent and you’ve read half a page.
So the pass has one rule. Read to the bottom, mark as you go, act on nothing. The page holds still while you read it. Everything on it is already written down.
Three marks are enough. Today. This week. Open the thread. Nothing else, and no writing while the pass is running.
This is where the standard return-morning advice above stays outside the read. A two-minute rule is a good rule for a queue you’re working, where doing the small thing costs less than the bookkeeping of tracking it. Inside a catch-up read it stops the reading. The two-minute item is always near the top. It’s always the most satisfying thing on the page. The moment it’s done there’s another one. The rule earns its place after the read, on the short list the read produced, and it’s genuinely useful there.
What you get at the bottom of the page is the size of the period. How many things. How many are dated this week. How much of it can be done at all today, given that the day is already 4 hours 15 minutes of meetings. That number is what you plan against, and you have it once you’ve read to the end.
Time it once. A nine-day digest at fourteen items and a count takes fifteen to twenty minutes. If yours takes an hour, one of two things is true. You’re acting while you read, which the three marks fix. Or what you have is a list of the messages in the period, and you’re doing the ranking yourself as you go. That’s a different job with its own method and its own timings: how to skim a full inbox in minutes.
The morning it has to land on
The catch-up digest and your ordinary morning briefing cover two different stretches of time. The return day is the one day you get both.
Keep them apart and read them in that order. The digest covers the period and tells you what the week now is. Then the briefing for the day itself covers the next eight hours. By the time you reach it you can tell which of its items are genuinely new, and which are the live end of something you just read about. Merge the two and that distinction goes, which is how a meeting proposal that expired six days ago lands in the same list as one that came in at 7:40 this morning.
The harder problem is when. Your first day back is the worst day of the month to find twenty quiet minutes, and there’s a plain reason for that. While you were away your calendar showed you as free from Monday, so the people who were waiting booked into it. Three of the four hours of meetings on that page went in during the absence. If the digest is waiting when the day starts, the day starts with it. If it arrives at nine, it competes with a 9:00.
So have the report before the return day rather than on it. Reading it the evening before you come back costs you fifteen minutes of a Sunday and buys the whole Monday morning. On a long absence that’s the difference between deciding what your week is and having it decided for you. Delivery is a setting, and choosing the hour is a briefing that runs on your schedule.
One more thing shapes what you find on the page, and you settle it before you leave. Whatever reached you during the absence is already read, so the report leaves it out. Let very little through and the report is the whole period, a fair account of it. Let a lot through and the report is the remainder, and it reads quieter than the period actually was. Both are fine. They’re different arrangements, and it helps to know which one you chose. That’s the subject of deciding what is worth an interruption.
What Point already has written down
Point reads the mail as it arrives, every day you’re gone. That’s why the report is in front of you before the day starts, rather than an hour into it.
That’s also what pays for every block on the page. Every conversation carries a plain summary written when it landed, so the report is assembled out of nine days of records, and the 412 raw messages stay where they are. An ask sitting halfway down a long message on day four became a dated task the moment it arrived, so the Latham report reaches the first block whether or not anything about it came in while you were gone. Work you passed to other people sits on the owed-to-you side of your list, and Point chases it for you at the right moment. That’s why an agreement nobody has signed can appear on a page at all. Your own calendars are read and reconciled, so the meetings that went into your first day back are on the page as part of the return. You know about the 9:55 at eight.
Scheduling keeps running while you’re out. Point runs the back-and-forth itself. So a proposal from the 24th that would otherwise be sitting in the expired block already has an agreed time on it, waiting for you to approve it before the invite goes out.
Two things keep the read honest, and both are already there. The 398 conversations the report left out sit in the same feed the report is sitting in, a click from whichever line you’re doubting. Each one carries its own summary, so a week of one client’s mail reads at a glance. And every action taken for you across those nine days is listed in sequence, in plain language. Each entry is there to be approved, turned down or reversed. Undo covers what Point did. Once a message is on somebody else’s server nobody recalls it, and nine days away doesn’t change that.
The dial for what Point does unprompted is kept separately for each kind of work. It runs suggest-only, then review, then fully handled. Every kind opens on review, so anything higher is a setting you raised deliberately, and at the far end of the dial that kind of work proceeds without asking you first. Delivery is a setting too. When and how often you’re brought up to speed is yours to choose, which is what makes reading the digest on Sunday evening a setting rather than a trick. What else survives an absence, and what Point does on an ordinary Tuesday, is set out under benefits.
Common questions
What should I read first after time off?
Whatever still has a clock running on it. Deadlines inside the week, notice windows, filings, invoices past terms, and work you promised for a date that’s already gone. Newest-first and sender-first both put the renewal that expires today somewhere in the middle of nine days, because neither one knows anything about dates.
How long should catching up take?
Fifteen to twenty minutes of reading for a week or two away, when what you’re reading is a report on the period. The reading is the cheap part, and it’s the only part with a fixed price. If it’s running an hour, you’re either acting while you read or doing the ranking yourself as you go. Only the second of those is a problem with the tool.
Do I still have to open the actual emails?
Some of them, and the report tells you which. Anything you’ll be quoted on goes into the third mark and gets opened. Fees, figures, scope, dates you’re now committed to. You know the count by then, so checking one line you doubt is a click rather than a decision to start over.
What if the digest and my morning briefing say the same thing?
On the return day they overlap by design, and the overlap is small. Read the digest first for the period, then the day’s briefing for the next eight hours. That order is what lets you tell a proposal that arrived this morning from one that expired last Thursday. Taking them the other way around is the most common way a catch-up read gets read twice.
Is a catch-up digest just a summary of my unread email?
No, and this is the one place the difference is worth spelling out. A summary of unread mail does the third block well. It does the second badly, because a decision taken without you is spread across a thread instead of stated in a message. It can’t produce the first block at all when the dated item never arrived as mail, and it can’t produce the fourth, because a thread that stopped sends nothing to summarize.
Can I get one for a period nobody planned for?
Yes, and that’s the common case rather than the exception. Two days of back-to-back client work. A stretch of travel. A week where you were technically reachable and not actually reading. None of those has leave in the calendar to mark where the window starts, so you name the stretch yourself. Set the start earlier than feels right. The days you half-read are the ones where something got past you.
The short version
- A catch-up digest is a report on a stretch of days, and the order of its blocks is what earns its keep.
- Four blocks, in this order. What still has a clock running, what was settled without you, what’s waiting on your decision, and what went quiet or expired.
- Order by arrival and the item that expires today sits at the bottom. Order by sender and it stays out of sight, because a renewal comes from a contracts mailbox and an unsigned agreement comes from nobody.
- The decided-without-you block is the one to slow down on. Each line changes a date, a number, or something you’ve already told somebody. None of it comes back around on its own.
- Read to the bottom before you act. Three marks, no drafting, and the number at the end is what you plan the week against.
- Have it before the return day rather than on it. Your first morning back was booked by other people while your calendar showed you free.