PSSR Team Roles And Responsibilities are a frequent point of discussion for HSE managers, plant leaders, and project teams who want startup and commissioning to be safe, compliant, and free of last‑minute surprises. A pre-startup safety review (PSSR) exists to verify that risk controls identified during design and hazard studies are truly in place and functioning before introducing energy or hazardous materials. In high-risk UAE industries—refining, petrochemicals, gas processing, power generation, construction and large MEP systems, logistics terminals—clarity about who does what in a PSSR is often the difference between a smooth handover and a costly delay or near miss. This article unpacks the PSSR team’s structure, individual accountabilities, and the practical ways roles coordinate to achieve safe, timely start-up while aligning with recognized practices like OSHA PSM, IEC 61511 (SIS), API RP 14C/750, NFPA codes, and UAE frameworks including OSHAD, Dubai Municipality requirements, Civil Defence approvals, MOHRE worker safety obligations, and ADNOC HSE expectations.
Who Does This Affect?

While the PSSR is commonly associated with process plants, the team’s roles and responsibilities span a wide set of environments where energy is introduced for the first time or after significant modification. Across the UAE, that includes onshore and offshore oil and gas assets, petrochemical complexes, bulk storage and loading terminals, district cooling plants, power generation and desalination facilities, large construction handovers (especially MEP-heavy systems), and high-hazard manufacturing lines. In every case, the PSSR team blends operations, engineering, HSE, and project personnel with the authority and competence to make start-up decisions.
Typical stakeholders include:
- Operations leadership and shift supervisors who will own the asset post-handover
- Process, mechanical, electrical, and instrumentation/control engineers who understand design intent
- Commissioning and completions leads responsible for functional checks and energization plans
- HSE advisors who ensure alignment with ISO 45001, ISO 14001, OSHAD, ADNOC HSE rules, and site standards
- Maintenance and reliability representatives who validate maintainability and spares readiness
- Project management and construction managers for close-out of punch items and redlines
- Contractor and vendor representatives for packages and proprietary systems
- Document controllers who verify as-built drawings, P&IDs, and O&M manuals are controlled and accessible
- Independent verifiers or discipline specialists for high-criticality systems (e.g., SIS, relief systems)
Because each facility and project context differs, the PSSR team’s composition adjusts to the scope and risk profile—yet the need for clear, non-overlapping responsibilities remains universal.
Why This Topic Matters

Ambiguity about who checks what during a PSSR is a root cause of many avoidable issues at start-up—line-ups reversed, interlocks not verified, permits incomplete, isolation integrity assumed but not proven, or emergency systems untested. In a region where regulators and asset owners are converging on robust process safety expectations, well-defined PSSR roles advance multiple objectives at once: reducing major accident hazards, meeting legal and client requirements, protecting people and the environment, and safeguarding business value with on-time, first-time-right start-up.
Standards and practices reinforce this clarity. OSHA PSM 29 CFR 1910.119 requires a pre-startup safety review for new and modified facilities. IEC 61511 expects proof that safety instrumented functions (SIFs) are installed, commissioned, and tested as specified. API RP 14C/750 supports functional safety and integrity in oil and gas systems. NFPA codes inform fire protection readiness and flammable liquid handling (e.g., NFPA 30). Locally, OSHAD provisions, Dubai Municipality and Civil Defence approvals, and ADNOC HSE requirements shape what “ready for start-up” means in practice—documentation controlled, training completed, risk controls verified, and emergency arrangements in place. Without explicit PSSR team responsibilities, these expectations can be partially met on paper but missed in the field.
Key Points to Understand

The PSSR is not a re-HAZOP or a paper exercise; it is a field-anchored verification that what was promised during design, hazard studies (HAZID, HAZOP, LOPA), and MOC processes is actually built, documented, and operable. Several core principles underpin effective team roles and responsibilities:
- Competence and authority: Individuals performing checks must be technically competent and authorized to accept or defer start-up decisions in their discipline.
- Independence in verification: Where feasible, verifiers should not be the same individuals who performed the installation or initial test, to avoid confirmation bias.
- Traceability: Each check must tie to a requirement source (HAZOP action, design basis, cause-and-effect, procedure), and produce verifiable evidence (sign-off, test record, photo, certificate).
- RACI clarity: Every responsibility has a Responsible (does the work), Accountable (approves/owns the outcome), Consulted (provides input), and Informed (receives updates).
- Scope discipline: PSSR scope focuses on readiness to safely introduce energy or hazardous material; non-critical aesthetic or documentation gaps become controlled post-start-up actions only if risk-assessed and approved.
Below is a concise mapping that many UAE facilities adapt to their context. The specifics will vary, yet the structure helps teams avoid gaps and overlaps:
| Role | Core Responsibilities During PSSR | Key Artefacts Verified/Produced | Decision Authority |
|---|---|---|---|
| PSSR Leader/Chair | Plan and lead the review; ensure scope completeness; confirm closure of critical actions; manage RACI; record decisions | PSSR plan, agenda, consolidated checklist, action log, minutes | Accountable for overall PSSR completeness and go/no-go recommendation |
| Operations Supervisor | Field line-up verification; procedure readiness; staffing and training check; control room configuration | Line-up sheets, start-up procedures, operator training records, alarm setpoint lists | Accepts operational readiness and signs off on start permission for operations |
| Process Engineer | Verify design intent, relief sizing basis alignment, setpoints; ensure HAZOP/LOPA actions closed | Updated P&IDs, PFDs, design basis notes, relief documents, action closure evidence | Approves process integrity and defers start-up if critical gaps exist |
| I&C / SIS Engineer | Check cause-and-effect, trip logic, interlock bypass control; confirm IEC 61511 test evidence | Cause-and-effect matrices, SIF proof test records, instrument calibration certificates | Approves SIS and interlock readiness, with authority to block energization |
| Mechanical / Maintenance | Verify mechanical completion and isolation integrity; check rotating equipment readiness; spares and tools | MC/Walkdown punch lists, torquing and pressure test records, spares inventory | Accepts mechanical integrity for start-up |
| Electrical Engineer | Confirm earthing, motor rotations, switchgear testing, arc-flash controls, UPS readiness | Test sheets, relay settings, single-line diagrams, LOTO procedures | Approves electrical energization readiness |
| HSE Advisor | Verify permits-to-work, SIMOPS controls, emergency response and PPE, environmental controls | PTW records, ER plans, spill kits, waste plans, emission controls evidence | Can stop start-up on safety, health, or environmental grounds |
| Commissioning Lead | Coordinate function tests, flushing/cleanliness, pre-energization checks, temporary works removal | Commissioning procedures, test packs, cleanliness certificates, temporary equipment register | Accepts commissioning completion milestones |
| Project Manager / Construction | Close construction punch items; finalize as-builts; confirm redlines applied and controlled | As-built drawings, weld/NDT records, redline P&IDs, completion dossiers | Confirms construction completion to allow PSSR sign-off |
| Vendor / OEM Representative | Witness functional tests; confirm warranty conditions; provide specialized training | Factory and site acceptance test records, OEM manuals, training certificates | Technical sign-off for package/system readiness |
| Document Controller | Ensure controlled access to the latest approved documents; archive PSSR evidence | Document transmittals, master drawing lists, PSSR dossier | Controls document status; no start-up with superseded docs |
| Regulatory Liaison | Verify external approvals and certifications are on file | Civil Defence no-objection, third-party inspection certificates, ADNOC/OSHAD submissions | Confirms regulatory readiness; flags any outstanding conditions |
For those exploring policy organization and governance insights relevant to complex compliance environments, a useful resource is CABINET NPM, which highlights how structured information management supports consistent execution—an underpinning of effective PSSR.
How This Works in Practice

Translating the framework into day-to-day work hinges on disciplined coordination among the roles above. After design hazard reviews (HAZOP, LOPA) and MOC steps conclude, project and commissioning teams drive completion and testing; operations prepare procedures and staffing; HSE readies the permit-to-work and emergency response. The PSSR then becomes a structured, field-oriented verification that synthesizes these streams into a single readiness decision.
- Define scope and boundaries: Clarify the systems to be started, interfaces with live plant, and any enabling works. In brownfield contexts, identify SIMOPS and isolation strategies to protect neighboring operations.
- Lock document baselines: Confirm that as-builts, P&IDs, cause-and-effect matrices, and procedures used for verification are current and controlled. Redlines must be captured and approved.
- Align the RACI: Assign who is Responsible and Accountable for each verification point—especially for critical safeguards like SIF proof tests, relief paths, and emergency shutdowns.
- Run focused field walkdowns: The most effective PSSR sessions happen in the field. Teams verify tag numbers, valve orientation, signage, fire and gas detector coverage, egress paths, and LOTO points.
- Test protective functions realistically: SIS trips, interlocks, and alarms should be tested in a manner representative of operational scenarios, documented per IEC 61511.
- Resolve or mitigate gaps: If a critical item fails (e.g., an interlock doesn’t trip), the PSSR team invokes management of change, assigns immediate corrective actions, and—if justified—applies a temporary operating envelope with compensating controls and a strict time limit.
- Make the go/no-go decision: The PSSR leader consolidates evidence, confirms closure of critical actions, and obtains accountable sign-offs. Non-critical items become controlled post-start-up actions, if risk-assessed and agreed.
Consider a few sector-specific nuances:
- Refining and petrochemicals: Relief and flare systems alignment with design loads; hydrocarbon line-ups with double-block-and-bleed isolation; tank farm overfill protection confirmed against API and site standards.
- Offshore platforms: SIMOPS with drilling or lifting; lifeboats and muster systems; HVAC pressurization for enclosed spaces; emergency shutdown and blowdown logic tested end-to-end.
- Power generation: Turbine permissives and trips; boiler feed controls; electrical protection coordination; fuel gas conditioning skids verified before gas-in.
- Construction/MEP handovers: Pressure testing of chilled water loops; AHU interlocks; fire alarm cause-and-effect; Civil Defence inspection certificates on file before energization.
Across all contexts, the principle is constant: the PSSR team verifies readiness through evidence—not assumption—so that when energy is introduced, the plant behaves as intended and people know what to do if it does not.
Benefits and Practical Use Cases

When roles and responsibilities are explicit and practiced, organizations consistently see benefits beyond “passing the PSSR.” These benefits are operational, financial, and cultural:
- Risk reduction made real: Closure evidence for HAZOP actions, functional tests for SIS and interlocks, and isolation checks reduce the likelihood of major accidents at the very moment risk peaks—start-up.
- Schedule integrity: Clear decision authority prevents last-minute disputes; issues are identified earlier and resolved systematically, avoiding cascading delays.
- Regulatory confidence: OSHAD-aligned documentation, ADNOC HSE expectations, and Civil Defence certificates in a single PSSR dossier simplify audits and approvals.
- Operational readiness: Operators start with procedures they co-validated, alarm setpoints they understand, and emergency plans rehearsed—raising start-up reliability.
- Asset lifecycle gains: Maintenance and spares readiness at start-up improve mean time between failures (MTBF) and shorten time-to-stable-operations.
Concrete examples help illustrate how the team model works:
In a gas processing plant, the I&C/SIS engineer and operations supervisor jointly verified that an emergency shutdown (ESD) valve closed on low downstream pressure—an overlooked logic path. The test exposed a wiring error; correcting it before gas-in avoided a potential overpressurization scenario. This outcome happened because responsibility for functional testing and acceptance was clear and evidence-based.
At a bulk storage terminal, the project manager believed the tank overfill protection was fully commissioned. During PSSR, the process engineer cross-checked the cause-and-effect matrix with the installed sensor tags and found a mismatch: the independent high-high level (IHHL) instrument was not wired to the shutdown relay. The role clarity—process engineer responsible for design intent verification, SIS engineer responsible for trip functionality—prevented an overfill risk on day one.
In a district cooling plant handover, the commissioning lead wanted to energize pumps to keep schedule. The HSE advisor insisted on completing LOTO verifications, egress checks, and emergency signage for confined equipment rooms. The PSSR leader mediated using the RACI and risk criteria; temporary energization proceeded under a narrow operating envelope with fire watch and immediate close-out actions, preserving safety and schedule.
Best Practices and Points of Caution

Experience across complex start-ups suggests a set of habits that consistently raise PSSR quality—and pitfalls teams should avoid:
- Anchor verification to source requirements: Every checklist item should point to where the requirement comes from (HAZOP node, MOC, design basis, IEC 61511 clause, API guidance). This keeps the PSSR from drifting into opinion-based debates.
- Use discipline-owned mini-checklists: Operations, process, I&C/SIS, mechanical, electrical, HSE, and commissioning each own their short lists that feed the consolidated PSSR record. Ownership raises accountability.
- Demand end-to-end testing for critical safeguards: For trips and interlocks, stimulate the sensor and observe the final element to prove the whole chain—not just PLC logic.
- Separate punch lists: Maintain a clear distinction between safety-critical items that block start-up and non-critical items that can be closed post-start under risk control. The PSSR leader protects this boundary.
- Manage SIMOPS deliberately: If brownfield or adjacent systems are live, secure isolations, communication protocols, and emergency arrangements. Involve operations early and visibly.
- Control changes even during PSSR: Late discoveries can trigger fixes; use MOC to ensure modifications are reviewed, documented, and tested before declaring readiness.
- Keep the dossier auditable: PSSR records—sign-offs, photos, test results, permits, certificates—should be traceable and stored in a controlled repository for future audits and learning.
- Train for the PSSR role, not just the task: Team members should understand why each verification matters, not just how to tick a box. This keeps the review risk-focused and resilient under time pressure.
A few cautions:
- Avoid checklist bloat: Keep the list risk-based and scoped; endless line items dilute focus on what truly prevents harm at start-up.
- Do not skip field time: Desktop reviews miss the details that cause upsets—reversed valves, mislabeled tags, blocked access, or temporary works left in place.
- Beware of authority gaps: If no one is empowered to say “no-go” for their discipline, the PSSR becomes a formality and risks migrate into operations.
Frequently Asked Questions About PSSR Team Roles And Responsibilities

How is a PSSR team different from a commissioning team?

