LLIRadar

The changes.

A weekly diff of the committed record: changed ERCOT documents, new PUCT filings, queue movement, and unresolved or upcoming Batch Zero milestones. The generator publishes the source-bound facts directly. Older issues are a historical record; they are not current regulatory status.

Change record

Correction — August 27, 2026. Issues below are superseded for Batch Zero timing and for the proposed §25.194 capital terms. The PUCT granted ERCOT's three requested good-cause exceptions on August 20. ERCOT intends to notify each interconnecting DSP or TSP of conditional classifications by August 31; receipt starts dispute and reconciliation. August 31 is not a final-inclusion cut, final classification date, or customer filing deadline. ERCOT has not published a current final-report or MW-allocation date. The older study-completion projection is unsupported and is not republished here. Observed Energized (5,700 MW) and the June non-simultaneous monthly peak (3,900 MW) are different measures. Staff Item 206 struck the interconnection fee; security is greater-of. Read the current status.

No edition has been published in 20 days. The generator runs Mondays; the newest issue below is dated 2026-08-31. Anything that changed since then is not on this page. A quiet week and a stopped generator look identical here, and this one has stopped. Do not rely on older issues for current regulatory status.

2026-08-31

ERCOT large-load changes: 2026-08-31

Primary-source changes, docket filings, queue movement, and unresolved Batch Zero milestones from the committed record.

Batch Zero

  • 2026-08-31 (0 days away) [WITHIN 30 DAYS]: ERCOT intends to notify interconnecting DSPs/TSPs of each Large Load's conditional classification by this date. The conditional notice starts the dispute and reconciliation process in Planning Guide §9.3.1(2)(a)(i)-(iii). This is ERCOT's announced target in market notice M-A080326-02, not a new adopted rule deadline. (status: announced)
  • 2026-08-31 (0 days away) [WITHIN 30 DAYS]: The June 5 timeline deck projected a final inclusion cut on this date. Later primary-source actions changed the Batch Zero process. The August 20 PUCT order granted ERCOT's good-cause exceptions, and M-A080326-02 now uses August 31 for conditional-classification notices. Do not treat the older final-inclusion-cut marker as an operative deadline. (status: superseded)
  • 2026-11-01 (62 days away): QSA prerequisite gate for Q2-2027 energization: an ILLE seeking Initial Energization in April, May, or June 2027 must satisfy all Planning Guide §5.3.5 prerequisites by this date. The 2026-08-20 PUCT order lets ERCOT include Large Loads it conditionally classifies as base load in this assessment before final classification. In its 2026-08-20 filing ERCOT put 17 Large Loads, approximately 6,874 MW, as potentially eligible. Inclusion in a QSA does not by itself authorize energization, and approvals to energize remain paused for Large Load data centers and virtual currency mining facilities. (status: scheduled)
  • 2026-12-10 (101 days away): ERCOT states it will file the Batch Zero Eligibility Verification Report and the Community Impact Review Report on this date. ERCOT's pause on further approvals to energize Large Load data centers and virtual currency mining facilities runs “until the verification has been completed”, so this filing is the first stated point at which that pause could lift. This is ERCOT's announced plan in its 2026-08-20 filing in PUCT Project 59142, not an adopted rule deadline or a PUCT order. (status: announced)
  • 2026-12-17 (108 days away): The Commission open meeting ERCOT identifies for its Batch Zero Eligibility Verification Report and Community Impact Review Report. This is ERCOT's announced plan in its 2026-08-20 filing in PUCT Project 59142. No PUCT order sets this date, and no outcome for any project follows from the meeting being scheduled. (status: announced)

Source changes

No new or changed large-load source documents since the baseline.

PUCT filings

No new PUCT filings since the baseline.

Queue

No new ERCOT queue status report since the baseline. Latest report_date remains 2026-06-18.

2026-08-27

ERCOT large-load changes: 2026-08-27

Primary-source changes, docket filings, queue movement, and unresolved Batch Zero milestones from the committed record.

Read full issue

Batch Zero

  • 2026-08-31 (4 days away) [WITHIN 30 DAYS]: ERCOT intends to notify interconnecting DSPs/TSPs of each Large Load's conditional classification by this date. The conditional notice starts the dispute and reconciliation process in Planning Guide §9.3.1(2)(a)(i)-(iii). This is ERCOT's announced target in market notice M-A080326-02, not a new adopted rule deadline. (status: announced)
  • 2026-08-31 (4 days away) [WITHIN 30 DAYS]: The June 5 timeline deck projected a final inclusion cut on this date. Later primary-source actions changed the Batch Zero process. The August 20 PUCT order granted ERCOT's good-cause exceptions, and M-A080326-02 now uses August 31 for conditional-classification notices. Do not treat the older final-inclusion-cut marker as an operative deadline. (status: superseded)
  • 2026-11-01 (66 days away): QSA prerequisite gate for Q2-2027 energization: an ILLE seeking Initial Energization in April, May, or June 2027 must satisfy all Planning Guide §5.3.5 prerequisites by this date. The 2026-08-20 PUCT order lets ERCOT include Large Loads it conditionally classifies as base load in this assessment before final classification. In its 2026-08-20 filing ERCOT put 17 Large Loads, approximately 6,874 MW, as potentially eligible. Inclusion in a QSA does not by itself authorize energization, and approvals to energize remain paused for Large Load data centers and virtual currency mining facilities. (status: scheduled)
  • 2026-12-10 (105 days away): ERCOT states it will file the Batch Zero Eligibility Verification Report and the Community Impact Review Report on this date. ERCOT's pause on further approvals to energize Large Load data centers and virtual currency mining facilities runs “until the verification has been completed”, so this filing is the first stated point at which that pause could lift. This is ERCOT's announced plan in its 2026-08-20 filing in PUCT Project 59142, not an adopted rule deadline or a PUCT order. (status: announced)
  • 2026-12-17 (112 days away): The Commission open meeting ERCOT identifies for its Batch Zero Eligibility Verification Report and Community Impact Review Report. This is ERCOT's announced plan in its 2026-08-20 filing in PUCT Project 59142. No PUCT order sets this date, and no outcome for any project follows from the meeting being scheduled. (status: announced)

