The desk you leave behind

The planning that gets a multi-day conference approved is almost entirely about the trip itself — the business case, the agenda, the travel dates. What rarely gets the same attention is the desk left behind for those same days, and that gap is why so many people come back from a good conference to a bad week. A submission deadline doesn’t pause because you’re at a podium in another city. Neither does a colleague waiting on a sign-off, or a question that only you can answer landing in an inbox nobody else is reading. None of that is a reason to decline the trip. It is a reason to plan the coverage with the same deliberateness as the travel.

Decide what actually can't wait

Most of what lands in a working inbox over three or four days can wait three or four days, and treating all of it as urgent is what turns “checking email once a day” into checking it constantly from a hallway between sessions. Go through what's realistically live during the trip — an active submission, a decision someone else is blocked on, a deadline that falls mid-conference — and name those specifically. Everything else gets a default answer: it waits until you're back, and the person covering for you is not expected to improvise one. The same instinct that makes pre-conference reading worth fifteen minutes applies here: a short, specific list beats a long vague one every time.

Hand off the short list, not your whole inbox

Whoever is covering for you does not need delegate access to everything you own; they need the short list from above, with enough context to act on each item without reconstructing the background themselves. That means naming who it is specifically — not “the team” in general, which usually means no one in particular when the moment actually arrives — and giving them a specific question they'd need an answer to before saying yes or no on your behalf. If something on the list is genuinely only answerable by you, say so plainly: the honest answer is sometimes “this one actually waits for me,” and naming that in advance is more useful to the person covering than discovering it live.

Have the conversation before the trip, not during it

This works best as a short, scheduled conversation the week before departure — not a Slack message sent from the gate, which tends to arrive after the covering colleague has already made other plans for that week. Treat it the way you'd treat the business case for the trip itself: specific, written down, and agreed to by the person taking it on, not assumed. A colleague who knows exactly what they're covering, and what they aren't, can actually do the job; one who finds out by being copied on an urgent email mid-conference usually can't.

What you come back to is part of the plan

The flip side of a good coverage plan is a bounded return: you know what was handled while you were out, what's genuinely still waiting, and what quietly resolved itself without needing you at all. Build in the first morning back as recovery time rather than double-booking it the way the rest of the week gets booked — a trip report and a readout both take real attention, and neither happens well wedged between two meetings you didn't plan for. The trip doesn't end when the flight lands; it ends when the desk you left is caught up, and that's worth planning for on the way out, not discovering on the way back.