Commissioning teams make systems function as designed; they execute tests to prove performance. The PSSR team independently verifies that critical risk controls and readiness criteria are actually in place before introducing energy or hazardous materials. Many people wear both hats in smaller projects, but the PSSR perspective is specifically risk- and readiness-focused, not just function-focused.
Who should lead the PSSR?
A senior individual with process safety awareness, cross-disciplinary credibility, and strong facilitation skills typically leads. The leader must be empowered to enforce scope discipline, manage disagreements, and issue a go/no-go recommendation based on evidence. In many organizations, this is an operations manager or process safety specialist with project exposure.
Do we need separate PSSRs for modifications?
Yes, significant modifications that change process safety information, introduce new hazards, or alter existing safeguards should trigger a PSSR prior to restart. The scope scales with risk: a like-for-like instrument swap may not need a full team, while a control system upgrade or new tie-in likely does.
What evidence satisfies IEC 61511 expectations during PSSR?
Evidence typically includes installed SIF lists tied to safety requirements specifications (SRS), proof test records, cause-and-effect matrices, loop checks, calibration certificates, bypass logs with expiration controls, and end-to-end trip demonstrations showing sensor-to-final-element action with documented results.
How should responsibilities be shared with contractors and vendors?
Vendors are responsible for demonstrating performance of their packages; contractors are responsible for mechanical completion and test packs. The owner’s team remains accountable for verifying safety-critical readiness, integrating package tests into plant-level safeguards, and making the final start-up decision. This RACI should be contractually explicit.
Is a PSSR required by UAE regulations?
While requirements can vary by emirate and regulator, the expectation of a pre-startup safety review is embedded in international good practice (e.g., OSHA PSM) and is often required or strongly implied by ADNOC HSE expectations, OSHAD frameworks, Civil Defence approvals, and client standards. Most major operators in the UAE mandate a PSSR for new starts and significant modifications.
What is the difference between HAZOP closure and PSSR sign-off?
HAZOP closure confirms that design-phase risk actions are addressed in drawings, specifications, and plans. PSSR sign-off confirms that those risk controls are physically installed, tested, documented, and ready in the field before start-up. HAZOP assures the plan; PSSR assures the reality.
Can we start up with open actions?
Only if the open actions are demonstrably non-critical to safe start-up and are managed under a documented temporary operating envelope with compensating controls, owners, and a short closure timeline approved by accountable leaders. Critical safeguards must be in place and working before start.
Conclusion
Clear, risk-based definition of PSSR team roles and responsibilities transforms pre-startup verification from a rushed checklist into a disciplined assurance step that protects people, assets, and schedules. As shown above, the team is multidisciplinary and authority-based: operations validates operability; engineering verifies design intent and protective functions; HSE enforces safe systems of work and emergency readiness; commissioning proves functionality; documents, vendors, and regulators each have defined places in the chain. When these parts work together—anchored in standards like IEC 61511, API guidance, NFPA codes, and UAE regulatory expectations—the PSSR becomes a confident “yes” grounded in evidence, not hope.
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 track record with pre-startup assurance and process safety spans complex, high-hazard environments worldwide. Over decades, our teams have supported refinery expansions, offshore brownfield tie-ins, petrochemical unit revamps, utility-scale power projects, and intricate construction handovers with demanding MEP and fire/life safety interfaces. In each case, the differentiator has been disciplined role clarity within the PSSR team, coupled with practical field experience to verify readiness beyond the paperwork. Our references illustrate how RACI models were adapted to owner/operator cultures, how commissioning and operations aligned on acceptance criteria, and how regulatory interfaces—from Civil Defence approvals to third-party inspections—were integrated into coherent dossiers that stood up to internal and external audits.
These references are not just summaries of outcomes; they provide a window into the methods that work under real schedule pressure and SIMOPS constraints. Readers will find examples of end-to-end safeguard testing under IEC 61511, the closure of HAZOP and LOPA actions traced to field evidence, lessons from QRA and Bowtie analyses that informed start-up barricading and egress checks, and environmental controls validated before introducing hazardous materials. Across jurisdictions and industries, the throughline is consistent: clearly defined roles and responsibilities, executed with technical rigor and operational common sense, deliver safe and timely start-ups. Reviewing our references can help teams benchmark their own PSSR approach, spot common pitfalls, and adopt proven practices tailored to their facility type and risk profile.
For more information about our references, visit Our References.
Speak With NPM
If you would like to discuss how role clarity could strengthen your next start-up or modification, we are happy to share perspectives grounded in real project experience. Whether you operate a refinery unit, a power island, or a complex MEP handover, our team can help you translate standards and hazard study outcomes into practical, field-ready PSSR responsibilities. We welcome questions and are available to talk through what “ready for start-up” means for your specific systems and risk profile.
For any further questions or to speak with our team, Contact Us.