Source proof
Every report separates what the public record proves from what it cannot prove.
Signal reports are packaged public-record reviews for teams that want lead lists, project screens, operator activity summaries, infrastructure watchlists, or territory-specific intelligence.
Every report separates what the public record proves from what it cannot prove.
The public page shows the shape; request access for the current report, CSV, and app workspace.
Built for teams that need account, county, project, facility, or infrastructure follow-up.
Report categories
The report page is the public preview. The current report, CSV, and app workspace are requested when a team needs current rows for a territory, source family, market segment, or account list.
PS-48, T-4, route-system, mileage, product, operator, county, and timing records organized for infrastructure follow-up.
APDs, reported spuds, facilities, gas-waste rows, gathered-volume context, operators, counties, coordinates, and source-date caveats.
PUCT, ERCOT, local-agenda, utility, jurisdiction, process-window, and later TCEQ/water/substation checks for Texas power demand.
What you receive
Signal reports sit between public examples and the app workspace. They prove the commercial use case, then point teams toward app access, monitoring, CSV delivery, or API scoping when needed.
Current packages
These public previews show the format, source basis, caveats, and request path. The current working rows, CSV, and app context are delivered through the report request.
Request a sample signal reportTX/NM midstream project signals
A current, source-backed register of verified company projects, federal named projects, Texas pipeline construction notices, and Texas facility activity. New Mexico permit and spud activity remains supporting context and is not counted as midstream project rows.
New Mexico Permian signal report
New Mexico APDs, reported spuds, OCD facilities, gas-waste rows, gathered-volume context, beneficial-use rows, operators, coordinates, and caveats organized for Eddy and Lea follow-up.
Texas power and AI infrastructure signal report
Track Texas data-center and large-load projects with PUCT, ERCOT, and local public records covering companies, utilities, timing, and evidence limits.
Delivery boundary
EnergyNetWatch does not publish the full working report table as a static article. The page gives enough proof to evaluate the workflow. The current CSV, report, and app context are delivered through request access or a scoped report package.
High-level proof, selected sample rows, source caveats, and request path.
Ranked current rows, source dates, rollups, caveats, and next checks.
Sortable source rows and fields for account, county, source, and timing review.
Maps, saved lists, exports, alerts, assistant answers, and API scoping where approved.