Pre-Startup Safety Review: Building a Readiness Evidence Pack

Prepare a pre-startup safety review evidence pack with clear scope, controlled records, reviewed findings and traceable readiness decisions.

A pre-startup safety review (PSSR) brings together evidence that a new or modified process is ready for the next authorised operating stage. Its value is not the number of boxes ticked. It is whether the people making the readiness decision can trace each important requirement to current, reviewed evidence.

This guide offers a practical way to assemble a PSSR evidence pack for project and operations teams. It is not a commissioning procedure, a compliance certificate or permission to introduce hazardous materials. The facility’s approved procedures, competent engineering judgement and applicable regulatory requirements govern the actual decision.

Start with the review boundary, not a generic checklist

Write a short scope statement before collecting documents. Identify the equipment, interfaces, modification and proposed operating stage being reviewed. Make clear whether the review covers an entire facility, one system or a staged handover. A drawing number alone may not identify what is included when neighbouring systems remain under construction or operation.

Record the design revision and change references against which readiness will be judged. Ask the project and operations representatives to agree the boundary. A late change to an instrument, control narrative or operating envelope should be assessed through the facility’s change process, rather than silently absorbed into the pack.

For a modified facility, the connection between management of change and hazard-study review helps explain why the review boundary needs to follow the change, including its interfaces.

Understand what the published guidance does and does not say

For US processes covered by its process safety management standard, OSHA 29 CFR 1910.119(i) sets out a pre-startup review addressing construction against design, procedures, hazard-analysis or management-of-change requirements, and operator training. This is a useful reference for the concept, but it is not an Australian legal requirement.

In Australia, identify the requirements applicable to the facility and jurisdiction. Safe Work Australia’s major hazard facility safety management systems guide addresses an integrated approach to controlling major-incident risks. WorkSafe Queensland’s adopted major hazard facility guides include safety assessment, safety management systems, emergency planning and worker training. Those resources concern major hazard facilities; they should not be presented as a universal checklist for every project.

Build an evidence index that a reviewer can use

Create one controlled index rather than sending an unstructured folder of attachments. For each requirement, record its source, the responsible person, the evidence reference and revision, the reviewer, the review date and any unresolved finding. Link to the controlled record where possible so that copied files do not become a competing source of truth.

Keep evidence status separate from acceptance status. “Uploaded” means a record is available. “Reviewed” means someone has examined it. “Accepted” should mean the authorised reviewer has judged it against the relevant acceptance basis. A dashboard that merges those stages can make unfinished work look complete.

Group the evidence around readiness questions

Design and installed condition: Can the team identify the applicable design basis and the records showing what was installed? Organise relevant drawings, equipment information, inspection records and formally resolved discrepancies. The reviewer needs to understand which records represent the installed condition and which are still being updated.

Hazard-study follow-up: Can each relevant recommendation be traced to its response and accepted evidence? Do not replace the study register with a summary stating that all actions are closed. Preserve the relationship between the original scenario, the action and the reviewed result. The HAZOP action close-out checklist provides a separate, more detailed way to organise that evidence.

Operating and emergency information: Are the relevant approved instructions available to the people who will use them? Record document revisions, review status and the arrangements for communicating changes. Listing a procedure title does not establish that it covers the changed equipment or proposed operating stage.

People and responsibilities: Who needs to understand the change, and what records demonstrate that the required preparation has occurred? Include relevant training and competency evidence under the site’s arrangements, rather than treating attendance at a project meeting as proof of operational readiness.

Protective functions: Where the scope includes safety-related functions, reference the applicable requirements, verification or validation records, and outstanding findings. Keep this evidence connected to the facility’s functional safety engineering arrangements. A general readiness checklist does not replace the work required by that lifecycle.

Make outstanding findings visible without normalising them

An open-item list should identify the affected requirement, the exact evidence gap, its owner, the required next action and who must assess its significance. The appropriate authority must determine what prevents progression under the facility’s procedures and applicable requirements. A due date, low item count or proposed temporary workaround is not itself a basis for proceeding.

Avoid vague entries such as “documentation to follow”. State which document, which system and which decision depends on it. If evidence conflicts with the installed condition, record the conflict explicitly and route it to the competent reviewer. Do not use the PSSR meeting to improvise technical acceptance criteria or bypass an unresolved protective requirement.

Use a short readiness record alongside the detailed pack

A concise cover record can make the decision traceable without reproducing every attachment. Include the review boundary, proposed stage, document baseline, participants and their roles, reviewed evidence index, unresolved findings, decision and authorisation references. State the conditions that require the review to be revisited, such as a subsequent design or scope change, according to the facility’s process.

An illustrative record might read: “System boundary: compressor package and identified utility interfaces. Evidence baseline: controlled index revision C. Finding: the operating instruction references a superseded control narrative. Owner: operations document lead. Next step: reconcile the instruction with the approved design and obtain review before the affected readiness decision.” This is an example of record quality, not a finding from a Pro Engineers project or an instruction to start equipment.

Keep the PSSR distinct from the earlier studies

A HAZOP study examines deviations and their consequences within an agreed scope. A PSSR evidence review asks whether the requirements relevant to the proposed stage are supported by adequate records and accepted outcomes. The activities connect, but repeating a workshop title in a checklist does not demonstrate that its recommendations were addressed.

Similarly, mechanical completion, commissioning activities and operational authorisation should not be treated as interchangeable labels. Use the facility’s definitions and responsibilities to show how their records connect. Where the boundary or acceptance basis remains uncertain, resolve that uncertainty with the responsible engineering and operating authorities before relying on the pack.

Practical next step

Begin with the project’s existing readiness procedure and create a one-page evidence index for the agreed scope. Test it against three important requirements: can a reviewer find the current evidence, identify who accepted it and see any unresolved finding? Address the gaps in that traceability before expanding the checklist. For related study planning, explore Pro Engineers’ process engineering services and the linked hazard-study resources.