Queue age
Every generation request still in the PJM, ERCOT and BPA queues, ordered by the date its region publishes for it, beside the changes this site has recorded for it week to week.
What this shows
The queues list requests, but they do not record how long each one has been waiting in one consistent way. This view lines up the requests still in the queue by the date each region publishes for them, oldest first, and puts next to each one what this site has observed about it since weekly tracking began.
Withdrawn, cancelled and other terminal requests are left out, and so are completed ones: in service, energized, or (for PJM transmission service requests) confirmed. Requests under construction or suspended are still in the queue and are listed.
Age is a fact about a filing, not a judgement of it. An old request may be waiting on studies, on network upgrades, on an agreement, or on nothing at all. The queue does not say which, and neither does this table.
Coverage
Listed means still in the queue: not withdrawn, cancelled or otherwise terminal, and not completed. Completed counts the requests left out for that reason (PJM In Service and Confirmed, BPA ENERGIZED; ERCOT's report has no completed status). Under-construction and suspended requests are listed. "Not reported" counts listed requests whose region publishes no date in that field.
| Region | Date field | Listed | Dated | Not reported | Completed (left out) | Oldest date | Tracked changes | Tracked since | Retrieved |
|---|---|---|---|---|---|---|---|---|---|
| PJM | Submitted Date | 1,262 | 911 | 351 | 1,462 | 2018-08-31 | 40 | 2026-08-27 | 2026-10-12 |
| ERCOT | Screening Study Started | 1,809 | 1,774 | 35 | 0 | 2013-11-27 | 211 | 2026-08-27 | 2026-10-12 (source published 2026-10-01) |
| BPA | Request Date | 185 | 185 | 0 | 106 | 2007-10-25 | 22 | 2026-09-22 | 2026-10-12 |
Loading…
| Age & date | Queue ID | Project | MW | Status | Tracked changes | First seen | State |
|---|
Which date each region publishes
- PJM publishes a Submitted Date for requests in its cycle process. Its serial export, which holds the older requests (here, mostly under construction, suspended, or in engineering and procurement), has no submission date. Those rows show "Not reported" and sort last. PJM queue IDs encode the queue window a request entered, but this table does not convert IDs into dates.
- ERCOT publishes no application date in its Generator Interconnection Status report. The earliest dated milestone on a large-generation row is Screening Study Started, and that is the date shown. A request is filed before its screening study starts, so its age is at least what is shown. Small-generation rows carry no comparable date.
- BPA publishes a Request Date on every row.
Because the three fields differ, an ERCOT age and a PJM age are not the same measurement. Filter to one region to compare like with like.
What this site adds
A queue report is a snapshot. It shows each request's status as of the day it was published, not the statuses it held before. This site has stored every weekly snapshot since tracking began, and the table shows two things only that record can:
- Tracked changes: how many differences were observed for the request between weekly snapshots, and the most recent one: a status change, a restated capacity, or the request first appearing.
- First seen: for a request that appeared after tracking began, the date of the first snapshot it was in. That date and the published one can be far apart. The table shows both and does not explain the gap.
Tracking is weeks old, not years, so most requests show no tracked changes yet. "None" means no change was observed since the date in the coverage table, not that the request never changed.
Source
Queue fields are reproduced from each region's published queue data, as of the retrieval dates in the coverage table. Tracked changes come from this site's comparison of weekly snapshots, the same record as the Queue Wire change log. The full table is available as JSON at /data/queue-age.json.