Texas RRC Wellbore Query Retrieval Provenance Worksheet

Direct answer

Give one official RRC Wellbore Query attempt a neutral ID. Record the exact entry route, displayed criteria labels and controlled values, navigation path, displayed result fields, access timestamp and timezone, source-stated limitation, retained result reference, and only located, not located, or unverified. The worksheet proves how the query was run, not what a well record means or whether it connects to a private mineral interest.

Key takeaways

• Start from the official RRC research directory and preserve the exact Wellbore Query route.
• Copy every used criterion label and selected or entered value into a controlled snapshot.
• Keep result-header criteria, result rows, sorting, pagination, and detail links separate.
• Use only located, not located, or unverified and preserve the source-stated limitation.
• Stop before well interpretation, property connection, title, acreage, compliance, drilling, completion, production, development, reserves, valuation, offer, or transaction conclusions.

Public-record retrieval boundary. This article records one Texas RRC Wellbore Query attempt. It does not interpret a wellbore, completion, API number, lease number, gas-well ID, operator, field, district, well type, current or historical flag, API depth, result row, detail page, tab, attachment, or record. It does not establish property connection, title, ownership, acreage, tract or unit inclusion, lease effect, royalty share, decimal, entitlement, compliance, completeness, accuracy, drilling, completion, development, operator intent, geology, reserves, production, cash flow, value, price, offer quality, or a transaction result. It does not provide legal, title, land, tax, accounting, appraisal, engineering, geological, reserve, 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 wellbore query retrieval worksheet answers one narrow question: exactly how was one official Wellbore Query attempted? Record the entry route, source-displayed criteria, navigation steps, result-header state, result-row locator, access timestamp, source limitation, retained reference, and one bounded retrieval status.

Use only located, not located, or unverified. Those terms describe the query attempt. They do not interpret a well record or connect a displayed result to private property.

Start with the named official route

The Railroad Commission of Texas Research Queries directory links to the Oil & Gas Data Query application. Its query menu presents the Wellbore Query separately from production, injection, severance, P-4, proration, organization, inactive-well, orphan-well, drilling-permit, inspection, and violation routes.

Open the named Wellbore Query and preserve the complete HTTPS address. Do not write only RRC search or merge this route with the separate drilling-permit query.

A reproducible attempt distinguishes:

• the Research Queries directory used as the entry point;
• the Oil & Gas Data Query menu;
• the Wellbore Query criteria screen;
• the result list reached after submission;
• any displayed detail route opened from a result; and
• any authorized screenshot or retained reference created during the attempt.

The RRC directory says its online data is continually updated, informational, non-authoritative, and without legal force or effect. Record that limitation with the access time. Do not turn a result into a claim that the online route is complete, current for every purpose, or legally controlling.

For a broad introduction to Commission systems, use Texas Railroad Commission: How to Use Public Records to Understand Your Mineral Rights. This worksheet owns the smaller reproducibility record for one Wellbore Query execution.

Create an attempt header before searching

Give the attempt a neutral ID such as TX-WB-RET-01. The ID labels a query session, not a property, owner, well conclusion, or transaction.

Record these fields before entering criteria:

• Attempt ID: a stable internal label;
• Purpose: public Wellbore Query retrieval only;
• Official entry route: the complete address opened;
• Query-page label: copied exactly as displayed;
• Access date and time: when the criteria screen was viewed;
• Timezone: the timezone attached to that timestamp;
• Prepared by: a role or controlled identifier;
• Worksheet version: the version used for this attempt; and
• Source limitation: the source’s authority, update, access, coverage, or display note.

Create a new attempt for a later rerun. Do not overwrite an earlier criteria snapshot, result state, timestamp, or retained reference merely because the interface or displayed data changed.

Capture every used criterion by its displayed label

The RRC’s About Oil & Gas Data Queries page and Wellbore Query Help identify search categories that include oil or gas selection, district, oil lease number or gas-well ID, well type, county, field, operator, drilling-permit number, API number, and current or historical selection.

These are locator fields, not conclusions. Create one row for every field used:

• Criterion label: copied as displayed;
• Entry method: typed value, selected option, search helper, or left unused;
• Controlled value reference: the entered or selected value stored appropriately;
• Format shown by source: split boxes, punctuation, option label, or leading characters;
• Used in submission: yes or no; and
• Capture note: any displayed instruction or default that affected the entry.

