Getting Started with Asphalyn

Asphalyn is a browser-based workspace for running HAZOP studies, assessing risk against configurable criteria, building LOPA with conditional modifiers, capturing SIF definitions for functional safety review, recording the study team, sessions, and reference documents, tracking actions and incidents, and exporting formal deliverables — including an Action Close-Out Report with per-action sign-off.

This guide walks through a complete study, end to end.

What you will do

• Sign in and create a workspace
• Configure the risk criteria for the workspace — matrix and LOPA threshold
• Create a HAZOP study, add nodes and deviations
• Record one or more scenarios under each deviation
• Assess initial and residual risk on a scenario
• Build a LOPA with IPLs and conditional modifiers
• Capture a SIF definition for functional safety review
• Record the study team, session schedule, and reference documents
• Turn a recommendation into a tracked action in one step
• Link a single action to multiple deviations
• Track actions to closure and export a formal close-out report
• Record and resolve an incident, linked to a node if relevant
• View the complete details of a study at a glance
• Export the study as PDF, Word, Excel, or CSV

Sign in

Asphalyn uses Google sign-in. There are no passwords to manage.

1. Go to the Asphalyn login page.
2. Click Sign in with Google.
3. Choose your Google account and approve access.

Your session lasts 7 days. You will be asked to sign in again after that, or after signing out.

Next: create your first workspace.

Create your first workspace

A workspace is an isolated container for your studies, actions, and incidents. Every study, action, and incident belongs to exactly one workspace, and no data crosses between workspaces.

1. After signing in, click Create Workspace.
2. Name the workspace. Use your company or consulting practice name.
3. Click Create.

You are automatically the Owner of a workspace you create. Owners and Admins can invite other members; see Invite team members below.

You can belong to more than one workspace and switch between them from the sidebar. Your role in each workspace is shown in the workspace list. A single account can create one Free workspace; additional workspaces require a paid plan.

Next: configure the workspace's risk criteria.

Configure risk criteria

Every workspace has a risk criteria policy — the risk matrix and the LOPA acceptability threshold. Both live in Workspace Settings → Risk Criteria and both are applied at the moment new work is created.

The policy is a workspace-level default, not a global one. Two workspaces you belong to can use different matrices and different thresholds. This is deliberate: a refinery HAZOP and a pharmaceutical HAZOP often use different scales.

Open Workspace Settings → Risk Criteria to see three cards: Risk Matrix, Custom Matrices, and LOPA Acceptability Threshold.

Risk Matrix

The matrix in force for new HAZOP rows in this workspace. Asphalyn ships four presets:

• Standard 5 × 5 — the conventional five-level severity and likelihood matrix.
• Safety 5 × 5 (Strict) — same levels, tighter band boundaries, so more combinations land in High and Extreme.
• ISO 31000 (4 × 4) — a four-level matrix aligned with ISO 31000 language.
• Simple 3 × 3 — a compact matrix for smaller or scoping-stage studies.

Every preset level comes with a long-form definition, so assessors scoring a scenario can see what each severity and likelihood level means.

To apply a different matrix:

1. Open the Matrix dropdown in the Risk Matrix card.
2. Pick a preset or one of your custom matrices.

Selecting a value opens a confirmation modal. It shows the current matrix on the left, the new one on the right, and a checkbox:

• Also re-apply to existing HAZOP rows — unchecked by default.

The default behaviour is existing rows keep their original matrix. Every row is snapshotted to whatever matrix was in force at the moment it was created, and changing the workspace default does not re-evaluate that historical assessment. This is the audit-trail behaviour — a signed-off risk assessment must read the same today as it did the day it was approved.

If you check Also re-apply to existing HAZOP rows, every row in the workspace is re-snapshotted to the new matrix. The checkbox is opt-in because the operation is irreversible and it changes historical records. It is used when the workspace's criteria have genuinely shifted and the team has decided that prior work should be re-read against the new criteria.

Re-application is refused if any existing scenario's scores exceed the new matrix's maximum. For example, if the workspace is on a 6 × 6 and you select a 5 × 5, any scenario with a severity or likelihood of 6 blocks the re-application with an error explaining how many are affected. You must either choose a matrix at least as large as your existing scores, or reduce those scores first. This prevents a silent failure where a stored score of 6 has no representation in a 5-level matrix.

Confirming the modal applies the change immediately. There is no separate Save button. The dropdown is disabled while the request is in flight, and a "Saving…" indicator appears next to it. If the request fails, the dropdown reverts to its previous value and an error toast appears.

