Work Handover Before Vacation: A Template and Filled Example

A useful vacation handover tells the person covering you what is open, what happens next, when it matters and who can make the necessary decision. Start with work that will need attention while you are away. A long history of everything you have done is rarely the document a colleague needs to act tomorrow.

Use your team's existing system where possible. The format below is an original Qerano template and fictional demonstration, not a real company record or a universal employment procedure. Follow your employer's rules for leave, information handling and coverage.

Vacation Handover Template

Copy this blank document into your team’s approved workspace and replace the bracketed fields. It is free to use and needs no registration. Repeat a task block for each open item.

You can also select the text below and copy it manually.

Prepared by: [Your name]
Vacation dates: [Start date] to [End date]
Expected return: [Return date]
Last updated: [Date]
Covering colleague: [Colleague]
Backup contact: [Name / approved contact channel]

TASK 1
Task / Project: [Task name]
Current status: [Completed work / outstanding work]
Next action: [Specific next step]
Deadline: [Date, time and time zone / can wait]
Responsible person: [Agreed colleague]
Blockers / Risks: [Missing input, risk or none]
Escalation contact: [Name / role and when to contact]
Relevant links / Documents: [Approved shared links]
Important decisions pending: [Decision and authorized approver]
Additional notes: [Context / access requirements]

TASK 2
Task / Project: [Task name]
Current status: [Completed work / outstanding work]
Next action: [Specific next step]
Deadline: [Date, time and time zone / can wait]
Responsible person: [Agreed colleague]
Blockers / Risks: [Missing input, risk or none]
Escalation contact: [Name / role and when to contact]
Relevant links / Documents: [Approved shared links]
Important decisions pending: [Decision and authorized approver]
Additional notes: [Context / access requirements]

TASK 3
Task / Project: [Task name]
Current status: [Completed work / outstanding work]
Next action: [Specific next step]
Deadline: [Date, time and time zone / can wait]
Responsible person: [Agreed colleague]
Blockers / Risks: [Missing input, risk or none]
Escalation contact: [Name / role and when to contact]
Relevant links / Documents: [Approved shared links]
Important decisions pending: [Decision and authorized approver]
Additional notes: [Context / access requirements]

Decide what needs to move, finish or wait

Review your current tasks against your absence dates. Mark each as something you can finish before leaving, something a named colleague will cover, something the team agrees to pause, or a decision your manager must resolve. Do not label everything urgent merely because you are about to be away.

GitLab's published support-team guidance illustrates the distinction: it asks staff to arrange role coverage and consider whether an open ticket should pause or be handed to someone else. Those are GitLab's operational practices, not leave entitlements or rules for every workplace. [1]

A shared document is useful for a small set of tasks. If the work already lives in a tracker, link to the current records and add an absence overview instead of maintaining two conflicting versions. A short walkthrough can clarify a complicated case; it should leave a written next action and owner behind.

Build a handover someone can act on

Record the absence dates, return date, document owner and last-updated date at the top. Then use the fields that make the work transferable:

Field	What to put in it
Task	A recognizable task name and link to its current record.
Status	What is actually complete and what remains; distinguish “draft ready” from “approved.”
Deadline	Date, time and time zone if timing matters. Say whether it is confirmed or provisional.
Next action	One observable action: send the approved file, request a decision, or check for a reply.
Owner	The person who has agreed to cover it; list decision authority separately if different.
Blocker	The missing input or approval, who can supply it and when to check again.
Priority	Why it needs attention during your absence, or why it can wait.
Relevant contact	The right internal role or authorized contact channel, not a dump of private details.
Notes	Current file location, access requirements and the condition for escalation.

“Continue the project” is too vague as a next action. “Ask the approver about version 3 by Tuesday; do not send it externally until approved” tells the colleague where to start and what not to assume.

A filled example: three tasks, two different kinds of urgency

Everything in this example is fictional. The dates, people and folders exist only to demonstrate the handover. There are no real clients, credentials or corporate documents.

