Offset Activity Records: Building a Property-Connection Cross-Check

Direct answer

Choose one identified offset record, preserve its source, query criteria, retrieval date, and displayed status, then compare each displayed identifier and property-connection field with one named owner record. Label every field only match, mismatch, or unverified, and turn each mismatch or unverified result into a neutral clarification question. The cross-check does not prove ownership, development, production, payment, or value.

Key takeaways

• Cross-check one offset record at a time and preserve the exact source, query criteria, retrieval date, and displayed status.
• Compare individual fields rather than treating a nearby map point, shared name, or permit as a complete property match.
• Use only match, mismatch, or unverified; a field match is not a title, drilling, production, payment, or value conclusion.
• Stop before probability, timing, future-location, DCF, valuation, offer, or transaction analysis.

Cross-check boundary. This article explains how to compare the displayed fields in one identified offset-activity record with records for an owner’s property. It does not prove ownership, title, depth rights, lease coverage, pooling authority, development, production, royalty entitlement, payment, value, or a future well. It is not a title opinion, legal opinion, reserve report, engineering study, tax opinion, appraisal, drilling forecast, or transaction recommendation. 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.

An offset activity property connection should be tested one field at a time. Start with one identified permit, wellbore, completion, producing record, or operator document. Preserve where and when you found it. Then compare each displayed identifier, location reference, date, and record label with one named record for your property.

Use only three results: match, mismatch, or unverified. A match means two displayed field values agree. It does not mean the nearby record belongs to the owner’s tract, controls a private instrument, predicts a well, or proves value.

Start with one record, not an area story

Do not begin with “activity is strong nearby.” That statement combines many possible records and already leans toward a development conclusion. Begin with a record you can identify precisely.

Create a source header before comparing anything:

Source-header field	What to record
Source system	The exact query, viewer, filing system, or operator document used
Record identifier	The displayed API, permit, status, lease, unit, well, or filing identifier
Query criteria	The filters or identifiers entered to retrieve the record
Retrieval date	The date the record was opened or downloaded
Displayed status	The status shown by the source on that date
Saved evidence	The permitted URL, PDF, screenshot, or export used for the comparison

This header prevents a later reviewer from confusing a current record with an amended filing, a historical result, a different wellbore, or a similarly named lease.

Keep record identities separate

The Railroad Commission of Texas provides separate research paths because permit applications, wellbore identities, completion records, map features, and production reports answer different questions.

The Commission’s Drilling Permit Query Results Help describes displayed fields such as API number, permit status, lease, wellbore profile, filing purpose, amendment indicator, and total depth. It also explains that detail links can lead to additional wellbore, operator, lease, and related records. Record the field you actually observed; do not collapse every linked page into one “well record.”

The Wellbore Query exposes a different set of query controls, including oil or gas, district, lease or gas-well ID, county, field, operator, drilling-permit number, API number, and current or historical scope. A name match from one query is not a substitute for an identifier from another.

If two source systems display different values, record a mismatch or unverified result. Do not silently choose the value that makes the property connection look stronger.

Build the field-level matrix

Use one row for one field. Identify both documents and copy only the displayed values.

Cross-check field	Offset record	Owner record	Result	Neutral question
API or permit number	Exact displayed identifier	Exact identifier if shown	Match, mismatch, or unverified	Which filing identifies the record being compared?
Operator	Displayed operator and date	Operator shown in the named owner record	Match, mismatch, or unverified	Does the owner record refer to the same operator and period?
Lease or unit	Displayed name and number	Exact lease, unit, or declaration reference	Match, mismatch, or unverified	Which instrument connects these two labels?
County, survey, section, or tract	Displayed location reference	Exact legal-description field used	Match, mismatch, or unverified	Is the same survey, section, tract, or abstract shown?
Formation or depth	Displayed interval if available	Deed reservation, lease, or amendment field	Match, mismatch, or unverified	Does the owner instrument cover the displayed interval?
Relevant date	Submitted, approved, completion, or report date	Effective, recorded, amended, or statement date	Match, mismatch, or unverified	Which dates must align for this comparison?

Do not put an ownership conclusion, probability, value, or recommended action in the result column.

Define match narrowly

Mark match only when the displayed values for one named field agree after ordinary formatting differences are accounted for. Record the comparison source on both sides.

For example, an API number can match while the lease name remains unverified. A county can match while the survey or formation does not. An operator name can match while the dates cover different periods. Preserve those separate results.

A match is not a conclusion that:

• the offset well crosses or drains the owner’s tract;
• the owner’s minerals are included in a lease, unit, allocation agreement, or payment account;
• a private deed or reservation has been interpreted correctly;
• a future location will be drilled or completed;
• production belongs to the owner; or
• the interest has a stated value.

Those questions require different records and, in some cases, qualified legal, land, engineering, accounting, or appraisal work.

Preserve mismatches instead of repairing them

Mark mismatch when both sources display values for the same field and those values differ. Copy both values exactly enough for a reviewer to retrieve them. Do not change a digit, expand an abbreviation, merge two names, select a later date, or replace a source until the records appear consistent.

Useful mismatch questions are neutral:

• “Do these API numbers identify the same wellbore?”
• “Does this lease label refer to the same regulatory lease or pooled unit?”
• “Which recorded instrument supports the survey or tract connection?”
• “Does the depth language in the owner record include the interval shown in the offset filing?”