After a successful change, the workspace's risk criteria are refreshed across the app without a page reload — any HAZOP study you have open in the same session resolves against the new matrix on the next render.

Custom matrices

If none of the four presets match your methodology, define your own.

1. In the Custom matrices card, click New matrix.
2. Name the matrix (required, up to 120 characters).
3. Add an optional description.
4. Define your Severity levels — two to ten. Levels are ordered least to most severe; the score is derived from the position (1 for the first, 2 for the second, and so on). You can add or remove levels, and rename each one.
5. Define your Likelihood levels — two to ten, same rules.
6. Choose 2, 3, or 4 risk bands. The score range 1 to (severity count × likelihood count) is divided into contiguous bands automatically, re-balancing whenever you change the dimensions or the band count.
7. Optionally, click + Add definition under any level to give it a long-form definition (up to 500 characters) — for example, what "Major" severity means in your organisation. Definitions are shown to the team while scoring and are printed in the report's Risk Criteria tables.
8. Check the Preview — it shows the full matrix with the current band colours, and the legend below shows the score range for each band.
9. Click Create matrix.

On success the form closes and an information modal appears. The new matrix is saved but not yet applied. It appears in the Matrix dropdown and the Custom matrices list, but it is not the workspace default until you select it. The modal explains this and reminds you to select it from the dropdown above.

Selecting a custom matrix from the Matrix dropdown is what applies it — and it goes through the same confirmation modal as a preset, with the same re-apply checkbox.

The four preset matrices cannot be edited or deleted. Custom matrices can be deleted from the Custom matrices card, but only if:

• The matrix is not currently the workspace default.
• No HAZOP row is snapshotted to it.

If either condition is violated, deletion is refused with a specific message explaining why. Delete the offending rows, or change the workspace default, then delete the matrix.

LOPA Acceptability Threshold

The workspace's default threshold for the LOPA acceptability check. The industry-standard value for a major-accident scenario is 1 × 10⁻⁵ per year, and that is the default. Change it if your organisation's tolerable risk criteria specify a different value.

1. Enter the new value in the Threshold per year field.
2. Scientific notation is accepted — 1e-5 and 0.00001 are the same number.
3. The value must be a number greater than 0 and less than 1.
4. Click Save Threshold.

Unlike the matrix dropdown, the threshold uses an explicit Save button. Free-text numeric fields are not auto-saved: partial input like 0.00 would fail validation and produce a toast on every keystroke. The Save button is a discrete commit.

Existing LOPA analyses keep the threshold they were created with. Changing the workspace default here affects only new analyses. When a saved analysis's snapshot diverges from the current workspace default, the LOPA panel shows a drift banner — see Run a LOPA below.

Next: create a HAZOP study.

Create a HAZOP study

1. From the workspace, click Setup HAZOP Study.
2. Enter a name (required) and, if relevant, a description, company, project, plant, and unit.
3. Set the status: Draft, In Progress, or Completed.
4. Add a study date if known.
5. Add general notes if relevant — see below.
6. Click Create.

Every study, action, and incident gets a reference number you can use in emails, reports, and audit trails. Studies use HAZ-0001, actions use ACT-0001, incidents use INC-0001, and SIF definitions use SIF-0001, each zero-padded and sequential within the workspace.

You can attach files to the study, such as P&IDs or reference documents, directly from the study form. Attachments are supported at the HAZOP level and at the node level — not yet on actions or incidents. You can edit any field later, and you can delete a study from the study list if it was created in error.

General Notes

The General Notes field on the study form is a free-text area for anything worth recording that does not fit the cause/consequence/safeguard structure of a HAZOP scenario. Typical uses:

• Scope boundaries — what is inside and outside the study
• Assumptions made by the team
• Decisions taken during the study that shape later work
• Observations that apply to the study as a whole rather than a single deviation

General Notes appear in the exported report as their own section, and they are visible from the study's View Complete Details panel. The field accepts up to 5,000 characters and preserves line breaks.

Next: add nodes.

Add nodes

A node represents a section of the process you are examining — a vessel, a line, a unit operation, or any logical boundary you define.

1. Open your study.
2. In the node sidebar on the left, click Create Node.
3. Enter a name and a design intent. Both are required.
4. Click Save.

Node names must be unique within a HAZOP study. You can reorder nodes by dragging them in the sidebar. You can edit or delete a node at any time; deleting a node removes its HAZOP rows and its linked incidents are unlinked.

