Governance

Reviews that lock, changes that leave a trail.

BarrierLedger runs the monthly integrity review, controls who can change a status, and keeps the method, the policy and the inputs behind every result — so the answer to “who decided this, and on what basis?” is always on the record.

Book a demo Read the methodology

The monthly review

Sign the month off with confidence.

The review is a workflow, not a meeting: everything that needs a decision is in front of the reviewer, and the decision is recorded.

Monthly integrity review
Every well in scope is assessed, every overdue test flagged, every open action and pending override reviewed before the period is signed off.
Period locking and restatements
An approved period locks. A change afterwards is a restatement with its own reason and approval, and the original stays on the record.
Overrides with second-person approval
An engineer can override an assessed status with a mandatory reason; it takes effect only once a second person approves it.
Actions register
Corrective actions with an owner, due date and closing evidence, linked to the well, and an ageing dashboard that shows what is slipping.

Method and policy

A policy can change without rewriting the past.

Your integrity policy sets the values; the method fixes the rules. Both are versioned, and every assessment keeps the versions it used.

One method profile per well type
An assessment uses only the profile for its well type, and profiles are versioned, so a result is never transferred from one type to another.
Signed defaults, tenant settings
The effective policy shows which values are platform defaults and which your organisation has changed — an integrity engineer requests a change and a client administrator approves it: bands, cadences, grace periods and tolerances.
Request and approval are separate
An integrity engineer requests a policy change with a reason; a client administrator approves or rejects it, and approval creates a new settings version.
The basis of every result is recorded
Each assessment records its profile and settings versions, input hashes, source-file hashes and engine build, so a changed limit never rewrites history.