Common PSSR Findings often reveal the small gaps that can escalate into serious incidents when systems are first energized or hazardous materials are introduced. Pre-Startup Safety Review (PSSR) is the last independent readiness check before turning the key on a new unit, a brownfield modification, or a restarted facility. In UAE industrial operations—across oil and gas processing, petrochemical complexes, bulk liquid terminals, high-risk construction handovers, manufacturing lines, logistics hubs, and power generation—this checkpoint sits at the intersection of engineering, operations, and compliance. Understanding the patterns that show up repeatedly in PSSRs helps leaders preempt delays, avoid rework, and, most importantly, ensure personnel and asset protection while aligning with frameworks such as ADNOC’s HSE requirements, OSHAD SF, Dubai Municipality codes, Civil Defence approvals, and international standards including ISO 45001, ISO 14001, IEC 61511, API RP 14C/750, and relevant NFPA codes.
What follows is a practitioner-level discussion of recurring issues seen in PSSR, why they matter, and how organizations can anticipate and address them. The intent is educational: to give HSE and operations professionals a structured view of typical pitfalls and practical steps to raise operational readiness before start-up.
Who Does This Affect?

Although a PSSR is often coordinated by HSE or process safety, its scope cuts across the full project-to-operations boundary. The topic concerns:
- HSE managers and process safety engineers responsible for implementing PSM elements aligned with OSHA 1910.119 principles and ADNOC/OSHAD directives.
- Plant managers, commissioning managers, and operations superintendents who own the start-up decision.
- Engineering disciplines—process, mechanical, piping, E&I, control systems, and loss prevention—responsible for technical integrity.
- Maintenance and reliability teams accountable for critical spares, calibration, and mechanical integrity baselines (e.g., API 570/653 regimes).
- Project and EPC teams closing out construction, punch lists, and as-built documentation.
- Regulatory liaisons coordinating Dubai Municipality or Civil Defence inspections and permits to operate.
- Contractor HSSE supervisors and SIMOPS coordinators managing interfacing works in brownfield settings.
This is relevant to refineries, gas processing plants, offshore platforms, petrochemical crackers and polymer units, storage and distribution terminals, aviation fuel facilities, power plants (including HRSG/boiler islands), large manufacturing sites (including ammonia refrigeration and solvent-based processes), and logistics operations with hazardous materials. Wherever energy, pressure, flammables, toxics, or complex electrical/control systems are present, PSSR and the recurring issues it surfaces are central to safe, compliant start-up.
Why This Matters

PSSR exists to verify that what was designed, procured, constructed, and configured is safe to start and aligned with the intended operating envelope. It provides assurance that safeguards identified in HAZOP, HAZID, LOPA, Bowtie analysis, and SIL determination (IEC 61511) were actually implemented as specified, and that human and organizational factors (procedures, training, competence, and emergency readiness) are in place. In the UAE context, it also demonstrates that statutory and regulatory requirements—such as OSHAD SF codes of practice, ADNOC corporate standards, and unit-specific Civil Defence approvals—have been met before introducing hazards.
When Common PSSR Findings are not anticipated and closed, the consequences often include start-up delays, temporary workarounds that incrementally raise risk, unplanned trips, permit non-compliance, or, in the worst case, a significant incident early in the operating life. A PSSR is not a “paper exercise”; it is the final barrier that tests the fidelity of management of change (MOC), documentation control, asset certification, and operational preparedness. Getting familiar with typical findings gives organizations a head start on eliminating them proactively, compressing schedules without compromising safety.
Key Points to Understand

To interpret typical findings constructively, it helps to view PSSR as a verification across six readiness dimensions: technical integrity, controls and safeguards, procedures and people, emergency response, documentation, and regulatory/permit status. Each dimension tends to generate its own recurring issues; anticipating them accelerates closure and strengthens assurance.
1) Technical Integrity and Mechanical Completion

Mechanical completion does not guarantee operational readiness. Frequent observations include incomplete pressure relief documentation (datasheets, set pressures, relief scenarios not reconciled with current design), missing or incorrectly installed gaskets at critical flanges, incomplete earthing/bonding continuity checks in hazardous areas, unverified bolt torqueing, and small-bore piping supports not aligned with vibration risks. For rotating equipment, lubrication system readiness, coupling guards, and direction-of-rotation marks are often overlooked in final checks. In tank farms and terminals, inadequate overfill alarm proof checks and untested independent high-high level trips show up regularly.
2) Controls, Instrumentation, and Functional Safety

Safeguards identified in HAZOP/LOPA must be visible in the field and in logic. Recurrent issues include discrepancies between cause-and-effect matrices and implemented DCS/ESD logic, missing alarm rationalization alignments (priority, setpoints, shelving rules), undocumented temporary bypasses, and incomplete SIL verification evidence versus the Safety Requirements Specification (SRS). Loop diagrams, calibration certificates, and signoffs are frequently incomplete. In hazardous area classification contexts, equipment certification (IECEx/ATEX) mismatches are another common thread.
3) Procedures, Competence, and Permit-to-Work

On the human-performance side, incomplete or generic start-up procedures, missing abnormal/emergency operating procedures, or inadequate job step hazard analyses are routine findings. Operations personnel may not yet be signed off as competent for the new system, or training records do not cover updated interlocks and alarm responses. Permit-to-work (PTW) alignment with start-up activities—especially where SIMOPS continue—is another recurrent theme, as are missing lockout/tagout (LOTO) verification records.
4) Emergency Response and Fire Protection

Deluge and foam systems not function-tested against design demand, firewater ring main hydraulics not revalidated after tie-ins, and gaps in emergency lighting or egress signage are noted often. Onshore and offshore facilities alike may show missing muster point signage after plot plan changes, untested gas detection mapping coverage, and insufficient communication checks for emergency channels. NFPA-driven design intent versus commissioning test evidence is a frequent mismatch.
5) Documentation Control and As-Builts

PSSR relies on as-built drawings that reflect what is truly installed. Recurrent problems include unincorporated redlines on P&IDs, outdated line lists, missing updated hazardous area drawings, and vendor data not imported to the document management system or CMMS. Without accurate P&IDs and cause-and-effect diagrams, operators cannot trust procedures or isolation plans.
6) Regulatory and Third-Party Requirements
From Civil Defence acceptance of fire/life safety systems to municipality approvals and, in Abu Dhabi, OSHAD SF-aligned documentation sets, the permitting picture must be complete. PSSR often surfaces late-stage administrative gaps—e.g., missing third-party inspection certificates, incomplete lifting equipment certification, or scaffold signoffs in areas that will remain active during start-up.
| Finding Category | Recurring Examples | Typical Risk If Unaddressed | Quick Diagnostic Question |
|---|---|---|---|
| Technical Integrity | Relief valve data not reconciled; incomplete earthing; unverified torque | Overpressure, ignition potential, leaks/fires | Can we trace each relief device to a current scenario and datasheet? |
| Controls & Safeguards | C&E mismatches; undocumented bypasses; SIL proof data missing | Safeguard failure on demand; false sense of protection | Do C&E, DCS logic, and field tags match one-to-one? |
| Procedures & Competence | Generic start-up steps; training not covering new alarms/interlocks | Operator error; slow or wrong response to trips | Have console and field operators been assessed on revised scenarios? |
| Emergency Preparedness | Unverified deluge flow; gas detection not function-tested | Delayed mitigation; ineffective response | Is there test evidence for each fire/gas safeguard tied to HAZOP? |
| Documentation | P&IDs not as-built; outdated line lists; missing loop sheets | Wrong isolations; incorrect procedures | Are operator procedures and isolations based on current P&IDs? |
| Regulatory/Permits | Incomplete Civil Defence closeout; third-party certs pending | Legal non-compliance; start-up delays | Are all statutory approvals in hand for the scope starting up? |
As practitioners, NPM emphasizes that PSSR is not a repeat of commissioning. Commissioning proves the system works; PSSR verifies the system is safe to work. The review triangulates design intent, field reality, and human readiness to ensure the guardrails are unambiguously in place. For additional perspectives on governance, technical notes, and industry commentary that complement this kind of operational readiness thinking, see curated materials available via CABINET NPM.
How This Plays Out in Practice
Turning principles into field reality requires discipline. Typically, the lead-up to PSSR begins once systems are mechanically complete and pre-commissioning is substantially finished. Construction punch lists should be reduced to items that do not affect safety or operability, and the commissioning team should have completed appropriate flushing, pressure testing, energization checks, and loop checks. At this point, the PSSR team—drawing from operations, HSE, engineering, maintenance, and sometimes a corporate process safety representative—walks down the scope, verifies documentation, samples safeguards, and challenges go/no-go assumptions.
In a refinery hydrotreater revamp, for example, a PSSR might compare the LOPA credit taken for a high-pressure trip with the actual implemented ESD logic and proof-test interval. If the updated compressor trip was credited as an independent protection layer (IPL) with 10-year PFD assumptions in the risk model, but the commissioning evidence shows a different sensor architecture or no formal proof-test procedure in the CMMS, the PSSR will flag a discrepancy. Similarly, in a storage terminal expansion, the PSSR may identify that the independent high-high level switch wiring is landed on the same marshaling panel and power supply as the primary transmitter, undermining independence claimed in the design.
Real-world application is also about interfaces. In brownfield tie-ins with live units, SIMOPS coordination is critical: isolation plans must be both technically correct and practically enforceable under the site’s PTW system. The PSSR often checks that blinds and spades are installed per drawing, tag numbers match, and boundary valves are locked and signed off. Where temporary bypasses are in place for commissioning, the PSSR confirms there is a documented plan, risk assessment, and authority to remove them logically and physically before introducing hazardous materials.
Another practical thread is documentation readiness. P&IDs must be signed “as-built” by the responsible engineer; cause-and-effect diagrams, alarm rationalization lists, and operating procedures must reflect the final configuration. If HAZOP actions are still open, the PSSR should see evidence that any risk-relevant actions have been resolved or that compensating measures and sign-off authority are documented. In the UAE, this record forms part of the evidence path that supports oversight by owners, corporate functions, and regulators such as OSHAD and ADNOC group companies.
Benefits and Practical Use Cases
When organizations internalize the typical issues surfaced by PSSR, they can design readiness into their workflows, rather than react at the last minute. Tangible benefits include:
- Reduced start-up delays by addressing common gaps upstream in design reviews, commissioning plans, and documentation control.
- Lower operational risk by ensuring that safeguards identified in HAZOP/LOPA and required by IEC 61511 are validated and documented.
- Fewer unplanned trips and nuisance alarms through better alarm rationalization, integrity of interlocks, and training on abnormal scenarios.
- Smoother regulatory engagements by demonstrating a robust, auditable path to readiness aligned with OSHAD SF, Civil Defence, and municipality expectations.
- Improved insurance defensibility and stakeholder confidence through traceable decision-making and closure evidence on safety-critical elements.
Concrete use cases where recurring PSSR issues can be proactively mitigated include:
- Brownfield compressor upgrades in gas processing plants, where surge control, trip logic, and isolation planning require tight integration.
- Tank farm expansions and jet fuel hydrant systems at logistics hubs, focusing on overfill protection, bonding/earthing, and firefighting systems.
- Offshore wellhead platform modifications, where SIMOPS and hazardous area compliance are particularly sensitive.
- Power plant boiler and HRSG changes affecting burner management system interlocks and fuel gas safety shutoff valves.
- Manufacturing sites introducing solvent-based lines or ammonia refrigeration, where leak detection, ventilation, and emergency response elements must be verified.
- Pipelines and metering skids, where pressure control, relief, and pigging safety require end-to-end checks.
Across these scenarios, the organizations that most effectively avoid recurring findings apply the PSSR mindset months before the formal review—embedding acceptance criteria into specifications, aligning commissioning test evidence to hazard studies, and maintaining documentation quality as a core deliverable rather than an afterthought.
Best Practices and Points of Caution
Drawing on field experience across diverse facilities, the following practices consistently reduce the volume and severity of PSSR findings:
- Start with the hazard studies: Build a “safeguards verification plan” directly from HAZOP/LOPA and SIL results, mapping each IPL and SIF to a test or piece of evidence that will be produced and independently checked.
- Define acceptance criteria early: Agree on what “ready” means for each system—e.g., relief devices reconciled to current design, cause-and-effect tested end-to-end, alarm priorities rationalized and documented, deluge coverage proven.
- Keep P&IDs as the single source of truth: Lock document control so that field changes can only proceed with immediate redline capture and expedited as-built issuance before PSSR.
- Harden independence: For IPLs and SIFs, verify physical and functional independence, not just logical intent—distinct sensors, power supplies, and voting arrangements per IEC 61511 where required.
- Manage bypasses and inhibits: Maintain a register with owner, reason, risk assessment, expiry, and removal plan; assure all temporary measures are cleared pre-start-up.
- Close competency loops: Train console and field operators on the final alarm list, trip responses, and start-up/abnormal procedures; document sign-offs based on observed demonstrations.
- Stress-test emergency readiness: Function-test firewater, foam, and gas detection; confirm muster procedures and communications; rehearse a realistic start-up upset scenario with the shift team.
- Risk-rank and gate decisions: Classify findings (e.g., A/B/C) with clear go/no-go rules; document any risk acceptance with authority and compensating measures, and time-bound them.
- Align PTW and SIMOPS: Ensure the permit system and isolations match the as-built drawings; avoid procedural gaps when live units neighbor the start-up scope.
- Anchor critical spares: Verify that maintenance has the spares and CMMS tasks to sustain safety functions—proof-test intervals, relief valve recertification, detector bump/calibration frequencies.
Common pitfalls include treating PSSR as a duplicate of commissioning, accepting “temporary” documentation promises without dates or owners, and assuming that if equipment is energized it must be safe to start. A disciplined, evidence-led PSSR avoids these traps and provides a clear record of due diligence.
Frequently Asked Questions About Common PSSR Findings
What are the most frequent finding themes during PSSR?
Recurring themes cluster around documentation that does not match the installed reality (outdated P&IDs and cause-and-effect), incomplete verification of safety functions and alarms, open HAZOP actions with risk relevance, gaps in emergency systems testing (deluge, foam, gas detection), and missing training or competence sign-offs for the operators who will run the system. Earthing, bonding, and hazardous area equipment certifications are also common in hydrocarbon facilities.
How should we risk-rank findings at PSSR?
Use a simple A/B/C or High/Medium/Low framework keyed to consequence and likelihood during start-up, with explicit go/no-go rules. “A” findings prevent start-up until closed; “B” may proceed with compensating measures if authorized; “C” can be post-start-up items that do not impact safety or compliance. Document the rationale, authority, and any temporary risk controls, and time-bound all follow-ups.
What documentation gaps most often delay start-up?
As-built P&IDs not issued, cause-and-effect matrices not aligned to final logic, incomplete relief system documentation, and missing calibration/loop checks for safety-relevant instruments are top culprits. In many jurisdictions, incomplete Civil Defence closeout or missing third-party certifications can delay start authorization even if the plant is otherwise mechanically ready.
How is PSSR different from commissioning?
Commissioning proves function; PSSR verifies safety to function. Commissioning asks “does it run?” while PSSR asks “is it safe and compliant to run?” PSSR triangulates hazard study intent, implemented safeguards, competent people, emergency readiness, and complete documentation/permits. It is the last independent check before introducing energy and hazards in steady-state operations.
How do SIL and LOPA considerations appear in PSSR findings?
PSSR often verifies that safety instrumented functions (SIFs) meet the Safety Requirements Specification: correct sensors/final elements, voting logic, proof-test procedures in the CMMS, bypass rules, and trip setpoints. LOPA credits for IPLs are checked against the real-world implementation to ensure independence, availability, and testing frequency are consistent with the risk model.
What do UAE regulators typically expect to see?
Expectations vary by emirate and authority, but generally include alignment with OSHAD SF in Abu Dhabi, compliance with ADNOC corporate standards in relevant group companies, and Civil Defence acceptance of fire and life safety systems. Authorities often expect traceable documentation: as-built drawings, test records for fire/gas systems, third-party certifications, and clear evidence that operators are trained and emergency procedures are in place.
Can we start up with open findings?
Yes, but only with a robust, documented risk decision. Safety-critical “A” items should be closed before start. For lesser items, define compensating measures, ownership, timelines, and monitoring; record formal authorization at the appropriate level. Avoid normalizing deviation: temporary measures should have clear expiry and follow-up audits.
What kinds of evidence best support finding closure?
Evidence should match the nature of the safeguard: signed as-built P&IDs, loop check and calibration records, cause-and-effect test sheets, photos of installed blinds or labels, firewater flow/pressure test reports, gas detector bump test logs, training attendance with competence assessments, and permit sign-offs. Tie each piece of evidence back to the specific risk control or action item.
Conclusion
Across sectors and facility types, the patterns are consistent: the most common PSSR issues sit where engineering reality meets human performance and documentation control. By organizing readiness around safeguards verification, accurate as-builts, competency, emergency preparedness, and permits, organizations can dramatically cut the noise during start-up and focus on safe, stable operations. NPM’s field experience confirms that when teams anticipate recurring findings—such as cause-and-effect mismatches, incomplete relief documentation, alarm management gaps, and emergency system test evidence—start-ups are not only safer, they are faster and more predictable. Treat PSSR as the last independent assurance gate that must reconcile hazard study intent with plant reality and you will avoid the classic pitfalls described throughout this article.
To go further on this topic, NPM’s broader Pre Startup Safety Review Services UAE page covers this in more depth.
Explore NPM’s References
NPM’s references highlight how operational readiness and PSSR principles translate into real-world improvements across complex, high-hazard industries. Our portfolio spans refinery debottlenecking, gas compression upgrades, downstream terminal expansions, offshore brownfield modifications, power generation changes affecting burner management systems, and manufacturing line introductions involving hazardous substances. In each case, the readiness story is visible not just in technical milestones, but in the quality of safeguards verification, documentation accuracy, and competency demonstrated by operating teams at the moment of start-up. We emphasize measurable outcomes: fewer start-up trips, tighter alarm performance, fully reconciled relief systems, and strong evidence trails that align with corporate and regulatory expectations. Because NPM works worldwide, our reference set captures lessons from multiple regulatory environments and operating cultures, enriching the perspective we bring to UAE facilities without diluting the local context. Readers exploring our references will see recurring themes from this article—closing HAZOP actions that truly matter, validating safety instrumented functions against IEC 61511, aligning cause-and-effect with implemented logic, and rehearsing emergency response keyed to realistic upset scenarios. The value lies in how these elements combine into a coherent readiness narrative that plant leadership and regulators alike can trust.
For more information about our references, visit Our References.
Speak With NPM
If you are evaluating start-up readiness or want to stress-test how typical PSSR findings might apply to your facility, our team is available to discuss practical approaches and share perspectives. We are glad to answer questions, compare notes with your engineering and operations leads, or review how to embed robust acceptance criteria ahead of your next start. For any further questions or to speak with our team, Contact Us.