Home/How-to/Reading interconnection queues

How to Read PJM, ERCOT, and MISO Interconnection Queues for Construction Leads

A working guide to reading ISO/RTO interconnection queues as a BD tool: what the columns mean, which study stages matter, how to filter the projects that will never get built, and how to convert a queue entry into a pursuit.

Published July 6, 2026

Every generator and, increasingly, every large load that wants a permanent grid connection must file with its regional grid operator. The resulting interconnection queue is public, updated regularly, and filed 12–36 months before a facility needs power. That makes it the earliest structured record of construction intent that exists — if you know how to read it.

Where the queues live

Each ISO/RTO publishes its own queue in its own format. PJM exposes its serial service requests through a public queue portal; MISO publishes a generator interconnection queue with study-phase tracking; ERCOT publishes a monthly generation interconnection status report, and its large-load interconnection process is where new data center loads surface. The formats differ, but every queue answers the same questions: how much capacity, where, requested in-service date, fuel or load type, and current study status.

The stages that actually matter

A raw queue entry is a request, not a project. What separates real projects from placeholders is progress through the study process. The classic sequence — feasibility study, system impact study, facilities study — has been consolidated in most regions into clustered study cycles, but the logic is unchanged: each stage costs more, requires larger deposits, and demands more site control. A project that has entered a definitive-phase study with security posted is categorically different from one that just joined the queue. The exit milestone is an executed interconnection agreement — for large generators, an LGIA filed in a public FERC docket that enumerates the substation and network-upgrade construction the project will pay for.

Filtering the noise

Most queued capacity never gets built — historical completion rates across ISO queues are low, and speculative entries are common. Three filters do most of the work. First, queue position and study stage: weight late-stage projects heavily, raw entries lightly. Second, withdrawals: a project that survives a cluster study restructuring while neighbors drop out is showing commitment. Third, the developer entity: project LLCs can be traced to parents, and a parent with a construction track record in that region is worth more than a name you cannot place.

Reading load queues for data centers

The newest and least-competed signal is on the load side. Large-load interconnection requests — ERCOT's process is the most visible — surface data center campuses long before a rezoning or permit exists. A few hundred megawatts of requested load in a county with no announced project is a lead in its purest form. Pair the request with county land records and you frequently identify the site before the developer confirms anything. See our data center tracker and power sector coverage for how these signals cluster.

Converting an entry into a pursuit

A qualified queue entry gives you geography, scale, and timing. Geography narrows the AHJ to watch for permits. Scale sizes the trade packages. The requested in-service date lets you work backward: energization minus construction duration minus procurement gives you an approximate EPC award window, and the weeks after that award are when sub-RFPs move. Doing this manually across PJM, ERCOT, and MISO is a standing research job — which is why ScopePlex parses the queues continuously and scores entries alongside permits and filings in the signal feed, built from the sources we monitor. If queue-stage leads would change what your team chases, start a trial and see this week's entries scored.