When your best manager leaves, three things go with them: the actions they do without thinking, the exceptions they handle from memory and the reasons behind your past decisions. Hiring gets sorted out in weeks. These three disappear in a day if nobody has made them visible. The right time to inventory them is not the last day of the notice period, it is today.
The Monday nobody knows
A fictional example. The manager of your second site tells you on a Friday that they are leaving the group at the end of the month. You start looking for a successor. On Monday, the temp covering opens up. The butcher's order does not go out, because the order was always sent before 10 a.m. by text to a number she does not have. The wine supplier delivers late: the manager had a verbal arrangement on delivery windows. A team member says "we usually don't do the dish pit before the rush," which was written down nowhere.
None of it is serious on its own. But within three weeks, everything the manager did without saying so resurfaces as a string of small incidents.
The three layers of what leaves
| Layer | Example | Where it lives | Risk at departure |
|---|---|---|---|
| What is written down | Receiving sheet, opening checklist | Binder, file, tool | Low if it is up to date |
| What is said but not written | Agreed delivery window, service routine | Team memory, word of mouth | Medium: you can recover it by asking questions |
| What has never been said | Why you switched suppliers, why a dish is not served on Sundays | The manager's head | High: nobody can reconstruct it |
The third layer is the most expensive, because you do not know it is missing.
Why a manager's departure hurts so much
- The reasons are never written down. Actions end up in procedures, the motives behind decisions do not. The successor reopens debates that were already settled.
- Arrangements are personal. A supplier or an employee has an agreement with a person, not with the role.
- The manager compensates in silence. They cover gaps in the system with their presence, and nobody sees the gaps while they are there.
- The notice period is short and busy. The time goes into finishing the schedule, not into handing over.
A handover in six steps
- Start the inventory as soon as the news breaks. Half an hour with the manager, using the three columns above, with you as the second person asking the naive questions.
- List the recent exceptions. The last three cases where they did things differently. For each: the rule, the exception, the reason, who approved it.
- Make the rounds of contacts. Suppliers, maintenance providers, temp agencies: who calls whom, for what, with which arrangement in place.
- Work through situations, not documents. A delivery, an opening and a peak service where the successor watches, then does, with the outgoing manager correcting. Half a day per situation.
- Turn what keeps coming up into short sheets. Assigned to a role (site manager), not to a person.
- Review after a month. The successor says what they were missing. You fill in the gaps, and you understand what should have been written down earlier.
Common mistakes
- Asking for a single "handover document." It will be too long to write and too vague to read. Several short sheets work better.
- Waiting for the last day. The manager's mind is elsewhere, the team is tense.
- Treating the departure as a betrayal. You lose the information, and the goodwill of the person leaving.
- Forgetting the verbal agreements with suppliers. They hold because of one person and fall apart with them.
To go beyond departures, the underlying method is in how many times to repeat an instruction before changing the system. If the issue is knowledge lost across the whole team, also read the hidden cost of lost knowledge in turnover. To check whether a successor is ready to take the site, see how to know whether a manager is ready to run a location.
What to measure
- The number of exceptions or arrangements discovered after the departure. Each discovery is something the inventory missed.
- The number of questions the successor has to ask the outgoing manager (or you) during their first month. It should drop week after week.
- The share of the site's instructions assigned to a role rather than a person. You can read it simply by going through the sheets.
Where Tsuno comes in
Tsuno keeps what it has been told, dated and viewable: standards, procedures, decisions and their reasons, observed facts, actions taken. When a manager changes, their successor asks Tsuno in plain language ("Why do we do it this way with this supplier?") and gets an answer based on what was recorded, with what supports it. If the information was never entered, Tsuno says so instead of making something up. It does not rate the manager and does not replace the human handover: it keeps the handover from being the only trace. Details on the Tsuno solution page.
Key takeaways
What leaves with a manager is not what they know how to do, it is what they never had to say. Inventory the three layers now, hand over through real situations and assign every instruction to a role.
Frequently asked questions
What should I do as soon as my manager announces their departure?
Start with an inventory in three columns: what is written down, what is said but not written, what has never been said. Then plan handovers around real situations (a delivery, an opening, a difficult service) rather than one long end-of-contract meeting.
How do I capture the exceptions the manager handles from memory?
Ask them to walk you through the last three cases where they did things differently from the rule. For each case, note the rule, the exception, the reason and who approved it. The reasons are what disappear first, not the actions.
Can a successor learn everything in a two-week notice period?
Not everything. The goal of the notice period is to pass on the situations that keep the site running (suppliers, team trade-offs, special cases) and to leave traces anyone can consult. The rest gets built afterward, with supports that no longer depend on the outgoing manager being there.
Is it unfair to ask a departing manager to document everything?
No, as long as you present it as handing over their work, not as a check on them. It is better to do it before any departure: documenting during normal operations, in small touches, avoids asking for everything in the last month.
How do we avoid depending so much on a single manager next time?
By assigning standards, instructions and decisions to roles rather than people, and by keeping the reason behind important trade-offs. The manager brings their judgment, but the site no longer rests on their memory alone.
Keep reading
Pass it on without repeating
Explain it once: how to keep a restaurant standard alive
A living standard fits in four lines, belongs to a role, is updated in one place and is checked on the floor. Here is the full cycle, start to finish.
Pass it on without repeating
How often to repeat an instruction before changing the system?
After the third reminder for the same instruction, the problem is no longer the person but the medium. Here is how to decide and what to use instead.
Pass it on without repeating
The real problem with the restaurant onboarding handbook
A handbook read on Monday is forgotten by Thursday. Split it into three layers and bring each piece of information back at the moment the task happens.