How to Do a Handover in an Office: 12 Steps

An office handover is one of those workplace tasks that sounds simple until someone forgets to mention the password-protected spreadsheet, the client who only answers emails before 9 a.m., or the printer that “works fine” as long as nobody looks directly at it. Whether an employee is leaving, taking vacation, moving to another department, or handing off a project, a smooth handover keeps business moving without drama, confusion, or frantic “Do you know where this file is?” messages.

A good office handover is more than a polite goodbye. It is a structured transfer of responsibilities, documents, deadlines, relationships, systems, and context. Done well, it protects productivity, reduces mistakes, supports the incoming person, and helps the departing employee leave on a professional note. Done poorly, it becomes a scavenger hunt with calendar invites.

This guide explains how to do a handover in an office in 12 practical steps, with examples, checklists, and real-world experience to help you create a process that actually works.

What Is an Office Handover?

An office handover is the process of transferring work responsibilities from one person to another. It may happen when an employee resigns, goes on parental leave, takes a long vacation, changes roles, or completes a project. The goal is to give the next person enough information, access, documentation, and confidence to continue the work without unnecessary disruption.

A strong handover usually includes current tasks, recurring duties, important contacts, deadlines, files, passwords or access instructions, pending decisions, known risks, and practical tips that are not obvious from official documents. In plain English: it tells the next person what to do, where to find things, who to talk to, and what tiny office dragons to avoid.

Why a Proper Handover Matters

Office handovers protect business continuity. When key knowledge exists only in someone’s head, the company becomes vulnerable the moment that person leaves the desk. A clear handover helps prevent missed deadlines, duplicated work, unhappy clients, compliance issues, and awkward internal confusion.

It also supports employee experience. The person leaving feels respected because their work is being handled responsibly. The person taking over feels supported instead of abandoned in a maze of folders named “Final_FINAL_v7.” Managers gain visibility into work status, and teams avoid unnecessary stress.

How to Do a Handover in an Office: 12 Steps

1. Start the Handover as Early as Possible

The best handovers begin before the final week. If an employee is leaving the company, start as soon as the departure date is confirmed. If someone is going on leave, begin at least two to three weeks in advance when possible. For complex roles, leadership positions, or client-heavy jobs, a longer timeline may be needed.

Early planning gives the outgoing employee time to document work properly, answer questions, clean up files, and introduce the incoming person to key contacts. It also gives the manager time to identify gaps. Waiting until the last day creates a handover that sounds like, “Everything is in the shared drive,” which is technically a sentence but not a strategy.

2. Clarify the Purpose and Scope of the Handover

Before writing anything, define what the handover needs to cover. Is the person handing over an entire role, one project, a temporary workload, or a set of client accounts? Different situations require different levels of detail.

For example, a vacation handover may focus on urgent tasks, backup contacts, and deadlines during the absence. A resignation handover should include deeper documentation, recurring responsibilities, system ownership, client history, and long-term risks. A project handover should include deliverables, status, stakeholders, budgets, timelines, open issues, and final approvals.

Clear scope prevents both under-documentation and over-documentation. Nobody needs a 40-page guide to watering the office plant, unless the plant is legally part of the finance department.

3. Create a Handover Checklist

A checklist keeps the handover organized and reduces the chance of missing important details. It should include sections for tasks, files, tools, contacts, deadlines, meetings, access needs, risks, and sign-offs.

A basic office handover checklist may include:

• Daily, weekly, monthly, and quarterly responsibilities
• Current projects and status updates
• Important deadlines and deliverables
• Key internal and external contacts
• Shared folders, documents, templates, and reports
• Software, tools, dashboards, and permissions
• Recurring meetings and calendar notes
• Open problems, risks, and pending decisions
• Company property, accounts, and access changes
• Final review and approval by the manager

The checklist should be simple enough to use but detailed enough to be useful. Think “clear map,” not “ancient scroll.”

4. List All Current Responsibilities

The outgoing employee should write a complete list of responsibilities, including routine tasks that may seem obvious. Everyday work often becomes invisible to the person doing it. That is why handovers frequently miss small but important duties, such as sending weekly reports, approving invoices, updating dashboards, or checking a shared inbox.

Divide responsibilities by frequency: daily, weekly, monthly, quarterly, and occasional. Then explain what each task involves, why it matters, and what happens if it is missed.

For example, instead of writing “send sales report,” write: “Every Monday before 10 a.m., export the sales report from the CRM, check totals against the dashboard, and email it to the regional managers. This report is used in the Tuesday leadership meeting.” That level of context turns a task into a usable instruction.

5. Document Ongoing Projects Clearly

Every active project should have a short status summary. Include the project goal, current stage, next steps, deadlines, stakeholders, blockers, documents, and decisions already made. This prevents the incoming person from reopening old debates or accidentally undoing progress.

A helpful project handover summary may include:

