Texas RRC H-10 Query Retrieval Provenance Worksheet

Direct answer

Give one official H-10 query attempt a neutral ID. Record the directory and H10 Public Main routes, the exact menu and criterion labels used, controlled values, time window, access timestamp and timezone, displayed limitation, retained reference, and only located, not located, or unverified. The worksheet proves how the query was attempted, not what any H-10 report, well, operator, volume, status, or violation means.

Key takeaways

• Start from the official RRC Research Queries directory and preserve the complete H-10 route chain.
• Copy each used Search for H10 criterion label and controlled value without turning it into a property conclusion.
• Record the visible data-period and date-range limitations with the access time.
• Keep result headers, result links, screenshots, and later record channels separate.
• Use only located, not located, or unverified, then stop before legal, environmental, production, value, or transaction conclusions.

Public-record retrieval boundary. This article records one Texas RRC H-10 public-query attempt. It does not interpret an H-10 report, UIC number, API number, district, field, lease, operator, date, status, result row, detail link, or document. It does not establish property connection, title, ownership, acreage, tract or unit inclusion, lease effect, payee status, royalty share, decimal, payment responsibility, entitlement, compliance, environmental condition, injection fact, volume, 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, environmental, 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 H-10 query retrieval worksheet answers one narrow question: exactly how was one official H-10 Query attempted? Record the entry route, source-displayed criteria, navigation steps, result-header state, result 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 an H-10 record, decide whether a report is complete, or connect a displayed item to private property.

Start with the named official route

The Railroad Commission of Texas Research Queries directory lists the H-10 Annual Disposal/Injection Well Monitoring Report Query as a named route. Preserve the complete directory address, then the H10 Public Main address, rather than recording a generic phrase such as RRC H-10 search.

The H10 Public Main menu separates Injection Volume Query, Fluid Type Query, Filing Cycles by Field, Search for UIC, Search for Violations, and Search for H10. This worksheet owns one bounded Search for H10 attempt. It does not merge those separate menu actions, and it does not convert a menu label into a factual conclusion about a person, well, property, condition, or report.

The RRC directory says its online research queries are intended for people needing specific information and warns that automated retrieval of volumes of data can degrade its systems. The directory also describes its online query material as informational. Record the source limitation and access time. Do not treat a screen, result list, or retrieval attempt as authoritative legal, title, regulatory, environmental, or transaction evidence.

For broad orientation, use Texas Railroad Commission: How to Use Public Records to Understand Your Mineral Rights. This page owns the smaller reproducibility record for a single H-10 Query execution.

Create an attempt header before searching

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

Record these fields before entering criteria:

• Attempt ID: a stable internal label;
• Purpose: public Search for H10 retrieval only;
• Official entry route: the complete addresses opened;
• Menu and page labels: copied exactly as displayed;
• Access date and time: when the criteria screen was viewed;
• 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 stated coverage, update, access, or display note.

Create a new attempt for a rerun. Do not overwrite a prior criteria snapshot or result state merely because the page, date, or displayed data changed.

Capture each used criterion by its displayed label

The current Search for H10 screen labels fields including UIC Number, API Number, District, Status, Field Number, Lease Number, Operator Number, and a From/To date range. The screen currently states that H-10 information is available from January 2007 forward, that entering a UIC or API number causes other fields to be ignored, and that a lease or operator number is required for a date range greater than three months. Preserve the exact note shown at the time of the attempt instead of relying on memory.

Each criterion is a locator field, not a conclusion. Create one row for every field used:

• Criterion label: copied as displayed;
• Entry method: typed value, selected option, or left unused;
• Controlled value reference: the entered or selected value stored appropriately;
• Format shown by source: date format, option label, or instruction;
• Used in submission: yes or no; and
• Capture note: any displayed constraint, default, or warning that affected the attempt.

If a control was not used, record unused. Do not replace individual labels with a vague statement such as searched an H-10. Do not publish real identifier values in a reusable example.

Preserve the stated time boundary without reconciling it away

The RRC’s H-10 information page describes the Commission’s Form H-10 online-filing context and separately discusses access to reported data. The live Search for H10 criteria screen supplies its own stated availability note. Preserve the page label, route, exact wording or controlled excerpt, and access time for whichever source informed the attempt.

Do not silently reconcile a period boundary from one source with an interface statement from another. A provenance worksheet can record that two official pages state different scopes or describe different contexts. It cannot decide which report exists, whether filings were required, whether a record is complete, or what a date boundary means for a property or operator.

Record the submission and navigation path

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

official directory → H10 Public Main → Search for H10 → criteria submitted → result list → displayed detail or next route

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 sequence from memory. If the session ended, an error appeared, or a stated constraint prevented submission, preserve that event and use not located or unverified for the narrow retrieval fact.

Keep result state and downstream meaning separate

The RRC’s public-query help describes separate public query types and describes how certain results screens may expose links. That identifies a source navigation pattern. It does not establish the meaning, accuracy, completeness, or legal effect of an individual H-10 result.

Record the result state separately from individual rows:

