When a private-equity fund or a capital partner buys an oil and gas asset, what they're really buying is a number: the estimated ultimate recovery of a pile of wells, discounted to a present value. Everything in the data room — the maps, the type curves, the engineering — exists to defend that number. And there is a specific, well-documented way that number gets quietly inflated before it ever reaches your investment committee. If you write checks against reserves, this is the trap to know.

The number you're underwriting

A deal's value anchors on the reserve report — usually a third-party engineering certification from a firm like Ryder Scott (whose "Green Book" is treated as a gold standard) or Netherland, Sewell & Associates. These firms also run dedicated A&D (acquisition & divestiture) evaluations, and their report becomes the spine of the model.

But a reserve report is a set of categories, and they are not created equal:

  • PDP — Proved Developed Producing. Wells already on production with a decline history. The hard core of the value. The most defensible, because there's actual data.
  • PDNP / PUD — Proved Developed Non-Producing and Proved Undeveloped. Reserves behind pipe or in locations not yet drilled. Real on paper, but contingent on future capital, future schedule, and the assumption that the wells will perform like the type curve says.

The soft tissue of almost every overstated deal lives in two places: the decline applied to the PDP, and the type curve applied to the PUDs. Both are where optimism hides, and both are where auto-fit software does the most damage.

How the EUR gets inflated: the b-factor and the missing terminal decline

We've written about this at length on the engineering side, but it matters even more on the buy side because you're paying cash for it. Here's the mechanism in one paragraph.

Arps decline curves have an exponent, b, that controls how fast a well's decline flattens. For real boundary-dominated flow, b lives between 0 and 1. But modern shale wells spend years in transient flow, and when software auto-fits a hyperbolic curve to that early data, it routinely returns a b greater than 1 — which is physically unsupportable and, when extrapolated without a constraint, makes cumulative production run toward infinity. The fit looks beautiful (R² of 0.99) and the EUR is fiction. The fix the careful engineers use — splicing on a terminal exponential decline so the well ends at a finite, defensible number — is exactly the constraint a seller's optimistic model is most tempted to leave off.

So the seller's deck can show you a gorgeous historical match and a headline EUR that is structurally biased high, entirely within the bounds of curves that "fit the data." Multiply that across a PUD inventory and you can pay real money for barrels that will never be produced.

The diligence discipline that protects you

The defense isn't to distrust the engineers — it's to re-do the part that drives the value yourself, with constraints the seller had no incentive to apply:

  • Re-decline the PDP independently. Don't accept the seller's curve. Re-fit the producing wells with an enforced terminal decline, and see how much the EUR moves. If the value collapses when you constrain the tail, you've found the inflation.
  • Risk the PUDs hard. Undeveloped locations are worth a fraction of a producing well: they depend on the operator's capital, their schedule, spacing assumptions, and parent-child interference. Apply a real development haircut and a real risk factor — don't book PUDs at the type-curve dream.
  • Interrogate the type curve. Where did the analog wells come from? Were they cherry-picked? Is the b-factor physical? Is there a terminal decline? A type curve without a constraint is a sales document.
  • Mind the gap between SEC-proved and a risked view. SEC proved reserves follow a rulebook; they are not the same as what a prudent buyer should pay for. Your job is the risked number, not the compliance number.

The asymmetry is the whole point: the seller's engineer optimizes the presentation; the buyer has to reconstruct the reality. A seller is never punished for an EUR that's a little too high — that's the person selling the asset. You are.

Why this is getting worse, not better

The marketing around "AI-powered" reserves forecasting makes this trap deeper. A model that optimizes purely for historical fit is, by construction, prone to the exact failure the literature warns about: a high-b hyperbolic with a perfect backward match and an unconstrained, runaway future. Faster, slicker, more confident — and, if it's allowed to produce a physically impossible curve, more wrong. The danger isn't the automation; it's automation that hides the single decision that matters (where the curve is constrained) behind a clean number and a confidence score.

Where this connects to what we build

This is precisely why Workollab built a transparent, browser-native decline engine: so a buyer can re-run the seller's decline themselves, with the terminal-decline guard on, validated against a known-good open-source reference, every assumption visible and auditable — instead of taking a PDF's headline EUR on faith. Diligence on reserves shouldn't require trusting the counterparty's black box. It should let you reproduce the number, constrain it honestly, and see exactly how much of the asking price depends on a b-factor the rock can't support.

You're not buying wells. You're buying a forecast of what those wells will produce. The least your diligence can do is make sure that forecast isn't lying about infinity — before you wire the money.

Sources

This article is general commentary on acquisition diligence, not investment, engineering, or reserves advice. Engage qualified reserves evaluators for any transaction. One of Workollab's oil & gas pieces.

Need to turn this engineering logic into a production-ready tool? Explore custom AI automation for oil and gas operators.