Show Notes
Why a few minutes can derail an investigation
A building’s clocks can appear close enough until someone needs to compare events across systems. In the opening example, video showed a restricted-area door opening at 11:42 p.m., while the access log recorded 11:38 p.m. That four-minute gap stalled an after-hours security investigation because the records could not establish who was present at the relevant time.
The issue is not necessarily one faulty clock. Cameras, access controllers, network switches, and other devices may each keep time independently. One may run fast while another runs slow. When investigators need to place events in order, small differences can create confusion and undermine confidence in the timeline.
- Video and access records may disagree about when a door was used.
- Conflicting timestamps can make it harder to determine who was present.
- Inconsistent records can weaken the credibility of an investigation or evidence.
Clock drift affects building operations, too
Time synchronization is also an operational concern. A building automation system (BAS) was reporting that HVAC had shut down at 6:00 p.m., while the energy meter showed cooling continuing until 8:30 p.m. The BAS clock was two and a half hours behind. The mismatch helped explain why cooling was running when it was not needed.
Another example involved ventilation controlled by occupancy schedules. A slow BAS clock caused fans to run during off-hours, and the problem was discovered after an energy bill increased. It took two weeks to trace the behavior back to the clock. When engineers troubleshoot a sequence such as a chiller that will not start, timestamped trends are important; if those records are out of sync, the timeline can mislead the investigation.
- Out-of-sync BAS and meter data can obscure when equipment actually ran.
- Incorrect schedules can contribute to unnecessary off-hours operation.
- Misaligned trends make troubleshooting harder and can send teams chasing the wrong cause.
Why building clocks drift
Even good clocks can drift. The discussion identifies temperature, age, and power fluctuations as possible contributors. The broader problem is the absence of a shared standard: devices keep their own time, and unless somebody checks, the differences may go unnoticed.
The same issue can cross technology domains. Cameras, access controllers, network equipment, building automation, and even a lobby display may not be aligned if they are not using a common time source. Assumptions about who handles synchronization are common: a BAS vendor may expect the security integrator to handle it, while the integrator may assume someone else is responsible.
Evidence, legal risk, and compliance
Inconsistent timestamps can affect insurance investigations and potential legal proceedings, where the credibility of records matters. The episode illustrates how a five-minute discrepancy between access control and video could make a contractor appear to have left before the time they said they were on site. The clock was fast; the contractor was not lying. But the discrepancy nearly led to the contract being terminated.
The discussion also raises compliance audits, naming HIPAA and SOC as examples of contexts where accurate timestamps may be required. If systems are not synchronized, audit records can be difficult to rely on. The takeaway is practical: clock alignment is a business risk, not merely a technical detail.
NTP helps, but ownership is essential
The proposed technical foundation is Network Time Protocol (NTP). Rather than letting each device keep independent time, establish a time source and configure devices to synchronize to it. NTP has been around for decades and is not presented as complicated, but it still needs an owner and coordination across vendors.
In an ideal arrangement, the organization responsible for the network owns the network and time source, while security and BAS vendors configure their devices to use it. The property manager or facilities director can set the expectation, ensure the contracts address it, and make sure somebody is accountable for verification and correction.
Questions to ask vendors and integrators
Do not accept “we handle it” without specifics. Ask vendors to explain their approach and show it in writing. The episode recommends asking:
- What is the time source: a public NTP server or a local one?
- How often do devices synchronize: once a day, once an hour, or on another schedule?
- Who monitors devices and corrects clock drift?
- Can you provide a report or test that proves synchronization is working?
If a vendor cannot show the time source, synchronization frequency, monitoring responsibility, or evidence of a test, assume the process has not been demonstrated. Make requirements explicit in vendor contracts and include time synchronization in RFPs.
A shared responsibility with a clear lead
Time synchronization crosses network, security, and building-automation systems, so it requires cooperation. Vendors need to configure their own equipment, while a designated owner ensures that a common standard exists and that the work is verified. Shared responsibility should not mean nobody is accountable.
For property managers, facilities leaders, and technology teams, the practical step is to make time synchronization a requirement before incidents or confusing trends expose the gap. A consistent time source supports investigations, operations, and compliance—and the best outcome is often unremarkable: building systems agree on what time it is.
The building clock is part of the evidence
A camera records a door opening at 11:42 p.m. The access-control log says the same door was used at 11:38 p.m. Which record is right? In the example discussed in this episode, the four-minute difference stalled a security investigation. The problem was not simply that one system had an incorrect clock. It was that the building’s systems could not provide a dependable shared timeline.
Commercial buildings depend on timestamps across video surveillance, access control, network devices, and building automation. When those systems keep time independently, their records may not line up. A few minutes might sound insignificant in ordinary conversation, but it can matter when someone is trying to determine who entered a restricted area, when equipment operated, or whether a sequence happened as expected.
One discrepancy can spread uncertainty
Each device may have its own clock. A camera can run fast while an access controller runs slow. If there is no shared source and no process for checking drift, the gap can go unnoticed until people need to compare records. At that point, they are not just comparing events; they are also trying to determine whether each timestamp can be trusted.
The consequences go beyond an investigation taking longer. The episode describes how an access-control clock that was five minutes fast made a contractor appear to have left earlier than they said. Video and access records created doubt about the contractor’s account. The contractor was not lying, but the discrepancy nearly led to the contract being terminated. A clock problem had become a relationship and business risk.
Time synchronization is an operations issue
Building automation systems rely on time for schedules and sequences. In one example, the BAS reported that cooling had shut down at 6:00 p.m., while the energy meter showed cooling continuing until 8:30 p.m. The BAS clock was two and a half hours behind. That mismatch helped explain why the building was paying for cooling it did not need.
In another example, a BAS controlled ventilation based on occupancy schedules. Because its clock was slow, fans ran during off-hours. The team noticed an increase in the energy bill, but tracing the issue back to the clock took two weeks. The system was following its schedule according to its own time; that time was simply out of alignment.
Clock differences can also complicate maintenance. When a chiller will not start, engineers may use timestamped trends to understand what happened before and after the failure. If those trends are inconsistent, troubleshooting becomes harder. The team may be following a timeline that never actually occurred in that order. In the engineer’s words, misaligned trends can send people “chasing ghosts.”
Good clocks can drift
Time drift is not limited to cheap devices. The discussion identifies temperature, age, and power fluctuations as factors that can affect clocks, including good ones. But the deeper issue is often organizational: nobody has established a standard that devices must follow, and nobody is checking whether they remain aligned.
That ownership gap is easy to create. A BAS vendor may assume the security integrator handles time. The integrator may believe the network team owns it. Meanwhile, each system continues to keep time on its own. A building can have capable vendors and still lack a reliable shared timeline if responsibilities are left implicit.
Why credible timestamps matter
When an investigation involves insurance or potential legal proceedings, records need to be credible. If timestamps conflict, people may question whether the evidence supports a particular sequence of events. Saying that a clock was wrong is not a reassuring explanation when the records are being used to establish what happened.
The episode also points to compliance audits, including HIPAA and SOC as named examples. Accurate timestamps can matter when records are reviewed. If systems are unsynchronized, an organization may have difficulty demonstrating a coherent event history. The point is not that every clock discrepancy automatically leads to a failed audit or legal outcome; it is that unreliable timestamps create avoidable doubt in settings where records matter.
Build a time-sync approach around NTP
The technical starting point is Network Time Protocol, or NTP. The basic idea is to establish a time source and configure devices to synchronize to it, instead of allowing every device to operate as an isolated clock. NTP is longstanding and does not need to become a science project. It does, however, need to be configured and managed.
In an ideal arrangement, the organization that owns the network manages the network and time source. Security and BAS vendors then configure their devices to use that source. This requires coordination: having a time source is not enough if individual devices are not pointed to it, and configuring devices is not enough if nobody monitors whether synchronization continues to work.
Make accountability explicit
Responsibility can be shared, but it should not be vague. The episode argues that the property manager or facilities director needs to set the expectation. That does not require them to know the technical details of NTP. It does require them to ask who owns the source, who configures the equipment, and who checks for drift.
Contract language and procurement are practical places to establish that expectation. The property manager in the discussion includes time-sync requirements in vendor contracts and RFPs. When the requirement is written down, it is less likely to fall between vendors who assume someone else is handling it.
Four questions to ask your vendors
Ask your integrator, IT team, BAS provider, and security vendor specific questions:
- What is your time source? Find out whether devices use a public NTP server or a local source.
- How often do devices synchronize? Ask whether the schedule is daily, hourly, or something else.
- Who monitors and corrects drift? Identify the person or team responsible when devices stop aligning.
- Can you prove it? Request a report or test that demonstrates the configuration is working.
Do not treat “we handle it” as a complete answer. Ask for the time source and sync frequency in writing, and ask for evidence. If a vendor cannot show how synchronization is configured or verified, assume that it has not yet been demonstrated.
A quiet control with meaningful value
Reliable time synchronization is easy to overlook because it often works in the background. But it supports the credibility of security records, helps operations teams interpret trends, and gives vendors a shared basis for diagnosing system behavior. It connects technology that may be managed by different teams and companies.
The goal is not to make clocks a recurring crisis. It is to establish a common source, configure each system to use it, assign responsibility for monitoring, and verify the result. When that work is done, video, access logs, network events, and building automation can tell a more consistent story. For a deeper discussion of the examples and vendor questions, listen to this episode of Built, Wired, and Secured.
Frequently Asked Questions
How can clock drift affect a building security investigation?
Clock drift can make video and access-control records disagree about when an event occurred. In the episode’s example, footage showed a door opening at 11:42 p.m., while the access log showed 11:38 p.m. That four-minute difference stalled the investigation because the records could not establish a dependable timeline.
What should I ask vendors about building system time synchronization?
Ask what time source devices use, how often they synchronize, who monitors and corrects drift, and whether the vendor can prove synchronization with a report or test. The episode recommends getting the source and sync frequency in writing rather than accepting a vague assurance that the vendor handles it.
How can an out-of-sync BAS clock affect energy use?
A BAS clock that is behind or otherwise misaligned can cause schedules and energy records to disagree. The episode describes a system reporting that cooling stopped at 6:00 p.m. while the meter showed it continued until 8:30 p.m. Another slow clock kept ventilation fans running during off-hours.