• Criteria echoed by the result page: exact labels and controlled values;
• Displayed result range or count: copied as shown, if present;
• Date-period or display-limit message: copied or accurately paraphrased if shown;
• Sort, page, and page-size state: only when displayed or used;
• Result-page access time: with timezone; and
• Result-page message or limitation: copied or accurately paraphrased.

Then preserve only labels actually observed. A row may contain a displayed UIC, API, district, field, lease, operator, status, date, or link label. Keep each label attached to its value and use not displayed when the source does not show a field. Matching text or numbers are not a property connection.

Treat every new route as a new retrieval step

If a result exposes a detail link, blank document, other query, help page, or another official record channel, create a separate step with:

• originating attempt ID and result 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.

The Search for H10 screen is not the same as an Injection Volume Query, Fluid Type Query, violation search, UIC search, Wellbore Query, Organization Query, P-4 Query, or drilling-permit search. Do not combine a result from any of those routes into one implied operational or property record.

The Texas RRC Organization (P-5) Query Retrieval Provenance Worksheet owns a different entity-focused route. The Texas RRC Wellbore Query Retrieval Provenance Worksheet owns a different wellbore route. Preserve those boundaries even where a screen displays an operator, lease, or number.

Use only bounded retrieval statuses

Keep the status vocabulary deliberately 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, compliant, permitted, active, delinquent, safe, injected, productive, paid, valuable, or legally effective. Not located does not mean nonexistent. Unverified preserves uncertainty without alleging an error or defect.

Turn gaps into neutral retrieval questions:

• Which criterion or time limitation narrowed this attempt?
• Did the result header echo every criterion as entered?
• Did the screen state a coverage limit, date-range limit, or display limit?
• Which result page and sort state were examined?
• Does the result expose a separate official route or controlled record channel?
• Which official source can describe the requested record class without converting it into a property conclusion?

Preserve an authorized retained 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 next-route reference;
• access timestamp and timezone;
• controlled storage location;
• file hash when your records process uses one; and
• handling note for identifiers, names, well data, legal descriptions, account data, or other sensitive information.

Do not publish an actual H-10 result, operator number, UIC number, API number, or property-specific record in a reusable worksheet. A controlled reference proves only what was retained for the recorded attempt.

Blank H-10 Query provenance worksheet

• Attempt ID: __________
• Purpose: public Search for H10 retrieval only
• Official entry routes: __________
• Menu and query-page labels: __________
• Access date, time, and timezone: __________
• Criterion labels and controlled values: __________
• Visible availability or date-range note: __________
• Navigation path: __________
• Result-header criteria: __________
• Displayed result range or limit: __________
• Sort, page, and page-size state: __________
• Result-row labels and controlled values: __________
• Displayed next-route 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 report, connects it to private property, or uses it for legal, title, land, regulatory, environmental, payment, 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, H10 Public Main, and Search for H10 routes are named;
• every submitted criterion retains its source label and controlled value;
• any availability, date-range, UIC/API, or lease/operator constraint is captured as shown;
• the navigation path records only steps that occurred;
• result headers, rows, detail links, and other query routes remain separate;
• the access timestamp, source limitation, and retained reference are attached;
• every status is only located, not located, or unverified;
• no row interprets a report, identifier, status, date, link, well, operator, or property relationship; and
• no row establishes title, ownership, acreage, unit inclusion, lease effect, payee status, payment responsibility, compliance, environmental condition, injection fact, production, 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 H-10 Query attempt. It does not decide what an H-10 report means.

Frequently asked questions

Does a located H-10 query result prove that a well, operator, or property has a particular legal, environmental, production, or payment status?

No. Located means only that the recorded official query exposed an identified result reference. It does not establish a property connection, ownership, title, permit effect, compliance, injection fact, volume, production, payee status, value, or a transaction result.

Does not located mean that no H-10 report, well, or record exists?

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

Can I publish a real operator number, UIC number, API number, report detail, or result row in a reusable worksheet example?

No. Keep query-specific identifiers and actual results in an authorized controlled reference. A reusable example should use blank fields and should not publish property-specific, operational, or sensitive records.

Can this worksheet determine a mineral-rights value, offer, sale, or investment decision?

No. It records query provenance only. It does not establish cash flow, price, value, offer quality, legal effect, payment entitlement, regulatory standing, or a transaction result.

Should I combine a Search for H10 result with an Injection Volume Query, violation search, or another RRC route?

No. Record each official route as a separate retrieval step with its own criteria, source limitation, access time, and bounded status. A shared identifier or label does not establish that the records have the same scope or meaning.

Sources

• Railroad Commission of Texas, Research Queries (accessed 2026-08-24)
• Railroad Commission of Texas, Annual Disposal/Injection Well Monitoring Report (Form H-10) Online Filing (accessed 2026-08-24)
• Railroad Commission of Texas, H10 Public Main (accessed 2026-08-24)
• Railroad Commission of Texas, Search for H10 (accessed 2026-08-24)
• Railroad Commission of Texas, H10 Public Queries Help (accessed 2026-08-24)