When a Building’s History Exists Only in Someone’s Head
Buildings rarely fail because nobody cares about operations. More often, they become difficult to operate because critical knowledge was never transferred from the people who held it. A facilities manager remembers which breaker feeds a panel. An electrician knows why a setting was changed. An IT lead can trace a network drop to a switch port without opening a diagram. The building works, so the knowledge remains informal.
That arrangement can last for years. Then the experienced employee retires, a contractor leaves, or an urgent incident exposes a gap. Suddenly, the team is not only repairing a problem. It is trying to discover how the building was built, modified, and operated in the first place.
The Cost of Missing History
In a recent Built, Wired & Secured conversation, James Rogers described a maintenance manager with 30 years in the same building. The manager could identify equipment and pathways from memory. After he retired on a Friday, a power blip brought down the network on Monday.
The incoming employee could not find the transfer switch. It was not shown on any drawing. Locating it took four hours, even though the eventual repair required only a two-minute switch throw. The building incurred approximately $10,000 in emergency callouts, overtime, and expedited parts. That figure did not include the frustration experienced by tenants. The new employee also spent 45 minutes looking for the panel room because the door was not labeled.
This is the documentation deficit in practical terms. The building did not necessarily need a sophisticated new system. It needed basic facts to be available to more than one person.
Documentation Erodes One Small Change at a Time
Employee turnover creates an obvious handoff problem, but the slower threat is undocumented change. A cable is rerouted to make space for a server. A contractor modifies a breaker setting after a nuisance trip. A panel is derated for a new load. The work solves an immediate problem, but nobody updates the drawing.
One omission may not create an incident. Ten years of omissions can make the official record unreliable. When a tenant reports an outage and the team asks for current as-built drawings, “we have something, but it is not exactly current” becomes a warning that the response will involve guesswork.
A drawing that no longer reflects the building is more than an administrative inconvenience. It can send technicians down the wrong path, delay restoration, increase emergency labor, and introduce safety concerns. It can also hide dependencies between systems that are normally managed separately.
How a Small Unknown Becomes a Building-Wide Problem
The episode includes an example of a panel that had been derated years earlier. The change was never marked. Later, more equipment was added, overloading the panel and causing it to trip. HVAC service was lost for an entire floor during the summer.
Tenants experienced the result as an 85-degree office and a network outage. They did not need to understand the panel history to feel the impact. The property manager then had to explain why what appeared to be a simple maintenance task had become a larger incident.
That is why documentation should be treated as an operational control, not just a records-management task. Accurate information helps the team understand what changed, where dependencies exist, and which response steps are appropriate before work begins.
Start With the Systems That Matter Most
Trying to document every asset, cable, valve, setting, and procedure at once is likely to overwhelm the team. James recommends starting with the critical 20 percent: the systems that could bring the building to its knees if they fail.
- Power systems and critical switching equipment
- Network topology and important connectivity paths
- Life safety systems
- Dependencies between power, network, HVAC, and other building systems
This approach creates a practical risk-based starting point. The objective is not to produce a perfect archive before anyone can use it. The objective is to make the most consequential information accurate and accessible first.
Capture the How and the Who
Physical diagrams are important, but they are only part of a usable operating record. Michael Harrington points out that teams also need to know how to access a room, which vendor supports a system, and who to contact during an emergency.
Those details often remain tribal knowledge because they are not viewed as engineering information. In a real incident, however, they can determine whether the team moves quickly or spends hours searching. A useful record should answer three questions: What is the system? How do we reach or operate it? Who can help when the internal team needs support?
Turn Documentation Into a Habit
Documentation usually loses to the urgent task in front of the team. The answer is to attach it to work that is already happening. After a significant change, perform a short after-action review. Record what was done, what was learned, and which drawings or procedures need to be updated.
The review may take only about 10 minutes, but consistency matters more than scale. Vendor agreements can reinforce the process by requiring contractors to submit updated as-built drawings before payment. The people who performed the work are responsible for documenting the result, rather than leaving the property team to reconstruct it later.
Transfer Knowledge Before Departure
When a veteran employee is leaving, conduct a knowledge audit. Walk through the building system by system. Ask the employee to identify equipment, pathways, settings, access requirements, vendor relationships, and exceptions that are not shown on the drawings. Record the walkthrough when possible.
In the example from the episode, a walkthrough uncovered a secondary waterline that no one else knew existed. That discovery illustrates why a structured conversation is valuable: experienced people often carry knowledge they do not realize is missing from the official record.
Knowledge transfer should also be shared across the team. Shadowing, cross-training, and rotating responsibilities reduce the risk that one person becomes the only keeper of a critical process. The goal is not to replace experience. It is to make experience available when the original expert is unavailable.
A Practical First Week
Owners and operators can begin without buying a new platform. This week, walk the building with the most experienced person available and note what is not documented. Select one critical system and document it completely enough for another qualified team member to understand it. Then schedule recurring time to review and update the records.
A shared drive with well-named folders is better than waiting for a perfect software system. The important decision is to establish a dependable place for the information and a clear expectation that changes will be recorded.
Protect the Building’s Memory
Documentation is often described as paperwork, but its real purpose is continuity. It preserves the history behind current conditions, shortens the path from failure to diagnosis, and reduces the cost of rediscovering facts under pressure.
The best day in operations is the day nobody notices. Small documentation habits help keep it that way. To hear the full discussion about building memory, tribal knowledge, and practical knowledge transfer, listen to this episode of Built, Wired & Secured.