The date is fixed months in advance, everyone you know is coming, and it cannot be moved because the business had a busy week. That is what makes a wedding different from every other holiday you have postponed: the deadline is real, so the handover finally gets built.
Which is the quiet upside. Owners who plan properly for two or three weeks away usually come back to a business that runs better, because the absence forces the documentation, cross-training, and decision rules that "when things calm down" never produces. The goal is not just to survive the fortnight. It is to make the fortnight repeatable.
Here is the plan, working backwards from the date.
Ninety days out: find out what only you can do
Do not start by writing procedures. Start by finding the dependencies, because you will be wrong about where they are.
For two weeks, keep a running list every time you do something nobody else in the business could do. Not tasks you prefer to do — tasks that would genuinely stop if you were unreachable. Approving a quote above a threshold. The bank login. The one supplier who only responds to you. Payroll. The key you keep in your desk drawer.
Sort the list into four buckets:
- Delegate — someone else could do this with a written procedure and one practice run.
- Defer — nothing breaks if it waits three weeks. Say so explicitly, so nobody improvises.
- Decide in advance — it will come up, and you can pre-authorise the answer.
- Genuinely yours — a very short list, and each item needs a named backup anyway.
Most owners find the first bucket is far bigger than they expected and the last is two or three items. That gap is the whole project.
Sixty days out: document the delegate bucket
Write a procedure for each delegated item, and write it to the standard where the least experienced person who could plausibly do the task can run it without asking you. The format matters less than the test: hand it to that person cold and watch them execute it. Every question they ask is a missing line. The SOP-writing approach covers the structure; a wedding just supplies the deadline that makes it happen.
Prioritise ruthlessly. You need procedures for what is frequent, expensive when done wrong, or bottlenecked on you — not for everything. Five good procedures beat twenty half-written ones nobody trusts.
Two that are worth writing regardless of your industry:
- Money out. Who can approve what, up to what amount, and what evidence they file. Write the threshold down; "use your judgement" is how a fortnight away becomes an argument.
- New enquiries. Leads do not pause. If your follow-up currently depends on you remembering, that is a system problem the absence will expose brutally. Build the follow-up system before you go, not after you come back to a full inbox and a cold list.
Forty-five days out: write the decision rules
The purpose of this step is to make your absence non-blocking, and it takes about an hour.
For each recurring judgement call, write the rule and the escalation point:
- Discounts: up to X percent without asking, anything more waits.
- Refunds: under Y, approve and log it; over Y, offer a hold and process on return.
- Scheduling: fill the calendar to Z percent capacity, leave the rest for your first week back.
- Complaints: acknowledge same day, resolve within the rule if it fits, otherwise escalate to the named deputy.
Then name one deputy, not a committee. One person with the authority to make the call and the explicit backing to be wrong occasionally. Shared responsibility with no named owner is how every decision ends up in your notifications anyway.
Thirty days out: tell customers and suppliers
Announce the closure or reduced hours in whatever channels your customers actually use — your website, your booking system, your voicemail, your email signature, your Google Business Profile hours. Do it early enough that anyone with a deadline can work around you.
Say three things and no more: the dates, who to contact instead, and when you will respond. You do not owe anyone the reason, though "I am getting married" tends to buy goodwill you did not expect.
For suppliers, confirm anything that lands in the window: standing orders, deliveries, invoices due, subscription renewals, insurance dates. Move what you can outside the window, and make sure whoever is covering has the authority to sign for a delivery.
Two weeks out: protect the cash flow window
The most common way a well-planned absence hurts is not chaos — it is a cash gap that appears six weeks later. If you invoice on completion and nothing completes for three weeks, the hole shows up after you return, when you have stopped watching for it.
Three defences, in order of impact:
- Invoice before you go for everything already delivered. Do not leave a fortnight of billable work sitting unbilled because you would rather do it "properly" when back.
- Diarise the payments due in the window and give someone the chasing script. Late payment does not pause for your honeymoon.
- Forecast the trough. Map the expected dip and confirm you can cover the fixed costs through it. A short, planned dip is fine. An unplanned one that lands on top of wedding spending is not.
If forecasting is a spreadsheet you dread, this is a good moment to fix it — the constraints that make an absence survivable are the same ones that make the whole operations layer less dependent on you.
The week of: hand over properly, then actually leave
Do one dry run before you disappear. Have the deputy run a normal day while you sit on your hands. Whatever they have to ask you is a gap you can still close.
Then set the boundary. "I will check messages once a day at 6pm for anything marked urgent by the deputy" is a workable rule. "I will keep an eye on things" is not a rule; it is how you spend your wedding day on your phone.
Which brings us to the day itself, and it deserves its own warning.
The day itself cannot be re-run
Everything above buys you one thing: the ability to be present for a day that has no second attempt.
A wedding day is a fixed sequence built weeks in advance — a getting-ready window with a hard stop, a ceremony at a fixed time, a compressed run of family group photographs worked from a list agreed beforehand, and a reception that runs on its own schedule of speeches and dances. Every professional on the day works to that timeline precisely because none of it repeats. Documentary photographers such as Photojournalism by Rodney Bailey, a Washington DC wedding photographer working in a photojournalistic style for over three decades, build coverage around the sequence in advance for exactly that reason: the real moments are unrepeatable, and you only capture them by being ready when they happen.
The parallel is worth taking seriously as an operator. The reason to build the handover is not tidiness. It is that a phone call about a delayed delivery costs you a piece of a day you cannot buy back, and the photographs will show where your attention was.
Turn the phone off for the ceremony. Give the deputy's number to anyone who might need it. Let the day be the one thing on your calendar that has no contingency plan because it does not need one.
Coming back: capture what you learned
In your first week back, spend an hour on the debrief while it is fresh:
- What did the deputy have to ask you? Each question becomes a line in a procedure.
- What actually broke? Usually less than you feared, and rarely what you predicted.
- What did not get done, and did it matter? Anything untouched for three weeks with no consequence is a candidate for stopping altogether.
- What did the deputy handle well? Make that permanent — the fastest way to lose the gains is to take everything back on day one.
Owners who run this debrief tend to find the absence bought them several hours a week permanently, because the procedures outlive the trip. That is the real return.
FAQ
How long can a small business realistically run without the owner? Two to three weeks is achievable for most owner-operated businesses with a genuine handover, and the constraint is usually authority rather than skill. If nobody can approve spending or make a customer decision, the business stalls in days regardless of how competent the team is.
What if I do not have any staff? Then your handover is a mix of pausing, pre-booking, and buying a little help. Close the calendar, pre-schedule anything automated, and consider a virtual assistant or a trusted peer in the same trade to triage enquiries and cover emergencies. Solo does not mean unplannable; it means the "defer" bucket is bigger.
Should I tell customers why I am away? Optional, and usually beneficial. A specific, human reason gets far more patience than a vague "reduced availability", and it makes the fixed dates feel non-negotiable rather than like a preference you might bend.
What if a genuine emergency happens while I am away? Define what counts as one in advance — safety, legal deadlines, a major account at risk — and give the deputy a single channel to reach you. Everything outside that definition waits. Without a written definition, every problem becomes an emergency by default.
Next step
Work backwards from the date: find your dependencies, document the top five, write the decision rules, name one deputy, invoice before you go, and set a boundary you will actually keep. Do that once and you have built the thing every owner-operated business eventually needs — proof that good outcomes do not depend on you being in the room.
Most of the friction in a handover is people not being able to see the work. When you are ready to make the day-to-day visible to someone other than you, compare the project management and operations tools built for small teams and pick the one that fits how your business already runs.
