Commissioning, Startup & Operational Readiness: A Complete Guide

Author: Fidelis Associates | Published: 2026-03-02 | Last Updated: 2026-03-02

Meta Description: Commissioning, startup, and operational readiness (CSU) ensure new or modified facilities achieve safe, reliable first production. Learn ORR, PSSR, turnover governance, and SIMOPS best practices.

---

Definition

Commissioning, startup, and operational readiness (CSU) is the structured process of verifying, testing, and transitioning new or modified facilities — from petroleum refineries and petrochemical plants to LNG terminals and hydrogen production facilities — from construction to safe, reliable operations. CSU encompasses system-by-system verification of installed equipment, formal handoff from project to operations teams, regulatory safety reviews, and the controlled introduction of process fluids to achieve first production. Effective CSU programs prevent startup incidents, reduce schedule delays, and establish the foundation for long-term operational reliability.

---

Table of Contents

1. Commissioning vs. Startup vs. Turnover
2. The Operational Readiness Review (ORR)
3. Pre-Startup Safety Review (PSSR)
4. SIMOPS Risk Management
5. How Should Turnover Governance Be Structured?
6. Control Room Readiness
7. What Are the Most Common Startup Failures?
8. How to Assess Your Operational Readiness

---

Commissioning vs. Startup vs. Turnover

These three terms are often used interchangeably, but they refer to distinct phases with different objectives, activities, and responsible parties. Confusing them leads to gaps in accountability and missed verification steps.

Commissioning

Commissioning is the systematic process of verifying that installed systems and equipment function as designed. It occurs after mechanical completion (construction is physically finished) and before startup (process fluids are introduced).

Commissioning activities include:

• Instrument loop checks — verifying that every instrument reads correctly, sends signals to the correct controller, and alarms at the correct setpoints
• Motor and rotation checks — confirming that pumps, compressors, fans, and other rotating equipment spin in the correct direction and operate within design parameters
• Valve stroking — testing that every control valve, isolation valve, and safety valve operates through its full range
• Electrical system testing — verifying power distribution, switchgear operation, grounding, and emergency power systems
• Piping pressure tests — hydrostatic or pneumatic testing to verify piping integrity
• Safety system function tests — confirming that emergency shutdown (ESD) systems, fire and gas detection, and relief systems operate as designed
• Utility system verification — testing instrument air, cooling water, steam, nitrogen, and other utility systems

Commissioning is typically led by the project team with support from the equipment vendors and construction contractor. It is system-by-system work — each system is verified independently before systems are integrated.

Startup

Startup is the controlled introduction of process fluids (hydrocarbons, chemicals, feedstocks) into the verified systems to achieve initial production. Whether at a petroleum refinery introducing crude feed, a chemical manufacturing facility starting a reactor, or a hydrogen production facility beginning electrolysis, startup is a higher-risk activity than commissioning because it involves hazardous materials under operating conditions for the first time.

Startup phases typically include:

• Inerting and purging — removing oxygen from process systems using nitrogen before introducing flammable materials
• Initial feed introduction — gradually introducing process fluids at reduced rates
• Heat-up and catalyst activation — bringing reactors and process units to operating temperatures
• Performance testing — verifying that the process achieves design throughput and product specifications
• Optimization — adjusting operating parameters to achieve stable, efficient production

Startup is typically led by operations with support from the project team, process licensor, and commissioning specialists.

Turnover

Turnover is the formal handoff of responsibility from the project team to the operations team. It is not a single event but a structured process that occurs in stages:

• System turnover — individual systems are turned over to operations as they complete commissioning
• Area turnover — physical areas of the facility are transferred from construction to operations control
• Final turnover — the entire facility is formally accepted by operations, project warranties are activated, and the project team demobilizes

Turnover governance — who signs, what criteria must be met, how exceptions are handled — is one of the most critical and most frequently mismanaged aspects of the CSU process.

---

The Operational Readiness Review (ORR)

The Operational Readiness Review is a structured assessment that confirms the facility, its people, and its management systems are ready for startup. ORR is the final decision gate before introducing process fluids and is conducted after commissioning is substantially complete.

What ORR Evaluates

A comprehensive ORR examines readiness across multiple dimensions:

