Every school facilities department has that person. They've been there for fifteen or twenty years. They know where every shutoff valve is located. They know that the boiler in Building C needs to be bled in September before it'll run efficiently. They know that the circuit labeled "Panel 3-D" in the electrical room is actually the one that controls the gym, despite what the diagram says. They know things that are nowhere written down, because they've never needed to be — because that person is always there.
Until they retire. Or take a new job. Or go on extended leave. And then those fifteen years of operational knowledge disappear, and the team is left to rediscover it the hard way — usually during the first emergency of the new school year.
What institutional knowledge actually looks like
The phrase "institutional knowledge" sounds abstract, but in a school facilities context, it's intensely practical. It's the knowledge of how a specific building actually operates versus how it's documented to operate. The gap between those two things is often substantial — and it only grows over time as systems are modified, added, patched, and worked around without documentation being updated to match.
In most school buildings, institutional knowledge falls into three categories. The first is system knowledge: understanding how HVAC zones actually map to the building (often different from the original drawing), where non-obvious shutoffs are located, which equipment has quirks that require specific handling. The second is procedure knowledge: the correct sequence for bringing the boiler online, the workaround for the access control system that doesn't get documented because it shouldn't work this way but it does. The third is history knowledge: what's been repaired before and how, what the chronic problems are, what's been deferred and why.
The retirement wave is hitting schools hard
The timing of this problem has gotten worse. The baby boomer generation of school facilities workers is in the midst of a retirement wave that will continue for the next decade. Many of the most experienced technicians and operations leads in school districts — people who've accumulated twenty or thirty years of campus-specific knowledge — are leaving or will be leaving soon.
The replacement challenge isn't just about hiring people with the right skills — it's about getting campus-specific knowledge transferred before the experienced staff leave. That's not happening in most districts, because there's no system to capture that knowledge and no structured process to transfer it.
The cost of undocumented knowledge
The costs show up in predictable ways. New technicians take longer to respond to issues because they're spending time locating shutoffs, reading faded panel labels, and calling former colleagues for help. Mistakes get made on equipment because the quirks that experienced staff knew instinctively aren't documented anywhere. Emergency responses take longer. Vendor callbacks happen more often, at higher cost, because the team doesn't have the background to troubleshoot effectively before calling for outside help.
These costs are real but hard to quantify — which is part of why they don't get taken seriously enough. Nobody tracks the hours lost to searching for a shutoff valve that a retired technician knew by heart. Nobody counts the service calls that could have been handled in-house with the right documentation.
Making knowledge structural
The solution isn't complicated — it's just rarely prioritized until after a retirement creates a crisis. The work is to capture operational knowledge in a structured, accessible form before the people who hold it leave.
This means systematically documenting how building systems actually work — not how the original drawings say they work. It means creating procedure documents that capture the real sequence of operation, including the workarounds and exceptions that experienced staff have learned over time. It means building asset records that capture not just equipment specifications but operational history, known issues, and repair notes.
What to capture before an experienced tech leaves
- Walk the building together — document all non-obvious shutoff, access, and control locations
- Record HVAC zone mapping against the actual building layout, not the original drawing
- Document equipment quirks: startup sequences, known issues, workarounds
- Create procedure documents for seasonal operations: startup, shutdown, winterization
- Build an asset history log for major equipment: repairs, service dates, known issues
- Map vendor contacts and the specific relationships built with service companies
- Record the "three things that always break" for each building — every tech knows these
The key is that this knowledge needs to live in a system — not in a Word document on someone's desktop, not in a binder in the facilities office that no one can find, not in a shared drive folder with an inconsistent naming convention. It needs to be searchable, accessible on a phone or tablet in the field, and structured so that someone new to the campus can navigate it under pressure.
The Campus IQ approach
One of the most useful things a school facilities team can build is a living campus knowledge base — a structured, maintained repository of exactly the information a technician needs when something goes wrong. Not a static document. A living system that gets updated as procedures change, as equipment is replaced, as new issues are discovered.
The goal is that anyone on the team — including someone hired yesterday — can answer the question "how do I deal with this problem in this building" without having to find the one person who's been here the longest. That's what makes facilities knowledge structural rather than personal. And it's the difference between an operation that's resilient to staff changes and one that's perpetually vulnerable to them.
The time to start capturing that knowledge is before the retirement happens. The second-best time is after it happens and the team is dealing with the consequences. But the best programs don't wait for a crisis to motivate the work — they treat knowledge documentation as ongoing maintenance, the same way they treat filter changes and inspection schedules.