The Contractor Calibration Gap

A contractor can deliver excellent work, pass inspection, and still create a problem somewhere else in the building. In this episode of Built, Wired & Secured, Alex Morgan talks with property management veteran Michael Harrington and facilities engineering leader James Rogers about the hidden risks created when individual trades work without a complete view of the building.

The discussion focuses on the “calibration gap”: the difference between a system working correctly on its own and working correctly as part of an interconnected building. Modern facilities rely on HVAC, building automation, access control, cameras, networks, backup power, fire alarms, and other systems that share physical space, electricity, communications infrastructure, and operational dependencies.

Why Excellent Work Can Still Create Operational Risk

The problem is not necessarily poor workmanship or careless contractors. Most contractors complete the work they were hired to perform. The challenge is that a narrowly defined scope may not require them to evaluate how their work affects adjacent systems.

A new chiller may operate properly while increasing startup power demand or adding heat to a room containing network switches.
A building automation system may be correctly programmed while generating enough network traffic to interfere with security cameras.
A new fire alarm panel may be installed correctly but overload a UPS already supporting an expanded security system.
A backup generator may work as designed while an overlooked fuel-line dependency causes emergency lighting to fail during testing.

In each example, the individual installation may be technically sound. The failure occurs at the boundary between systems, where responsibility is often unclear.

Modern Buildings Are Interconnected

Michael and James explain that buildings have become more dependent on shared infrastructure. HVAC, security, networks, automation, and life-safety systems may now share power, data connections, rooms, pathways, and backup resources. A change made to one system can therefore create consequences for systems managed by completely different vendors.

Tenants and building occupants do not experience these failures as separate trade issues. If the network goes down, they cannot work. If access control fails, they may not be able to enter. If cameras freeze, security teams lose visibility into areas such as parking garages. The business impact is immediate, regardless of which contractor performed the original work.

A Real-World BAS and Camera Failure

James describes a building automation retrofit involving new controllers and sensors. The installation and programming were completed properly, but the contractor did not check the existing network environment. The new controllers used the same switch that carried security camera traffic, and the polling rate was aggressive enough to cause packet loss.

The result was intermittent camera freezing. The network team blamed the security vendor, while the security vendor blamed the network team. It took three weeks to identify the building automation upgrade as the source of the problem. During that time, the security team could not reliably see what was happening in the parking garage, creating more than an inconvenience—it created a liability concern.

Who Owns Integration Risk?

The guests discuss whether the owner, general contractor, or individual trades should be responsible for integration. Their conclusion is that coordination is shared, but the owner ultimately bears the risk. Owners and facility leaders must therefore make coordination an explicit project requirement rather than assuming it will happen automatically.

Scope boundaries exist for practical reasons. Contractors compete on price and generally keep bids focused on the work they were hired to perform. That makes owner-led coordination essential. Before work begins, leaders should ask what else could be affected, what shares power or network infrastructure, and what other equipment occupies the same room or pathway.

Three Practical Prevention Measures

Add commissioning language to contracts. Require testing of the new system and its interactions with adjacent systems, not just a test of the installation in isolation.
Hold a pre-work coordination meeting. Bring the HVAC, security, network, facilities, and other relevant teams together before the project starts. Many integration problems can be identified before equipment is installed.
Create a buildingwide system map. Document which systems share power, networks, physical spaces, pathways, and backup resources. The map does not need to be elaborate to reveal important dependencies.

How Small Coordination Steps Prevent Major Problems

James shares an example involving a fire alarm panel upgrade. A simple check of the backup power arrangement revealed that the UPS expected to support the new panel was already close to capacity because of a recent security system expansion. Connecting the panel without that check could have overloaded the UPS and caused the fire alarm to fail during a power outage.

Michael recalls a separate generator project in which a new generator was tied into the same fuel line serving emergency lighting. When the generator was tested, the lights went out. Correcting the issue required reworking the fuel line, costing time and money that could have been avoided through earlier coordination.

What Facility Leaders Can Do Next

The episode closes with three actions leaders can begin immediately: ask every contractor what else the project could affect, require a practical integration test with adjacent systems, and document system interdependencies. A full commissioning process may not be necessary for every small job, but even a few hours of coordinated testing can reveal problems before they become outages, rework, or liability events.

The central lesson is simple: great work is not enough if it does not fit the whole building. Owners who take responsibility for integration become better project managers, build stronger relationships with contractors who understand the larger environment, and improve the reliability of the systems their tenants depend on. GDS Technology also offers a free checklist on cross-trade coordination at gds.technology.

The Contractor Calibration Gap: When Good Work Creates Hidden Risk

A contractor can complete a flawless installation, pass inspection, and still leave a building less reliable than it was before the project began. The issue is not always poor workmanship. Often, the problem is that the new work was evaluated as an individual system rather than as part of the entire building.

That disconnect is what Michael Harrington, a property management veteran, and James Rogers, a facilities engineering leader, call the contractor calibration gap. In a recent episode of Built, Wired & Secured, they explain why good work can create hidden operational risks—and what owners and facility leaders can do to prevent them.

What Is the Contractor Calibration Gap?

The calibration gap is the space between a system working perfectly on its own and working perfectly as part of an interconnected building.

Consider a contractor installing a new chiller. The chiller may run beautifully and meet every requirement in the project scope. But if the installation increases startup power demand beyond what the electrical panel can comfortably support, or releases additional heat into a room containing network switches, the project may create a new operational problem.

