A catch-up digest is one written account of a stretch of time you were away for: what happened, what got settled while you were out, and what’s still waiting on a decision. The unit is your absence rather than a day. Nearly everything else about it follows from that one difference.
This series is about stepping away from a business that runs mostly through your inbox. It starts here because the digest decides whether the rest of it is possible. A first week off that costs you a Monday is the reason there’s rarely a second one. So this chapter is about the report itself: what it has to carry, what has to have been true while you were gone for it to exist at all, and the two ends of it where things reliably fall through.
Thirteen people cut off for five days
The best evidence anyone has about coming back comes out of a small study about something else.
In May 2012, Gloria Mark and Stephen Voida of the University of California, Irvine presented A Pace Not Dictated by Electrons at the CHI conference in Austin. Their co-author was Armand Cardello of the U.S. Army Natick Soldier Research, Development and Engineering Center. The design sits in the first line of the abstract: “We report on an empirical study where we cut off email usage for five workdays for 13 information workers in an organization.” Heart rate monitors, window logging, shadowing, interviews at the end. It’s usually cited for one finding: cut off from email, people multitasked less and were measurably less stressed.
The part that belongs here is two sentences from the discussion. “In the interviews, most of the informants described that they dreaded reading their email when they concluded participation in the study. However, the process of catching up was not as bad as they anticipated.”
Thirteen people in one organization in 2012 is a small study, and the authors treat it as one. What it does is name something everybody who has taken a week off already knows. The Monday you picture at the airport and the Monday you get are two different Mondays. The gap between them holds a good deal of the reason people stay at their desks.
Read the next sentences and it gets more useful, because the study also records how one of them coped. “One informant, for example, said that when he returned to email, he read through his inbox quickly and learned a strategy of eliminating emails based on their subject header. He claimed that this took far less time than handling emails by checking them regularly throughout the day.”
That’s the whole problem in one anecdote. The strategy worked. It cleared the pile quickly, and he was pleased with it. It also ran entirely on the least reliable evidence in the message. A subject header gets typed once, before the exchange it names has happened, by whoever started it. It stays that way for the rest of the conversation. Why a preview is not a summary sets out how little of a thread survives in its packaging. Clearing a nine-day backlog off subject headers is a coin toss you can perform quickly.
So what a returning person needs is a different object in front of them.
A report on a period rather than a pile
Three things get called the same thing, and separating them is most of the work.
A morning briefing reports on a day. The period is fixed and it’s chosen for you. The report arrives on a schedule; one morning read that holds the whole working day is what that object has to carry. A skim is a pass you make over what’s in front of you, and how to skim a full inbox in minutes covers how to run one and what it costs.
A catch-up digest is the third thing. It’s a report on a stretch of time that you name, produced once, for a reader who was somewhere else the whole time.
The window is what makes it a different animal, and it’s worth sitting with, because it’s the part most people skip. The length of a night is fixed for you. You choose the length of an absence, and you have to, because you’re the only one who knows where it starts. A calendar entry saying vacation tells you where your body was. The moment you stopped deciding things is usually earlier.
There’s a second difference underneath that one. A briefing is a member of a run. It has one before it and one after it, and both do quiet work. Yesterday’s read is the reason today’s can be short. Tomorrow’s is the reason today’s can afford to be wrong. That forgiveness is the run, and a catch-up digest stands alone. The standard it’s held to changes accordingly.
Both ends of the window leak
The trailing end first, because it’s the one that actually costs people.
Your absence began at the last moment you made a real decision. For most people that’s a good half day earlier than the calendar says. Friday afternoon at the gate, you read eleven messages on your phone. You replied to two, forgot a third, and formed an intention about a fourth that went nowhere. Those eleven are now the most dangerous items in the whole period, because every one of them is marked as read. A report of what you missed leaves them out. You saw them, in a bad light, on a small screen, while boarding, and let them go.
Including a few things you genuinely handled costs you four extra lines to read. So set the start of the window earlier than your leave. Half a day usually does it, a full day if you traveled. Leave the window where the calendar put it and you lose the thing you thought about at the gate.
The leading end leaks differently. Mail keeps arriving while you read about the mail that already arrived. If the digest recomputes underneath you, you finish a different list from the one you started, and you lose track of which items you’ve actually seen. A report on a period needs an end as well as a start, and that end should be a moment you can name. Whatever came in after it is today’s problem, handled the ordinary way. Keep the two apart and you finish the catch-up, rather than discovering an hour later that you’re still in it.
There’s one moving part most people have while they’re gone, and it points outward. Microsoft’s own documentation describes the out-of-office feature in Outlook as one that “automatically sends a customized message once to each person who emails you during your absence” (checked September 6, 2026). Google says of the Gmail equivalent that “In most cases, your reply is only sent to people the first time they message you”. A second one goes out if the same person “contacts you again after four days and your automatic reply is still on” (checked September 6, 2026). Both are addressed outward, and both do their job. An automatic reply tells the world you’re away. What happened while you were away is a separate question.
There is no second digest
A morning briefing is a forgiving object. If it drops something today, tomorrow’s picks it up, because whatever it dropped is still sitting there open and presents itself again. That forgiveness does more work than anybody notices. A catch-up digest is on its own. You read this one, believe it, and go on with your week as though the days it covers are closed.
Three things follow. They’re the difference between a digest you can lean on and one that just reads well.
Omission is the failure mode. A wrong summary announces itself the moment you open the thread behind it. A conversation left out of the report stays silent forever. So the question to ask of a catch-up read is what governed what got left out. That matters more than whether the lines are accurate.
It has to state its denominator. A nine-line list is either an excellent digest of a quiet period or a broken one, and the nine lines read the same either way. Three hundred and twelve conversations, nine still open, is a different sentence entirely. The count is what makes the shortness mean something. A digest that tells you what it read hands you the way to check it.
The remainder has to stay one move away. Reachable, now, from where you’re sitting, so that going and looking at the three hundred and three costs a minute rather than a morning. That’s what turns a suspicion into a spot check. Otherwise a suspicion becomes a decision to re-read everything, which is how people end up doing the catch-up twice.
Those three together also settle the doubt that arrives around four in the afternoon, when the read felt too easy. The answer is the count, and one look behind it. A second pass over the pile is the old Monday, arriving late and calling itself diligence.
What the length of the absence changes
The same object behaves quite differently depending on how long you were out. Knowing which case you’re in tells you what to read first.
Half a day to a day. Arrivals are almost the whole story. Very little resolved itself, and almost everything was still live when you got back. A digest of a single day out is close to a long briefing, and you can treat it as one. That’s worth knowing mainly because this is the common case and it’s the one people skip: the sick day, the day of back-to-back meetings, the Thursday you meant to look and the day got away.
Three days to a week. This is the crossover. It’s long enough for a question to be raised, argued and settled while you’re gone. So the number of conversations still open comes apart from the number of messages that arrived. Read in order and you live through arguments that finished on Wednesday, which is why a report ordered by arrival is close to useless at this length.
Two weeks and beyond. Mail becomes the smaller half. Dates are what matter: a renewal, a response window, a filing, the document somebody promised for the 6th. These hold steady however long you’re away. One missed deadline is one missed deadline whether you were out for two days or twenty, and it costs the same either way. So read a long absence at the calendar end first and the mailbox end second. Tracking what you are owed is that record kept as a habit, and it’s far easier to have before an absence than to build back after one.
Two kinds of item decay faster than everything around them. Both are worth pulling out by hand at any length past a couple of days. Meeting proposals are the first. Somebody offered you Tuesday or Thursday nine days ago and both are gone, so the message is now a small piece of admin. The second is the expensive one: the thread where you were the last person expected to speak. It just stops, and the stopping arrives as silence. So unanswered emails is the shape of that problem and what catches it.
The rough rule that comes out of all this: up to about a week, ask what arrived. Past a week, ask what came due.
Silence does not arrive as a message
Here’s the part that decides whether any of the above is available to you. It’s settled before you leave, rather than after you get back.
Everything a tool can reconstruct on the Monday has a message behind it. That sounds like a small limitation, and it’s the whole ceiling. The expensive events in an absence tend to be the quiet ones. A document promised for the 6th stays promised, and the mailbox stays quiet. A client decides on the Wednesday that they’ve waited long enough, and the mailbox stays quiet. A renewal lapses, and the mailbox stays quiet. Aim a summarizer at four hundred messages on the return morning and it does a real job on four hundred messages. The four things that stayed quiet sit outside its reach.
To report a silence, something has to have been holding the expectation while you were gone. It knows on day three that the document is due. It sees on day four that the mailbox is quiet. It keeps that until you’re back to read it. That’s a watch, held continuously, and it has to be set before you go. A mailbox on Monday holds what arrived. Whatever it was waiting for on Wednesday had to be written down on Wednesday.
The milder version of the same point applies to everything else in the report. A thread’s last message from Sunday holds Sunday. What that thread meant on the Thursday it mattered lived on the Thursday. The state a conversation was in while it was live, who was blocked on whom, what was still open at the point somebody gave up and decided it alone: that’s information that existed during the period, and it thins out afterward.
So the honest test of a catch-up digest is a question about the days before it, rather than about the report: was anything reading while you were away. If the answer is no, what you have is a fast summarizer pointed at a backlog. That’s genuinely useful, and it beats sorting by subject header by a wide margin. It tells you what came. It cannot tell you what stayed quiet, and that one difference is the one worth carrying out of this chapter.
Which makes the reading something you arrange before you go rather than something you ask for when you get back. Setting it up, and deciding which parts of it a person still has to hold, is covering the inbox while you are on leave, later in this series.
The parts a digest cannot reach
Four boundaries, said once, because a report that oversells itself costs you more than a shorter one.
It knows what your mailbox knows. A phone call, a conversation in a corridor, a decision taken in another system: a two-week absence contains some of that, and it sits outside the period as far as any digest is concerned. The report covers most of what happened. The gap is usually a conversation somebody had about you.
Tone goes first. Warmth, irritation, the particular coolness of a client who has decided something and kept it to themselves: a short account keeps the facts and drops the temperature. In a digest, a client who has quietly cooled reads exactly like a client who agreed.
Anything you will be held to, you read. Fees, figures, scope, dates you’re now committed to, advice with your name on it. The digest’s job is to tell you which threads those are, and that’s the more useful job of the two.
A pile that’s genuinely too big for one person needs a second person. Somebody has to be able to act while you’re gone. That’s either a partner who covers for you, which has its own failure modes, or a second seat on your side of the business, which is later in this series. A digest makes the return survivable. Somebody available on the Wednesday is a separate arrangement.
What Point has already been keeping
Point is the client your mail already lives in rather than a summarizer aimed at a backlog, and for this particular job that distinction is the whole thing. The reading happened while you were away. By the time you sit down, it’s done.
Gone for an afternoon or gone for three weeks, what you get back is a single digest of the stretch. It carries both halves: the account of what happened, and the shorter list of what’s still waiting on a decision from you. It’s cheap on the Monday because it was built across the days themselves. Every conversation was summarized and ranked as it landed, across all the days you were gone. So the read assembles out of records that were kept a day at a time, rather than out of four hundred raw messages at the moment you ask.
The calendar half survives the absence for the same reason. A request buried three paragraphs into a Wednesday message got lifted out at the time as its own dated item, with the conversation still hanging off it. The promises other people made to you sit separately from the ones you made to them. So the deadline question on your return goes to a record, rather than to your recollection of a week you spent somewhere else. Scheduling is the other half of it. Point runs the back-and-forth itself, so where you left that running, some of what came in while you were out already has an agreed time on it instead of a proposal that expired on Thursday.
Two things keep a short read checkable rather than something you take on faith. Whatever the digest left out sits in the same feed you’re reading it in, so going to look at that part is one move inside one application. And what got done on your behalf is written down in order, in plain words, with the way back attached to the entry. That’s worth a great deal more after nine days than after one night.
How much Point does on its own is set per kind of work, along a range that runs from suggest-only, through review, to fully handled. Every kind starts at review, so a higher setting on any of them is one you chose and moved. At the top of that range, work of that kind goes ahead on its own. Undo covers what Point did. Once a message has reached another company’s server it’s gone, and a vacation works the same way as any other day. Everything Point does has the rest.
The report is the easy half
Standard advice for the return morning is decent as far as it goes. A widely circulated version tells you to take leadership and stakeholder mail first, delete the newsletters and the threads where the decision has already been made, apply a two-minute rule to anything quick, and then read the calendar for the meetings that need preparing for. Every step of that is sensible. Every step of it also assumes the pile is already in a state where those judgments are cheap to make. Getting it into that state is what this chapter has been about.
The whole list leaves one thing out, and it’s the same thing the digest leaves out.
At twenty past eight you know what the period held, which nine things are open, and what falls due by Thursday. It took twenty minutes, and it’s the cheapest part of the day. What comes after it is harder. The momentum you left with is still somewhere behind you. How much of the week is already spoken for is an open question. And a report about the past has one question it can’t touch: what to do first with a clear morning.
The hours that follow the reading are where a week away quietly turns into two, and they’re the part that rarely gets written about. They are the next chapter.