Texas Paused the Data Center Grid Queue, and the Gate Is Paperwork

On August 3, 2026 Governor Greg Abbott wrote to Public Utility Commission of Texas Chairman Thomas Gleeson and ERCOT President and Chief Executive Officer Pablo Vegas with a directive in one sentence: the PUC and ERCOT must conduct a comprehensive verification and audit of all data centers advancing through ERCOT’s interconnection process before any additional data centers are approved to move forward. The letter states that ERCOT is considering approximately 474 gigawatts of requests to connect to the Texas grid, more than five times Texas’ record peak electricity demand for ERCOT, and that approximately 90 percent of the new power requests are data centers. It gives a trigger, which most coverage skipped: the failure of some data centers to comply with the PUC’s survey measuring water and power usage under the General Appropriations Act. And it sets out five categories of information to collect from each project, covering state and local tax incentives, grants and abatements received or expected; projected annual and peak electricity consumption and progress toward on-site generation; projected annual and peak water consumption, water sources, and whether cooling will be air-cooled, closed-loop or another water-efficient system; measures to reduce impacts on neighbors including noise mitigation, light controls, setbacks, traffic improvements and emergency response coordination; and the ownership and controlling interests in the project. Any project that fails the verification and audit, the letter says, must be denied.

ERCOT moved the same day. Market Notice M-A080326-01, issued August 3, told the market it would not meet the August 7, 2026 deadline to classify Large Loads in the Batch Zero study and would seek relief from the Commission. On August 10 it filed that request in PUC Project No. 59142, seeking three good cause exceptions under 16 Texas Administrative Code § 25.3(b) to the requirement of 16 TAC § 25.361(b)(16), so it could deviate from ERCOT Planning Guide §§ 9.3.1(2)(a), 5.3.5(5)(a)(ii) and 9.2.2(3)(a). The Commission granted all three on August 20, 2026 in an Order Granting Good Cause Exceptions signed by Chairman Gleeson and the commissioners. The order records what ERCOT intends to do with the time: temporarily pause the transitional Batch Zero interconnection study of loads that are 75 megawatts or more, including data centers and virtual currency mining facilities, until the verification and audit are complete, and separately request community impact information from all data centers and crypto facilities of 25 megawatts or more that have not yet energized. ERCOT told the market on August 21, in Market Notice M-A080326-02, that it intends to notify interconnecting distribution and transmission service providers of each large load’s conditional classification by August 31, 2026, which starts the dispute and reconciliation process in the Planning Guide.

The thing being audited is not capacity. It is documentation, and the list ERCOT filed on August 20 is one an acquisitions team would recognize on sight. To hold a Batch Zero eligibility path, a developer must show site control with evidence such as a deed, lease, purchase and sale agreement or option agreement; long-lead equipment ordered, supportable by purchase orders and delivery schedules; a notice to proceed showing the developer instructed the service providers to construct the required interconnection facilities; end-use customer confirmation, meaning a retail electric service agreement if the developer is itself the end user or a binding contract with the end user if it is not; site approvals such as orders, permits and resolutions, or a statement that no approvals are required; a binding general contractor contract; a binding substation contractor contract with the contractor’s electrical license; an affiliate form backed by an organizational chart and ownership documents; financial security confirmed by the transmission or distribution service provider; and satisfaction of contribution in aid of construction. ERCOT states it may conduct site verification, meaning physical inspection, of loads with a requested initial energization date before April 1, 2027. Those are ERCOT’s filed requirements, not a PSV interpretation of them.

The filing also sizes what is sitting still. Seventeen large load data center and crypto facilities, representing 6,608 megawatts of total peak demand ramping over five years, have finished every ERCOT process except approval to energize, and ERCOT has paused those approvals. Six large loads representing approximately 1,959 megawatts were expected in the August 1 quarterly stability assessment with projected energization in the first quarter of 2027, and a separate set of 17 large loads representing approximately 6,874 megawatts is potentially eligible for the November 1 assessment with projected energization in the second quarter of 2027. On the community impact side, ERCOT’s April snapshot counted 157 medium data center and crypto loads, those at least 25 megawatts and under 75, totaling approximately 8,766 megawatts. One number in the presentation is worth more than any of those to a developer: ERCOT says it has reviewed 290 dynamic models and approximately 18 percent were acceptable on first review. The consequence is stated without hedging. Large loads that do not pass verification, or do not respond, will be disqualified from Batch Zero.

The artifact worth building here is an interconnection evidence file kept per site, structured to the eligibility list rather than to a marketing deck. The inputs are documents a developer already holds, and the point of the exercise is finding which ones do not exist yet: the deed, lease, purchase and sale agreement or option that evidences site control and the parcels it actually covers; the purchase orders and delivery schedules behind long-lead equipment; the notice to proceed and the date it was issued; the retail electric service agreement or the binding end-user contract; every discretionary approval on the site with its issuing body and status, or the written basis for saying none are required; the executed general contractor and substation contractor agreements with the contractor’s license; the organizational chart and ownership documents that answer the ownership and controlling interests question; the financial security instrument and the service provider’s confirmation of it; and the contribution in aid of construction record. Alongside them sits the second file the Governor’s letter asks for, which most developers have never assembled in one place: every state and local incentive, grant and abatement received or expected, the projected annual and peak electricity and water consumption, the water source, the cooling technology by name, the on-site generation plan, and the noise, lighting, setback, traffic and emergency response commitments made to the host community.

The output is a single readiness sheet: one row per eligibility requirement, the document that satisfies it, the date and signatory of that document, the gap where no document exists, and the person who owns closing the gap. An assistant can assemble that sheet from a document set, cite the page behind every cell, keep it current as executed agreements land, and flag when a requirement moves from evidenced to unevidenced because a contract lapsed or a parcel changed. It should not draft an attestation. Several of these requirements are satisfied by a developer’s legal declaration that it meets them, which makes them a signature by an officer with liability attached rather than an output. The reviewer is the development lead working with counsel and the interconnection consultant, and the approval gate is that nothing is submitted to a service provider or to ERCOT on a machine-assembled record without that human signature. PSV has not audited any project in this queue, has no view on whether any particular load should qualify, and is describing a filed process rather than predicting its outcome.