Who Else Holds the Pen? Testing Continuity in UK Service Relationships

Most buyers of professional and business services have heard the assurance. The account is led by a particular partner or manager, but the client is told not to worry: someone will step in if needed. The sentence is offered as comfort. It should be treated as a question. Who, precisely, will step in? What do they know? What may they decide? How will they have learned enough to act without asking the client to start again?

Key-person risk is not a remote concern. It appears when a lead adviser resigns, when a manager is on long-term leave, when a specialist is seconded to another project, or when a supplier reorganises its teams. In each case, the client discovers whether continuity was designed or merely assumed. The difference is rarely visible in normal service. It becomes visible at the point of disruption, which is the worst time to test it.

The weakness of the step-in assurance

An assurance is not a control. It rests on availability, memory and goodwill. Those are useful qualities in a person, but they are not substitutes for a system. If the only person who understands the client's history, obligations and open decisions is the named contact, the supplier has built a single point of failure. The client is exposed even if the service has been good for years.

This is a governance issue as much as a service issue. Boards and senior buyers are accustomed to reviewing financial exposure, regulatory risk and supplier concentration. Key-person risk belongs in the same conversation. It affects the reliability of advice, the speed of decisions and the cost of recovery when a relationship is disrupted. A supplier that cannot demonstrate continuity is asking the client to carry a risk that the supplier should be managing.

Four tests of genuine continuity

1. A named deputy with a working role

A nominated deputy is not enough. The deputy should have worked on the account, attended relevant meetings and have access to the same records. Buyers should ask for the name, the role and the last occasion on which that person acted for the client. If the answer is theoretical, the continuity is theoretical too.

2. Documented context that is maintained

The second name on the file should be able to answer basic questions without calling the first. That requires an account record that captures decisions, rationale, obligations, stakeholder preferences, open risks and upcoming deadlines. It must be maintained as work progresses, not reconstructed after a resignation. Buyers can ask to see the structure of that record, even if they do not need to read every entry. The existence of a template is not proof. The proof is that it is used.

3. Decision rights that are delegated in practice

Continuity fails when the deputy knows the history but cannot act. Buyers should ask what the deputy may approve, sign or commit without escalation. They should also ask how quickly authority can be transferred when the named contact is unavailable. A supplier that requires every decision to pass through one person has not designed continuity; it has designed a queue.

4. Handover discipline with clear triggers

Handovers should be triggered by events, not arranged in a hurry after them. Planned leave, sickness, resignation, role change and team reorganisation should each have a process. The process should include a written handover, a client introduction where appropriate, and a check that the receiving person understands the current position. Buyers should ask when the last handover took place and what changed as a result.

The second name should be on the file

A simple procurement question exposes most of the issue: who is the second name on the file? If the supplier cannot answer immediately, the client has learned something useful. If the supplier names someone who has never met the client or never worked on the account, the assurance is weaker than it sounded.

The question is not an accusation. Good suppliers will have an answer because they have thought about cover. They will be able to explain where the deputy sits, what they know and how they would take over. They may also be honest that some specialist knowledge is concentrated, and set out how they would manage that concentration. Candour is more valuable than a confident promise.

Questions for procurement and board oversight

• Who is the named deputy for each critical role, and when did they last act for the client?
• What documentation would a replacement need, and who is responsible for keeping it current?
• What decisions can the deputy make without escalation, and what must wait?
• How are handovers triggered, recorded and reviewed?
• What happens to the client relationship during long-term leave or a resignation?
• Does the supplier's business continuity plan address key-person loss, not just premises and technology?
• Are continuity arrangements reviewed at contract renewal or at least annually?

Proportionate, not bureaucratic

Continuity does not require a heavy apparatus for every account. The effort should match the risk. A routine service may need a named deputy and a shared record. A critical service with regulatory deadlines, complex decisions or significant financial exposure may need delegated authority, tested handovers and board-level reporting. The principle is the same: continuity should be designed before it is needed.

Buyers often ask suppliers to demonstrate capability at the point of selection. They should also ask how that capability survives the absence of the person who demonstrated it. The second name on the file is a better indicator of resilience than the first name on the pitch.