Show Notes
When Building Knowledge Walks Out the Door
This episode of Built, Wired & Secured opens with a familiar worst-case scenario: it is Monday morning, a tenant reports that the elevator schedule stopped responding overnight, no one can get the cable closet key, the on-call contractor is an hour away, and nobody knows who changed the access rules. That is the operational reality Alex Morgan, Michael Harrington, and James Rogers set out to address in this conversation about knowledge continuity.
The discussion stays grounded in a simple idea: modern buildings rely on systems that may look routine on a normal day, but become mission-critical the moment something breaks. When staff retire, contractors rotate offsite, or vendors change hands, the biggest risk is often not the equipment itself. It is the loss of context around how that equipment is supposed to work, who can access it, and what changed over time.
The Three Failure Modes That Cause Real Trouble
Michael breaks the problem down into three practical failure modes.
- Credentials that live in someone’s head instead of a controlled system
- Undocumented custom work, such as BAS tweaks made to reduce nuisance alarms
- Missing spare-parts lists that turn routine failures into procurement scrambles
Those issues sound small until they collide with an outage. A password that was never vaulted can stop troubleshooting before it starts. A logic change that was never documented can be reversed by a well-meaning technician months later. And a failed control board without a documented replacement plan can create costly delays while teams scramble to source parts.
James and Michael both emphasize that the visible repair bill is only part of the damage. The hidden cost shows up in downtime, emergency labor rates, tenant complaints, and lost trust. There is also the time sink of reverse engineering past decisions in the field instead of following a known good process. As they put it, preventative maintenance for knowledge is far less expensive than emergency recovery after context disappears.
Centralized Documentation vs. Lightweight Runbooks
One of the more useful parts of the episode is the debate over how teams should preserve operational knowledge. Michael notes that a centralized repository is attractive because it offers one ownership map and one source of truth. The catch is that central systems go stale when no one owns the updates.
James pushes back slightly, arguing that a single source can scale if ownership is clear and validation checks are part of the process. That leads to a healthy discussion around cadence. Michael prefers monthly lightweight checks for critical systems because building environments change quickly. James agrees that monthly is ideal where resources allow, but points out that many teams cannot sustain that schedule across every system.
The practical compromise they land on is risk-based validation frequency:
- Monthly checks for top-tier critical systems
- Quarterly checks for less critical systems
- Clear assignment of ownership for every artifact
The key takeaway is that the format matters less than the discipline behind it. Whether a team uses a centralized repo, lightweight runbooks, or a combination of both, documentation only helps if someone is responsible for keeping it current.
The Artifacts That Actually Help in the Field
Rather than advocating for a massive documentation effort, the guests recommend a short list of practical artifacts that can immediately reduce confusion during outages or transitions.
- One-page handoff checklists for each critical system, including BAS, access control, and network closets
- A critical systems baseline listing normal sensor values and schedules
- A spare-parts list with lead times
- A vendor contact matrix with roles and escalation rules
These are intentionally lightweight. The point is not to build a giant binder no one opens. The point is to create short, usable references that work under pressure.
James adds an operational ritual that helps these artifacts stick: a 15-minute handoff walkthrough after contractor work or during shift changes. In that brief meeting, teams can review baseline values, flag recent changes, and confirm where keys, drawings, and other essentials are stored. It is a small habit that can save hours when something fails later.
Sharing Enough Without Oversharing
The episode also addresses a common concern in commercial real estate and building operations: how do you share useful knowledge without overexposing sensitive information?
The answer is layered documentation. Secrets should stay out of public-facing documents. Passwords belong in a vault, while the documentation should record who has access rather than listing the secrets themselves. Ownership maps can be role-based instead of exposing overly detailed sensitive layouts. The guests recommend a public-facing one-page cheat sheet for first responders and a separate locked folder for credentialed staff who need deeper detail.
They also recommend short validation drills annually or after vendor changes. James shares an example where a drill uncovered expired contractor access before a real emergency exposed the gap. That kind of exercise turns documentation from a static file into an operational control.
Two Stories That Show the Difference
The episode includes two short examples that make the value of knowledge continuity easy to understand.
In the success story, a hospital campus experienced an issue at night, but the team had a one-page runbook that included an alternate vendor contact and a temporary IO isolation workaround. Staff were able to isolate the circuit, keep critical systems online, and avoid any impact to patients. Tenants did not even realize there had been an incident.
The failure story is just as instructive. A retrofit crew relabeled ducts and adjusted control logic without updating the baseline documentation. Months later, a calibration caused an air handling unit to run full tilt and trigger repeated alarms. Because the ad hoc changes were never recorded, it took weeks to trace the source of the problem. One skipped documentation step created a long and expensive recovery.
A Low-Friction Playbook to Start This Week
For listeners who want an immediate next step, the guests keep the assignment simple. Start with the top three critical systems in your building or portfolio. For each one, create a one-page handoff that includes:
- A contact matrix
- Two or three baseline values that confirm normal operation
- Where spare parts are stored
- Who has keys or vault access
Then take the extra step that proves whether the artifact is actually useful: have someone unfamiliar with the system use that one-pager to perform a basic check. If they cannot do it, the handoff still has a gap. Fix it now, not during a crisis.
The Practical Compromise
By the end of the conversation, Michael and James align on a workable operating model: assign owners, tie validation cadence to system risk, and keep artifacts short enough to stay usable. Start small, pilot in one building, and show measurable value through reduced confusion, faster recovery, and less finger-pointing when something changes hands.
The final message is straightforward. Ask what breaks if a system goes down. Let that answer guide where you invest your documentation effort. Knowledge continuity does not require heavy process overhead to be effective. It requires short handoffs, clear ownership, and a repeatable validation habit.
If your building operations depend on people remembering how things work, this episode is a reminder that memory is not a control. A practical handoff package is.
Keeping the Keys: Why Knowledge Continuity Matters More Than Most Building Teams Realize
Turnover is easy to treat as a staffing issue. In reality, it is often a systems issue.
In this episode of Built, Wired & Secured, Alex Morgan sits down with Michael Harrington and James Rogers to talk about knowledge continuity in building technology. The opening scenario makes the stakes obvious: a tenant calls on a Monday morning because the elevator schedule stopped responding overnight, no one can find the cable closet key, the on-call contractor is an hour away, and nobody knows who changed the access rules.
That is not just a frustrating start to the week. It is a direct example of how operational risk builds when critical knowledge is never turned into usable artifacts.
The conversation is especially relevant for commercial real estate teams, facilities leaders, and property operators managing increasingly connected buildings. BAS platforms, access control systems, network closets, scheduling tools, and vendor relationships all create dependencies. When the people who know those details retire, rotate off the account, or leave for another job, the building does not become simpler. It becomes harder to operate.
The Real Problem Is Lost Context
Michael outlines three of the biggest failure modes in plain language, and each one points to the same root issue.
- Credentials live in someone’s head instead of in a controlled vault
- Custom changes are made in the field but never documented
- Spare parts are not listed, staged, or tied to a response plan
None of those failures require a catastrophic equipment breakdown to cause serious disruption. A missing login can stall a diagnosis. An undocumented BAS tweak can be reversed by someone trying to restore normal settings. A missing spare-parts list can turn a simple swap into a procurement emergency.
What makes these situations so expensive is not just the repair cost. The bigger issue is the chain reaction that follows. Downtime grows longer. Emergency labor rates kick in. Tenants experience delays. Internal teams lose time tracing old decisions instead of executing a known fix. Trust erodes because the building appears unprepared.
That is why the episode frames knowledge continuity as preventative maintenance for operations. The team is not talking about paperwork for its own sake. They are talking about reducing recovery time, improving resilience, and protecting the occupant experience.
Why Documentation Fails Even When Everyone Agrees It Matters
One of the strongest parts of the conversation is the honest debate around documentation strategy.
On paper, a centralized repository sounds ideal. One source of truth, one ownership map, one location to update. Michael points out the operational reality: centralized documentation becomes stale quickly if no one is explicitly accountable for maintaining it.
James does not reject centralization, but he does force the more useful question. The problem is not that a single source exists. The problem is whether validation is built into the process. If owners are assigned and checks are done on a real cadence, a centralized system can work.
That leads to a practical disagreement about timing. Michael argues that monthly lightweight checks are safer for critical systems because conditions change quickly. James agrees that monthly is strong, but notes that not every team has the staffing capacity to do that across the board.
The compromise they reach is the kind of answer real operators can use: set cadence by risk.
- Monthly validation for top-tier critical systems
- Quarterly validation for lower-risk systems
- Named owners for every key artifact
This matters because it shifts the discussion away from documentation ideology and back toward operations. Teams do not need to win an argument about formats. They need a system that stays current enough to be trusted when something goes wrong.
Short Artifacts Beat Big Binders
Another useful theme in the episode is restraint. The answer is not to create massive documentation packages that nobody uses. The answer is to create a few artifacts that are short, current, and field-ready.
The guests recommend four items that consistently move the needle:
- One-page handoff checklists for critical systems such as BAS, access control, and network closets
- Critical systems baselines showing normal values and schedules
- Spare-parts lists that include lead times
- Vendor contact matrices with defined roles and escalation rules
Each one solves a different operational problem.
The one-page handoff gives the next person enough orientation to act. The baseline provides a reference point for what normal looks like. The spare-parts list prevents reactive scrambling. The contact matrix reduces delays when escalation is needed.
These artifacts are also easier to keep current than a large static manual. That is important because the most elegant document in the world has no value if it is six months out of date.
The Role of Rituals in Making Documentation Useful
Documentation only matters if people use it. James offers a simple ritual that makes a big difference: a 15-minute handoff walkthrough during shift changes or after contractor work.
That short meeting is enough to review baseline values, note recent changes, and confirm where keys, drawings, or supporting materials live. It turns documentation from a file into a habit.
This is an important operational point. Knowledge continuity is not just about storage. It is about transfer. A one-page handoff becomes much more powerful when it is part of a repeatable operating rhythm.
The same principle applies to validation. The team recommends having someone unfamiliar with a system use the one-page artifact to perform a basic check. If they can do it, the artifact is working. If they cannot, the problem has been exposed in a controlled setting instead of during an outage.
Security Still Matters
The conversation also avoids a common documentation trap: over-sharing.
Useful documentation does not require putting secrets into broadly accessible files. Passwords should stay in a vault. Documentation should record roles, access paths, and who can retrieve what, not the secrets themselves. Public-facing materials can remain high level, while deeper technical details live in a locked folder for credentialed staff.
This layered approach is especially important in buildings where access control, network infrastructure, and physical layouts all carry security implications. Teams need enough visibility to respond quickly without turning every cheat sheet into a liability.
The recommendation to run annual validation drills or perform them after vendor changes supports that same goal. Drills can expose expired permissions, missing contacts, or broken assumptions before a real incident forces the issue.
Two Examples With Very Different Outcomes
The episode includes two short stories that clarify the value of doing this work.
In the first, a hospital campus team had a one-page runbook that included an alternate vendor contact and a temporary IO isolation workaround. During a night issue, staff used that artifact to isolate the circuit and keep critical systems online while a part was in transit. Patients were unaffected, and the incident stayed invisible to tenants.
In the second, a retrofit crew relabeled ducts and adjusted control logic without updating the baseline documentation. Months later, a calibration caused an air handling unit to run full tilt and generate repeated alarms. Because the ad hoc changes were never recorded, tracing the root cause took weeks.
Those stories capture the operational difference between context that survives and context that disappears. In one case, a short artifact enabled continuity. In the other, missing documentation created wasted time, avoidable cost, and prolonged confusion.
A Practical Starting Point for This Week
The guests close with advice that is intentionally low friction.
Pick the top three critical systems in your building or portfolio. For each one, create a one-page handoff that includes the contact matrix, two or three baseline values, where spare parts are located, and who has keys or vault access. Then make that sheet part of the weekly walkthrough.
That is a manageable starting point. It creates immediate value without requiring a large transformation project. More importantly, it creates a repeatable pattern that can scale once the team sees the time saved and the reduction in confusion.
Michael and James also make a political point that many operators will appreciate: start small and prove value. Pilot the process in one building. Show how it reduces response time and prevents finger-pointing. Once the return is visible, it stops looking like busy work and starts looking like operational discipline.
Why This Matters for Commercial Real Estate
For commercial real estate teams, knowledge continuity is more than a documentation exercise. It directly affects tenant experience, operational resilience, and the ability to manage increasingly interconnected systems with confidence.
When access rules, network dependencies, BAS logic, vendor escalation paths, and spare-parts readiness are documented well, buildings recover faster and teams make cleaner decisions. When those details live only in memory, every personnel change increases fragility.
This episode offers a practical reminder that resilient operations do not start during an emergency. They start with simple artifacts, assigned owners, and regular validation.
If this topic hits close to home, this episode is worth a full listen. It turns a familiar operational pain point into a concrete playbook that building teams can start using right away.