Find the work that depends on memory

Start with tasks people usually ask you about. Perhaps you know which file is current, who approves a request or how a recurring report is assembled. List those points of dependence before writing a long description of your role. The useful question is: what would another person need to know to take the next ordinary step?

Include work that is easy to overlook because you do it automatically. Updating a shared calendar, checking a recurring deadline or telling a colleague that an input has arrived may not appear in a formal job description. These small actions often explain why a process works smoothly. Record them plainly without turning the document into a claim that nobody else can manage.

Agree the scope with the right person

Discuss the handover with your manager or the person responsible for allocating work. Ask which tasks should continue, pause or move elsewhere. You should not have to assign everyone else's responsibilities by yourself. Put agreed owners beside tasks, and mark genuinely unresolved decisions as unresolved rather than inventing certainty.

Workplace policies and individual arrangements differ. Check your actual workplace documents and appropriate contacts for leave or employment questions; a general article cannot tell you what applies to your role. Keep the handover focused on operational information. Personal information belongs only in the channels and conversations where you have chosen to share it.

Write for someone doing the task

For each important process, give its purpose, starting point, next steps, file location and completion check. Link to the current source rather than copying large amounts of information that may become outdated. Use descriptive names. “Monthly report template in the shared reports folder” is more helpful than “the usual sheet.”

Do not put passwords, private client material or secret access codes into an ordinary handover document. Follow your workplace's approved access process so the new owner receives their own appropriate access. A colleague being able to read your instructions does not automatically mean they are authorized to see every file you can open.

Let someone try it while you are there

Choose one representative task and ask the receiving colleague to work through the notes. Notice where they need clarification. If they cannot find a file, improve the location description. If an instruction depends on a decision you normally make, explain the decision or identify who now owns it.

This is a test of the handover, not an examination of the colleague. Allow questions without filling every silence with a demonstration. Watching someone use the instructions reveals assumptions that are invisible when you read your own writing. Update the document immediately so the useful explanation does not remain only in a conversation.

Set a realistic contact boundary

Agree whether any contact during your absence is expected, through which channel and for what purpose. Avoid a vague promise to “always be available” if that is not the arrangement you want. A named alternate contact helps colleagues solve ordinary questions without routing everything back to you.

Set your automatic reply and calendar information to the agreed level of detail. They can direct people to the right place without describing your personal circumstances. If the plan changes, update the work contact rather than relying on colleagues to infer new availability from informal messages or social media posts.

Close with a short status page

Before the handover date, make a one-page overview of active work: current position, next action, owner and relevant date. Keep completed background material elsewhere so the live list stays readable. Note any decision that has not been made and who is expected to make it. Do not hide uncertainty inside a confident-looking checklist.

Ask the receiving person to confirm that they have the document and appropriate access. Then save it in the agreed shared location. A successful handover transfers understanding and responsibility; it does not require you to keep carrying every task from a distance.