Starting a new facility is a complex undertaking, and the transition from construction to operation is one of the most critical phases. Without a systematic verification of every safety system, procedure, and piece of equipment, organizations expose themselves to significant operational, regulatory, and human risks. A pre-startup safety review (PSSR) serves as the final checkpoint—a structured, documented process that proves a facility is ready to operate safely. This article provides a comprehensive guide to planning, executing, and documenting an effective PSSR for new facilities, covering essential steps, best practices, common pitfalls, and regulatory context.

What is a Pre-Startup Safety Review?

A pre-startup safety review is a systematic assessment performed before a new or modified facility begins operations. Its primary goal is to ensure that all safety-related features—hardware, software, procedures, and personnel—are in place and functioning as designed. The concept originates from process safety management (PSM) standards, particularly those enforced by OSHA (29 CFR 1910.119) for highly hazardous chemicals, but it has become a universal best practice for any new industrial or manufacturing facility.

An effective PSSR goes beyond a simple equipment walk-down. It validates that hazard analyses (such as HAZOP or what-if studies) have been completed and that recommended safeguards are implemented. It checks that operating procedures are written, understood, and available. It confirms that emergency response plans are in place and that staff have been trained. Without a thorough PSSR, small oversights—like a missing lockout/tagout point or an incorrectly configured alarm—can escalate into major incidents during startup, when the process is most vulnerable.

Key Steps in Conducting an Effective PSSR

While the specific sequence may vary by industry and facility complexity, the following eight steps form a robust framework that can be adapted to any project.

1. Plan the Review

Every successful PSSR begins with clear planning. First, define the review's scope: Which systems, equipment, and areas are included? Is this a brand-new facility, an expansion, or a modification to an existing process? Establish measurable objectives—for instance, "verify that all pressure-relief devices are installed and certified" or "confirm that all safety interlocks are tested and operational."

Assemble a cross-functional team. A typical PSSR team includes representatives from engineering, operations, maintenance, safety, and environmental compliance. For complex projects, include the process hazard analysis (PHA) facilitator and a subject-matter expert for specialized systems (e.g., fire protection, instrumentation). Assign a team leader responsible for scheduling, documentation, and final sign-off. Set a realistic timeline that allows enough time for inspections, document reviews, and corrective actions. Rushing a PSSR compromises its thoroughness.

2. Gather Documentation

The PSSR team must have ready access to all relevant design, safety, and operational documentation. This typically includes:

  • Process flow diagrams (PFDs) and piping and instrumentation diagrams (P&IDs), as-built.
  • Process hazard analysis (PHA) reports and associated recommendations.
  • Equipment datasheets and vendor manuals.
  • Safety system design specifications (e.g., fire and gas detection, emergency shutdown systems).
  • Standard operating procedures (SOPs) and emergency response plans.
  • Training records and competency assessments for operators and technicians.
  • Regulatory permits and environmental compliance documents.
  • Previous PSSR checklists from similar facilities or phases, if applicable.

Organize this documentation in a central repository. The team should review key documents before any physical inspections to identify potential discrepancies between design and actual installation.

3. Inspect the Facility

Physical inspection is the heart of a PSSR. The team conducts a systematic walk-down of the facility, comparing the installed equipment against the as-built drawings and design specifications. Key inspection items include:

  • Safety equipment: Are fire extinguishers, eyewash stations, safety showers, and emergency exits in place, unobstructed, and properly labeled?
  • Process safety devices: Are pressure-relief valves, rupture disks, and interlocks installed correctly? Check that settings match the design basis.
  • Piping and electrical systems: Verify proper supports, insulation, grounding, and labeling. Look for potential pinch points, leaks, or loose connections.
  • Instrumentation and controls: Confirm that sensors, transmitters, and control valves are correctly positioned and calibrated.
  • Ventilation and containment: Ensure that secondary containment, dikes, and ventilation systems are operating as intended.

Use a detailed checklist to ensure every element is reviewed. The team should photograph any non-conformances and note their exact location.

