Questions integrity teams ask us.

It does — until the person who maintains it is away, or someone asks how a status was decided. Import your existing workbook, review the column mapping and row-level checks, and see every difference against your own figures before you commit. Your team can keep exporting to Excel whenever it wants.

A fictional operator created for the walkthrough. Every screenshot on this site comes from that fictional tenant; no real operator’s data is shown anywhere, and no real operator is named as a user.

Front End Engineering Consultancy (FEEC), an independent upstream and midstream engineering consultancy. The engineers who write the integrity method profiles also build the product and deliver the engineering services alongside it.

Book a demo and we will walk through the platform on the fictional tenant, then agree the next step: a fixed-fee register health check, a pilot on your own wells, or a subscription. Hosting, permissions and data-processing terms are agreed before any of your data is onboarded.

The method for each well type is written down and versioned, and your integrity policy sets the bands, cadences and tolerances within it. Every assessment records the profile and settings versions it used, so unusual wells are a configuration conversation, not a code change.

Yes. Enter or paste the deviation survey, casing, liner and tubing strings, cement tops and completion equipment, and the platform draws the schematic for vertical, deviated, horizontal and multilateral wells, with the barrier envelopes overlaid. Schematics export as SVG or PNG, and missing inputs are flagged rather than guessed.

Yes. The review walks every well in scope, every overdue test, every open action and every override awaiting approval. Once approved, the period locks; a later change is a restatement with its own reason and approval. The monthly review pack is generated from the locked record.

Each well type — producer, injector or disposal well — is assessed against a method profile written for that type, and one profile never serves another, so a result is never carried across types.

Each monitored annulus carries its own MAWOP/MAP value as master data with its source, date and reference, imported with your register or entered directly. Readings are assessed against that value and the bands in your method profile.

Sustained casing pressure has its own exception path in the method. The platform records the applicable flag and outcome against the annulus, using the criteria set in your tenant policy, and the case stays visible in the monthly review until it is resolved.

Each operator is a separate tenant, isolated by PostgreSQL row-level security. Customer data is held in production only — never in the demo or staging environments — on the shared cloud, on dedicated hosting managed by FEEC, or inside your own infrastructure. A Data Processing Agreement is signed before any data moves.

Upload a CSV or Excel workbook, or paste surveys and tallies straight into the wellbore editor. Columns are mapped, every row is validated, and the reconciliation shows the differences against your register before valid data is committed. The onboarding wizard walks a new tenant through the first import.

BarrierLedger keeps the operator’s register, test records, reviews and assessment history, and produces in-house integrity reports from them. It does not file anything with a regulator or certify compliance; submissions and official well records remain the operator’s responsibility. The regulations page summarises what each regime asks, with its public sources.