Returning from leave: reading the first week back honestly
· 6 min read
The first week back is disorienting in a specific way: it feels unproductive while also feeling full. You are busy from Monday morning and by Friday it is hard to name anything you finished.
Both impressions are usually accurate, and a record of the week explains why they coexist.
What the first week actually contains
The shape is consistent across most kinds of work.
Correspondence dominates. Mail and messaging take a far larger share than a normal week, because a backlog arrived while you were away and it all needs at least a decision.
Context reconstruction takes longer than anyone budgets for. Reopening a project means remembering where it was, which is a real cost and an invisible one, because it does not look like work while it is happening.
Actual production is small. The blocks of sustained work that normally carry the week are squeezed between the other two.
Seeing that written down is more useful than it sounds, because the alternative reading is that you have come back slow or lost your edge. The record says something more accurate: the week was full of a different kind of work, and that kind of work has to happen.
Why the guilt is misdirected
The unproductive feeling comes from comparing this week against a normal one on the wrong measure. Judged by output, it is poor. Judged by what it is for, catching up and reloading context, it may have gone perfectly well.
A record makes the comparison honest, because you can see that six hours went into correspondence rather than that six hours vanished.
There is a second, quieter finding worth watching for. Some people work more in the first week back than in a normal week, driven by a sense of owing something for the absence. That is worth catching early, because the pattern of returning from rest by immediately overworking undoes the rest.
What to do with the week
Do not schedule anything demanding on day one. The morning is going to be correspondence regardless of what is planned. Planning something else produces a failure that was structurally guaranteed.
Batch the backlog rather than working through it. Two long passes are cheaper than a day of interruption. Everything in that backlog has already waited; none of it needs answering within the hour.
Pick one substantive thing for the week. Not a normal load. One thing that gets finished restores momentum better than five things half-started.
Expect the second week to be normal. If it is not, the problem is the workload rather than the return.
The measurement that helps most
The comparison against a normal week is what makes any of this useful, which means the record has to predate the leave.
That is the argument for automatic tracking rather than starting a log on the way back: you cannot construct a baseline retrospectively, and the first week back is exactly when nobody has the appetite to start maintaining anything.
Punchcard records the frontmost application by name and prints a receipt of the day at the closing time you set. The receipts from before the leave are the baseline, the ones from the week back are the comparison, and neither required you to remember anything.
The comparison to make is the distribution rather than the total. If mail was fifteen percent of a normal week and forty percent of this one, that is the whole explanation for how the week felt, and it is the sort of thing that is obvious in hindsight and invisible at the time.
Counting the days covers what a run of receipts shows, and tracking a sabbatical, a job search or a quiet month covers longer periods away from a normal pattern.
The leave itself
Worth a sentence, because it is the more important half.
A record that runs while you are away shows whether you were away. Ninety minutes on a Wednesday of annual leave is a data point, and a week of them means the leave was not leave.
That is not an argument for policing yourself on holiday. It is an argument for knowing, because the sense of having had a break and the fact of having had one diverge easily, and only one of them is visible in a record. A receipt for a day off, and why it is worth printing covers this directly.
Questions
Should I check mail before returning, to reduce the backlog? It reduces Monday’s volume and extends the leave into the days before it. Most people find the trade is not worth it; the backlog is finite and a genuine break is not recoverable afterwards.
How long should the first week back take to normalise? Commonly one week for a short absence and two for a long one. If the third week still looks like the first, the issue is workload rather than return.
My record shows less time than I felt I worked. Common after leave, and usually accurate. Fragmented, low-focus work feels longer than it is. The days are full of small pieces rather than long stretches.
Is it worth keeping the tracker running during leave? Yes, precisely because a blank receipt is the useful outcome. A record with nothing on it is evidence you actually stopped.