It's a more common gap than people in the industry like to admit: ask someone on a construction site to define commissioning, and you'll often get an answer that's actually describing QA, QC, or project management instead. The terms get used almost interchangeably in casual conversation, and most of the time nobody notices, because the disciplines overlap enough that the confusion doesn't cause visible damage. It causes damage when it matters — when an owner assumes one of these functions is covering a risk that only a different one actually covers.
Commissioning (Cx) is its own discipline, distinct from the three it gets confused with most. Here's the actual difference, not the textbook definition.
What Commissioning Actually Is
Commissioning is the process of verifying that a building's systems perform as designed, under real operating conditions, before an owner accepts them. Not that they were installed. Not that they turn on. That they perform — a chiller holds setpoint through a summer peak, a redundant power system actually fails over the way the sequence of operations says it will, a life safety system responds correctly to the exact conditions it was designed to detect.
A commissioning agent's job is independent verification against the owner's project requirements, from design review through functional performance testing to post-occupancy verification. Commissioning doesn't build anything and doesn't manage the schedule. It exists to answer one question objectively: does this system actually do what it was designed to do.
How Commissioning Differs From QA
Quality Assurance is process discipline — the systems and procedures that are supposed to produce correct work in the first place. QA asks whether the right process was followed: was the concrete mix design approved before the pour, was the welding procedure qualified, was the submittal reviewed by the right people before fabrication started.
Commissioning doesn't care what process produced the installed system. It cares whether the finished system performs. A system can pass every QA checkpoint along the way — correct process, correct approvals, correct documentation — and still fail commissioning, because QA verifies the process was right and commissioning verifies the outcome actually works.
How Commissioning Differs From QC
Quality Control is inspection discipline — checking completed work against the spec. QC asks whether what got built matches what was drawn: is this conduit run installed per the drawing, does this weld meet the specified standard, is this equipment installed within the manufacturer's tolerances.
QC verifies conformance to a static reference — the drawing, the spec, the standard. Commissioning verifies dynamic performance — how the system actually behaves once it's running, interacting with every other system around it, under conditions that a static inspection can't replicate. A conduit run can pass QC inspection and still be part of a control system that fails commissioning because a sequence of operations doesn't behave the way the design intent required.
How Commissioning Differs From Project Management
Project management owns the schedule, the budget, and the coordination between trades — keeping a project moving toward substantial completion on time and within cost. A project manager's incentives are structurally tied to schedule and budget performance.
Commissioning's incentives are structurally tied to something else entirely: whether the systems actually work. That's precisely why commissioning has to report independently rather than through the project management chain — a commissioning agent who answers to the same schedule pressure as the PM has every incentive to sign off early, and an owner who lets that happen has quietly given up the one function whose entire purpose is catching problems before handover.
Why the Confusion Is Expensive
None of this is academic. An owner who believes QA/QC coverage means commissioning is redundant is skipping the one function that catches systems which were built correctly, to spec, by the book — and still don't perform as designed once they're running together as a whole facility. That gap doesn't show up in a QC checklist. It shows up during a summer peak, a power failover event, or an audit trail nobody can produce, months after the ribbon-cutting, when it's far more expensive to fix than it would have been to catch.
Frequently Asked Questions
If a project already has strong QA/QC, do you still need commissioning?
Yes — strong QA/QC reduces the number of things commissioning will find, but it doesn't replace the function. QA/QC verifies process and conformance; commissioning verifies that the finished, integrated systems actually perform together under real conditions, which is a different question neither QA nor QC is designed to answer.
Does commissioning report to the project manager?
It shouldn't, structurally. Commissioning's value comes from independence — reporting to the owner rather than through the same chain that's incentivized to protect the schedule keeps commissioning free to flag a system as not-ready even when that's an unwelcome answer.
What's the simplest way to remember the difference between the four?
QA asks if the right process was followed. QC asks if the finished work matches the spec. Project management asks if the project is on schedule and budget. Commissioning asks if the systems actually perform as designed. Four different questions, and skipping any one of them leaves a real gap the others don't cover.
