A commissioning plan is the document that sets out how a project will take its systems from mechanical completion to safe start-up and handover: what is in scope, who does what, in what sequence, to which procedures, with which records, and through which certificates. A useful plan covers scope, organisation, systemisation, sequence, procedures, documentation, the completions system, handover and safety, and is specific enough that a new commissioning engineer could pick it up and know how the project works.
Many projects call it a commissioning execution plan or commissioning management plan, and some split it into a high-level philosophy and a more detailed execution plan. The outline below works for either approach.
What a commissioning plan is for
A commissioning plan does three jobs:
- It agrees the rules between owner, contractor, vendors and operations before the pressure starts: stage definitions, certificate chain, punch categories, sign-off authorities.
- It drives upstream work. Systemisation, construction sequencing, vendor requirements and document deliverables all need to be set up to suit commissioning, months before commissioning starts.
- It is a reference during execution. When there is a dispute about whether a system is ready, the plan is what people go back to.
A plan that is written to satisfy a contract deliverable and then filed will fail at all three. Write it to be used.
When to write it
Start the commissioning plan during detailed design, once the process and utility schemes are stable and the contract strategy is known. An early issue can carry the philosophy and structure; later revisions add the detailed sequence, procedures list and resources. Revise it at defined points: before construction starts, before the first mechanical completion, and before first energisation are sensible triggers.
Section-by-section outline
The table gives a typical structure. Adjust headings to the owner's template if one is required.
| # | Section | Key content |
|---|---|---|
| 1 | Introduction and purpose | Project description, objectives, reference documents, definitions |
| 2 | Scope and interfaces | What is in and out; contractor, vendor and owner scopes; interfaces |
| 3 | Organisation and responsibilities | Commissioning team structure, roles, sign-off authorities |
| 4 | Systemisation | System and subsystem breakdown, boundaries, numbering |
| 5 | Stages and certificates | Stage definitions, certificate chain, prerequisites, punch rules |
| 6 | Sequence and schedule | Commissioning priority, utility-first logic, key milestones |
| 7 | Procedures | List and hierarchy of commissioning procedures and test procedures |
| 8 | Inspection and test records | ITR sets by discipline and stage; ITP linkage; witnessing |
| 9 | Completions system | Tool, data structure, workflows, reporting |
| 10 | Punch and issue management | Categories, who raises and clears, review cadence |
| 11 | Safety and control of work | Permit to work, isolations, transition of control, MOC |
| 12 | Vendors | Vendor representatives, pre-commissioning and commissioning scopes |
| 13 | Operations readiness and training | Operations involvement, procedures, training |
| 14 | Handover | Handover dossier contents, TOC process, exceptions |
| 15 | Reporting and meetings | KPIs, dashboards, meeting structure |
| 16 | Appendices | Registers, templates, forms, marked-up drawings |
1. Introduction and purpose
Keep it short. Describe the facility, the commissioning objectives (for example, first power export or first product by a given milestone), and list the governing documents: contract, owner's commissioning philosophy, completions procedure, HSE plan. Include a definitions section. Terms like "mechanical completion", "ready for commissioning" and "handover" mean different things to different companies, and defining them here avoids arguments later.
2. Scope and interfaces
Say exactly what the commissioning team is responsible for and what it is not. Common grey areas include pre-commissioning (construction or commissioning?), vendor packages, owner-furnished equipment, tie-ins to existing plant and temporary facilities. For brownfield work, describe interfaces with the operating asset and who controls them.
3. Organisation and responsibilities
Include an organisation chart and a responsibility matrix. Typical roles:
- Commissioning manager
- System or area commissioning leads
- Discipline commissioning engineers (mechanical, electrical, instrumentation, control systems)
- Completions manager and completions coordinators
- Vendor representatives
- Owner's commissioning representatives and operations staff
- QA/QC and HSE interfaces
Crucially, state who can sign each certificate and each ITR stage, and who can approve a deviation.
4. Systemisation
Summarise the system and subsystem breakdown, the numbering convention, how boundaries are defined and where the marked-up P&IDs and single line diagrams live. State when systemisation will be frozen and how changes are controlled. See systemisation in commissioning for the detail behind this section.
5. Stages and certificates
Define each stage (construction, mechanical completion, pre-commissioning, commissioning, start-up, handover) and the certificate that closes it. For each certificate, list the prerequisites, the signatories and which punch categories may remain open. Certificate names and sequences differ between owners, so write your project's chain down explicitly. The typical chain is described in commissioning certificates explained.
6. Sequence and schedule
Set out the commissioning logic: usually utilities first (power, instrument air, nitrogen, water, control systems, fire and gas), then process systems in the order needed for start-up. Give construction a subsystem priority list so it can complete by system rather than by area. Show the key milestones and link to the integrated schedule.
7. Procedures
List the procedures that will govern execution:
- Completions procedure
- Pre-commissioning procedures by activity (flushing, pressure testing reinstatement, loop checking, electrical testing)
- Commissioning test procedures by system
- Energisation procedure
- Start-up procedures (usually owned by operations)
State who writes, reviews and approves each type, and the target date for approval ahead of use. Commissioning test procedures should include prerequisites, isolations, step-by-step instructions with expected results, hold points, acceptance criteria and sign-off.
8. Inspection and test records
Define the ITR sets by discipline and stage, typically "A" records for mechanical completion and "B" for pre-commissioning, and how they link to the inspection and test plans. The relationship between ITPs, ITRs and checksheets is covered in ITP vs ITR vs checksheet. Include the witnessing approach: which tests need owner or third-party witnessing, notice periods and how witnessing is recorded, as described in hold points and witness points.
9. Completions system
Describe the system of record: which tool, how the tag register is loaded, how records are created and closed, who has access and how progress is reported. Specify how paper or offline records are brought into the system and how quickly. If the owner requires a particular handover data format, state it here.
10. Punch and issue management
Define the punch categories used on the project, who can raise and grade items, who clears and verifies them, and how often the punch list is reviewed. Also cover how NCRs, technical queries and RFIs relate to the punch list, so that the same defect is not tracked in three places.
11. Safety and control of work
This section must be specific. Cover:
- The permit-to-work system during each stage and when it changes
- Isolation management and lock-out arrangements
- How live and non-live systems are segregated and identified on site
- Energisation controls and notifications
- Management of change for design or procedure changes during commissioning
- Pre-start-up safety reviews before introducing hazardous media
12 to 16. Vendors, operations, handover, reporting and appendices
Vendors: list packages requiring vendor representatives, their scope and the notice they need. Operations readiness: describe how operations staff are integrated into commissioning and trained on the systems they will take over. Handover: define the handover dossier contents per system, the TOC process and how exceptions are recorded. Reporting: set the KPIs (ITR completion by subsystem, punch trends, certificate status) and the meeting cadence. Appendices: system register, certificate templates, ITR index, marked-up drawings and procedure register.
Commissioning plan checklist
Before issuing the plan, check that it:
- Defines every stage and certificate in your project's terms
- States who can sign each certificate and approve deviations
- References a frozen or freeze-dated systemisation
- Gives construction a subsystem priority list
- Lists every procedure needed and its approval deadline
- Specifies the completions system and how records reach it
- Defines punch categories and review cadence
- Explains how permits and isolations change as systems go live
- Describes handover dossier contents per system
- Has been reviewed by construction, operations and the owner, not just commissioning
Managing this in Accord
Accord can act as the completions system your plan describes. It structures work by project, system, subsystem and tag; manages A and B ITRs with witnessing; enforces a configurable certificate chain; tracks Category A/B/C punch items that block stage gates; and supports commissioning test procedures with revisioning, hold-point enforcement and step-by-step execution. Works planning, work packages and scheduling sit alongside, as do permit to work, change requests, and per-system handover dossiers with required-document matrices. Real-time dashboards give the progress reporting the plan calls for.
Frequently asked questions
What is the difference between a commissioning plan and a commissioning execution plan?
Terminology varies. Some projects use a single commissioning plan; others separate a high-level commissioning philosophy (principles, stages, certificates) from a commissioning execution plan (sequence, resources, procedures, schedule). The content is similar; the split is about level of detail and ownership.
Who writes the commissioning plan?
Usually the contractor's commissioning manager, with input from completions, construction, engineering, vendors and HSE, and review and approval by the owner. On owner-led projects, the owner may write the philosophy and require the contractor to produce the execution plan.
Is there a standard commissioning plan template?
There is no single universal template. Owners often supply their own, and the outline above covers the sections most templates contain. Whatever template you use, make sure stages, certificates, responsibilities and safety arrangements are specific to the project.
How long should a commissioning plan be?
Long enough to answer the questions people will ask during execution, and no longer. Keep registers, templates and detailed procedures in appendices or separate documents, and keep the main body focused on rules, responsibilities and sequence.
How often should the commissioning plan be updated?
Revise it at defined milestones, such as before construction starts, before first mechanical completion and before first energisation, and whenever a significant change affects scope, sequence or responsibilities. Changes should go through normal document control.