How to Build a PDP, PUD, and Undeveloped Acreage Terminology Register

Direct answer for mineral owners

Create one row for each displayed PDP, PUD, or undeveloped-acreage term. Preserve the exact wording, source, effective date, named preparer, stated standard and edition, and stated scope. Label the row only term displayed, standard stated, or standard not stated. Ask a neutral question for missing context. Do not classify reserves, equate standards, connect the label to an owner property, forecast development, or determine value.

Key takeaways for mineral owners

• Copy the complete displayed term before interpreting an acronym, and preserve the document title, page, date, preparer, standard, edition, and scope in the same row.
• Use only term displayed, standard stated, or standard not stated; do not translate one document label into another classification.
• Keep reserves terminology, acreage-disclosure terminology, regulator production observations, and private owner documents in separate evidence lanes.
• Stop before reserve certification, engineering conclusions, property attribution, development forecasting, DCF inputs, offers, or value.

Terminology boundary. This article explains how to record PDP, PUD, and undeveloped-acreage language displayed in an identified document. It does not certify or assign reserves, reconcile classification systems, determine securities-disclosure compliance, interpret geology or engineering, connect a label to an owner’s property, forecast development, build a DCF, appraise mineral rights, or recommend a transaction. MRX provides educational information and resources only and does not buy mineral rights.

A PDP PUD undeveloped acreage terminology register is a provenance record, not a reserve report. Create one row for every displayed term. Copy the wording exactly, identify the document and page, preserve its effective date, named preparer, stated standard and edition, and stated scope, then use only term displayed, standard stated, or standard not stated.

If a field is missing, record not stated and write a neutral question. Do not fill the gap from memory, a different report, or a glossary that the document did not identify.

Why the source belongs beside the term

The same short label can appear in a securities filing, reserve report, acquisition presentation, engineering summary, owner worksheet, or email. Those documents may have different preparers, audiences, effective dates, governing standards, and scopes. A register prevents the acronym from becoming detached from those facts.

The current SEC definitions in 17 CFR 210.4-10 distinguish developed oil and gas reserves, proved oil and gas reserves, and undeveloped oil and gas reserves within a particular federal reporting framework. The presence of a familiar acronym in another document does not prove that the document used that rule, applied it correctly, or addressed an owner’s mineral interest.

The SEC’s Oil and Gas Reporting Modernization guide also separates the rule definitions, preparer or auditor context, and disclosure about proved undeveloped reserves. That is a reason to preserve the stated standard and preparer, not a license to perform a reserve classification yourself.

Build one source-preserving row per displayed term

Use a separate row even when two terms appear on the same page. That keeps the observation reproducible and prevents one label’s scope from being silently applied to another.

Register field	What to record
Exact displayed term	Complete wording, capitalization, punctuation, acronym, and nearby qualifier
Document identity	Title or record type, stable URL or file reference, version, page, table, or section
Effective or report date	Date stated in the document, or not stated
Named preparer	Person, company, team, or not stated; do not infer authorship
Stated standard	Exact standard name and edition, or standard not stated
Stated scope	Property, field, geographic area, formation, depth, entity, or report boundary exactly as described
Register status	term displayed, standard stated, or standard not stated
Neutral question	What source, date, preparer, standard, edition, or scope would resolve a missing field?

Keep a permitted copy, screenshot, or stable link to the source when practical. A reviewer should be able to find the displayed term without relying on your summary.

Preserve the entire displayed phrase

Do not enter only PDP if the source displays a longer label, table heading, qualifier, footnote marker, or date. Copy the complete phrase into the exact-text field. Put your observation in a separate note so the source wording remains unchanged.

If a document uses PDP or PUD without expanding it, the register should not supply expanded wording. Mark standard not stated unless the document actually identifies a governing definition. A neutral question could be: “Which named standard and edition governs this table?”

The Society of Petroleum Engineers’ 2018 Petroleum Resources Management System is one named resources-classification system with its own classes, subclasses, categories, status definitions, and terminology. Preserve PRMS 2018 only when the source states that identity. Do not assume a report follows PRMS because its wording looks similar.

Keep three evidence lanes separate

Reserve or resource terminology

Record the exact reserve or resource term, governing standard, edition, effective date, preparer, and report scope. Do not decide whether the classification is correct, current, comparable to another report, or attributable to a specific owner.

Acreage-disclosure terminology

The SEC’s acreage-disclosure provision in 17 CFR 229.1208 separately addresses developed and undeveloped acreage in a registrant’s disclosure context. Record that context when it is the stated source. Do not convert an acreage label into a reserve status, well count, drilling schedule, ownership conclusion, or value input.

Regulator production observations

Production data is another lane. The Railroad Commission of Texas Production Data Query FAQs explains that Texas production is reported by operators at the lease level for oil and the gas-well level for gas, that online information has a reporting lag, and that records can change with revised, corrected, or delinquent reports. Preserve the query, retrieval date, displayed period, lease or well reference, and source limitations.

A production result does not certify a reserve classification or explain an acreage label. It also does not prove that a report’s stated scope includes the owner’s tract, depth, or interest.

Use only three register statuses

Term displayed

Use term displayed when the selected source visibly contains the exact term. This status proves only the observation. It does not approve the term, expand an acronym, establish the governing standard, or validate the classification.

Standard stated

Use standard stated when the document explicitly names the standard and, when shown, its edition or effective version. Copy that text. Do not decide that the document complies with the standard or that another document uses an equivalent framework.

Standard not stated

