Texas RRC New Lease IDs Built Query Retrieval Provenance Worksheet

Direct answer

Give one official New Lease IDs Built Query attempt a neutral ID. Record its exact routes and labels, controlled criteria, access time and timezone, displayed state, retained reference, limitations, and only located, not located, or unverified. This documents retrieval without deciding what new or built means or whether a result relates to a mineral interest.

Key takeaways

• Keep New Lease IDs Built Query separate from Production Report Queries and every other RRC route.
• Record source-displayed criteria, selector modes, controls, and limitations as interface state, not findings.
• Keep actual operator, API, permit, field, lease-ID, result, and screenshot information in an authorized controlled location.
• Capture access time, timezone, navigation, displayed state, retained reference, and source limitations.
• Use only located, not located, or unverified, then stop before property, title, production, valuation, legal, or transaction conclusions.

Public-record retrieval boundary. This article records one Texas RRC New Lease IDs Built Query attempt. It does not interpret new lease, built, a criterion, selector mode, drilling permit, API, operator, field, district, county, date, result, lease ID, help term, or source status. It does not establish property connection, title, ownership, acreage, lease effect, production, reserves, cash flow, status, compliance, value, offer quality, legal effect, or a transaction result. It does not provide legal, title, land, tax, accounting, appraisal, engineering, geological, regulatory, 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 New Lease IDs Built Query retrieval worksheet answers one narrow question: exactly how was one official retrieval attempt performed? Record the official directory, application, and help routes; exact source-displayed labels; access timestamp and timezone; controlled chosen criteria; navigation or displayed state; authorized retained reference; source limitations; and one bounded retrieval status.

Use only located, not located, or unverified. Those words describe the retrieval attempt. They do not decide what new or built means, establish a lease, connect a result to private property, verify production, or support a valuation or transaction conclusion.

Start with the exact New Lease IDs Built Query route

The Railroad Commission of Texas Research Queries directory lists New Lease IDs Built Query as a separate oil-and-gas research tool and currently labels its update frequency as nightly. Preserve the directory URL, exact label, launch URL, access time, and the directory’s access and data limitations. Do not substitute a search-engine result, old bookmark, or neighboring RRC application for the current official route.

The launched New Lease IDs Built Query uses publicQueriesNewLeaseAction.do. It displays the query title, a search area, source-defined criteria, field and operator selector modes, Submit, Reset, Restart Search, and a results area. Record the exact route and labels visible during the attempt.

The separate Production Report Queries home uses another route and displays separate production-report search forms. A navigation link between the pages does not merge their jobs. This worksheet owns only one publicQueriesNewLeaseAction.do attempt. It does not document a Production by Lease, Filing Operator, Operator of Record, or other production-report query.

For broader orientation, use Texas Railroad Commission: How to Use Public Records to Understand Your Mineral Rights. For a different route-specific job, use the Texas RRC Drilling Permit Query Retrieval Provenance Worksheet. Keep attempt records separate even when the same permit, API, field, operator, district, county, or lease label appears across systems.

Create an attempt header before entering criteria

Give the attempt a neutral ID such as TX-NEW-LEASE-ID-RET-01. That identifier labels a retrieval session, not a lease, permit, operator, well, field, property, mineral interest, finding, status, or transaction. Record:

• the Research Queries directory route and exact directory label;
• the launched application route, HTML title, visible heading, and navigation label;
• the help route and exact page title actually used;
• access date, time, and timezone;
• preparer role and worksheet version;
• stated purpose, limited to one New Lease IDs Built Query retrieval;
• source-stated date, coverage, access, search, result, and data limitations; and
• the controlled location where real criteria and retained evidence will be stored.

Create a new attempt ID for every rerun. Do not replace an earlier record because a label, criterion, selector, result area, validation message, error, or access condition changed. A sequence of preserved attempts shows what was actually retrievable at each recorded time.

Record the date range and source limitation exactly

The official New Lease Query Help page says the date format is MM/DD/YYYY and the maximum date range is 90 days. It also states that query results are only for lease IDs built after November 1, 2006.

Preserve those statements as query mechanics and source limitations. Record the controlled From and To values, the displayed format instruction, whether the interval stayed within the stated maximum, any validation message, and the access timestamp. Do not transform the entered range into a claim that a lease was created, changed, filed, effective, or connected to a property during that period.

The post-November 1, 2006 statement limits what this query says it returns. It does not prove that an older reference is absent, that another official system has no record, or that a private interest began on a particular date. If the sought reference may fall outside the source’s stated coverage, record that limitation and use unverified or a separately scoped next question.

Record only the criteria the source displays

The current query page displays fields for Date Range, Drilling Permit No, API No, District, County, Field, and Operator. For each criterion, record four items: the exact source label, whether a default appeared, whether the preparer changed it, and the controlled evidence reference for the actual value.

The official help page describes field and operator search modes that include containing characters, beginning with characters, and matching a number exactly. It also describes minimum-character behavior for the beginning-with path and separate selection steps. Record the mode chosen, controlled input, returned selection state, selected row reference, and navigation back to the main query.