Files can be attached to a node — a P&ID excerpt, a photograph, or a datasheet.

Collapsing the sidebar. Click the collapse icon at the top-right of the node sidebar. The sidebar shrinks to a narrow rail showing the first two initials of each node. Hover any avatar to see the full node name; click to select it. Your collapsed state is saved and survives page reloads. This is useful during a workshop when you want maximum worksheet width.

Next: add deviations.

Add deviations and scenarios

The worksheet has two levels. Each row is a deviation — a guideword applied to a parameter, such as "More Pressure". Under each deviation you record one or more scenarios: a specific cause, what it leads to, the protection in place, and the risk. A single deviation often has several credible causes with different consequences and different risk, and each one is assessed on its own.

Select a node from the sidebar to see its deviations in a spreadsheet-style table.

Add a deviation

1. Select a node.
2. Click Add Row, or use Add Row Below on an existing row.
3. Pick the Guideword and Parameter.

• Guideword — a strict dropdown. The standard seven values are No, More, Less, As Well As, Part Of, Reverse, and Other Than. You cannot type a free-text value. This is intentional: the guideword vocabulary is closed by design, and "Other Than" is the catch-all for anything the other six do not cover.
• Parameter — a free-text combobox with suggestions. You can pick Pressure, Temperature, Flow, Level, Composition, Viscosity, pH, or Other from the list, or type any value that is not in the list. The dropdown is a convenience, not a constraint.

The deviation row also shows three summary cells:

• Highest Risk — the worst initial and residual risk across the deviation's scenarios. Click it to show or hide the scenarios.
• LOPA — Acceptable when every LOPA on the deviation's scenarios is acceptable, Additional Protection Required when at least one is not, and — when no scenario has a LOPA.
• Scenarios — reads Show N scenarios or Hide N scenarios. On a deviation with no scenarios yet, it shows Add scenario.

Add scenarios

1. On a deviation, click Add scenario (or expand the deviation and click Add scenario below its scenarios).
2. A new empty scenario appears inline with the cursor in its Cause cell.
3. Fill in the columns directly in the table.

The scenario columns are:

• Cause — free text. The event or failure that produces the deviation.
• Consequence — free text. What happens if the cause occurs.
• Category — Safety, Environment, Asset, Business, or Other. Defaults to Safety.
• Safeguard — free text. The existing protection that reduces the risk.
• Risk — click to open the risk inline panel.
• LOPA — click the button to open the LOPA panel for the scenario.
• SIF — click the button to open the SIF definition panel for the scenario.
• Recommendation — free text. What should be done. A recommendation is what makes the scenario eligible for action creation.

Each scenario's menu has Move Up, Move Down, and Delete Scenario. Deleting a scenario removes its risk data, its LOPA, and its SIF definition.

Changes save automatically as you type, with a short delay. You do not need to click a save button.

Keyboard navigation. Press Tab or Shift+Tab to move between editable cells. Focus skips the Risk, LOPA, and SIF cells, since those open panels rather than accept typing.

If a save fails. A red retry badge appears on the failed cell, and a toast appears with a Retry action. Click either to re-fire the write. Do not type over a failed cell expecting it to save — click the badge.

Row actions. Each deviation row has a set of icons for:

• Add Row Below — insert a new empty deviation immediately below this one.
• Duplicate Row — copies the deviation and its scenarios into a new row. LOPA, SIF, actions, and comments are not copied. The duplicate inherits the source row's risk matrix snapshot, not the workspace default.
• View Actions — opens the list of actions linked to this deviation.
• Comments — opens the comment panel for this deviation. Posting comments requires the Team plan; on the Professional plan the panel is view-only, and on the Free plan it shows an upgrade prompt.
• Create Action — creates a general action without a recommendation.
• Delete Row — removes the deviation, all of its scenarios with their risk data, LOPA, and SIF definitions, and any actions created from it.

You can also reorder deviations by dragging the drag handle at the start of the row.

Next: assess risk.

Assess risk

Each scenario has an Initial Risk and, optionally, a Residual Risk.

1. On a scenario, click the Risk cell. The risk inline panel opens.
2. Select a Severity and a Likelihood for Initial Risk. The definition of the selected level is shown beneath each dropdown, so the team scores against the same meaning.
3. Asphalyn calculates the resulting risk level against the deviation's matrix.
4. If safeguards reduce the risk, select a Severity and Likelihood for Residual Risk.

