Cover That Holds: A One-Page Continuity Plan for UK Service Teams
Photo: Nicholas Mutton, CC BY-SA 2.0, via Wikimedia Commons
Most small UK service firms do not need a bound business continuity manual. They need a single page that answers a practical question: if the person who usually handles a client, a supplier or a system is unavailable, who else knows what to do? The test is not whether a plan exists. It is whether a colleague can act on it without a trail of phone calls.
Begin with the work that cannot wait
Start by listing the activities that would cause immediate difficulty if they stalled for five working days. For a professional services firm this may include client deliverables, invoicing, payroll, supplier orders, statutory filings and any commitments made in a proposal. For each, ask the 'who else knows?' question. If the answer is a single name, the firm has a key-person dependency. Some dependencies are unavoidable. Undocumented ones are the risk.
Four columns are enough
Keep the core of the plan to four columns: activity, usual owner, named backup and where the instructions live. The fourth column matters most. A backup who has to search a shared drive for a process note is not a backup in any useful sense. The plan should point to a short handover note, a supplier record or a password manager entry, not to a general instruction to 'ask the team'.
Client handover notes that can be used
For each client, maintain a concise note: scope, main contacts, deliverable dates, current issues, billing arrangements and the location of working files. The note should be short enough to read in ten minutes and specific enough for a colleague to send a sensible email or attend a meeting. Update it when the scope changes, not once a year. The test is whether someone outside the account can pick it up on a Monday morning and keep the week moving.
Supplier contacts and access records
List critical suppliers with a named contact, account number, renewal date and what the supplier provides. Record where contracts and order confirmations are stored. For logins, use a business password manager with emergency access rather than a spreadsheet. Avoid shared credentials where individual accounts are possible; use multi-factor authentication and least-privilege access. The plan should say who can approve access in an emergency and how that approval is recorded. Data protection obligations do not pause because someone is on leave.
Decide who can make decisions
Continuity is not only about tasks. It is also about authority. Record who can approve expenditure, sign off work, contact a client about a delay and make a judgment call on a supplier issue. Set an escalation route for matters above that threshold. In a small team, one named deputy per function is usually enough, provided the deputy knows they are the deputy. Ambiguity here causes more delay than missing process notes.
Test the page, not the manual
Twice a year, run a thirty-minute exercise. Choose a scenario: the account lead is off sick for a week; the operations manager cannot access email; a key supplier contact has left. Ask the backup to find the relevant note, access the necessary systems and explain the first three actions they would take. Record any gaps on the page itself. Do not turn the exercise into a full simulation. The aim is to confirm that the plan is usable, not to rehearse every eventuality.
Keep it current with triggers
Review the page when a client joins or leaves, when a supplier changes, when a system is replaced or when a member of staff changes role. Give one person responsibility for the page and a diary date for review. Store it where the team can reach it, and keep a secure offline copy if access to systems is part of the scenario. A plan that lives only in one person's inbox has failed the first test.
A one-page plan will not cover every crisis. It will cover the common ones: illness, leave, resignation and a sudden loss of access. For most UK service firms, that is the practical standard. If the page cannot be read in ten minutes and acted on in thirty, it is too long. In 2026, with lean teams and client expectations of continuity, the question is not whether to have a plan but whether the plan would survive the absence of the person who wrote it. The principle is simple: the firm should remain present even when a particular person is not.
