Construction Commissioning in GCC: How to Hand Over Systems Without the 6-Month Extension

The moment construction declares "complete" and the moment a client can actually use the building are often separated by months. On large GCC projects — hospitals, mixed-use towers, data centres, industrial plants — commissioning failures routinely add 3 to 6 months to the programme. Liquidated damages tick, retention stays blocked, and your team stays mobilised. The root cause is almost never technical. It is a management failure: no register, no sequence enforcement, no pre-commissioning gate before systems are energised.

Pre-Commissioning, Commissioning, and Start-Up: The Distinction That Matters

Most GCC contractors treat commissioning as a single event — it is not. There are three distinct phases, each with its own deliverables and ownership:

Pre-commissioning is the contractor's work. Flush pipework, inspect equipment installations, verify cable terminations, complete loop checks, submit ITP records. Nothing gets energised or filled with process fluid until pre-commissioning is signed off. This phase is entirely within your control.

Commissioning is joint work. Vendor representatives, specialist subcontractors, and the client's commissioning team are all involved. Systems are powered up, performance is verified against specifications, and defects are recorded. This is where the sequencing problem lives — commissioning a chiller before the AHU is connected, or testing fire alarm systems before the building management system (BMS) is online, creates cascading failures and restart cycles.

Start-up and performance testing is the final phase before calling for inspection under FIDIC Clause 10.1. It verifies that systems perform as specified under real operating conditions — not just that they switch on.

Separating these phases in your commissioning register prevents the single biggest failure pattern: jumping to energisation before pre-commissioning is complete, then spending weeks troubleshooting problems that a loop check would have caught in 10 minutes.

What Your Commissioning Register Must Track

A commissioning register is not a punch list. It is a structured document that tracks every system and package through its commissioning lifecycle. For each item, you need at minimum:

• Work package reference — MEP zone, floor level, or discipline area
• System description — HVAC chiller group, LV switchboard MDB-3, fire suppression zone B
• Pre-commissioning completion date — signed off by subcontractor and QC
• Commissioning start date — when vendor and joint team begin
• Test certificates required — which certificates must exist before the item is closed
• Status — Not Started / Pre-Comm In Progress / Pre-Comm Complete / Commissioning / Complete / Defective
• Outstanding defect references — linked to the NCR or snag register
• Certificate issue date — when the system commissioning certificate is issued

On a 25-storey mixed-use tower in Riyadh, a typical commissioning register carries 400–600 line items. Without a single shared register, subcontractors report verbally, superintendents have different views of progress, and the client's commissioning manager operates from a separate document entirely. The gap between those documents is where delays hide.

Sequencing: The Most Underrated Challenge in MEP Commissioning

Large GCC projects involve multiple discipline-specific commissioning teams working simultaneously — HVAC, ELV, plumbing, fire systems, electrical, BMS. Each team has its own vendor representatives on different schedules. The sequencing failures are predictable:

• Power before panels — electrical commissioning teams try to energise distribution boards before LV panel FAT (Factory Acceptance Test) records are uploaded.
• Chiller before pipes — HVAC commissioning proceeds before pipework pressure tests and flush records are complete.
• Fire alarm before BMS — fire alarm testing proceeds independently, then fails integration with the BMS because integration points were not verified first.

The fix is a commissioning sequence matrix that defines predecessor relationships between systems. A simple dependency table — stating that "MDB-3 energisation requires LV DB FAT certificate and cable insulation test records" — gives your commissioning manager the enforcement tool they need to say no.

On a SAR 380M hospital project in the Eastern Province, missing this sequence discipline resulted in a BMS re-commissioning cycle that added 11 weeks to the programme. The technical failure — a communication protocol mismatch between BMS and HVAC controllers — took two days to fix. The documentation rework took 11 weeks.

FIDIC Clause 9 and the Clause 10.1 Call: Your Contractual Framework

FIDIC Silver Book (EPC) and Yellow Book (Design-Build) both place commissioning obligations explicitly on the contractor under Clause 9 (Tests on Completion). The contractor must carry out all required tests and provide documentation before issuing the Notice of Completion under Clause 10.1.

If you issue a Clause 10.1 notice and the client's engineer identifies missing commissioning documentation, the notice fails. The 28-day TOC clock does not start. Worse, if you have already demobilised supervision staff in anticipation of TOC, you are now remobilising at full cost to manage a documentation exercise.

The practical implication: track your Clause 9 deliverables in your commissioning register. Every test certificate, every performance record, every vendor commissioning report the contract requires — it should have a line item, an owner, and a due date. The Clause 10.1 call is only made when every line item is green.

For Aramco, NEOM, and ROSHN projects, the baseline is the approved inspection and test plan. SAEP-316 specifies exact hold points and witness requirements at commissioning. NEOM projects typically require a Commissioning Management Plan approved before commissioning begins. Treat these requirements as register entries — named deliverable, due date, responsible party.

Managing Multi-Vendor Coordination

Large GCC projects involve 8–15 specialist vendors for commissioning — chillers, lifts, escalators, generators, UPS, fire suppression, BMS, CCTV, access control. Each vendor arrives on a fixed schedule, often from outside the Kingdom, with mobilisation costs running SAR 25,000–80,000 per visit.

An uncoordinated vendor mobilisation — where the site is not ready for the vendor's specific task — results in standby or remobilisation costs plus programme extension. On a SAR 450M commercial tower in King Abdullah Economic City, uncoordinated lift vendor mobilisation cost SAR 340,000 in unnecessary standby across four visits that could have been consolidated into two.

Your commissioning register prevents this by giving each vendor a clear readiness gate: a named list of pre-commissioning tasks that must be complete before their scope begins. Build a readiness certification step into your vendor subcontracts — your commissioning manager signs off that the site is prepared before any mobilisation date is confirmed.

Five Starting Steps

• Build the commissioning register at contract award, not at construction completion. Draft it in the first 60 days and review it monthly. By the time you need it, it must already exist.
• Define three status gates for every system. Pre-commissioning complete (contractor sign-off), commissioning complete (joint sign-off with client), certificate issued (document in register). No system progresses until the prior gate is closed.
• Create a commissioning sequence matrix. List the 15–20 critical sequence dependencies across disciplines. A one-page dependency table gives your commissioning manager a documented basis to enforce sequence and reject premature energisation requests.
• Tie vendor mobilisation to readiness certificates. Before confirming any specialist vendor mobilisation date, your commissioning manager must sign a readiness certificate confirming the site is prepared for that scope. Build this requirement into vendor subcontracts at award.
• Track commissioning certificate completion as a KPI on your monthly report. Percentage of systems with pre-commissioning complete, commissioning complete, and certificate issued gives your client visibility and gives your programme team the early warning signal they need to protect the Clause 10.1 notice date.

The 6-month commissioning extension is a solvable problem. It is caused by treating commissioning as an event rather than a process. A structured register, clear sequence dependencies, and document discipline convert commissioning from the phase where GCC projects go wrong into the phase where they close out on time — and where your retention gets released.