In this guide 8 sections
You have written the handover, set your out-of-office reply and closed the laptop. Then a message arrives: “Quick question. What are we supposed to do with this?”
Sometimes a genuinely new problem appears. But a long document can still leave the important things missing: who is covering the work, what they can decide, where to find the current version and which problems can wait until you return.
The aim is not to predict every possible question or finish every task before taking leave. It is to make the next reasonable action possible without you. Here is a practical way to do that, including a fictional example you can adapt.
Start with what actually needs coverage
Do not begin by documenting your entire job. Make three groups: work that must move during your absence, work that can wait, and work whose timing or ownership needs a decision. Put dates beside anything described as urgent. “Important” and “needs action while I am away” are not the same thing.
For each item that must move, name the consequence of waiting. A customer deadline on Wednesday needs different coverage from an internal draft that someone would prefer to see on Wednesday. If the consequence is unclear, ask before turning your colleague into the default owner.
Coverage also needs capacity. Writing somebody's name in a document does not create their agreement or spare time. Discuss the proposed cover with them and your manager. If nobody has capacity, the unresolved question belongs in that conversation: reduce the scope, move the date or arrange different cover. Our guide to asking what should move when more work arrives offers wording for that trade-off.
Write for the next decision, not the full history
Choose one live item and imagine the covering colleague opening it on the first day you are away. What will they need to understand within a couple of minutes?
Start with the outcome, current state and next action. Then add the decision they might face. For example: “The draft is complete except for the delivery estimate. If Operations confirms Friday delivery by Tuesday noon, send version 3 for approval. If not, ask Priya whether to move the launch or remove that promise.”
This is more useful than “Launch proposal: see folder.” The folder supplies evidence; the note explains how that evidence changes the next step. Keep enough history to explain a constraint, but do not make someone reconstruct a decision from six meeting notes.
Two company examples illustrate parts of this approach. GitLab's support time-off buddy guidance[1] describes agreeing expectations and leaving internal notes with status and expected next steps. Atlassian's out-of-office guide[2] describes bringing dates, contacts and useful links together. Those are examples of their practices, not rules every workplace must follow. The template below is CareerFood's own practical synthesis.
Give responsibility a boundary
Separate three things: who notices an issue, who does the work and who can approve a change. One person may fill all three roles, but do not assume that they do.
“Alex is covering” could mean checking messages, making delivery decisions or simply passing a problem to the right person. Spell it out: “Alex checks the shared inbox once each working day and handles routine updates. Priya approves changes to scope, price or delivery dates.” Agree this with the people concerned, rather than presenting it as a completed arrangement.
If you do not have authority to delegate a decision, say so and get the appropriate owner involved. For specialist, safety-critical or regulated work, use your organisation's required handover and escalation procedures. A general career article is not a substitute for them.
Use a small handover template
Copy these fields for each item that genuinely needs coverage. A paragraph per field is enough if it tells the covering person what to do. Use approved systems and link to the current source rather than making unnecessary copies.
Item and outcome: What is this, and what result are we trying to achieve?
Status and current version: What is complete, what is unresolved, and where is the authoritative file or record?
Next action and trigger: What happens next, by when, or when which event occurs?
Agreed cover: Who has agreed to do that action? Who approves anything outside their remit?
Decision boundary: What can they decide themselves, and what must go to someone else?
If blocked: Who should they contact, what context should they provide, and what can safely wait?
Return point: When will you pick this up again, and where should changes be recorded?
Do not paste passwords, access tokens or unnecessary personal information into a handover. Check access through your organisation's approved process. A link that only works for you is not usable cover.
A fictional example: a proposal due during leave
Imagine Maya is away from Monday to Friday. A customer proposal needs internal approval on Wednesday, but one delivery estimate is still missing. Here is the substance of a usable handover, after the people named have agreed their roles.
Outcome and status: “Get the Northbank proposal ready for Priya's approval by Wednesday at 11:00. Version 3 in the shared proposal record has the agreed scope and pricing. The delivery date is the only open point. This is an internal approval deadline, not permission to send it to the customer.”
Next action: “Alex checks for Operations' estimate on Tuesday morning and updates the delivery section. The estimate request and latest reply are linked in the record. Alex can correct the wording to match the confirmed estimate, but cannot promise a date that Operations has not confirmed.”
If blocked: “If there is no estimate by Tuesday noon, Alex asks Priya to choose between moving the proposal deadline and removing the delivery-date commitment. Include the request date, latest reply and consequence of waiting. If Priya is unavailable, follow the team's agreed deputy arrangement. Do not assume Maya will answer during leave.”
Return point: “Record the decision and final version in the proposal record. Maya reviews it on the following Monday. Routine questions that do not affect Wednesday's decision can stay in that record until then.”
The useful detail is not the fictional names or deadlines. It is the distinction between an action, an approval and a fallback. Adapt those to your actual work. If getting the missing estimate is already difficult, ask for a specific kind of help before your final afternoon.
Test the handover before you leave
Ask the covering colleague to open the links and talk through one likely situation. “The estimate has not arrived. What would you do?” is a better test than “Does this all make sense?”
Listen for missing context, blocked access and decisions they did not know they were expected to make. Fix the note where the question arose. Do not turn the test into a memory exercise or another large meeting. One realistic case can reveal a gap that a polite acknowledgement misses.
Then confirm the arrangement with the relevant people: who is covering, what can wait and where updates belong. If coverage is still unresolved, make that visible to your manager before leaving rather than disguising it with “message me if anything comes up”.
Make your availability clear, then close the loop
Keep your out-of-office message short: your dates, the appropriate contact or team route, and any necessary boundary about when you will respond. Avoid broadcasting internal project details to external senders. Make the message match the cover you actually agreed.
This method does not override your contract, formal on-call rota or workplace policy. If your role includes a specific availability requirement, clarify the arrangement with the appropriate person. Do not casually promise open-ended availability to compensate for a missing decision owner.
On return, read the recorded changes before asking everyone to repeat the week. Confirm what is still open and thank the person who covered. Save useful outcomes in your work record, without treating routine cover as somebody else's invisible extra job.
Your next step: fix one weak handover
Choose one item that might need attention while you are away. Write only its current state, next trigger, agreed owner and fallback. Open its links as the covering person would. Then ask them to explain the next decision back to you.
If you cannot name the owner or fallback, your next step is an agreement, not a longer document.
Sources and further reading
Optional source checks. External sources open in a new tab.