Operating Pack 01 · Process Safety Management

Your systems record what happened. Sovel preserves why it happened — and shows when the gap was closed.

When a PHA recommendation is declined or modified, the reasoning is what an auditor asks for three years later — and it's almost never where they can find it. Sovel turns every PHA recommendation disposition into a governed Decision Card: the grounds, the evidence, and a qualified reviewer's sign-off, in one tamper-evident record.

Talk to a founder Work with Sovel

Built on the same evidence base your safety culture is built on — CSB investigations, API / CCPS guidance, OSHA PSM practice. Reviewer-operated. You keep your data; Sovel keeps the audit chain.

Disposition WorkbenchREC-2026-0419 · node PSV-114

Why unwrittenPSV-114 relief recommendation is open; the basis for the prior set point is not in the file.Gap

AI-suggested draft“Likely revised per the 2026 relief study.” — unverified, awaiting a qualified reviewer.Suggested

Governed sign-offGround selected, relief study attached, signed by a qualified reviewer; basis bound to the evidence.Governed

Disposition & rationale

Declined under Not Necessary — the existing relief path is independently protective per the 2026 study. The missing basis is now captured against this recommendation, not left to the next revalidation to rediscover.

SealedAPI 510 inspector · cred #IN-510-4471 · 2026-04-19 14:02 CT

ed25519:9f3c…a71b · evidence-anchored · ALCOA+ retained · illustrative example

01 · The disposition

The disposition is where the reasoning leaks out.

Your PHA / HAZOP team generates recommendations. Most get accepted and tracked to closure. But the ones that get declined or modified are where the audit risk lives — because the rationale for not acting is the hardest thing to reconstruct later.

In most facilities that rationale lives in a free-text “Basis” field, a meeting minute, or a retired engineer's memory. None of those survive:

Basis decay

The conditions that justified declining a recommendation in 2021 — a since-removed interlock, a since-changed operating envelope — are no longer true, and nobody re-checked.

Turnover

The process-safety engineer who wrote the disposition rationale has moved on. The next revalidation team inherits a decision with no defensible reasoning attached.

Revalidation archaeology

Every 5-year PHA revalidation turns into a forensic dig: why did we say no to this last cycle, and is that still valid? That dig is billable consultant-hours your team pays for repeatedly.

This is not a knowledge-management nicety. It is recurring spend — revalidation archaeology hours, audit-prep scramble, declined-recommendation re-litigation — plus a tail risk every PSM leader recognizes: the declined recommendation that an investigation later identifies as the one that mattered, with no documented, qualified basis behind the decision.

02 · The Decision Card

One recommendation. One Decision Card. One sealed record.

A PHA recommendation surfaces — from a HAZOP, a LOPA, a revalidation, a what-if. Sovel walks the disposition through a structured Decision Card.

Step 01Signal

A PHA recommendation is open and undisposed, or marked declined with thin basis. Sovel surfaces it as an issue.

in: REC-2026-0419 open · basis thin

Step 02Question

Sovel asks the right person at the right time the one question only they can answer: on what grounds, and with what evidence?

ask: on what grounds — and what evidence?

Step 03Record

The disposition becomes a governed Decision Card — grounds selected from a structured taxonomy, evidence attached, rationale written, signed off by a qualified reviewer.

bind: ground → evidence + rationale

Step 04Proof

The Card is verified in place and sealed. Who signed what, when, with what evidence — provable, and handed to an auditor as-is.

seal: qualified sign-off · tamper-evident

The recognition

Most PSM teams recognize the finished Decision Card as the artifact they've been reconstructing by hand every revalidation cycle. Sovel produces it once, at the moment of decision, and keeps it.

03 · The grounds

Declining a recommendation, done right.

When a team declines or modifies a PHA recommendation, good practice — CCPS guidance, OSHA PSM enforcement practice, Primatech and peer methodology — recognizes four defensible grounds. Most PHA tools leave this as a free-text box. Sovel makes it a structured, evidence-backed, signed selection.

