Ask most businesses what would happen if the person who understands their technology disappeared tomorrow, and the honest answer is a wince. The knowledge lives in someone’s head — how the systems work, why decisions were made, where the bodies are buried — and it has never been written down. Clean technology handover is the discipline that closes that gap. Most businesses never have it, not because it is hard, but because there is never an urgent reason to do it until it is too late.
The gap between what’s documented and what’s known
Every business runs on knowledge, and technology knowledge is especially prone to living in people rather than documents. The person who set it up knows how it fits together, what is fragile, why something was done a particular way, which warnings to ignore and which to heed. None of that is written anywhere, because while the person is there, it does not need to be. The gap between what the business has documented and what its people actually know is precisely the measure of its risk — and it is invisible right up until the moment the knowledge walks out the door.
This is the substance of a bus factor of one: the risk is not really about people leaving, it is about knowledge that exists only in their heads. Handover is how you move knowledge out of heads and into the business.
Free · 4 minutes
If your most senior engineer left tomorrow, would anyone still understand the system?
Fourteen questions on documentation, dependencies, and the gap between how the architecture works and how many people know it. Banded finding on screen, full sheet by email.
What clean handover actually contains
Clean handover is not a single document; it is the state in which the business could continue and adapt its technology without any one specific person. In practice that means a few things exist. A clear picture of what the technology is — the systems, what they do, how they connect. Access to everything, held by the business rather than locked in one person’s accounts. Documentation of how things work and how to run and maintain them, in enough detail that a competent newcomer could pick it up. A record of the important decisions and why they were made, so the reasoning is not lost with the person. And knowledge of the dependencies and the fragile points — what to be careful of. Together these mean the technology is understood by the business, not just by an individual within it.
Why most businesses never have it
Clean handover is rare for a simple reason: there is never an urgent, visible reason to create it. While the key person is present, everything works, so documenting their knowledge feels like overhead with no payoff. It is always the thing to do later. Then the person leaves — or a CTO departs, the scenario in what happens when the CTO leaves, or an agency walks away without a proper handover — and the business discovers, too late, that the knowledge left with them. The cost was invisible right up until it was enormous.
How to close the gap
The work is to create the handover state while the knowledge is still available, rather than trying to reconstruct it after the person has gone. It does not have to be done all at once or to perfection; even a structured effort to capture the most critical knowledge dramatically reduces the risk. The key is to treat it as ongoing hygiene — knowledge captured as it is created — rather than a one-off panic triggered by a resignation. A business that does this routinely is one that can lose anyone and keep running.
Bus factor risk is the gap between what’s documented and what’s in someone’s head. This is how to close it before it closes on you. We will work out where your knowledge is dangerously concentrated and how to capture it.
Start a ConversationFree interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Can you trust the architecture you have?
Architecture diagrams rarely show the reality of how systems actually operate. An independent review establishes what is really there.