Two facts, side by side. FacilitiesNet puts roughly 40% of facility management leaders over the age of 55. And the replacement pipeline behind them is thin — IFMA has been tracking the profession’s recruitment problem for years: FM is a career people arrive at sideways, rarely one they study toward, and the incoming cohort is a fraction of the outgoing one.

This isn’t one operation’s succession problem. It’s the entire industry scheduling the departure of its institutional memory inside a single decade — and the standard corporate response to it is built on a premise that’s quietly false.

The standard response, and why it runs backward

Watch how most organizations handle a senior FM’s announced retirement. Somewhere in the final ninety days, a knowledge-transfer project begins: exit interviews, a shadowing period for the successor (if one was found), and the request every retiring FM has heard — “could you document your processes before you go?”

Run the math on what that produces. Thirty years of operational knowledge — why each vendor was chosen, which asset behaves badly in August, what the inspector flagged in 2019 and how it was resolved, which PM frequencies were adjusted from the manual and why — compressed into a few weeks of interviews and a binder written by someone with one foot out the door, answering questions the successor doesn’t yet know enough to ask. The knowledge that surfaces is the knowledge that happens to come up. Everything else retires on schedule.

The premise underneath this model is that knowledge transfer is an event — something you do at the end. That premise is the failure. Thirty years of context cannot be exported in ninety days, by interview.

The premise underneath this model is that knowledge transfer is an event — something you do at the end. That premise is the failure. Thirty years of context cannot be exported in ninety days, by interview, no matter how good the interviewer. The transfer window is the career, not its final quarter.

The same retirement, in an operation where the system was learning all along

Now rerun the retirement in an operation built differently — where the senior FM spent the last several years working through infrastructure that records as a side effect of operating.

STAGE 1 Operational History

Every work order touched logs the asset, vendor, cost, and findings, ensuring asset histories are queryable records rather than memory.

STAGE 2 Cumulative Judgment

Vendor judgments are scores accumulated from every engagement based on response times, completion quality, and invoice accuracy.

STAGE 3 Automated Compliance

The compliance calendar runs itself. Every inspection, certificate, and regulatory deadline is decoupled from human memory.

The PM frequencies she adjusted from the manufacturer’s defaults exist as templates in the system, with the adjustment dated and the reasoning attached. The compliance calendar — every inspection, every certificate, every regulatory deadline across multi-site facility management — runs itself, because it never depended on her remembering.

Her retirement party is in the same month. The operational difference: her successor inherits a running system on day one — and the ninety-day transition gets spent on the things that genuinely require a human handoff, the politics and the relationships, instead of on archaeology. The knowledge-transfer project doesn’t fail. It was never needed, because the transfer happened continuously, invisibly, for years.

What changes at the industry scale

Here’s why this matters beyond any single operation. The hiring market cannot solve a 40%-over-55 problem — the replacement humans don’t exist in sufficient numbers, and won’t by the time they’re needed. Which means the industry-level question isn’t “how do we recruit faster.” It’s “how much of what senior FMs do can be made transferable — held in systems rather than in tenure?”

The honest answer from our interviews: a great deal of it. The judgment — repair versus replace, vendor negotiation, capital strategy — stays human, and stays scarce. But the operational knowledge underneath the judgment — the histories, the schedules, the vendor records, the compliance state — is exactly the layer that systems hold better than people anyway, because systems don’t retire, don’t take their contact list with them, and don’t compress thirty years into a binder. Building that layer as standard infrastructure is the bet Sweven FM made, because the retirement math made it unavoidable.

The Succession Question

So the planning question for your operation isn’t whether your senior people will leave — the demographics already answered that. It’s this: on the day they announce it, will the system already know what they know?

Sources: