ERCOT held the first of two workshops presenting a draft batch-study framework for large-load interconnections.

For data centers—and the generators planning to serve them—the workshop clarified several design choices that seem worth highlighting:

Five takeaways from the workshop:

1. Dispatchable load and co-located generation will be evaluated inside the batch framework. ERCOT indicated that controllable load, minimum-firm-plus-dispatchable configurations, and load paired with on-site or co-developed generation will be modeled within the batch studies themselves, rather than through separate or parallel pathways. Data centers willing to commit to a firm floor with dispatchability above that—and generators pursuing true co-development—stand to benefit in constrained areas because the batch model is designed to maximize served load subject to constraints and to condition load energization on associated generation actually being in service. While some of these projects might prefer a path entirely outside the batch to move faster, ERCOT’s stated direction is to internalize these concepts within a single, enforceable framework.
2. Batch results will specify how much load can be served by year, not just whether interconnection is feasible. ERCOT stated that study outcomes will identify MW availability for each project across Years 1–5, making ramp timing and partial service explicit rather than leaving those questions to later restudies or negotiations.
3. Constraints identified in the batch are not assumed to persist indefinitely. ERCOT made explicit that full requested load is assumed to be serviceable by Year 6 through normal regional transmission planning processes, rather than remaining subject to batch-level limitations beyond the near-term horizon.
4. Allocation outcomes will be determined centrally through an ERCOT-run batch process. While ERCOT has always overseen reliability, the workshop clarified that MW allocations for large loads will come out of an ERCOT-led batch framework, replacing the current dynamic where sequential TSP studies are repeatedly overtaken by later requests.
5. Maintaining a six-month batch cadence requires trade-offs developers should plan for now. To keep the process moving, ERCOT signaled shorter post-study commitment windows and reliance on stability screening rather than full stability studies at the batch stage—choices that directly affect financing timelines and development sequencing.