Show Notes
When building knowledge walks out the door
A building can appear to run smoothly until the person who understands its hidden dependencies leaves. The episode opens with a familiar risk: after a building engineer retires, third-floor VAV boxes stop responding. The panel schedules do not help, and nobody knows which controller feeds the zone. A repair that should take two hours becomes a three-day investigation, overtime expense, and a tenant losing patience. This is the documentation void: essential knowledge exists only in people’s memories.
That void creates a hidden single point of failure. Building operations depend on interconnected systems and past decisions that are easy to overlook while experienced staff remain available. When they leave, routine maintenance can become emergency discovery. The impact includes more than contractor invoices; tenants may lose confidence in the team responsible for keeping the property dependable.
Why drawings and manuals can mislead
Documents may exist and still fail when they describe an earlier version of the building. One example involves a fire alarm panel replaced during a retrofit. The as-built drawings still identified the old panel. When the new panel developed ground faults, a technician spent half a day tracing circuits that no longer existed while tenants heard repeated alarm chirps. Incorrect documentation can slow diagnosis precisely when accurate information matters most.
Vendor manuals present another risk. A chiller plant’s actual sequence of operations may differ from the generic “typical sequence” in its manual. A controls technician customized the programming and later left. Without a record of those changes, the building must pay a controls contractor to reverse-engineer a system it already owns. The speakers cite an invoice of roughly $4,000 for figuring out information that should have been in the O&M manual. If changes are not captured as they happen, the same discovery cost can recur.
Why documentation gets neglected
Operations teams face immediate demands: when there is a leak on the 12th floor, updating a riser diagram rarely feels urgent. Documentation becomes a “when we have time” task, and that time may never arrive. The episode also names a less comfortable cultural factor: some engineers worry that sharing everything they know could make them replaceable. The guest argues that professional value lies not in hoarding knowledge, but in building systems that can operate without depending on one person.
Responsibility is another obstacle. If property management, the chief engineer, and outside vendors each assume another party owns the records, nobody keeps them current. A documentation program needs a named owner as well as a practical routine.
A practical, low-cost way to begin
The recommendation is to start small rather than launch a sprawling documentation project. Identify the systems whose failure would hurt the property most. Life safety and critical power are suggested priorities, along with main HVAC serving a data center or lab. Then use a phone to record a narrated walkthrough. A technician can point out the main breaker for an area and explain what it feeds, such as an elevator room or an air-handling unit. The aim is to capture useful context, not to buy sophisticated software.
- Choose high-consequence systems first, especially life safety and critical power.
- Record short walkthrough videos with clear narration about components and what they serve.
- Involve frontline technicians, whose practical knowledge may otherwise leave with them.
- Assign someone to maintain, review, and update the records.
- Capture knowledge before an employee retires or a contractor moves on.
Making participation part of the team’s habits helps turn documentation from a special project into ordinary work. The people closest to the systems are often best positioned to explain what is actually installed and how it behaves.
What to document first
The first priority is power paths: what feeds what, and what will go dark if a panel loses power. That information supports troubleshooting and helps teams understand the consequences of an outage. Next, document network topology, particularly where building controls and security rely on IP networks. Record building automation system points and sequences, access-control hierarchies—including who can enter the server room or override access—and vendor escalation paths.
Escalation information should include who to call when a system fails and who to contact if the first person does not respond. During an incident, searching for a phone number wastes time. These records turn scattered knowledge into actionable information for the people on call.
The cost of waiting
The speakers push back on the idea that documentation requires too much time or budget. A small water leak once triggered a false fire alarm in a building with undocumented fire-alarm systems. When firefighters arrived, staff could not identify the affected zone because panel labels were wrong. This is not merely a maintenance inconvenience; it is a life-safety and response problem.
Documentation also supports capital planning. Before a retrofit, decision-makers need to know what is actually in the walls. If records do not reflect reality, budgets are based on uncertainty. Preventive documentation can reduce emergency discovery and give property teams better information for planning future work.
Make records a living asset
The closing framework is straightforward: treat documentation as a living asset, assign clear ownership, and capture knowledge before transitions. Review and update records as systems change, just as teams maintain other critical assets. When a knowledgeable employee or contractor is still available, ask them to explain and record the details only they know. The best documentation is created by people who understand the system firsthand.
A useful first step is to choose one critical system, record a short walkthrough, and identify who will keep that record current. The goal is not paperwork for its own sake. It is dependable operations, more informed planning, fewer avoidable searches, and a building less reliant on any single person’s memory.
The building still runs—until the person who understood it leaves
Imagine an experienced building engineer retiring after decades on the job. A month later, a group of VAV boxes stops responding. The panel schedules are useless, and the new engineer cannot tell which controller feeds the affected zone. A repair that might have taken two hours turns into a three-day search, overtime, and an increasingly frustrated tenant.
This is what a documentation void looks like. The building’s systems remain in place, but the practical knowledge that connected them has departed with the people who knew their quirks. In an episode of Built, Wired & Secured, the conversation focuses on why that gap is common, what it costs, and how property teams can begin closing it without waiting for a major software purchase or a perfect documentation project.
Documentation can be present and still be wrong
Possessing a drawing or manual does not guarantee that it describes the building as it exists today. In one example, a fire alarm panel had been replaced during a retrofit, but the as-built drawings still showed the old panel. When ground faults appeared on the replacement panel, a technician spent half a day tracing circuits that were no longer there. Meanwhile, tenants had to listen to alarms chirping.
The problem is not limited to drawings. A manual may describe a typical operating sequence while the actual system contains custom programming. The episode describes a chiller plant whose sequence had been modified by a controls technician who later left. Without a record of that change, a contractor had to reverse-engineer the building’s own system. The speakers mention a bill of roughly $4,000 simply to determine what should have been documented in the O&M manual.
These examples reveal a costly distinction: documentation is useful only when it reflects reality. A record that has not kept up with retrofits, programming changes, or field modifications can send a technician in the wrong direction. Each undocumented change can recreate the same investigative work later.
Why the knowledge gap keeps growing
Building teams rarely ignore documentation because they think it has no value. More often, urgent work wins. When a leak demands attention, updating a riser diagram feels less pressing. Documentation becomes something to do “when we have time”—but the next operational problem arrives before that time appears.
The discussion also acknowledges a cultural issue: some professionals may feel that documenting their knowledge makes them replaceable. That concern can be subconscious, but its effect is real when vital information remains in one person’s head. The counterpoint offered in the episode is that a professional’s value is not measured by being the only person who can keep a system running. It is measured by building systems and teams that can run without that dependency.
Even willing teams can stall over ownership. Is the property manager responsible? The chief engineer? An IT vendor? If everyone expects someone else to maintain the records, they quickly become stale. A practical program needs a clear owner and a process that fits daily operations.
Start with the systems that matter most
A documentation effort does not have to begin with an inventory of every asset in the property. The episode recommends starting with the systems whose failure would have the greatest consequences: life safety, critical power, and essential HVAC, particularly in places such as a data center or lab.
Then use a tool already at hand: a phone. A narrated video walkthrough can identify a main breaker and explain that it feeds a particular area, elevator room, or air-handling unit. This simple record may capture more immediate operational value than an elaborate platform that nobody has time to populate. The goal is clear, usable context from someone who knows what they are looking at.
Frontline technicians should be involved. They understand how equipment is actually arranged and may know which labels are wrong, what changed during a retrofit, or which workaround has become part of normal operations. Involving them also gives the organization a chance to preserve information before a retirement or vendor change removes access to that experience.
A priority list for the first records
When deciding what to capture, begin with dependencies and consequences. The speakers put power paths first: what feeds what, and what stops working if a panel goes down. This is foundational during troubleshooting because it helps teams determine what an outage may affect.
- Power paths: identify what each panel or source feeds and what would lose power.
- Network topology: map connections, especially for IP-based building controls and security.
- BAS points and sequences: record relevant points and how the system is programmed to operate.
- Access-control hierarchies: document who can enter sensitive areas and who can override access.
- Vendor escalation paths: list the first contact and the backup when that person does not answer.
The escalation list may seem mundane, but it matters during an outage. Searching for a phone number while the clock is ticking is avoidable. A usable record should help the person responding understand both the technical dependency and the next action.
Documentation is also a life-safety and planning tool
To illustrate the risk of waiting, the episode describes an undocumented fire-alarm system affected by a small water leak that triggered a false alarm. When the fire department arrived, staff could not identify the affected zone because the panel labels were wrong. That failure goes beyond wasted maintenance time. It affects communication during a life-safety event.
Accurate records also support capital planning. A property team preparing a retrofit needs to know what is actually in the walls. If nobody can verify existing conditions, the budget is built on guesswork. Better documentation helps teams make informed decisions about future work rather than discovering hidden conditions after a project has begun.
This is why preventive documentation should be viewed as operational infrastructure, not clerical overhead. The financial case includes fewer avoidable discovery efforts; the operational case includes faster, better-informed responses; and the planning case includes a clearer understanding of the asset being managed.
Keep the record alive
The episode’s closing advice is to treat documentation as a living asset rather than a one-time project. Someone must be accountable for reviewing and updating it. When a system changes, the record should change too. When a knowledgeable employee or contractor is preparing to leave, capture their explanations while they are still available. Information created by the people who actually know the system is more likely to describe what is real.
A manageable starting point could be one high-consequence system, one narrated walkthrough, and one named owner for keeping the record current. That modest habit can begin to reduce dependence on memory and make future maintenance less like a treasure hunt.
For property owners, facility teams, and IT leaders, the key question is not whether every document is perfect. It is whether the people responsible for the building can quickly determine what feeds what, how critical systems behave, and whom to call when something fails. Listen to the episode for the full discussion and practical framework for closing the documentation void before a transition or failure forces the issue.
Frequently Asked Questions
What building systems should I document first?
Start with power paths so you know what feeds what and what will go dark if a panel fails. Then document network topology, especially for IP-based controls and security, followed by BAS points and sequences, access-control hierarchies, and vendor escalation contacts.
How can a property team document building systems without buying new software?
Start with a phone and record narrated walkthroughs of the most critical systems. Explain what components are and what they feed, and involve frontline technicians who know how the systems actually work. Assign someone to keep the records reviewed and updated as systems change.
Why are as-built drawings and vendor manuals not always enough?
They can describe an earlier installation or a generic system rather than what is operating now. The episode describes a replaced fire alarm panel missing from the as-builts and a chiller sequence customized beyond the vendor manual. In both cases, staff had to investigate or reverse-engineer the real system.