Texas RRC Production Data Query Retrieval Provenance Worksheet

Direct answer

Give one manual limited-area PDQ attempt a neutral ID. Select General Production Query or Specific Lease Query, then record the exact official path and used criteria labels, controlled values, access time and timezone, displayed state, retained reference, source limitations, and only located, not located, or unverified. This preserves retrieval provenance without interpreting production.

Key takeaways

• Select General Production Query or Specific Lease Query before recording criteria and keep one path per attempt.
• Record source-displayed update, coverage, navigation, validation, result, and error states as time-bound interface evidence.
• Keep actual lease, well, operator, field, county, district, period, and production details in an authorized controlled location.
• Use the source-provided Query Path or Return controls and do not automate or bulk-retrieve the RRC system.
• Use only located, not located, or unverified, then stop before production, property, title, ownership, valuation, offer, legal, or transaction conclusions.

Public-record retrieval boundary. This article records one manual attempt in the Railroad Commission of Texas limited-area Production Data Query. It does not interpret a source-displayed production figure, disposition, lease, well, field, operator, county, district, date, coverage note, update note, validation, result, or error. It does not connect a regulator record to private property, establish title, ownership, acreage, payment entitlement, reserves, value, offer quality, legal effect, or a transaction result. It does not provide legal, title, land, tax, accounting, appraisal, engineering, geological, regulatory, investment, or financial advice. MRX may have an economic interest in a later transaction; when that applies, the buyer relationship is disclosed in writing before an agreement is signed.

A Texas RRC Production Data Query retrieval worksheet answers one narrow question: exactly how was one authorized, manual PDQ attempt performed? Record the official directory route, the selected General Production Query or Specific Lease Query path, exact criteria labels actually used, controlled values, access timestamp and timezone, displayed state, retained reference, source limitations, and one bounded retrieval status.

Use only located, not located, or unverified. Those terms describe the attempt. They do not decide whether a displayed lease, well, production period, operator, field, county, district, or volume belongs to a mineral owner or supports a production, title, valuation, offer, legal, or transaction conclusion.

Start with the official directory and limited-area application

The Commission’s Research Queries directory lists Production Data Query (limited area) and currently labels its update frequency as monthly. Preserve the exact directory label, directory URL, launch route, access time, and displayed update label. The directory also states that online-query data is informational, continually updated, and not an authoritative public record with legal force. Keep that limitation attached to the attempt.

The launched Production Data Query is the only application this worksheet owns. Its home page presents two source-labeled paths: General Production Query and Specific Lease Query. It also displays time-bound coverage and processed-through information and warns that the browser Back button can produce inconsistent results. Record those visible states as observed source evidence; do not turn them into promises of completeness, currency, accuracy, or suitability.

This worksheet does not own the separately listed Production Reports Query (Form PR), a separately routed statewide PDQ surface, Wellbore retrieval, New Lease IDs retrieval, oil or gas proration, or any other RRC route. The Texas mineral production record locator sheet owns a broader multi-route locator job. This article owns only one attempt in the named limited-area PDQ application.

Create a neutral attempt header

Give the attempt a neutral ID such as TX-PDQ-RET-01. It labels a retrieval session, not a lease, well, property, operator, production finding, title conclusion, or transaction. Record:

• the official directory and launched application URLs;
• the exact source-displayed directory and page labels;
• the selected General Production Query or Specific Lease Query path;
• access date, time, and timezone;
• preparer role and worksheet version;
• stated purpose, limited to one PDQ retrieval attempt;
• displayed update, coverage, navigation, access, and data limitations; and
• the controlled location for real criteria and retained evidence.

Use a new attempt ID for every rerun. Do not overwrite an earlier attempt because the application, criteria, path, displayed coverage, update state, result, validation message, error, or access condition changed. Preserved attempts show what was retrievable at each recorded time.

Choose one official path before entering criteria

The PDQ home page says the General Production Query is suited to a wider or more extensive scope and lets a user drill into more specific information. It describes Specific Lease Query as the path for a particular lease when the lease number and district number are available, with a lease-name search available when a number is not known. Preserve those source descriptions as navigation context only.

Mark one path as selected and the other as out of scope. If both paths are needed, create two attempt IDs with separate timestamps, criteria, displayed states, retained references, and limitations. Do not merge a broad result path and a specific-lease path into one provenance record.

The path choice does not prove that an identifier is correct, that a displayed lease or well matches a private mineral interest, or that reported production belongs to an owner. It only documents how the source was approached.

Record exact used labels and controlled values

After selecting a path, copy only the labels actually used in that attempt. Depending on the route and drill-down, the source may expose lease, field, operator, district, county, well, period, or other production-query controls. Do not prefill a reusable worksheet with assumed criteria. Preserve the source’s spelling, capitalization, selected options, and displayed defaults at access time.

For each used criterion, record the exact source label, the displayed default if any, whether the preparer changed it, and a controlled reference for the actual value. Public placeholders can include [controlled lease reference], [controlled district], [controlled field reference], [controlled operator reference], [controlled county], [controlled well reference], or [controlled period].

Do not publish real criteria or results in a reusable worksheet. An entered value is an input to one attempt. It does not authenticate an identifier, establish a property connection, prove production entitlement, or determine value.

Preserve navigation and displayed state

The PDQ home page warns that using the browser Back button may cause inconsistent query results and directs users to Query Path links or Return buttons. Record the navigation control used and the complete displayed path. Do not infer that a reconstructed browser-history route reproduces the same state.

An attempt may stop at the home page, a selected query form, a validation message, a result table, a drill-down page, an empty result, a changed date range, an error, a timeout, or an access boundary. Record the state neutrally:

