Commissioning Plan

Definition

A commissioning plan is the master document that defines how each system on a project will be tested, verified, and transitioned from the construction team to the operations team. It sequences pre-commissioning (mechanical completion, static testing), commissioning (functional testing under simulated load), and initial operations (performance testing under real load). On any project with mechanical, electrical, or process content — a hospital, a factory, a data centre, an oil refinery, a wastewater plant — commissioning is where good projects prove themselves and where bad projects unravel.

Core Components

• System list — every system that needs commissioning, uniquely numbered.
• Commissioning sequence — the order in which systems must be brought online (chilled water before air handling, DC power before controls, etc.).
• Test procedures — one per system, with acceptance criteria.
• Responsibility matrix — who witnesses each test (owner, engineer, vendor, third-party).
• Punch list closure protocol — how defects are managed during commissioning.
• Turnover packages — the dossier of records handed to operations for each system.
• Training plan — how the operations team is trained on each system before takeover.

Real-World Construction Example

A 640-bed teaching hospital had a commissioning plan spanning 187 systems across HVAC, medical gas, electrical, low-voltage, fire, and specialised departments (imaging, laboratories, operating theatres). The commissioning window was six months. What made it work: the sequence was locked eight months before it started, based on the dependencies — no air handling could be commissioned before its chilled water loop, no operating theatre before its air handling, no isolation-room before its operating theatre. What nearly derailed it: the electrical contractor treated commissioning as "we'll energise it and see". A senior commissioning manager was appointed six months into the construction phase — earlier would have been better — and rebuilt the plan with the vendors around the table. Total defects identified during commissioning: 2,900. Total remaining at handover: 12, all cosmetic.

Real-World IT / Agile Example

Commissioning translates directly to the launch readiness process for a complex software platform. A multi-country e-commerce launch had a "commissioning plan" in all but name: 47 system components (payment gateways, tax engines, warehouse APIs, CDN, CMS, authentication, analytics), sequenced dependency-first (identity before checkout, checkout before payments, payments before analytics), with a test procedure per component and a witnessed acceptance sign-off. The pattern from construction — locked sequence, defined witnesses, controlled defect management — worked cleanly. The launch was on time; the previous attempt (without a formal readiness plan) had missed by 11 weeks.

Levels of Commissioning

• Pre-commissioning — cleanliness, static tests, insulation checks. No power, no fluids.
• Commissioning — functional test under simulated conditions. Energised, but not fully loaded.
• Initial operations / performance test — real load, real users, real production data.
• Handover — turnover packages transferred, operations team accepts responsibility.

Expert Tips

• Appoint a commissioning manager during construction, not during commissioning. A commissioning manager parachuted in three weeks before energisation is set up to fail.
• Lock the commissioning sequence early. Once construction sequences are set with commissioning as an afterthought, expensive rework is inevitable.
• Build the turnover packages progressively. Do not wait until the last week to compile system dossiers — do them as each system is completed.
• Involve the operations team early. They must witness tests they will later own, or they will refuse acceptance.
• Separate mechanical completion from commissioning readiness. A system can be mechanically complete but not commissioning-ready (missing test connections, missing settings sheets). Do not blur the two.

Common Mistakes

• No commissioning manager until late — sequence chaos, no owner in the room.
• Commissioning treated as "energise and hope" instead of a formal test programme.
• Test procedures written by the commissioning contractor without owner review — acceptance criteria too loose.
• Turnover packages compiled retrospectively from incomplete records.
• Operations team first sees the plant on handover day and refuses acceptance.

Practical Lessons Learned

• Every project I have seen underestimate commissioning has done so by 30–60%. Every project that has staffed it early has finished on time.
• Third-party commissioning agents (independent of the construction contractor) reduce disputes at handover because their sign-off is credible to the owner.
• The single best investment on a complex project is a dedicated turnover-package coordinator running from month three, not month thirty.

Key Takeaways

• Commissioning is a distinct phase requiring its own plan, its own manager, and its own budget.
• Lock the sequence early and build construction around it, not the other way around.
• Involve operations from the start; they are the final accepting party.
• The same discipline applies to complex software launches — a launch readiness plan is a commissioning plan under a different name.

Related Encyclopedia Entries

• Operational Readiness
• Snagging Process
• Work Package
• Milestone Payment

Related Research Articles, Case Studies & Tools

• Commissioning Templates
• Project Controls Academy: Delivery & Handover
• Hospital commissioning case study