Building Commissioning Handover: The Evidence an Owner Needs Before Acceptance

What is the difference between starting equipment and proving system performance?

An air-handling unit fan starting up proves the equipment ran under one condition; it does not prove the system does what the owner needs. A functional test checks what happens when demand changes, a control signal arrives or a fault occurs, within an agreed scenario.

The Whole Building Design Guide (WBDG) describes verification test procedures as detailed instructions, with acceptable results, for thoroughly testing each system, and their results are recorded in functional and performance test reports. They are preceded by checklists, usually prepared by contractors and reviewed by the commissioning provider, documenting that each system is ready for testing. ^[3]

Each test procedure should therefore state the starting condition, the signal or change, the expected response, the measuring instrument, the result and any notes. Anything not written into the procedure cannot be judged at handover.

For example, “test the air-handling unit” is not enough. A procedure that can be judged reads more like this: when the zone temperature set point is raised, the chilled water valve is expected to close down and the temperature to settle within the limit stated in the OPR within a declared time, with readings taken from the building management system and from an independent instrument.

Where do the acceptance criteria come from?

Acceptance criteria are not invented on test day. WBDG explains that the owner originates the Owner’s Project Requirements (OPR) at project inception, that they should be available no later than pre-design, and that they are updated as the project develops. They cover goals, measurable criteria and success criteria, and they determine the commissioning activities and tests. ^[4]

ASHRAE/IES Standard 202-2024 sets the minimum acceptable commissioning process for new buildings and new systems, including new portions of buildings and new systems in existing buildings. It covers project delivery from pre-design through occupancy and operation, with minimum documentation and acceptance requirements. ^[2]

Existing buildings have a separate reference, ASHRAE Standard 230-2022, which sets minimum commissioning requirements for existing buildings and systems and leaves the owner to set scope and budget. ^[1] So define your project’s scope before choosing the reference.

What evidence file should the owner ask for?

Link every requirement in the OPR to a test, a location, a responsible party and a result. With that link the owner can ask of any requirement: where was it tested, who tested it, and what was the result?

WBDG lists the commissioning documents to expect, including functional and performance verification plans, forms and reports, issues and resolution logs, and preliminary and final commissioning reports. ^[4] It adds that the issues log records each issue, the date it was found, the responsible party and its status, and that the owner approves the resolutions. ^[3]

The file is incomplete without the systems manual. WBDG recommends that it be easy to understand, ideally delivered as an indexed, hyperlinked electronic file, and assembled before training begins. ^[3] The OPR sets the manual’s requirements, including how it is submitted and its format. ^[4]

How are open issues and deferred tests managed?

Not everything closes on handover day. WBDG notes that some systems cannot be fully tested during construction because of the weather, such as heating in summer or cooling in winter, and that plans should allow testing across more than one season, which often extends into initial operation. ^[3] It also asks for opposite-season verification to be built into the project schedule from the start. ^[4]

In practice, “to be completed later” in the handover minutes is not enough. For each deferred item, record:

• The required test and its acceptance criterion.
• The condition that allows it to be carried out, such as a given cooling load or specific operating conditions.
• The expected date, the party responsible and the resources required.
• The effect of the deferral on warranty or payments under the contract’s acceptance mechanism.

What applies to deferred tests applies to open issues too: each has a closure owner, a verification date and an assessment of its effect on operation.

Is training part of the evidence?

Yes, because the owner takes over the building for its own team to run, not the project team. WBDG explains that the OPR should set the training required for operations and maintenance staff, emergency response personnel and occupants, including the level of training, trainer qualifications and how it is documented. ^[4] ASHRAE publishes a separate guideline on operations and maintenance training within the HVAC&R commissioning process, and another on preparing systems manuals. ^[1]

An attendance sheet does not prove knowledge transfer. Stronger evidence is a hands-on demonstration by the site operator: tracing an alarm, finding the approved procedure in the systems manual and carrying out its first step.

Hypothetical example: a building handed over in winter

A hypothetical office building in the Gulf is handed over in winter, so the conditions needed to verify cooling performance under the seasonal load stated in the OPR are not available. The owner records the deferred test in the exceptions log, with its condition, an expected date the following summer, the resources the contractor will provide, and a link to the contract’s acceptance mechanism.

During training, the facilities manager asks an operator to trace a simulated alarm on the building management system and find the approved procedure in the systems manual. The exercise shows that some links in the electronic manual open files on the project team’s server, which the operations team cannot reach. An issue is added to the log, and the manual is not accepted until the files are moved and the exercise repeated.

What should the owner ask before signing acceptance?

Before signing, bring together the project manager, the commissioning provider and the facilities manager and review:

1. Does every requirement in the OPR have a completed test and a documented result?
2. Were the readiness checklists signed before the functional tests, not after?
3. How many issues are still open, and who owns closing each one, by when?
4. Which tests are deferred, and what is the condition for each?
5. Has the operations team accepted the systems manual after actually using it?
6. Have operators given a hands-on demonstration of the critical tasks?
7. Has the preliminary commissioning report been issued, and when is the final report due?

If the answer to any question is “don’t know”, that is an item for the issues log before signing, not after.

What do Gulf authorities require?

Requirements differ between countries and emirates, so no single example should be generalised. In Dubai, Version 2.0 of Dubai Municipality’s Green Building System (Al Sa’fat) includes a requirement for commissioning building services in new air-conditioned buildings with a cooling load of 1 MW or more. It covers air and water distribution, lighting, central control and building management systems, refrigeration and boilers, and requires commissioning to CIBSE codes or another standard approved by the Municipality. ^[5]

The same requirement asks for commissioning results to be recorded and available for inspection by the Municipality, and for a systems manual to be handed to the building operator when commissioning is complete. ^[5] Dubai Municipality’s website now lists a second edition of Al Sa’fat (January 2023) and marks the first as superseded, so confirm the clause and threshold in that edition before relying on them. ^[6] In other countries, review the national building code, the competent authority’s requirements and any green building rating system that applies.

Conclusion

Good acceptance is a decision based on evidence traceable to the owner’s requirements. Ask for functional tests with declared acceptance criteria, an issues log with named owners, a systems manual that works for the operations team, training proven by performance rather than attendance, and written closure terms for everything deferred.