Avoid questions that already announce the answer, such as “Why is the permit wrong?” or “Why was my tract excluded?”

Use unverified when a required field is absent or incomparable

Mark unverified when one side does not display the field, the field labels are not comparable, the source is unavailable, or the record version is unclear. Unverified is not a weak match and not a mismatch. It means the current record set cannot support that field comparison.

If a private instrument does not show an API number, do not infer one from a nearby map point. If a royalty statement shows a lease number but not a tract or depth, preserve the lease-number comparison and leave tract or depth unverified. If an operator presentation uses a project name that does not appear in regulatory or owner records, keep the project-name connection unverified.

Treat map proximity as a locator, not proof

The Commission’s Public GIS Viewer can help locate oil, gas, pipeline, survey, lease, and related map features. The agency also states that its GIS data is informational, may be approximate, is not intended as an authoritative public record for a geographic location, and has no legal force or effect.

Use a map point or line to find the record identifier that should be checked. Preserve the layer, feature identifier, retrieval date, and map limitation. Do not use screenshot proximity alone to mark a tract, unit, lease, depth, or ownership field as matched.

The live acreage-contiguity guide owns the broader question of how connected acreage and development context may be reviewed. This cross-check does not repeat that analysis. It asks only whether one displayed offset-record field connects to one displayed owner-record field.

Keep production reporting limitations in the row

If production is part of the offset record, record the reporting level and period. The Commission’s Production Data Query System FAQs explain that Texas oil production is reported by lease rather than individual well, that online data has a reporting lag, and that reported information can change as revised, corrected, or delinquent reports arrive.

A lease-level production row should not be presented as individual-well output unless the source supports that attribution. A current query result should carry its retrieval date. A revision should remain traceable rather than overwriting the earlier observation without explanation.

Production agreement with a lease label does not prove that the owner receives the production, owns the listed decimal, or participates in every well on the lease. Those connections remain separate fields.

Stop before development or valuation analysis

The cross-check is complete when every selected field has a source on each side, a result, and a neutral question where needed. Stop if the next step would:

• grade or rank development evidence;
• assign drilling probability or timing;
• infer operator plans or capital allocation;
• count future locations or create type curves;
• place a nearby well into a DCF or valuation scenario;
• determine reserves, economics, ownership, title, or payment entitlement;
• analyze an offer; or
• recommend whether an owner should sell, hold, sign, negotiate, or transact.

The existing-wells and future-locations guide addresses the later modeling boundary. It assumes the underlying record identity has been established. This article supplies only the earlier field-level diagnostic and does not carry any record into a model.

Review the completed cross-check

Before sharing it, confirm that the matrix:

• covers one identified offset record;
• preserves the source system, query criteria, retrieval date, and displayed status;
• names the owner record and displayed date or version used for each comparison;
• uses one row per field;
• limits results to match, mismatch, or unverified;
• treats map proximity only as a locator;
• preserves lease-level production and revision limitations;
• turns mismatches and unverified fields into neutral questions;
• excludes personal data that is unnecessary for the review; and
• contains no title, drilling, production, payment, value, offer, or transaction conclusion.

The matrix can make a review question easier to reproduce. It cannot decide which instrument controls, prove that an offset record belongs to an owner’s property, or predict what will happen next.

Source notes

• RRC Drilling Permit Query Results Help supports the limited descriptions of displayed permit-query fields, current status, detail links, and record identifiers used above.
• RRC Wellbore Query supports the listed query criteria and the distinction between current and historical searches.
• RRC Public GIS Viewer supports the map-view description and the agency’s informational, approximate, non-authoritative, and no-legal-effect limitations.
• RRC Production Data Query System FAQs support the lease-level oil-production, update, lag, and revision limitations.

For a bounded review of one identified record and the property documents you are authorized to share, request an underwriter review. Bring the original records with the cross-check; do not replace them with the matrix.

Frequently asked questions

What is an offset activity property-connection cross-check?

It is a field-level comparison of one identified regulatory or operator record with one or more named records for the owner’s property. It preserves the source and compares displayed identifiers, location references, dates, and record labels. Each field is marked only match, mismatch, or unverified.

Does a nearby well or permit prove that my minerals are connected to it?

No. Proximity, a shared lease name, or a matching county can create a question, but it does not by itself prove tract inclusion, depth rights, lease coverage, pooling authority, ownership, royalty entitlement, future drilling, production, payment, or value.

What does match mean in this cross-check?

Match means only that the displayed value for one named field agrees with the displayed value in the specified owner record. It does not validate either record, resolve a conflicting instrument, or establish the legal or economic effect of the match.

Can I use the cross-check to estimate development probability or value?

No. This workflow stops before development-potential classification, probability or timing assumptions, future-location modeling, type curves, DCF, appraisal, offer analysis, or transaction recommendations.

What should I do with a mismatch or unverified field?

Record the exact field, both displayed values or the missing value, and one neutral clarification question. Route the question to the relevant qualified reviewer without changing a document or deciding which record controls.

Sources

• Railroad Commission of Texas, Drilling Permit Query Results Help (accessed 2026-08-23)
• Railroad Commission of Texas, Wellbore Query (accessed 2026-08-23)
• Railroad Commission of Texas, Public GIS Viewer (accessed 2026-08-23)
• Railroad Commission of Texas, Production Data Query System FAQs (accessed 2026-08-23)