Interconnection queues
Compare official queue publications across all seven organized markets, then inspect county, project, publication, and history detail without losing source semantics.
Open the public queue view- Status
- Live
- Access
- No account required
- Reading time
- 14 minutes
- Reviewed
- Sep 1, 2026
- Maintained by
- Grid intelligence
The national interconnection layer combines official queue publications from ERCOT, CAISO, ISO-NE, MISO, NYISO, PJM, and SPP. Shared county capacity, project counts, technologies, and normalized active, completed, and withdrawn groupings make geographic comparison possible; operator, publication date, queue ID, native status, and project history remain attached to the source record.
A queue is a development process, not an operating-fleet forecast. Requested MW is not installed, accredited, deliverable, approved, or likely-to-complete capacity. Proposed dates and operator statuses must be read as fields from the stated publication, with exact project geometry shown only when the source supports it.
On this page · 5 sections
Compare all seven organized markets
Use national scope to compare geography and published queue scale before opening an operator-native record.
Turn on the national queue
Open Map content, turn on Interconnection queue, and use National grid scope to see supported organized-market publications together. County shading summarizes requested capacity under the active technology and status filters.
- 1Open any market map and choose National grid scope.
- 2Under Infrastructure, turn on Interconnection queue.
- 3Filter by technology or normalized status only when the comparison requires it.
- 4Select a county to compare the operator publications present there.
Keep overlapping markets separate
A county can intersect more than one organized-market footprint. The county card lists each operator's publication date, project count, active requested capacity, and total requested capacity separately, then routes each project row to its native queue record.
Know the coverage boundary
The layer covers the seven organized US markets supported by Ask the Grid. Areas outside those footprints require additional utility or balancing-authority publications and do not become zero-capacity counties merely because they are absent.
Configure an operator view
Enter one market when the workflow depends on its publication controls, native statuses, or project fields.
Preserve operator-native status
The common layer groups statuses for discovery, but the project card retains the exact status published by the operator. Use the native value and publication date when describing one project.
Replay the available publication
Where the market supports historical snapshots, move the map clock into the past to load the queue publication available then. Do not use a later snapshot to describe what was knowable at an earlier date.
Use delivery horizons as schedules of intent
A future horizon can show active projects whose proposed completion date falls inside that window. It is a filter over published developer or operator dates, not a forecast that those projects will reach commercial operation.
Move from county to project
Read the county aggregate
The county card separates project count, requested MW, publication date, delivery cohorts, and changes from the prior publication where those measures are available. Read the map-time label before comparing counties or screenshots.
Open the native project row
Select a project from the county list to open its queue ID, developer or interconnecting entity, technology, requested capacity, status, proposed point of interconnection, queue date, proposed completion date, and other market-published fields.
- 1Select a shaded county.
- 2Confirm the operator, publication date, and active filters.
- 3Open one project row.
- 4Use the back action to return to the same filtered county list.
Ask about the selected record
Attach the selected county or project to the agent and ask a precise question such as which active battery projects match the current county filters or what changed across publications. The agent uses the canonical queue table rather than treating the visible card as the only evidence.
Inspect project history
Compare official snapshots
Project history follows the stable queue ID across publications and surfaces changes in status, requested capacity, proposed dates, or other reported fields. A missing project in one publication requires source-specific interpretation; it is not automatically proof of withdrawal or completion.
Use location evidence at its real precision
Some queues provide detailed points of interconnection or project locations; others support only a county or another approximate geography. A county centroid is a navigation anchor, not exact project geometry or evidence of thermal headroom, feasibility, or study outcome.
Interpret queue values correctly
Requested MW is not operating capacity
Queue capacity measures an interconnection request under the source publication. It does not establish construction, commissioning, commercial operation, accreditation, deliverability, available transmission, or the probability of completion.
Dates and statuses need attribution
Write that the operator publication lists a proposed date or status. Completed can describe a queue-process state without independently proving that the facility is online, and a proposed in-service date remains reported rather than observed.
Compare like with like
Before ranking markets or counties, align publication dates, status inclusion, technology filters, treatment of uprates or withdrawals, and whether the measure is project count or requested MW. A larger queue is not automatically a stronger development pipeline.
Did this guide get you unstuck?
One click is enough. No message or account required.