A pre-startup safety review, or PSSR, is the final, documented gate a facility passes through before it is allowed to start up. After new equipment is installed, a change is made, or a plant comes out of a turnaround, there is a moment just before hazardous material is introduced or the process is re-energized when someone has to formally confirm the facility is genuinely ready. The PSSR is that confirmation. It is a structured check that the procedures are in place, the people are trained, the outstanding work is closed, and the safety systems will actually function - and it is signed off before anyone opens a valve to bring the process back to life.
Pre-Startup Safety Review in one line: A pre-startup safety review (PSSR) is a formal, documented check performed before introducing hazardous material into new or modified equipment, or restarting a facility after a change or turnaround. It verifies that construction matches the design, procedures and training are in place, the punch list is closed, and safety systems are functional - the final readiness gate before startup.
A pre-startup safety review works through a defined checklist, and each item confirms a different dimension of readiness. The first is that the physical facility matches its design and specifications - that what was actually built or modified is what the drawings and the reviewed design called for, not a field improvisation that never went back through review. The second is procedural: operating procedures, safe work procedures, and emergency procedures for the equipment must be in place and current, because a plant cannot be safely run on procedures that do not yet exist or still describe the old configuration.
The review also confirms the human side. The operators and maintenance staff who will run the equipment must have been trained on it, so that the startup is not the first time someone learns how the new or modified process behaves. And it verifies that the punch list - the record of outstanding construction and commissioning items - has been worked down to the point where nothing safety-critical remains open. A punch list item that would be merely inconvenient during operation may be perfectly acceptable to carry, but one that affects safe startup has to be closed before the review can pass.
Crucially, the PSSR confirms that safety systems are functional, not merely installed. Relief valves set and in service, shutdown and interlock systems tested and enabled, alarms configured and proven, gas and fire detection live - these are the barriers that protect the plant once hazardous material is present, and the review checks that they will actually work at the moment they might first be needed. The whole point of doing this before startup is that these are precisely the systems there is no safe way to test with a live, hazardous process already running. The PSSR is the last opportunity to confirm the protections are real before betting the startup on them.
A pre-startup safety review is closely coupled to management of change, and the two are designed to work as a pair. When a change is made under an MOC - new equipment, a modified process, a revised operating limit - the MOC identifies what was changed and what has to be updated as a result: drawings, procedures, training, safety systems. The PSSR is where all of that is confirmed complete before the changed facility is started. In effect, the MOC defines what readiness means for this particular change, and the PSSR checks that the readiness was actually achieved.
This pairing closes a gap that would otherwise be easy to leave open. It is entirely possible to approve a change on paper, install the hardware, and then start up without ever confirming that the promised procedure updates were made or the promised training was delivered. The PSSR is the checkpoint that forces those loose ends to be tied before startup rather than discovered afterward. A change that sailed through its MOC approval but left the operating procedure unrevised should be caught at the PSSR, because the review asks directly whether the procedures for the equipment are current.
The scope of a PSSR follows the scope of what triggered it. A major turnaround or a large capital modification warrants a thorough, wide-ranging review, while a small, well-understood change may need only a focused check of the specific items it touched. What does not change is the principle: any time hazardous material is about to be introduced into equipment that is new, has been modified, or has been down for significant work, the readiness is confirmed and signed off before startup. The PSSR is the disciplined answer to the question every startup should force someone to answer out loud - is this facility actually ready to run safely.
The control room is deeply involved in a pre-startup safety review because it is the room from which the startup will actually be conducted and the place where the facility's readiness becomes visible in real time. Many of the items a PSSR verifies show up directly on the control system - that alarms are configured and not disabled, that interlocks are enabled rather than bypassed, that instruments are reading sensibly, that valves are in their expected startup positions. On a site with a cloud SCADA platform such as Merobix, the operator can confirm much of that readiness from the live displays, checking that the safety and control systems the PSSR calls out are genuinely live before the startup begins.
A common and dangerous failure mode is starting up with protections still defeated from the work that just finished - an interlock left bypassed for testing, an alarm suppressed during construction, a temporary jumper still in place. The control system is where those defeats are most visible, and a PSSR that includes checking the control room for active bypasses, forced points, and suppressed alarms catches the protection that was quietly switched off and never restored. The screen that shows a bypass still active is doing exactly the job the review needs it to do.
Once the review passes and the startup proceeds, the control room becomes the place where readiness is proven in practice. As the process is brought up, the operators watch the pressures, temperatures, and flows against expectation, confirming that the plant behaves as the review predicted and that the safety systems the PSSR verified actually engage if needed. For a remote or lightly manned facility, having that full live picture in the control room is what lets a startup after a change be conducted deliberately - with the readiness confirmed on paper by the PSSR and then confirmed again in the data as the plant comes to life.
A PSSR is performed before introducing hazardous material into equipment that is new, has been modified, or has been down for significant work such as a turnaround. It is the readiness gate that must be passed before startup, confirming the facility is genuinely ready to run safely. The scope scales with the trigger - a major modification warrants a broad review, while a small change may need only a focused check of what it touched.
Management of change is the process that evaluates and approves a change and defines what must be updated as a result - drawings, procedures, training, safety systems. The pre-startup safety review is the checkpoint that confirms all of that was actually completed before the changed facility is started. In short, MOC defines what readiness means for the change, and the PSSR verifies that readiness was truly achieved before startup.
A PSSR confirms that safety systems are functional, not just installed - relief valves in service, shutdown and interlock systems tested and enabled, alarms configured and proven, and gas and fire detection live. It also checks for protections that may have been defeated during the preceding work, such as bypassed interlocks or suppressed alarms left over from testing. These are exactly the systems that cannot be safely tested once a live hazardous process is running, so the review confirms them beforehand.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.