What Is Pre Startup Safety Review?

Design Hazard Review for New Processing Facility

“What Is Pre Startup Safety Review?” is a question that comes up often when HSE and operations leaders in high-hazard industries are preparing to introduce hydrocarbons, energize systems, or restart after a major modification. In simple terms, a pre-startup safety review (PSSR) is the final, structured verification that all risk controls, procedures, people, and plant conditions are in place and functional before an initial startup or re-introduction of hazardous energy. It closes the loop between design-stage risk analysis (like HAZOP/LOPA) and real-world operating readiness, ensuring that what was intended on paper is demonstrably true in the field.

For industrial operators across the UAE—spanning oil and gas production, petrochemical complexes, power and desalination, bulk liquid storage, and complex manufacturing—this review is more than a good practice. It is a key element of process safety management aligned with recognized standards and regulator expectations, including ADNOC Codes of Practice, Abu Dhabi OSHAD SF (OSHAD-SF), Dubai Municipality EHS guidelines, UAE Civil Defence fire safety approvals, and global frameworks such as OSHA PSM (29 CFR 1910.119), IEC 61511 for safety instrumented systems (SIS), API Recommended Practices (e.g., RP 14C offshore; RP 750 for process hazards management), ISO 45001, ISO 14001, and relevant NFPA codes.

The following article explains who is concerned, why this subject matters, what a robust PSSR covers, and how it plays out in practice—especially in facilities handling flammables, toxics, high pressures, or complex energy systems. The objective is practical clarity: understanding what must be true and provable before a safe startup.

Who Does This Affect?

What Is Pre Startup Safety Review?

The need for a robust PSSR spans many roles and functions because the review integrates engineering integrity, procedural readiness, competency, and emergency preparedness. It directly concerns:

  • HSE Managers, Process Safety Leads, and OSHAD/PSM coordinators who steward the management system and regulatory interfaces.
  • Plant Managers, Operations Superintendents, and Commissioning Managers accountable for safe introduction of feedstock, utilities, and energy.
  • Maintenance and Reliability Leaders responsible for mechanical integrity (MI) baselines, relief devices, rotating equipment condition, and proof-testing.
  • Engineering, Projects, and EPC contractor teams handling detailed design, as-built deliverables, management of change (MOC), and punch-list closeout.
  • Control and Automation teams validating interlocks, ESD logic, cause-and-effect matrices, alarm management, and SIS functionality per IEC 61511.
  • Emergency Response and Security teams ensuring drills, access/egress, muster points, and coordination with Civil Defence are in place.

Facility types particularly affected include refineries, gas processing plants, pipelines and compressor stations, offshore platforms and FPSOs, petrochemical crackers and polymer units, storage terminals and truck loading racks, power generation units (including CCGT and desalination tie-ins), as well as manufacturing lines using hazardous chemicals, solvents, or combustible dusts. In the UAE context, PSSR also intersects with approvals and notifications to local authorities—such as Civil Defence for fire life safety, and in some cases MOHRE for worker safety aspects—especially when a startup changes workforce exposure or emergency arrangements.

Why Does This Question Matter?

What Is Pre Startup Safety Review?

Understanding PSSR matters because the highest-risk moment in a plant’s lifecycle is often the transition from construction or modification to live operation. This is when latent design deviations, undocumented field changes, incomplete procedures, or untested interlocks can converge into loss-of-containment, fires, explosions, or toxic releases. Major industrial incidents have repeatedly shown that robust pre-startup controls would have prevented escalation—by catching open drain valves, mis-ranged transmitters, reversed relief valve orientation, disabled trips, or non-calibrated gas detectors before they mattered.

Beyond incident prevention, a reliable PSSR provides:

  • Regulatory compliance alignment: With ADNOC HSE requirements, OSHAD SF, Dubai Municipality EHS rules, and best-practice standards like OSHA PSM’s “Pre-Start-up Safety Review” element and API/CCPS guidance.
  • Barrier integrity assurance: Confirmation that engineered safeguards, procedural controls, and human factors are integrated and functional as intended.
  • Operational efficiency: Smoother ramp-up and fewer unplanned shutdowns by ensuring procedures, spares, and commissioning handover are complete.
  • Governance evidence: Documented due diligence—meeting audit expectations and strengthening an organization’s license to operate.

