Plain-English framing of two related deadlines. ERCOT (the Texas grid operator) has historically used a process called the Large Load Interconnection Study, or LLIS, to evaluate new electrical loads above 75 MW. A developer building a new hyperscale data center submits a study application; ERCOT runs power-flow analyses; if approved, the developer gets to connect. The whole LLIS framework was designed for industrial customers in the 5-50 MW range and stretched, awkwardly, to cover the hyperscale wave starting in 2023. Batch Zero (PGRR145) replaces LLIS. After July 10, 2026, no new LLIS applications are accepted — the old pathway is closed. A developer who wants to be 'in the queue' under the old rules has 24 days from today to file. After that, every new large-load project routes through Batch Zero, which is the new framework PUCT will formally approve on June 18. The second July 10 deadline. The new Batch Zero process requires 'dynamic models' — detailed electrical engineering simulations of how a data center's load behaves under transient grid conditions (voltage dips, frequency events, etc.). These models are mandatory for any project participating in the first Batch Zero cycle. July 10 is also the deadline for those model submissions. Developers who don't have dynamic models built and submitted by July 10 are deferred to the next Batch Zero cycle, which adds 6-12 months of schedule risk. What changes after July 10. Three things: (1) Any developer holding off on LLIS submission to wait for the new rules has now run out of optionality — submit by July 10 or accept Batch Zero. (2) The dynamic-model requirement is a new engineering deliverable most developers haven't built before; the cost is $50K-$200K per project for the electrical engineering work plus 4-8 weeks of lead time, which means projects starting the model build now are already tight. (3) Texas Transmission Service Providers (TSPs) and Distribution Service Providers (DSPs) have until July 24 to finalize the Batch Zero eligibility packages they submit to ERCOT on behalf of the developers in their service territory.
Primary source · ZeroEmissionGrid (Batch Zero Readiness 06-11-26) / EPE Consulting / Foley & Lardner / Keentel Engineering ↗
Why it matters
Cliff's stated near-term wedge is live docket intelligence + interruptible-load math, driven by the April-July 2026 ERCOT deadlines. The wedge is most valuable in the 3-4 weeks immediately after the PUCT vote, when developers have to make binding submissions under unfamiliar rules. Three product moves: (1) The Cliff docket page for Batch Zero needs the five-deadline table above as a permanent header — not buried in the body — because a developer hitting the page on July 8 needs to see 'Jul 10' immediately. (2) The dynamic-model requirement is the single highest-friction technical deliverable in Batch Zero; Cliff should publish a short explainer on what a dynamic load model actually is (with example IEEE-style block diagrams), what consulting shops can build them in 4 weeks vs. 8, and what a developer should pay — that's exactly the unstructured-regulatory-text-meets-engineering content where the LLM ingestion advantage compounds. (3) For sites in the Cliff CRM that have an ERCOT interconnection in process, the wiki should auto-tag whether the developer has filed LLIS or is targeting Batch Zero — that's the operational state every TX call should start from.
Related filings
VA DEQ Tier 4 / HB 507 / Jul 1 2026 effective / SCR + DPF + CEMS required / non-emergency designation
Plain-English framing. A 'backup generator' at a hyperscale data center is a diesel or natural-gas engine that turns on if utility power fails. A typical 100 MW hyperscale campus has 40-80 of them. Historically, these were treated as 'emergency' generators —...
Oracle sued Wisconsin PSC Jun 19 Ozaukee County / challenging April tariff rule / $100M/year financial security / very large customer >20 MW sub-A credit / Oracle BBB / Port Washington $15B 672 acres 1 GW 4 buildings We Energies / statutory-authority + discrimination + due-process theories / parallel administrative reconsideration / first hyperscaler-vs-PSC ratepayer-protection lawsuit / template for VA SCC MD FERC IL DCIP TX SB6 / AWS BBB+ adjacent risk / expected 6-12 months to ruling
Plain-English background on why this lawsuit matters more than a single facility dispute. Multiple states have enacted or are enacting 'ratepayer protection' rules for hyperscaler-scale customers in 2025-2026: Virginia's SCC rate class (approved Nov 2025,...
T-7 ERCOT ILLE Form W Jul 10 / T-21 Form W step 2 Jul 24 / PJM 2028-29 auction closes Jul 7 / results Jul 14 / price band $175-325 MW-day / 13-state governor pre-negotiated band / MD FERC ratepayer complaint comment deadline Jul 27 extended / NY A11560 not delivered to Hochul / 10-day clock not started / passive enactment plausible / 4 deadline-anchored windows next 24 days
Plain-English background on why the four operational-track deadlines all matter this month. Each of these deadlines drives a specific action by developers, hyperscalers, or state parties, and each represents a concrete moment where Cliff can produce a...
T-8 to Jul 10 ERCOT ILLE Form W deadline / Form W Part A now posted Large Load Integration page / notarized to TSP DSP / miss = 438000 MW proposed queue 89% data centers 3-5 years slower / Jul 24 TSP DSP to ERCOT step 2 / Microsoft Fairwater Mount Pleasant WI fully operational Jun 23 / 3.3B first phase / Brad Smith world's most powerful supercomputer / MISO not PJM / low friction state routing / 550 FTE 10000 construction workers / capex not slowing on T+0 morning / state-vs-federal misalignment produces geographic sorting
Plain-English background on the operational track. Yesterday's newsletter covered the regulatory calendar (VA tax, IL DCIP freeze, FL SB 484, Trump EO 14318, PJM auction open, ERCOT Batch Zero deadlines, Abbott Texas memo). Today's operational read is about...