Use standard not stated when the source does not identify the governing standard, the relevant page cannot be retrieved, or the reference is too incomplete to verify. Missing context is not permission to borrow a definition.

Pair the status with a neutral question, such as:

• “Which named standard and edition governs this displayed term?”
• “Who prepared this table, and what effective date applies?”
• “What property, formation, depth, geographic area, or entity is within the stated scope?”
• “Which source page contains the complete label and footnote?”
• “Is there a dated revision that supersedes this document?”

Avoid questions that assume a conclusion, such as “When will these PUD wells be drilled?” or “Why was this acreage left out of the value?”

Do not translate across documents

Place separate reports on separate rows even when their terms appear similar. Preserve each report’s standard, edition, effective date, preparer, and scope. A later reviewer can decide whether comparison is appropriate; the register should not.

Do not transform:

• a displayed reserve term into a development promise;
• an undeveloped-acreage label into a future well location;
• a regulator production observation into a reserve status;
• a company-level disclosure into an owner-property attribution;
• a report quantity into an ownership quantity or royalty forecast; or
• any classification into a DCF input, offer benchmark, or mineral-rights value.

The live existing-wells versus future-locations DCF guide owns the separate modeling boundary. It explains why existing production and future-location scenarios require different evidence. This terminology register never supplies or validates those model inputs.

The acreage-contiguity guide owns geometry and development-context limits. A displayed acreage term does not establish that land is contiguous, positioned in a unit, developable, or scheduled.

The valuation-methodology guide owns economic-method distinctions. The register records language; it does not choose a method or calculate value.

Stop before classification or attribution

The register is complete when every selected term has an exact source reference, date or not stated, preparer or not stated, standard or standard not stated, stated scope, one permitted status, and a neutral question for each gap.

Stop if the next step would require you to:

• certify, correct, reconcile, or assign reserves or resources;
• interpret engineering, geology, probability, commerciality, or project maturity;
• determine federal securities-disclosure or accounting compliance;
• connect the label to a tract, lease, unit, depth, title chain, owner, or payment account;
• infer operator intent, drilling, completion, production, timing, or a development outcome;
• translate a gross quantity into a net owner quantity;
• build or validate a decline curve, price deck, DCF, appraisal, offer, or transaction analysis; or
• recommend whether to sell, hold, sign, negotiate, or transact.

Those tasks may require qualified engineering, geological, securities, legal, land, accounting, appraisal, tax, or regulatory review.

Review the completed register

Before sharing it, confirm that the register:

• uses one displayed term per row;
• preserves the exact wording and nearby qualifier;
• identifies the document, version, page, table, or section;
• separates effective date from retrieval date;
• records the named preparer without inferring one;
• copies the stated standard and edition or says standard not stated;
• keeps the source’s scope intact and does not expand it;
• uses only the three permitted statuses;
• includes a neutral question for every missing field; and
• contains no classification, comparability, compliance, property, development, production, ownership, payment, valuation, offer, or transaction conclusion.

A careful register turns an ambiguous acronym into a traceable question. It does not turn the person building the register into the report’s engineer, geologist, preparer, auditor, regulator, attorney, appraiser, or owner of the conclusion.

Source notes and research limitations

• 17 CFR 210.4-10 supports the distinction among developed, proved, and undeveloped reserves terminology within the SEC rule framework.
• 17 CFR 229.1208 supports the separate developed- and undeveloped-acreage disclosure context.
• The SEC small entity compliance guide supports the rule framework, preparer or auditor context, and separate PUD disclosure requirements; the SEC states that the guide is not a substitute for the rules.
• The 2018 PRMS supports preserving the exact named classification system and edition and its project-based resources terminology.
• The RRC Production Data Query FAQs supports the production-query reporting basis, update timing, possible revisions, and query limitations.

For a bounded review of identified documents you are authorized to share, request an underwriter review. Bring the original source pages with the register; do not replace them with the summary.

Frequently asked questions

What is a PDP, PUD, and undeveloped acreage terminology register?

It is a source-preserving list of terms exactly as displayed in identified reports, disclosures, or owner documents. Each row records the source, date, preparer, stated standard and edition, stated scope, and only whether the term or standard was displayed.

Should I expand PDP or PUD when the document does not?

No. Preserve the acronym exactly as shown and mark the standard or expansion as not stated. Ask which governing standard and definition the preparer used instead of supplying one from another source.

Are PDP, PUD, and undeveloped acreage interchangeable categories?

Do not treat them as interchangeable. A reserve status and an acreage disclosure can answer different questions, and their meaning depends on the identified source, governing standard, effective date, preparer, and scope.

Does a displayed classification prove that it applies to my mineral interest?

No. The label may have a stated report or disclosure scope, but that does not by itself connect it to a particular tract, unit, depth, title, ownership share, payment account, or mineral interest.

When should I seek qualified review?

Use a qualified engineer, geologist, securities professional, attorney, land professional, accountant, appraiser, or other appropriate reviewer when the next step requires validating a classification, interpreting a governing standard, connecting it to property rights, or using it in an economic decision.

Sources reviewed for this article

• GovInfo, 17 CFR 210.4-10 (2025 edition; accessed 2026-08-23)
• GovInfo, 17 CFR 229.1208 (2025 edition; accessed 2026-08-23)
• SEC, Oil and Gas Reporting Modernization: Small Entity Compliance Guide (accessed 2026-08-23)
• Society of Petroleum Engineers, 2018 Petroleum Resources Management System (accessed 2026-08-23)
• Railroad Commission of Texas, Production Data Query FAQs (accessed 2026-08-23)