Cover Without Collapse: Rehearsing a Key-Person Swap Before a UK Client Asks
Continuity is seldom tested at a convenient moment. A named account lead falls ill, a specialist resigns, or a peak in demand exposes that too much knowledge sits with one person. In each case, the client expects the service to continue as though nothing has changed. For UK service suppliers, the answer is not a curriculum vitae kept in a drawer. It is a substitution plan that has been written down, approved where necessary, and rehearsed before a real absence forces the issue.
Begin at the contract boundary
A stand-in arrangement starts with the agreement, not with an internal list of willing colleagues. Before nominating a substitute, the supplier should establish whether the contract permits substitution, whether the client must approve it, and what notice is required. Some commercial agreements allow a suitably qualified replacement with prior written consent. Public sector contracts may add vetting, security clearance, conflict-of-interest checks, or named-person requirements. A back-up team that cannot satisfy those conditions is not a back-up at all.
The same discipline applies to access. If the substitute will need to use client systems, handle personal data, or attend secured premises, the supplier should confirm the permissions route in advance. It is better to discover a missing authorisation during a rehearsal than on the morning of an unplanned absence. In late 2026, UK buyers are also more likely to ask for evidence of continuity planning during supplier reviews, so the contract file and the operational file should tell the same story.
What belongs in the substitution file
A useful substitution file is compact, current, and role-specific. It should include the role profile and the minimum competencies required, together with evidence that the proposed substitute meets them. Relevant qualifications, training records, professional memberships, and any clearances should be listed with review dates. The file should also state what the substitute is not authorised to do, particularly where financial approvals, contractual commitments, or regulatory decisions are reserved to a named post-holder.
Access permissions deserve their own section. This should cover client systems, shared drives, email groups, building passes, and any third-party portals. Each entry should identify who grants the permission, how long it takes, and how it will be removed when the cover ends. A substitute who can enter a system but cannot be removed from it cleanly is a security risk, not a continuity solution.
Handover notes should be written for the substitute rather than for the incumbent. They should summarise live work, upcoming deadlines, client sensitivities, decision logs, and open actions. Client notification steps belong in the file too: who inside the supplier approves the message, who contacts the client, what is said, and what confirmation is recorded. The pack should not become a copy of the client's data. It should contain enough information to operate safely, with references to controlled sources rather than unnecessary duplication.
Run a dry run with limits
A rehearsal should test the plan without disturbing the service. A tabletop exercise is a sensible first step: the incumbent, substitute, account manager, and a compliance or security representative walk through a simulated absence and identify where the plan fails. A controlled live exercise can follow where the contract and client relationship allow it. The substitute might shadow the account for a day, handle a low-risk task under supervision, or take part in an internal review of open actions.
The dry run should test more than knowledge. It should test time. How long does access take to arrange? How quickly can the client be notified? Can the substitute find the latest handover note without asking the incumbent? Are contact details current? The supplier should record the date, participants, tasks observed, gaps found, and actions assigned. That record becomes useful evidence of diligence, provided it is kept securely and does not expose client-confidential material beyond those who need it.
Notify without surprising the client
Clients dislike discovering a substitution through a routine email signature change. Where the contract requires notification or approval, the supplier should follow the agreed route precisely. Where it does not, good practice still favours a short, factual message explaining who is covering, for how long, what authority the substitute holds, and how to reach the usual escalation contact. The message should avoid overpromising. A substitute is not automatically a clone of the incumbent, and clients respect a plan that states its limits.
For public sector work, the notification route may sit within a wider contract management process. The supplier should check whether the client's contract manager, security team, or procurement function needs to be informed. The same applies to subcontractors: a substitute supplied by a third party may need separate approval and vetting.
Prove continuity without breaching trust
Evidence of a rehearsal should demonstrate control, not curiosity. A short log showing that the plan was tested, that access was verified, that the client notification route was checked, and that actions were closed is usually sufficient. Confidential client material should stay in approved systems and be shared only with authorised personnel. Redacted extracts may be appropriate for internal audit, but the supplier should not create a parallel copy of sensitive records simply to prove that it is prepared.
The final step is refreshment. A substitution file that is not reviewed becomes a historical document. The supplier should set a review interval, update it when roles, systems, or client contacts change, and rerun a limited exercise after any significant restructure. The aim is not to manufacture anxiety about absence. It is to make sure that when a UK client asks who will carry the work if a key person is unavailable, the answer is already written down, approved, and tested.