Crucially, this is not a paperwork exercise. It is a disciplined, field-verified, multi-functional review that validates the plant’s readiness at the moment it matters most.

Key Points to Understand

What Is Pre Startup Safety Review?

With the stakes established, it helps to break down the core dimensions of a strong PSSR framework. While organizational specifics differ, the following pillars are widely recognized across process industries:

1) Scope and Triggers

What Is Pre Startup Safety Review?

PSSR applies before initial startup of a new unit and before re-start after a “major modification.” A modification is typically “major” if it changes the process chemistry, operating envelope, relief and blowdown design, controls or interlocks, equipment duty, or the nature/quantity of hazardous inventory. Minor like-for-like maintenance is generally not a trigger, but cumulative small changes may warrant a review. Integrate PSSR criteria with MOC and project stage-gates so triggers are explicit and consistent.

2) Distinction from Other Activities

What Is Pre Startup Safety Review?

PSSR is not the same as mechanical completion or pre-commissioning. Mechanical completion shows that construction matches drawings and equipment is installed; pre-commissioning checks that systems function at a basic level (e.g., hydrotesting, loop checks). PSSR goes further by demonstrating that risk controls and operating conditions are holistically ready for safe operation—procedures, training, emergency response, permits, and regulatory approvals included. It is also distinct from HAZOP/LOPA, which are design risk assessments; PSSR confirms those risk-reduction actions are implemented in the field.

3) Content of a PSSR

What Is Pre Startup Safety Review?

Although forms vary, typical PSSR content covers:

  • Design and risk basis alignment: HAZOP/HAZID actions closed, LOPA targets met, and deviations documented via MOC.
  • As-built integrity: Updated P&IDs, isometrics, cause-and-effect matrices, and electrical single-lines reflect reality; punch-list A items closed.
  • Protection systems: Relief devices sized/installed correctly; SIS logic, trips, and interlocks tested per IEC 61511; fire and gas systems calibrated and functionally tested; ESD and blowdown verified.
  • Procedures and training: Operating, start-up, shutdown, and emergency procedures current; operators trained and, if relevant, competency demonstrated.
  • Permit-to-work and isolation practices: Lockout/tagout, energy isolation plans, and override management ready and effective.
  • Emergency preparedness: Alarm setpoints validated; muster and evacuation arrangements confirmed; drills performed; Civil Defence coordination established as required.
  • Environmental controls: Emissions, effluent, and waste controls aligned with permits and ISO 14001 practices.
  • Regulatory approvals: Where applicable, NOCs or certificates secured (e.g., Civil Defence for fire systems) and documentation available.

4) Team Composition and Independence

What Is Pre Startup Safety Review?

Include operations, maintenance, process engineering, instrumentation/control, HSE/process safety, and (as needed) vendor/EPC representation. Independence matters: involve at least one member who was not directly responsible for the design or construction of the system being reviewed, to provide an objective challenge.

5) Evidence and Traceability

What Is Pre Startup Safety Review?

Given auditability requirements under frameworks like OSHA PSM, OSHAD SF, and ADNOC HSE expectations, evidence should be specific, dated, and traceable to individuals. That typically means attachment of test records, check sheets, redlines, competency sign-offs, and photographs. Document control and governance tools can help maintain version integrity across P&IDs, cause-and-effect matrices, and procedures.

For organizations maturing their governance, document control, and evidence management—especially across multi-site portfolios—resources such as CABINET NPM can support structured, auditable information management that aligns engineering deliverables with safety gate decisions.

6) Acceptance Criteria and Go/No-Go