Avoid a summary such as searched by operator and county. Preserve each label and value separately. If a control remained at its default, record unused or the exact displayed default rather than inventing an entry.

Record the submission and navigation path

After submitting criteria, preserve only the sequence that actually occurred. A bounded path can look like:

official directory → query menu → Wellbore Query → criteria submitted → result list → displayed detail link

For each step, record:

• the displayed page or link label;
• the route or controlled route reference;
• the action taken;
• the access time and timezone;
• whether the page loaded, changed, timed out, or showed no rows; and
• the next step actually selected.

Do not reconstruct a route from memory. If the session ended, an error appeared, or the interface changed, preserve that event and use not located or unverified for the narrow retrieval fact.

Preserve the result-header and display state

The official Wellbore Query help says the result header lists the criteria used. It also describes navigation by page links, a page-size control, and sorting through column headers. Broad criteria can reach a stated 10,000-record display limit, so a displayed result set should not be represented as proof that every relevant record was reviewed.

Record the result state separately from individual rows:

• Criteria echoed by result page: exact labels and controlled values;
• Displayed result range or count: copied as shown, if present;
• Display-limit message: copied or accurately paraphrased, if shown or applicable;
• Sort field and direction: only when selected or displayed;
• Page and page-size state: the page or control actually reviewed;
• Result-page access time: with timezone; and
• Result-page message or limitation: copied or accurately paraphrased.

This lets another authorized reviewer understand the same attempt. It does not certify completeness or validate the displayed data.

Keep result-row labels attached to values

The official help lists result columns such as API number, operator name, district, lease name, lease number, well number, county, field name, current or historical, and API depth.

Record only fields actually observed, and keep each label attached to its value:

• API number: [controlled value];
• operator name: [displayed value];
• district: [displayed value];
• lease name: [controlled value];
• lease number: [controlled value];
• well number: [controlled value];
• county: [displayed value];
• field name: [displayed value];
• current or historical: [displayed value]; and
• API depth: [displayed value].

Use not displayed when the source does not show a field. Similar labels are not interchangeable. An API number is not a private property connection, a lease label is not a private lease interpretation, an operator label does not establish authority, and a current or historical flag is not a conclusion about operating status, production, compliance, or value.

Treat linked details as new retrieval steps

The help describes API-number and lease-number links, along with links to district, field, operator, and county information. It also describes lease-detail tabs for wellbore, injection, severance, P-4, gas proration, inactive-well, and operator information.

Opening a link or tab changes the retrieval context. Create a separate step with:

• originating attempt ID and result-row reference;
• displayed link or tab label;
• destination route or controlled reference;
• destination page label;
• new record class or fields displayed;
• access timestamp and timezone;
• retained reference location; and
• located, not located, or unverified.

Do not merge every linked page into one generic well record. Do not infer a property relationship from matching operator, lease, county, field, well, permit, or API labels. That downstream job belongs to the Offset Activity Property-Connection Cross-Check and remains outside this article.

Keep production and drilling-permit work separate

The Wellbore Query menu exposes separate production and drilling-permit routes. This worksheet does not retrieve production periods or volumes, interpret a W-1, or forecast drilling.

Use explicit source-role labels:

• public research directory;
• Oil & Gas Data Query menu;
• Wellbore Query criteria screen;
• Wellbore Query result list;
• displayed detail route or tab;
• separate official record-access channel; or
• authorized retained query reference.

The Texas mineral production record locator owns production-period retrieval. The drilling-permit query worksheet owns W-1 query provenance. Preserve the boundary even when a detail page links to another record class.

Use only bounded retrieval statuses

Keep the status vocabulary intentionally small:

• Located: the recorded official query exposed an identified result reference.
• Not located: the recorded attempt did not expose the sought result.
• Unverified: a label, identifier, route, or result appeared, but the narrow retrieval fact or relationship was not established.

Located does not mean connected, applicable, complete, accurate, current, active, compliant, productive, legally effective, or valuable. Not located does not mean nonexistent. Unverified preserves uncertainty without alleging an error or defect.

Turn gaps into neutral retrieval questions:

• Which criterion may have narrowed this attempt?
• Did the result header echo every criterion as entered?
• Did a display limit or page-size setting constrain what was reviewed?
• Which result page and sort state were examined?
• Does the row expose a separate detail route or tab?
• Which official record-access channel may hold the record class sought?
• What authority, update, access, or coverage limitation does the source state?

