The Handover Someone Can Use

Asha's first handover folder was immaculate. It contained seventeen neatly named documents, a screenshot of the proof board and a farewell note saying everything was up to date. Jon opened it on Tuesday and could not tell whether the blue-labelled brochure was ready to send.

The folder was not useless. It simply answered a different question: what had Asha worked on? Jon needed to know what he was responsible for doing next.

Asha, Jon and their manager Ruth are fictional. Their small design studio provides the running example in this short practical book. Asha is taking planned leave, Jon will cover the proof queue, and Ruth retains authority over deadlines and client commitments. Their situation is ordinary, but their decisions give us something specific to examine.

Start your own handover with a sentence about the receiving person's work. For example: “On Tuesday morning, Jon needs to identify proofs awaiting a reply, distinguish approved artwork from working files, and raise uncertain deadlines with Ruth.” That sentence is a better organising principle than the contents of somebody's laptop.

Ask the recipient which part of the job they have already done. A capable colleague may need the history of three unusual jobs rather than instructions for opening a familiar application. Another person may know the subject well but lack access to the team's approved records. Those are different needs.

This book concerns ordinary business work. It is not a procedure for transferring clinical responsibility, controlling dangerous equipment, meeting a legal disclosure obligation or administering computer security. Use the qualified people and formal processes those situations require. Even for a small studio, the guide supplements the organisation's rules; it does not authorise anyone to change them.

Before gathering more files, write down the next person's first useful action. You will return to that action when you test the handover.

“Cover my projects” sounds generous until there are six projects and no agreement about what cover means. Jon was comfortable checking the proof queue. He had not agreed to quote for new work, approve discounts or promise revised delivery dates.

Ruth drew the boundary with both colleagues present. Jon would review the queue each working morning, prepare already-approved material for the usual checks, and record client replies. Ruth would decide changes to scope, price or promised dates. A different colleague would cover a supplier relationship Jon did not know.

This was not a demotion of Jon's judgement. It stopped a vague assignment from quietly expanding into authority nobody had given him.

An original working note can be very short: “Work covered; work excluded; receiving owner; decision owner; start; finish; backup.” Fill those fields in ordinary language. If the end date is uncertain, state when it will next be reviewed rather than inventing certainty.

Do not label somebody the backup merely because they have been copied into an email. They need to know what the role means and agree through the appropriate manager. Similarly, the person leaving cannot create capacity in a colleague's week by documenting an extra responsibility.

If nobody can take a task, record the gap. A manager may need to reassign work, reduce a service or change a commitment. The document should make that decision visible, not disguise the absence of an owner with the phrase “team to monitor”.

At the studio, the agreed boundary fitted on half a page. Its value was not its length. When an unfamiliar request arrived, Jon knew that raising it with Ruth was part of the arrangement, not evidence that he had failed.

The blue-labelled brochure had three versions. One contained approved wording, another contained a designer's experimental layout, and the newest file included an unapproved change. Sorting by modification date would not settle which one Jon could use.

Asha added a status note beside the approved record: “Client approved wording on Thursday. Layout still awaiting internal check. Do not send the experimental file. Next action: Ruth reviews the layout on Tuesday.” In this fictional example, the studio keeps the supporting approval in its normal restricted job record.

A useful status entry distinguishes what is known from what remains to happen. Try these fields: job or reference; present state; next action; owner; relevant date; evidence location; unresolved question. The date should say what it means. A client response requested by Friday is different from a firm delivery promised for Friday.

Avoid turning the handover into a second uncontrolled copy of every business record. Link to the approved location when that is permitted and practical. Keep confidential material within the access boundaries that already apply. A list distributed widely does not need a customer's private correspondence pasted into it.

Check the important links as the recipient, using their own authorised access. A link that opens for the sender proves little about the recipient's ability to use it. If the test cannot be performed yet, record that limitation and give the access request an owner.

The old files still had a purpose as history. Jon simply no longer had to infer today's status from them. Asha's account of the present pointed him towards the right evidence without pretending that a filename was an approval.

People often remember a conversation as more definite than it was. “We should manage Wednesday” gradually becomes “Wednesday confirmed”. A handover is a poor moment to let that drift harden into fact.

Look for the actual record of each significant commitment. If there is a promise, identify its scope and who was authorised to make it. If there is only a working target, call it that. If the position is unclear, say so and assign a clarification through the normal route.

At the studio, an email said the client hoped to receive a revised cover before a meeting. Asha's task list said Wednesday. Neither established that the studio had promised delivery by Wednesday. Ruth checked the correspondence before deciding what Jon should communicate. The handover itself did not send a message or renegotiate the arrangement.

Write dates so another person can understand them without reconstructing your context. Include the year where confusion is possible, and the time zone when a time matters across locations. “Tomorrow” is fragile in a document somebody may read next week. “By 15:00” is incomplete when sender and recipient use different local clocks.

Do not silently repair an impossible promise by writing a more convenient date in the handover. Record the discrepancy and take it to the person responsible. An honest unresolved issue is more useful than a tidy account which hides the problem.

For each open item, ask: what will someone else reasonably expect, and what evidence supports that expectation? You may discover there is no commitment at all. That finding still matters. It gives the receiving person permission to seek clarity rather than act on a guess.

Jon found a note saying not to use a particular printer for a folded insert. Without context, it looked like a permanent ban on the supplier. The actual reason was narrower: that supplier had not confirmed availability for this job's required paper.

Asha rewrote the note. The constraint concerned this job, not every future order. The last check had been made on a stated date, and Ruth would decide whether a new enquiry was worthwhile. Nobody had discovered a timeless rule about the printer.

Decision context helps when circumstances change. Keep the relevant question, the choice made, the important reason, the evidence location and the condition that would justify reconsidering it. You do not need a transcript of every discussion.

Mark uncertain knowledge as uncertain. “The customer usually prefers a call” is an impression unless there is a recorded communication preference that the team is allowed to use. “Last two replies came by phone” describes an observation but does not prove a permanent preference. Avoid collecting personal speculation simply because it might someday be useful.

Practical knowledge can also live in a demonstration. Ask the experienced person to explain a real decision while walking through a permitted example: what are they looking for, and what would make them stop? Use a safe substitute if the original contains confidential or sensitive material. Obtain any necessary permission before recording; a recording is not automatically the best record.

The recipient should leave with enough context to recognise a changed situation, rather than a list of instructions to follow indefinitely. At the studio, Jon now understood when the supplier question belonged with Ruth. He did not need to adopt Asha's personal habits to do the work well.