> Source: https://brendanlevin.com/insights/how-to-take-a-real-holiday-as-a-business-owner/ > A concrete preparation checklist for founders who want to take a real two-week holiday without checking in. Covers decision rights, coverage protocols, and the operating rhythm your team must run without you. For founders, owners, and operators # How to Take Two Weeks Off Without the Business Breaking By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m. To take two weeks off safely, install three things before you leave: a written decision-rights threshold (a real number, not a vague guideline), a named coverage protocol, and a standing weekly rhythm your team runs without prompting. **The holiday is the test, not the reward.** If something breaks, that is your [owner dependency](/insights/what-is-owner-dependency/) map. Key takeaways - A two-week absence is the most honest diagnostic for what still runs through you personally. - Written decision-rights thresholds, not general trust, are what make unsupervised decisions safe. - A standing weekly team rhythm must exist before you leave, not be invented while you are gone. - Checking in 'just in case' voids the test and keeps the dependency intact. ## Why the two-week holiday is a diagnostic, not just a break Most founders do not take a real holiday. They take a working holiday with better scenery. They check Slack at breakfast, approve things from the pool, and return feeling like they never left. Nothing breaks, but nothing was actually tested. A genuine two-week absence with no contact is a structural stress test. What stalls reveals what still runs on you. A deal that cannot progress because no one can approve the discount. A hire that pauses because no one owns the final call. A client who emails you directly because your team has no clear point of contact. Each one is a finding, not a failure. The holiday surfaces the exact list of things that need fixing before the business can genuinely run without you. This page is about the preparation checklist that makes the test safe to run, not the conceptual journey of letting go. If you want to understand the deeper structural problem, [start here](/insights/how-to-get-my-business-to-run-without-me/) first. ## The three pre-conditions that make a two-week absence safe You need exactly three things in place before you board the plane. Not ten. Three. If any one of them is missing, the absence will either break something real or force you to check in, which means the structure is not ready yet. First: written decision-rights thresholds. Not 'use your judgment'. A real number and a real rule. For example: any unbudgeted spend under $2,000, the owning person acts and tells you after in a summary email. Any spend from $2,000 to $10,000, the owning person makes the call and logs the reason in your shared decision log. Anything above $10,000 waits for you, full stop. Every common decision type in the business needs this treatment: hiring, client commitments, contract changes, pricing exceptions. [A full guide to writing these is here.](/insights/how-to-set-decision-rights-in-your-business/) Second: a named coverage protocol. One named person holds the role of 'point of contact while the founder is away'. They are not running the business. They are the single escalation point for anything that genuinely cannot wait. They know your red lines. They have your emergency contact for a true crisis, which is defined as: the business loses a client worth more than X per year, a key person resigns, or a legal or regulatory event occurs. Everything else is not a crisis. Third: a standing weekly operating rhythm the team already runs. This is the one most founders skip. They assume the team will hold itself together for two weeks. But if the weekly rhythm only happens because you call it and chase the agenda, it stops the moment you leave. The rhythm must already be running without your prompting before you go. ## The preparation checklist: what to do in the four weeks before you leave Run through this in order. Do not skip to the later items. The sequence matters because each one builds on the last. - Week 4 before departure: Write your decision-rights thresholds for spend, hiring, client commitments, and pricing. Put them in a single document your team can find without asking you. - Week 4 before departure: Name the coverage owner and brief them on the red-line criteria. Write it down, not just in a conversation. - Week 3 before departure: Run your standing weekly meeting and deliberately do not lead it. Sit in the room but say nothing until the end. If it stalls, that tells you the rhythm is not yet self-running. - Week 3 before departure: Identify every recurring decision that currently routes to you. For each one, either write a threshold rule or explicitly hand the call to a named person. - Week 2 before departure: Tell your team the exact dates, the coverage owner's name, and the red-line criteria. Write it in a shared channel, not just verbally. - Week 2 before departure: Run the weekly meeting again without leading it. If it runs cleanly, the rhythm is ready. - Week 1 before departure: Do a single handoff call with the coverage owner. Walk every open item, who owns it, and what good looks like by the time you return. - Day of departure: Set an out-of-office that names the coverage owner and the red-line criteria. Do not put your mobile number on it. ## The common failure mode: checking in just in case The most common reason a founder's two-week absence fails is not that something breaks. It is that the founder checks in before anything has a chance to break. Checking in just in case feels responsible. It is actually the thing that keeps the dependency alive. Your team learns to wait for your confirmation rather than trust the decision-rights framework you built. The framework atrophies. You return and the structure is no weaker than when you left, but no stronger either. The honest version of this: if you feel the need to check in on day three, that is a signal the pre-conditions were not fully in place before you left. Make a note of what you wanted to check on. That list is your [dependency map](/insights/signs-your-business-is-too-dependent-on-you/) for after you return. One check-in is acceptable and worth building in deliberately: a single thirty-minute call at the end of week one with the coverage owner, structured purely around the red-line criteria. Not a status update. Not a Slack browse. One call, one question: has anything hit the red lines? If the answer is no, the call ends. That is the only contact that belongs in a real two-week absence. ## What to read when you return: the post-holiday debrief The two weeks away generated a finding list. Use it. Within your first week back, run a short debrief with the coverage owner: what decisions were made in your absence, what would have been escalated under the old structure, and what stalled that should not have. Whatever stalled is the next thing to fix. If a proposal sat unsigned because no one had authority to approve a standard-terms contract under $15,000, write that threshold. If a client called you directly because they did not know who else to contact, fix the client-facing coverage protocol. If the debrief reveals that most things ran fine, you have real evidence the structure works. That evidence is worth more than any consultant's assurance. It is the business demonstrating it can run without you for a defined period. The next step is extending that period and [reducing your operational load permanently.](/insights/how-to-get-out-of-the-day-to-day/) ## When the structure is not ready and you know it Some founders read this checklist and know immediately that they cannot safely complete it before their planned departure. The decision-rights thresholds do not exist. The weekly rhythm runs because they run it. The coverage owner does not exist yet. That is a structural gap, not a character gap. The business was built to run through you, and it does. [Owner dependency](/insights/what-is-owner-dependency/) is a structure problem, not a discipline problem. The fix is installing the structure, which is a defined piece of work, not a long journey. If you want to know exactly where the gaps are before you start, the [free Founder Dependency Diagnostic](/executive-diagnostic) maps where your week actually goes and shows what still runs on you. It is the right starting point before you attempt the two-week test. If the checklist above revealed gaps you cannot close before your next planned absence, the free Founder Dependency Diagnostic maps exactly where your week goes and what still runs on you. [Take the free diagnostic](/executive-diagnostic) ## Common questions What if something genuinely urgent comes up while I'm away? That is exactly what the red-line criteria and coverage owner are for. Define 'urgent' before you leave, in writing: a client loss above a named revenue threshold, a key-person resignation, or a legal or regulatory event. Everything else is not urgent in the way that requires you. If your team cannot agree on what counts as a genuine crisis before you go, that conversation is part of the preparation work. How do I write decision-rights thresholds without getting it wrong? Start with spend, because it is the easiest to put a number on. Pick a number below which the owning person acts and tells you after, and a number above which they wait for you. Everything in between gets logged with a reason. Then repeat the exercise for the three or four other decision types that most commonly route to you: pricing exceptions, client commitments, hiring decisions, and scope changes. You do not need a perfect framework. You need a workable one that your team trusts enough to use. Can I just promote someone internally to cover me while I'm away? Naming a coverage owner is part of the protocol, but that person needs the authority and the written rules to act, not just the title. A person without clear thresholds and a decision log will still escalate everything to you out of caution. The written decision-rights framework is what makes the coverage role functional. My team says they are fine without me, but I don't believe it. Who is right? Run the test and find out. Take a week first if two weeks feels too risky. Watch what stalls. Your instinct may be right, in which case you have a list of things to fix. Or your team may be right, in which case you have evidence you can build on. Either outcome is useful. Neither is achievable by having the conversation in the office. Is this different from getting out of the day-to-day? Yes. Getting out of the day-to-day is the ongoing structural goal: reducing how much of the business routes through you permanently. The two-week absence is a one-time diagnostic and stress test. It tells you where the dependency currently lives. What you do with that finding is the longer structural work. What if I return and everything went wrong? Then you have a precise finding list rather than a vague sense that things depend on you. Each thing that went wrong points to a specific structure gap: a missing decision threshold, an unclear ownership line, a rhythm that was not self-running. Fix those specific things. The holiday was worth running even if it was imperfect. Related: [what is owner dependency](/insights/what-is-owner-dependency/) · [how to set decision rights in your business](/insights/how-to-set-decision-rights-in-your-business/) · [signs your business is too dependent on you](/insights/signs-your-business-is-too-dependent-on-you/) · [how to build an operating rhythm](/insights/how-to-build-an-operating-rhythm/) · [how to get my business to run without me](/insights/how-to-get-my-business-to-run-without-me/) · [what is a founder operating system](/insights/what-is-a-founder-operating-system/) · [more insights](/insights).