4. Review Procedures

No matter how well equipment is installed, safe operation depends on clear, accurate procedures. The PSSR team must review all SOPs for each major operation, including startup, shutdown, normal operation, and abnormal situations. Emergency response procedures—spill response, fire evacuation, medical emergencies—must be available and easy to follow. Verify that procedures reflect the current facility configuration and that any changes made during construction are incorporated.

Besides written documents, review the availability of safety data sheets (SDS) for all chemicals. Check that warning signs, labels, and safety placards are posted according to regulatory requirements.

5. Identify Hazards

Although a full PHA should have been completed during the design phase, the PSSR provides an opportunity to re-examine risks in the as-built environment. The team should conduct a hazard identification session focused on anything that might have changed since the original analysis—such as layout modifications, equipment substitutions, or new chemical interactions.

Use structured techniques such as a what-if analysis or a bow-tie diagram to assess residual risks. For each identified hazard, confirm that appropriate safeguards exist. If new hazards are found, they must be documented and addressed before startup. For example, if a ventilation duct was rerouted during construction, the team needs to verify that the new path still provides adequate air exchange in occupied areas.

6. Verify Training

People are the last line of defense. The PSSR must confirm that all personnel who will operate or maintain the facility have received adequate training. Review training records to ensure that each operator has completed required modules—both general safety training and equipment-specific instruction. Conduct practical drills where possible: ask an operator to demonstrate a startup sequence, or simulate an alarm and watch the response.

Training verification should also cover contractors who will be present during startup, such as commissioning engineers or temporary operators. Ensure they are briefed on site-specific safety rules and emergency procedures.

7. Document Findings

During the review, every observation—compliant or non-compliant—must be captured. Use a standardized PSSR checklist or a digital form that tracks findings by category (e.g., equipment, procedures, training). For each deficiency, assign a priority level and an owner with a deadline for corrective action. Critical issues, such as a missing fire suppression system or an untested emergency shutdown, must be resolved before any startup activity. Non-critical items may be tracked as action items with a defined completion date.

All documentation should be secure and retained for future audits, regulatory inspections, and subsequent PSSRs for modifications. A well-documented PSSR also supports continuous improvement when the facility is later expanded or decommissioned.

8. Conduct the Final Review

Once corrective actions are completed, hold a final sign-off meeting with all stakeholders—management, operations, engineering, safety, and regulatory liaisons. Present a summary of the PSSR findings, including any outstanding items and their resolution plans. Obtain written authorization from facility management to proceed with startup. This sign-off should be documented in a formal PSSR completion report.

Some organizations also perform a "dry run" or simulation of the startup process as part of the final review, especially for highly complex or hazardous facilities. The final review meeting is not a formality—it is the last chance to catch oversights before the process becomes live.

Best Practices for a Successful PSSR

Beyond the step-by-step process, adopting the following best practices will elevate the quality and reliability of any pre-startup safety review.

Involve a Cross-Functional Team

A PSSR performed solely by engineers or safety professionals will miss critical operational insights. Operators know how equipment behaves under different conditions; maintenance personnel can spot installation mistakes; environmental specialists ensure compliance with permits. Assemble a team that mirrors the diversity of stakeholders who will be responsible for safe operation. Rotate team members for different sections to avoid fatigue and bring fresh eyes to each area.

Use Standardized Checklists

