Commissioning · Reviewed 10 September 2026

Make every acceptance claim traceable.

A neutral procurement framework for turning owner requirements into package tests, integrated scenarios, defect decisions and an operational handover record.

Browse commissioning suppliers

Requirement basis

Write the acceptance chain before testing starts

Current UK property guidance plans the transition into operations from the start of a construction project. The GSA guide likewise carries commissioning from planning through occupancy. Put requirements, roles, evidence and handover gates into the procurement package early enough to affect design, supplier scope and programme.

Input 1

Owner requirements

Record the services the facility must support, operating states, resilience intent, environmental limits, safety constraints, maintainability needs and evidence required for acceptance. Keep design authority with the responsible specialists.
Input 2

System and package boundaries

Map each electrical, mechanical, controls, security, fire, network and life-safety package to its interfaces. Name the party responsible for every shared signal, utility, dependency and test condition.
Input 3

Test sequence

Set the order for document review, factory evidence, delivery inspection, installation checks, start-up, functional tests, integrated scenarios and seasonal or deferred work. Define entry criteria for each gate.
Input 4

Witness and data plan

Name the test author, performer, witness and approver. Specify instruments, calibration, sampling, timestamps, trend data, alarms, settings, photographs and result format before the test is run.
Input 5

Defect and change rules

Define severity, containment, retest scope, deviation approval, configuration control and the conditions for accepting open work. Preserve the link from each issue to the affected requirement and result.
Input 6

Operational handover

Set the manuals, asset data, settings, spares, training, drills, permits, warranties, maintenance tasks, escalation routes and post-occupancy checks required before the operator takes control.

Evidence matrix

Join every requirement to a result and owner

Evidence set

Requirements baseline

Comparison record

Approved owner requirements, design basis, system list, operating modes, interfaces, acceptance criteria and change record

Accountable input

Owner, operator and design authority

Evidence set

Commissioning plan

Comparison record

Scope, roles, programme, dependencies, safe systems of work, test environments, witness points and gate entry criteria

Accountable input

Commissioning manager and package leads

Evidence set

Package readiness

Comparison record

Approved submittals, factory evidence, delivery checks, installation records, inspections, pre-start checks and outstanding constraints

Accountable input

Supplier, installer and quality lead

Evidence set

Functional evidence

Comparison record

Controlled scripts, instruments, raw readings, trends, event logs, alarm states, settings, witnessed results and deviations

Accountable input

Test lead, witness and design authority

Evidence set

Integrated evidence

Comparison record

Scenario, initial condition, simulated event, system response, recovery path, human actions, timing, dependencies and result

Accountable input

Commissioning authority and operator

Evidence set

Handover and aftercare

Comparison record

Defect status, configuration baseline, manuals, asset data, training record, drills, maintenance plan and deferred-test schedule

Accountable input

Project owner and operations lead

Acceptance gates

Separate readiness, performance and handover decisions

Technical acceptance

Control the initial state and the recovery

An integrated scenario is useful only when the approved starting condition, simulated event, expected sequence, timing, alarms, operator actions and recovery state are clear. Store the raw evidence with the signed outcome and any approved deviation.
Operational acceptance

Make readiness a separate gate

CIBSE connects commissioning with operational readiness at handover. Confirm trained people, controlled documents, asset data, maintenance tasks, spares, escalation routes, safe operating instructions and the owner of deferred work before service responsibility transfers.

Offer comparison

Compare the evidence chain, test conditions and handover

01

Compare the controlled process

Ask how each bidder will turn one approved requirement into a script, witnessed result, issue record, retest and signed close-out. A list of test names does not show that chain.
02

Price the test conditions

Compare temporary loads, utilities, instruments, software access, vendor attendance, fault simulation, safe isolation, witness time, repeat tests and out-of-hours work on the same basis.
03

Keep the operator in the loop

Compare when operators review scripts, attend tests, receive training, practise abnormal scenarios, accept asset information and own unresolved or deferred work.

Build the research set

Connect the plan to the directory

Use the filtered records to identify organisations for further research, then issue the same requirements, responsibilities and evidence matrix to every candidate. Directory inclusion is not proof of competence, independence, design responsibility, test quality, capacity, availability or successful delivery.

Primary references

Sources used for this guide

The current standard says construction projects should plan the transition into operations from the outset and maintain attention to it throughout delivery.
The active GSA guide provides a commissioning framework from project planning through occupancy and identifies team participation across the process.
The active 2022 code frames commissioning management around safe delivery, operational readiness at handover and performance against the specified needs of users and operators.
The Playbook sets out commercial practices for assessing, procuring and delivering public works and gives buyers a reference point for early planning, roles and supplier engagement.

Sources checked 10 September 2026. Requirements vary by facility, system, operating model, market and contract; confirm the applicable design, test, safety, regulatory and acceptance obligations with the responsible specialists and authorities.