Evidence-led Cause Mapping for PSM

Turn an incident into a clear, review-ready investigation.

Capture the problem, timeline, causes, evidence, work process, and actions in one focused workspace. Built for process-safety teams that need to understand what happened and decide what to improve.

Get Early Access Try the Cause Map →

"intelligence in every layer of protection."

The Fragmentation Problem

Your engineers run the same incident through three disconnected tools — re-typing data at every step, introducing errors by design.

hazops_study

Teams spend weeks in spreadsheets. Hundreds of deviation rows. No machine-readable output. Findings trapped in a PDF.

Tool 1 of 3

lopa_calc

LOPA engineers rebuild every hazard scenario from scratch. No link to the HAZOP. Wrong data. Duplicated effort. Compliance risk.

Tool 2 of 3

rci_report

Root cause findings live in isolation — never linked to the HAZOP that could have predicted the event, or the LOPA that quantified it.

Tool 3 of 3
The cost: Re-entry errors, audit trail gaps, repeat incidents, and regulatory non-compliance — caused entirely by tool fragmentation that is 100% preventable.

root_cause_map — Available now

A connected investigation workspace. Built for process-safety engineers.

Start with the incident context, build an evidence-led cause map, and carry candidate solutions into an action plan. Keep the investigation, supporting material, and follow-up in one portable Cause Map file.

  • Build and automatically lay out goal-to-cause maps
  • Capture incident context, a sortable timeline, and evidence notes, photos, or video
  • Map the work process with steps, decisions, and problem points
  • Sync possible solutions into an owner, due-date, status, and evidence action table
  • Save a portable .causemap.json file or opt into on-device autosave
TPC Port Neches Demo → BP Texas City Demo → Join the Beta

The connected PSM roadmap

Today: a focused Cause Map workspace. Next: the links, review controls, and analysis modules that turn each investigation into lasting process-safety learning.

Next

Review & audit history

Named reviewers, approvals, version history, and an exportable investigation record for consistent team review.

Future

HAZOP links

Connect a cause-map finding to its process node, deviation, safeguard, and recommendation—so investigation learnings improve the HAZOP record.

Future

LOPA & barrier links

Trace failed or effective safeguards to LOPA scenarios, with structured barrier data and prompts to review protection layers.

Future

MOC & fault-tree analysis

Open a controlled change from an action, flag the analyses it affects, and extend cause-map findings into quantitative fault-tree analysis.

Why process_safety.ai

Built by engineers who've lived the fragmentation. Designed to make structured investigation easier today—and connected process-safety learning possible next.

One investigation file

Keep the problem outline, timeline, cause map, evidence, work process, and solutions together. Save or move the complete investigation as one portable file.

Visual, evidence-led analysis

Build a clear cause-and-effect explanation, distinguish potential causes from excluded paths, and keep evidence and possible solutions with the relevant cause.

Private by default

Use the tool without an account. Optional autosave keeps drafts in the current browser, and you control when to download or share the investigation file.

Limited Beta — Now Open

Join the teams building safer processes.

Early access to root_cause_map. Shape the connected PSM roadmap. Free during beta — no credit card, no commitment.

No spam. No credit card. Unsubscribe anytime. Your data is never sold. Form submissions are processed by Winterlude; see our privacy notice.