Checklists are essential for consistency. Generic checklists should be customized for the specific facility—adding items for unique hazards (e.g., hydrogen piping, high-temperature reactors) or regulatory requirements (e.g., EPA's Risk Management Plan for flammable substances). Digital checklists with photo attachments and real-time syncing can streamline documentation and make it easier to track resolution of findings. Many industry associations provide template PSSR checklists that can be adapted: for example, the NIOSH has guidance for chemical processing, and the Center for Chemical Process Safety (CCPS) publishes detailed checklists for process safety reviews.

Address Issues Promptly

Delays in resolving PSSR findings erode confidence in the review process. Establish a clear escalation path: any finding rated as "stop-work" should be reported to senior management immediately. Use a risk matrix to prioritize—high-probability, high-consequence items must be fixed before any startup; low-priority items may be completed within a scheduled window but must not be forgotten. Prompt resolution also prevents the accumulation of corrective actions that can overwhelm a startup team.

Maintain Meticulous Documentation

Documentation is not just for the current review—it serves as a baseline for future modifications, audits, and regulatory inspections. Keep a master log of all PSSR findings, including dates, assigned owners, and closure evidence. Store this log with the facility's safety records. For large facilities, consider integrating PSSR documentation into an existing safety management system (e.g., SAP, Intelex, or Sphera). Duplicate records should be avoided; use a single source of truth that is accessible to the entire team.

Invest in Training and Drills

Training verification should not be a box-checking exercise. Conduct site-specific drills that simulate real startup scenarios—such as a pressure buildup or a small leak—to test operator response under pressure. If the facility has automated systems, run functional tests of all alarms and shutdowns with operators present. Training must be repeated after any significant changes found during the PSSR. Document each training session and test result.

Common Pitfalls to Avoid

Even experienced teams can fall into traps that compromise a PSSR. Being aware of these pitfalls helps maintain rigor.

  • Rushing the schedule: A compressed timeline leads to skipped inspections or superficial reviews. Allow buffer time for unexpected issues.
  • Relying too heavily on checklists: Checklists are tools, not substitutes for critical thinking. Encourage team members to question assumptions and look beyond the list.
  • Ignoring "minor" findings: Small issues—like a missing bolt or a slightly misaligned sensor—can cascade during operation. All findings should be tracked and resolved.
  • Poor communication with construction teams: If the PSSR team discovers a discrepancy, it may be due to an undocumented field change. Maintain open channels with construction managers to capture all deviations.
  • Lack of management commitment: Without visible support from leadership, the PSSR can become a bureaucratic step rather than a safety gate. Management must allocate resources and enforce sign-off discipline.

Regulatory and Standards Context

In many jurisdictions, a PSSR is not optional. For facilities handling highly hazardous chemicals, OSHA's Process Safety Management standard (29 CFR 1910.119) mandates a pre-startup safety review that includes verification of everything from equipment integrity to operating procedures. The U.S. Environmental Protection Agency similarly requires a PSSR as part of its Risk Management Program for regulated processes.

International standards such as ISO 45001 (occupational health and safety management) and ISO 31000 (risk management) emphasize systematic reviews before introducing new operations. Industry-specific guidance—from the American Petroleum Institute (API RP 752) for refinery hazards to NFPA codes for fire protection—further define what a PSSR should cover. Organizations that adopt these standards not only comply with regulations but also build a stronger safety culture.

Integrating PSSR with Overall Project Management

A PSSR should not be a last-minute event. To be truly effective, it must be embedded in the project lifecycle. During the front-end engineering design (FEED) phase, begin collecting the documentation that the PSSR will later verify. Include PSSR milestones in the project schedule—for example, three months before mechanical completion, start forming the team; one month before startup, complete all inspections and corrective actions.

Use a management of change (MOC) process to handle any modifications discovered during the PSSR. If the team finds that a valve type was swapped without an MOC, stop the review, formally approve the change, and then re-verify safety implications. This integration prevents the PSSR from becoming an afterthought and ensures that safety is built into the project from the start.

Conclusion

A pre-startup safety review is much more than a box to check before turning on the equipment. It is a rigorous, team-based verification that saves lives, protects assets, and prevents regulatory penalties. By planning thoroughly, involving a diverse team, using structured checklists, and maintaining strong documentation, organizations can significantly reduce the risk of incidents during the vulnerable startup phase. As facilities become more complex and automation increases, the discipline of a thorough PSSR becomes even more critical. Invest the time and resources upfront, and you will not only meet compliance requirements but also build a foundation of operational excellence that lasts for the facility's entire life.