Handing over a facilities role without losing institutional knowledge

A facilities manager who's been in post for several years accumulates a huge amount of knowledge that never made it into any system — which valve actually controls which zone despite what the label says, which contractor is reliable versus which one just answers the phone quickly, which asset has a known quirk that isn't in any manual. None of that is written down anywhere, because writing it down was never forced by any process, and it walks out the door the day they leave.

Why the good handover document is never enough on its own

A conscientious departing manager will often write a handover document, and it genuinely helps — but a document written in the final weeks of a role is trying to capture years of accumulated context under time pressure, and it will always miss things the writer didn't think to include because they'd stopped noticing them as noteworthy. The knowledge that's easiest to forget to write down is exactly the knowledge that's become second nature.

The better fix is continuous, not a one-off document

The more reliable protection against this isn't a better handover document — it's not needing one to be comprehensive in the first place, because the knowledge already lives somewhere durable rather than in one person's head. An asset register with genuine detail, a contractor register with real notes on reliability, and job records that capture what was actually found and done all reduce how much any single handover has to carry.

• –Capture quirks and exceptions in the asset record at the time they're discovered, not from memory months later
• –Record contractor reliability notes as part of the ongoing register, not as a verbal aside passed between managers
• –Keep site-specific access and safety knowledge written down somewhere every relevant person can actually find it
• –Treat a handover document as a summary and index of what's already recorded, not the sole repository of it

What a genuinely useful handover period looks like

Where an overlap between outgoing and incoming manager is possible, the most useful thing to do with it isn't a document review — it's walking the actual sites together, going through a sample of the trickier assets and contractors in person, and letting the incoming manager ask the questions that only occur to them once they're standing in front of the thing in question. This connects to the same continuity challenge that shows up whenever a multi-site team structure has to absorb staff changes without losing coverage.

Even without an overlap, a system that already holds detailed asset and contractor information gives an incoming manager a genuine starting point, rather than a blank slate and a single document written under pressure in someone's final fortnight.

Four weeks is not enough for eight years

A handover document written in a notice period captures what the departing manager thinks to write down, which is reliably the formal part of the job — contracts, schedules, key contacts. What it misses is the accumulated informal knowledge that actually makes the estate run, and which is invisible precisely because it has been internalised.

The realistic protection is not a better handover document but a job that has been externalising its knowledge continuously: asset data in a register rather than a memory, contractor arrangements recorded rather than habitual, decisions captured with their rationale. Estates that do that have short handovers because there is less that only one person knows.

Common mistakes

• –Starting handover at resignation rather than treating documentation as continuous
• –Capturing formal arrangements and missing the informal knowledge that matters daily
• –No overlap between outgoing and incoming, so questions cannot be asked
• –Contractor relationships held personally rather than institutionally
• –Undocumented local arrangements that only surface when they fail
• –Treating the document as the deliverable rather than the successor's ability to operate