Seven days away is a document problem, not a willpower problem

The reason most owners cannot disappear for a week has very little to do with how hard they work and almost everything to do with what has never been written down.

Ask an owner whether they could take a week off and you get a feeling in reply. Probably not. It would be difficult. Maybe in January.

Ask a different question and something useful happens instead.

If you were completely unreachable from Saturday to Saturday, what specifically would break, and what would each break cost?

Most owners cannot answer that with specifics, and the inability to answer is the finding. It is not evidence that the business is fragile. It is evidence that the operating knowledge lives in one head as a set of reflexes, and reflexes cannot be handed over in a conversation on the way to the airport.

What the honest evidence base looks like

We went looking for a trustworthy public number on how many small business owners take a full consecutive week away, and we did not find one.

What exists is a set of figures published by payroll companies, insurers and booking platforms, each polling a self selected panel of a few hundred owners, each with methodology that is either undisclosed or thin. Those numbers get quoted as fact for years afterwards.

So we are not going to tell you that some percentage of owners have not taken a week off since 2019. There is no good public number for this. What can be said instead is structural, and structure is checkable by anyone against their own business, which makes it more useful than a survey anyway.

The five things a cover person actually needs

A person covering your lane for seven days does not need to know everything you know. They need five things, and each one fails in a specific way when it is missing.

1. Authority, with numbers on it

This is the one that decides whether the week is a break or a slow motion interruption. A cover person with no spending authority escalates twenty times a week, and every escalation is a phone call to a beach.

Authority means real figures written down in advance:

• Daily advertising spend cap.
• Goodwill refund limit per order, and a separate limit per week so twenty small refunds cannot add up to a large one.
• A limit for supplies and small purchases.
• An explicit list of what needs you first regardless of amount: any new subscription, any purchase order to a supplier, any discount above a stated percentage, any change to a product price, any payment to a contractor.

And then the list that matters more than all of it: what is never permitted, even with approval by message. No wire transfers and no changes to bank details, whoever asks and however urgent the email sounds. No new contracts signed. No replies to legal letters or to press. No new tools connected to the store with write access.

That bank details line is not bureaucratic caution. A supplier emailing to say their bank account has changed is one of the oldest fraud patterns in commerce, and the ideal target is exactly a person covering for somebody who is unreachable and under time pressure to keep things moving.

If the handover document contained only that one sentence it would still have earned its afternoon.

2. Failure modes, with the response written for a slightly panicked reader

This is the section that earns the document. Not a description of the systems. A list of the things that actually go wrong, each with what to do first, who to call, and what not to do under any circumstances.

The usual set for an ecommerce brand: the payment processor holds funds, the advertising account or the email account is disabled, a shipping partner misses a pickup, a discount code stacks with another and starts draining margin on live traffic, a supplier misses a ship date, the store goes down.

Write each response as steps somebody can follow while their heart rate is up. Short sentences. The order matters. And be explicit about the forbidden move, because under pressure the instinct is usually to do something large and irreversible.

3. Contacts, as humans, with hours

Name the person, not the company. A support portal is not a contact. Add the hours they actually answer, and their time zone, because a covering person in a different city discovering at 4pm that your 3PL contact stopped answering at 2pm has lost the day.

4. The rule for the case nobody imagined

Every handover meets a situation its author did not think of. Without a rule for that case, the week stalls and everything waits for you, which is the outcome the document was written to prevent.

The rule is three questions:

1. Does it cost money above the written limits?

2. Is it visible to the public?

3. Is it hard to undo?

If any answer is yes, it waits for you. If all three are no, take the smallest reversible step that keeps the customer whole, and take it now. Then write it in the log within the hour: what happened, what was done, what it cost, why.

Then post it where the team can see it, so it is not a surprise later. Then add the answer to the document, so the next person does not have to decide it again.

That last step is what turns a handover from a static file into something that gets better every time it is used.

5. The return note

The first thing that should happen on the day you come back is not you opening dashboards for four hours.

