Quick answer
A network operator’s record of generation and storage connection requests and study status; queue entry or position does not establish approved capacity or an operating date.
Answer: An interconnection queue is a record of proposed generation or storage projects progressing through a network operator’s connection process. Entries identify requests and study status; they are not a list of approved operating plants. Study grouping, readiness requirements, priority and deadlines depend on the applicable rules. A queue number alone cannot establish a completion date, reserved capacity or permission to operate.
Queue entry versus an operating project
A project requests review of a specified connection and operating configuration. The operator evaluates network effects, possible works and applicable responsibilities. Study results, an interconnection agreement, required construction and operating authorization are separate milestones.
An entry may be active, suspended, withdrawn or operational according to the dataset’s definitions. Confirm the operator’s status labels and last update before drawing conclusions. An “active” project can still have substantial commercial, technical or permitting conditions to resolve.
Serial and cluster processes
The queue is not universally a simple first-come, first-served line. FERC’s Order 2023 explainer describes a U.S. transmission-interconnection reform toward first-ready, first-served cluster studies, financial readiness and site-control requirements, and restudies when relevant project changes or withdrawals occur.
That federal reform is a particular regulatory context. Consult the actual provider’s current tariff, accepted implementation and transition arrangements. Do not apply a transmission procedure to every rooftop distribution application or assume all countries use the same process.
A cluster studies multiple requests together. Shared network effects and changing assumptions can affect the group’s study results and cost allocation. A facilities-stage estimate is not necessarily a guaranteed final construction cost; read the applicable estimate, agreement and adjustment terms.
Reading a public queue record
| Field | Practical question |
|---|---|
| Request identifier | Is this the exact project and current request, rather than a superseded entry? |
| Status and update date | Which operator-defined stage does it represent, and how fresh is the record? |
| Proposed capacity | Is it generation, storage, DC/AC or another requested rating convention? |
| Point of interconnection | Which network location and voltage are proposed? |
| Study group/milestone | What is complete, pending, revised or dependent on other requests? |
| Target operation date | Is this a developer target or an accepted milestone with conditions? |
Use public data within its stated privacy and use limits. A queue table cannot replace the current project correspondence, study assumptions or agreement. Also distinguish hosting capacity screening information from project-specific acceptance; a favorable map result does not reserve a connection.
U.S. snapshot: dated capacity, not guaranteed deployment
Berkeley Lab’s 2026 Queued Up edition reports about 8,200 active requests at the end of 2025, representing 1,312 GW of generation and approximately 749 GW of storage. Those rounded capacity totals sum to about 2,061 GW, consistent with its headline of over 2,060 GW.
These are proposed capacities in the report’s transmission-queue coverage, not installed capacity or annual energy. The report notes that many requests are ultimately withdrawn. Do not infer that all listed projects will be built, add hybrid categories again to an already aggregated total, or apply a national completion statistic to an individual application. The source explains its dataset and offers downloadable materials for deeper analysis.
Managing a project through the process
Start by identifying the operator, tariff/program, connection configuration, relevant study window and required readiness evidence. There is no worldwide size threshold separating “fast track” and a formal queue.
Keep a project register with request ID / applicable rules / current study stage / unresolved condition / responsible party / response deadline / dated source. Record deposits and withdrawal exposure using the actual agreement or tariff, rather than treating every deposit as refundable.
For a hypothetical handoff, an impact study is complete but an affected-network review and connection works remain unresolved. The register should show both dependencies; a completed study does not justify a promised energization date. Reconcile configuration changes with the operator before relying on the previous result.
Designers should supply consistent equipment models, capacities and connection data. Developers/installers should track required responses and evaluate upgrade exposure before committing to later spending. Sales teams should present conditional milestones and the underlying evidence, rather than a guaranteed wait based on queue position. A reduced-size or phased alternative needs its own applicable review; it does not automatically bypass study or preserve expansion rights.
Planning software can help compare documented design scenarios. Verify its actual functions, and do not promise that generated documents will shorten an operator’s queue or secure approval.
Frequently asked questions
Does queue position guarantee priority or a connection date?
No. The relevant process can involve clusters, readiness requirements, restudies and transition rules. Use the operator’s actual milestone information.
Do all residential projects bypass queues?
No universal rule applies. Check the utility’s process, project configuration and screening requirements; a generic 25 kW threshold is insufficient.
Is queued capacity the same as future installed capacity?
No. It represents requests within a dataset and period. Projects can change or withdraw, and capacity is different from energy production.
Does an interconnection agreement finish the process?
Not necessarily. Required works, other approvals, commissioning and operating authorization may remain outstanding.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
