PUCT, ERCOT, and Red Oak source rows
Texas Data Center and Large Load Power Signal Report
PUCT, ERCOT, and Red Oak public records organized into a company, utility, process-timing, and local-evidence screen for Texas large-load and data-center infrastructure follow-up.
large-load, data-center, utility, or local relevance
de-duplicated lead-export rows
loaded local agenda evidence
What this report answers
Which Texas public records point to large-load, data-center, power, utility, local-agenda, or follow-up infrastructure signals?
Source clock
PUCT, ERCOT, and Red Oak records are loaded as a signal baseline; TCEQ, water, utility, substation, and site-plan layers remain follow-up checks.
Built for
Source layers
Sample rows
Selected records from the report workflow.
These examples show the format and evidence discipline. The current report includes the working table, CSV fields, and source-date context.
Fields included in the report / CSV
The public page shows selected rows. The requested report and CSV include the sortable fields needed for account, county, project, source-date, and follow-up review.
What the source supports
A company, utility, jurisdiction, and process-timing screen for large-load and data-center infrastructure research.
A lead-export table that separates source/process owners from commercial account candidates.
A repeatable monitoring path for PUCT controls, ERCOT process materials, local agendas, and later TCEQ/water/utility evidence.
What the source does not prove
Construction starts, project spend, vendor need, energization date, final interconnection approval, exact load size, or contract award.
That every named company is the right buying account without direct project and stakeholder confirmation.
That TCEQ, water, utility, substation, and site-plan evidence is complete; those layers remain follow-up checks.
Report package
Request current rows
Request the Texas data center and large load power signal report.
Tell us the buyer segment, territory, and export format you need. We will scope the current report, companion CSV, app workspace, and any API/custom delivery path.