Define what must be true before “Go.” Typically, all high-severity risks (e.g., punch-list category A) are closed; overrides are minimized, time-bound, and risk-assessed; emergency systems meet performance criteria; operating envelopes are defined; and procedures/competency are confirmed. If conditions are not met, authority to delay startup must be clear—and exercised.

Illustrative PSSR Checklist Map

The table below maps common PSSR topics to practical field checks and helpful references frequently applied in UAE operations.

PSSR Topic Practical Field/Evidence Checks Reference/Standard Context
Design Basis & Risk Actions HAZOP/LOPA actions closed; deviations approved via MOC; operating limits documented CCPS guidance; ADNOC CoP; OSHA PSM; API RP 750
As-Built Documentation Latest P&IDs redlined and signed; cause-and-effect matrices updated; loop drawings current Project QA/QC; internal document control governance
Relief & Blowdown PSVs installed per sizing; relief routes clear; flare systems commissioned; vent/PSV tags verified API 520/521; ADNOC/OSHAD expectations; NFPA guidance
SIS & Interlocks Proof-test results available; trip setpoints verified; bypasses logged and risk assessed IEC 61511; corporate SIS standards
Fire & Gas Detector placement validated; calibration certificates; ESD/F&G cause-and-effect tested UAE Civil Defence codes; NFPA 72/70; ADNOC requirements
Procedures Start-up, shutdown, emergency procedures controlled and accessible; sign-offs of operator training OSHA PSM; ISO 45001; corporate OMS
Permit to Work & Isolation PTW forms active; LOTO plans verified; overrides controlled with expiry OSHAD SF; ADNOC PTW standards
Emergency Preparedness Muster signage; drills logged; radios and PA tested; access/egress clear UAE Civil Defence; ISO 45001
Environmental Controls Effluent sampling in place; bunding integrity; emissions abatement operable ISO 14001; local environmental permits
Regulatory Approvals NOCs/certificates filed; inspection punch list closed; statutory testing records retained Dubai Municipality; Civil Defence; free zone authorities

How Does This Work in Practice?

Building on the framework above, the real-world application of PSSR hinges on integrating the review into the project lifecycle and operational routines without creating bottlenecks. A practical path looks like this:

First, embed PSSR triggers in the MOC process and project execution plan. Define upfront which changes require PSSR and how it aligns with mechanical completion, pre-commissioning, and commissioning stage gates (e.g., MC, pre-commissioning complete, hot commissioning readiness, hydrocarbon introduction). Clear definitions prevent last-minute debates when schedules are tight.

Second, prepare early. As HAZOP/LOPA action items are closed and vendor packages arrive, begin assembling PSSR evidence: updated P&IDs, test certificates, SIS proof-test records, relief valve tags, and procedure updates. Early assembly reduces end-of-project scramble and makes omissions visible while time remains to act.

Third, walk the plant. The PSSR should include a disciplined field verification—checking that what is in the file is true in the field. This includes tag verification, line-up, blinds and spades, valve orientation, instrument ranges, alarms, and actual signage. Many operators use punch-list A/B/C categories; a Go decision typically requires category A items (those affecting immediate safety) to be cleared.

Fourth, validate human and procedural readiness. Conduct a pre-start tabletop or drill of the startup sequence, including abnormal situations and emergency response. Confirm that operations and maintenance teams know the override policy, understand alarm priorities, and can explain when and how to stop the startup if conditions drift outside safe limits.

Fifth, confirm regulatory interfaces. In UAE contexts, ensure Civil Defence inspections are passed where fire life safety has changed; where relevant, coordinate with free zone EHS authorities or Dubai Municipality on any altered risk profile. For ADNOC assets, confirm that overrides and impairments are managed per corporate policy and that any additional assurance reviews (e.g., Technical Integrity verification) are complete.

Finally, formalize the Go/No-Go. The decision should be made by designated accountable leaders, with the PSSR record capturing conditions, exceptions, and expiry of any temporary measures. If a No-Go is chosen, document the reasons and required actions—this “paper trail” is vital for governance and future audits.

Benefits and Practical Use Cases