Do not copy real values into a reusable public worksheet. Use placeholders such as [controlled date range], [controlled permit reference], [controlled API reference], or [controlled operator selection]. A criterion is an input to one attempt. It does not validate the named entity, prove a property relationship, or establish the meaning of a returned result.

Preserve selector navigation as its own evidence

Field and operator selection may involve multiple visible states. Record each route or page state actually used:

• parent query displayed before opening the selector;
• exact selector label and search mode;
• controlled input entered;
• search control selected;
• selection list displayed or not displayed;
• controlled selection added or returned;
• parent query repopulated or not repopulated; and
• timestamp for each material navigation step.

A list entry or selection control is interface state. It does not prove that a field or operator is correct for a property, that a permit or API belongs to an interest, or that a resulting lease ID has a particular meaning. If the selector state cannot be reproduced, use unverified.

Record the displayed state without interpreting it

An attempt may stop at the initial query page, a selector, a validation message, an empty result area, a populated result area, an error, or an access boundary. Record the state neutrally:

• query page displayed with no submission;
• controlled criteria entered and Submit selected;
• source validation or date constraint displayed;
• selector displayed and returned to the parent query;
• result area displayed with no visible row;
• result area displayed with one or more visible rows;
• sought controlled reference displayed or not displayed;
• Reset or Restart Search selected and resulting state recorded;
• error, timeout, session, or access state displayed; or
• source state could not be verified.

An empty initial result area is not the same as a submitted query with no visible match. A query with no visible match is not proof that no lease ID or other record exists. Preserve what was displayed, what action preceded it, and which evidence reference captures the state.

If a substantive source term or value appears, retain the exact wording in controlled evidence. The Production Reports Help Contents page provides separate help navigation for New Lease Query, PR Queries, operator search, error messages, and the glossary. Record a help route only if it was actually opened during the attempt.

Use glossary terms only as source wording

The official Oil and Gas Glossary contains broad agency terminology. A worksheet may record that a particular displayed term was checked against the glossary, preserve the exact glossary route and access time, and store the source wording in controlled evidence.

Do not use a glossary definition to declare that a displayed query result applies to a specific lease, well, operator, field, permit, API, property, mineral interest, production stream, or title chain. Glossary context is not a property match, status determination, title opinion, legal conclusion, or valuation input.

Retain evidence in a controlled location

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

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

Do not publish credentials, session tokens, cookies, private correspondence, personal contact details, actual permit, API, operator, field, district, county, lease-ID, result rows, screenshots, property identifiers, production records, or internal case notes. If evidence must be shared with an authorized professional, provide the controlled reference and the minimum necessary underlying record through an approved channel.

Assign only a bounded retrieval status

Choose one status after the attempt:

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

Located does not authenticate a result, establish that it applies to a mineral interest, or interpret a field. 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 rerun with a corrected controlled criterion, should a separately named official route be searched, or should an authorized reviewer compare the retained reference with another official record? Do not end with a conclusion about a lease, operator, permit, API, field, production, title, ownership, value, offer, or transaction.

Protect the mineral owner’s information

Store real permit, API, operator, field, district, county, date-range, lease-ID, criterion, result, screenshot, property, title, production, 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 public agency, title examiner, attorney, engineer, geologist, accountant, appraiser, regulator, or neutral fiduciary.

Final retrieval check

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

Stop there. The next step may be another official-source retrieval or an appropriately scoped professional review. It is not a conclusion about new lease, built, a lease ID, operator, permit, API, field, district, county, production, status, compliance, property connection, title, ownership, acreage, legal effect, value, offer quality, or transaction.

Frequently asked questions

Does a New Lease IDs Built Query result prove that a new private lease exists?

No. Located means only that the recorded official attempt exposed the controlled reference sought. The worksheet does not interpret new, built, lease identity, private-property connection, title, ownership, acreage, lease effect, production, value, or legal effect.

How large can the query date range be?

The official help page states a maximum 90-day date range and specifies MM/DD/YYYY. Record the exact controlled dates and the source-displayed validation state without treating the range as evidence about a lease or property.

Does not located mean that no lease ID was built?

No. Not located describes one attempt using stated criteria at a stated time. Coverage, the post-November 1, 2006 help limitation, criteria, interface state, access limits, or a different official route may require a separate retrieval step.

Is New Lease IDs Built Query the same as Production Report Queries?

No claim of equivalence should be made. The source presents publicQueriesNewLeaseAction.do as its own query and publicQueriesMainAction.do as the Production Report Queries home. Keep their attempt records and meanings separate.

Can a reusable worksheet publish real permit, API, operator, field, district, county, lease-ID, or result details?

No. Keep actual identifiers, criteria, results, screenshots, and source-displayed details in an authorized controlled location. Reusable public examples should remain blank.

Sources

• Railroad Commission of Texas, Research Queries (accessed 2026-08-24)
• Railroad Commission of Texas, New Lease IDs Built Query (accessed 2026-08-24)
• Railroad Commission of Texas, New Lease Query Help (accessed 2026-08-24)
• Railroad Commission of Texas, Production Report Queries (accessed 2026-08-24)
• Railroad Commission of Texas, Production Reports Help Contents (accessed 2026-08-24)
• Railroad Commission of Texas, Oil and Gas Glossary (accessed 2026-08-24)