Methodology
Dated measurements with their populations, calculations and sources. The directory describes operators and providers; the tracker records the numbers.
What each dataset contains
242 readings record one measurement for a named operator, resource and date. The 49 directory listings describe operators, data providers, software and study firms. Each dataset has its own download: readings JSON / CSV, and listings JSON / CSV.
The observation date describes the snapshot, completion cohort or reported event. It retains the source’s precision: a year or month is not converted into an invented day. The accessed date says when the source was checked. Readings are dated snapshots, not a live feed.
Resource MW and hybrid projects
ISO/RTO and US active capacity comes from the regional/resource summary in LBNL and GridTracker’s Queued Up 2026. GW are multiplied by 1,000 to store MW. Wind combines onshore and offshore. Storage combines standalone and hybrid storage, including the summary’s imputed hybrid MW. The year-end 2024 readings use the historical series in the 2026 workbook, so they can differ from an earlier edition.
Major utility readings and ISO nuclear readings sum the project sheet’s reported component MW for active requests in the named entity group. Battery and other-storage components count as storage. Missing component MW stay missing and are excluded from the reported sum; the note states how many matching components lack MW. No imputation is added. A zero means no reported matching MW in that sample. Utility footprints are the workbook entity groups, including grouped Duke companies and Dominion’s non-ISO sample.
Resource components are not net export limits. A hybrid project can contribute to both solar and storage, but request counts count its workbook row once. The regional total includes resources beyond the displayed solar, storage, wind, gas and nuclear columns. Displayed MW round to whole MW; stored calculations round to three decimal places.
Completion and withdrawal denominators
Outcome readings divide operational or withdrawn MW by all MW in the source’s requests-submitted-2000–2020 cohort, observed at end-2025. The denominator includes active, operational, withdrawn and suspended capacity. Sample counts are the corresponding request counts, not the weights used in the percentage. The source’s regional completion sheet covers operators that supply comprehensive status information. These historical proportions are not forecasts for a new application.
Measured wait times
Waits are the workbook’s median months from the interconnection request to actual commercial operation, grouped by the year projects reached operation. This is elapsed development time, including activity after interconnection studies. It is not the median age of today’s queue or a guaranteed study duration. Proposed CODs are never substituted for actual CODs.
The all-region annual table and the regional table have slightly different sample counts in some years. Each reading retains its own sheet’s sample and locator. An absent regional/year reading stays absent; the snapshot shows a dash when no measured 2025 regional cohort is supplied.
Large-load requests and stages
Generation queue MW exclude load requests. Large-load readings come from operator reports and utility filings: study requests, delivery-point requests, conditional classifications and binding contracts retain those labels. Operator and utility footprints can overlap; load stages and generations of a queue can also overlap. No national load total or inferred data-center share is calculated.
ERCOT’s September Batch Zero report gives a studied-load total of 127.9 GW in its summary and 125.4 GW on its chart. Both sourced readings are retained with conflict notes. They describe one population and must not be added. Base load also includes some energized facilities. Exclusion from Batch Zero is not treated as withdrawal from every future process.
Reform events and scheduled milestones
Each milestone separates its observation date from the event or scheduled target date. A filing is described as filed, partial compliance as partial, and a future schedule as scheduled. Historical orders are not presented as a complete statement of current legal status. Primary orders and operator announcements are linked on each record.
Workbook retrieval and reproducibility
The official workbook download challenged automated shell retrieval. Extraction used a public mirror pinned to a commit. The mirror matches the official attachment’s listed size (14.85 MB), and its national totals match every headline on LBNL’s Queued Up page: over 2,060 GW active, 773 GW solar, 749 GW storage, 220 GW wind, 253 GW gas and a median above 5 years to operation for 2025 builds. Both URLs appear on each affected reading.
Each reading includes a workbook sheet/cell reference or a report locator and the calculation applied. The repository retains a compact CSV extraction ledger, the import script, the workbook hash and the builder for operator readings. Rebuilding the JSON from the checked ledger does not require a network connection.
Directory verification
Directory fields use first-party queue pages, tariffs, product pages and documentation. A missing fact stays blank. Vendor claims are labelled where their scope matters. Fees and security reflect the cited source on the access date. Acquired companies sit under the surviving provider where the existing directory records the change.
Attribution and reuse
LBNL-derived readings are adapted from Lawrence Berkeley National Laboratory and GridTracker, Queued Up 2026, under CC BY 4.0. Adaptations include unit conversion, component aggregation, cohort percentages and rounding. Retain that attribution when reusing these readings. Operator and regulatory readings retain their own cited authorship; source documents are not relicensed by this site.
Corrections and placement
Send corrections with a public source to hello@interconnectionqueues.com. A substantive correction updates the reading and access date. Paid featured placement is labelled and does not change measurements or sorting.
Reading field definitions
- Operator / scope
- The operator or geographic population named by the source.
- Measurement
- The measured stage, capacity, outcome, duration or dated reform event.
- Resource / load type
- Resource component or load population. Wind includes onshore and offshore; storage includes batteries and other storage.
- Observation date
- Snapshot, cohort year or reported event date, retaining source precision. Separate from the source access date.
- Value
- Numeric measurement; interpret with unit, basis and note. Null for a dated milestone.
- Unit
- MW, projects, percent, months or date. Capacity is not energy or dependable capacity unless explicitly stated.
- Population and denominator
- Population, study stage, status filter or outcome denominator for this reading.
- Source locator / calculation
- Workbook sheet and cells or report section, including explicit conversions and derivations.
- Requests / sample
- Number of projects or requests supporting the measurement where available; resource counts may overlap for hybrids.
- Coverage and qualifications
- Source limitations, conflicts, missing component MW and distinctions needed to interpret this reading.
- Milestone date
- Date of the observed or scheduled reform milestone; the observation note distinguishes events from future targets.
Directory field definitions
- Type
- Queue operator, data provider, software or study firm.
- Offering
- The named queue, report, dataset, software product or service, as the source names it.
- Coverage
- Geography, operators or years the source says the offering covers.
- Request types
- Generation, storage, load, transmission or DER request types the source says are covered.
- Delivery and access
- How the queue or product is delivered: public listing, download, API, SaaS or services.
- Update frequency
- Refresh cadence as the publisher states it. Not a measured data latency.
- Data as of
- The as-of or last-updated date shown on the source page when we read it.
- Queue data fields
- Identifiers, project attributes and filters the queue or product lists.
- Status tracking
- How request status and study stage are tracked.
- Timing data
- Dates or durations the source publishes or models. A proposed in-service date is not a guaranteed wait time.
- Historical wait
- Median or typical wait published in a named report, with its scope.
- Study turnaround
- Published turnaround target or vendor claim, with its qualifier kept in the value.
- Study types
- Engineering analyses or process study types the source describes.
- Capacity analytics
- Published capacity, hosting or transfer analysis.
- Cost analytics
- Upgrade cost modelling, estimates or cost-reduction advisory.
- Risk analytics
- Project-risk, completion or congestion analytics.
- Queue analytics
- Queue management, extraction or scenario capabilities.
- Financial tracking
- Deposits, upgrade costs and other financial obligations the product tracks.
- Standards and compliance
- Regulatory frameworks or compliance services the source names. Not a certification.
- Application support
- Help with preparing or processing interconnection applications.
- Integrations and tools
- APIs, modelling tools or data exchange the source lists.
- License
- Data or software licence as published.
- Customers
- Customer types or a named customer, as published.
- Operations support
- Real-time monitoring, dispatch or control features.
- Application deadline
- Next application deadline the operator publishes.
- Application window
- Next cluster application window the operator publishes.
- Application acknowledgment
- Published time to acknowledge an application.
- Application review
- Published time for the completeness review.
- Project size range
- Project sizes the source says it serves.
- Engagement start
- When a documented client engagement began, per a published case study.
- Ownership
- Parent or owner as the source states it.
- Trial
- Free trial or evaluation version the source describes.
- Application fee
- Application fee the operator publishes.
- Pre-application report fee
- Fee for a pre-application report.
- Milestone security
- Security required per MW studied, as the operator publishes it.
- Large generator threshold
- Size above which a request counts as a large generator.
- Modeled capacity, published minimum
- Vendor-stated lower bound of project capacity modeled. Not capacity available for purchase.
- Qualified capacity
- Capacity the vendor says it has qualified.
- Customers, published minimum
- Vendor-published lower bound. Not audited.
- Completed studies, published minimum
- Lower bound of studies completed, as the firm states it.
- Reference projects, published minimum
- Projects in a published case study, lower bound.
- Reference capacity
- Total requested capacity of the projects in the published case study.
- Model size
- Largest network model the software supports, as published.