Absence: 12–16 October 2026. Return: 19 October. Updated: 9 October. Working location: team-approved shared tracker, “October coverage.” The covering colleagues have agreed to the assignments shown.

Scroll horizontally to see all columns.

Task	Status	Deadline	Next action	Covering owner
Weekly project update	Draft ready; approval missing	13 Oct, 12:00, team time zone	Ask Alex to approve version 3; send only the approved version.	Sam
Supplier delivery check	Confirmation requested	Review on 14 Oct; delivery date not confirmed	Check the supplier reply and update the shared record.	Lee
Archive completed folders	Files identified	No deadline during absence	Leave queued until the author returns.	Original owner on return

The second table adds the context that the task list alone cannot show:

Scroll horizontally to see all columns.

Task	Blocker	Priority and relevant contact	Notes / escalation condition
Project update	Alex's approval	Time-sensitive; Alex is the internal approver.	Version 3 in the shared tracker. If approval is missing on the morning of 13 Oct, ask the team lead to decide the next step.
Delivery check	Supplier reply	Needs a check, not automatic escalation; use the authorized supplier contact in the record.	If the reply proposes a date that conflicts with the project schedule, ask the project owner to decide; do not promise acceptance.
Archive	None	Can wait; original owner.	Do not delete or reorganize shared files during coverage.

The important distinction is between doing the next step and authorizing the outcome. Covering a task does not automatically grant purchasing, approval or external-commitment authority. Ask your manager to settle uncertainty before you leave.

Check access with the colleague, not just the link

Ask the covering person to open the linked record and identify the next action. A document can look complete while its attachments are unavailable or a named owner has never agreed to cover the work.

Use approved access-sharing procedures. Do not put passwords, personal authentication codes or confidential customer information in a general handover. Link to information only where the recipient is authorized to see it. If a required permission is missing, resolve it through your normal team process.

A specific example of explaining context to a colleague can also support a later transferable-skills inventory. A salary-review evidence record has a different purpose: it explains contributions, rather than replacing the operational handover.

Send a short message with the decision points

An adaptable example, using the fictional document above:

“I will be away 12–16 October and back on the 19th. The current handover is in our shared tracker under ‘October coverage.’ Sam is covering the project update; Alex's approval is needed before it goes out on the 13th. Lee is checking the delivery reply. The archive task can wait. Please confirm that the links open and the coverage is workable before I leave. Unresolved priority or approval questions go to the team lead.”

Agree your availability during leave according to your workplace arrangements; do not offer round-the-clock personal contact as the default escape hatch. Update your absence message and calendar to point to the agreed contact. If a professional course affects your schedule too, arrange that absence separately rather than assuming vacation coverage includes it.

When you return, ask what changed, read the current records and confirm which tasks come back to you. Keep the old handover as a dated record where your team's policy permits; do not treat its old status as current. More work and learning decisions are in Career & Money.

Vacation Handover Email Template

You can also select the text below and copy it manually.

Subject: Handover for my vacation — [Start date] to [End date]

Hi [Recipient],

I will be away from [Start date] to [End date] and expect to return on [Return date]. The handover document is here: [Approved shared link / location].

Open tasks:
- [Task]: [Next action] by [Deadline]; agreed owner: [Colleague].
- [Task]: [Next action] by [Deadline]; agreed owner: [Colleague].
- [Task that can wait]: resume on [Date / agreed condition].

[Covering colleague] is the main contact during my absence; [Backup contact] is the backup. For urgent issues, contact [Escalation contact] via [Approved channel] when [Escalation condition]. Decisions about [Pending decision] need approval from [Authorized approver].

Please confirm that you can open the linked documents and that the coverage is agreed.

Thank you,
[Your name]

Before You Leave: Final Handover Checklist

All open tasks are listed.
Each task has a specific next action.
Deadlines and priorities are clear.
Covering colleagues have agreed to their responsibilities.
The covering colleague has confirmed access to the documents.
An escalation contact and conditions are recorded.
The manager knows which decisions remain open.
The handover message has been sent.

Sources

GitLab. Support Team Member Time Off. Publication date not provided. Accessed: 2026-10-07.