How to Take a Week Off Without the Shop Stopping

Why this matters

The week off that fails does not fail during the week. It fails in the two weeks before, when you decide it will be fine, and the evidence that it will not be fine never gets collected. Then you spend the week on the phone, come back to a pile, and conclude you cannot leave. This procedure runs on a six-week countdown and its centrepiece is a dry run: two days where you are unreachable, three weeks out, so that what breaks breaks while there is still time to fix it and while you are still in town.

Week minus 6: pick the week against your own load history

Put the dates in the schedule everyone else builds from, not just in your own calendar. A week that lives only in your head gets booked over by your own dispatcher.

Choose the week by looking at your own job counts for the same week in prior years, if you have two or three years of history. Aim for a week whose same-week job count sits at or below your annual median week. Owners routinely pick a week that is convenient for their family and happens to be their fourth-busiest week of the year, then read the resulting chaos as proof that they can never leave, when it was a scheduling error.

If you do not have history yet, use the crude version: not the first or last week of a month if your billing clusters there, and not a week containing a holiday your customers treat as a deadline.

Week minus 5: build the decision list from real traffic

For two weeks you write down every question that reaches you. Not a guess at what might come up, an actual log of what did. Then sort each entry into three piles:

• Already has a written answer. Point to where it lives. If you cannot point to it, it belongs in pile two.
• Needs a written answer before you go. This is the pile that becomes your work in weeks minus 4 and minus 2.
• Genuinely needs you. Should be short. If more than a handful of items land here, you are not looking hard enough at the locks holding them.

The two-week log matters more than the sorting. Owners who skip straight to writing answers write answers to the questions they remember, which are the dramatic ones, not the frequent ones.

Week minus 4: one covering person per lane, never one person for everything

Name coverage by lane: field and scheduling, money and customer accounts, supplier and parts. Two or three lanes, each with one named person, each knowing which lane is theirs and which is not.

One person covering everything fails for a mechanical reason, not a competence one: the questions arrive simultaneously and that person is also doing their own job. Splitting by lane means each covering person absorbs a fraction of the traffic and can hold their own work as well.

Also name the tiebreaker. When two lanes disagree, or something falls between them, who decides. Without a named tiebreaker, cross-lane questions become your phone calls, and cross-lane questions are the majority of the hard ones.

Week minus 3: the dry run

Two consecutive working days. You are unreachable except for a genuine emergency, and you define what counts as one before you start, in writing, so the definition is not negotiated in the moment. Injury, a job that has damaged property, a legal or safety matter, a customer situation escalating past the covering lead. Nothing about pricing, nothing about scheduling.

Have the covering people log every escalation: what it was, which lane, and how it resolved. You want the log even for escalations they handled without you, because those are the ones that show the coverage working.

The rule: an escalation rate above 3 per working day (unit: per working day, over a dry run of at least 2 consecutive working days) means the week off will not hold in its current shape. At or below 1.5 per working day, it holds. Between 1.5 and 3 you have gap-closing work to do, not a cancelled trip. The two-day minimum is not optional: a one-day run gives you a single day's traffic and one busy Tuesday will misread the whole shop.

Week minus 2: close the gaps the dry run found, one cause at a time

Sort the dry run's escalations by class, then fix the largest class first. Not all of them. The largest, in writing, this week.

The reason to attack the largest class rather than the scariest one is that escalation classes are heavily skewed. Two thirds of the traffic is usually one or two shapes, and one written authority boundary removes most of it. The scary escalation is usually a genuine one that should reach you even from a beach, and rewriting the rules to prevent it would be the wrong outcome.

Then re-run the dry run: another two consecutive working days, same conditions, same log.

Week minus 1: the money calendar and the notices

Two lists.

The money calendar. What has to be paid or collected while you are gone, on what date, by whom, with what authorization. Payroll runs, supplier terms falling due, tax deposits, an invoice batch that has to go out or the whole month slides. Because federal employment tax deposits fall due on the schedule the IRS assigned your business, either monthly or semiweekly depending on your lookback-period liability, an absence spanning a deposit date needs a named person with the authority to make that deposit before you leave, not a plan to handle it on your return.

The notices. The customers and vendors who will notice, told who to contact instead. Keep it short and do not apologize. "I am out the week of the ninth. Anything you need, call the shop and ask for the covering lead, who has full authority on your account." A notice that reads as an apology invites people to save their question for you.

