PJM Interconnection Timeline, Explained

PJM has moved from studying interconnection requests one at a time to batch cluster studies, working through its backlog in Transition Cycles before settling into periodic cycles. A project that misses a cycle’s readiness requirements can be pushed to the next cycle, adding a full cycle to its wait. Data center load in Northern Virginia adds pressure to the queue that most other regions don’t face at the same scale.

This guide assumes the general interconnection process — request, feasibility study, system impact study, facilities study, interconnection agreement — as background. What follows is specific to PJM: the largest RTO by footprint in the US, spanning all or part of 13 states and DC, and the FERC-jurisdictional transmission provider for the mid-Atlantic corridor.

From serial studies to Transition Cycles

PJM's queue had, like most RTOs, historically studied interconnection requests one at a time in the order they were filed — a workable model until the volume of renewable and storage requests grew far faster than the queue could process them, leaving a backlog stretching years. Ahead of FERC Order 2023's industry-wide cluster-study mandate, PJM restructured its own process around Transition Cycles: large batch studies specifically designed to work through the existing backlog, followed by a move to steady-state periodic cluster cycles for new requests going forward. The mechanics track the same logic covered in the general interconnection guide — feasibility, system impact, and facilities studies — just run for a batch of projects together rather than one at a time.

Readiness requirements matter more than filing date

A consequence of moving to batch cluster studies: PJM's process leans harder on readiness deposits and site-control requirements to keep speculative projects from occupying a study slot without a realistic path to construction. A project's queue position is necessary but not sufficient — whether it clears each readiness milestone on schedule now matters as much as when it was originally filed. Confirm current deposit amounts and readiness milestones directly against PJM's published tariff and queue documents before budgeting a project timeline around them; these are exactly the kind of figures that get revised between tariff filings.

The data-center dimension

PJM's footprint includes Northern Virginia's "Data Center Alley" — the largest concentration of data center load anywhere in the world — which adds a demand-side pressure most other US grid regions haven't faced at the same scale. That shows up two ways: generation interconnection requests inside PJM increasingly cite data-center demand growth as the driver, and PJM has also had to work through direct large-load interconnection requests from data-center operators themselves, a process that runs alongside (and shares transmission-planning attention with) the generation queue rather than through it. If a data center project's power plan depends on new PJM generation clearing the queue on a specific timeline, that assumption deserves the same scrutiny as an equipment lead time — see Data Center Power Equipment for how redundancy targets and equipment sizing interact with a project's power delivery timeline.

Where this diverges from other regions

PJM's Transition Cycle structure, its specific readiness-deposit tiers, and its data-center-driven large-load process are particular to PJM's own FERC-filed tariff — they don't transfer directly to MISO's Definitive Planning Phase or to ERCOT's non-FERC process next door. A project spanning PJM and a neighboring region needs its timeline built separately for each.

Frequently asked questions