• Operating procedures — Are procedures written, reviewed, approved, and available in the field? Do they cover normal operations, startup, shutdown, and emergency scenarios?
• Training and competency — Have operators been trained on the specific equipment and procedures? Have they demonstrated competency through practical exercises or simulations?
• Safety systems — Are all safety-critical systems (ESD, fire and gas, relief devices) tested, functional, and properly documented?
• Punch list status — Are Category A (safety-critical) punch list items closed? Is there a plan and timeline for remaining Category B and C items?
• Permits and regulatory compliance — Are all operating permits in place? Have regulatory notifications been completed? Are environmental monitoring systems operational?
• Maintenance readiness — Are spare parts available? Is the computerized maintenance management system (CMMS) populated with equipment data and preventive maintenance schedules?
• Emergency response — Is the emergency response plan complete and communicated? Have emergency drills been conducted? Are emergency response resources (fire protection, medical, security) available?
• Staffing and organization — Is the operations team fully staffed? Are shift schedules in place? Are roles and responsibilities clear?
• Management of change — Have all changes since the original design been properly managed through MOC? Have associated hazard evaluations been completed?

Who Conducts the ORR

ORR teams typically include:

• Operations leadership — the operations manager and senior operators who will be accountable for the facility
• Process safety — PSM and HSE professionals who evaluate safety system readiness
• Engineering — process, mechanical, and instrument engineers who verify technical readiness
• Maintenance — maintenance leadership who confirm equipment and spares readiness
• Independent reviewers — experienced personnel from other facilities or third parties who provide objective assessment

The most effective ORRs include a mix of internal and external reviewers. External reviewers bring fresh perspective and are less likely to rationalize gaps that internal teams have become accustomed to.

Common ORR Gaps

The following gaps appear repeatedly in ORRs across industries:

• Operating procedures that exist on paper but have not been walked down in the field
• Training records showing classroom attendance but no verification of practical competency
• Safety system punch items classified as non-critical when they should be Category A
• Incomplete MOC reviews for field changes made during construction
• Emergency response plans that have not been tested through realistic drills
• CMMS data entry deferred because "we'll catch up after startup"

---

Pre-Startup Safety Review (PSSR)

The Pre-Startup Safety Review is a regulatory requirement under OSHA PSM (29 CFR 1910.119(i)) that must be completed before introducing highly hazardous chemicals into new or modified facilities. PSSR is distinct from ORR — it is a specific, compliance-required verification.

What PSSR Requires

OSHA requires that PSSR confirm:

1. Construction and equipment are installed in accordance with design specifications
2. Safety, operating, maintenance, and emergency procedures are in place and are adequate
3. A process hazard analysis has been performed for new facilities, and recommendations have been resolved or implemented before startup
4. Training of each employee involved in operating a process has been completed
5. For modified facilities: the management of change requirements have been satisfied

Multi-Party vs. Single-Party PSSRs

In complex projects — particularly those involving an owner, EPC contractor, and multiple subcontractors — PSSR responsibility can become fragmented. Multi-party PSSRs require clear governance:

• Who initiates the PSSR process
• Who signs off on each verification item
• How conflicts between parties are resolved
• What documentation transfers from the project to operations

Single-party PSSRs (where one organization is both constructor and operator) are procedurally simpler but still require discipline to avoid treating PSSR as a rubber-stamp exercise.

Common PSSR Gaps

• PSSR conducted too late in the schedule, leaving no time to address findings before startup
• Checklist items marked complete without field verification
• PHA recommendations listed as "resolved" when they are only "in progress"
• Training verified by attendance records rather than competency demonstration
• Modified facilities that bypass PSSR because the change was classified as "like-for-like"

For a detailed guide to PSSR requirements and best practices, see What is a Pre-Startup Safety Review (PSSR)?.

---

SIMOPS Risk Management

Simultaneous Operations (SIMOPS) occur when construction, commissioning, and operations activities overlap in time and space. SIMOPS are common during phased startups, brownfield modifications, and turnarounds where parts of a facility are operating while adjacent areas are still under construction or commissioning.

Why SIMOPS Create Risk

SIMOPS introduce hazards that do not exist when construction and operations are separated:

• Ignition sources in proximity to flammable materials — welding and cutting near live hydrocarbon systems
• Safety system conflicts — fire and gas systems may be inhibited in construction areas while operations depends on them
• Communication gaps — construction and operations teams may use different radio channels, different permit systems, and different emergency procedures
• Shared utilities — nitrogen, instrument air, and electrical systems may serve both construction and operating areas
• Egress conflicts — emergency escape routes may be blocked by construction activities or equipment

Managing SIMOPS Effectively

Effective SIMOPS management requires:

• SIMOPS risk assessment — a formal evaluation of the interactions between concurrent activities, conducted before SIMOPS begin
• Integrated permit-to-work — a single permit system that covers both construction and operations activities, with cross-referencing to prevent conflicting work
• Communication protocols — defined channels and escalation procedures that connect construction supervisors, operations shift leads, and safety oversight
• Boundary management — clear physical and procedural boundaries between construction and operations zones, with controlled access points
• Shared safety systems plan — documented agreements on which safety systems are live, which are inhibited, what compensating measures are in place, and who has authority to change the status

