When a chemical plant, refinery, or food-processing facility flips the switch on a new line, the moment looks routine from the outside. Inside, it’s anything but. The hours before startup are when small oversights become expensive ones, and where leadership teams either prove their process safety program works or discover it doesn’t.
That’s why pre-startup safety reviews, often called PSSRs, are getting more boardroom attention than they used to. Insurers ask about them. Investors flag them in ESG conversations. And after a string of high-profile incidents across heavy industry, operations leaders are tightening the screws on what a PSSR actually has to cover before a process goes live.
What a PSSR actually does
A PSSR is a structured, documented check performed before a new or modified process introduces hazardous chemicals or energy. The idea is simple: confirm that what was designed on paper matches what was built in the field, and that the people, paperwork, and protections are all in place.
In the United States, the requirement sits inside OSHA’s Process Safety Management standard, specifically the PSM regulation, which applies to facilities handling threshold quantities of highly hazardous chemicals. The standard spells out what a PSSR has to verify before startup, and inspectors take it seriously.
Beyond the legal text, a good PSSR is a final sanity check. It’s the moment where engineering, operations, maintenance, and safety stop working in parallel and sit in the same room with the same checklist.
The pieces that a strong review covers
Companies that run PSSRs well tend to organize them around a few non-negotiable categories. The exact format varies, but the spirit is consistent.
- Construction and equipment checks. Confirm that equipment was built and installed to the design specs, with the right materials, ratings, and tie-ins. Walk the line, don’t just read the drawings.
- Procedures in place. Operating, maintenance, emergency, and safe-work procedures should be written, current, and accessible to the crew that will use them on shift one.
- Training completed. Operators and maintenance staff need documented training on the new or modified process, including the hazards and the upset scenarios, not just the normal run conditions.
- PHA recommendations closed. Any action items from the process hazard analysis or management-of-change review should be resolved, deferred with justification, or formally accepted by leadership.
- Management of change. For modified processes, the MOC paperwork should be complete and signed off. Skipping this step is one of the most common audit findings.
Why leadership is paying closer attention
Process safety used to live deep inside the operations org chart. That’s changing. The U.S. Chemical Safety Board has spent years documenting incidents where the root cause traced back to a rushed or skipped startup review, and those CSB investigations have become standard reading for risk committees and corporate counsel.
There’s also a financial layer. Property insurers in the industrial market are asking sharper questions about PSM program maturity during renewals, and a sloppy PSSR record is the kind of detail that surfaces during loss-control surveys. The cost of getting it wrong shows up in premiums long before it shows up in an incident.
Even outside PSM-covered facilities, the logic carries over. Food and beverage plants, battery manufacturers, and pharmaceutical lines all benefit from the same discipline: don’t start until someone independent has signed off that you’re ready.
Where teams get tripped up
The pattern of PSSR failures isn’t mysterious. It’s almost always pressure. Schedules slip, a customer needs product, and the startup date doesn’t move even when the punch list grows. Reviews get compressed, signatures get chased, and the checklist becomes a formality.
The other common trap is treating the PSSR as a single-person job. A meaningful review needs cross-functional eyes, including someone outside the project team who can ask uncomfortable questions without worrying about the schedule. For complex modifications, many operators bring in a third-party reviewer, and detailed guidance from consultancies like Safety by Design can help internal teams benchmark their own checklist against what an outside expert would expect to see.
A third issue: poor documentation. If the review happened but nobody can find the signed record two years later during an audit, the regulator will treat it as if it didn’t happen. Paper trails matter.
Building a culture that takes startup seriously
The companies that handle PSSRs well share a few habits. They schedule the review with the same weight as a commissioning milestone. They give the safety lead authority to delay startup, not just to recommend it. And they treat findings as learning material for the next project, not as a scolding.
Industry research has long argued that strong process safety culture correlates with stronger overall operational performance, not weaker. Plants that take time before startup tend to spend less time fixing things after it.
The boardroom version of this story is short. A PSSR is cheap. An incident isn’t. And in 2026, with regulators, insurers, and investors all watching the same dashboard, the cost of skipping the review keeps going up.