Every deviation uses the matrix that was in force at the moment it was created, and all of its scenarios are scored against that matrix. A deviation created while the workspace was on a 5 × 5 will present severity and likelihood scores of 1–5 forever, even if the workspace default has since moved to a 6 × 6. A deviation created under a 6 × 6 presents scores of 1–6. The matrix name and dimension are shown at the top of the risk panel so there is no ambiguity about which criteria are being applied.

This is the audit-trail behaviour. If the workspace's risk criteria change after the study is signed off, existing assessments are not silently re-read against the new criteria. If you want them re-read, an admin must explicitly apply the new matrix to existing rows from workspace settings — see Configure risk criteria above.

Residual risk requires an initial risk to be set first. The residual selects are disabled until both initial severity and likelihood are chosen. You can revisit and change either at any time; the calculated level updates immediately.

Click View Risk Matrix at the bottom of the panel to see the full grid for the matrix with the current cell highlighted. If different deviations in the same study use different matrices — which happens when the workspace default changed mid-study — each one is shown against its own criteria.

The risk level is derived from the matrix and its bands. A given score maps to Low, Medium, High, or Extreme according to how the matrix's bands were defined. The four presets use different band boundaries (the "Safety Strict" preset places more scores in High and Extreme than the "Standard" preset), and custom matrices define their own bands.

Next: run a LOPA.

Run a LOPA

If a scenario needs a Layer of Protection Analysis, open the LOPA panel from that scenario by clicking its LOPA button. Each scenario can have its own LOPA.

Initiating event

1. Enter the Initiating Event — a short description of what starts the scenario.
2. Enter the Initiating Frequency — occurrences per year.

Independent Protection Layers

Add each IPL that reduces the scenario:

1. Click Add IPL.
2. Enter a Name (for example, "High-pressure alarm" or "PSV-2204").
3. Choose a Type: Alarm Operator, SIS, Relief Device, Physical Barrier, Interlock, or Other.
4. Enter the PFD — the probability of failure on demand, a number between 0 and 1.
5. Add any Notes.

Each IPL's PFD multiplies into the residual frequency.

Conditional modifiers

Conditional modifiers are the probability factors applied between the initiating event and the IPLs. Asphalyn supports the three that IEC 61511 and the CCPS LOPA methodology expect:

• P(Ignition) — probability that the release ignites. Relevant for flammable scenarios. Leave blank for toxic-only or non-flammable scenarios.
• P(Personnel Presence) — probability that personnel are in the affected area. Relevant when occupancy is not continuous.
• P(Fatal Injury) — probability of fatality given exposure.

Each modifier is optional. A modifier you leave blank is treated as not applicable, meaning its factor is 1. Existing LOPA analyses without modifiers behave exactly as before — the residual frequency is unaffected until you enter a value.

The combined conditional modifier and the residual frequency both update live as you type.

Calculation

Asphalyn calculates:

• Residual Frequency = initiating frequency × P(Ignition) × P(Personnel Presence) × P(Fatal Injury) × product of all IPL PFDs
• Risk Reduction Factor = initiating frequency ÷ residual frequency
• Status = Acceptable if residual frequency is below the analysis's threshold; otherwise Additional Protection Required

The acceptability threshold

The threshold is a workspace-level default, but each LOPA analysis snapshots the threshold that was in force at the moment it was created. A workspace on the default 1 × 10⁻⁵ per year produces analyses evaluated against 1 × 10⁻⁵. If the workspace default later changes — say the organisation's tolerable risk criteria move to 5 × 10⁻⁵ — that change applies to new analyses only. The existing ones keep their original threshold, because re-reading a signed-off LOPA against a new criterion is a decision the team must make explicitly.

When a saved analysis's snapshotted threshold differs from the current workspace default, the panel shows a drift banner. It reads:

Workspace policy has drifted. This analysis is evaluated against the threshold that was set when it was created (X per year). The workspace default has since changed to Y. Per process safety revalidation practice, this analysis should be re-evaluated against the current criterion.

The banner has a Re-evaluate button. Clicking it:

1. Snapshots the current workspace threshold onto the analysis.
2. Recalculates the residual frequency, risk reduction factor, and acceptability verdict against the new threshold.
3. Writes an activity log entry recording the change.
4. Removes the banner and shows a success toast.