Do not convert those questions into statements about ownership, title, acreage, unit inclusion, lease effect, operating status, compliance, drilling, completion, production, development, reserves, or value.

Preserve an authorized result reference

The live query and a retained object are different evidence. For every authorized screenshot, export, or file, record:

• attempt ID;
• official route and navigation path;
• criteria snapshot;
• result-header and display state;
• result-row or detail reference;
• access timestamp and timezone;
• controlled storage location;
• file hash when your records process uses one; and
• handling note for identifiers, names, addresses, legal descriptions, account data, or other sensitive information.

Do not publish an actual API number, lease identifier, owner record, private document, or property-specific result in a reusable example. A controlled reference proves only what was retained for the recorded attempt.

If the online query is insufficient, the Commission’s Oil and Gas Well Records page supplies separate official record-access context. Record the next route as a question or new attempt; do not claim the online result is the complete agency record.

Blank Wellbore Query provenance worksheet

• Attempt ID: __________
• Purpose: public Wellbore Query retrieval only
• Official entry route: __________
• Query-page label: __________
• Access date, time, and timezone: __________
• Criterion labels and controlled values: __________
• Navigation path: __________
• Result-header criteria: __________
• Displayed result range or limit: __________
• Sort, page, and page-size state: __________
• Result-row labels and controlled values: __________
• Displayed detail-link or tab path: __________
• Source-stated limitation: __________
• Authorized retained-reference location: __________
• Retrieval status: located / not located / unverified
• Neutral next retrieval question: __________

Use one attempt per worksheet record. If a qualified reviewer later interprets a well record, connects it to private property, or uses it for legal, title, land, engineering, geological, production, valuation, or transaction work, preserve that as a separate output with its own author, date, sources, assumptions, and scope.

Final quality check

Before closing the worksheet, confirm that:

• the exact official directory, menu, and Wellbore Query routes are named;
• every submitted criterion preserves its source label and controlled value;
• the navigation path records only steps that occurred;
• result-header state, result rows, links, and tabs remain separate;
• result range, display limit, sorting, pagination, and page size are recorded only when displayed or used;
• the access timestamp, source limitation, and retained reference are attached;
• every status is only located, not located, or unverified;
• no row interprets a wellbore, completion, API number, lease, operator, field, district, well type, current or historical flag, depth, or detail page;
• no row establishes property connection, ownership, title, acreage, unit inclusion, lease effect, royalty share, entitlement, compliance, completeness, or accuracy; and
• no row infers drilling, completion, development, operator intent, geology, reserves, production, cash flow, value, price, offer quality, or a transaction result.

A strong provenance worksheet is narrow by design. It lets an authorized reviewer understand and repeat the recorded Wellbore Query attempt. It does not decide what a well record means.

Frequently asked questions

Does a located Wellbore Query result prove that the well affects my mineral interest?

No. Located means only that the recorded official query exposed an identified result reference. It does not establish a property connection, ownership, title, lease effect, unit inclusion, acreage, royalty share, entitlement, drilling, production, or value.

Does not located mean that no well or record exists?

No. Not located describes one attempt using stated criteria at a stated time. A criterion mismatch, display limit, interface issue, data change, or separate official record channel may require another bounded retrieval step.

Should I copy an API number or lease number into a public worksheet example?

No. Keep owner-specific identifiers and actual query results in an authorized controlled reference. A reusable example should use blank fields and should not publish private or property-specific information.

Can I interpret a current or historical label from this worksheet?

No. Preserve the source-displayed label and value as retrieval evidence. This worksheet does not determine operating status, legal effect, production, compliance, development, or a property relationship.

Can this worksheet support a drilling forecast or mineral-rights valuation?

No. It records query provenance only. It does not establish reserves, operator intent, completion probability, production, cash flow, value, price, offer quality, or a transaction result.

Sources

• Railroad Commission of Texas, Research Queries (accessed 2026-08-23)
• Railroad Commission of Texas, About Oil & Gas Data Queries (accessed 2026-08-23)
• Railroad Commission of Texas, Oil & Gas Data Query (accessed 2026-08-23)
• Railroad Commission of Texas, Wellbore Query (accessed 2026-08-23)
• Railroad Commission of Texas, Wellbore Query Help (accessed 2026-08-23)
• Railroad Commission of Texas, Oil and Gas Well Records (accessed 2026-08-23)