The Vendor Knows Your Network Better Than You Do

At the end of a managed services contract, the documentation transferred cleanly. Topology, configurations, escalation paths, run books — all of it arrived, all of it accurate, all of it describing the network as designed.

What did not transfer was the set of things the vendor’s engineers knew about how it behaved. Which links degraded before they failed. Which alarms were reliably meaningless. Which site had to be touched in a particular order, and why.

Two kinds of knowledge

The first kind is written down because it can be. It survives a handover because it exists independently of the people who hold it. The second kind is produced by repetition — by being the team that has restored the same segment forty times — and it lives in judgement rather than in documents.

For the duration of the contract this is invisible, and sensibly so: the vendor is being paid to hold that knowledge. It becomes visible only at the boundary, when the work returns and the new team begins rediscovering, incident by incident, what the previous one had already learned.

The cost is real but it is not in the contract. It is in the eighteen months afterwards, and it lands on the operation, not on the decision that created it.