The Fortnight Without You: A Resilience Drill for Owner-Led UK Businesses
Photo: Francisclarke, CC BY-SA 4.0, via Wikimedia Commons
Most owner-managers have a plan for fire, flood or a cyber attack. Far fewer have a workable plan for the most likely disruption of all: being unavailable for two weeks. A diary gap is not a strategy. The business may keep trading, but cash approvals, supplier relationships and customer escalations often route through one person. If that person is off the grid, decisions stall or get made without authority.
A tabletop exercise can expose those dependencies without the cost of an actual absence. The aim is not to test whether staff can do their jobs. It is to test whether the organisation can make decisions, move money and hold key relationships when the owner is not there. Run the drill over a fortnight, record what happens, and fix the gaps while the disruption is still hypothetical.
Set the rules before the fortnight starts
Choose a two-week window that reflects normal trading rather than a seasonal lull. If the business has a quiet period, use it for the first run, but repeat the exercise later in a busier month. The owner should step back from routine approvals for the duration, though not from a genuine emergency. Appoint a drill coordinator, usually the most senior manager outside the owner, and brief the team that the exercise is about systems, not blame.
Agree what counts as an emergency. A cyber incident, a payroll failure or a safety event may justify contacting the owner. A supplier asking for a payment run, a customer requesting a credit note or a routine pricing query should not. Write those thresholds down. The exercise fails if every decision escalates to the same person by mobile phone.
Days one to three: access and authority
Start with money. Can the business make payments without the owner present? Check bank mandates, online banking tokens, dual authorisation rules, payment limits and card controls. Confirm who can release a BACS run, approve a Faster Payments transfer and view balances. If the owner holds the only token or the only mobile number registered for a one-time passcode, that is a finding.
Next, map delegation limits. List the decisions that normally reach the owner: supplier payments above a set amount, customer refunds, credit notes, discounts, purchase orders, overtime and urgent repairs. For each, record who may approve during the drill, the temporary limit and the evidence required. A verbal approval is not a control. Use a simple decision log with date, request, decision, decision-maker, amount and rationale.
The first three days should also test payroll and tax routines. Who has access to the payroll software? Who can approve a VAT return or a payment on account? Where are the accountant's contact details and the timetable for management accounts? These are routine tasks until they are missed. A fortnight is long enough to cover a payroll cycle or a supplier payment run, so use the calendar rather than memory to set the test.
Days four to seven: relationships and escalations
The operational gap often appears in relationships, not systems. List the key external contacts: major customers, critical suppliers, the bank relationship manager, the insurer, the landlord and the main professional advisers. For each, record who holds the relationship, what the contact expects and where the latest correspondence sits. A customer who only trusts the owner is a commercial risk. A supplier who only accepts instructions from the owner is a supply risk.
During the middle of the drill, route customer escalations to the nominated manager. The manager should resolve them using agreed limits and record any case that would normally have gone to the owner. Do the same with supplier disputes, delivery failures and pricing queries. The point is not to pretend the owner does not exist. It is to reveal how often the business relies on their presence to keep a relationship calm.
Days eight to ten: cash and decisions under pressure
By the second week, the drill should include a cash decision. Create a realistic scenario: a customer pays late, a supplier tightens terms, or an unexpected repair lands. Ask the nominated manager to decide whether to delay a payment, use an overdraft, chase a debtor or ask the owner for approval. Record the decision and the time taken. Slow decisions are a resilience issue even when they are eventually correct.
Review the decision log at the end of each day. Look for three patterns: decisions that could not be made, decisions made without the right authority, and decisions that were made twice because nobody knew the first one had happened. These patterns point to unclear limits, missing information or poor handovers. They are more useful than a general impression that the fortnight felt busy.
Days eleven to fourteen: recovery and review
In the final days, test the return. What has built up in the owner's inbox? Which approvals are waiting? Which relationships need a personal call? A two-week absence does not end when the owner returns; it ends when the backlog is cleared and the business is back to normal. Ask the drill coordinator to prepare a short handback note covering open decisions, cash movements, customer issues and supplier commitments.
Then hold a review within a week. Keep it factual. Produce a table with three columns: finding, risk and fix. For each finding, name an owner and a deadline. Fixes may be simple: add a second bank authoriser, document a supplier contact, set a temporary approval limit, move key correspondence into a shared folder or ask the accountant to copy another manager into routine filings. None of these requires a large project.
The test is repeatable. Run it again in a busier period, or after a change of staff, bank or software. The objective is not to prove that the owner is dispensable. It is to ensure the business can operate safely when the owner is not available, whether for a holiday, an illness or an unexpected emergency. A fortnight of structured rehearsal is a modest cost compared with discovering the gaps after an unplanned absence has already forced the issue.