What haql-dataroom does
haql-dataroom is built for acquisition and divestiture (A&D) technical review. It reads the seller's package, maps the files to their roles and checks whether the production, well, regulatory, revenue, tax, reserve and log tables tell the same story.
In one sentence: It turns the seller's folder into a row-traced question list for the deal team.
Find the red flags
See contradictions before they are buried in a purchase price.
Cross-check the story
Compare production, wells, RRC volumes, revenue, taxes and reserves exhaustively.
Ask better questions
Every finding points to the source row behind the question.
Why it matters
The contradictions that move a price are spread across files. None is visible in a single table. Each takes an analyst cross-referencing two exports by hand — exactly the work that runs out of time before the bid.
- A producing well can be missing from the well master.
- Internal production can disagree with the RRC-reported lease volume.
- A plugged or inactive well can still report production.
- A claimed remaining volume can be unsupported by the history behind it.
An analyst spot-checks production and the reserve summary, then moves on. Cross-table contradictions are found after signing, or not at all.
The contradictions are named before the bid, each traced to a row, and become the question list for the seller.
What goes in
The tool runs on the files the seller handed over. Nothing is uploaded to a portal.
| What goes in | What it means |
|---|---|
| Production CSV | Well-level volumes and dates. |
| Well master CSV | Well identity, status, API number and ownership context. |
| Texas RRC volumes CSV | Regulator-reported lease or well volumes for comparison. |
| Revenue and severance-tax CSVs | Statement values and taxable volumes for back-checks. |
| Reserve summary CSV | Claimed remaining volumes and the basis to test. |
| LAS well-log headers (the standard well-log file format) | Well-log headers that should match the well master. |
| Column mapping | The tool maps common header synonyms; --map ROLE=PATH overrides a guess. |
What comes out
The output is designed to become a deal-team question list, not a valuation.
| What comes out | How to use it |
|---|---|
| Dataroom audit | JSON and HTML red-flag sheet with one record per cross-table finding. |
| Row-level evidence | The source file and row behind each contradiction. |
| Machine-checkable JSON | A structured output for your own models and review workflow. |
| Embedded QC | Structural and numeric checks run before the cross-table rules. |
What it checks
The checks compare tables that are normally reviewed in isolation.
| Check area | What it flags |
|---|---|
| Orphan and barren wells | Production without a well record, or a well with no production history. |
| RRC variance | Internal production that disagrees with the reported lease volume. |
| Interest and API identity | Ownership lines that violate the revenue-interest identity, or malformed API numbers. |
| Duplicates and status | The same well appearing twice, or a plugged/inactive well still producing. |
| Shut-in and timing | Days-on and volume contradictions, or production dated before completion. |
| LAS and revenue links | Log headers that do not match, or revenue referencing a missing lease. |
| Severance and decline | Severance-taxable volume versus produced volume; claimed reserves unsupported by history. |
| Revenue internal value | A statement whose volume, price, deductions and value do not agree. |
The full rule list and rule identifiers are shown in the report and on the product page.
What it does not do
A useful tool should be clear about its boundaries. These are the current limits, not hidden caveats.
- It is not a valuation, reserve certification or investment recommendation.
- It depends on the completeness of the seller's package; missing files limit what can be checked.
- It does not run a data-room portal, upload service or multi-user deal workspace.
- Findings are advisory: a contradiction is a question to resolve, not a conclusion about price.
Findings are advisory. The tool names a contradiction or a risk with the evidence behind it. The engineering, legal or commercial judgement remains with you.
How to try it
Send a dataroom package for a free red-flag check, or run the standalone binary locally.
- Send the seller exports — anonymised if preferred — for a free review.
- Receive a red-flag sheet with each finding traced to its source row.
- Use the findings as the technical question list before the bid.
Access
| Access | What you get |
|---|---|
| Sample check | Free. One dataroom package, no key and no card. |
| Team | $349/month. Annual commitment, up to 10 users and unlimited packages. |
| On-premise | $1,750/month. Annual, per site, unlimited users on that site. |
Nothing leaves your machine. The paid tools run offline. The free libraries have no account, cloud call or telemetry.
Common questions
Does it replace technical due diligence?
No. It makes the cross-file review exhaustive and reproducible, but a qualified reviewer still interprets the findings and the asset.
Do I have to upload the dataroom?
No. The tool runs locally on the files you provide.
Does it value the asset?
No. It finds contradictions in the package; valuation and reserve judgement are separate.
What is a dataroom?
The folder of technical and commercial files a seller provides during an acquisition review.