The same pattern can occur with building automation, access control, video surveillance, fire alarms, backup power, and network infrastructure. Each trade may perform its assignment correctly while the building experiences an unexpected failure at the boundary between systems.

Why the Risk Is Increasing

Buildings are more connected than they were in the past. HVAC, security, automation, and network systems increasingly share power, data, physical spaces, and backup resources. A change made by one vendor can therefore affect systems managed by several others.

Twenty years ago, many of these systems operated more independently. Today, a building automation controller may communicate across a network that also carries security camera traffic. An access control system may depend on shared network switches and backup power. A fire alarm panel may rely on a UPS that was sized before a security expansion. These relationships are easy to miss when each project is planned in isolation.

Occupants do not experience the resulting failure as a trade dispute. If the network drops, tenants cannot work. If doors go offline, people may not be able to enter. If cameras freeze, security teams lose visibility into areas such as parking garages. The building owner is left managing the operational consequences, regardless of which contractor performed the work.

A Building Automation Upgrade That Froze Cameras

James describes a retrofit in which a contractor upgraded a building automation system with new controllers and sensors. The work was completed properly, but the existing network was not reviewed as part of the project.

The new controllers communicated through the same switch carrying security camera traffic. Their polling rate was aggressive enough to cause packet loss, and the cameras began freezing. Initially, the network team blamed the security vendor, while the security vendor blamed the network. It took three weeks to trace the issue back to the building automation upgrade.

The consequences went beyond inconvenience. The security team could not reliably see what was happening in the parking garage, creating a potential liability concern. The BAS installation was not necessarily defective. The missing step was evaluating how the new traffic would interact with an existing system.

Scope Boundaries Do Not Remove Owner Risk

Why does this happen so often? One reason is the way projects are scoped. Contractors are usually hired to perform a specific job, and they often keep their scope narrow to remain competitive. That is a practical reality, not necessarily a criticism of the contractor.

However, a narrow scope does not eliminate the building’s integration risk. Someone still has to ask how the project affects shared power, network capacity, physical space, backup systems, and adjacent equipment. Michael and James argue that coordination is a shared responsibility, but the owner ultimately bears the risk.

That makes owner-led coordination essential. Facility leaders should not assume that every contractor will automatically understand the full building environment. Before work begins, they should ask direct questions:

What else could this project affect?
What equipment shares power with the new installation?
Will the project add traffic to an existing network?
What other systems are located in the same room?
What backup power, fuel, pathways, or controls are shared?

If a contractor cannot answer these questions, that is a signal to bring in the appropriate facilities, network, security, or engineering resources before work starts.

Three Ways to Reduce Integration Risk

1. Put commissioning requirements in the contract

Commissioning language should require more than confirming that the new equipment turns on. The contractor should test the new system’s interaction with adjacent systems. That can include network behavior, power transfer, backup operation, control signals, alarms, and other dependencies relevant to the project.

The requirement does not have to be complicated. A clear expectation that the installation will be tested as part of the building can prevent months of troubleshooting later.

2. Hold a pre-work coordination meeting

Bring the relevant trades together before installation begins. Depending on the project, that may include HVAC, building automation, security, network, electrical, life-safety, facilities, and property management teams.

A short coordination meeting can expose conflicts that are difficult to see in separate drawings or vendor proposals. It gives each team an opportunity to explain what it needs, what it will change, and what it depends on.

3. Document system interdependencies

A buildingwide system map does not need to be elaborate. A simple diagram can show which systems share power, network connections, physical rooms, pathways, UPS capacity, or other resources.

Without a map, every project begins with incomplete knowledge. With one, facility leaders can identify likely risk areas before approving changes. The map also becomes valuable when vendors change, systems are expanded, or an outage requires rapid troubleshooting.

Small Checks Can Prevent Major Failures

James shares an example involving a fire alarm panel upgrade. Before the new panel was connected, someone checked the backup power situation. That review revealed that the UPS intended to support the panel was already near capacity because of a recent security system expansion.

Connecting the fire alarm panel without that check could have overloaded the UPS and caused the fire alarm to fail during a power outage. A simple conversation with the security contractor prevented rework and avoided a serious life-safety risk.

Michael describes another project involving a new backup generator. The generator was tied into the same fuel line serving emergency lighting. During testing, the lights went out, revealing a dependency that had not been accounted for. Correcting the problem required reworking the fuel line, along with additional time and expense.

These examples show why integration work is not limited to large technology projects. The hidden dependency may be a network switch, a panel, a fuel line, a UPS, a control signal, or a piece of equipment in a shared room.

Great Work Must Fit the Whole Building

The most important lesson is that technical excellence is only part of project success. A system can be installed correctly and still create operational risk if it is not evaluated in context.

Owners and facility leaders can improve reliability by making integration part of the project from the beginning. Ask what else could be affected. Require a practical integration test. Document the dependencies that connect the building’s systems. These steps do not have to slow down a project or damage trusted contractor relationships. They give every contractor better information and give the owner a clearer way to manage risk.

As the episode emphasizes, great work is not enough. It has to fit the whole building. For more practical guidance, listen to this episode of Built, Wired & Secured and explore GDS Technology’s free cross-trade coordination checklist at gds.technology.

The Contractor Calibration Gap: When Good Work Creates Hidden Risk

Show Notes