The readiness decision
A commissioning readiness review should answer a defined decision, not simply collect status information.
- What activity or milestone is being authorised?
- Which system, subsystem or area is included?
- What starting condition is required?
- Which prerequisites must be complete?
- Which outstanding items can remain under control?
- Which items prevent safe or meaningful execution?
- Are procedures, people, equipment and utilities ready?
- Are connected-system interfaces available?
- Are acceptance criteria and restoration requirements defined?
- Is the evidence sufficient for the approving authority to decide?
A review is effective when it produces a clear decision supported by traceable evidence, assigned actions and an understood system condition.
1. Define the milestone being reviewed
Begin by defining the exact transition or activity for which readiness is being assessed. Different milestones require different evidence and must not be treated as interchangeable.
Examples may include:
- mechanical-completion acceptance;
- release for pre-commissioning;
- electrical energisation;
- introduction of utilities;
- flushing or cleaning;
- functional testing;
- control-system integration;
- equipment start-up;
- performance testing;
- sea trials;
- operational handover.
The review should state:
- the intended activity;
- the system or area involved;
- the planned date or execution window;
- the required starting condition;
- the required final condition;
- the authority making the readiness decision.
“Ready for commissioning” is too broad unless the specific activity and system state are defined.
2. Establish system boundaries
Readiness must be assessed against a controlled system boundary. Without a clear boundary, teams may report completion against different scopes or overlook dependencies outside the immediate equipment package.
The boundary review should identify:
- system and subsystem limits;
- physical isolation points;
- electrical supply boundaries;
- control and communication interfaces;
- supplying and receiving systems;
- shared utilities;
- temporary facilities;
- connected equipment;
- excluded areas;
- ownership at each interface.
Use approved system definitions, drawings, marked-up diagrams or boundary registers where available.
3. Define measurable readiness criteria
Readiness criteria should be established before the review and should describe objectively verifiable conditions.
Criteria may cover:
- construction completion;
- inspection and test records;
- punch status;
- approved procedures;
- available utilities;
- permits and isolations;
- equipment configuration;
- software and settings;
- vendor attendance;
- calibrated test equipment;
- operations participation;
- temporary systems;
- emergency arrangements;
- restoration requirements;
- acceptance documentation.
Avoid criteria such as:
- substantially complete;
- nearly ready;
- expected to be finished;
- minor work only;
- no major concerns;
- ready apart from paperwork.
A readiness criterion should allow a reviewer to determine whether the condition is met, not invite interpretation during the meeting.
4. Review mechanical completion and construction status
Confirm that the physical installation has reached the level required for the planned commissioning activity.
Review evidence may include:
- completed inspection and test records;
- system walkdowns;
- construction completion certificates;
- equipment installation checks;
- alignment and mechanical condition;
- piping and tubing completion;
- cable installation and termination;
- earthing and bonding;
- lubrication and consumables;
- guards and protective devices;
- access and maintainability;
- labelling and identification;
- housekeeping and foreign-material control.
The required construction status depends on the planned activity. A system may be ready for one limited test while remaining unsuitable for energisation, operation or handover.
Construction completion should be demonstrated by inspected condition and accepted records, not only by reported progress.
5. Classify punch items and outstanding work
Not every open item has the same effect on readiness. Outstanding work should be classified according to its impact on safety, function, test validity, access, restoration and final acceptance.
Blocking items
Work or defects that prevent safe execution, invalidate the planned test, compromise protection or leave the system condition uncontrolled.
Controlled outstanding items
Items that do not prevent the defined activity but require ownership, limitations, monitoring or completion before a later milestone.
Close-out items
Documentation, finishing or minor work that can remain after the activity without affecting safety, function or evidence, subject to agreed completion controls.
For every open item, record:
- description;
- system;
- location;
- category;
- owner;
- required completion date;
- effect on the planned activity;
- temporary control where applicable;
- evidence required for closure.
6. Verify technical documentation and configuration
The review should confirm that execution will be based on current, approved and traceable technical information.
Relevant documents may include:
- system definitions;
- approved drawings;
- equipment data sheets;
- control narratives;
- cause-and-effect diagrams;
- settings schedules;
- manufacturer manuals;
- commissioning procedures;
- test sheets and ITRs;
- risk assessments;
- method statements;
- permits and isolation plans;
- technical queries;
- approved deviations;
- software and configuration records.
Confirm that:
- important documents have identifiable revisions;
- field configuration matches the approved basis;
- superseded information is removed from use;
- approved changes are reflected in the execution documents;
- unresolved technical queries are visible.
A complete installation can still be unready when the execution team cannot establish which technical basis is current.
7. Confirm safety, authority and operating control
Readiness includes the ability to control the work and the system state safely throughout execution.
Confirm where applicable:
- executing authority;
- operating authority;
- permit responsibility;
- isolation ownership;
- lockout or tag control;
- energy-source identification;
- stored-energy controls;
- emergency-stop arrangements;
- exclusion zones;
- simultaneous-operations controls;
- communication method;
- stop-work authority;
- abnormal-condition response;
- safe interruption point;
- restoration authority.
The review should identify who may:
- authorise the start;
- operate the equipment;
- change the system state;
- pause or stop the work;
- approve a deviation;
- accept the result;
- release the system after completion.
A technically complete system is not ready when authority, isolation control or the safe operating boundary remains unclear.
8. Confirm utilities and supporting services
Many commissioning activities depend on services outside the immediate system boundary. These dependencies should be verified rather than assumed.
Supporting services may include:
- permanent electrical supply;
- temporary electrical supply;
- instrument air;
- service air;
- hydraulic power;
- cooling water;
- fuel;
- lubrication;
- ventilation;
- drainage;
- communications;
- control-system availability;
- lighting;
- lifting or access equipment;
- waste handling;
- environmental control.
For each dependency, confirm:
- required condition;
- supplying system;
- responsible owner;
- availability period;
- capacity or limitation;
- contingency;
- restoration requirement.
A system is not ready when a required utility is only expected to become available after execution begins.
9. Review procedures and test records
The approved execution procedure should match the actual system condition, planned activity and available interfaces.
Confirm that the procedure defines:
- purpose;
- scope;
- responsibilities;
- prerequisites;
- safety controls;
- starting condition;
- execution sequence;
- expected results;
- hold and witness points;
- acceptance criteria;
- abnormal-result response;
- temporary configurations;
- restoration;
- required records;
- final acceptance.
Also confirm that:
- the correct revision is available;
- referenced drawings and documents are current;
- required test sheets are prepared;
- result fields are usable;
- witness requirements are understood;
- the procedure has been reviewed against the real installation.
An approved procedure is not sufficient when it no longer represents the installed system or the planned execution sequence.
10. Confirm people, competence and vendor support
Readiness depends on the required people being available, competent, briefed and clear about their responsibilities.
Review:
- commissioning personnel;
- discipline engineers;
- operators;
- safety representatives;
- construction support;
- control-room personnel;
- vendor representatives;
- client or Class witnesses;
- marine or lifting support;
- emergency-response support;
- final accepting authority.
Confirm where applicable:
- role;
- competence;
- authority;
- attendance time;
- mobilisation status;
- access approval;
- briefing requirements;
- communication method;
- shift or handover arrangements.
Do not treat a name on an attendance list as proof that the required competence or authority is available.
11. Confirm tools, instruments, materials and spares
The review should establish that the practical resources needed for execution and recovery are available.
Check where applicable:
- calibrated test instruments;
- specialist tools;
- temporary hoses or cables;
- communication equipment;
- consumables;
- lubricants and fluids;
- test media;
- seals and gaskets;
- replacement components;
- critical spares;
- approved temporary equipment;
- lifting accessories;
- barriers and identification materials;
- data-recording equipment.
For test instruments, confirm:
- identification;
- measurement range;
- calibration status;
- suitability for the environment;
- required accuracy;
- availability for the full execution period.
A readiness review should consider the resources needed to respond to a failed test as well as those needed for the planned successful sequence.
12. Review interfaces and dependent systems
Commissioning failures frequently occur at interfaces rather than within the primary equipment package.
Review dependencies involving:
- electrical supply;
- control and communication systems;
- process inputs and outputs;
- alarms and trips;
- upstream equipment;
- downstream equipment;
- common utilities;
- safety systems;
- shutdown systems;
- marine systems;
- temporary systems;
- operations control;
- external vendors or contractors.
For each important interface, confirm:
- owner;
- required state;
- communication method;
- acceptance evidence;
- test sequence;
- restoration responsibility;
- limitation or outstanding work.
An interface should not be declared ready by one party when the connected party has not confirmed the same condition.
13. Confirm controls, software and protection status
Physical completion alone does not demonstrate readiness where function depends on software, logic, communications, settings or protective devices.
Confirm where applicable:
- approved software version;
- configuration backup;
- control logic;
- cause-and-effect implementation;
- alarm settings;
- trip settings;
- permissives;
- interlocks;
- inhibits;
- bypasses;
- overrides;
- simulated signals;
- communication links;
- time synchronisation;
- access permissions;
- change history.
Any temporary inhibit, override or simulation should have:
- purpose;
- owner;
- approval;
- identification;
- operating limitation;
- monitoring requirement;
- removal point;
- final restoration evidence.
14. Confirm operating and handover readiness
Where operations will participate in testing or receive the system after completion, their requirements should be included before the activity begins.
Review where applicable:
- operating procedures;
- operator familiarisation;
- control-room displays;
- alarm presentation;
- equipment identification;
- access and maintainability;
- routine inspection requirements;
- consumables;
- spare parts;
- maintenance information;
- known limitations;
- preservation requirements;
- final operating mode;
- handover records.
Commissioning completion and operational acceptance are related but distinct decisions. The review should identify which decision is being made and who owns it.
15. Control exceptions, deviations and temporary conditions
A readiness review should make every exception visible. Unresolved conditions should not be hidden inside general comments or optimistic completion statements.
For each exception, record:
- description;
- technical basis;
- risk;
- affected activity;
- owner;
- approval;
- temporary control;
- monitoring requirement;
- expiry or review date;
- required final action;
- evidence for closure.
Do not use readiness approval to legitimise an uncontrolled temporary condition.
A deviation may be accepted only by the appropriate authority and only when its effect on safety, function, test validity, restoration and future milestones is understood.
16. Conduct the readiness review
The review meeting should confirm evidence and decisions rather than become the first occasion on which teams discover the status.
Before the meeting
- issue the scope and milestone;
- distribute the readiness criteria;
- identify required attendees;
- collect evidence;
- update action status;
- highlight known exceptions;
- confirm the decision authority.
During the meeting
- review the boundary;
- confirm each criterion;
- distinguish evidence from expectation;
- identify conflicting status;
- classify outstanding items;
- assign actions;
- record conditions;
- make the readiness decision.
After the meeting
- issue the decision record;
- confirm action owners and dates;
- record limitations;
- update the system status;
- communicate the approved operating boundary;
- schedule revalidation where required.
The meeting should resolve the decision, not replace the preparation needed to support it.
17. Record the readiness outcome
Use a clear outcome that reflects the evidence and the defined milestone.
Ready
All mandatory criteria are met, blocking items are closed, required controls are in place and the activity may proceed under the approved procedure.
Ready with controlled conditions
The activity may proceed with explicitly recorded limitations, actions or temporary controls that have appropriate ownership, approval and expiry conditions.
Not ready
One or more unresolved conditions prevent safe execution, invalidate the planned test, leave the system state uncontrolled or remove the evidence needed for meaningful acceptance.
The outcome should identify:
- reviewed system and milestone;
- decision date;
- evidence basis;
- open conditions;
- action owners;
- approval authority;
- validity period;
- trigger for re-review.
Do not use a conditional decision when the unresolved condition is actually a blocker.
18. Revalidate after change
A readiness decision is valid only for the system condition and execution basis that were reviewed.
Revalidation may be required after:
- construction change;
- software or setting change;
- new punch item;
- failed test;
- temporary intervention;
- isolation change;
- utility interruption;
- procedure revision;
- personnel or vendor change;
- delay beyond the agreed execution window;
- damage or environmental event;
- change in connected-system status.
The review does not always need to be repeated in full. The approving authority should determine which criteria and interfaces are affected and what evidence must be reconfirmed.
Readiness can be lost after approval when the system, evidence or execution conditions change.
Readiness review and PSSR are not interchangeable
A commissioning readiness review may be used before several different activities and can focus on a system, test, energisation, vendor intervention or handover milestone.
A pre-start-up safety review is a specific control before introducing operating energy, hazardous materials or process conditions, according to the project, facility and regulatory requirements.
The two reviews may share evidence, including:
- completion status;
- procedures;
- safety systems;
- training;
- alarms and trips;
- permits and isolations;
- emergency arrangements;
- temporary conditions;
- outstanding actions.
However, completing a general readiness review should not be presented as completion of a required PSSR unless the defined PSSR scope, authority, criteria and approvals have been satisfied.
Worked example: readiness for electrical energisation
The following simplified example demonstrates the review method without replacing project-specific energisation procedures, electrical safety rules or competent technical authority.
Milestone
Controlled energisation of a completed distribution system to support subsequent functional testing.
Defined boundary
The review covers the incoming supply, switchboard, outgoing feeders included in the energisation scope, protection configuration, earthing, control interfaces and the systems that will receive power.
Mandatory criteria
- installation inspection accepted;
- required test records complete;
- earthing and bonding verified;
- protection basis approved;
- energisation procedure approved;
- isolation and access controls established;
- affected personnel briefed;
- downstream boundaries confirmed;
- temporary supplies identified;
- emergency response agreed.
Outstanding work
Several final labels and one non-critical enclosure finish item remain open. These do not affect electrical safety, protection, operation, isolation or the validity of the energisation activity and are retained as controlled close-out items.
Blocking finding
One outgoing feeder boundary cannot be confirmed against the latest drawing and field identification.
Decision
Not ready.
Required action
Resolve the feeder identity, update the controlled boundary evidence, inspect the corrected condition and reconvene the affected part of the readiness review.
The example shows why a high overall completion percentage cannot override one unresolved condition that affects isolation, system identity and safe execution.
Commissioning readiness review checklist
- Define the exact milestone or activity being reviewed.
- Identify the decision authority.
- Confirm system and interface boundaries.
- Establish measurable readiness criteria.
- Verify mechanical completion and construction status.
- Review inspection and test evidence.
- Classify punch items by consequence.
- Confirm approved drawings and technical documents.
- Verify software, settings and configuration status.
- Confirm procedures and test records.
- Establish permits, isolations and operating authority.
- Confirm utilities and supporting services.
- Confirm personnel, competence and vendor attendance.
- Verify calibrated instruments and practical resources.
- Review connected-system dependencies.
- Confirm alarms, trips, permissives and interlocks.
- Control temporary supplies, bypasses, overrides and simulations.
- Confirm abnormal-result and restoration arrangements.
- Include operations and handover requirements.
- Record deviations, limitations and expiry conditions.
- Distinguish evidence from expected future completion.
- Assign actions with owners and dates.
- Record Ready, Ready with controlled conditions or Not ready.
- Define the validity period and revalidation triggers.
- Communicate the approved system state and limitations.
Minimum readiness-review record
The record should allow another competent person to understand what was reviewed, which evidence supported the decision and which conditions remained at the time of approval.
- project or asset;
- system and subsystem;
- milestone or activity;
- review date;
- planned execution window;
- boundary definition;
- readiness criteria;
- evidence references;
- completion status;
- punch summary;
- interface status;
- procedure revision;
- permit and isolation status;
- utilities status;
- personnel and witness status;
- temporary conditions;
- deviations and limitations;
- blocking items;
- actions and owners;
- readiness outcome;
- validity period;
- revalidation triggers;
- approving authority.
Readiness is an evidence-based decision
A commissioning readiness review should create a common factual position before the system changes state.
When boundaries, prerequisites, interfaces, authority, procedures, resources, acceptance criteria and restoration are visible, the project can make a controlled decision and focus effort on the conditions that genuinely affect execution.
When readiness is reduced to a percentage or meeting-room assurance, unresolved risks and dependencies are transferred into the test, start-up or handover activity.