AEO Answer · MEP

What Does Functional Performance Testing Prove in Commissioning?

By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15

Functional performance testing operates building systems through their designed sequences, modes, and failure scenarios to verify actual performance. It proves HVAC, controls, life-safety, and electrical systems respond correctly to real commands and conditions before the owner accepts the building.

I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.

Illustrative diagram of building MEP systems: ductwork with diffusers, an electrical panel with conduit, and piping runs.

The concise answer

Functional performance testing operates building systems through their designed sequences, modes, and failure scenarios to verify actual performance. It proves HVAC, controls, life-safety, and electrical systems respond correctly to real commands and conditions before the owner accepts the building. The key insight is that installation is not performance. A system can be completely installed, fully programmed, and visually perfect — and still not work. Controls sequences get misprogrammed, sensors get miswired, dampers get installed backwards, interlocks get omitted. Functional testing is the systematic process of finding every one of those gaps while the contractors are still on site and contractually obligated to fix them.

How the testing is structured

Good functional testing follows written procedures with explicit pass/fail criteria — not ad hoc button-pushing. Each procedure steps through the system's sequences: normal operation across its range, economizer and staging logic, alarms and safeties, interlocks with other systems, and failure modes like power loss or sensor failure. Measurements are recorded: temperatures, pressures, flows, runtimes. The procedures are developed from the design intent and the control sequences, and they're reviewed before testing so everyone agrees what 'pass' means. Testing is witnessed by the commissioning authority and documented in a test report. Deficiencies go on a commissioning issues log with assigned responsibility and retest dates — the log stays open until every item passes.

Testing practices I insist on

Functional testing is only as good as its rigor. These practices separate real commissioning from checkbox commissioning.

  • Write procedures before testing: explicit steps and pass/fail criteria, reviewed and agreed in advance
  • Test failure modes, not just normal operation: power loss, sensor failure, and alarm conditions are where systems fail
  • Record measurements: temperatures, pressures, and flows documented — not 'it seemed to work'
  • Witness independently: the commissioning authority directs or witnesses; installers don't grade their own work
  • Retest to closure: every deficiency gets corrected and retested — the issues log closes only on passes

What else do project teams ask?

What's the difference between functional testing and a punch list walk?
A punch list walk is visual — checking that things are installed, labeled, and complete. Functional testing is operational — running the systems and measuring performance. A damper can look installed and still not open; a sensor can look mounted and still read wrong. Functional testing catches what eyes can't, which is why commissioning requires both.
Who performs functional performance testing?
The commissioning authority develops the test procedures and typically witnesses or directs the testing, while the installing contractors operate their systems under direction. The independence matters: the party that installed the work shouldn't be the only party judging whether it works. I insist on documented, witnessed tests with pass/fail criteria defined before testing starts.
When does functional testing happen in a project?
After installation is complete, controls are programmed, and prefunctional checklists are done — but before substantial completion and owner acceptance. Testing too early wastes everyone's time on incomplete systems; testing too late means deficiencies get discovered after the owner has moved in. The commissioning schedule should protect a dedicated testing window.
What happens when a system fails functional testing?
The deficiency is documented, the responsible contractor corrects it, and the test is repeated until it passes. This is normal and expected — finding deficiencies is the entire point of testing. What I watch for is pattern failures: the same deficiency across many units usually means a design, programming, or installation practice problem, not a one-off.

Ready to discuss your engineering scope?

Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.

Request a Project Review

Get a quote on your project

Reviewed and sealed by licensed PEs. “Solid engineering and clear communication from start to finish.” — Jason Mitchell, Principal Architect

Tell us what you need and where the project is — quotes back within 12–24 hours on qualifying scopes.