Landman Business | September 28, 2026 | 10 min read
well status change evidence log: The business question this workflow answers
A well status change evidence log helps a land team organize state regulator records, operator reports, permits, completion records, plugging records, production data, and internal notices. Its purpose is not to manufacture certainty. It creates a controlled packet showing the assignment, sources consulted, exact observations, administrative work completed, open exceptions, and the person authorized to make the next decision.
This distinction matters in distributed land operations. A reviewer should be able to reproduce the work without asking which portal result, document image, exhibit, email, or spreadsheet row supported it. Record the custodian, jurisdiction, collection, query, direct locator, page, access time, and document role. A result is useful only when another person can reopen it.
Define scope and acceptance before research begins
Name one asset or record group, one jurisdiction, a time boundary, the requested output, and the reviewer. “Check the file” is not a usable assignment. State whether the deliverable is a chronology, crosswalk, register, comparison, evidence packet, or exception queue and define the evidence required for review.
For example, an internal report calls a well inactive while the regulator portal still displays a producing status. Preserve both observations rather than choosing one because it looks newer or more complete. Quote the relevant source language, cite its page or screen locator, label each date by event, and ask the smallest question the reviewer must answer.
At minimum capture well identifier, jurisdiction, source status, status date, filing or order locator, operator statement, observed conflict, access time, reviewer decision. Store exact source values beside normalized and calculated working values. If a project uses a naming, matching, acreage, decimal, deadline, or status rule, record the approved rule and version. A derived value should never appear to be a transcription from the source.
Apply the topic-specific control
Record what each source calls the status and when. Do not translate regulatory, operational, and accounting status labels into one another without an approved mapping.
Put this control in both the assignment and the quality checklist. When a new image, corrected filing, later instrument, or reviewer direction arrives, log what changed, which observation it affects, and whether the question reopens. That history prevents a later document from silently rewriting the record.
Build a reproducible evidence trail
Begin with the custodian closest to the record and follow the project’s approved source order. Save the search inputs, filters, date range, result count, URL, document identifier, page, and retrieval time. If an index links to an image, inspect the image. Indexes may abbreviate parties, omit clauses, misstate page counts, or lag a correction.
Retain a working copy only when the engagement permits it. Use a stable file name tied to the asset and source, but keep the official locator too. A screenshot can preserve a changing display; it should not replace an available official document. If a portal fails, log the returned condition and plan a bounded retry. Temporary inaccessibility is not proof that a record does not exist.
Separate observation, working, and decision layers
The observation layer holds exact names, descriptions, dates, identifiers, amounts, decimals, acreage, status labels, and citations. The working layer holds normalized names, candidate links, approved calculations, and exception flags. The decision layer records reviewer disposition, scope, conditions, and date.
Do not overwrite a conflict to make a schedule look complete. Add a row for each source and observation time. Preserve punctuation, suffixes, aliases, tract calls, formation names, and source-specific identifiers before normalization. Label execution, acknowledgment, filing, recording, effective, notice, payment, production, approval, and access dates separately.
| Control |
Ready for review |
Return for correction |
| Scope |
One asset and deliverable are named |
The request is open-ended |
| Evidence |
Locator and page are repeatable |
The summary has no source |
| Dates |
Every value names its event |
Dates are blended |
| Differences |
Competing values stay visible |
One value replaced another |
| Handoff |
The question has an owner |
The reviewer must rebuild the file |
Work exceptions as a managed queue
Describe the field-level difference, the sources compared, searches performed, and evidence still needed. Avoid labels such as correct, invalid, same owner, expired, satisfied, or superseded unless an authorized reviewer made that decision. Neutral wording lets the reviewer test the evidence without first undoing an unsupported conclusion.
Give each exception an owner, next action, follow-up date, and status. Useful states are new, researching, waiting on source, ready for review, returned, and accepted. Define entry and exit criteria. “Ready for review” confirms packet quality; it does not resolve the underlying title, payment, regulatory, legal, or operational question.
A practical handoff example
Suppose one record uses a shortened party name and an effective date while another uses a fuller name and a recording date. Create two observation rows. Each receives its exact value, event label, locator, and access time. A comparison row may describe similarities and differences, but it should not collapse the records.
The handoff question can ask whether those observations may be treated together for this named deliverable, given the identifier and date differences. After review, store the reviewer, decision date, precise scope, and conditions. Retain the underlying observations so later staff can understand both the evidence and the limits of the decision.
Quality-control checklist
- Confirm the asset, jurisdiction, time boundary, output, and reviewer.
- Reopen every material locator and sample exact transcriptions.
- Label every date by event and every value by source role.
- Separate exact, normalized, and calculated values.
- Keep unresolved differences visible at field level.
- Assign every exception an owner and next action.
- Remove unsupported company facts and professional conclusions.
- Lead the handoff with the decision question.
Frequently asked questions
Can remote support maintain this workflow?
Yes. Trained staff can gather authorized records, index fields, preserve provenance, apply documented administrative rules, maintain exception queues, and assemble review packets. The assignment should reserve legal, title, payment, engineering, regulatory, and management judgments for the appropriate professional.
What if an official portal is unavailable?
Record the URL, query, time, and error. Use an approved alternate only when the assignment allows it, label that source by role, and retain a follow-up for the authoritative system. A failed search is evidence about an attempt, not an absence finding.
When is the item complete?
Completion follows the assignment’s evidence and acceptance criteria. A sent email, uploaded image, search result, or database row is progress. Close the item only when the required packet exists and the named reviewer accepts it.
Authoritative starting points
Use the official custodian relevant to the asset and jurisdiction. These sources help confirm terminology, coverage, identifiers, and access routes:
Closing standard
A durable well status change evidence log makes sources repeatable, differences visible, and the next decision explicit. It speeds review without turning an administrative inference into a company fact.
If your team needs help organizing land records, exception queues, and review packets, Book a free consultation.
