The shift ends. You leave a note: “Everything is basically fine. Keep an eye on the usual thing.”

To you, this is a concise operational summary. To the next person, it is the first sentence of a mystery novel.

Which thing? What does “basically” exclude? Does “keep an eye on” mean check it once, check it hourly, or position a chair beside it until dawn? The note has successfully transferred your confidence while leaving most of your knowledge behind.

A good handover closes that gap. It gives the next person enough context to continue the work without requiring access to your memory. This is useful during a shift change, a vacation, a project transition, or any moment when one human being stops being the entire information system.

Describe the state, not only the story

People naturally explain how they reached the current situation. That history can be useful, but the receiving person first needs to know where things stand.

Consider a service request. “We called twice, then someone said they would look into it” describes activity. “The issue remains unresolved; the assigned technician is expected tomorrow, and this is the temporary arrangement” describes state.

Start with what is complete, what is open, and what has changed. Then include the history needed to understand those facts. You do not need to document every conversation. You need to preserve the decisions and uncertainties that affect what happens next.

A short status summary also reveals ambiguity to the person writing it. If you cannot say whether something is approved, underway, or waiting, the confusion probably existed before the handover. Writing has simply given it a place to stand.

Name the current source of information. A reference to “the diagram” is less useful than a link to the approved diagram with its revision or date. The next person should not have to choose between three files that all look sufficiently final.

Every open item needs a next move

An unfinished task without an owner tends to become communal background anxiety. Everyone knows it exists. Nobody is quite sure why it is still there.

For each important open item, identify who owns the next step, what that step is, and when it is needed. If the owner has not accepted the assignment, say that plainly. A handover should not manufacture agreements that have not happened.

“Waiting on confirmation” is an acceptable status if the note says who was asked and what confirmation is needed. “Follow up” is much better when it includes a name, a channel, and a meaningful time.

Separate a deadline from a hoped-for arrival. “Must be ready by 10” and “vendor expects to arrive around 10” are not interchangeable. When the difference matters, the note should make it visible.

You can also specify what would trigger escalation. If the delivery has not arrived by a certain point, or a temporary arrangement stops working, who should be contacted? The trigger saves the next person from guessing whether they are allowed to act.

Distinguish a warning from a rumor

A handover often includes information that is incomplete. That is normal. The problem comes when uncertainty acquires the tone of a confirmed fact during transmission.

Write what you know, how you know it, and what still needs checking. “A colleague reported an intermittent problem; it has not been reproduced” is more honest and useful than “the system is broken.” Equally, a verified problem should not be softened until it becomes invisible.

For sensitive material, use the organization’s approved channel. A helpful note can become unhelpful very quickly if it exposes personal information to people who do not need it. Do not include passwords in a handover document. Explain how authorized access is obtained.

Avoid using the note as a place to settle personal grievances. The next person needs operational context, not a cast list of everyone who has disappointed you since Tuesday.

Write in terms someone outside your immediate routine can understand. Abbreviations and nicknames may save six seconds for the writer while creating six minutes of translation for the reader.

A short conversation can finish the transfer

For important work, a written note and a brief conversation often complement each other. The document preserves facts. The conversation reveals what the receiving person has not understood.

Invite the other person to explain the next step back in their own words. This need not feel like a test. It is a quick check that both people are leaving with the same map.

If the work is safety-critical or regulated, follow the formal handover process required for that setting. A general note is not a substitute for an established procedure. In ordinary work, the same underlying principle remains useful: the handover is complete when the information is usable, not merely when the message is sent.

Before leaving, ask one final question: “What would I need to know if I were arriving now?”

Then remove anything that exists only to prove you were busy and add anything that prevents the next person from being surprised.

A good handover is a small act of professional generosity. It lets somebody begin their shift with work to do rather than a séance to organize.