Commissioning is where a lot of otherwise well-run jobs come apart. The building is 95% done, the finishes look great, the owner is already measuring for furniture — and then a functional test on the smoke-control sequence fails, the controls contractor is on another job, the balancer's report is two weeks out, and your certificate of occupancy slides right along with all of it. Commissioning is the phase where every trade's work finally has to prove it actually functions together, and it lands squarely on the critical path to turnover. That combination — high coordination, low float, and a hundred small prerequisites — is exactly what the Last Planner System was built to handle.
This isn't about buying software to solve commissioning. It's about running the front end of the job so the back end doesn't turn into a fire drill. The planning discipline is what matters; a good look-ahead tool just makes that discipline stick across a dozen subs who don't all read the same schedule.
Why Commissioning Breaks Normal Scheduling
Most of a project schedules linearly enough — frame, rough-in, close walls, finish. Commissioning doesn't. It's a web of dependencies where tests must run in a specific order, systems interact while you're testing them, and half the "activities" are really conditions that have to be true before anyone can push a button.
You can't functionally test air handling until the units are started, the VAV boxes are addressed, and the air is balanced. You can't run the smoke-control sequence until the fire alarm is programmed and the mechanical side responds to it. You can't verify emergency power transfer until the generator is commissioned and the transfer switches are wired and labeled. Miss one prerequisite and the whole test day evaporates — you've pulled four contractors to the site to watch each other point fingers.
The trap is that a bar-chart CPM schedule shows "Commissioning" as one clean 20-day bar near the end. That bar hides fifty micro-dependencies, and the person who owns those dependencies isn't the scheduler in the trailer — it's the foremen who know their own systems. That's the whole premise of pull planning and short-interval scheduling: the people doing the work commit to what's actually ready, and you surface the constraints six weeks out instead of the morning of the test.
Nail the Prerequisites Before Anyone Tests Anything
The single biggest cause of blown test days is starting functional testing on systems that were never truly ready. Pre-functional checklists exist for exactly this reason, and skipping them to "save time" always costs more than it saves.
Before a system goes to functional testing, four things need to be genuinely done — not 90% done:
- Installation complete and verified. Not "the ductwork's up" — every damper installed, every sensor mounted in the right spot, every device with power. Walk it with the pre-functional checklist in hand.
- Startup done and equipment running. Manufacturer startups completed, motors bumped for rotation, refrigerant charged, pumps running without cavitating. Get the startup reports in your hand; a verbal "yeah it's running" is not a startup report.
- Point-to-point checkout on the controls. Every physical point verified end to end — the sensor in the field reads correctly at the front end, the command from the BMS actually moves the actuator. This is the step people cheat, and it's the step that fails you in front of the commissioning agent.
- As-builts and documentation available. The tester needs the sequence of operations, the balancing report, and accurate as-builts. Testing a system against a sequence nobody can produce is a guaranteed rework loop.
Put these prerequisites into your weekly work plan as their own committed activities, with the responsible foreman's name on each one. When a task hits your look-ahead, the crew that owns it confirms the constraint is cleared before it's promised. That's the difference between "controls checkout — week of the 14th" and a red flag three weeks out that the controls contractor is short a tech and point-to-point won't finish in time to protect the test date.
Plan System by System, Then Plan the Interactions
Break commissioning down by major system first, because each one has its own crew, its own prerequisites, and its own tempo:
- HVAC — air handling and hydronics started, controls checked out, and then test-and-balance, because you can't commission air you haven't balanced.
- Electrical — normal power, emergency/standby power, transfer schemes, and lighting controls including any daylighting or occupancy sensors.
- Plumbing — domestic hot and cold, waste and vent, and gas, including any pressure and disinfection work that has its own hold times.
- Fire protection — sprinkler flow and tamper, fire alarm, smoke control, and any special suppression in electrical or kitchen spaces.
Sequencing within a system matters too. Balance the air before you commission the VAV sequences, or you'll chase phantom problems that are really just an unbalanced system. Megger and verify the feeders before you energize and test the transfer scheme, not after you've smoked something.
Once each system stands on its own, plan the integrated tests — where the real coordination pain lives. Smoke mode ties the fire alarm to the mechanical systems: the alarm calls for smoke control, and the air handlers, dampers, and exhaust fans all have to respond in the right sequence. Emergency power transfer ties electrical to fire and life safety: on loss of normal power, the generator picks up, and egress lighting, fire pump, and elevators do the right thing in the right order. The BMS integration test proves everything is actually talking. These tests need multiple contractors standing in the same room at the same time, which is precisely why they get scheduled badly and slip repeatedly.
Get the Right Bodies in the Room
An integrated test with a missing contractor isn't a partial test — it's a canceled one. When you plan a functional or integrated test, you're really scheduling an attendance list, and every name on it has to show up ready to run their part:
- Mechanical present to operate and adjust HVAC.
- Electrical present to switch power and prove the transfer schemes.
- Controls / BMS present to drive the sequences and override points on command.
- Test and balance with their report, ready to demonstrate numbers on site.
- The commissioning authority (CxA) witnessing and signing.
Coordinating that attendance is where a shared, current look-ahead earns its keep. When every sub is working off the same weekly work plan — and the crew leaders can see it on their phones instead of relying on a printout that's three revisions stale — a Thursday integrated test doesn't get ambushed by a controls tech who thought he was coming Friday. The commissioning agent's availability is usually the hardest constraint of all; a good CxA is booked across several jobs. Get their witness dates into your look-ahead early and build the test sequence around them, not the other way around.
Build in the Buffers and the Rework Loop
Here's the mistake that kills schedules: planning commissioning as if every test passes the first time. They don't. Functional testing finds problems — that's the entire point of doing it. If your schedule has zero room between "functional testing complete" and "certificate of occupancy," you've planned a fantasy.
A few rules of thumb worth building in:
- Assume a meaningful share of functional tests will kick out issues. On a typical mid-size commercial job, budget for a re-test loop on a real percentage of your systems, not one or two edge cases.
- Leave a buffer between each system's functional test and the integrated test that depends on it — a day or two — so a failed HVAC test doesn't automatically blow up smoke-control day.
- Every issue you log needs four things: a clear description, a responsible party, a scheduled correction, and a scheduled re-test. An issue with no re-test date isn't resolved; it's just deferred.
- Roll those corrections and re-tests back into the next weekly plan as real activities. This is where a rolling look-ahead shines — the issues log feeds directly into the next cycle instead of living on a spreadsheet nobody updates.
The teams that finish commissioning on time aren't the ones who never fail a test. They're the ones who expected to fail some, left room for it, and had a disciplined loop to close each issue out fast.
The Things People Forget Until They're the Problem
Seasonal tests. You can't fully load a chiller in January or prove heating in July. Decide early which tests get deferred to the right season, document the plan with the CxA, and don't let a deferred cooling test quietly hold your closeout hostage. Deferred testing is normal and acceptable — an ambushed superintendent discovering it the week of turnover is not.
Authorities having jurisdiction. The fire marshal's acceptance test, the elevator inspection, the health department sign-off on a commercial kitchen, the building inspector's final — these run parallel to commissioning and each has its own lead time and its own prerequisites. The fire marshal test in particular usually can't happen until fire alarm and smoke control are functionally proven, so it stacks right on top of your hardest integrated test. Get these dates on the look-ahead as milestones weeks out; you don't call the fire marshal on Tuesday for a Wednesday test.
Owner training and documentation. Training has to happen before the owner takes the building, the right owner personnel have to be there, and it's smart to record it — nobody remembers the boiler lockout sequence eight months later. O&M manuals, the commissioning report, and warranty documentation all feed closeout, and warranty periods often don't start until systems are commissioned and accepted. Treat training and turnover documentation as scheduled activities with owners' names on them, same as any other work.
Enhanced commissioning. On LEED or high-performance projects, expect extended testing scope, design-phase review periods, and sometimes post-occupancy monitoring. That's more calendar and more documentation, and it needs to be in the plan from the start rather than discovered as a surprise near the end.
Protect Testing From the Finish Trades
One coordination gotcha worth its own paragraph: sequence commissioning access before final finishes wherever you can, and protect finishes during any testing that comes after. Testers need to get to dampers, valves, sensors, and terminal units — the same places a ceiling grid and drywall want to hide. Prioritize commissioning-driven punch items ahead of cosmetic ones, and don't let a balancer pull a diffuser after the ceiling's painted if you can help it. Keep commissioning items ahead of the general punch list; a system that fails commissioning isn't a punch item, it's incomplete work.
Milestones Worth Tracking
Whatever tool you run, track commissioning against a handful of real milestones rather than one vague bar:
- Pre-functional complete — every checklist done, systems genuinely ready for functional testing.
- Functional testing complete — each system verified on its own.
- Integrated testing complete — systems proven working together, smoke mode and emergency power included.
- Issues resolved and re-tested — the log is closed, not just started.
- Final commissioning report issued — documentation in hand for closeout and warranty.
None of this requires software to be true. But commissioning is precisely the kind of many-hands, tight-sequence, low-float work where a shared short-interval schedule stops being a nicety and starts being the thing that keeps you off the critical path. A visual, location-based weekly work plan that every sub and every crew leader can actually see — with the trade-flow sequences connected so the smoke-control test can't be promised before its prerequisites clear — turns the usual end-of-job scramble into something you can steer. Tools like LookAheadWall exist to carry that plan into the field; the discipline of pulling the plan from the people doing the work is what actually saves the schedule.
Start commissioning planning the day systems begin going in, not the day the owner asks for a date. Put the prerequisites, the witness dates, and the re-test loop into your look-ahead early, run it every week, and commissioning stops being the phase that surprises you.