![\"Modern](\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/06\/1781434094_475_0x0.jpg\")
<\/p>\n<\/p>\n
Oil companies are shifting reserve estimates from human engineering to machine-learning models.<\/p>\n
getty<\/p>\n
Permian Resources\u2019 latest quarterly report, filed this spring, names \u201cartificial intelligence and its application in our industry\u201d<\/a> as a risk to the business. The same filing repeats a line that has run in oil-company reports for years: reserve engineering is \u201ca process of estimating underground accumulations of oil and natural gas that cannot be measured in an exact way.\u201d A new tool flagged as a hazard, a few pages from an admission that the number it helps produce was never exact.<\/p>\n To be clear about what that filing does and does not say: it\u2019s a standard risk-factor disclosure, the kind that now shows up in the company\u2019s press releases too. It is not Permian saying it books reserves with AI. Its year-end 2025 reserves were prepared by Netherland Sewell & Associates, an outside engineering firm<\/a>. The story here is broader than one company. Across the industry, the math under the reserve number is changing, and the rules that turn that number into a stock price have not.<\/p>\n Proved reserves are what an oil company is mostly worth on paper. They drive PV-10 (the standardized present value of the oil in the ground), the impairment tests that can force a writedown, and a five-year clock on \u201cproved undeveloped\u201d reserves \u2014 wells a company has committed to drill. Change the reserve figure and the valuation moves with it. The forecast feeding that figure used to come from a chart an engineer drew by hand. More and more, it comes from a model.<\/p>\n The shift from decline curves to models<\/p>\n The traditional method is decline-curve analysis. An engineer plots a well\u2019s falling output, fits a curve, and projects it forward. It dates to the early 1900s, and its main advantage is that anyone can check the work. Its weakness is that it handles complex reservoirs poorly<\/a> \u2014 it can\u2019t account for multiphase flow, wells draining into each other, or the irregular behavior of shale.<\/p>\n Machine learning has stepped into that gap. Petroleum engineers have spent recent years documenting, through the Society of Petroleum Engineers, how models built on top of or in place of the decline curve improve forecast accuracy<\/a>, processing more data and finding patterns the standard equations miss. On accuracy, the case is solid.<\/p>\n The trade-off is visibility. A decline curve shows its reasoning. Many machine-learning models do not. The engineers building them know it, which is why their own research now pushes toward explainable AI and physics-informed models<\/a> that improve interpretability and limit overfitting. A model you can\u2019t fully explain is workable for internal planning. It\u2019s a harder thing to defend once its output becomes a reported asset on a public company\u2019s books.<\/p>\n What the rules require<\/p>\n The governing standard predates this technology by years. SEC Regulation S-X, Rule 4-10(a)(22)<\/a> \u2014 quoted nearly verbatim in 2026 filings from drillers including MACH Natural Resources, which directs readers to that rule for the full definition<\/a> \u2014 defines a proved reserve as a quantity that \u201ccan be estimated with reasonable certainty to be economically producible,\u201d using deterministic or probabilistic methods. Both named methods are forms of engineering a person can trace. The rule doesn\u2019t mention machine learning.<\/p>\n It does leave an opening, and that opening carries most of the weight here. The SEC permits \u201creliable technology,\u201d which it defines as \u201ca grouping of one or more technologies (including computational methods) that has been field tested to provide reasonably certain results with consistency and repeatability.\u201d<\/a> Consistency and repeatability. A model whose output can move when it\u2019s retrained on new data sits uneasily against that requirement. The 2008 modernization that rewrote these rules \u2014 Release 33-8995 \u2014 was meant to let companies adopt better technology. It was not written with an un-auditable model in mind.<\/p>\n There\u2019s also a disclosure rule already in force. Under Regulation S-K, a company reporting material reserve additions has to provide \u201ca concise summary of the technology or technologies\u201d it used, though that summary \u201cmay be general in nature\u201d<\/a> and need not reveal proprietary detail. That carve-out made sense for protecting trade secrets in 2009. Whether a line like \u201cwe used a proprietary machine-learning model\u201d tells an investor enough to judge a reserve\u2019s reliability is an open question.<\/p>\n One number, from the rock to the market cap<\/p>\n The chain is short. An engineer feeds well data into a model. The model produces a production forecast. That forecast becomes a booked reserve, which feeds the PV-10, which feeds the company\u2019s valuation. At one link in that chain, an outside firm is supposed to test the number and ask whether the company is reasonably certain.<\/p>\n Those outside firms \u2014 Ryder Scott, Netherland Sewell, DeGolyer & MacNaughton \u2014 are the names in the reserve-report exhibits at the back of an annual filing. Their sign-off is what turns an internal estimate into a number investors can rely on. They aren\u2019t rubber stamps, and their certifications are evidence-based and, they\u2019d argue, method-agnostic: they test the result against the well data and their own judgment, not against which software produced it. If a model\u2019s forecast matches the production history and the logs, by that logic the software behind it doesn\u2019t change the verdict.<\/p>\n That defense holds up, and it deserves to be stated. It also runs into the one real difference between a model and a curve. You can re-run an engineer\u2019s decline analysis and land on the same answer. Reproducing an opaque model \u2014 and explaining why it weighted one input over another \u2014 is a different job. The certification standards these firms follow, and the industry\u2019s SPE-PRMS framework, were written for deterministic and probabilistic work. They don\u2019t contemplate the reproducibility or explainability of a model. The auditors aren\u2019t cutting corners. Their measuring stick was built for a different kind of estimate.<\/p>\n Who carries the risk<\/p>\n The exposure is concrete. Shareholders own a number partly set by a tool they can\u2019t examine. Banks that lend against reserves \u2014 reserve-based lending, resized every six months on a borrower\u2019s booked barrels \u2014 are extending credit on forecasts that are harder to check. The reserve auditors carry legal and reputational weight each time they certify an estimate. And the SEC enforces a 2008 standard against 2026 tools.<\/p>\n The agency has acted in this area before. Its staff regularly send comment letters asking companies to explain the \u201creliable technologies\u201d behind material reserve additions<\/a> and to justify keeping proved-undeveloped reserves on the books past the five-year limit, beyond which undeveloped reserves can be forced off the books absent specific circumstances<\/a>. If AI starts compressing drilling schedules against that clock, or a model\u2019s role grows large enough to matter to a reserve estimate, those letters have an obvious next question to ask. No marquee case has landed yet.<\/p>\n What to watch<\/p>\n Three markers will show whether the gap narrows. The spring reserve-report cycle, when operators file their third-party exhibits, is where any change in how auditors treat model-derived forecasts would surface first. SEC comment letters are the second \u2014 watch for staff testing how clearly companies disclose AI in their reserve methodology. The third is the reserve-auditing standards themselves: the SPE-PRMS framework and the certification rules are where the profession would have to write explainability into the job, if it decides the moment calls for it.<\/p>\n The number that anchors an oil company\u2019s value is increasingly produced by a tool the rules never anticipated and signed off by auditors working to a standard older than the tool. The gap between the two is the thing to track.<\/p>\n The Bottom Line<\/p>\n Read the reserve number as an estimate with a method behind it, and find out what that method is. The \u201ctechnologies used\u201d disclosure in a company\u2019s annual report tells you whether it leans on \u201creliable technology\u201d or proprietary models; the third-party reserve-report exhibits show how the outside firm frames its certainty. The standard hasn\u2019t caught up to the tooling, so for now the work of asking falls to the investor, the lender, and the regulator. <\/p>\n This article is for informational purposes only and is not investment advice.<\/p>\n","protected":false},"excerpt":{"rendered":"Oil companies are shifting reserve estimates from human engineering to machine-learning models. getty Permian Resources\u2019 latest quarterly report,…\n","protected":false},"author":2,"featured_media":73348,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[24,25,40477,40471,40475,40470,40473,40474,40476,7168,40472,40478],"class_list":["post-73347","post","type-post","status-publish","format-standard","has-post-thumbnail","category-ai","tag-ai","tag-artificial-intelligence","tag-decline-curve-analysis-machine-learning","tag-machine-learning-reserve-estimation","tag-proved-undeveloped-reserves-five-year-rule","tag-pv-10","tag-pv-10-valuation-oil","tag-reasonable-certainty-reserves","tag-reserve-based-lending-ai","tag-sec","tag-sec-reserve-disclosure-rules","tag-third-party-reserve-audit"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/73347","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=73347"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/73347\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/73348"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=73347"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=73347"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=73347"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}