The two-week holiday test
Here's a test that costs nothing and tells you more than any consultant's audit: book a two-week holiday somewhere with patchy signal, and see what actually happens. Not what you think will happen; what happens when you genuinely don't check in for fourteen days.
Most owners fail this test in the first 72 hours, not because their business is badly run day to day, but because nobody has ever worked out what has to be true for it to run without them specifically. This isn't a motivational exercise about letting go. It's a dependency check: a list of things that either exist or don't, each one true or false, no room for "mostly."
What actually breaks in the first 48 hours?
Almost never the big strategic calls. It's the small decisions that only you make, because only you have ever made them.
A distribution business with three warehouses, in Pune, Nashik and a smaller unit in Aurangabad, runs fine on a normal Tuesday because the owner is one WhatsApp message away. Stock discrepancy between the Pune ledger and the physical count? He looks at it, decides whether to write it off or investigate, moves on. Multiply that by ten small judgement calls a day across three sites, and you can see why week one of a holiday is where things start slipping even though nothing catastrophic happens. The business isn't broken. It's just waiting for an answer only one person gives.
The fix isn't a manual for every scenario. That's impossible to write, and nobody reads it anyway. It's deciding, in advance, which decisions can be made by a rule and which need a person. Stock discrepancy under ₹5,000: write off, log it, move on. Over ₹5,000: escalates to the warehouse manager, who has three hours to decide before it escalates again. That's a dependency resolved, not because someone became braver, but because the decision got a rule and an owner that isn't you.
Who is actually allowed to decide without you?
This is the one owners get wrong most often. They assume that because someone is senior, they're authorised. Those are different things.
A construction contractor might have a site engineer with fifteen years of experience who still texts the owner before approving anything over ₹20,000 in material overage, not because he can't judge it, but because nobody has ever told him he's allowed to. Authority that isn't explicit doesn't exist. It sits unused, and the decision waits for the owner instead.
The dependency test here is simple: for every recurring decision above the smallest ones, is there a named person with an actual rupee limit and a stated right to act without asking first? If the honest answer is "they'd probably check with me anyway," that's not a delegation. It's a habit, and habits don't survive fourteen days of silence. This is the same gap that shows up when SOPs describe a process instead of assigning it: a document that explains what should happen without saying who is allowed to make it happen.
Where does the money keep moving without you?
Payroll, supplier payments and customer collections are the three places a two-week gap turns into a real problem fast, because they carry external deadlines that don't pause for anyone's holiday.
Take a retail chain running eight outlets with roughly ₹18 lakh moving through supplier payments each month. Does someone other than the owner have the authority and the access to release those payments against agreed terms? Is there a second signatory on the account who isn't the owner? If payroll runs on the 1st and the owner is unreachable that day, does it still run? Statutory obligations don't wait for anyone's leave: PF and ESI contributions carry fixed monthly deadlines, so a payroll dependency on one person turns a scheduling problem into a compliance one.
The test isn't whether the owner trusts someone else to handle money. It's whether that person has actually been given the access and the mandate before the holiday starts, not promised it as a contingency.
What happens when something actually goes wrong?
Everything above assumes a normal fortnight. The real test is what happens when it isn't: a cold-chain temperature breach at 2am with a full delivery run at risk.
A food distribution business with a cold-chain fleet logs van temperatures every two hours, because a single excursion above threshold can spoil the whole run. On a normal day, the driver flags it, the ops manager calls the owner, and someone decides whether to reroute or discard. On day nine of a two-week gap, that call still needs to happen, just not to the owner. The dependency that has to be true here is an escalation path with a real name at the end of it, not "someone will sort it out." If the honest answer is that the ops manager would still try three times to reach the owner before doing anything, the escalation path doesn't exist yet. It only looks like it does.
Write this down properly, for once, because it's genuinely a list: for each of your two or three highest-risk failure modes, what's the trigger, who gets the call, what can they do without further permission, and what's the ceiling above which they wait.
How do you know it worked, without calling to check?
You don't want a business that ran fine because you texted twice a day from the beach. That's not the business running without you. That's you, still running it, just from further away.
The real test is whether you can look at one place, one dashboard, one summary, one message, after fourteen days, and see what happened without having asked for it during. Not six WhatsApp groups you'd have to scroll through to reconstruct the story. One place that shows what was flagged, what got resolved, and what's still open. If that place doesn't exist, the business didn't run without you. It ran on a longer leash, and you'll find out what snapped when you're back. This is the same shift covered in why chasing is a structural problem, not a discipline one: the goal isn't a team that never needs input, it's a business that surfaces the exceptions and handles the rest on its own.
What to do this week
Don't plan the holiday yet. Pick one process, payroll, or the highest-value customer escalation, or stock write-offs, and write down, honestly, what happens to it if you're unreachable for two weeks starting tomorrow. Not what should happen. What actually would. Wherever the answer is "they'd wait for me," that's your first dependency to fix, and it's smaller than it feels: a rupee limit, a named person, and a rule for what happens if they're unsure. Fix one a week, and the two-week test stops being hypothetical.