Production that has no well
A well reports volumes in the production file but is absent from the well master. You are paying for barrels with no title record behind them (DR001).
haql-dataroom · A&D dataroom QC
Before a deal closes, the dataroom's production, well master, RRC-reported volumes, revenue statements, severance-tax lines, reserve summary and LAS headers have to agree with each other. They rarely do. haql-dataroom scrubs the package offline, cross-checks every table against every other, and names each contradiction to the row — so you negotiate on facts, not on the seller's spreadsheet.
Run it yourself: download the standalone binary — a directory in, a red-flag sheet out. Fully offline, deterministic, every finding traceable to a source row.
Read the public guide: what it does, what it checks and what it does not do →
# generate a synthetic dataroom (7 tables + LAS) haql-dataroom demo # scrub the package before you bid haql-dataroom dataroom_demo --no-open --report dataroom-audit.json # result rows=26 wells/leases=4 exceptions=54 critical=0 high=44 medium=8 low=1 info=1 by rule: DR001_ORPHAN_PRODUCTION 6 DR003_RRC_VARIANCE 12 DR007_PRODUCTION_WHILE_ABANDONED 14 DR013_SEVERANCE_BACKCHECK 6 … (DR001–DR015) red-flag sheet → dataroom-audit.html report → dataroom-audit.json
Header names can be whatever the seller used — the tool maps them to canonical roles by synonym, and recognises the files by filename.
What it is
No data-room portal. No upload. Just the files the seller handed over, checked against each other the way a technical reviewer should check them — but exhaustively and reproducibly.
Production, well master, RRC volumes, revenue, severance tax and reserve CSVs plus any LAS well-log headers. Column names are mapped to canonical roles by synonym and the files are recognised by filename hint; --map ROLE=PATH overrides the guess. Sensitive, so the whole thing runs on your machine.
A dataroom audit (JSON + HTML): a self-contained offline red-flag sheet with one record per cross-table finding, each traced to its source row, plus a machine-checkable JSON for your own models.
Why you need it
None of them is visible in any single table. Each one takes an analyst cross-referencing two exports by hand — which is exactly the work that runs out of time before the bid.
A well reports volumes in the production file but is absent from the well master. You are paying for barrels with no title record behind them (DR001).
Internal production disagrees with the RRC-reported lease volume. One of the two is what you will actually be paid on — and a reviewer will ask which (DR003).
A well marked plugged or inactive still reports production. Either the status is wrong or the volumes are (DR007).
A claimed remaining volume is not supported by the production history it is supposedly derived from (DR014) — the reserve number that carries the most price.
An analyst opens the folders, spot-checks the production and the reserve summary, and moves on. Cross-table contradictions — the ones that change the number — are found after signing, or not at all.
The deal closes on the seller's arithmetic.
Fifty-four contradictions named across the package before the bid, each traced to a row. You negotiate on facts that are in writing, not on a spreadsheet's self-agreement.
The findings become the question list for the seller.
What it actually catches
Same design stance as the rest of the suite: read-only, offline, deterministic, traceable to the row — which matters most when the data is a deal in progress.
Pricing
One orphaned well, one unsupported reserve, or one RRC variance the size of a rounding error is worth far more than a year of a license. On a dataroom, the tool pays for itself the first time it is right.
Free
One dataroom package, on the house. No key, no seat limit, no card. You get the full red-flag sheet back.
Send me the dataroom$349/month
Annual commitment, up to 10 users, unlimited packages. Academic research and evaluation use needs no key.
$1,750/month
Annual, per site, unlimited users on that site. Under most data-residency policy this is the premise, not a feature.
Evaluation: 30 days, no license key needed.
Next
Email the package — anonymised if you prefer — and get the full red-flag sheet back at no cost.
kunleaz100@gmail.com