When applied thoughtfully, PSSR delivers tangible safety and operational returns that extend far beyond the startup moment. Among the most practical benefits are:

  • Incident prevention at the riskiest transition point: catching configuration errors, incomplete interlocks, or missing procedures before hazardous energy is introduced.
  • Higher startup reliability: avoiding nuisance trips and early unplanned shutdowns by validating alarms, setpoints, and safeguards.
  • Reduced rework and schedule pain: discovering issues early, rather than during a critical path startup window with contractors demobilizing.
  • Audit-ready documentation: providing clear evidence for OSHAD, ADNOC, and corporate audits, as well as for insurers and external stakeholders.
  • Stronger organizational learning: using PSSR outcomes to improve design standards, vendor specifications, and competency programs.

Common, concrete use cases include:

  • A refinery introducing a revamped hydrotreater, where new hydrogen service elevates explosion risk and SIS integrity per IEC 61511 is critical.
  • A gas compressor station upgrade with new antisurge control—PSSR validates setpoints, cause-and-effect, lube oil interlocks, and relief routing.
  • A petrochemical plant adding a truck loading skid for flammable liquids—PSSR checks grounding/bonding, overfill protection, emergency shut-downs, and firefighting coverage per Civil Defence expectations.
  • A power plant executing an HRSG modification—PSSR ensures water chemistry, blowdown control, and electrical protections (NFPA 70) are aligned before synchronization.
  • An offshore production platform after brownfield tie-ins—PSSR confirms SIMOPS constraints, ESD segment integrity, and muster arrangements under revised layouts.

Best Practices and Points of Caution

Effective PSSR is as much about disciplined habits as it is about forms. Consider these best practices—and the cautions that pair with them:

Prioritize Risk-Based Scope

Not all changes need the same depth. Tie the review depth to the hazard profile and potential for major accident events. Risk-based scoping keeps focus where it matters and avoids checklist fatigue. The caution: if scope is downsized, document the rationale and retain a clear record for auditors.

Integrate with MOC and Project Controls

Link PSSR gates to MOC approvals, HAZOP action tracking, and construction punch-listing. The more these systems “talk,” the fewer surprises at the end. The caution: do not allow late, undocumented field changes to bypass MOC and therefore dodge PSSR.

Insist on Field Truth

Make the plant walkdown a non-negotiable element. Photos, tag verifications, and witness testing trump assumptions. The caution: avoid “desk PSSR” approaches that over-rely on paperwork.

Protect Independence and Authority

Include at least one independent reviewer and empower them to call a halt if acceptance criteria are not met. The caution: schedule pressure must not override safety; make leadership expectations explicit.

Control Overrides and Impairments

Where temporary bypasses are truly necessary, record them, set expiry dates, and add compensating measures. The caution: unmanaged overrides are a frequent precursor to incidents, especially when handover between shifts is weak.

Verify Relief and Venting Thoroughly

Relief devices and vent systems are a last line of defense. Confirm set pressures, service, orientation, and discharge segregation; ensure no deadlegs or inadvertent blockages exist. The caution: changes in process conditions or fluids may invalidate old sizing assumptions—review calculations where triggers exist.

Close the Loop with Learning

Use PSSR findings to refine corporate engineering standards, vendor quality expectations, and training curricula. The caution: without feedback into standards and training, the same issues will recur in the next project.

Frequently Asked Questions About Pre-Startup Safety Reviews

When is a PSSR required?

A PSSR is required before initial startup of a new or significantly modified system that changes the hazard profile—chemistry, inventory, pressure/temperature limits, safeguarding systems, or relief/blowdown design. Many organizations codify triggers in their MOC procedure to remove ambiguity.

How does a PSSR differ from pre-commissioning?

Pre-commissioning demonstrates that equipment and systems function at a basic level (e.g., hydrotests, loop checks). PSSR verifies that the entire risk control framework—procedures, people, protections, and permits—is ready for safe operation. It is the last gate before hazardous energy or process fluids are introduced.

Who should be on the PSSR team?

