Wildcatters Learn · Production

What is a production reporting entity?

Production Reporting Entity is the well, lease, unit, or other entity to which a regulator assigns reported volumes.

Wildcatters Editorial3 min read

What to know

  • A production volume belongs to a named reporting entity and period.
  • A lease total is not automatically an individual well total.
  • Entity relationships and revisions must be preserved when comparing records.

The entity is the scope of the reported volume

A production table needs more than a volume and a well name. It needs the entity to which the regulator assigned that volume. That entity may be a well, a lease, a unit, or another reporting group. Its identifier determines what can safely be compared or joined to other records.

In Texas, the Texas RRC · Production Data Query FAQ explains the use of lease-level production reporting. Oil leases can contain multiple wells, while gas production is reported by individual gas-well lease. That distinction is specific to the source system; it should not be generalized to every state's reporting model.

Why it matters

Lease-level volumes cannot be allocated to individual wells without an authoritative relationship and allocation method.

Read the record before joining the data

Keep the reporting entity identifier, entity type, regulator, production period, product, unit of measure, and reported volume together. A well's API identifier and a production lease identifier are different keys. A similar name does not make them interchangeable.

Use the regulator's documented relationship between a well and its reporting entity. The Texas RRC · Production and wellbore data documentation lists separate Texas wellbore and production datasets. The existence of those datasets does not establish a one-to-one relationship between every row. Check the documentation and relevant period before joining them.

Researching a well inside a reporting group

First locate the well using its official identifier. Next establish the production entity associated with it for the period under review. Read the entity's total as a group total until the source supports a finer level of detail.

If a lease contains several wells, dividing its production equally among them invents an allocation. Even an allocation based on a plausible operating assumption should not be presented as reported well production. Keep any unresolved relationship visible, and use separate well-level records if the regulator actually provides them.

Compare like scopes and reporting periods

When comparing two properties, ask whether one series represents a well and the other a multiwell lease. A larger total may reflect a broader reporting scope. Differences in product, units, dates, or revised filings can also explain apparent changes.

An operator change is another reason to check continuity. Preserve the identifiers and effective periods used by the source instead of treating an operator name change as a new physical well. The same care applies when a reporting group changes over time.

Production totals do not establish an owner’s proceeds

Reported production does not by itself establish mineral ownership, an owner's payment decimal, realized sales price, or deductions. A royalty statement may use sales or payment periods that differ from the regulator's production period.

Use production records to understand reported activity. Use the applicable ownership, lease, allocation, and payment documents to investigate a revenue question. A discrepancy is a reason to reconcile those records, not proof of a payment error.

Research checklist

  • Identify the reporting entity and its type.
  • Confirm the well-to-entity relationship for the period.
  • Keep products, units, and periods aligned.
  • Do not manufacture a per-well allocation from a group total.

Put it into practice

Check the records behind a property

Use Wildcatters Intelligence to explore the available well, operator, production, and regulatory records. Confirm the source, jurisdiction, and reporting dates before drawing conclusions.

Open Intelligence 2.0

Sources and review

Primary sources are linked beside the relevant explanations. Source publication dates and jurisdictions still apply.