---

How Should Turnover Governance Be Structured?

Turnover governance is the framework that controls how systems and facilities are formally transferred from the project team to the operations team. Weak turnover governance is one of the most common root causes of startup delays and incidents.

Turnover Packages

Each system turnover should be supported by a turnover package containing:

• Completion certificates — signed confirmation that construction, testing, and commissioning are complete
• As-built documentation — P&IDs, isometrics, equipment data sheets, and wiring diagrams that reflect the actual installed configuration
• Test records — hydrostatic test reports, loop check sheets, motor run tests, and safety system function test records
• Punch list — categorized list of remaining items with severity classifications and target completion dates
• Equipment files — manufacturer documentation, material certifications, and warranty information
• Operating and maintenance procedures — system-specific procedures required for safe operation

Punch List Management

Punch lists are the primary tool for tracking incomplete items during turnover. Effective punch list management requires:

• Severity classification — Category A (must close before startup), Category B (must close within defined period after startup), Category C (discretionary timing)
• Clear ownership — every item assigned to a responsible party with a target date
• Regular review cadence — daily or weekly reviews during the startup period
• Escalation process — defined path for items that are overdue or disputed
• Audit trail — documentation of closure evidence, not just status updates

System Completion Tracking

Large projects may have hundreds of systems, each moving through construction, pre-commissioning, commissioning, and turnover at different rates. System completion tracking provides visibility into:

• Overall project readiness by system and area
• Critical path systems that are gating startup
• Resource allocation needs for commissioning and turnover activities
• Trending of completion rates to predict startup readiness dates

---

Control Room Readiness

The control room is the operational nerve center during startup. Control room readiness encompasses the people, technology, and procedures that enable safe, effective monitoring and control of the process.

DCS and SIS Testing

Distributed Control System (DCS) and Safety Instrumented System (SIS) testing must be completed and documented before startup:

• Point-to-point verification — every input and output confirmed to connect the correct field device to the correct controller
• Logic testing — control sequences, interlocks, and safety functions tested against design logic
• Cause-and-effect testing — comprehensive testing of the safety system cause-and-effect matrix, verifying that every initiating condition produces the correct protective action
• Alarm review — verification that alarm setpoints are correct, alarm priorities are appropriate, and the total alarm load is manageable

Control System Cybersecurity Verification

Before startup, control system cybersecurity configurations must be verified as part of commissioning:

• Network segmentation confirmed — DCS and SIS networks are isolated from business and external networks per ISA/IEC 62443 zone models
• Default credentials eliminated — all factory default passwords changed on controllers, HMIs, network devices, and engineering workstations
• Remote access secured — vendor remote support connections and VPN access paths reviewed, authorized, and documented
• Firmware validated — controller and device firmware versions checked against ICS-CERT advisories and vendor security bulletins
• Backup and recovery tested — control system configuration backups verified with a successful test restore before process fluids are introduced

A compromised control system during startup — when operators are already managing abnormal conditions and unfamiliar equipment — represents an acute process safety risk that must be addressed during commissioning, not after.

Operator Training Verification

Operators must be trained and competent on the specific DCS and SIS configuration before startup. Training verification should include:

• Simulator exercises — if a simulator is available, operators should complete startup and emergency scenarios
• Tabletop drills — walkthrough exercises for startup procedures, emergency shutdown, and abnormal operations
• Console familiarization — hands-on time at the actual console with the actual displays and controls

Alarm Management

Alarm floods during startup are a leading contributor to operator error and startup incidents. Alarm management readiness includes:

• Rationalized alarm database with justified setpoints and priorities
• Suppression strategy for alarms that are not meaningful during startup conditions
• Monitoring plan for alarm rates during the startup period
• Defined response for alarm conditions that are expected during startup versus those that indicate actual problems

Communication Systems

Startup requires reliable communication between the control room, field operators, commissioning teams, and emergency response:

• Radio systems tested and channels assigned
• Public address and emergency notification systems verified
• Communication protocols for critical startup steps documented
• Backup communication methods identified and tested

---

What Are the Most Common Startup Failures?

Startup is the highest-risk phase of any project. The following failure patterns appear repeatedly across industries and project sizes.

1. Incomplete Punch Lists

Facilities that start up with unresolved Category A punch list items are accepting risk they have explicitly identified but not mitigated. The pressure to meet schedule milestones drives premature startup — the most frequent and most preventable startup failure pattern.

