Take a Real Vacation or Stay Tethered to the Phone: A Decision Tree
Why this matters
A vacation is the honest test of whether you actually stepped back or just moved your desk. If the shop cannot survive a week without you answering the phone, you have not built a business, you have built a job that pays worse than a job because it never stops. Deciding whether to truly unplug or stay reachable is not about how much you trust your people in the abstract. It is about what is actually in place. And whatever you cannot unplug from tells you the exact gap to go fix. This tree helps you pick the right level for this trip and read what it reveals.
Before you go: set the real-emergency path
One thing gets locked down no matter which level you pick, because it is about safety, not convenience. Make sure the crew knows the escalation path for a genuine emergency, a gas smell, water meeting electricity, a fire, an injury, an unsafe structure, before you leave.
- Name who has the authority to stop a job and send everyone home if a site is unsafe. That call cannot wait for you to land.
- Confirm everyone knows the response for a real hazard is to make people safe first and call the right emergency number, not to phone the owner for permission.
- Leave the emergency contacts and the shut-off basics written down and visible. This is the one thing you never delegate away entirely and never leave ambiguous.
With that set, the rest of the decision is about business continuity, not safety.
The three levels, side by side
| Level | What you do | What it requires | What it signals |
|---|---|---|---|
| Fully unplug | Phone off, someone else runs everything | Coverage, authority map, systems all real | The transition worked |
| Reachable for true emergencies | Off, but callable for a real crisis only | Good coverage, a few gaps you are watching | Nearly there, one or two things to firm up |
| Tethered | Working remotely, taking routine calls | Coverage or authority still missing | Not a vacation; a diagnosis of what to build |
If you can fully unplug
You have coverage that holds, an authority map so decisions have somewhere to go, and systems that run without you.
- Actually turn the phone off. A vacation you spend waiting for it to ring is not the test passed, it is the test half-taken.
- Tell the crew you are unreachable and that they are expected to handle it, then let them. The point is to prove the shop runs, which it cannot do if you are a safety valve they can pull.
- This is the goal state. If you are here, take the trip and enjoy the proof.
If you should stay reachable for true emergencies only
Coverage is mostly there, but a couple of situations still genuinely need you, or you are not yet certain the net holds.
- Define "emergency" narrowly and in writing before you go: what actually warrants a call and what does not. "A customer is annoyed" is not it. "A decision above the lead's authority that cannot wait a week" might be.
- Route everything through your number two first. They filter; only the real exceptions reach you. If your phone still rings ten times, the filter or the authority map is the gap.
- Treat every call you do get as data. Each one names a decision that had nowhere else to go, which is your build list for next time.
If you cannot unplug at all
The shop needs you daily and a real vacation is not yet possible. This is not a personal failing, it is a diagnosis.
- Name why you are tethered. Almost always it is one of three: nobody has authority to decide, nobody can cover your production, or the knowledge to run things lives only in you.
- That reason is the exact thing to build before the next attempt. The vacation was not the goal, it was the diagnostic, and it just handed you the answer.
- In the meantime, take a short trip, even a long weekend, with a narrow reachable window, and watch what breaks. What breaks first is what to fix first.
When to pick which
- Fully unplug: coverage, authority, and systems all pass the week-without-you test. Take it and prove it.
- Reachable for emergencies: the net is mostly there; use a tight, written definition of emergency and a number two who filters.
- Tethered, briefly: the shop cannot yet run without you. Do a short trial, read what breaks, and build that before the real trip.
Recap
- Lock the real-emergency safety path first, no matter the level.
- Fully unplug only when coverage, authority, and systems all hold.
- Reachable-for-emergencies needs a narrow written definition and a filtering number two.
- If you cannot unplug, name the reason; it is your build list.
- Treat every call that reaches you on vacation as a decision with nowhere else to go, and fix that.
References
- See related: The Systems That Have to Exist Before You Can Step Away
- See related: The Owner Who Is the Bottleneck and Doesn't Know It
- Trade-standard practice for continuity planning in owner-operated businesses