A Good Handover Lets Someone Else Carry the Work

A practical handover helps a colleague find the work, understand the limits, and complete the next task without relying on the person who stepped away.

By Arbab Naseebullah Kasi, Chief Executive Officer - CEO, Feel Worldwide Foundation Inc.

Illustration of colleagues preparing a practical work handover.

There is a particular kind of worry that follows a responsible person on a day off. Will someone find the current list? Will they know which promise still needs attention? Will a small exception turn into a long chain of messages? The person may have written careful notes and still feel unable to step away. That feeling deserves a practical response: make the next piece of work possible for someone else to carry.

For a small nonprofit, community group, or growing service business, a useful handover is more than a collection of files. It is an agreement about what continues, who can act, and how the incoming colleague will know whether the work is complete. The central question is simple: could another authorized person handle the next ordinary task, and recognize when to stop, using what we have prepared?

Start with the work that cannot quietly wait

Trying to document an entire role in one afternoon usually creates an exhausting list. Begin with one recurring responsibility whose interruption would affect another person: confirming a room booking, sending a promised update, or preparing materials for an agreed appointment. Name the result and its deadline. Then name the work that may safely wait. A temporary colleague needs permission to prioritize, especially when covering this responsibility alongside their own.

Choose a manageable boundary. “Cover operations” is too broad. “Confirm next week's room bookings using the approved calendar, and flag unresolved requests by Thursday afternoon” gives the handover a testable purpose. Include the consequence of a missed deadline in plain language. Someone may otherwise assume that an internal administrative task has no effect outside the office.

The UK's Health and Safety Executive describes effective handover as preparation by outgoing staff, an exchange of relevant information, and checking by the incoming staff as responsibility transfers. Its guidance concerns workplace handovers, including safety-critical settings. For ordinary office work, a useful adaptation is to treat preparation, conversation, and demonstration as separate parts of the transfer. This article's exercise is an educational adaptation, not a replacement for a regulated workplace procedure. Read HSE's shift-handover guidance.

Show the current state, not just the usual procedure

A procedure explains how work normally happens. A handover must also explain what is happening now. The next colleague needs to distinguish a completed request from a pending one, a confirmed arrangement from a possibility, and a current file from an older copy. Without that distinction, even a clear procedure can lead to the wrong action.

Keep the stable instructions in one place and the changing status in another clearly linked place. The instruction might say where approved bookings are recorded. The status note might say which booking is awaiting a response today. Give both an owner and a last-checked date. Avoid copying the same information into several documents that will drift apart. A short note pointing to the authoritative record is often more useful than a long email containing an outdated snapshot.

Write down the exceptions the experienced person normally carries in memory. What happens if the contact does not reply? Which request needs a supervisor's decision? What counts as evidence that the task is finished? This is where much of the value sits. The substitute may already know how to send a message; they may not know when sending another message is the wrong next step.

A fictional handover that reveals the missing piece

Consider this fictional teaching example. Leila coordinates room bookings for a neighborhood association and will be away for a week. Marco agrees to cover confirmations. Leila gives him a folder containing a calendar, an email template, and the venue's conditions. At first, the handover looks complete.

During a practice run, Marco finds two calendar files. One shows a Wednesday booking as confirmed; the other marks it provisional. He also discovers that the confirmation template is available, but the approved mailbox is not accessible from his account. Neither problem reflects a lack of commitment. Both are gaps that a folder alone concealed.

They repair the handover together. Leila identifies the current calendar and archives the obsolete working copy according to their usual records practice. Their administrator arranges the access Marco actually needs through the organization's approved process. They do not pass around Leila's password. The supervisor clarifies that Marco may confirm requests within existing approvals, but must escalate requests to waive a condition. A named alternate can make that decision during Leila's absence.

Their compact handover note now reads:

• Result and deadline: Send confirmations for approved bookings by Thursday at 3 p.m.; record each response in the current calendar.

• Current state: Two requests are waiting for information. Their entries identify the missing details and the last contact date.

• Where the work lives: Use the shared booking calendar and the approved confirmation template; test access from Marco's own account.

• Authority and limits: Confirm already approved arrangements. Refer exceptions to the duty supervisor; do not promise a waiver.

• Evidence of completion: The confirmation is recorded, the booking status is updated, and unresolved cases have a named owner.

• If work cannot continue: Tell the supervisor which request is blocked and by when a decision is needed. Use the agreed holding message if a customer update is due.

The note contains only information needed to carry the task. Private customer details stay in the approved record, with access limited to authorized staff. In your own setting, use the organization's actual privacy, access, and records rules. A handover should make responsibility clearer without spreading confidential information into personal accounts or informal group chats.

Let the incoming colleague drive the rehearsal

Ask the colleague to work through one ordinary sample and one realistic exception. For the booking example, that means locating an approved request, preparing its confirmation, recording its status, and explaining what they would do with a request outside their authority. Use fictional or appropriately protected records. Do not send test messages to real customers by accident.

The outgoing person observes and records where the instructions leave room for guessing. Resist the urge to rescue every pause immediately. A pause may reveal a confusing filename, a missing permission, or an assumption that has never been written down. Agree that the exercise is testing the handover, not judging the colleague. Stop and intervene immediately if a real safety, privacy, or other material risk appears.

This approach is consistent with the City of Boston's business continuity exercise guidance, which uses a constructive, no-fault setting to reveal gaps and assigns responsibility for improvements. Boston's tool addresses larger disruption scenarios; the short rehearsal here applies that learning principle to one everyday responsibility. See the city's exercise and improvement-plan resource.

Write down what the colleague completed independently, where they needed help, and what remains blocked. “Document shared” is evidence of delivery. “Colleague located the current record and handled the sample exception within their authority” is stronger evidence of readiness. Neither proves that every future situation is covered. It tells you what has actually been tested.

Make continuity humane and proportionate

An effective handover also respects the person receiving the work. Ask about workload, language, accessibility, and the format they can use comfortably. HSE's communication guidance explicitly calls for language suited to the workforce and consideration of communication methods. Read its communication principles. For your team, that might mean a clear written note plus a conversation, accessible headings, or a demonstration that can be revisited with permission.

Documentation takes time, and not every task deserves the same depth. Start with work where delay, confusion, or a mistaken commitment would matter most. A small team may decide to reduce a service temporarily if nobody has the necessary authority or competence. A clear holding arrangement is more responsible than silently expecting an unprepared colleague to keep everything running.

Review the handover after the first real use and whenever the process changes. Keep one person responsible for maintaining it. Also agree what happens when the usual owner returns: which decisions were made, which cases remain open, and when responsibility transfers back. The goal is dependable work that allows people to take leave, learn new roles, and meet ordinary life demands without feeling permanently on call.

This focus on practical organizational capability connects with Feel Worldwide Foundation Inc.'s Leadership, Institutions & Implementation Capacity pathway. You can explore that work or contact the foundation about a relevant collaboration. For your own team, begin with one recurring responsibility this week. Prepare the smallest useful handover, let a colleague try it, and fix the first point where the work still depends on guesswork.