• PDQ home page displayed with no path selected;
• General Production Query selected;
• Specific Lease Query selected;
• controlled criteria entered and the source search control selected;
• source validation or required-field message displayed;
• result table or drill-down page displayed;
• sought controlled reference displayed or not displayed;
• Query Path or Return navigation used;
• displayed coverage or processed-through state captured;
• error, timeout, session, or access state displayed; or
• source state could not be verified.

An initial blank form is not a submitted search with no visible match. A submitted search with no visible match is not proof that no record exists. Preserve the action immediately before the state, the selected path, controlled criteria reference, timestamp, and retained-evidence reference.

Keep production context attached to its limits

The official PDQ FAQs explain that production information comes from operator reports, that oil and gas reporting can be organized differently, that online information has a reporting lag, and that later revised, corrected, or delinquent reports can change a prior view. The FAQ also describes PDQ coverage and monthly updates.

Record those limitations beside the retained result. Do not convert them into a conclusion that a displayed figure is current, complete, accurate, owner-attributable, or suitable for valuation. The official Production Data page lists PDQ and Production Reports Query as separate routes. A result from one does not prove what the other would display.

This worksheet does not compare months, reconcile reports, calculate decline, estimate reserves, normalize units, or connect regulator-reported production to a royalty statement. Those are separate analytical jobs requiring their own evidence and qualified review.

Do not automate or bulk-retrieve

The Research Queries directory warns that automated tools used to retrieve volumes of data can degrade Commission systems and that the system may end such a session. This worksheet is for one authorized manual attempt. It does not authorize scraping, scripted navigation, bulk exports, repeated automated polling, or attempts to evade source limits.

If a task requires a dataset rather than one manual provenance record, stop and select an official data-delivery route designed for that purpose. Do not repurpose this worksheet into a collection tool.

Retain evidence in a controlled location

The reusable worksheet should store a controlled reference, not sensitive evidence. A retained-evidence record can identify:

• attempt ID and worksheet version;
• authorized repository, case system, or evidence-vault location;
• capture, note, or result filename;
• capture timestamp and timezone;
• file SHA-256 or another integrity reference;
• source URL, selected path, and displayed page label;
• access role and retention rule; and
• whether a later reviewer independently repeated the attempt.

Do not publish credentials, session tokens, cookies, private correspondence, contact details, actual lease or well identifiers, operator details, property identifiers, criteria, results, production figures, screenshots, royalty information, or internal case notes. Share underlying evidence only with authorized recipients through an approved channel and for a stated purpose.

Assign only a bounded retrieval status

Choose one status after the attempt:

1. Located: the recorded path exposed the specific controlled reference sought.
2. Not located: the recorded attempt did not expose that reference using the stated path and values.
3. Unverified: the route, path, used labels, controlled values, displayed state, retained reference, or source limitation was not captured well enough to reproduce the attempt.

Located does not authenticate a record or connect production to a mineral interest. Not located does not prove absence. Unverified is the correct status when the evidence trail is incomplete.

End with one neutral next question. For example: should the attempt be repeated with a corrected controlled value, should the other official PDQ path receive its own attempt ID, or should an authorized reviewer compare the retained reference with a separately named official source? Do not end with a conclusion about production, property, title, ownership, acreage, payment, reserves, value, offer quality, legal effect, or a transaction.

Protect the mineral owner’s information

Store real identifiers, criteria, results, screenshots, production, royalty, property, title, payment, and correspondence details in an access-controlled location. Share only records you are authorized to provide and disclose why each record is requested.

MRX may act as an educator, evaluator, marketplace operator, or possible buyer. If MRX or an affiliate could acquire an interest, that economic relationship should be stated clearly before a transaction agreement is signed. A provenance worksheet improves reproducibility; it does not make MRX a regulator, title examiner, attorney, engineer, geologist, accountant, appraiser, investment adviser, or neutral fiduciary.

Final retrieval check

Before closing the attempt, confirm that the worksheet preserves the complete official route, one selected path, exact used labels, access time and timezone, controlled values, displayed navigation, validation, result, error, coverage, or update state, retained reference, source limitations, bounded status, and one neutral next question. If one item is missing, use unverified until the record is complete.

Stop there. The next step may be another official-source retrieval or an appropriately scoped professional review. It is not a production, property, title, ownership, acreage, payment, reserves, valuation, offer, legal, or transaction conclusion.

Frequently asked questions

Does a PDQ result prove production attributable to my mineral interest?

No. PDQ contains operator-reported production information organized according to the source system. A displayed result does not connect a lease or well to a private interest, establish ownership or a payment decimal, reconcile a royalty statement, or determine value.

Should General Production Query and Specific Lease Query be combined in one attempt?

No. Select one source-labeled path per attempt. If both paths are needed, create separate attempt IDs with their own criteria, timestamps, displayed states, retained references, and limitations.

Does not located mean that no production record exists?

No. Not located means only that one recorded attempt did not expose the controlled reference using the selected path, criteria, source coverage, and interface state at the recorded time.

Can the worksheet use an automated script to collect PDQ results?

No. The RRC warns that automated retrieval of volumes of query data can degrade its systems and end a session. This worksheet is for one authorized manual attempt, not scraping, bulk retrieval, or automated monitoring.

Can this worksheet compare production or calculate mineral value?

No. It records retrieval provenance only. It does not interpret volumes, reconcile reports, estimate reserves or decline, calculate cash flow or value, assess an offer, or provide legal, title, tax, engineering, geological, appraisal, investment, or financial advice.

Sources

• Railroad Commission of Texas, Research Queries (accessed 2026-08-24)
• Railroad Commission of Texas, Production Data Query (accessed 2026-08-24)
• Railroad Commission of Texas, Production Data Query System FAQs (accessed 2026-08-24)
• Railroad Commission of Texas, Production Data (accessed 2026-08-24)