Most organisations are good at handing over work. When someone resigns, there is a checklist within a day or two: active matters, documents, passwords, the colleague who will pick up each piece. Clients get a courteous email introducing the replacement. Everyone feels the transition has been handled.
What the checklist rarely covers is the way business actually gets done. The procurement manager who rings the departing director before every tender. The client's general counsel who sends her the awkward questions first, because she will give a straight answer. The former colleague, now running a government agency, who has sent two pieces of work her way this year. None of that is in a file, and much of it isn't in the CRM either.
Months later, a large client runs a tender without inviting the firm. Nobody can point to the moment the relationship slipped, because nobody was watching it.
Formal and informal handovers
There are really two handovers when someone leaves, and organisations usually do only one of them.
The formal handover is about responsibility. Who now owns this client, this matter, this project? It is visible, it has a deadline and it is easy to check.
The informal handover is about relationships: the people who trust the departing person, the conversations that happen outside formal meetings, the contacts who would quietly follow them to their next firm. It is harder to see, and it rarely has an owner. It is also where most of the value sits.
The informal side is difficult for a simple reason. Relationships are not assigned, so they can't be reassigned. A client doesn't transfer their trust because an email told them to. Someone new has to earn it, and that takes time the notice period often doesn't allow.
Why it catches organisations out
The problem is less that departures happen than that organisations don't know, in advance, which relationships depend on whom.
Formal ownership is a poor guide. A CRM might list a partner against a client, while the relationship that keeps the work coming sits with a senior manager who speaks to the client every week. When that manager leaves, nothing in the records suggests anything has changed.
Busy accounts can mislead, too. An account with plenty of activity looks safe. But if almost all of that activity runs between one of your people and one of theirs, the organisation's hold on the client is much narrower than it seems.
And departures rarely come with much warning. Notice periods can be short. Someone leaving for a competitor may be kept away from clients altogether. Either way, there is little time to work out what needs protecting, and the response becomes guesswork.
What helps
Organisations that handle departures well tend to treat relationships as something to look after continuously, rather than something to rescue at exit time. That sounds like a large programme. In practice it comes down to a few habits.
Look before anyone resigns. Once or twice a year, go through your most important clients and ask how many of your people are in regular contact with how many of theirs. Where the answer is one and one, that is worth a conversation, however good the relationship is.
Broaden relationships while things are going well. Bringing a second colleague into a client relationship is easy as part of normal work: a joint meeting, a shared piece of work, an invitation to an event. It is much harder as a rescue effort after a resignation.
Start every handover with people, not files. When someone does leave, the first list should be the external people they are in regular contact with, how strong those relationships are and who else in the organisation already knows each of them. That turns "please introduce your replacement to your clients" into a specific plan, with priorities.
Use the notice period for introductions, not just handover notes. A departing colleague introducing a successor in person, ideally more than once, carries far more weight than a farewell email. Agree early which clients get that treatment.
Watch the months afterwards. The real test comes after the person has gone. Keep an eye on whether contact with affected clients continues at its usual rhythm, or quietly falls away. Our guide to the early warning signs of a weakening relationship covers what to look for.
An illustration
Take a fictional accounting practice where a long-serving partner announces his retirement with three months' notice. The usual response is to ask him for a list of his key clients and contacts. That list will reflect his memory and his view of what matters. It will probably miss the people he deals with informally, and it won't say whether colleagues already know them.
A better starting point is the activity itself. His email and calendar patterns show which external people he is in regular contact with, and how strong those connections are. Set against everyone else's activity, that shows which clients already have other colleagues involved and which have nobody.
Suppose most of his clients turn out to be well covered. Two family businesses, and a referral source at a law firm, are known only by him. Those three become the focus of his last three months, each with joint meetings and a clear new lead. The effort goes where the exposure is, rather than being spread thinly across everyone he ever emailed.
Seeing it in advance
That kind of review is far easier when relationships are visible without anyone compiling them by hand. Inhere builds that picture from everyday email and meetings. Its Coverage view groups accounts by how many people are in touch on each side, and shows which accounts would go dark if a particular colleague left, and who else knows someone there. Flow helps in the months afterwards, by bringing forward relationships that have gone quiet against their usual rhythm.
None of it replaces the human part. Someone still has to make the introductions, take the meetings and earn the client's trust. But the question leaders most need answered, which relationships would leave with this person, is one they can answer before the resignation letter rather than after it.
