Texas Governor Greg Abbott orders statewide power grid audit and halts all new data center grid connection approvals pending completion. 474 GW of projects in queue are frozen.
Gov. Greg Abbott sent a letter directing the Public Utility Commission (PUC) Chairman Thomas Gleeson and Electric Reliability Council of Texas (ERCOT) President and CEO Pablo Vegas to run a full verification and audit of every data center advancing through ERCOT's interconnection process. No new data center moves forward until that audit is complete. Any project that fails the requirements set by the PUC, ERCOT, and state law will be denied connection to the grid.
Two factors drove the order: scale and a compliance gap. ERCOT is reviewing about 474 gigawatts of connection requests—more than five times the state's record peak demand—and roughly 90% of that new load is data centers. Gov. Abbott also pointed to data centers that failed to comply with the PUC's survey on water and power use under the General Appropriations Act as a reason for this directive, noting that the gap prevents regulators from making informed decisions.
The moratorium's true significance lies not in the pause itself but in what it exposes. ERCOT is holding 474 gigawatts of requests, more than five times the state's record peak, and no one expects all of it to be built. A large share is speculative, and that phantom load distorts planning and pushes costs onto everyone else. The audit questions—own power, own water, own capital, and real ownership—function as a viability screen. They sort projects that can stand on their own from those padding the queue. If a project is real and funded, this screening may actually help by clearing the noise ahead.
However, the viability screen comes packaged as a hard pause with no end date. A serious, well-capitalized project sits in the same freeze as a speculative one until the agencies act. There is no published standard for what will clear the audit. The directive lists what to collect but never says what passes. It gives no threshold, no score, and no line between a project that clears and one that gets denied. The governor says projects that fail the requirements will be turned away, but no one has written down what those requirements are. That leaves developers with nothing firm to aim for—a developer could answer every question in full and still not know if their answers are good enough.
A pause with no published criteria hands the agencies wide discretion, and wide discretion invites obvious concerns. The process can look like the government picking its favorites. Two projects with similar profiles may receive opposite decisions, and neither developer would know why. This is a due-process problem and a real business risk. Until the PUC and ERCOT publish concrete, measurable criteria, developers should treat the standard as unknown, document their projects against every factor the directive identifies, and be ready to press for equal treatment if a decision appears arbitrary.
The governor's letter directs the PUC and ERCOT to collect information from every data center project including ownership and control structures, incentive and abatement agreements, projected annual and peak power draws, on-site generation plans, water sourcing and reuse details, cooling designs, and community mitigation measures.
The order strikes directly at ERCOT's "Batch Zero" process. In a recent market notice, ERCOT stated that before the PUC's 20 August open meeting, it will request a good-cause exception to delay the "Batch Zero" timelines. ERCOT will no longer be notifying parties on 7 August how they will be classified in the "Batch Zero" interconnection study, inevitably delaying the study's commencement. ERCOT will consult with the PUC on next steps, and the PUC has not yet responded. That classification notice has been viewed as the gating step many developers were tracking toward closing and financing. Pulling it freezes a milestone that plenty of pending deals are built around.
All projects not yet interconnected are likely impacted. The question remains whether this letter will affect islanded projects that are not connected to the ERCOT grid.
Developers should build the audit file before being asked. ERCOT and the PUC will want ownership charts, incentive and abatement agreements, projected annual and peak power draws, on-site generation plans, water sourcing and reuse details, cooling designs, and community mitigation measures. Assembling these now prevents a request from stalling a project for weeks.
The audit reaches deep into ownership and control. If a change of control or an equity transfer is pending, expect it to draw attention and be prepared to show the full ownership chain. Gov. Abbott cited data centers that failed to comply with the PUC's water and power survey under the General Appropriations Act as a reason for the audit. If a project has not responded to that survey, or responded thinly, fixing that now is the fastest way to stay on the right side of this.
With no standard on the table, developers should ask the agencies, through comments or filings, to adopt objective, measurable benchmarks. Clear criteria reduce the risk of an arbitrary denial and give developers a way to test their projects.
Termination rights, drop-dead dates, closing conditions, and financing milestones tied to an ERCOT confirmation or classification notice now carry real timing risks. The 7 August classification notice is on hold, so developers should review their contract dates and identify where exposure exists. They should also review change of law and force majeure provisions to see if these notices trigger any of those clauses.
If a purchase agreement or financing depends on "Batch Zero" timing or there are tight delivery timelines for power, developers should get ahead of it with buyers, sellers, and lenders. A short extension or a standstill is easier to negotiate before a deadline hits than after. ERCOT's good-cause filing lands before the 20 August PUC meeting, where the PUC may set the path forward. That date is the next clear signal on timing and potentially on process.
Noise, lighting, setbacks, traffic, water, and emergency coordination are all in scope. Projects that demonstrate they are a good neighbor will move through this audit better than those that cannot.
Legally, the governor cannot directly halt grid connections or order these agencies to act. The PUC is an independent agency exercising powers the Texas Utilities Code grants it, not powers the governor hands down. ERCOT runs under the PUC's oversight by statute. Nothing in that structure allows the governor to freeze the queue or deny a project. That is why ERCOT files a good-cause exception, the PUC rules on it, and the PUC changes its own rules through its own process. The governor's letter reads like a command, but the legal action must come from the agencies, and even then, they may not have full authority.
The governor's real hold on this matter is the appointment power, which is complete. All five PUC commissioners are appointed by the governor to six-year staggered terms, and the governor names the chair. The governor has appointed every sitting commissioner, including the chair. Those deciding whether to follow the directive are the governor's own appointees, any of whom he can pressure to resign. That is why a letter with no direct legal force still moves the market.
The legal footing becomes softer here: the audit and pause hold up only if they fit inside the agencies' existing statutory authority. There is a plausible hook in Texas Senate Bill 6, which the governor signed in 2025. That law gave the PUC and ERCOT new power over large loads, including interconnection, study fees, and curtailment. An audit tied to interconnection screening probably fits there. However, the agencies themselves told the governor in July 2026 that they lack authority in key areas and asked the legislature to expand it. PUC Chairman Gleeson wrote that the PUC has not historically regulated end-users and needs new statutory power to do so. That admission cuts against any claim that a broad moratorium rests on solid existing authority. A developer denied a connection could argue the agency exceeded its statutory grant, and the agency's own words would help make that case. The missing standards make that argument stronger. A denial with no published criteria is easier to attack as arbitrary.
Developers should treat the pause as real for timing purposes because it is enforceable in practice. They should also preserve the authority argument for later use. If a denial or delay