Show Notes
When Building Systems Follow Different Clocks
In this episode of Built, Wired, and Secured, Alex Morgan sits down with Michael Harrington and James Rogers to examine a common but often overlooked operational problem in modern buildings: different systems can be technically correct at the same time while still producing a bad occupant experience.
The conversation opens with a simple winter-morning scenario. An early shift arrives at 6:10 a.m. Access control works and lets the team in. But the heating schedule says the workspace does not need to be ready yet. Security sees movement after hours. Facilities sees people on the floor and assumes the space should be comfortable. No one system is necessarily broken, and no one may have made an obvious mistake. Still, the operation feels wrong.
That gap between system logic and real-world use is the heart of the episode. The team explains why these issues are rarely just technical failures. More often, they come from conflicting assumptions about occupancy, timing, and responsibility.
Why Small Mismatches Become Bigger Problems
James Rogers explains that these issues often look ordinary from the building side. Someone arrives before the published start time. A room is colder than expected. A manual adjustment is made. By 9:00 a.m., the dashboard looks normal again.
That apparent recovery is exactly what makes the problem easy to miss. The building record may show a resolved condition, but the people who experienced the cold room, made the extra call, or improvised a workaround remember something very different. Over time, those workarounds become routine. A portable heater appears. Staff wait in another space. A door gets propped open. What started as a small timing mismatch gradually turns into an unmanaged operating pattern.
Michael Harrington reinforces an important point: tenants do not care which schedule was technically correct. They care whether their people arrived and the space was ready. That means operations teams need to look beyond schedule files and ask how the building is actually being used.
The Episode's Core Idea: Buildings Run on More Than One Clock
One of the strongest ideas in the conversation is that buildings operate on multiple clocks at once.
- The published schedule says when a space should be in use.
- The actual occupancy pattern reflects when people really arrive and work.
- The equipment clock reflects how long a space needs to reach stable comfort conditions.
- The security clock reflects what activity should be expected and authorized.
Those clocks do not always align. A comfort schedule that starts when people arrive may already be too late if a large area needs time to warm up. An access rule may permit entry, but that does not mean every operational sequence is ready. A recurring early arrival pattern may signal a real business need, but it is not automatically an approved permanent change.
The speakers are careful to separate discovery from approval. A repeated pattern matters because it tells the team something is happening in real life. But recognizing that pattern is different from officially changing how the building should operate.
How to Review Real Scenarios Without Creating a Giant Project
The solution presented in the episode is practical, not theoretical. Rather than treating every mismatch like a full redesign, the team recommends using small scenario-based reviews.
Start with a few real situations:
- A normal weekday
- An early shift
- A late meeting
- A weekend event
For each one, ask a short set of questions:
- What should be accessible?
- What should be comfortable?
- What should security expect?
- Who responds when those answers do not match?
This kind of review does two important things. First, it exposes whether teams are working from different assumptions. Second, it surfaces gaps in ownership, escalation, and fallback procedures before occupants are affected.
The conversation also makes the case for including both operations teams and the people who actually use the space. Occupants often understand the real routine better than the official schedule does. Their input should help shape approved operating decisions, while still respecting established controls and governance.
Exceptions, Manual Overrides, and the Risk of Invisible Operations
A major theme in the episode is visibility. The speakers describe a generalized multi-tenant example where an early-access arrangement had been created for a legitimate recurring need. Months later, the business need changed, but the exception remained. The first sign was not a major incident. It was repeated confusion about why activity at an unusual hour seemed both normal and unexplained.
The lesson is simple: yesterday's assumption can quietly remain in place long after the reason for it disappears.
That is where manual overrides come in. James Rogers draws a clear line between responsible temporary action and warning-sign behavior. An override is responsible when the condition is known, approved, temporary, and has a clear end. It becomes a warning sign when the same override keeps returning, nobody knows who owns it, and the next shift discovers it by accident.
One practical test from the episode stands out: ask, "What breaks if this goes down?" If the answer involves critical operations, physical security, or major tenant impact, the change deserves broader coordination than a simple comfort tweak.
At the same time, the conversation warns against creating approval processes so slow that teams resort to hidden workarounds. The answer is not bureaucracy for its own sake. It is a tiered process that lets low-impact short-term changes move quickly while routing higher-impact changes through broader review.
What Good Ownership Looks Like
The episode argues that shared decisions are fine, but ownerless decisions are not. Ownership does not mean one department controls everything. It means the cross-system outcome has a clear home.
That may look like this:
- Property coordinates the business requirement.
- Facilities manages the operating sequence.
- Security defines access conditions.
- IT supports the system boundary.
What matters is not departmental control. It is clarity. Who calls the meeting? Who approves the change? Who records it? Who knows the fallback if the usual contact is unavailable? If those answers are vague, the operation is depending on memory and habit instead of process.
A Simple Framework Teams Can Use This Week
To close the episode, the speakers turn the discussion into an immediate next step. Take one real rule that touches comfort, access, security, or occupancy and walk through its timeline out loud. Who arrives? What should be ready? What does access expect? What does facilities expect? What happens if the schedule is wrong?
If people answer from memory and the answers differ, that gap is the issue to fix.
Then document four things:
- Who owns the decision
- Why the current rule or exception exists
- What the fallback is if the main contact is unavailable
- When the exception expires or gets reviewed
As the episode makes clear, five visible lines of operational documentation are better than a hidden workaround that slowly becomes permanent.
Key Lesson From the Episode
This conversation is a strong reminder that reliability is not just about equipment maintenance or system integration. It also depends on disciplined communication, clear ownership, and regular review of how a building is actually used. When building clocks agree, occupants notice consistency instead of the machinery behind it. When they do not, small frictions become operational risk.
For building operators, facilities leaders, security teams, and commercial real estate stakeholders, this episode offers a practical framework for aligning systems before the next early shift, late meeting, or seasonal change exposes the gap.
The Building Has Two Clocks: Why Operational Alignment Matters More Than Perfect Systems
Modern buildings are full of systems designed to make decisions automatically. Access control determines who can enter. Building automation manages heating and cooling. Security teams monitor activity and exceptions. Facilities teams respond to the actual conditions inside the space. On paper, each system can be functioning exactly as designed.
And yet the result can still be a bad day for occupants.
That is the central point of this episode of Built, Wired, and Secured, where Alex Morgan speaks with Michael Harrington and James Rogers about what happens when comfort, security, occupancy, and operations run on different assumptions. Their message is straightforward: many building problems are not caused by a broken system. They are caused by multiple systems each doing the right thing according to a different clock.
The episode begins with a relatable scenario. It is 6:10 on a winter morning. An early shift arrives. Access control lets them in. The heating schedule says their area does not need to be ready yet. Security sees motion after hours. Facilities sees people on the floor and assumes the space should be comfortable. No one may have configured anything incorrectly. But the occupants still walk into a cold room, and the operation still feels wrong.
That example captures a reality many commercial properties face. The problem is not always technical failure. More often, it is misalignment between schedules, expectations, and ownership.
When a Workaround Becomes the Real Process
One of the most useful observations in the episode is how often these problems hide in plain sight. James Rogers notes that from the building side, the issue can look ordinary. Someone arrives early. A room is colder than expected. A manual change gets made. By normal business hours, everything looks fine again.
That is what makes the issue easy to dismiss. The dashboard says the building recovered. But the people who arrived early remember the cold room, the extra call, and the inconvenience. If the same thing happens more than once, people adapt. They wait in a warmer area. They bring in a portable heater. They prop open a door. They stop reporting the problem because they assume that is just how mornings work.
At that point, the building has developed an informal operating process that exists outside the official one.
This matters because invisible workarounds are rarely harmless. They can create comfort issues, energy waste, security exposure, and confusion during shift changes. Most importantly, they mask the fact that the documented schedule no longer reflects how the building is really being used.
Buildings Operate on Multiple Clocks
The episode frames this issue through a simple but powerful idea: buildings operate on more than one clock.
There is the published schedule, which says when a space is supposed to be occupied. There is the actual use pattern, which reflects when people really show up. There is the equipment clock, which determines how much lead time a large space needs to reach a comfortable condition. And there is the security clock, which defines what activity should be expected and when.
Problems start when those clocks drift apart.
For example, a workspace may officially begin at 7:00 a.m., but if staff routinely arrive at 6:10 a.m., then the published schedule is no longer the whole truth. A heating sequence that starts at 7:00 a.m. may be technically on schedule while still being operationally late. At the same time, security staff may see repeated early activity and treat it as an exception, even though it has become common practice. Each team is reading a different version of reality.
That is why Michael Harrington makes an important distinction in the conversation: authorization is not the same as convenience. A recurring early arrival may reveal a real business need, but it does not automatically justify making every area available or normalizing a permanent exception. Repeated activity should trigger investigation, not immediate permanent change.
That difference between discovery and approval is critical. Teams need a way to recognize real patterns without bypassing control.
Scenario Reviews Beat Assumptions
Rather than recommending a major redesign effort, the episode points teams toward a simpler practice: short scenario-based reviews. The idea is to take a few common situations and walk through them from multiple perspectives.
The examples they suggest are practical:
- A normal weekday
- An early shift
- A late meeting
- A weekend event
For each scenario, teams should ask a few direct questions. What should be accessible? What should be comfortable? What should security expect? Who responds if those answers do not match? That structure does not require a new platform or a lengthy consulting engagement. It requires honest operational conversation.
The real value is that it exposes hidden assumptions quickly. If property, facilities, security, and occupants all describe the same scenario differently, then the building already has a coordination problem. The issue is not hypothetical. It is already affecting expectations, even if the impact has not yet triggered a major incident.
The speakers also emphasize that the people who use the space often know the routine better than the schedule file does. Their feedback matters. It should not become a side door around established controls, but it should absolutely inform what gets reviewed and what gets approved.
Manual Overrides Are Signals, Not Just Fixes
The episode spends meaningful time on manual overrides because they often reveal the health of the operating process. An override is not automatically a problem. In many cases, it is the right response. A scheduled event changes expected occupancy, so a temporary adjustment is made. The key is whether the change is visible, approved, and time-bound.
James Rogers puts it clearly: an override is responsible when the condition is known, approved, and temporary. It becomes a warning sign when the same override keeps coming back, no one knows who owns it, and the next shift discovers it by accident.
That definition is useful because it shifts the conversation away from whether a manual change occurred and toward whether the organization has control of the exception. A temporary change with an owner and end point is operations. A recurring change with no visibility is drift.
One of the best practical questions from the episode is: What breaks if this goes down? If the answer touches critical operations, physical security, or major tenant impact, the change deserves broader review. If the impact is low and temporary, the process should allow teams to act quickly without getting buried in approvals. The speakers advocate for a tiered approach that balances agility with governance.
Ownership Is the Difference Between Coordination and Confusion
The conversation also makes a strong case for clearly assigning ownership. Not total control, but ownership of the cross-system outcome.
That distinction matters. Complex building decisions often span multiple teams. Property may own the business requirement. Facilities may manage the operating sequence. Security may define access conditions. IT may support the system boundary. Shared decision-making is normal. What fails is ownerless decision-making.
Without ownership, small exceptions linger. Review dates vanish. Fallbacks are unclear. The same question gets answered differently depending on who is on shift. Over time, the building becomes dependent on tribal knowledge instead of process.
The speakers describe a generalized example from a multi-tenant setting where an early-access arrangement had originally been created for a real business need. Months later, the need had changed, but the exception remained. The first clue was not a major event. It was repeated confusion about why activity at an unusual hour was considered normal by some teams and unexplained by others. The eventual improvement was not a new product. It was making the decision visible by assigning an owner, a review point, and a fallback.
A Practical Next Step for Building Teams
The most valuable part of the episode may be how actionable its advice is. Teams do not need to overhaul every schedule this week. They need to choose one rule that affects comfort, access, security, or occupancy and test whether it matches actual building use.
Start with one real scenario and say it out loud. Who arrives? What should already be ready? What does access expect? What does facilities expect? What happens if the schedule is wrong? If the answers vary depending on who speaks, the gap is already visible.
Then document four basic items:
- The owner of the decision
- The reason the rule or exception exists
- The fallback if the usual contact is unavailable
- The review or expiration date
As the episode argues, five clear lines of visible documentation are better than a hidden workaround that quietly becomes permanent.
Why This Matters Beyond Comfort
At first glance, this conversation may sound like it is mainly about heating schedules and early arrivals. It is broader than that. It is about operational trust. Occupants assume buildings are coordinated. They do not think in terms of separate clocks for access, comfort, and security. They just know when the space is or is not ready for use.
That is why this discussion matters for commercial real estate leaders, facilities teams, security managers, and technology partners alike. Reliable operations are not only built through strong systems. They are built through clear decisions, visible exceptions, and disciplined handoffs between teams.
If you want connected building systems to support the business instead of confusing it, this episode offers a practical framework. Review real scenarios. Make exceptions visible. Assign ownership. Test the fallback. Then revisit the rule before a workaround becomes policy by accident.
For more conversations on the operational realities behind modern buildings, listen to this episode of Built, Wired, and Secured and consider how many clocks your own building is following today.