Re-evaluation is user-initiated. Asphalyn does not silently re-evaluate any LOPA. If the new threshold makes a previously-acceptable scenario fail, the status flips to Additional Protection Required — which is exactly why the decision belongs to the user and not to the system.

If the analysis's threshold was explicitly overridden at creation — which happens when a manual threshold is passed to the create-or-update call — the panel shows a Manual override in effect banner instead of the drift banner. Manual overrides are preserved across ordinary edits. Clicking Re-evaluate replaces the override with the current workspace threshold and resets the source to SNAPSHOT; the drift banner's Re-evaluate action is therefore also how you clear a manual override.

Ordinary edits — changing the initiating event, adding an IPL, adjusting a conditional modifier — do not change the threshold snapshot or the threshold source. Editing an analysis and clicking Save Changes keeps whatever threshold was already in effect.

Conclusion

Add a conclusion comment if relevant, then click Save Changes.

Not every scenario needs a LOPA. Skip this step for scenarios where it does not apply — the LOPA panel is entirely optional.

Next: capture a SIF definition.

Capture a SIF definition

A SIF (Safety Instrumented Function) is the instrumented protective function that will be verified against a target SIL by a functional safety engineer. Asphalyn captures the SIF definition at the HAZOP stage so the register can be handed to the engineer running the SIL verification — it does not perform that verification itself.

What Asphalyn does and does not do. The SIF panel captures the definition — the function, target SIL, sensor, logic solver, final element, and the operational parameters the verification engineer needs. It does not compute PFDavg, does not claim an achieved SIL, and does not replace the verification. That work belongs to the functional safety engineer and their own tool.

Open the SIF panel

1. On a scenario, click the SIF button in the SIF column.
2. The SIF panel opens. On a scenario with no existing SIF, the fields are empty and no reference is shown.

Function

The Function Description is required. Write a short statement of what the SIF does — for example, "Trip fuel gas to the reformer firebox on high-high reformer outlet temperature." This is the sentence that will appear in the SIF register.

Definition

The remaining fields are optional. Fill in as many as are known at the HAZOP stage; the verification engineer can complete the rest.

• Target SIL — the required SIL level, e.g. "SIL 2". This is the target set by the LOPA or by the company's tolerable risk criteria.
• Sensor — the sensor or sensor group, e.g. "2 × Type K thermocouple, 1oo2 voting".
• Logic Solver — the logic solver that executes the SIF, e.g. "Safety PLC SIS-01".
• Final Element — the actuator or valve that brings the process to a safe state, e.g. "SDV-201 fuel gas isolation valve".
• Voting Architecture — the redundancy scheme, e.g. "1oo2", "2oo3".
• Proof Test Interval — how often the SIF is proof-tested, e.g. "12 months".
• Safe State — what the SIF drives the process to, e.g. "Fuel gas isolated, firebox purged, reformer depressurised to flare".
• Response Time — the required time from sensor trip to safe state, e.g. "< 2 s".

Click Save Changes to save. The panel then shows the SIF reference (SIF-0001, SIF-0002, and so on) next to the title. The reference is generated on first save and is stable — editing the SIF does not change it.

A scenario can have at most one SIF definition, matching the LOPA cardinality. Delete a SIF with the trash icon in the panel header; it is removed immediately with a confirmation.

SIF definitions are compiled into a SIF Register section in the exported report — a flat table listing every SIF in the study. That register is what you hand to the verification engineer.

Next: record the study team.

Record the study team

A formal HAZOP report names the people who took part. The study team register captures this.

1. Open the study workspace.
2. Click Team & Sessions in the tab strip at the top of the workspace.
3. The Team sub-tab is shown by default.
4. Click Add Team Member.

Fill in:

• Name (required) — the person's name.
• Role (required) — for example, Team Leader, Scribe, Process Engineer, Operations Supervisor.
• Organization (optional) — the company or practice the person represents.
• Email (optional) — a contact address.

The team list appears in the exported report as a "Study Team" section. It is also the pool of people you mark present or absent when recording session attendance.

Edit or remove a team member at any time using the pencil and trash icons in the row. Removing a team member also removes their attendance entries for every session.

Next: record sessions.

Record session schedule and attendance

For a study that runs over multiple days or weeks, the session schedule records when the team met and who was present at each meeting.

1. In the Team & Sessions tab, click the Sessions sub-tab.
2. Click Add Session.

Fill in:

• Date (required) — the day the session took place.
• Start time and End time (both required) — 24-hour format.
• Location (optional) — for example, "Conference Room A" or "Microsoft Teams".
• Agenda (optional) — what the session covered.
• Notes (optional) — anything else worth recording.

Each session gets a session number (Session 1, Session 2, and so on) assigned automatically in the order sessions are added.

Mark attendance

Click a session row to expand it. An attendance editor opens, listing every member of the study team. For each person, choose:

• Present
• Partial — for people who joined late, left early, or attended remotely for part of the session.
• Absent

Click Save Attendance when done. The collapsed session row shows a summary — for example, "5 present, 1 partial, 1 absent" — so you can see the shape of each session at a glance without expanding it.

Attendance is saved as a full set each time: if you clear a person's status, their attendance entry for that session is removed on save.

The exported report contains the session schedule and an attendance matrix. Above eight sessions the matrix is replaced with a per-session stacked list, so the section stays readable on the page.

Next: record reference documents.

Record reference documents

The reference documents register lists the P&IDs, PFDs, procedures, standards, and other inputs the study was based on.

1. In the Team & Sessions tab, click the Documents sub-tab.
2. Click Add Document.

Fill in:

• Title (required) — for example, "P&ID — Reformer Furnace and Burner System".
• Category — a combobox with common values (P&ID, PFD, Cause & Effect, Datasheet, Procedure, Standard, and others). You can also type a value not in the list.
• Document No. — the internal document number.
• Revision — for example, "Rev C".
• Document Date — the date on the document.
• Notes — a short description of what the document covers.

The register appears in the exported report as a "Reference Documents" section. The documents themselves are not embedded in the export — a 400 MB P&ID bolted into a PDF makes the report unusable. The register records what was consulted; you hand the files over separately.

Next: create an action from a recommendation.

Create an action from a recommendation

Once a scenario has a recommendation, you can turn it into a tracked action without leaving the worksheet.

1. On the scenario, click the Create Action from Recommendation icon (the clipboard) in its Actions cell.
2. Fill in Assignee, Responsible Person, Department, Designation, Due Date, and Priority. The title is pre-filled with the recommendation; click the pencil icon next to "From Recommendation" to edit it before creating.
3. Click Create Action.

The action is created with the recommendation as its title (or your edited title), linked back to the scenario's deviation, and marked as recommendation-derived. The deviation's action count increments.

You can also create actions with no HAZOP link, directly from the Actions section, and mark their source as General. Actions can also be created from an incident.

Next: link an action to multiple deviations.

Link an action to multiple deviations

A single remediation often closes out the same underlying issue across several deviations. Instead of duplicating the action, link one action to every deviation it addresses.

1. Create an action from a deviation or scenario, or open an existing HAZOP-sourced action from the Actions list.
2. Near the top of the action form, find the panel titled Also applies to HAZOP rows.
3. Open the multi-select and choose the additional deviations this action addresses. The current deviation is not shown — it is the action's primary source and cannot also be a secondary link.
4. Save the action.

Every deviation the action is linked to shows the action in its Actions panel, and its action count badge includes it. The Actions list shows a (+N more) indicator next to the action title; click it to see every linked row.

The Additional Rows panel appears only on actions whose Source Type is HAZOP Row. It does not appear for general actions or for incident-sourced actions, since those have no primary HAZOP row to extend.

If your study has only one deviation, the panel shows "No other rows in this study" and is disabled — there is nothing else to link.

In the exported report, each source reads like Node 2 · Deviation 2.3. An action with multiple links shows a bulleted list of sources in the Close-Out Report and a comma-separated list in the register.

Next: track and close actions.

Track and close actions

Every action has a status: Open, In Progress, or Closed.

1. Open the Actions list from the sidebar to see all actions across the workspace.
2. Update status, assignee, responsible person, department, designation, priority, or due date from the row itself or from the action's detail page.
3. To close an action, set its status to Closed and enter a closure comment describing what was done.

Closed actions retain their closure comment and closed date for the audit trail.

Import actions

If you have existing actions to bring in, click Import Actions from the Actions list.

1. Download the template as Excel (.xlsx) or CSV. Keep its first row: it identifies the template version.
2. Fill in one action per row. Columns are matched by their header, so their order does not matter. Due dates must use the YYYY-MM-DD format, for example 2026-05-31; other date formats are rejected.
3. Upload the file as CSV, XLS, or XLSX, up to 200 rows. A file with more rows is refused as a whole and nothing is imported; split it and upload each part.