GroundPlain meaningWhat Sovel attaches

MFEMaterial factual errorThe analysis the recommendation rests on contains a factual error.The corrected fact + its source.

NNNot necessaryThe recommendation isn't necessary to protect employee safety and health.The basis for why the existing safeguards already cover it.

AMAlternative measureA different measure provides an equal or greater level of protection.The alternative, and the evidence it's at least as protective.

INFInfeasibleThe recommendation is not feasible as written.The feasibility constraint + what was done instead.

Defensible best-practice taxonomy — not a CFR-mandated schema. The value is audit-evidence quality and consistency.

The difference

PHA tools record the disposition as free text. Sovel records it as a structured ground, with the evidence attached and a qualified reviewer's sign-off — the difference between “Approved By: J. Smith” in a text box and a defensible, tamper-evident record.

04 · The Disposition Workbench

A working console, not a dashboard

Where the reviewer works.

The Disposition Workbench is the reviewer's screen for the PSM pack. It's a working console, not a dashboard.

Open dispositions, ranked: Undisposed and thin-basis recommendations surfaced and prioritized — the riskiest, oldest, and most-cited first.
Evidence pinned alongside the decision: The recommendation, the relevant P&ID / node / safeguard, prior MOCs and incidents on the same node — pinned next to the disposition so the reviewer signs the pair, not a bare verdict.
Structured grounds, not a free-text box: The reviewer selects the ground (MFE / NN / AM / INF), writes the rationale, and attaches the evidence. The form won't let a disposition close on an empty basis.
Qualified sign-off, tied to the evidence: The reviewer's qualification is part of the record. The Card is sealed when they sign — who signed what, when, with what evidence.
Verified in place: The sealed Card carries a tamper-evident, cryptographically verifiable lineage an auditor can read directly. No export, no reconstruction.

Concept rendering of the Disposition Workbench — an illustrative example of the sealed record, not a live attestation.

Disposition WorkbenchREC-2026-0419 · node PSV-114

Open disposition, rankedPSV-114 relief recommendation is undisposed; the basis for the prior set point is not in the file. Surfaced riskiest-first.Gap

AI-drafted candidate, probationary“Likely revised per the 2026 relief study” — drafted, unverified, awaiting a qualified reviewer. Never the final word.Suggested

Structured ground + qualified sign-offReviewer selects the ground (NN), attaches the relief study, writes the rationale, and signs. The form won't close on an empty basis.Governed

Disposition & rationale

Declined under Not Necessary — existing relief path is independently protective per the 2026 study; basis captured against this recommendation, not left to the next revalidation to rediscover.

SealedAPI 510 inspector · cred #IN-510-4471 · 2026-04-19 14:02 CT

ed25519:9f3c…a71b · evidence-anchored · ALCOA+ retained · illustrative example

05 · Lead, not limit

PSM is the lead. It is not the limit.

Sovel is the cross-system decision-evidence layer — it finds the missing reasoning behind operational decisions and binds a qualified reviewer's sign-off and provenance to it, across work history, logbooks, MOC / CAPA / QMS / EHS records, historian / BAS signals, procedures, training, and inspections.

We lead with PSM because the PHA recommendation-disposition is the single highest-density capture-the-reasoning moment we've found — validated across process-safety discovery conversations. So it ships first, as Operating Pack #1. The same engine renders other regulated closure surfaces. Each ships as its own pack.

Operating Pack #1 — PSMshipping first

PHA recommendation disposition · MOC closure basis · ITPM-frequency basis

Muni water

Sanitary Survey response · AWIA / RRA closeout

NERC

Mitigation Plan closure · CIP change basis

Pharma

CAPA Effectiveness Verification · Part 11 procedure-revision basis

No vertical lock, ever. Choosing the PSM pack first doesn't narrow what Sovel reads. It reads any combination of sources from any CMMS, logbook, or handoff stream — the pack is the vocabulary the closure record renders in, not a wall around your data.

