The catch-up read is the short part of the first day back. Twenty minutes after you sit down, the days you were gone are accounted for. The open threads are counted. This week’s dates are in front of you. Then seven hours are left, and the pile is out of them. The week ahead already holds commitments other people made while you were away. Those seven hours decide whether the time off holds or gets spent by Wednesday.
The chapter before this one is about the report itself, what it carries and where it stops. This one picks up after the reading. It covers the order to work in on the first day, the one decision that gets more expensive every hour you leave it, and why the third day is usually the day that goes.
The hour after the reading
The instinct is to start at the top of the open list and work down it. That treats every item as though it needs the same thing from you. It also spends the best hour of the week on the cheapest decisions in it.
Three passes, in this order. The order is most of the method, because each pass makes the next one shorter.
One: decide what the week can hold. Before you answer anything, read this week and next in the calendar. Add what the digest says falls due. You’re after one number, which is how many hours are already committed. It’s nearly always more than you expect. The first free slot on a returning person’s calendar is the slot other people booked while you were away, and they booked it in good faith. Two things help here, and both are arrangements you make before you leave: keeping client work off the first day, and holding the first morning for the return itself. If today has neither, today is shorter than you think, and it’s better to know that at 8:30 than at 2:00.
Two: decide what moves. Which commitments move, rather than which ones you do. The next section is about this pass. It’s the one part of the day with a deadline of its own.
Three: answer things. Last, with the shape of the week already settled. Then every reply you write knows whether the thing it promises can actually happen.
Most people run pass three, then pass one, and stop there. That sequence is how a week off turns into two weeks of repair.
The dates did not move
Here’s the arithmetic, out loud. You were gone five working days. The work that was due in those five days waited for you while you were on a beach. It moved onto this week, where a week’s work was already waiting. So you’re holding something like nine or ten days of obligation. You have five days to put it in. One of those five is today, and most of today is going to this.
Something is going to move. That’s subtraction, and it happens to everyone who takes a week. You choose what moves on Monday morning, or you find out on Thursday afternoon.
Choose it on Monday, because the explanation has a half-life. On the first day back, “I was out last week, so the draft will reach you Thursday rather than tomorrow” is a complete and ordinary sentence. Almost everyone you send it to reads it as competence. By the fourth day the same sentence has quietly become an excuse. You’ve been back long enough to have said something, and the person waiting has spent three more days assuming their date still stood. The absence pays for the change for about a day. After that you pay for it.
So the first working hour goes to the two or three commitments that will slip. Each one gets a message with a new date in it rather than an apology. A date is a decision the other person can plan around. An apology asks them to do the planning. Telling a client about a delay is the longer version of that message. The short version is three lines: where the thing stands, the new date, and anything you need from them to hold it.
One more piece of the same arithmetic. If you’re moving nine dates rather than three, the week you took is the messenger. The business was already running full before you left, and the vacation is simply the first thing that showed it.
Most of what arrived is not a reply
By the time you get to the mail, the useful question about each item is what state it’s in. There are four.
Live. Still waiting on you, still current, still yours to settle. These get a real reply. On a five-day absence there are usually fewer of them than the volume suggests, and they’re the ones that deserve your full attention.
Overtaken. Events answered the question, or somebody else did, or time did. A colleague handled it. The client found the number themselves. Two people argued it out on Wednesday and landed where you would have. These get one line to say you’ve read it, and plenty of them get nothing at all. A considered answer to a settled question reopens something that closed on its own, and it makes everyone re-read a thread they’d finished with.
Expired. The offer of Tuesday or Thursday, both of which are gone. The invitation to the thing that has now happened. The request for input on a decision made on day three. These are small pieces of admin with the judgment already gone out of them. Close them explicitly rather than answer them late. One line, and the thread ends.
Newly due. These sit outside the mail. A date arrived while you were gone, or arrives this week, and it was always a date rather than a message. A pile leaves this category out, and a reply leaves it standing. On absences longer than a week, this is usually where the real cost sits.
Most returning people give all four the same treatment and the same length, in the order they arrived. Sorting first costs about ten minutes, and it removes more than half the work.
Two habits go with it. Deduplicate before you write anything: three messages from one person is one reply, and the newest almost always supersedes the two before it. And apologize once. You were away, you said you were away, and the fortieth “so sorry for the slow response” reads as anxiety rather than courtesy. “I was out until Monday and I’m catching up on this now” is enough, and it’s true.
Everything you send today comes back Wednesday
This is the part that surprises people who did the first day well.
The size of your Wednesday is set by how many of Monday’s replies invite an answer. Sixty replies that each carry a question are sixty threads you have just started. They come back in a block, because you sent them in a block. You can clear a backlog on Monday and build a heavier one for midweek in the same morning, and the second one is easy to miss while you’re building it.
Two things fix it, and both take about as long as the alternative.
Write to close where you honestly can. A reply that states a decision ends a thread. A reply that asks “what do you think?” starts one, and half the time you already know what you think and were being polite. That politeness costs more this week than it does in an ordinary week.
Stagger the ones that have to open. Six threads genuinely need real back-and-forth. Send two today. Set the other four aside for Tuesday and Wednesday, and their replies land spread out rather than on one afternoon. Setting something aside until you want it back is what that’s for, and the first week back is the week it earns its keep.
The part of the fade-out nobody measured
All of this is worth structuring because the thing you’re protecting is smaller and shorter-lived than people assume.
The evidence sits in a meta-analysis published in the Journal of Occupational Health in 2009, Do We Recover from Vacation?. Jessica de Bloom and colleagues at Radboud University Nijmegen, in the Netherlands, wrote it. Seven studies survived their exclusion criteria. The finding runs two ways: “vacation has positive effects on health and well-being (small effect, d=+0.43), but that these effects soon fade out after work resumption (small effect, d=-0.38).” The benefit is real, and it goes.
The interesting part is the limit the authors put on their own reading. Fade out appeared to happen within two to four weeks. Then they say this: “since the second post-vacation measure was scheduled at least 2 wk after vacation in all 4 studies, we were not able to determine when beneficial effects on different variables exactly started to diminish and were erased.” So the first week back sits inside the gap in the measurements. The studies that make up the finding mostly looked again two weeks later, and found the effect had already gone.
Treat that gap carefully. The research stops short of saying that a well-run Monday preserves anything measurable. What it does establish is the shape of the thing: a small effect, with a short life and an unknown decay rate. That makes it a poor thing to spend three days of on a reconstruction of the past.
A second finding sits next to it. Pew Research Center surveyed 5,188 U.S. workers from February 6 to 12, 2023. “Some 46% of U.S. workers who receive paid time off from their employer… take less time than they are offered,” Pew reports. Among those who do not take it all, “a similar share (49%) say they’d worry about falling behind at work if they took more time off.” The fear is about the return, and it forms before anyone goes anywhere.
Notice who that sample is, though, because it matters here. Pew surveyed employees, explicitly not the self-employed. Every one of those workers had colleagues to fall behind relative to, and a job that carried on without them. If you own the firm, falling behind means something else, and in one way something worse. The work stopped when you left, and it waited for you alone. So the calculation on the return day is yours, and the answer to it arrives at the end of this series. It’s a question about who else can act, rather than about how fast you read.
The third day is the one that goes
Day one usually goes fine. It has a shape, you’re rested, and the reading gave you a map.
Day two brings the reply wave, plus the first meetings you moved to Tuesday because you were sensible enough to keep Monday clear.
Day three is where the week you missed meets the week you’re in. What you deferred on Monday is due. The replies to Monday’s replies are here. The two dates you decided to hold are looking tighter than they did. This is the return behaving the way returns behave, and all of it simply arrives at once. Wednesday afternoon is when people quietly conclude that the week off cost more than it was worth and put the next one off.
Naming it in advance is most of the defense. Expect the third day to be the heaviest day of the return. Keep it clear of anything you care about. Read how it feels as a Wednesday, and leave the vacation out of the verdict. If you moved the right dates on Monday, Wednesday is merely full. If you moved none, Wednesday is the day you find out which ones you should have.
What you are working from
Point has most of this day written down before you sit down, so the passes above are readings rather than reconstructions.
The first pass has the week’s shape ready, because the dates came through the absence as records. An ask buried three paragraphs into a Wednesday message became a dated task the moment it arrived, with the conversation still attached. What other people owe you is held apart from what you owe them. So “what falls due this week” and “what am I waiting on” are two lists you read. A thread you’re waiting on returns to you rather than going quiet, which matters most for the one that stalled on day two of your absence and would otherwise surface a month later.
The second pass is cheaper for the same reason. Moving three dates means knowing which three, and that’s a question about commitments rather than about messages.
The third pass starts from mail that’s already sorted. Each conversation got its short summary and its place in the order on the day it arrived. So sorting into live, overtaken and expired is mostly reading one-line accounts rather than opening threads. Anything you decide to hold until Thursday you set aside, and it comes back then. Some of what would have expired never got there. Where a scheduling thread was running, Point ran the back-and-forth itself, so a proposal that arrived on the Tuesday you were away may already have a time on it, rather than two slots that both passed.
Each kind of work carries its own setting, on a range whose two ends are suggest-only and fully handled. Every kind of work ships at the review setting in between. A setting further along the range is therefore one you moved deliberately. At the far end, that kind of work goes ahead while you’re away without waiting to ask you. Whatever went ahead left a plain-language entry in a log you read in sequence, and each entry carries its own reversal, which is what makes the return an inspection. Point can undo its own work. Mail that has already landed on another company’s server is past recall, on your first day back as on any other. Everything Point does has the rest.
What a good Monday does not fix
Three limits, said plainly, so you know what a day can give you.
A well-run return hands you information rather than hours. It shows you, early and cheaply, that the week is oversubscribed, and it lets you choose the subtraction rather than have Thursday choose it for you. That’s worth a great deal, and the week stays as full as it was.
The second limit is length. Parental leave, a medical absence, or three months out is a re-entry into an organization that moved on. The questions there are about what changed, who does what now, and where you fit. This chapter is written for the five-day version. Treating a twelve-week return as a large version of a five-day one is the main way people get it wrong.
The third limit is people. A good first day leaves the Wednesday you were away exactly as it was. If the honest summary of your week away is that four things needed a decision from a person, and the decision waited each time, then the fix is cover. That’s the subject the rest of this series is about.
The list the day hands you
By six o’clock on the first day back you’ve produced something you did not set out to produce, and it’s more valuable than the cleared inbox.
It’s a short list of the things only a Wednesday could have saved. The slot that both parties offered and nobody took. The client who waited four days, drew a conclusion, and has been polite about it ever since. The document that stayed where it was, with nothing watching for it. The decision that got made in your absence, slightly wrong, in a way that is expensive to unwind now. Four or five items, and every one of them shares a property. Each needed a moment that sat inside the absence, so reading on the return morning was always going to be too late.
That list is a specification, and it’s addressed backward, to the week before you leave rather than the week you come back to. Every item on it names something that needed to be able to happen while you were gone.
Each of those items is an argument for cover. That’s what covering the inbox while you are on leave is built from, and it’s where this guide goes from here.