A validation viewer shows any errors before upload, so you can correct or remove rows in place. If some rows still fail on upload, the others are imported and the failed rows stay in the viewer with their errors. You can download an error report, fix it, and upload it again.

Import History lists past imports with their counts. Import details are kept for 90 days, then cleaned up automatically on your next activity in the workspace. Only the import summary (counts and status) is kept longer. The person who ran an import can delete its details earlier at any time with Delete details.

Export actions — list or close-out report

When you export actions, choose a layout:

• List — a single flat register with one row per action. Good for tracking and for reading in a spreadsheet.
• Close-Out Report — a formal deliverable. A seven-column action register followed by one response sheet per action. Each response sheet shows the action's source (one or more deviations, or an incident), title, description, assignee, responsible person, department, designation, priority, category, type, due date, status, closed date, an evidence / implementation notes field, a closure comment field, and a sign-off table with Prepared By, Reviewed By, and Approved By rows. This is the format you send to a client, a regulator, or an internal audit.

The Close-Out Report layout is available in PDF, Word, and Excel. CSV always falls back to the List layout, because CSV cannot represent the multi-page per-action structure.

Next: record incidents.

Record incidents

Incidents can stand alone or be linked to a HAZOP node.

1. Open Incidents from the sidebar, or click Create Incident from a node's action menu.
2. Enter a title, description, incident date, severity, category, and type.
3. Assign an owner if known.
4. Click Create.

Incident fields:

• Severity — Low, Medium, High, or Critical.
• Category — Safety, Operability, Environment, Asset, Production, Cyber, Procedure, Maintenance, Compliance, or Other.
• Type — Near Miss, Minor Incident, Major Incident, Equipment Failure, Process Deviation, Spill / Leak, Injury, Fire / Explosion, Observation, or Other.

An incident's status moves through Open, Under Review, Resolved, and Closed. Resolving an incident requires a resolution comment. Closing an incident sets its closed date.

You can generate an action directly from an incident. You can link or unlink an incident from a node at any time — linking is useful when an incident occurred at a specific piece of equipment that is also a HAZOP node.

Incidents can also be bulk-imported with Import Incidents, the same way as actions: download the .xlsx or CSV template, use YYYY-MM-DD for incident dates, and upload up to 200 rows per file. Import History and the 90-day retention of imported row details work the same way.

Next: view complete study details.

View complete study details

The study header shows the reference number, status, and study name. For everything else about the study, open the details panel.

1. Open the study.
2. Click View Complete Details below the study name.

The panel shows:

• The reference number and status badge
• The study's description, if one was entered
• Summary counts — nodes and deviations (HAZOP rows)
• Study Information — Company, Project, Plant, Unit, Study Date, and an Attachments item with a button to open the attached files
• General Notes, if any were entered

This is the single place to look when you want to know what the study is, what it covers, and what supports it — without scrolling the worksheet.

Next: export the study.

Export the study

1. Open the study you want to export.
2. Click Export HAZOP Study.
3. Choose a format.
4. Select which sections to include.
5. For the Actions section, choose a layout: List or Close-Out Report.
6. Click Export.

Sections

The export modal offers the following sections:

• Cover Page
• Table of Contents
• HAZOP Rows
• LOPA
• SIF Register
• Study Team
• Session Attendance
• Methodology
• Reference Documents
• Actions
• Incidents

Selecting HAZOP Rows is required for the sections that are part of the composed study — LOPA, SIF Register, Study Team, Session Attendance, Methodology, and Reference Documents. Unchecking HAZOP Rows disables those six, since the server renders them inside the HAZOP-rows block.

Sections that have no data are omitted from the report, even if their checkbox is on. A study with no attendees will not show a Study Team section, and the following sections' numbers shift up accordingly.

The export modal notes that each deviation may contain multiple scenarios; the report lists every scenario.

The report order in the exported file is:

1. Cover Page
2. Table of Contents
3. Executive Summary
4. Study Summary
5. Risk Distribution
6. Study Information
7. General Notes
8. Methodology
9. Reference Documents
10. Study Team
11. Session Attendance
12. HAZOP Analysis
13. SIF Register
14. Incidents
15. Actions
16. Sign-Off

