For developers and independent power producers navigating today's interconnection landscape, the most expensive surprises rarely show up in the original system impact study. They show up in the restudy.

Under FERC Order 2023's first-ready, first-served cluster framework, projects are now studied together in annual groups rather than one at a time. The intent was to clear the backlog and bring more certainty to the queue. But clustering created a new dynamic that developers underestimate at their peril: when a higher-queued project withdraws, the assumptions underpinning everyone behind it can shift. Power flows redistribute. Network upgrade obligations get reassigned. And the cluster, or a portion of it, may need to be restudied.

Each restudy cycle carries real cost. There is the direct expense of additional engineering and the study deposits at risk. There is the schedule slip, often measured in quarters, that pushes back financing, equipment procurement, and commercial operation dates. And there is the strategic cost: a project whose interconnection cost estimate doubles between the cluster study and the restudy may no longer pencil out at all, forcing a withdrawal that triggers yet another restudy for the projects behind it. The churn compounds.

Why restudies cascade

The mechanics are straightforward once you see them. A cluster study models all projects in the group as if they will be built. Network upgrades and cost allocations are calculated against that combined footprint. When a project drops out, whether because its own economics failed or it couldn't meet a readiness milestone, the electrical picture changes for the remaining projects if upgrading is still in the planning scheme. Upgrades that were shared across ten projects may now be borne by seven. A constraint that one project's output relieved may reappear.

"The single biggest driver of restudy risk isn't the rules, it's the quality of the data going into the study," says Dr. Mehrdad Rostami, Director of Power System Studies at E Source. "When a project's interconnection request relies on optimistic power apparatus ratings and capabilities or an incomplete or low-fidelity model, it doesn't just create risk for that developer. It distorts the study for the entire cluster, and that distortion surfaces as a restudy nobody wanted."

Where engineering rigor pays off

The good news for developers is that a meaningful share of restudy exposure is self-inflicted and therefore avoidable. The lever is an upfront engineering discipline, applied before the interconnection request is ever submitted.

Three areas matter most. First, accurate and high-fidelity facility modeling: providing the transmission provider with a model that reflects how the plant will actually behave (inverter parameter settings, reactive capability, protection and ride thorough schemes) rather than a generic placeholder that triggers conservative assumptions and inflated upgrade requirements. Second, realistic equipment ratings: specifying ratings the project can actually achieve and sustain, so that the study reflects deliverable capacity instead of nameplate optimism that later forces revisions. Third, honest project readiness: entering the cluster only when site control, offtake, and permitting are mature enough that the project is unlikely to become the withdrawal that destabilizes everyone else.

"Developers who treat the interconnection study as an engineering exercise rather than a paperwork hurdle consistently see fewer surprises," Rostami adds. "Getting the quality model right the first time is far cheaper than discovering the problem in a restudy, and it builds credibility with the transmission provider that pays dividends across a portfolio."

A portfolio mindset

The smartest developers are also thinking beyond a single project. Because withdrawals are now the primary restudy trigger, the composition of the cluster you enter matters as much as your own readiness. Understanding the maturity and risk profile of neighboring projects, the historical withdrawal rates in a given region's queue, and the ISO’s or transmission provider's specific restudy provisions can inform which clusters to enter and when.

This is where regional expertise becomes a competitive advantage. The cluster study process is national in framework but highly variable in execution, and the restudy triggers, deposit-at-risk rules, and cost-reallocation mechanics differ meaningfully by transmission provider.

The bottom line

Restudies are an inherent feature of the cluster era, not a defect. They cannot be eliminated. But the exposure any individual developer carries is substantially within their control. Accurate models, realistic ratings, and genuine readiness reduce both the chance that your project triggers a restudy and the chance that you're caught in someone else's. In a process where a single restudy cycle can cost a project its viability, that engineering discipline is no longer optional, it's the difference between a project that reaches commercial operation and one that quietly leaves the queue after wasting a lot of budgets and efforts.

E Source's Grid Engineering and Interconnection team helps developers, IPPs and utilities strengthen interconnection requests, validate models and ratings, and navigate region-specific cluster study processes.