A handover is not a document

A handover often starts with good intentions.

Someone decides that a process needs to be written down. They open a document and begin listing the steps.

First, do this.

Then, check that.

After that, send the email.

The document grows. Screenshots are added. Links are included. The person who created it feels a little more confident that someone else could now take over.

Then the handover is tested.

The next person reads it and asks:

"What do I do if that information is missing?"

"Which version should I use?"

"Does this need approval?"

"What happens if the client changes their mind?"

"Who do I speak to if this does not follow the usual route?"

The document may be detailed.

The work is still sitting with the person who originally created it.

This is because a handover is not really about transferring instructions. It is about transferring enough understanding for another person to make sensible decisions.

Those are different things.

Instructions describe the normal route.

Understanding helps someone recognise when the normal route no longer applies.

That distinction matters because real work rarely arrives in a perfectly tidy sequence. Information is late. Dates move. People misunderstand each other. A client changes their mind. Something that looked straightforward turns out to need a decision before it can continue.

A handover that only explains the expected route is not necessarily wrong. It is simply incomplete.

The unusual parts are often the most important parts to capture.

What tends to go wrong?

Which details need checking?

What usually causes a delay?

What should happen if the person responsible is unavailable?

What can move forward without approval?

What needs to come back to the founder?

These questions make the handover more useful because they show where judgement is needed.

They also make it easier to see whether the work has genuinely been handed over. If every unusual situation still comes back to the original person, the person may have taken on the tasks, but not the responsibility around them.

That can create a strange kind of support.

The founder no longer does every action, but they still have to remain mentally attached to the process. They check whether things are moving. They remember which exceptions are still waiting. They keep an eye on the work because they do not yet trust that it will be handled without them.

The handover has moved the actions.

It has not moved the weight.

This is why I prefer to test a handover rather than simply finish writing it.

Give it to someone who was not involved in creating the process. Ask them to use it to complete a real piece of work, or a realistic example of one.

Do not immediately explain when they get stuck.

Notice what they ask.

Where do they stop?

What information do they look for?

Which decisions do they assume need approval?

What do they do when the instructions do not quite match the situation?

Those pauses tell you where the process needs attention.

The answer may be another sentence in the document. It may be a decision that needs to be made earlier. It may be a clearer boundary around what someone can decide for themselves.

It may also show that the process has too many steps.

This is useful information. The aim is not to create a huge document that tries to explain every possible outcome. The aim is to make the important parts of the work clear enough for someone else to carry.

A good handover usually needs to answer a few simple questions.

What is this work trying to achieve?

What needs to happen first?

What information is needed?

Where are the important decisions?

What should happen when the usual route changes?

Who needs to be involved, and when?

The wording can stay plain. The document does not need to sound formal to be useful.

What matters is that the next person does not have to guess what good judgement looks like.

A handover is not finished because the original person has written everything they know.

It is finished when another person can use that understanding to move the work forward.

That is a much more demanding test.

It is also the one that tells you whether the business has actually made room for someone else, or whether it has simply given them a list while keeping the responsibility in the same place.