Executive Summary. Included whenever HAZOP Rows is selected. It states the scope, the counts (nodes, deviations, scenarios, actions, incidents), up to five key findings — the deviations with the highest initial risk, each shown with its worst scenario's reference, the full cause, and initial and residual risk — the open, critical-and-high, and overdue action counts, and a conclusion. The conclusion is built only from the study's data: its status (it says the study is complete only when the status is Completed), the counts, the initial and residual risk by level, recommendations and actions, and LOPA and SIF counts when there are any.

Risk Distribution. Initial and residual risk counts by level, counted per scenario, plus action and recommendation statistics. It is followed by the risk criteria for every matrix used in the study: a coloured severity × likelihood grid with its band legend, and the severity and likelihood levels with their definitions.

Methodology. Describes how the study was run, using only what the study holds: the technique, the scope in numbers, the guidewords and parameters used, the risk matrix and its bands, the scenario categories, and the LOPA and SIF counts. It makes no claim of compliance with a standard; a standard is named only if it appears in your reference documents. Uncheck Methodology in the export modal to leave it out.

HAZOP Analysis. For each node, two tables. Deviation & Scenario Analysis lists the reference, guideword, parameter, cause, consequence, category, and safeguard. Risk & Recommendation lists the reference, initial risk, recommendation, and residual risk. Each node is followed by the LOPA analyses of its scenarios.

References. Deviations are numbered within their node: 2.3 is the third deviation of node 2. When a deviation has more than one scenario, each scenario adds a third number — 2.3.1, 2.3.2. Deviations with no content are left out of the report, with a note saying so; the numbers of the remaining deviations do not change. A one-line legend under each Deviation & Scenario Analysis table explains the two forms.

Sign-Off. The final section opens with a Document Control table — document number, study status, report date, prepared by, and a blank Revision field to fill in by hand — followed by signature and date lines for Facilitator, Reviewed by, and Approved by.

Risk criteria in the report

Every scenario in the HAZOP Analysis section carries its deviation's matrix name and dimension, so a reader can see which criteria it was assessed against. If the workspace default changed mid-study, and different deviations carry different matrices, each one's matrix is shown against it. This preserves the audit trail — a reader never has to guess which criteria produced a given score.

Formats

The formats available depend on your plan:

• Free plan — one PDF export for the lifetime of the workspace. Word, Excel, and CSV are visible in the format dropdown but disabled. Selecting PDF and clicking Export opens a confirmation dialog; confirming it consumes your single free export. It does not renew. The embedded Actions section is fixed to the List layout, since the close-out report is a paid-plan layout.
• Professional and Team plans — unlimited exports in PDF, Word, Excel, and CSV, with no restriction on sections or layouts.

PDF and Word reports are A4. The report is portrait, with one landscape block for HAZOP Analysis, SIF Register, Incidents, and Actions; the standalone Actions and Incidents exports are landscape. Every page has a page header (study reference and name) and a footer with the page number. The Table of Contents lists every section that will render, with its page number, and each entry links to its section in both formats. In Word, the page numbers fill in when Word asks to update fields on open; if it does not ask, or you declined, press Ctrl+A then F9. Excel exports split the study across multiple sheets — one for each section that has data — and print A4 landscape. Excel and CSV list one row per scenario.

Actions and incidents can also be exported on their own, without including the rest of the study — but only on a paid plan. On the Free plan, the Actions and Incidents export buttons route to the upgrade dialog.

Next: invite team members.

Invite team members

This section applies to workspaces on the Team plan.

1. Go to workspace settings and open Members.
2. Click Invite Member.
3. Enter the email address and choose a role: Admin or Member.
4. Click Send Invitation.

Only Owners and Admins can invite members. You cannot invite someone directly as Owner. You can cancel a pending invitation at any time from the Members page.

Team plan also enables:

• Comments on HAZOP rows — any member can leave a note on a specific deviation. Comments are single-level (not threaded). Authors can edit or delete their own comments.
• Activity logs — record who changed what, with before-and-after values, filterable by user, resource type, action, and date range.

Activity logs are visible from the Recent Activity sidebar entry.

Next: manage your subscription.

Manage your subscription

Each workspace has its own plan and subscription, billed independently of any other workspace you belong to. There is no per-seat pricing.

To change plans, go to workspace settings and open Billing. Only the workspace Owner can manage billing. You can upgrade, downgrade, cancel, or resume a subscription here. The billing portal opens in a new tab, where you can update your payment method and view invoices.

Cancelling stops future renewals; the workspace keeps access until the end of the current billing period. You can undo a scheduled cancellation before it takes effect.

If you run into anything that is not covered here, contact us through the address at the bottom of this site.