It is one note, before nine in the morning, containing: revenue and orders against the previous week, spend and blended return, tickets opened and closed, anything that broke and how it was handled, every decision taken that was not covered by the document, and the three things needing a decision today.

Without this, the week off costs you the following Monday and half of Tuesday, and people conclude that time away is not worth it. It was worth it. The re entry was unmanaged.

Never write a password anywhere in it

This document gets printed, forwarded, left open on a desk and pasted into chat. It is the least secure file in the company by design, because its whole purpose is to be available to somebody who is not you.

Every serious tool has an invite system. Use it, grant the smallest role that does the job, and remove the access on the day cover ends, as a diary entry rather than an intention.

Where a login genuinely has no invite system, share it through a password manager as a shared item with two factor authentication switched on, and write the name of the password manager in the document, never the credential.

If you find a password written down anywhere while doing this, delete it and change that password the same day.

Define what a true emergency is, in writing

An undefined emergency means every item is potentially one, which means the phone is never quiet, which means you did not take a week off. You took a week of working from somewhere with worse internet.

So write the definition down. The store cannot take orders. The payment processor is on hold. The advertising account or the email account is disabled. A customer is threatening legal action, or is public and angry. Anything that will cost more than the approval limit if it waits a day.

Everything else waits for one evening message. Not because those things do not matter, but because a covering person who knows the boundary can hold the line, and a covering person who does not know it will call about a delivery exception at eleven at night out of pure decency.

The cheap test before the expensive one

Do not write this document and then immediately leave for seven days. Test it for one day, at a cost of one day.

Run a silent day. You are in the building, at your desk, and you answer nothing. Someone else holds the lane using only what is written. Every time they have to ask you something, that question is a missing line in the document. Write it down and keep going.

In our own dry run, one silent day surfaced over a dozen missing lines, and almost all of them were limits and thresholds rather than instructions. Then run a silent Friday, which is harder because Friday carries the week's reporting and the weekend's promotions. Then take the week.

This sequence turns a leap into a test, and a test is something you can afford to fail.

The same document is the first hire document

Here is the part that changes the economics of writing it.

The document that lets you take a week off is, word for word, the document that lets anybody else run the lane. A contractor. A first hire. A family member covering while you are on a plane.

The authority limits, the failure modes, the contacts, the uncovered case rule and the log are identical in both situations, because both situations are the same situation: somebody who is not you making decisions in your absence.

Most owners write this twice, once badly under time pressure before a holiday, and once again properly when they hire. Writing it once, well, before either, is the whole saving.

The Seven Day Handover tool in our free library is that document as a form.

It matters that it is not blank: every field arrives prefilled with a strong default written for a Shopify, Klaviyo and Meta brand, because a blank form is the single most common reason these documents never get written.

You edit what is wrong, delete what does not apply, and fill in only the parts nobody but you can answer.

It runs entirely inside the page and stores nothing, which also means closing the tab clears it, so print it or copy the text out when you are done.

If you want a quick read on where you currently stand, the last question in the Founder Score is exactly this one: could you take seven consecutive days off without the store degrading, yes easily, yes with preparation, not really, or no.

What to do this week

1. Answer the specific question in writing. If you were unreachable Saturday to Saturday, name the three things that would break and what each would cost. Three lines. This takes ten minutes and it tells you what the document has to cover.

2. Write the spending limits first, with real numbers. Daily advertising cap, refund limit per order, refund limit per week, small purchases. Numbers, not adjectives.

3. Write the never list. No bank detail changes, no wire transfers, no contracts, no replies to legal or press, no new tools with write access. Copy that list as it stands if you like. It applies to almost every business.

4. Write three failure modes with their first response. Choose the three that have actually happened to you in the last year, not the three that worry you most.

5. Book a silent day in the next fortnight and tell the person covering that you will not be answering. Log every question they have to ask anyway. That log is the second draft of your document, and it is more accurate than anything you would have written from imagination.

One week from now you will not have taken a holiday. You will have something more durable: a written answer to the question of what happens when you are not there.