- operations
- delegation
- small business
Holidays: what has to keep running without you
How to prep your business before you go away: sort what can wait from what can't, and set up only the second half. One page, one week.
You shut the laptop on Friday genuinely believing everything is squared away. By Tuesday, phone face-down on the towel, three things surface at once: the quote for the industrial-estate job, the woman who asked about the September course, and whether anyone has opened the email from the accountant. You flip the phone over. Holiday's over.
This is about the boring, useful half of the problem: separating what can wait from what can't, and only setting up the second part. It works whether you're a one-person operation or a team of fifteen, and it takes a week to prepare.
The problem isn't the backlog, it's the thread that snaps
When you leave, the work doesn't disappear — it queues up. And a queue is rarely the real damage. Silence is.
A customer who writes on the 3rd and hears nothing until the 17th isn't waiting for you. They called someone else, someone picked up, done. You'll never know they existed, because customers who leave don't say goodbye. Same with the supplier who needed a yes to hold stock for you, or the two-star review that sits unanswered for a fortnight and becomes the first thing anyone searching for you reads.
Then there's the middle option, which is the worst of the three: checking your phone "a couple of times a day". You're neither resting nor running the business. You reply with half the context and a short fuse, and you come back feeling like you never stopped.
Build the list backwards
The usual way to prepare is to sit down and imagine what might go wrong while you're away. It works badly, because your brain hands you the three historic disasters and quietly forgets the twenty small things you do without noticing.
Flip it. The week before you go, open a note on your phone and write one line every time someone interrupts you, and every time you do something only you know how to do. No sorting, no judging. "Call asking about August opening hours." "Moved an appointment." "Approved a 10% discount." "Dug out a delivery note from March."
By Friday you're looking at your actual job, which almost never matches the one you'd describe if asked. That list — not your memory — is the starting point.
Three boxes: can wait, needs an answer, needs a decision
Take the list and drop every line into one of these:
Can wait. Far more than you think. The rep selling you a new phone system, the report you haven't opened in six months, the trade association meeting. The only action here is saying so plainly: an out-of-office with a real return date, not an "I'll get back to you as soon as possible" that means nothing to anyone.
Needs an answer, but no judgement call. Opening hours, the address, list prices, whether there's a slot on 2 September, where an order is, what paperwork a given process requires. The information already exists; it just has to come out on time. This box is usually the biggest of the three, and it's where nearly every "I wrote to you and got nothing" comes from.
Needs a decision. An off-list discount, a deadline that's going to slip, a serious complaint, anything involving refunds or signatures. This needs a named human — you from the pool, or someone on your team with explicit authority to decide. What it can't be is undecided in advance.
The classic mistake is filing everything under box three. Since everything needs your judgement, everything waits, and you come back to three hundred emails, two hundred and eighty of which were asking what time you open.
What to write down (one page is enough)
You don't need a manual. You need one page with five things on it:
- Who covers what, by name. "The customers" is not an owner. "Marta has WhatsApp and the phone, Javi has quotes" is.
- What gets answered automatically, in the exact words. Eight to twelve common questions, written as they'll actually be sent. Not "explain the returns process" — the literal returns text.
- What never goes out without you, as a short list. Off-list pricing, delivery commitments, complaints, press, anything involving money going back. Genuinely short: a twelve-point list is a list nobody learns.
- How you get alerted, and the threshold. One channel, stated without wiggle room: "if this happens, ring me; everything else waits until the 25th." An alert that arrives via three routes is an alert nobody sends.
- Access. The point that looks administrative and is the one that wrecks the fortnight. A good share of August emergencies aren't emergencies — they're passwords only you had.
If someone who joined a month ago can't follow the page, it isn't finished.
Where an agent fits, and where it will let you down
Box two — answering without deciding — is precisely where an AI agent earns its keep. Picking up whatever arrives by WhatsApp, the website and email at any hour, answering what's already settled, putting an appointment in the calendar, confirming an order has shipped, and escalating only what falls outside the script. The advantage isn't that it works in August; it's that it replies in two minutes, while the customer is still thinking about you.
Now the honest part. Setting up an agent the week before you leave is a bad idea. An agent you haven't watched running isn't a safety net — it's a new system talking to your customers before anyone knows how it behaves. It needs two or three weeks of you standing over it, correcting replies and tuning when it should escalate. If you're off next week, do it by hand with people this time, and have the agent ready for the Christmas break, which you prepare in October.
Second warning: don't try to automate box three. "I'll just check from my phone" isn't a cover plan. It's the polite way of not going on holiday.
What you're really preparing is September
When you get back, spend twenty minutes on the post-mortem: what got handled without you, what stalled, what reached your phone that shouldn't have. Those twenty minutes are worth more, organisationally, than the fortnight on the beach.
Because the page you wrote isn't a holiday document. It's the delegation manual you've been meaning to write for three years and never had a deadline for. August just supplied the deadline.
And if sorting the list shows box two has quietly got out of hand — follow-ups, reminders, quotes coming off a template — that's the part an operations agent can carry all year, not just in August. You approve what matters; the rest keeps moving with your phone face-down.
