How to hand off a client without losing context starts before anyone resigns.

A month of notice sounds like plenty of time to hand over an account, and then the handover meeting gets booked for the last Thursday. Say the person leaving has looked after your cleaning and security contract with a business park operator for six years, across four sites, and writes a handover document the weekend before. It is a decent document. Whoever inherits the account reads it on the Friday.

The document holds what anyone would think to write down: the contract and its four sites, plus a page of contacts and open issues. What it leaves out is everything that had become normal to the person writing it. The second site runs a different security rota because of a complaint two winters ago that never went further than a phone call. The operator's facilities lead agreed a price review in a corridor and is still waiting on the paperwork. All of that was known, by one person, and none of it ever needed writing down while that person was in the building.

Why the handover meeting comes too late

A handover meeting collects what the outgoing person remembers is unusual, and six years in, very little feels unusual to them. The gaps turn up in the second month. The facilities lead asks how the price review is going, the new account manager has never heard of it, and the facilities lead starts to wonder what else got lost.

Some companies pay for this gap with a salary. Account coordinator and client services coordinator are among the job titles OCTYN reads as a signal, because the postings describe a person whose whole job is reassembling context that the work never kept.

A record the work writes into

What survives a resignation is one record per client that the work writes into as it happens: the rota change with its date and the complaint behind it, the price conversation with who said what. Then a handover is mostly reading, and the person taking over can ask why the second site is different and get an answer that says where it came from. That is what a company brain is for.

OCTYN runs its own planning on a system built this way, called Brain, over more than twenty codebases whose context would otherwise be rebuilt every morning. Two lessons from running it carry over to client accounts. A blended answer costs more than a missing one. In Brain that means two projects merged into a single confident reply, and on an account it would be the second site's rota quoted for the first. The other is that facts go stale without saying so. The Brain case study calls a fact that was true in July and recalled in September with no sense of its age worse than no memory at all, so every entry carries its date and its source.

What the new account manager still decides

The record carries the history and nothing more. Whether to honour a price review agreed in a corridor, and how to introduce yourself to a facilities lead who liked the last person, are judgement calls that stay with the person taking over. Those calls come out better when that person starts with six years of dated history in front of them. The entry on human in the loop covers where that line usually sits.

Keep the Thursday meeting in the diary anyway. It will be shorter.