Texas pauses data-center grid approvals as requests hit 474 GW
On August 3, Texas Governor Greg Abbott directed the Public Utility Commission of Texas and the Electric Reliability Council of Texas to pause further approval of data centers advancing through ERCOT’s grid-interconnection process until they are audited. Axios’ account of the August 3 action states that ERCOT was considering more than 474 GW in connection requests—over five times its record peak demand—and that about 90% of new requests were from data centers.
The August 3 measure pauses an electric-grid approval, not data-center construction throughout Texas. Tom’s Hardware’s scope assessment likewise distinguishes the ERCOT hold from a statewide building moratorium and notes that projects outside ERCOT or operating without an ERCOT connection do not use the affected approval pathway.
Which projects the pause covers
The controlling test is whether a data center is advancing through ERCOT’s interconnection process. The directive prevents additional projects in that process from moving forward before verification; it does not suspend every permit, development or operating facility associated with the industry.
- ERCOT interconnection applicants: These projects are within the audit’s express scope. A connection cannot be approved until the required verification is complete, and noncompliance can lead to denial.
- Projects outside ERCOT: The directive does not establish an equivalent pause for areas of Texas served by other grids. Those developments remain subject to the rules and approvals that apply in their own service territories.
- Fully islanded projects: A facility that neither connects nor seeks to connect to ERCOT is outside the interconnection process. Merely proposing on-site generation does not create an exemption if the project also expects an ERCOT connection.
- Existing facilities: The directive contains no instruction to disconnect data centers already operating. An existing operator could still be affected if a new project or expansion requires an interconnection approval.
- Construction and local approvals: The order does not suspend zoning, building, environmental or water decisions statewide. Those separate processes can continue or impose their own restrictions.
The practical consequence is narrower than a construction ban but still substantial. A developer may be able to pursue site work or local permits while lacking certainty about whether, when or at what scale the facility can draw electricity from ERCOT.
Why 474 GW is not a demand forecast
The 474 GW total aggregates capacity requested by prospective large loads. ERCOT’s record peak, by contrast, measures the highest actual demand served by the system at one time. Comparing the two shows the scale of the screening problem, but it does not mean 474 GW of data-center consumption is operating, committed or expected to arrive simultaneously.
The distinction also explains why the queue can exceed the existing system peak by more than five times. An interconnection request describes power a project may seek under its proposed configuration; the audit is meant to determine whether each proposal is sufficiently documented and meets the applicable requirements before it advances.
The 90% figure requires similar care. The governor’s materials describe approximately 90% of new power requests as data centers; they do not say that data centers already consume 90% of ERCOT electricity. The number identifies the dominant type of applicant in the current request pool, not its present share of grid use.
What each developer must disclose
Abbott’s official audit directive requires PUCT and ERCOT to obtain five broad categories of information from each affected project. It also says the review became necessary because some data centers failed to comply with a state survey measuring water and power use.
- Public financial assistance: State and local tax incentives, grants, abatements and other public support already received or expected.
- Electricity demand and supply: Projected annual and peak consumption, expected dependence on ERCOT, and progress toward constructing or procuring on-site generation, including the generation type.
- Water and cooling: Projected annual and peak water use, intended water sources, reuse plans and the proposed cooling technology, including whether it is air-cooled, closed-loop or another water-efficient system.
- Community protections: Noise mitigation, lighting controls, setbacks, traffic improvements, emergency-response coordination and other measures addressing effects on neighboring properties.
- Ownership: The entities holding ownership and controlling interests in the project.
Disclosure alone does not guarantee approval. The directive says projects that fail to comply with the audit, PUCT and ERCOT requirements, or state law must be denied a connection; compliant projects still have to pass the agencies’ reliability and interconnection review.
What remains unresolved
PUCT and ERCOT must now determine how the project-level verification will operate and which applications can resume advancing. The August 3 directive does not provide a completion deadline, a public audit schedule or a list showing the status of individual projects.
That leaves developers with two separate questions: whether their submissions satisfy the new information requirements and whether the grid can support the requested connection. A project can clear the disclosure review yet still face limits arising from location, transmission capacity, timing or other interconnection requirements.
The confirmed position is therefore specific: additional data centers in ERCOT’s interconnection process cannot move forward without an audit, and projects that do not comply must be denied connection. The next material developments will be the agencies’ audit procedure, its timetable and their decisions on individual applications—not a statewide decision on whether data centers may be built.
Also read:
Subscribe to our newsletter
Get the latest Web3, AI, and crypto news delivered straight to your inbox.