Week 0: the departure rules

Three rules, agreed out loud before you go.

• One channel. A single way to reach you, used only under the emergency definition. Not your normal phone, normal email, and the group chat, because three channels means every channel gets used.
• A daily check window, or none at all. If you cannot go dark, pick one 20-minute window at a fixed time. Fixed and short beats open and constant, because an open channel means the covering people never fully take the wheel.
• Nothing lands in your first day back. Block your first morning back for the return read, not for meetings. Everything people saved for you will arrive that morning regardless; the block is what stops it turning into a fourteen-hour day.

A worked countdown

An owner of a six-tech shop plans a week off. He has run these dates against three years of job counts and picked a week sitting just under his annual median week.

Dry run at week minus 3. Two working days, 9 escalations logged.

• 5 were pricing or authorization: added scope on a quoted job, a warranty goodwill call, a discount request.
• 2 were scheduling conflicts between two lanes.
• 1 was a supplier credit hold.
• 1 was a genuine emergency, water damage on a callback, which correctly reached him.

Nine escalations over 2 working days is 4.5 per working day. Against the stated rule, that is above 3, so the week off does not hold as of week minus 3. That is the honest reading and it is the reason for running the dry run three weeks out rather than the week before.

The gap-closing. Pricing and authorization is 5 of 9, about 56% of the escalations. One written authority boundary: the covering lead may approve added work up to a stated multiple of the original quote and may issue goodwill up to a stated share of an invoice, both without calling; anything above either line, or any customer disputing scope, goes to the covering lead's tiebreaker rather than to the owner. The supplier credit hold gets one line: who at the supplier to call and what the shop's standing terms are.

The scheduling conflicts are left alone this cycle. Two of nine is not the largest class and the tiebreaker rule already covers them on paper.

Second dry run at week minus 2. Two working days, 4 escalations. That is 2.0 per working day: below 3, above 1.5, so still in the gap-closing band rather than the holds band. Of the 4, two were the scheduling conflicts he had deliberately deferred. He writes the lane boundary that week.

Third dry run at week minus 1. Two working days, 2 escalations, so 1.0 per working day. At or below 1.5, so the trip holds by the rule as stated.

Note what the sequence produced beyond a number. Between the first and third runs the escalation count fell from 9 to 2 over the same two-day span, and the composition changed: the first run was dominated by one class, the third contained two unrelated one-offs. A residue of unrelated one-offs is what a working coverage arrangement looks like. A residue that is still mostly one class means the boundary you wrote did not carry an authority, only a description.

What changes the thresholds

A covering lead who is new to the role. If this is their first coverage stint, move the holds floor from 1.5 down to 1.0 escalations per working day, because a new covering person absorbs fewer surprises and the margin has to come from somewhere. The gap-closing band moves with it.

Peak season. Same adjustment, same reason. A dry run in a slow week and a trip in a busy one are not measuring the same shop, so run at least one of your dry runs in a week that resembles the week you are taking off.

If you still run calls. The week costs the shop your field hours whether or not coverage holds, and that is a capacity question the dry run does not measure at all. Either the board absorbs the gap, or you accept fewer jobs that week, or someone covers your calls too, which is a fourth lane. Decide which before week minus 4, because the third option changes who your covering people are.

A shop with one other person. The lane split collapses and the dry run still works, but the rule changes: with a single covering person the useful reading is not escalations per day, it is whether any escalation took them more than an hour, because a single person's capacity fails on depth rather than on count.

Verifying it held

Judge the week on the return, not on how the week felt.

• The return pile against the dry-run prediction. If the third dry run read 1.0 per working day and you come back to a week's worth of held decisions, the covering people were logging escalations they were not actually authorized to resolve, and the dry run measured politeness rather than coverage.
• Decisions made in your absence, and how many you would reverse. Zero decisions made is the worst outcome, not the best. A handful made and one you would have called differently is a working arrangement.
• Whether the boundaries stayed after you returned. The authority band you wrote for the week is now the shop's standing band unless you take it back. Most owners take it back without noticing, which is why the next dry run reads exactly like the first one did.

References

• See related: The Owner Vacation: Actually Taking One
• See related: The Systems That Have to Exist Before You Can Step Away
• See related: The Owner Absence Readiness SOP
• See related: Covering the Billable Hours You Give Up When You Step Back
• IRS Publication 15 (Circular E), Employer's Tax Guide, for federal employment tax deposit schedules