Methodology

How EnergyNetWatch turns public oil and gas records into source-aware workflows without hiding source clocks, caveats, or record limits.

What public records can show

Who filed or reported the record.
Where the record is located when the source provides usable geography.
When the source record was filed, approved, updated, or reported.
Which county, operator, commodity, project, well, lease, or facility label appears in the source.
Which records deserve follow-up in a table, map, export, alert, or report workflow.

What public records cannot prove by themselves

Final construction status, in-service status, contract award, spend, or exact project economics.
A drilled well from a permit alone.
A company-wide total when source labels still need acquisition or subsidiary review.
Exact route geometry unless the source or matched GIS evidence supports it.
Live field activity when the source clock is stale or publication cadence lags field work.

Trust center

How the records become workflows

EnergyNetWatch does not treat every public row as the same evidence. The platform keeps source family, date basis, record stage, geography, operator label, and caveat close to the row.

Source collection

EnergyNetWatch starts with public state and federal records: permits, wells, production, operator names, infrastructure filings, source PDFs, GIS files, and regulatory tables. Each source keeps its own source clock and caveat.

Source clocks

A permit table, reported-spud table, production table, and infrastructure filing can all be current on different dates. EnergyNetWatch keeps those dates visible so one fresh source does not make every related metric look current.

Record normalization

Records are cleaned into app fields for filtering, mapping, joining, and export. Normalization does not erase the original source meaning; permit-stage rows, production rows, and project notices stay separate.

Operator labels

Operator names can vary across state systems, acquisitions, subsidiaries, and reporting labels. EnergyNetWatch shows source labels and uses reviewed grouping where a company-level rollup needs more care.

Permit vs production timing

Permits can show intent before drilling. Spuds can show drilling-start evidence. Production records usually arrive later. The platform separates those stages before ranking activity.

Infrastructure signals

A facility permit, T-4 pipeline permit, PS-48 construction notice, and state-source surface lead are different evidence types. EnergyNetWatch labels the basis before a row becomes a report, export, map point, or watchlist item.

Review model

Automation where repeatable. Review where claims matter.

Automated processing

Used for repeatable collection, parsing, normalization, source-date handling, and table generation.

Human review

Used where public content, operator grouping, caveats, source claims, and customer-facing reports need judgment.

Public samples

Selected and caveated examples. They are not the full app table, current export, or complete account list.

App access

Used for current records where available, maps, exports, alerts, saved workflows, and API-ready fields.

Detailed notes

Methodology pages

Updated 2026-05-04

Need the current table, map, or export?

Public methodology explains the rules. App access is where the current records, maps, exports, alerts, and API-ready fields live.

Request access