Source changes

PUCT filings

  • Docket 58481: 2026-08-24 -- PUC RULES & PROJECTS: VOID SEE ITEM 205
  • Docket 58481: 2026-08-24 -- PUC RULES & PROJECTS: Memo Requesting CR Void Item No. 204
  • Docket 58481: 2026-08-24 -- PUC RULES & PROJECTS: Staff Memo w/Draft Recommended Changes to Proposed Rule
  • Docket 58482: 2026-08-18 -- Modern Tex Consulting LLC: Comments of Modern Tex Consulting LLC on Performance Reporting and Evaluation Under Proposed 16 TAC § 25.521
  • Docket 59142: 2026-08-10 -- ERCOT: ELECTRIC RELIABILITY COUNCIL OF TEXAS, INC.’S REQUESTS FOR GOOD CAUSE EXCEPTIONS RELATING TO BATCH ZERO DEADLINES AND STATUS UPDATE ON ADDITIONAL MATTERS INCLUDING THE LONG-TERM LOAD FORECAST
  • Docket 59142: 2026-08-13 -- Matthew Horany: Public Comment of Matt Horany
  • Docket 59142: 2026-08-13 -- First Ammonia LLC: Letter regarding ERCOT's Requests for Exceptions Relating to Batch Zero Deadlines
  • Docket 59142: 2026-08-13 -- Octa Data Center Development Company LLC: Octa's Comments on ERCOT's August 10, 2026 Status Update
  • Docket 59142: 2026-08-16 -- Sandra Gail Gilbreath Wright: Public Comment – Audit Standards Required Under Governor’s Directive
  • Docket 59142: 2026-08-16 -- Pallara, Inc.: Comments of Pallara, Inc. on ERCOT's Requests for Good Cause Exceptions Relating to Batch Zero Deadlines
  • Docket 59142: 2026-08-19 -- Ionic Digital Inc.: Ionic Digital Inc.'s Comments Regarding ERCOT's Requests for Good Cause Exceptions Relating to Batch Zero Deadlines
  • Docket 59142: 2026-08-19 -- PowerHouse CloudPeak Venture Alpha LLC and PowerHouse CloudPeak Venture C LLC: Request for Commission Action on Batch Zero Eligibility (CloudPeak BZ-259 & BZ-180)
  • Docket 59142: 2026-08-19 -- Jordan Smith: Review of ERCOT's Interconnection Process for Large Loads
  • Docket 59142: 2026-08-19 -- Anthony D Smith: Review of ERCOT's Interconnection Process for Large Loads
  • Docket 59142: 2026-08-20 -- ERCOT: ERCOT UPDATES – GOOD CAUSE EXCEPTIONS FOR PGRR 145, BATCH ZERO VERIFICATION AND AUDIT PROCESS, AND COMMUNITY IMPACT REVIEW PROCESS
    (+2 more)

Queue

No new ERCOT queue status report since the baseline. Latest report_date remains 2026-06-18.

Superseded historical issues

These issue bodies are retained in the repository audit trail but are not republished here because they contain Batch Zero timing or ERCOT MW labels superseded by the August 27 correction above.

  • 2026-08-25-project-58481-item-206 · 2026-08-25-project-58481-item-206
  • 2026-08-08 · ERCOT large-load changes: 2026-08-08
  • 2026-07-06 · The week in data, 2026-07-06 (numbers-only edition)
  • 2026-07-01 · Batch Zero is locked, the queue jumps to ~466 GW, and the ILLE clock reads 9 days
  • 2026-06-11 · lli-radar #1: The Queue Nobody Else Publishes, and a 28-Day Clock to Batch Zero

Public evidence example

See what the public record can support.

The public change record shows what moved. Project readiness still depends on the project's own facts and evidence. This frozen research example shows the source evidence, contradictions, unknowns, and public facts that would change the estimate. Radar changes can trigger new simulations or shadow decisions; they do not authorize production action or establish customer readiness.

Cipher Colchis18%at least 75 MW by 2028 Q2

Eight quarterly horizons show the estimated chance of energization and expected energized MW.

This first vintage is prior_only: intentionally wide, not calibrated, not a claim of ERCOT approval, and not based on private customer evidence.

Inspect the public exampleRead the method