One Page Between Order and Panic: The Continuity Note Every UK Business Should Write This Week
Every small business has a person who quietly holds the keys. Not the director, necessarily — often it's the office manager who knows which client invoice needs a gentle nudge each Friday, or the bookkeeper who understands why the payroll spreadsheet has three tabs and only one of them matters.
Then, one Monday, that person isn't there. Flu, a family emergency, a fortnight in the Algarve. The business keeps trading, but everything takes twice as long, mistakes creep in, and someone spends a very expensive afternoon reconstructing knowledge that took years to accumulate.
This is not a disaster-recovery problem. It is a continuity problem, and it has a remedy that costs nothing more than an hour of honest writing.
Why the Obvious Solution Never Gets Done
Most owner-managers will nod along to the idea of documenting processes. Very few ever do it, because the mental image is a forty-page operations manual nobody will read. The gap between the ideal and the achievable is where good intentions go to die.
The answer is to shrink the ambition. A continuity note is not a manual. It is one page — genuinely one page — that answers a single question: if this person vanished today, what would the replacement need to know by close of play tomorrow?
What Belongs on the Page
Through our work with owner-managed businesses across the UK, we suggest structuring the note around four headings.
Who to contact. The accountant's direct line, not the firm's switchboard. The IT support provider and the account reference. The payroll bureau. The landlord's managing agent. Two or three named suppliers who matter most. Phone numbers and email addresses, written out in full.
Where things live. Not the passwords themselves — never that — but where the credentials are held: the password manager, the sealed envelope in the safe, the shared vault with the accountant. The location of the payroll file, the client database, the insurance policy documents, the bank mandates. Note which systems require two-factor authentication and how a second person would legitimately gain access.
What happens each week. A short rhythm of recurring obligations: VAT deadline on the 7th, the supplier run on Tuesday, the client who insists on Friday chasing, the direct debits that fall on the 1st. This is the section most often omitted and most keenly missed.
The unwritten rules. The client who must never be emailed before 10am. The reason the bank account has two signatories. The supplier relationship that's cordial but contractual only in theory. These are the things that make the difference between a functioning handover and a fortnight of apologising to people.
Who Holds the Copy
A continuity note locked in the head of the person it describes is worthless. It should exist in printed form with at least two trusted parties — commonly the owner and the external accountant — and in a secure digital location the named people can reach without the absent person's help.
Review it twice a year. Phone numbers change, suppliers come and go, and a stale continuity note can be worse than none at all, because it inspires confidence it doesn't deserve.
The Cost–Benefit Case
Set against the alternatives, the arithmetic is stark. A single day of disrupted payroll processing, a missed filing deadline attracting HMRC penalties, or one irritated client drifting to a competitor will cost more than the hour it takes to write the note — and infinitely more than the zero pounds it costs to keep it current.
For businesses with more than a handful of staff, consider extending the exercise: a short note per key role, not just the owner's. The principle is the same. Identify the single points of failure, write them down, and share the answer with someone you trust.
A Starting Point
If you would like a template, the four headings above are sufficient to begin. Set aside an hour this week, fill in the blanks for the role that would hurt most to lose, and put the result in front of a second pair of eyes.
Businesses rarely fail because of one dramatic event. They wobble because of ordinary absences meeting extraordinary gaps in documentation. One page, written calmly in advance, closes that gap for good.