Show Notes
Why commissioning matters
A new building can look ready for tenants while its technology systems remain unproven. This episode examines the commissioning gap: the difference between installing equipment and verifying that it performs as the owner intended. The discussion focuses on systems that affect everyday operations and safety, including access control, network infrastructure, HVAC, building automation, and life safety.
The opening scenario illustrates the risk. Six months after a building opens, an access control system fails during a routine power test, leaving doors that should lock open. The system had been installed, but it had never been tested as a whole. The resulting security concern and scramble to diagnose the failure show why commissioning is more than a final checklist item.
Commissioning is a process, not a single test
Commissioning covers the full path from requirements to operational readiness. It begins before installation with planning, checklists, and submittals. It continues through installation checks, startup, functional testing, and integrated systems testing. It concludes with training and documentation. Skipping any of these steps leaves owners and operators without reliable evidence that a system works.
- Define the owner’s requirements and commissioning scope before installation.
- Inspect installation and use checklists during the work.
- Test individual components after they are installed and powered.
- Test connected systems together under realistic scenarios.
- Provide training and a report documenting tests, results, and resolved issues.
Testing individual devices is not enough. Building systems depend on one another. Access control may rely on network configuration; HVAC may depend on occupancy sensors or schedules; life-safety events may trigger door behavior. Commissioning verifies these connections rather than assuming that separately tested parts will work together.
Why the commissioning gap happens
Construction schedules and budgets put commissioning under pressure. A fixed move-in date can dominate decision-making, while commissioning is treated as work that can be compressed or performed alongside other tasks. But systems cannot be meaningfully tested before they are fully installed and powered. When time runs short, quality assurance is often the first thing squeezed.
Cost contributes to the problem. In a scrutinized project budget, commissioning can look like an extra expense. The discussion reframes it as an investment: a failure, emergency repair, security exposure, or tenant dispute can cost far more than testing. A few percent of project cost allocated to commissioning may help avoid a five-figure emergency repair later.
Responsibility and coordination
Commissioning can fall through the cracks when each participant assumes another party owns it. The general contractor may expect a subcontractor to handle it; the subcontractor may expect the engineer to catch problems; and the owner may assume the building will simply work. The episode emphasizes that accountability needs to be explicit.
Coordination matters because different trades often work in silos. Network, access control, HVAC, and building automation teams may each complete their own work without anyone verifying the integrated result. Owners should define who leads commissioning, who participates, what will be tested, and how issues will be resolved.
What failures look like in practice
One example involves a fire alarm linked to access control. The alarm and doors were tested separately, but not together. During an alarm, doors unlocked as intended; after the alarm reset, they did not relock. The building remained open for hours, and the issue came to light only when a tenant called. Integrated testing could have exposed the behavior before occupancy.
Another example involves HVAC scheduled to reduce operation after hours. Because scheduling was not integrated with occupancy sensors, the system ran at full output over a weekend. The tenant faced a large utility bill and was understandably unhappy. In both cases, the components could appear to function individually while the building-wide behavior failed.
These defects may surface months after handover, when contractors have left and warranties are expired or difficult to enforce. At that point, owners bear the operational cost, tenants experience the disruption, and the original project team may be harder to hold accountable. Documentation and timely testing help preserve a record of what was required and what was delivered.
Practical steps for owners and operators
- Require a commissioning plan. Make it specific to the building and its systems, and include it in the contract rather than treating it as an optional value-add.
- Set clear accountability. Identify the commissioning agent and the people responsible for each system and integration test.
- Protect time and budget. Schedule testing after systems are installed and powered, with time to correct defects and retest.
- Connect payment to deliverables. The discussion recommends the right to withhold final payment until the commissioning report is complete and signed off.
- Require documented results. The report should show what was tested, the results, and whether identified issues were resolved.
Documentation and accountable oversight are complementary. A commissioning agent provides ownership of the process; the report provides evidence that can help resolve disputes and support operations later.
Existing buildings can be commissioned, too
Commissioning is not limited to new construction. Retro commissioning can assess existing systems without requiring wholesale replacement. The participants describe energy savings as one possible return, while also emphasizing reduced risk—particularly where life-safety systems have not been verified. Owners can use the process to identify performance issues and improve confidence in the building they already operate.
Key takeaway
Commissioning is not simply a last-minute test or a binder of paperwork. It is a planned, accountable process that verifies equipment, integrations, and operational readiness. For owners planning construction or a major technology upgrade, the practical starting point is to demand a building-specific plan, budget for the work, and require documented results before accepting the system. A few additional days of testing can help protect tenants, budgets, and long-term building performance.
The building is open. Are its systems actually ready?
A ribbon cutting can make a new building feel complete. The doors open, tenants arrive, and the project team moves on. But installation and readiness are not the same thing. A system can be physically in place and still fail when it has to interact with other building systems under real operating conditions.
That distinction is at the center of the commissioning gap. In this episode, the conversation explores why building systems sometimes reach occupancy without rigorous verification, who is responsible for making sure commissioning happens, and what owners and operators can do to protect their buildings. The examples span access control, fire alarms, HVAC, occupancy sensors, networks, and building automation.
Commissioning means verifying the whole lifecycle
Commissioning is often mistaken for a final round of testing. Testing is part of the work, but commissioning begins earlier and continues beyond it. It starts before installation, with the owner’s requirements, a plan, checklists, and submittals. It carries on through installation inspections and startup. Then individual components receive functional tests, followed by integrated testing that checks how systems behave together. Training and documentation complete the process.
This broader approach matters because an owner needs more than a collection of devices that turn on. The owner needs the building’s systems to perform according to the requirements that were established for the project. Operators need to know how the systems work, and they need a record of what was tested and what issues were corrected. Without that foundation, the people responsible for the building are left hoping everything works.
Why schedules and budgets squeeze quality assurance
Construction projects operate under pressure. The move-in date is fixed, and work across the project bends around it. Commissioning may be treated as something that can be compressed or carried out in parallel with other tasks. But meaningful testing depends on systems being installed and powered. If the work is not ready, the integrated behavior cannot be verified.
Budget scrutiny adds another obstacle. Commissioning can appear to be an extra line item rather than an investment in operational performance. The discussion points out the mismatch in that calculation: a single failure can cost more than the commissioning process, whether through emergency repairs, security risk, wasted energy, or damaged tenant confidence. A few percent of project cost may help prevent a five-figure emergency repair later.
The schedule pressure is understandable, but leaving quality assurance until the end—or cutting it when the schedule slips—transfers risk to the owner and occupants. A plan needs to reserve time for testing and corrections, not just installation. If testing identifies a problem, there must be time to fix it and verify the fix.
When responsibility belongs to everyone, it can belong to no one
One reason commissioning gets missed is that project participants assume someone else owns it. A general contractor may expect the subcontractor to test the system. A subcontractor may expect an engineer to identify problems. The owner may believe that the project team has everything covered. Without explicit ownership, the work can fall between those assumptions.
Coordination is just as important as assigning responsibility. The access control contractor, network team, HVAC contractor, and building automation team may each focus on their own scope. Yet the systems depend on connections across those scopes. If the network is configured incorrectly, access control may not communicate. If building automation is not integrated with occupancy information, HVAC may not respond as intended. Someone must be accountable for verifying the interfaces.
Owners can reduce ambiguity by putting commissioning requirements in the project specifications and contract. The plan should name the scope, participants, schedule, deliverables, and accountable commissioning agent. It should not be left as an informal expectation or a vague promise to test at the end.
Why integrated tests catch the failures that component tests miss
A striking example in the conversation involves a fire alarm connected to access control. The fire alarm was tested, and the doors were tested, but the two systems were never tested together. When a minor alarm occurred, the doors unlocked—which was the intended response. The failure came afterward: the doors did not relock when the alarm was reset. The building remained open for hours, and a tenant eventually reported the issue.
Testing each part separately did not reveal what would happen across the full sequence. An integrated test could have simulated the alarm, checked that doors unlocked, reset the alarm, and verified that the doors returned to their expected state. The issue was not that the intended unlock behavior was wrong; it was that the complete scenario had not been tested.
HVAC provides another example. A system intended to ramp down after hours ran at full output all weekend because its schedule did not work with occupancy sensors. The result was a large utility bill and a frustrated tenant. As with the door issue, the real-world outcome depended on how separate functions interacted.
These are not abstract technical defects. They affect safety, security, costs, and the tenant experience. A tenant who finds doors unsecured may lose confidence in the building. A tenant paying for unnecessary energy may question how the property is managed. The failures can also become more expensive to address when they surface months after handover, after the contractor has moved on or the warranty has become difficult to enforce.
Make commissioning contractual, accountable, and documented
A commissioning plan should be specific to the building and the systems it contains. The conversation recommends making commissioning a contract requirement, with clear deliverables and a timeline. Owners should also consider linking final payment to completion and sign-off of the commissioning report. That creates a concrete incentive to finish the work and gives the owner a defined basis for acceptance.
Paperwork by itself does not make a building operate correctly. The process also needs an accountable commissioning agent who can coordinate participants and verify that the work is done. At the same time, documentation matters: the report is the record of what was tested, what the results were, and whether identified issues were resolved. Accountability and documentation support one another.
A practical sequence is straightforward:
- Before installation, establish the commissioning scope, team, and schedule.
- During installation, use inspections and checklists to confirm work is being completed correctly.
- After installation and startup, conduct functional tests of individual components.
- Run integrated tests that simulate realistic building scenarios and verify system interactions.
- Train operators and provide a final report documenting results and resolved issues.
Owners should not accept a system based solely on a device being installed or a contractor saying it works. They should ask what was tested, how it was tested, what failed, and how the team verified that corrections were successful.
Retro commissioning can help existing buildings
The same principle applies after a building has been occupied for years. Retro commissioning can assess existing systems and improve performance without replacing everything. The discussion notes that energy savings can help pay for some projects. It also highlights risk reduction, particularly where life-safety systems have not been verified. Owners do not have to wait for a new construction project to investigate whether their building performs as intended.
Invest in evidence of readiness
Commissioning is an investment in a building’s future, not simply an added construction expense. It helps owners verify that systems work individually and together, gives operators the information they need, and reduces the chance that tenants will discover defects first. For a planned build or major technology upgrade, demand a building-specific commissioning plan, budget for the process, and require documented results before sign-off.
To hear the full discussion and its examples of commissioning failures, listen to the episode. A little more time spent verifying the building can help avoid much larger costs and disruptions later.