Going on leave should not require you to spend your last afternoon answering frantic messages, writing a novel-length handover, or trying to transfer your entire job into someone else’s head. A useful handoff does something simpler: it tells the next person what matters, what can wait, what could go wrong, and where to look if they need context.
What should a work handover include before leave?
A work handover before leave is a short, usable record of the responsibilities another person may need to handle while you are away. It should help a backup colleague find the latest information, make permitted decisions, spot problems early, and know when to escalate. The aim is continuity—not a complete history of everything you do.
At a minimum, give the covering colleague five things:
- Coverage: your last working day, absence dates, expected return date, primary backup and secondary contact.
- Work: what must be completed, what only needs monitoring, and what can wait.
- Ownership: one accountable person for each task, with the specific next action and due time.
- Authority: decisions the backup may make, those that need a named approver, and the boundaries recorded in company policy.
- Source of truth: links to approved files, status boards, message threads and escalation instructions.
Ask the backup to review the handover before your leave begins. A document nobody has accepted is not a completed transfer.
Step 1: Sort work into four priority buckets
Start with the recurring obligations and open requests that might affect others during your absence. You do not need to list every small administrative task. Categorizing the work makes it clear which items deserve attention and which should not interrupt the backup unnecessarily.
| Bucket | How to handle it | Practical example |
|---|---|---|
| Must happen | Complete on a specific date; name the owner, outcome and evidence. | Send the approved weekly supplier summary by Thursday noon. |
| Delegated approval | Act only within documented approval authority; otherwise escalate. | Prepare the billing backup, but route approval to the authorized team lead. |
| Watchlist | Check at an agreed time and act only when a defined trigger occurs. | If a rate sheet is still missing at 11 AM, chase the supplier. |
| Can wait | Defer with a known return date or approved holding response. | Archive old project notes after the employee returns. |
These are illustrative tasks. Your team’s obligations may differ. The bucket does not change anyone’s delegated authority: a “must happen” task can still require approval from somebody else.
Step 2: Build a handover task matrix that someone can actually use
For every active item, write down the work in a format that can be scanned during a busy day. A useful task line includes the deliverable, due date and time zone, backup owner, next action, source file, completion evidence and escalation trigger.
| Task | Owner and due time | Next action | Escalation |
|---|---|---|---|
| Weekly supplier summary | Morgan · Thu 29 Oct, 12:00 | Confirm signed figures, send approved report, save sent copy. | Ask Jordan if figures remain unapproved at 10:00. |
| Client status note | Morgan · Tue 27 Oct, 15:00 | Check approved milestones and send via the agreed contact list. | Escalate material changes in promised delivery dates. |
| Missing supplier rate sheet | Morgan · Review Wed 28 Oct, 11:00 | Contact supplier if the current sheet is still missing. | Ask Jordan for a decision if still unavailable at 13:00. |
Fictional example for explanation only. Use your organization’s actual owners, dates, recipients and approved information sources.
Avoid vague entries such as “follow up on suppliers.” Write the next concrete action: “Ask the supplier for the approved October rate sheet by Wednesday 11 AM; record the response in the project folder.” This gives the backup a task they can finish or escalate.
Step 3: Name your backup and document approval boundaries
A backup is not necessarily an approver. The colleague covering your inbox may be able to gather information, acknowledge requests and prepare documents without being authorized to approve pricing, spending, external commitments or changes to client scope.
Record who holds authority for each sensitive decision and how to contact them through an approved business channel. Where relevant, reference the written delegation or policy. Do not invent a spending limit or presume that acting as a backup gives someone new authority.
Agree on the escalation trigger in advance. For example: “If corrected supplier pricing is unavailable by 1 PM, contact the authorized approver before confirming any figure externally.” If the approver cannot be reached, follow the organization’s backup or management escalation path instead of treating silence as permission.
For urgent situations, see How to Handle an Urgent Work Request When a Manager Is Unavailable.
Step 4: Put the current documents in one approved location
Do not make the covering colleague reconstruct a project from old chats. Link to the latest approved source document, task board, decision log, relevant email thread or shared folder. Note which file is authoritative if several versions exist.
Keep access permissions consistent with your company policy. Share the document or a properly restricted link, not a collection of passwords, confidential client data or sensitive employee details pasted into the handover. If access is needed, request it through the approved IT or document-owner process before the leave starts.
For decisions that may be questioned later, link to the work decision log rather than repeating long explanations in multiple documents.
Step 5: Run a focused 15-minute handover briefing
A briefing should confirm that the new owner understands the active work. It should not be a tour of every project your team has ever handled. A practical agenda is:
- Minutes 0–3: Confirm coverage dates, the most important outcomes and any deadlines that cannot move.
- Minutes 3–7: Check every “must happen” item, its owner, source document and proof of completion.
- Minutes 7–11: Review authority boundaries, watchlist triggers and the escalation chain.
- Minutes 11–15: Ask the backup to explain the next actions, resolve access gaps and agree on the next check-in.
Before finishing, ask the backup: “Which decision would you need help with first? Can you find the latest approved file? What will you do if the critical input does not arrive?” These questions expose uncertainties more effectively than simply asking, “Any questions?”
Step 6: Set a clear out-of-office response and stakeholder expectations
Tell the people who rely on you who is covering critical work and how requests will be handled. Avoid promising that your backup will respond instantly unless that service level has been agreed. An out-of-office message should share only approved business contact routes.
Example out-of-office email
Thank you for your message. I am away from 26–30 October and expect to return on 2 November.
For ongoing project requests, please contact the agreed team coverage address. For decisions requiring management approval, the team will route the request to the authorized approver.
I will respond to other messages after I return.
Illustrative wording. Replace the dates and contact arrangements with real approved details, and follow your organization’s response-time policy.
A separate handover email to your backup can be even shorter:
Subject: Leave coverage — 26–30 October | key tasks and escalation
Hi Morgan, the approved handover document is in our shared operations folder. The two must-do items are the Thursday supplier summary and Tuesday client update. The rate sheet is on watchlist. Jordan retains approval authority for billing and material pricing changes. Please confirm that you can access the files and that the dates and escalation contacts are clear before Friday. Thank you.
Step 7: Prepare for your return, not just your departure
A good handover works in both directions. Ask the covering colleague to keep a brief record of completed work, decisions, items waiting for others, new risks and changes to important source documents. Agree on where these notes belong, so the information does not disappear in separate private messages.
On your first working day back, request a short return briefing: what was completed, what changed, which decisions were made, and what needs attention next. Record any follow-up owner and date. Where responsibility changes again, make that transition explicit so two people do not assume the other is handling the same task.
Taking over an active project: the first 48 hours
The same method works if you are the person receiving a project rather than the person going on leave. During the first two working days, focus on verified current context: intended outcome, next milestone, latest approved files, open decisions, critical stakeholders, blockers and the people who can authorize changes.
Compare the written handover with the actual project board and ask someone who knows the work to correct important gaps. Avoid redesigning the entire workflow until you understand its commitments. For a more detailed process, read How to Take Over a Project Midstream Without Losing Context.
Common handover mistakes to avoid
- One huge document with no priorities: A backup should quickly find what is urgent, conditional or safe to defer.
- No named owner: “The team will handle it” can leave everyone thinking someone else is responsible.
- Deadline without lead time: Include preparation, review and approval checkpoints—not just the final due date. A recurring deadline calendar can help.
- No authority boundaries: Coverage does not authorize new commercial, legal or financial commitments.
- Outdated or inaccessible files: Check permissions and source-of-truth links before leaving.
- No return-to-work plan: Completed actions and newly opened issues need to flow back to the original owner.
Need an editable leave handover template?
If you would rather start with a prepared document than format your own tables, the Leave Handoff & Project Takeover Kit includes an editable Word handover document, priority and approval sections, practical email scripts, a 20-point project takeover checklist, a printable reference and fictional completed examples.
See the Word/PDF Kit — US$5.99 →
Digital download. DOCX templates are editable; the PDFs are references, not fillable forms. Templates do not replace your organization’s approval or privacy policies.
Frequently asked questions about leave handovers
How far in advance should I prepare my handover?
Start early enough to identify missing approvals, access permissions and backup coverage before your last working day. For complex work, arrange an earlier review rather than relying on a briefing at the end of the day.
What is the difference between a handover checklist and a handover document?
The checklist verifies that key preparations are complete. The handover document contains the actual owners, actions, due dates, links, risks and escalation rules that the next person needs.
Should I include every task I normally perform?
No. Prioritize work that must happen while you are away, decisions that may arise, conditional risks and anything another person must locate quickly. Work that can wait can be marked as such.
Can my backup approve urgent payments or client changes?
Only if they already have the required written or policy-based authority. Otherwise, identify the approved decision-maker and escalation route.
How should I share confidential or sensitive information?
Use approved systems and permissions. Share links where possible, do not paste passwords into the handover, and follow your organization’s privacy and retention policies.
How do I know the handover is complete?
Confirm that the backup accepted the responsibilities, can access the sources, knows the deadlines, understands approval limits, and can explain what to do when an expected input or approver is unavailable. Plan a return briefing as well.
Editorial note: The scenarios and sample messages above are fictional illustrations, not firsthand client case studies or evidence of software testing. Customize the process for your organization.
Browse the Office Logs & Trackers hub and Workplace Scripts hub for related practical guides.