Production and Drilling Data
A decision-grade, source-backed study of Texas W-3A notice-of-intention-to-plug record lineage, with reproducible controls, limitations, and land-work applications.
10 official source routes
5 evidence layers
Checked September 23, 2026
How should a land team connect a Texas W-3A notice of intention to plug with the correct well identity, operator filing, plugging event, and later agency record without treating notice, work, and acceptance as one event?
Texas plugging research spans form instructions, well queries, organization records, document images, and plugging-status materials. A reliable chronology preserves the API number, district, lease and well numbers, operator number, filing role, proposed work, agency dates, and the later record that documents what occurred.
The operational decision is whether the file contains enough traceable evidence for the responsible land, regulatory, legal, environmental, engineering, or commercial reviewer to evaluate the record against the correct vintage. This study does not decide title, ownership, boundaries, approval, compliance, operating authority, environmental sufficiency, accounting, payment entitlement, or legal effect. Those judgments remain with the qualified professional responsible for the file.
Land and energy work often combines a search result, submitted form, agency image, downloadable row, map layer, and current status screen. Those artifacts were created for different purposes. They may all be accurate while describing different events. A current display can help locate a file, but it cannot reconstruct an amendment, transfer, correction, approval, expiration, or historical status that the display does not contain.
The practical risk is false continuity. A familiar name or stable asset number can make two records appear to describe an uninterrupted state even when the governing interest, location, operator, filing role, or effective period changed. The opposite error also occurs: minor formatting changes can split one record chain into several apparent assets. Both errors are avoidable when source-native evidence is preserved before normalization.
We reviewed ten current, publicly reachable, authoritative publisher routes on September 23, 2026. Five sources address the record family directly; five establish adjacent federal data, publication, or archival boundaries. The source set identifies record roles, research routes, form fields, rules, and limitations. It is not a statistical sample and does not measure agency accuracy, processing time, or prevalence of defects.
The unit of observation was one source artifact at one access time. Core fields were API number, district, lease number, well number, operator number, filing type, proposed plugging date, received date, approval or exception notation, completion evidence, and image locator. Source-native spelling, punctuation, leading zeroes, codes, date labels, and status labels were retained. Normalized comparison keys were stored separately with the transformation rule.
Candidate links were evaluated in descending order: exact identifiers from the same jurisdiction; explicit cross-references in official records; then corroboration across several independent fields. A matching name, nearby date, similar acreage, or geographic proximity alone remained a research lead. It was not promoted to confirmed identity.
| Evidence layer | Minimum capture | What it does not prove |
|---|---|---|
| Identity | jurisdiction and unaltered native identifier | that similar names are the same party or asset |
| Document | form role, version, page, and locator | that submission equals acceptance or approval |
| Event | publisher's event or status wording | that an internal label has a legal meaning |
| Time | date paired with its event label | that filing, approval, and effective dates coincide |
| Review | question, exception, owner, and next action | that administrative completion resolves the issue |
The first finding is that a system name is not adequate provenance. A query page, image repository, blank form, rule publication, case docket, map, and downloadable dataset expose different slices of the record. The ledger must name the exact route and artifact used. When a result points to an image, preserve both the result context and the image locator; neither replaces the other.
The second finding is that identifiers are evidence, not formatting. Store them as text. Leading zeroes, prefixes, suffixes, punctuation, and jurisdiction-specific layouts can carry meaning. A normalized key can speed comparison, but the original stays beside it. If values fail to join, create an exception instead of trimming characters until they match.
The third finding is temporal. A current display is a current observation and should not be copied backward into an earlier row. Reconstruct history from separately sourced events and label missing intervals. Submission, receipt, filing, approval, rejection, effective, completion, update, access, and review dates may all be valid while answering different questions.
The fourth finding concerns negative evidence. A search that returns no result proves only that the documented query returned no result through that route at that time. It does not establish that a record never existed, was never filed, or cannot be found through a historic identifier, different office, archive, subscription system, client file, or formal records request.
A fact in this workflow is a bounded observation: a named field appears on an official form, a publisher offers a specified research route, or a record displayed a stated value at a recorded time. Analysis compares facts, such as identifying different operator names, interests, locations, document roles, or date labels.
An inference proposes a relationship the sources do not state directly. It should explain why the link is plausible and what evidence would confirm it. Uncertainty records absent images, inaccessible systems, conflicting values, unclear versions, incomplete coverage, and undocumented intervals. These categories belong in separate fields rather than a single confident narrative.
This separation protects the decision boundary. A support team can locate, preserve, transcribe, compare, and route evidence. The authorized reviewer decides what the evidence means for the asset, interest, obligation, permit, or compliance question.
Begin with a scoped question and named decision owner. Record the jurisdiction and at least one native identifier before searching by name. For each search, capture the route, query terms, filters, access time, and result condition. Preserve permitted documents with a stable filename, retrieval timestamp, byte count, and SHA-256 hash.
Create one row per observation, not one row per presumed real-world event. Keep the displayed value and source label unchanged. Add normalized values only in separate columns. Link observations through a relationship table containing both identifiers, evidence basis, confidence category, analyst, review state, and next action.
Build chronologies from named events. If two sources conflict, retain both. Describe the variance at field level and mark any selected working value as provisional with reviewer and rationale. Never overwrite an earlier observation when a public record changes; append a new dated observation and state what changed.
A useful exception queue names the affected identifier, conflicting fields, material sources, decision at risk, owner, and next action. High-value exceptions include unexplained party-name changes, identifiers that differ after normalization, conflicting legal descriptions or interest scopes, missing attachments, amended filings without visible predecessors, and status changes without supporting decisions.
Before handoff, a second researcher should reopen a deliberate sample of material locators and confirm jurisdiction, identifier, document role, page, displayed value, event-date meaning, and access date. They should reproduce normalization from the saved original strings and verify that every proposed link states its evidence basis.
The packet should open with the decision question, then show identifiers, direct locators, material pages, original and normalized values, chronology, query history, exceptions, unavailable evidence, limitations, and the professional action requested. Another trained researcher should be able to repeat the material searches without oral context.
This review was limited to the public official routes listed below and checked on September 23, 2026. It did not test authenticated functions, every query combination, agency back-office systems, field-office paper records, county subscriptions, client documents, or the legal sufficiency of a particular filing. Interfaces, forms, rules, and documents may change after access.
No asset, operator, owner, permit, or filing population was sampled. This study therefore makes no claim about completeness, defect rates, processing time, ownership, acreage, boundaries, compliance, physical condition, production accuracy, royalty correctness, or entitlement. It presents a defensible research method, not a substantive determination for a specific property.
For Texas W-3A notice-of-intention-to-plug record lineage, the strongest deliverable preserves source identity, native identifiers, document role, event-specific dates, version, locator, conflicts, and inference limits. The goal is not the smoothest story. It is a review packet in which facts, analysis, inference, and uncertainty can be distinguished without retracing undocumented work.
No. A matching source-native identifier can strongly support record identity, but authority, title, compliance, accounting, and legal effect depend on the complete record and qualified review.
Yes. Trained support staff can retrieve authorized sources, preserve files, transcribe native values, document transformations, maintain exception queues, and assemble review packets while reserving professional judgments for the responsible reviewer.
Reopen it when a source changes, an amendment or later event appears, an identifier conflict emerges, the assignment scope changes, or the reviewer rejects the prior handoff. Preserve the earlier observations rather than rewriting history.
If your team needs help building a repeatable Texas W-3A notice-of-intention-to-plug record lineage workflow, Book a free consultation.
A decision-grade, source-backed study of New Mexico C-101 intent-to-drill record lineage, with reproducible controls, limitations, and land-work applications.
Verified 2026-09-28
A decision-grade, source-backed study of Oklahoma Form 1000 intent-to-drill record lineage, with reproducible controls, limitations, and land-work applications.
Verified 2026-09-28
A decision-grade, source-backed study of Oklahoma Form 1003 plugging-record lineage, with reproducible controls, limitations, and land-work applications.
Verified 2026-09-25
