Header row
Formatted, frozen, with set column widths so the sheet scrolls cleanly on long registers.
HAZOP worksheet Excel template.
A HAZOP, hazard and operability worksheet is the process safety study document. One row per node-parameter-deviation tuple carries the cause, consequence, severity, likelihood, the existing safeguards, the recommendation if additional protection is required, the recommendation owner, and the closure status. The guide-word method follows IEC 61882, the HAZOP application standard. The seven standard deviation modes are NO, MORE, LESS, REVERSE, AS WELL AS, PART OF, OTHER THAN, each applied to every parameter at every node.
What the template carries.
HAZOP study worksheet template with 13 columns covering node, parameter, deviation guide word, cause, consequence, severity, likelihood, existing safeguard, recommendation, recommendation id, assignee, status, and closure reference. Pre-formatted with frozen header, auto-filter, and 48 blank rows.
By Tagsight Team·Published Feb 17, 2026·Reviewed Aug 7, 2026
- Format.xlsx
- Columns13
- Rows48 blank
- Opens inExcel · Sheets · LibreOffice
Every column, defined.
13 columns mapped to how a hazop study worksheet is issued on a real project. Dropdown columns enforce values; free-text columns let house notation preserve as drawn.
| # | Column | Type | Description |
|---|---|---|---|
| 01 | Node ID | Text | HAZOP node identifier |
| 02 | Node Description | Text | Process boundary covered by the node |
| 03 | Parameter | List | Flow, Level, Pressure, Temperature, Composition, Other |
| 04 | Guide Word | List | No, More, Less, Reverse, As Well As, Part Of, Other Than |
| 05 | Cause | Text | Specific cause of the deviation |
| 06 | Consequence | Text | Hazard consequence if deviation occurs |
| 07 | Severity | List | Risk matrix severity, 1-5. |
| 08 | Likelihood | List | Risk matrix likelihood, 1-5. |
| 09 | Existing Safeguard | Text | Current protective layer |
| 10 | Recommendation | Text | Recommended action |
| 11 | Recommendation ID | Text | Unique recommendation identifier |
| 12 | Assignee | Text | Action owner |
| 13 | Status | List | Open, In Progress, Closed, Rejected |
What each HAZOP worksheet column is for, and who fills it
| Column | What goes in it | Filled by |
|---|---|---|
| Node ID, Node Description | The section of process under study, bounded by one design intent. A node is a line or a vessel with a single intent, not a whole unit. | Facilitator, before the session |
| Parameter | The process variable being deviated: flow, pressure, temperature, level, composition. | Facilitator, before the session |
| Guide Word | No, More, Less, Reverse, As Well As, Part Of, Other Than, applied to the parameter to generate the deviation. IEC 61882 defines the set. | Facilitator, in session |
| Cause | The credible initiating event that produces the deviation. One row per cause, never a list inside one cell. | The team, in session |
| Consequence | What happens if nothing intervenes. Written unmitigated, or the risk ranking beside it means nothing. | The team, in session |
| Severity, Likelihood | Ranked against the project risk matrix. That matrix belongs in the front of the workbook, not in somebody's head. | The team, in session |
| Existing Safeguard | Protection already in the design. A safeguard claimed here that is not on the P&ID is one of the most common audit findings. | The team, checked against the drawing |
| Recommendation, Recommendation ID | The action, and a stable identifier that survives into the action tracker and the safety requirements specification. | Facilitator, in session |
| Assignee, Status | Who owns it and where it stands. This is what turns a study into a closeable action list. | Project, after the session |
What ships in the file.
Worked example
One filled row shows the format for every column so the schema is clear before the engineer starts typing.
Auto-filter
Enabled on every column. Pivot by any field without a single formula.
48 blank rows
Pre-formatted and ready to paste into. Extends without breaking the dropdown or filter range.
Enforced dropdowns
Categorical columns (priority, signal class, status, type) enforce values so the register stays clean.
Cross-tool
Plain .xlsx. Opens cleanly in Excel, Google Sheets, and LibreOffice. No macros, no add-ins.
No tracking
No macros, no add-ins, no telemetry inside the file. Edit and ship.
Quiet signoff
A single mint-italic line at the bottom: Drag a source document at tagsight.io to fill this automatically. Easy to delete.
Extract from a source document instead.
Upload the source document instead and the same 13-column schema this template defines comes back populated. Type, tag, vendor, model, and per-row metadata come from the document itself.
Scanned binders, CAD-exported PDFs, and image scans all work. House conventions, vendor-specific forms, and dialect-specific tag schemes read as drawn.
Common questions
What is a HAZOP study worksheet.
The HAZOP, hazard and operability worksheet is the process-safety register of every deviation considered during a HAZOP study. One row per, node, parameter, guide word, cause combination with consequence, existing safeguard, recommendation, and assignee. It is the document the LOPA team reads to scope independent protection layers and the action tracker reads to drive closure.
What columns are in this template.
Thirteen columns. Parameter, Guide Word, Severity, Likelihood, and Status are dropdowns. The seven guide words, No, More, Less, Reverse, As Well As, Part Of, Other Than are enforced. Deviation rows that fall outside the standard set are typically a sign the parameter list needs revisiting.
Does this drive the LOPA worksheet too.
No. LOPA, layer of protection analysis is a separate worksheet that takes the high-consequence HAZOP rows as input. The two documents are linked at the recommendation level. A HAZOP recommendation that calls for additional protection becomes a LOPA scenario with an independent protection layer count.
What is the difference between a HAZOP worksheet and a HAZOP report.
The worksheet is the row-by-row record produced in the session: one row per node, parameter and guide word, carrying the cause, consequence, safeguards and recommendation for each. The report is the document written around it, holding the scope, the team, the risk matrix, the methodology and the conclusions, with the worksheet as its central appendix. Auditors read the report. Engineers work from the worksheet.
How many rows should a HAZOP worksheet carry per node.
One row per credible deviation, meaning one per parameter and guide word combination the team judges to have a credible cause. A node with five parameters against seven guide words has thirty-five combinations, of which perhaps eight to fifteen are credible on a typical process node. Recording only the credible ones is correct. A blank row for every combination makes the worksheet unreadable and buries the real findings.
Should severity and likelihood be ranked before or after safeguards.
Both, and the worksheet has to be explicit about which it is showing. The unmitigated ranking, before safeguards, is what justifies the recommendation. The mitigated ranking, after safeguards, is what shows residual risk. A worksheet carrying one ranking without saying which it is cannot be reviewed, and that is a routine audit finding.
Can a HAZOP worksheet be reopened during a revalidation.
Yes, and the recommendation identifier is what makes it possible. A revalidation checks whether the original causes and safeguards still hold against the current P&ID. Stable identifiers let the revalidation reference the original finding instead of restating it, so the history of a hazard survives across studies.
What file format should the worksheet be in for handover.
Whatever the operating company process safety information system accepts, which in practice is nearly always a spreadsheet with one row per deviation. Keep the column order stable across studies on the same asset, because the value of the register is comparison across revalidations.
Related.
Run it on your drawings.
The template is a manual starting point you fill yourself. Upload the source document instead and the same schema comes back populated.