Sample post
A handover plan for an owner-led team
A longer sample guide to transferring decisions, relationships and daily routines during a handover.
A handover is easier to plan when it describes what the team needs to do on an ordinary day. In this example, the owner of a small field-service company is preparing to step back. The team already knows its trade. What it needs is access to decisions, relationships and a few routines that currently live with the owner.
Make the invisible work visible
For one week, keep a record of the times someone interrupts the owner. Capture the question, who asked it and what the owner looked at before answering. Categories will emerge. Some questions are about spending approval, some concern a client relationship and others arise because a booking tool is out of date.
Circle the questions that come up more than once. Choose one the team could answer with better information and one that needs a clear decision maker. Work on those first. The list will become more accurate once the team sees how it is used and can add the decisions that arrive by phone.
Describe the boundaries of a decision
Consider a technician who finds unexpected work while inspecting a property. They may be able to explain the issue and quote a small variation on the spot. A more expensive variation may need a second opinion or written approval. The handover should specify when each route applies and who the technician can reach.
Write down what qualifies as an exception
An exception can be high cost, high risk or a promise the business can only meet by moving another customer. Use agreed examples from past jobs. These make the line between ordinary work and an escalation easier to recognise than a dense policy written in abstract terms.
Transfer relationships over several calls
Choose the clients who typically call the owner directly. Work out who will support each relationship and have that person join the next relevant call. To give the introduction a practical purpose, let the incoming contact handle the next booking or ask about a recurring problem. Document preferences and confirmed commitments immediately afterwards.
One advance note helps: list the commitments currently outstanding before introducing the new contact. This avoids introducing a capable colleague into a conversation about a promise they have never heard about. If the transition affects a particular deadline, confirm the responsible person in writing.
Practise a week with the owner out of the routine
Start with a normal period when the team has enough cover. The owner agrees to step out of the routine schedule and is available through a named escalation route. Ask the team to log what they could finish, what they delayed and what still needed input. Record the lag between a question and an answer as well as whether the answer was correct.
Review that log after the week. If several decisions stopped because no one understood a customer’s contract, that points to a specific documentation problem. If everyone knew the terms but nobody felt authorised to hold the line, that is a different problem and belongs in the responsibility map.
Protect a short review rhythm
In the first weeks after the change, meet briefly at a predictable time. Review open exceptions, promises to customers and decisions that had to wait. Close items as they become routine and pick the next recurring decision to transfer. The aim is to make the team’s work easier to run and leave a record that another incoming leader can understand.