You know which spreadsheet matters, who can approve a last-minute change, and why the weekly report always needs a second look. Then you accept another job, and suddenly all that everyday knowledge needs to make sense to someone who has never sat at your desk.
A useful handover helps another person keep essential work moving without guessing their way through your old responsibilities. Whether you have two weeks or just a few days, you can build one around a simple question: What would someone need to know to handle the next normal workday?
Start with what could get missed
Before documenting anything, list the tasks that would cause confusion if nobody handled them. Think about approaching deadlines, recurring customer requests, scheduled reports, and approvals that depend on your input. Your calendar and recent task history can help you catch responsibilities you perform so automatically that you barely notice them.
Separate those responsibilities by urgency. Something due the day after you leave deserves more attention than an annual process that happens six months later. If time is tight, document the nearest deadlines and highest-impact tasks first, then add background material once those essentials are clear enough for someone to follow.
For example, a monthly supplier payment might require invoice checks three days before its official deadline. Record that earlier cutoff so the next owner does not discover the preparation work only when payment is already due.
Ask your manager to review the list and confirm the priorities. This is especially helpful when several people will divide your work, because each responsibility needs a clear destination. You do not have to decide the entire staffing plan yourself, but you should make any unassigned work visible before leaving.
Give the reader a clear starting point
Create one main document that tells the reader where to begin. A folder containing thirty unexplained files creates another task for your replacement before they can do any actual work. Your main document should briefly describe your role, its immediate priorities, and where the supporting materials live within company systems.
Put the most useful information near the top: your final working day, the person coordinating the transition, and the next few important deadlines. Include a short explanation of what your role contributes to the team. That context helps someone understand why a task matters instead of simply copying your routine.
Use descriptive labels for supporting documents, such as “Weekly inventory report instructions” instead of “Helpful information.” If there are several versions, identify the current one. A newcomer should be able to distinguish an active template from an old example without opening everything and comparing dates or asking around for clues.
Describe tasks as decisions and actions
For each recurring responsibility, explain what starts the task, what the person should do, and what a finished result looks like. “Prepare the Monday update” leaves too much open to interpretation. Specify where the information comes from, which template to use, who reviews it, and where the approved version goes.
Add the judgment calls that instructions often leave out. Perhaps you wait for a department to confirm its numbers, or you flag unusual changes before distributing a report. These details help your replacement recognize when the standard process applies and when they should pause and ask someone for guidance first.
For a weekly sales update, explain whether canceled orders belong in the total. Link to an example showing the exclusion and identify who can resolve disputed entries before the figures reach the wider team.
A compact task entry can use five labels: When, inputs, steps, review, and completion. Write enough under each to make the process understandable. For a complicated task, add a worked example using approved company material, with brief notes explaining the choices that might otherwise seem arbitrary to a new reader.
Make unfinished work easy to pick up
Active projects need a different kind of explanation from recurring tasks. Someone taking over needs to know where things stand today, not just what the project was intended to accomplish. Record the current status, the most recent meaningful action, the next action, and any deadline that affects what happens next.
Be precise about what “waiting” means. “Waiting on feedback” is vague; “Draft sent to the operations manager Tuesday; follow up Friday if there is no response” gives the next person a usable instruction. Describe dependencies clearly, especially when work cannot continue until another team provides information or makes a decision.
Include the location of the latest working draft and any response already promised to a customer. For instance, note that a revised delivery estimate is due Thursday even if the underlying project deadline remains unchanged.
Keep confirmed decisions separate from suggestions and unresolved questions. If you proposed a new approach but nobody approved it, say so. Otherwise, your replacement may reasonably assume that anything written in the handover represents an agreed plan, which can lead to avoidable rework or awkward conversations with colleagues and customers.
Explain who helps and how access works
A list of names becomes much more useful when you explain what each person handles. Identify the contact for approvals, technical problems, customer questions, and scheduling changes. Use roles alongside names where practical, so the document still makes sense if someone changes teams or another employee temporarily covers their responsibilities.
Describe the normal route for getting help. For example, your team might submit requests through a shared queue instead of messaging a particular colleague. Include relevant meeting names or internal channels, but avoid filling the handover with personal commentary about coworkers. Keep relationship notes factual, respectful, and connected to work.
List the systems and shared folders the next person will need, then identify the established process for requesting access. Never put passwords, recovery codes, or other credentials in the document. Ask the appropriate administrator to arrange access through company procedures, and flag anything that could prevent the new owner from starting.
Check whether access includes the actions the role requires. Someone may be able to view a shared dashboard but still lack permission to export its data or update the figures used in the weekly report.
Test the document with a real task
The quickest way to discover missing instructions is to let someone use them. Choose one representative task and ask a colleague to walk through your written steps while you observe. Resist the urge to explain everything immediately; their questions show you where the document relies on knowledge you forgot to include.
If possible, have the future owner perform the task during your overlap period. A demonstration can look clear while you are doing all the clicking and decision-making. Letting the other person take the lead reveals missing permissions, unfamiliar terms, and steps that need a screenshot or a more specific written explanation.
After the walkthrough, revise the instructions where the reader hesitated. If they selected the wrong reporting period, add the exact date rule beside that step. Then ask them to try it again to check that the wording resolves the confusion.
You may not have a replacement available before departure. In that case, ask your manager or a teammate unfamiliar with the task to review the essentials. Focus the conversation on what they would do next, where they would find the necessary materials, and which situations would require help from someone else.
Finish with a clear transfer of responsibility
On your final working day, update the status of active items and mark when the document was last reviewed. Send your manager the main document’s location and flag any remaining ownership or access gaps. If plans changed during your notice period, make sure the written handover reflects those changes rather than earlier assumptions.
Your final check is simple: can someone find the next deadline, take the next action, and identify the right person to ask for help? If those answers are clear, you have given the team something useful. Close your remaining tasks, confirm who is taking over, and leave the document where your colleagues can find it.