Handovers happen constantly in service businesses. Account managers leave, teams get restructured, work moves from the person who sold it to the people who deliver it, and a client used to dealing with one familiar face is asked to start again with someone new. The work itself usually transfers cleanly enough. The relationship is the part that gets dropped, because nobody is holding it while the change is happening.
Clients rarely complain about a handover directly. They go slower to reply, start collecting comparison quotes, or mention that suppliers are being reviewed at the end of the quarter. Treating the relationship as something that has to be transferred alongside the files, with the same care given to deadlines and deliverables, is what keeps that from happening.
What leaves with the person, not the file
Project notes record decisions and almost never record the reasoning, so whoever picks the account up inherits an account history without the context that made it make sense. That gap is expensive on its own, and it sits on top of everything else a departure costs; the cost of replacing an experienced employee has been put at more than a full year’s salary once lost output is counted. The details clients actually care about are the unwritten ones, such as which stakeholder has to be copied into everything, which topic caused an argument in March, and which deadline is genuinely fixed rather than aspirational.
Sectors where continuity is written into the rules
Regulated services can’t treat a change of provider as an internal matter, because the person receiving the service has protections attached to them. Continuity requirements around transferring fostering agencies exist for that reason, since a child’s placement, relationships and existing plan have to hold together while the responsible organisation changes underneath. Commercial work carries no equivalent duty, but the logic travels. Ask what your client stands to lose if the change is handled badly, then design the process backwards from that answer.
Telling the client before they work it out
Tell the client yourself, before an out-of-office reply does it for you. Someone who suspects a change is happening and hasn’t been told starts assuming the worst version of it, which is a bad position to open a new working relationship from. A short note ahead of the change should cover:
- who is taking over, and from what date
- what stays the same, including scope, pricing, reporting and billing contacts
- who to reach during the transition if something urgent lands
- what the first conversation with the new contact will cover
Overlap does more than documentation
Two weeks of both people being visible does more for the relationship than any handover pack. The outgoing contact introduces the new one in a live conversation rather than an email, sits quietly in the first meeting, and says plainly that they’re confident in whoever is taking over. Professional services formalise a version of this. When firms merge, clients are invited to transfer their instructions and agree fresh terms rather than being moved across quietly, and that deliberate re-consent is worth copying even where nothing obliges you to ask for it.
Checking that it landed
Put a review in the diary four to six weeks after the change and ask the client directly whether anything has slipped since. Most handover problems show up in that window as small friction, a missed report or a question answered slowly, long before they turn into a formal complaint, which makes them cheap to fix while goodwill is still intact. A handover has worked when the new contact had enough context to be useful in their first week and the client was given a reason to trust them, and both of those are built before the previous contact walks out of the building.