2. Untrained or Undertrained Operators

New facilities with new operators are inherently higher risk. When training consists of classroom hours without practical competency verification, operators face their first abnormal situation without the skills to respond effectively. This risk is amplified when experienced operators are not available to mentor new staff during startup.

3. Inadequate or Untested Procedures

Procedures written by engineers who will not use them, reviewed by managers who will not follow them, and handed to operators who have never practiced them. The gap between the procedure as written and the procedure as needed becomes apparent during the first abnormal condition — which often occurs during startup.

4. Safety System Bypasses

During commissioning, safety systems are frequently bypassed to enable testing. If bypass management is not rigorously controlled, systems may remain bypassed during startup. A single bypassed safety interlock can negate the protection designed into the facility.

5. Communication Breakdowns

During startup, decisions must flow rapidly between the control room, field, engineering, management, and sometimes contractors and licensors. When communication channels are unclear, decisions are delayed, conflicting instructions are given, and critical information does not reach the people who need it.

6. Scope Changes During Startup

Late-breaking design changes, field modifications, and "improvements" introduced during the startup window create risk because they bypass the normal engineering review and MOC process. The urgency of the startup schedule is used to justify shortcuts that would not be accepted during normal operations.

---

How to Assess Your Operational Readiness

Whether you are planning a new facility startup, a major turnaround restart, or a brownfield modification, understanding your readiness level before the startup window begins is critical.

Self-Assessment (FidelisCheck)

Start with a FidelisCheck Operational Readiness & Startup Scan to evaluate your CSU program against industry best practices. The assessment covers commissioning planning, turnover governance, PSSR readiness, SIMOPS management, and control room preparedness.

Start Free Readiness Assessment →

Expert-Led Assessment (FidelisGap)

For complex projects or first-time startups, FidelisGap provides a comprehensive operational readiness evaluation led by experienced startup professionals. The assessment identifies gaps in your CSU program, prioritizes them by risk, and delivers an actionable improvement plan aligned with your startup schedule.

Request Readiness Assessment →

---

Related Resources

• What is a Pre-Startup Safety Review (PSSR)? — Detailed guide to PSSR requirements, process, and common gaps.
• What is Process Safety Management? A Complete Guide — PSSR is one of the 14 PSM elements. Understanding the full PSM framework provides context for CSU safety requirements.
• Operational Readiness & Startup Scan — Free self-assessment to benchmark your CSU program maturity.

---

Frequently Asked Questions

What is the difference between commissioning and startup? Commissioning is the system-by-system verification that installed equipment functions as designed, conducted before process fluids are introduced. Startup is the controlled introduction of process fluids (hydrocarbons, chemicals, feedstocks) into verified systems to achieve initial production. Commissioning is typically led by the project team; startup is typically led by operations. Commissioning involves testing with non-hazardous utilities (air, water, nitrogen); startup involves hazardous process materials under operating conditions.

Is an Operational Readiness Review (ORR) required by regulation? ORR is not explicitly required by OSHA as a named activity. However, OSHA PSM requires Pre-Startup Safety Review (PSSR), which covers many of the same verification items. Many operating companies require ORR as an internal standard that goes beyond the minimum PSSR requirements. ORR is considered industry best practice for any new facility or major modification, and regulatory agencies increasingly expect to see evidence of structured readiness assessments during inspections.

How long should the commissioning and startup phase take? Duration varies significantly based on project complexity, facility size, and team experience. A simple single-unit modification may require weeks; a grassroots petroleum refinery, LNG terminal, or petrochemical plant may require 6-12 months from mechanical completion to stable operations. The most important factor is not speed but thoroughness — facilities that rush through commissioning and startup to meet schedule milestones consistently experience more incidents and longer times to stable operations than those that follow their CSU plans completely.

What is SIMOPS and when does it apply? Simultaneous Operations (SIMOPS) occur when construction, commissioning, and live operations happen concurrently in the same facility. SIMOPS are common during phased startups (where one unit is operating while an adjacent unit is still being commissioned), brownfield projects (new construction within an operating facility), and turnarounds (where some units restart while others are still under maintenance). SIMOPS require specific risk assessments, integrated permit-to-work systems, and defined communication protocols to manage the interactions between concurrent activities safely.

---

Fidelis Associates provides commissioning, startup, and operational readiness consulting through FidelisForce and FidelisGap. Our team has supported startups across refineries, chemical plants, LNG terminals, and hydrogen facilities — from planning and readiness assessment through on-site execution and post-startup support.

Schedule a Discovery Call → | Start Free Readiness Assessment →