x
Itself, next month. That's the useful framing — you're not writing for a colleague you don't have, you're writing for the version of you who comes back from a week away, or gets ill, or simply forgets how the thing was set up.
Solo businesses skip handover documents because there's nobody to hand to. The result is that everything operationally important lives in one head, undocumented, and the business has a single point of failure that also needs a holiday. This isn't a resilience abstraction. It's the reason coming back from a week off takes three days.
Six documents. An afternoon, once, then fifteen minutes of upkeep a month.
1. The money calendar. What goes out and when — subscriptions, tax dates, anything on a card that expires. Written down, not remembered. The failure this prevents is a lapsed payment for something load-bearing while you're on a beach.
2. The access list. Where the accounts are, how you get in, and what happens if you can't. Not the passwords in a document — the map: which manager holds what, which email recovers which account, which two-factor device matters. If you'd struggle to reconstruct this after losing a phone, that's the gap.
3. The client state. One line per live client: what stage, what they're waiting for, what's promised and when. This is the one that stops the post-holiday scramble, and it's fifteen minutes to write.
4. The answer library. The twenty questions you answer repeatedly, answered once, properly — the same library that powers holiday cover that actually answers. It's the highest-reuse document you'll ever write.
5. The automation map. What runs on a schedule, what it touches, what it does when it doesn't know. If you've been writing escalation rules, this is just collecting them in one place. If you haven't, discovering you can't list what runs unattended is itself the finding.
6. The stop list. What should not happen while you're away. No new commitments, no pricing decisions, no publishing without review. Automated systems don't know you're away; this is where you write down what your absence means.
Because automation moves work out of your head and into systems — and undocumented systems are worse than undocumented habits.
A habit you've forgotten simply stops. A scheduled job you've forgotten keeps running, quietly, doing something you no longer remember authorising. Six months later you find an automation emailing a list you retired, or an agent filing into a folder you stopped using. The handover pack is what keeps the machine legible to its owner.
Here's the checkable version, and it's the same principle every operational-resilience framework uses: document the dependency at both ends. The system says what it reads; the file says which system reads it. When only one end is documented, the other end eventually disappears without anyone noticing — which is precisely how a working process becomes a mystery.
There's a harder version of this lesson. A process that exists only in one place — one head, one chat, one undocumented habit — is one bad day from not existing. The pack is cheap; rebuilding from memory is not.
Now, badly, rather than later, properly. A rough version covering all six beats a polished version covering two, because the value is in the coverage — the gap you didn't write down is the one that bites.
Set a repeating fifteen minutes on the first of the month to update it. That cadence sits naturally alongside closing the week like a CFO — same instinct, longer interval.
And keep it somewhere that survives the device it was written on. A document that only exists on the laptop that broke is a document you didn't write. Cloud-synced, ideally in the same place as everything else operational.
Hand the pack to someone who doesn't know your business and ask: could you keep this alive for a week? If the answer is no, the gap is your next fifteen minutes. If it's yes, you've built something most solo businesses never do — a business that can be left alone.
For the prompts that draft five of these six in an afternoon, the free 5-min read is here: 7 AI Prompts That Run a One-Person Business.
Related Decodes
TL;DR: A solo business should hand over to its own future self — the version returning from a week away or a bad week. Six documents cover it: the money calendar, the access map, one line per live client, the answer library, the automation map, and the stop list of what must not happen while you're away. Write it roughly this afternoon rather than properly later, keep it somewhere cloud-synced, and update it for fifteen minutes on the first of each month.