Not a PSM facility? See the other packs — the same engine, packaged per industry.

06 · The continuous surface

The audit is the proof. The continuous surface is the relationship.

A revalidation-cycle Decision Card sprint is the entry. But PSM closure isn't a once-every-five-years event — it rides the continuous-use surfaces.

MOC closeout basis: Every Management of Change carries a disposition reasoning that decays the same way PHA dispositions do. The Workbench captures it as it happens.
ITPM-frequency basis: When a team extends or modifies an inspection / test / preventive-maintenance interval, the basis for that change is exactly the kind of reasoning that goes missing. Same Card, same sealed record.
MOC → mechanical-integrity follow-through: The decisions that flow from a closed MOC into the integrity program, captured and linked.

Over time, the account accumulates a governed, cross-cycle record of every non-routine safety decision and the reasoning behind it — the asset that makes the next revalidation faster and the next audit boring.

07 · Why Sovel finds real gaps from the start

Three primitives already shipped.

01A reviewer-validated knowledge corpus: Sovel has already learned what “missing” looks like across regulated maintenance — built against CSB investigations, FDA warning letters, NERC notices, and API / CCPS / OSHA guidance. So Sovel finds real gaps in your PHA backlog from your first export, not after months of tuning.
02Reviewer governance: Every AI-drafted artifact stays probationary until a qualified reviewer approves it. The AI surfaces the open disposition and drafts a candidate; it never has the final word. The reviewer does. The decision is theirs, signed, and on the record.
03Cryptographically verifiable provenance: Every reviewer decision carries an audit chain a PSM auditor can read — tamper-evident lineage from recommendation through sealed disposition. Audit-evidence quality you can hand over as-is.

The division of labor

FDD watches the sensor. Sovel watches the reviewer.

An override on a setpoint shows up in your FDD layer; the reasoning the operator never wrote into the CMMS — and the PHA disposition that should have caught it — is what Sovel captures.

08 · What your PHA tool doesn't do

What's already in the room — and what Sovel adds.

In the roomWhat it doesWhat Sovel adds

PHA / HAZOP toolsPHA-Pro, SpheraCloud ARA, EnablonRun the study, list recommendations, store dispositions as free text.Enforces a structured ground + attached evidence + qualified sign-off on every disposition, sealed in a tamper-evident record.

CMMS AIMaintainX, UpKeep, eMaint, FiixRetrieves what's in the work order.Finds what was never documented — the disposition reasoning that never hit the CMMS.

FDD / MBCxSkySpark, Aspen Mtell, AuguryWatches the sensor; flags drift and overrides.Complement. Those findings generate Sovel dispositions — Sovel watches the reviewer.

09 · Straight answers

The questions a PSM leader actually asks.

Our PHA tool already records dispositions.: Does it enforce which of the four defensible grounds you're using, make you attach the evidence, and tie the sign-off to a qualified reviewer in a tamper-evident record? Or is it a free-text “Basis” box and an “Approved By” line? That difference is the whole audit.
We'd build this internally.: Let's walk your open PHA recommendations together. If your team can reconstruct and seal these dispositions faster, keep the findings and move on.
No budget for this.: No hardware, no new operator adoption, no change management. One export and a few hours of reviewer time on the dispositions you already owe.
What happens after the audit?: Retainer: ongoing capture of MOC, ITPM, and PHA dispositions as they happen — the continuous surface. The audit is the proof; the retainer is the business.
Is this blockchain on industrial data?: No. Sovel anchors reviewer-decision artifacts — roughly one record per signed disposition — not raw process data. The verifiable chain is invisible to your reviewers; the value is the accumulated, auditable decision history.

10 · Work with Sovel

See what's undisposed in your PHA backlog.

We usually start with a Decision-Card Sprint — a short working pass over the declined or deferred recommendations you already have, turned into signed Decision Cards a named reviewer stands behind. It fits naturally before a PHA revalidation or an audit. What we'd need, and the scope, we settle together on a call.

Talk to a founder Work with Sovel