Revenue and Royalty Data
A source-backed study of ONRR revenue periods, date semantics, provenance, limitations, and review controls.
10 public sources
5 evidence controls
Verified September 1, 2026
Which period and source fields are needed to compare federal revenue observations without mixing sales, production, and disbursement dates? This article treats ONRR revenue periods as a record-lineage problem: what a publisher displayed, which identifier and date give the observation meaning, and what must remain for an authorized reviewer.
The documentary review began with the primary public source and compared ten public federal and state research systems listed below. Each was accessed on September 1, 2026. The protocol recorded publisher, geography, record family, query path, stable identifier, original date label, displayed value, and coverage limitation. Review protocol 2 is specific to this study.
| Evidence field | Comparison rule |
|---|---|
| Identity | Match jurisdiction and stable identifier before names |
| Date | Preserve both the publisher label and value |
| Provenance | Keep publisher, locator, access date, and coverage together |
| Analysis | Store separately from the original observation |
| Decision | Leave to the authorized reviewer |
This is not a statistical sample of every lease, well, order, owner, payment, or jurisdiction. Public systems change, and some controlling evidence may require a document image, local repository, subscription, or professional interpretation. No missing result was treated as proof that an event or record does not exist.
One evidence row should represent one observation from one source at one access time. Preserve original identifiers and labels beside any normalized working values. This lets a reviewer reconstruct the query and see whether an apparent match depends on formatting, name similarity, map proximity, or a stable key.
Dates require semantics. Filing, recording, approval, execution, effective, hearing, production, sales, payment, update, and access dates can all be accurate while describing different events. A chronology should sort normalized dates only after retaining the publisher's label.
Begin with a narrow question and a stable asset key. Search the source most closely associated with the record family, capture its exact locator, and then use adjacent systems to test identity, timing, or context. Record search terms and filters. If a system reformats an identifier or omits older values, keep that limitation visible.
For candidate matches, compare jurisdiction and stable identifiers before names. Names change and abbreviate; maps generalize geometry; an access date does not prove an underlying event date. A working crosswalk should therefore include the match basis and a review state.
The review supports four operational findings. Provenance must travel with each value. Date labels determine whether two observations are comparable. Normalization helps sorting but can hide conflicts. Unresolved associations are safer in a review queue than forced into a yes-or-no conclusion.
The sources also demonstrate why absence statements must stay narrow. Results can depend on spelling, identifier formatting, geographic coverage, indexing delay, revision policy, and access path. A defensible note says exactly which source was searched, how, when, and what it returned.
Use an evidence ledger with asset key, publisher, source locator, original and normalized identifiers, date value, date meaning, access date, observation, limitation, match basis, reviewer question, owner, and next check. Link the underlying document where permitted and retain earlier observations when a public value changes.
Route each conflict to its actual decision boundary. Researchers can repeat searches, reconcile formatting, and assemble evidence. Land, legal, survey, regulatory, engineering, revenue, or commercial reviewers decide matters within their authority. The handoff should name the question rather than asking for a general review.
This study does not establish title, ownership, lease validity, regulatory compliance, well status, survey location, payment entitlement, or commercial approval. Public systems may be incomplete, delayed, revised, or organized under historical identifiers. Access on September 1, 2026 records the research date, not a warranty that each displayed value was current that day.
A daily review should prioritize new evidence, identity conflicts, aging dependencies, and questions waiting on authorization. Each update should explain what changed and why the next action belongs to its owner. Teams should sample locators before handoff and repeat material searches when the source or assignment changes.
Reliable land-support records keep the question, source, date, status, limitation, and next action together. That discipline gives working teams clearer review queues and reviewer-ready handoffs. See Landman Business services for supported workflows.
No. It documents only what the specified query returned through that source and access path on the research date.
Only after aligning jurisdiction, identifier, record scope, and date meaning. Otherwise, preserve both observations and explain the mismatch.
The authorized professional or business owner for that decision should resolve it using the evidence packet and its visible limitations.
For ONRR revenue periods, the defensible unit is a dated, source-specific observation with an explicit identifier and limitation. Comparisons can reveal gaps and next searches; they do not independently create a professional conclusion.
If your team needs help organizing a reproducible evidence ledger, Book a free consultation.
A source-backed study of ONRR revenue dataset units and periods, including methodology, evidence limits, and inference boundaries.
Verified 2026-09-10
An unexecuted research protocol defining evidence fields, source limits, and reviewer boundaries. It reports no completed sample or empirical findings.
Protocol reviewed 2026-09-07
An unexecuted research protocol defining evidence fields, source limits, and reviewer boundaries. It reports no completed sample or empirical findings.
Protocol reviewed 2026-09-04