Include operations, maintenance, process engineering, instrumentation/control, and HSE/process safety specialists, plus vendor/EPC participation when appropriate. At least one member should be independent of the project to ensure objective challenge.

Is PSSR mandatory under UAE regulations?

While specific mandates vary by asset owner and emirate, PSSR aligns with expectations under ADNOC HSE requirements, OSHAD SF, Dubai Municipality EHS guidelines, and international best practices like OSHA PSM. Many organizations treat it as a mandatory internal standard to satisfy regulators, insurers, and corporate governance.

Does PSSR apply to utilities and non-process systems?

Yes, where those systems materially affect process safety. Instrument air reliability, power distribution protection, cooling water capacity, and flare knock-out performance can all influence risk. Risk-based scoping helps determine the correct depth of review for utilities.

How is PSSR documented?

Typically via a controlled checklist or form referencing evidence: as-built drawings, test certificates, photos, training records, and approvals. The sign-off records who verified each item and the Go/No-Go decision, including any temporary measures with expiry conditions.

How does PSSR relate to IEC 61511 and SIL requirements?

IEC 61511 governs the lifecycle of safety instrumented systems. PSSR should verify that SIS elements are installed, configured, and tested per the SRS (Safety Requirements Specification), and that proof-test results and bypass controls are in place before startup.

Can a PSSR be done remotely?

Some document reviews can be remote, but the field component is essential. Physical verification—tags, orientation, signage, access/egress, and witness tests—cannot be reliably substituted by remote means.

What common issues does PSSR catch?

Frequent findings include incomplete or outdated procedures, unclosed punch-list A items, missing or mis-ranged instruments, incorrect relief valve installation, disabled or unmanaged overrides, and gaps in emergency response readiness.

Conclusion and Next Steps

PSSR is the disciplined moment where organizations confirm that design intent, risk controls, and operational readiness truly converge. As discussed above, it is triggered by new startups or significant modifications, depends on cross-functional collaboration and independence, and hinges on verifiable evidence—from SIS proof-tests under IEC 61511 to Civil Defence approvals and updated P&IDs. When integrated with MOC and project controls, it reduces incident risk, boosts startup reliability, and strengthens governance. For HSE, operations, and engineering leaders, mastering PSSR is central to safe, efficient commissioning and sustained process safety performance.

To go further on this topic, NPM’s broader Pre Startup Safety Review Services UAE page covers this in more depth.

Our References

NPM’s work in process safety and operational risk assurance spans diverse geographies, asset types, and regulatory environments, giving our teams a practical vantage point on what makes pre-startup verification succeed under real project pressures. Across refineries, gas plants, offshore platforms, storage terminals, and complex manufacturing sites, NPM has supported readiness reviews interwoven with HAZOP/LOPA closeout, IEC 61511 lifecycle implementation, relief and blowdown verification, and the orchestration of commissioning handovers where multiple EPCs and OEMs intersect. Just as importantly, our references reflect close coordination with authorities having jurisdiction—such as fire safety authorities and environmental regulators—so that compliance evidence and field reality remain aligned. By exploring NPM’s reference portfolio, readers can see how good practices discussed in this article—like independent challenge, risk-based scoping, rigorous field verification, and disciplined override control—translate into measurable outcomes: safer startups, fewer early-life trips, and audit-ready documentation trails. These case highlights also illustrate how lessons learned are fed back into corporate standards, competency programs, and project governance frameworks, enabling continuous improvement beyond a single project. Whether the context is a greenfield unit approaching first hydrocarbons or a brownfield tie-in affecting relief paths and interlocks, the through line in NPM’s references is a commitment to traceable, defensible decisions at the point where safety, production, and schedule converge.

For more information about our references, visit Our References.

Speak with NPM

If you are refining your internal readiness criteria or preparing for a complex startup, our team is available to discuss practical approaches, benchmarking, and lessons learned. We are glad to explore how these principles apply to your facility, whether for a new unit or a significant modification. For any further questions or to speak with our team, Contact Us.