• Project name and purpose
• Current status
• Completed work
• Upcoming milestones
• Responsible people
• Key documents and links
• Budget or resource notes
• Risks and unresolved issues
• Recommended next action

Specific examples are powerful. “Client approved design direction on April 15; legal review is pending; do not send final contract until procurement confirms vendor code” is much better than “Contract stuff still happening.”

6. Organize Files, Folders, and Templates

A handover can collapse quickly if the files are messy. Before transferring work, clean up shared folders, rename documents clearly, archive outdated versions, and place important files where the next person can find them.

Use consistent file names such as “Client_Name_Project_Status_April_2026” instead of “new one use this maybe.” Group documents by category: reports, templates, contracts, meeting notes, budgets, presentations, and reference materials.

If your office uses cloud tools, make sure permissions are correct. The incoming person should not need to request access to every document one by one. That turns the first week into a digital obstacle course.

7. Identify Key Contacts and Communication Preferences

People are part of the handover too. List important internal and external contacts, their roles, what they handle, and how they prefer to communicate. Include clients, vendors, managers, cross-functional partners, finance contacts, IT support, HR contacts, and anyone else who helps the work move forward.

Good contact notes include practical details. For example: “Maria in finance approves urgent vendor payments; email first, then message her if the deadline is same day.” Or: “Client prefers one weekly summary instead of multiple small updates.”

These details save time and help the incoming person build trust faster. They also prevent accidental communication mistakes, such as calling someone who has made it spiritually clear that they are an email-only human.

8. Transfer System Access and Security Information Properly

Access management is a serious part of the office handover. The incoming person may need permissions for shared drives, project management tools, email groups, CRM systems, finance platforms, reporting dashboards, calendars, or communication channels.

Never share passwords casually in a document or chat message. Instead, follow company policy by using approved password managers, access request forms, single sign-on tools, or IT-managed permissions. If the outgoing employee is leaving, IT should remove or adjust access according to the offboarding process. This protects company data and reduces security risk.

The handover document should state what systems are used, who owns access approval, and what permissions the successor needs. It should not expose sensitive credentials. In other words, write the treasure map, not the treasure itself.

9. Schedule a Handover Meeting

A written handover is essential, but a live meeting adds context. Schedule a meeting with the outgoing employee, incoming employee, and manager. For larger roles, include key stakeholders or team leads.

Use the meeting to review the handover checklist, walk through active projects, explain priorities, answer questions, and confirm ownership. The outgoing employee should highlight the most important risks, not read every line of the document like a bedtime story for exhausted professionals.

For complex roles, consider multiple sessions: one for daily operations, one for projects, one for clients, and one for tools or reporting. Recording the session may also help, if company policy allows it.

10. Arrange Shadowing or Training Time

Some work is easier to learn by watching than by reading. If timing allows, schedule shadowing sessions where the incoming person observes the outgoing employee completing important tasks. This is especially useful for reporting workflows, client calls, software processes, approvals, and tasks with many small steps.

Shadowing can work both ways. First, the incoming person watches. Then they try the task while the outgoing person observes and corrects mistakes. This “watch, do, review” approach catches gaps before the handover is complete.

For example, a written note might say “update the monthly dashboard,” but shadowing reveals that three numbers must be checked manually because the export sometimes duplicates canceled orders. That is the kind of detail that saves future headaches.

11. Confirm Priorities, Risks, and Pending Decisions

Not all tasks are equal. A good office handover explains what matters most. Identify top priorities for the first day, first week, and first month after the transition. Also list known risks, blockers, sensitive relationships, and decisions waiting for approval.

Use plain language. For example: “The renewal deadline for Client A is the highest priority this week. If legal does not approve the contract by Wednesday, escalate to the operations director.” That gives the new owner a clear action path.

Risk notes should be honest but professional. Do not use the handover document to write a workplace novel titled “Everyone Who Annoyed Me: A Memoir.” Focus on facts, context, and recommended actions.

12. Get Final Sign-Off and Keep the Document Updated

The manager should review the handover before the transition is complete. This final sign-off confirms that responsibilities, files, access, contacts, and risks have been covered. It also gives the incoming person a chance to ask final questions.

After the handover, store the document in a shared, approved location. Do not let it disappear into someone’s personal desktop folder. The document can become a living resource for future onboarding, training, audits, or emergency backup planning.

After one or two weeks, the manager should check in with the person who took over. Ask what was missing, what was unclear, and what should be improved. A handover process gets stronger each time the team learns from it.

Office Handover Document Template

Use this simple structure to create a practical handover document:

Role Overview

Explain the purpose of the role, main responsibilities, reporting lines, and how success is measured.

Regular Tasks

List daily, weekly, monthly, and occasional duties with step-by-step instructions where needed.

Current Projects

Summarize active projects, current status, deadlines, stakeholders, documents, and next steps.

Important Contacts

Include names, roles, departments, email addresses, phone numbers if appropriate, and communication notes.

Systems and Tools

