Commissioning In Construction

Commissioning is “systems talking” - so where do you start?

What’s the first thing you do when a building “works” but the owner still complains? You usually chase a symptom - an air handler that won’t stabilize, doors that don’t coordinate with alarms, lights that stay on after occupancy. Then you find out the real problem: the systems never got a chance to talk to each other in the right sequence.

Commissioning in construction fixes that gap. It turns a pile of installed equipment into an integrated set of systems that performs to design intent - so the owner can take over without a guessing game. And it solves the biggest commissioning fear on job sites: “We built it, so why do we still have work to do?” The answer is simple: building is the install. Commissioning is the verification that the install meets how the building must operate for people, safety, and comfort.

After this chapter, you’ll know what commissioning actually means (not the version people summarize as “some testing”), why it gets hard fast, and how to frame your commissioning work as integrated systems - not as a checklist of inspections. You’ll also walk out with a practical way to set up the early schedule conversations that prevent rework later.

The Systems-Conversation Model: commissioning as integrated system verification

Here’s the core idea: commissioning doesn’t just check components. It verifies conversations between systems - who starts when, who signals who, what happens during normal operation, and what happens during upset conditions like a fire alarm. If you only inspect equipment and never run the sequences end to end, you end up with a building that looks complete but doesn’t behave correctly.

Ask yourself this: when you turn a switch on, what other systems must respond? In a real commercial job, the answer is often more than you think. HVAC changes airflow, controls send signals, lighting responds to occupancy logic, fire alarm outputs trigger shutdown or override modes, and the building management system (BMS) reports status. Commissioning forces those dependencies into the open and makes your team prove they work together.

The Systems-Conversation Model gives you a clean way to frame the work. You treat every commissioning activity as one of three “conversation targets,” then you schedule and test accordingly:

1. Define the conversation pairs (what talks to what).

Write down the system-to-system interactions you must verify. Example: smoke control mode triggers fan speeds; fire alarm outputs command dampers; occupancy scheduling changes lighting and HVAC setpoints. You don’t start with “we’ll test the fire alarm.” You start with “the fire alarm must drive these specific control actions.”

2. Define the conversation rules (how they must behave).

For each interaction, state the expected behavior: start/stop sequence, time delays, alarm priorities, and what “normal” versus “alarm” looks like. Example: when the fire alarm goes into alarm mode, the BMS must override occupied schedules and place designated zones into the required safety state within the control’s defined response window.

3. Run the conversation test (prove it with a controlled method).

You don’t “hope” the behavior works. You run test conditions and observe the complete chain: inputs, outputs, status points, and the final equipment response. Example: you simulate an alarm condition at the fire alarm panel, then you verify the damper position feedback point at the BMS and confirm the affected fan or AHU transitions to its commanded mode.

4. Record the conversation results (verify, then fix with a closed loop).

You document what happened, not just what you tried. When results don’t match, you route the corrective action, retest the same chain, and confirm the building behaves correctly after the fix. Example: if a damper “commands closed” but feedback stays “open,” you correct wiring, confirm point mapping, then retest the alarm-triggered sequence.

Drew Alvarez (26), assistant project manager on a mid-size commercial fit-out, learned this the hard way early in his career. He saw a lot of “we passed inspections” language, but the walkthrough still flagged issues: alarms didn’t produce the expected control responses, and the BMS didn’t show the right status during test mode. After he shifted his focus from “did the device pass” to “did the chain respond,” he stopped firefighting and started preventing repeat problems. That’s the difference the Systems-Conversation Model gives you: you control the order and the evidence.

Takeaway prompt: On your current project, list one complaint from the field and trace it back to a missing system-to-system conversation. What conversation did no one prove yet?

Why commissioning gets hard: the schedule and handoffs break the conversations

Commissioning feels hard because construction naturally breaks systems into packages....