Commissioning is where a building either proves it works or exposes every corner that got cut during the rush to close out. It's the phase that verifies systems actually perform the way the design intended — that the chillers stage correctly, the smoke dampers close on alarm, the VAV boxes hit their setpoints, and the building automation system does what the sequence of operations says it does. Done right, the owner takes a building that runs from day one. Done poorly, they take one that's fighting comfort complaints and change orders through the entire first year.
The hard part isn't the testing itself. It's the coordination. Commissioning drags a commissioning agent, the mechanical and electrical subs, the controls contractor, a test-and-balance firm, and often the manufacturer's factory rep into the same rooms, in the right order, after the work in front of them is genuinely complete. That's a scheduling problem before it's anything else, and it's exactly the kind of problem a look-ahead schedule is built to solve. This article walks through how the commissioning sequence really unfolds on a jobsite and where good field scheduling keeps it from derailing.
Why Commissioning Belongs in Your Look-Ahead Weeks Before You Think It Does
The single most common mistake superintendents make with commissioning is treating it as a closeout task — something that lives in the last two weeks of the job with the punch list and the final cleaning. By then it's too late. Functional testing has hard prerequisites, and if you haven't been driving those prerequisites in your weekly work plans for the previous month, you'll show up to your first test with a commissioning agent standing there billing hourly while your controls tech tells everyone the graphics aren't loaded yet.
Pull commissioning into your rolling three-to-six week look-ahead the moment mechanical rough-in is topping out. You're not scheduling the tests yet — you're scheduling the things that have to be true before a test can happen. Power to the equipment. Controls terminated and points mapped. Start-up completed by the manufacturer. Test-and-balance finished and reported. Water treatment in the loops. Each of those is its own mini-sequence with its own trade, and each one that slips pushes your first functional test to the right.
Get the Sequence Right: Start-Up, TAB, Then Functional Testing
There's a natural order to this work, and violating it is how you end up testing the same system three times. Roughly, it goes:
- Point-to-point verification and pre-functional checklists. Before anyone runs a system, the controls contractor confirms every physical point maps to the right software point — that the sensor labeled "AHU-3 supply air temp" is actually reading AHU-3's supply air, not the return. This is tedious and it is where controls jobs live or die.
- Equipment start-up. The manufacturer's rep energizes and starts the major equipment, confirms rotation, refrigerant charge, and safeties. Never let TAB or functional testing get ahead of start-up. A fan you balance before the rep confirms the belt tension and rotation is a fan you balance twice.
- Test, adjust, and balance. TAB sets the airflows and water flows to design. This has to finish before functional testing because functional performance is measured against balanced conditions. Testing a VAV system that hasn't been balanced tells you nothing useful.
- Functional performance testing. Now the commissioning agent drives the systems through their sequences — heating and cooling modes, occupied and unoccupied, economizer operation, failure and alarm response — and verifies the building responds as designed.
Sequence these as dependencies in your look-ahead, not as a wish list. Start-up feeds TAB, TAB feeds functional testing, and functional testing feeds the issues log. When one predecessor slips, everything downstream of it should visibly slide with it so you can see the collision coming. That trade-flow dependency view — where you connect one activity's finish to the next activity's start and watch the whole chain react — is the entire reason a tool like LookAheadWall earns its place on a job like this.
Pre-Functional Checklists: Don't Bring the Cx Agent to a System That Isn't Ready
The pre-functional checklist is your gate. It's a signed confirmation from the responsible sub that a system is installed, started, and ready for functional testing — filters in, dampers stroked, valves confirmed, controls online. The commissioning agent should not schedule a functional test until that checklist is back and complete.
Here's the discipline that saves you: make the pre-functional checklist a scheduled deliverable with the sub's name on it, one to two weeks ahead of the functional test date. Not a verbal "yeah it's ready." A returned document. The most expensive hour on a commissioning job is the commissioning agent, the controls tech, and the mechanical foreman all standing in a fan room discovering that a control valve was never wired. Every one of those hours is avoidable with a checklist you actually enforced in your weekly work plan.
The Issues Log Is the Real Deliverable — Track It Like a Punch List
Every functional test generates findings. A damper that doesn't fully close. An economizer that won't engage. A pump that short-cycles. These land in the commissioning issues log, and the log becomes a second punch list running in parallel with your architectural one — except this one has a diagnostic step before the fix, because someone has to figure out whether it's a mechanical, controls, or design problem before anyone can correct it.
Treat issue resolution as scheduled work, assigned to a responsible party, with a retest date attached. The failure mode here is silent: an issue gets logged, everyone nods, and it sits for three weeks because nobody owns the retest. Then you're back for a second commissioning mobilization you didn't budget for. Put each open issue and its retest into the look-ahead the same way you'd schedule any other crew activity — with a name, a date, and a dependency on whatever fix has to happen first. A field scheduling tool that lets you assign an activity to a sub and share the plan with them keeps the log from becoming a graveyard.
Building Automation and Controls: Budget More Time Than You Want To
If your project has a serious BAS, understand now that controls commissioning will take longer than any single trade's estimate suggests, and it will find problems no one else can. Point-to-point verification alone on a mid-size commercial job is days of work, and it routinely surfaces reversed sensors, mislabeled points, and sequences that were programmed to an older revision of the specification.
Two rules of thumb from experience. First, the controls contractor needs the systems energized and the network up well before your first functional test — get power and controls online as an explicit look-ahead milestone, not an assumption. Second, don't schedule integrated systems testing — the coordinated stuff, like the fire alarm releasing a smoke control sequence that repositions dampers and fans — until each individual system has passed on its own. Integrated tests fail for boring reasons when the underlying systems weren't clean first, and each failed integrated test is a full remobilization of multiple trades.
Coordinating the Commissioning Agent's Time
The commissioning agent usually isn't on site full-time. They fly or drive in for scheduled testing windows, which means their availability is a genuine constraint you're scheduling around — not a resource you can summon on a day's notice. Give the Cx agent a realistic look at what will actually be ready when they arrive, and protect that window.
The trust-killer is calling an agent to a testing window and having half the systems not ready. Do it twice and the agent starts padding their schedule and their invoice. Share the look-ahead with them directly so they see the same prerequisite chain you do and can plan their trips around reality. A schedule that everyone can see, subs included, beats a stack of emails that no two people are reading the same way.
Documentation and Turnover: Start Collecting Early, Not at the End
Commissioning produces a paper trail: pre-functional checklists, functional test forms, the issues log, the final commissioning report, and it feeds the O&M manuals and owner training. The mistake is treating documentation as an end-of-job scramble. Collect start-up reports and test-and-balance reports as they're generated, not when someone finally asks for the closeout binder in month eleven.
Owner training is part of this too, and it has to be scheduled against system completion — you can't train facilities staff on a system that isn't running. Line up training sessions in the look-ahead once functional testing on a given system passes, while the controls tech and manufacturer's rep are still on site and still remember the details. Record what was covered and who attended; that record matters more than anyone expects the first time a warranty dispute comes up.
Don't Forget Seasonal and Warranty-Period Testing
Some tests genuinely can't happen at turnover. You can't fully test heating performance in July or peak cooling in January. These get deferred to the appropriate season, and deferred work has a way of being forgotten — the general contractor has demobilized, the superintendent is on another job, and the seasonal test that was promised nine months ago quietly evaporates.
Assign deferred seasonal tests to a responsible party with a target month before you leave the site, and put a marker in the schedule that outlives your presence on the job. The same goes for warranty-period and post-occupancy commissioning that's increasingly written into contracts. It's not glamorous scheduling, but it's the difference between closing a job clean and getting a phone call the following winter.
The Bottom Line
Commissioning isn't a phase you bolt onto the end of a project — it's a dependency chain that reaches back a month or more into your mechanical and electrical work, and it succeeds or fails on whether you drove the prerequisites in your weekly work plans before anyone showed up to test. Get start-up, TAB, and functional testing in the right order. Enforce the pre-functional checklists as real gates. Own every issue on the log with a name and a retest date. Give the commissioning agent an honest schedule and protect their windows. Do that, and the owner gets a building that works from the day they take the keys — which, in the end, is the whole point of the exercise.