List software, dashboards, shared inboxes, calendars, folders, and access requirements.

Deadlines and Calendar Items

Include upcoming meetings, reporting dates, renewal dates, contract deadlines, and recurring reminders.

Risks and Open Issues

Explain unresolved problems, possible delays, sensitive matters, and recommended follow-up actions.

Final Notes

Add practical advice, lessons learned, and anything that would help the next person succeed faster.

Common Office Handover Mistakes to Avoid

Leaving the Handover Too Late

Rushed handovers are usually incomplete. Start early enough to document, review, train, and correct gaps.

Writing Vague Instructions

“Handle invoices” is not useful. “Check the invoice inbox every Tuesday and Thursday, match invoices against purchase orders, then send exceptions to finance” is useful.

Forgetting Informal Knowledge

Not everything lives in official systems. Include practical context such as client preferences, approval habits, common errors, and team routines.

Ignoring Security

Access should be transferred or removed through proper IT procedures. Sensitive data, passwords, and confidential documents must be handled carefully.

Failing to Assign Ownership

Every task and project should have a named owner after the handover. If everyone owns it, nobody owns it, and the deadline quietly walks into the sunset.

Practical Example of an Office Handover

Imagine a marketing coordinator is leaving the company. Their handover should include the monthly content calendar, social media login access process, agency contacts, campaign reports, invoice approval steps, upcoming deadlines, brand guidelines, and notes about recurring meetings.

A weak handover says: “Social posts are scheduled in the tool. Reports are in the drive.”

A strong handover says: “Social posts for May are scheduled through May 22. The Memorial Day campaign still needs legal approval by May 10. Weekly performance reports are saved under Marketing > Reports > 2026 > Weekly. The agency contact is Jordan Lee, who sends creative drafts every Thursday. Check UTM links before approving posts because the tool sometimes removes campaign tags.”

The second version gives the next person direction, context, and confidence. That is the difference between a handover and a shrug wearing business casual.

of Real-World Experience: What Office Handovers Teach You

One of the biggest lessons from real office handovers is that people often underestimate how much they know. Employees who have been in a role for a long time may say, “There is not much to explain,” and then casually mention 27 exceptions, four approval shortcuts, two unofficial backup contacts, and a spreadsheet that must never be sorted alphabetically. The hidden knowledge is usually where the real handover value lives.

In many offices, the most successful handovers happen when the outgoing employee writes the first draft, the incoming employee asks questions, and the manager reviews everything with a business continuity mindset. This three-person approach works because each person sees different gaps. The outgoing employee knows the work. The incoming employee notices unclear instructions. The manager understands priorities, risks, and accountability.

Another practical experience: screenshots help. A step-by-step instruction is useful, but screenshots of software settings, dashboard filters, folder paths, and report exports can prevent confusion. This is especially true when tools have similar buttons or when the process only happens once a month. Nobody wants to learn a monthly report by guessing which “Export” button is the friendly one.

It also helps to separate urgent knowledge from reference knowledge. The incoming person should know what must be handled immediately, what can wait, and what is simply useful background. A 30-page document with no priorities can be overwhelming. A document that starts with “First Week Priorities” is much easier to use.

Real handovers also show the importance of tone. A good handover should be honest without being negative. If a process is messy, say so professionally: “This workflow is being revised, and the current workaround is listed below.” If a client is demanding, write: “Client prefers detailed updates and quick acknowledgment of emails.” That is more helpful than “Brace yourself.” Funny? Yes. Useful in an official document? Not so much.

Another common lesson is that access issues cause unnecessary delays. The new person may understand the job perfectly but still be unable to work because they cannot open a dashboard, shared inbox, or folder. That is why access requests should be handled before the transition date. Managers should coordinate with IT early and confirm permissions before the outgoing employee leaves.

Finally, the best office handovers become reusable assets. A well-written handover document can later become an onboarding guide, training manual, standard operating procedure, or backup plan. This is especially valuable for small teams where one person may carry a large amount of operational knowledge. Instead of rebuilding knowledge every time someone changes roles, the organization gets smarter.

In short, an office handover is not just an exit task. It is a knowledge transfer exercise, a risk management tool, and a kindness to the next person. When done well, it says: “I cared enough about the work, the team, and the future to leave a clear path behind.” That is professional, practical, and much better than leaving behind a mysterious folder called “Old Stuff.”

Conclusion

Learning how to do a handover in an office is essential for smooth transitions, whether someone is leaving permanently, taking temporary leave, or passing a project to another team. The best handovers are planned early, clearly documented, supported by meetings, protected by proper access controls, and reviewed by managers.

A complete office handover should cover responsibilities, projects, deadlines, contacts, files, tools, risks, and next steps. It should also include the practical knowledge that rarely appears in job descriptions but keeps the office running smoothly. With the 12 steps above, you can create a handover process that saves time, reduces stress, and helps the next person succeed without needing a detective badge.