Quality control, government quality assurance, and commissioning can involve the same equipment and documents. They serve related purposes, but their responsibilities are not interchangeable.

The distinction should be established in the project requirements, staffing plan, and schedule. A team that treats commissioning as an undefined activity at turnover risks discovering too late that nobody has clearly assigned the testing, documentation, or operating handoff.

At the same time, the difference should not be exaggerated. Contractor QC can include performance testing, and commissioning also reviews installation and contract conformance. The useful question is who does what, against which requirements, and with what evidence.

Separate contractor QC from government QA

FAR 52.246-12 places responsibility for an adequate inspection system and complete inspection records on the contractor. It also provides for government inspection and testing without relieving the contractor of its responsibilities. [^1]

Calling all QA/QC “contractor-executed” obscures that division. The contractor manages its quality-control obligations; government personnel perform their assigned assurance and acceptance-related functions.

UFGS 01 45 00, Quality Control, provides the three-phase framework: preparatory, initial, and follow-up controls. Its current guide is August 2023 with Change 4, August 2026. The project’s tailored specification determines the detailed obligations. [^2]

A helpful responsibilities matrix should identify the contractor’s inspections and tests, the government’s review or witness activities, and the documents each role produces.

Commissioning connects installation with operation

FEMP describes commissioning as a process that checks performance against design intent and owner needs. For new construction and major renovations, it identifies design review, functional testing, system documentation, and operator training as elements of that process. [^3]

Consider an air-handling system as an illustrative example. Installation evidence might confirm equipment identification and the connections required by the contract. The operating evidence might then demonstrate the specified responses to occupied and unoccupied commands, changes in demand, or a defined interlock.

The test scope must identify which conditions apply. A test record should show the initial condition, command or event, expected response, observed response, and disposition of any failure. Simply recording that the fan ran leaves the intended sequence unverified.

Where systems interact, define the interfaces and responsibilities before testing. An integrated test should be scoped to the facility and the applicable requirements; not every project calls for the same fault simulations.

Shared equipment does not make QC and commissioning redundant. It makes their responsibilities worth defining early.

Keep the OPR and contract requirements aligned

The Owner’s Project Requirements can help articulate operating expectations. Its contractual status must still be checked.

UFGS 01 91 00.15, Building Commissioning, includes optional OPR language that identifies the document as being for commissioning review rather than a contract requirement. It also contains agency and delivery-method tailoring. An OPR should therefore not be described as automatically overriding, or independently expanding, an awarded contract. [^4]

If a review reveals a mismatch between an owner expectation and the contractual requirement, document it and route it through the authorized project process. The commissioning team should not silently change the acceptance criteria.

As a planning practice, give each test a traceable reference and resolve ambiguities before execution. That helps the contractor, commissioning specialist, and government reviewer evaluate the same condition.

Use the applicable commissioning arrangement

The unified commissioning guide includes a contractor-hired first-tier commissioning firm with specified independence requirements, as well as a government-hired option under Navy tailoring. It distinguishes direct reporting access from contractual authority. [^4]

The arrangement should be identified in the actual project documents. Do not infer that a commissioning subcontractor is automatically noncompliant, or that direct communication with a COR gives the specialist authority to direct contract changes.

For the project team, record who prepares the test procedures, performs the work, witnesses the test, reviews the result, corrects deficiencies, and determines acceptance. Identify how disagreements are escalated.

Plan readiness, correction, and turnover together

Build a commissioning schedule around the prerequisites for each test. As a practical checklist, consider installation completion, required startup and balancing, controls availability, safe access, approved procedures, and the attendance of the necessary trades.

Keep failed, incomplete, and deferred tests distinct. Each status should have a reason, an owner, and the next required action. Where seasonal testing is part of the contract, make its timing and documentation explicit rather than treating it as an informal promise.

At turnover, connect the accepted operating information with the materials used to train staff. Preserve unresolved issues and the agreed process for resolving them.

QC, QA, and commissioning work best when their evidence is coordinated and their authority is clear. Define those connections at the start of the project so that performance verification is a planned deliverable.