How Is Work Handed Over?
Handing over work is something most owners have tried and abandoned: “you handle it from now on” was said, the job came back two weeks later, and the conclusion was “it’s better if I do it”. The problem wasn’t the team; it was that the handover was done in one sentence. 🔁
Short answer: a handover needs three things — a written rule, a limit, a checkpoint. A handover done without those three isn’t a handover, it’s abandonment, and abandoned work comes back.
Below: the three parts, the handover sequence, the moment of the mistake and the discipline of not taking it back. 📋
First part: the written rule
Handing over work starts with writing the rule.
What if the rule isn’t complete?
Fine. A rule covering eighty percent of cases beats a draft trying to cover a hundred. The remaining twenty gets handled by the limit.
Second part: the limit
Where the team stops and where it asks.
Third part: the checkpoint
What makes it possible for the owner to let go.
What’s the handover sequence?
Not all at once.
One job, one person, one month
The first handover is a rehearsal: the single most repeated job, to one person, with a one-month trial. During that month the rule gets corrected, the limit adjusted, the checking rhythm settled. When it succeeds, the second job comes — the sequence sits in the starting article. 🎯
What happens at the moment of a mistake?
The moment the handover dies or lives.
The first mistake will come
Definitely — and in that moment there are two options: take the job back, or fix the rule. An owner who takes it back tells the team “don’t decide”, and nobody decides again. An owner who fixes the rule writes the mistake into the system. The difference is in a one-sentence response. ⚠️
📝 Field Notes
An owner had handed over quote writing three times and taken it back all three. The fourth time we did it differently: a three-line rule, a single amount limit, a fifteen-minute weekly look. Two mistakes came up in the first month; both were written into the rule, the job wasn’t taken back. In month three the owner stopped writing quotes. A handover holds when it isn’t taken back at the third mistake. 🔁
📖 Quick Glossary
Written rule: three to five lines on what to decide in which situation. Limit: the threshold where the team’s decision authority ends. Checkpoint: the moment a handed-over job gets reviewed at regular intervals. Rehearsal handover: one job, one person, one month as a first trial.
⚡ Quick Summary
Three parts: written rule, limit, checkpoint. 🔁 The rule is three to five lines, the limit starts narrow, the checkpoint replaces intervention. One job, one person, one month. The first mistake will come; it gets written into the rule, not to the person.
🎯 Next Step
Let’s build your first handover together: rule, limit and checkpoint in one sitting: the quote page. Scope on the consulting page. 📋
Frequently Asked Questions
Sık Sorulan Sorular
Not how the job is done — the team already knows that — but what to decide in which situation. “If the customer asks for a discount, give up to this rate; above it, bring it to me.” Not a page; three to five lines. The longer the rule, the less it gets applied. 📄
From the owner’s head. There’s logic behind every decision they make today; the job is reducing that logic to one sentence. Most owners, sitting down to write the rule, say “I was always looking at the same thing anyway”. 🧠
By amount, time or situation: “up to this amount”, “until this date”, “for this customer type”. Below the limit is the team’s; above it is the owner’s. Without a limit the team still asks even with a rule — because it doesn’t know where it should stop. 📏
The first limit is as wide as the owner is comfortable with, not as wide as ideal. A limit that starts narrow grows; one that starts wide gets reset at the first mistake and the handover dies. Starting small isn’t slowness, it’s insurance. 🔒
Not looking at every job, but looking at the outcome at set intervals: once a week, fifteen minutes, what happened with the handed-over job. The owner relaxes not because they don’t see every job but because they see regularly. The checkpoint replaces intervention. 🔬
Because without a checkpoint the only form of control is intervention. Letting go feels like losing control. Once a checkpoint exists, letting go becomes making control regular. 🪑
Not to the person; to the rule: “the rule didn’t cover this situation, let’s add it.” That sentence is the only sentence that keeps a handover alive. The mechanism sits in the why-everyone-asks-me article, all questions on the consulting page. 📋
It’s usually not unwillingness but distrust: they don’t know what happens if they’re wrong. A written rule and the “mistakes get written into the rule” response remove that fear in a few weeks. Asking for responsibility starts with making it safe.
The logic from you, the sentence together. You answer “what do I look at”, the team turns it into an applicable sentence. A rule written by the team gets applied more easily because it’s in their own words.
It gets checked, just at regular intervals; the difference is between looking at every job and looking at outcomes once a week. An owner looking at every job looks tired and misses things. Regular and careful beats constant and superficial.
Source: SHRM — topics and tools