How Hazard Analysis Should Shape Operating Procedures in Oil and Gas
How should hazard analysis shape operating procedures?
A process hazard analysis (PHA) should tell the procedure writer exactly where the procedure matters most. Every scenario the PHA team identifies, every safeguard it credits, and every deviation it evaluates points to a step, a limit, or a warning that belongs in an operating procedure. When the two documents are connected, the operator holding the procedure is carrying the hazard analysis into the field one step at a time.
In practice, the connection is often weaker than it looks. The PHA is completed by one team, filed in a report or a software database, and revalidated every five years. The procedures are written and revised by a different group, on a different schedule, against a different standard. Both can be complete and compliant while saying different things about the same hazard.
This guide covers what the OSHA standard connects between the two, where the connection tends to break down, and six practical ways to make hazard analysis shape the procedures your operators actually use.
What does OSHA require to connect the PHA and the procedure?
OSHA's Process Safety Management standard, 29 CFR 1910.119, treats hazard analysis and operating procedures as separate elements, but it ties them together in several places. Knowing where those ties sit is the first step to using them.
The PHA identifies the hazards and the controls. Under 1910.119(e)(3), a process hazard analysis must address the hazards of the process, previous incidents with potential for catastrophic consequences, the engineering and administrative controls applicable to the hazards, the consequences of failure of those controls, facility siting, and human factors. Operating procedures are among the most common administrative controls a PHA team relies on.
PHA findings must reach the people doing the work. Under 1910.119(e)(5), employers must establish a system to promptly address the team's findings and recommendations, document the actions taken, and communicate those actions to the operating, maintenance, and other employees whose work may be affected. For many recommendations, the operating procedure is where that communication lands.
Procedures must carry operating limits and the consequences of deviation. Under 1910.119(f)(1)(ii), operating procedures must address the consequences of deviation and the steps required to correct or avoid deviation. That is the same territory a PHA covers when it evaluates what happens if a parameter drifts outside its intended range.
Procedures must describe safety systems and their functions. Under 1910.119(f)(1)(iv), the procedure explains the safety systems the PHA credited as protection.
Changes must flow both ways. Under the management of change requirements in 1910.119(l), a change that affects operating procedures requires those procedures to be updated accordingly. A change to the process that the PHA evaluated is, by definition, a change the procedure may need to reflect.
Taken together, the standard expects the hazard analysis and the operating procedure to describe the same process, the same hazards, and the same protections. For a deeper look at the operating procedure requirements themselves, see our guide to how refineries meet OSHA Process Safety Management procedure requirements.
Why does the connection break down in practice?
Most facilities don't have a PHA problem or a procedure problem. They have a handoff problem between the two. These are the patterns we see most often.
Different teams, different documents. The PHA team is usually a cross-functional group of engineers, operators, and a facilitator working through scenarios in a structured method such as a HAZOP or What-If review. The procedure writer often isn't in the room. What the team meant by "operator responds per procedure" may never be checked against what the procedure actually says.
Procedures credited as safeguards that don't exist as written. A PHA worksheet may list "operator follows startup procedure" as a safeguard against a scenario. If the procedure doesn't contain a clear step addressing that hazard, the safeguard is assumed rather than real. This is one of the most common gaps a procedure review against the PHA uncovers.
Recommendations closed with a caution. When a PHA recommendation is resolved by "add a caution to the procedure," the caution often lands wherever it fits. It may sit after the step it was meant to protect, or it may contain an action the operator is expected to perform but can't sign off.
Different clocks. PHAs are revalidated at least every five years under 1910.119(e)(6). Procedures are revised continuously and certified annually. Between revalidations, small procedure changes can drift away from the assumptions the PHA was built on, and no one notices until the next revalidation or an event.
Human factors treated as a checklist line. The standard requires the PHA to address human factors, but many PHA reports cover it in a short checklist. The detailed human factors work, how a step is written, formatted, and placed, happens in the procedure, if it happens at all.
Six ways to carry hazard analysis into the procedure
The goal is simple to state: every hazard the PHA relies on a procedure to control should be traceable to a specific, usable step. Getting there takes a few deliberate practices.
1. Map PHA scenarios to procedure steps. For each PHA scenario that credits an operating procedure or operator action as a safeguard, identify the exact procedure and step that delivers it. Where no step exists, that is a gap to close. Where the step exists but is vague, that is a gap too. A simple cross-reference between PHA node or scenario numbers and procedure step numbers makes the connection visible to writers, reviewers, and the next revalidation team.
2. Treat procedure-credited safeguards as critical steps. If the hazard analysis depends on an operator performing a step correctly, that step deserves the protections a critical step gets: its own line, a single action, a sign-off or place-keeping mark, and where appropriate, an independent or peer verification. A safeguard buried in the middle of a multi-action paragraph is not much of a safeguard.
3. Turn deviation consequences into limits the operator can use. The PHA evaluates what happens when pressure, temperature, level, or flow drift out of range. Under 1910.119(f)(1)(ii), the procedure has to tell the operator the consequence of that deviation and what to do about it. Write those limits as numbers the operator can read on the board, paired with a clear action, rather than general guidance to "maintain within normal range."
4. Put the caution before the step, and keep actions out of it. When a PHA recommendation becomes a caution or warning, place it immediately before the step it protects, so the operator reads the hazard before taking the action. Keep the caution informational. An action embedded in a note, caution, or warning is one of the 18 error traps we teach, because operators reasonably read cautions as information and can skip the action inside them.
5. Give the operator a clear decision at abnormal conditions. PHA scenarios often turn on what the operator does when something doesn't go as expected. Where the PHA assumes a response, write it as an explicit conditional step: if this condition exists, then take this action. Leaving an in-field decision without clear guidance is another of the error traps, and it is the one most likely to surface under time pressure.
6. Close the loop through management of change and revalidation. Make the procedure-to-PHA cross-reference part of both processes. When a procedure changes through management of change, check whether a PHA-credited step is affected. When the PHA is revalidated, review the current procedures rather than the ones that existed when the last PHA was performed. Bring a qualified procedure writer into the revalidation, or at least have one review the safeguards column.
What this looks like on a single step
Consider a simplified, illustrative example from a fired heater startup. It isn't taken from any specific facility. Suppose the PHA identified an explosion scenario if a pilot is lit before the firebox is adequately purged, and credited the startup procedure as a safeguard.
Before: a typical legacy step.
4.3 Open fuel gas block valve and light pilot. CAUTION: Make sure the firebox has been purged.
The caution arrives after the action. The step bundles two actions. "Make sure" gives the operator nothing to verify or sign. The safeguard the PHA relied on depends on the operator noticing the caution in time.
After: the same step, shaped by the hazard analysis.
CAUTION: Lighting a pilot before the firebox purge is complete can cause a firebox explosion.
4.3 VERIFY firebox purge is complete per Attachment 2. ___ (initials)
4.4 OPEN fuel gas block valve. ___
4.5 LIGHT pilot. ___
4.6 IF pilot does not light within the time specified in the burner management limits, THEN CLOSE fuel gas block valve AND REPEAT the purge per Attachment 2 before re-attempting.
The hazard is stated before the action. The safeguard the PHA credited is now its own verifiable step with a sign-off. The abnormal condition the PHA worried about has an explicit response. Nothing about the technical content changed. The structure did.
Where the writing standard and human factors fit
The OSHA standard tells you what a procedure must contain. It doesn't tell you how to write it so a competent operator executes it correctly under pressure. That is the job of a procedure writing standard.
The Procedure Professionals Association's AP-907-005 Procedure Writing Standard, Revision 4 (December 2024), is the industry's authoritative reference for that craft. Its guidance on step structure, conditional steps, sign-offs and place-keeping, and the placement and content of notes, cautions, and warnings covers exactly the decisions that determine whether a PHA safeguard works on paper or in the field. The standard was developed largely in the nuclear industry, and its principles apply directly to oil and gas operating procedures.
This is also where the human factors requirement in 1910.119(e)(3)(vi) becomes practical. A PHA can note that human factors were considered. The procedure is where human factors are actually applied: one action per step, the hazard before the action, a clear decision at every branch, and a way for the operator to know where they are. When the hazard analysis and the writing standard work together, the procedure stops being a separate document and becomes the operator's version of the PHA.
The bottom line
Your process hazard analysis already knows where your procedures matter most. The scenarios it evaluates, the safeguards it credits, and the deviations it worries about all point to specific steps an operator will one day perform. When those steps are written to the same rigor as the analysis behind them, the PHA works in the field and not only in the report.
If your PHA and your procedures have been maintained on separate tracks, a side-by-side review of PHA-credited safeguards against current procedures is a practical place to start. Procedure Solutions Management helps oil and gas operators assess, convert, and develop operating procedures written to PPA AP-907-005, with the hazard analysis built in. Contact us to talk about your program.
Quick FAQ
How does a process hazard analysis relate to operating procedures? A PHA identifies process hazards and the controls that protect against them. Operating procedures are among the most common administrative controls a PHA relies on, so the PHA effectively identifies which procedure steps must be written and followed correctly.
Does OSHA require procedures to reflect PHA findings? 29 CFR 1910.119(e)(5) requires employers to address PHA findings and recommendations and communicate the resulting actions to affected operating and maintenance employees. Procedures must also address operating limits, consequences of deviation, and safety systems under 1910.119(f)(1), and must be updated through management of change under 1910.119(l).
What is a procedure-credited safeguard? It is a safeguard in a hazard analysis that depends on an operator performing a procedure step correctly, such as verifying a purge before lighting a burner. Those steps should be written and protected as critical steps.
How often should procedures be checked against the PHA? At minimum, during each PHA revalidation, which 1910.119(e)(6) requires at least every five years, and whenever a procedure change through management of change affects a PHA-credited step. Many facilities also include the cross-check in the annual procedure certification under 1910.119(f)(3).


