PJM's Jan-2026 near-term trim: slipped projects, or a new large-load haircut?
The question
"Did PJM's Jan-2026 near-term load forecast trim come from data-center projects actually slipping in-service dates, or from a Manual 19 / large-load-haircut methodology change?"
Context: [[2026-07-28-pjm-peak-load-forecast-power-cycle-corroboration]] established that PJM's Jan-2026 vintage cut target years 2026-2029 by 1.6-2.6% versus Jan-2025 while raising 2033-2035 by up to 3.3%, and left the cause open. power-cycle-v1.1 has $20,000 of paper capital deployed against a phase-2-into-phase-3 timing call that this cause materially affects.
Headline: mostly the haircut, with one genuine exception at the front edge. For target years 2027-2029, where the deepest cuts land, PJM's effective inclusion rate on large-load requests collapsed from 82-84% to 60-74% while the utilities' submitted volume held flat or rose sharply. That is a haircut, not slippage. For target year 2026 alone it is the reverse: submitters themselves cut their 2026 ask by 1,530 MW (-9.9%), and PJM's inclusion rate for that year actually ticked up, so the nearest year's large-load reduction is submitter-side, not PJM-side. Separately, the question's "Manual 19 revision" premise is false: the haircut rules lived in a standalone implementation guideline dated 2025-07-01 and did not enter Manual 19 until Revision 39, effective 2026-06-30, six months after the forecast published.
Confidence: high that the haircut is the dominant cause of the 2027-2029 cuts, and high on the Manual 19 timing correction. Medium on the precise split for target year 2026, where the two submitted-request snapshots differ in zone granularity (see Table 2 caveats).
What we already know (from the vault)
- The delta shape, already established. [[2026-07-28-pjm-peak-load-forecast-power-cycle-corroboration]] computed Jan-2026 vs Jan-2025 on identical target years: 2026 -1.61%, 2027 -2.27%, 2028 -2.60%, 2029 -2.59%, 2030 -0.48%, then higher from 2033 (+0.92%) through 2035 (+3.31%). All ten figures reproduce exactly from the Table B-1
PJM RTOrows re-pulled in this run, so the parent brief's arithmetic is confirmed, not re-derived. - PJM's stated 10-year summer CAGR rose rather than fell. The Jan-2026 report states 3.6%/yr over the next 10 years (2026 Load Report, p.6, read directly in this run). The parent brief recorded 3.1%/yr from the Jan-2025 report p.6; that earlier figure is carried from the vault and was not re-fetched here. A near-term trim coexisting with a raised long-run growth rate is the signature of a timing reclassification rather than demand loss.
- The thesis already asserted this answer without primary evidence. [[2026-05-17-power-cycle-v1]], bear-case point two: "PJM trimmed its near-term load forecast in late 2025 specifically because the operator started vetting data-center load-additions more strictly — many announced data centers are speculative or double-counted across multiple utility territories." That claim rode on footnote [2], a secondary Inside Lines post. This is the second power-layer claim traced back to that same footnote; the parent brief traced the thesis's 3.3% PJM growth baseline to it and flagged it unverified.
- None of v1.1's five founder-review triggers watch forecast vintages. [[2026-05-18-power-cycle-v1.1]], "Anchors to watch": ERCOT interconnection queue, hyperscaler PPA cadence, GEV order velocity, smart-money 13F deltas, PJM/CAISO power price normalization. A forecast-methodology change is invisible to all five.
- Adjacent vault coverage of the speculative-load problem exists in [[2026-08-29-data-center-opposition-permitting-tracker]], which tracks the demand-side opposition channel but not the ISO accounting channel.
What the web says
All figures below were read from documents downloaded and parsed on 2026-10-10. Nothing is recalled.
- PJM attributes the near-term cut to the haircut in writing, and never mentions project withdrawal or slipped dates. 2026 Load Forecast Report (posted 2026-01-14), Executive Summary, p.4: *"The 2026 Long-Term Load Forecast is lower than the 2025 Long-Term Load Forecast in the near term through 2032 due to updates to the electric vehicle forecast, economics and large load adjustments... Near-term forecast years need 'firm' commitments, such as Electric Service Obligation (ESO)/Construction Commitments (CC), while longer-term projects will be considered 'non-firm' and will be derated because of their greater uncertainty. This distinction has brought large load adjustments down in the near-term forecast years compared to the 2025 Long-Term Load Forecast."* A sidebar on p.5 quantifies three years of interest versus the 2025 report: 2026 (3rd Incremental Auction year) -2,564 MW / -1.6%, 2028 (RPM Auction year) -4,414 MW / -2.6%, 2031 (RTEP Study year) -1,630 MW / -0.8%. (2026 Load Report)
- The rulebook is a standalone document dated 2025-07-01, not a manual revision. "Load Adjustment Request Implementation," PJM Resource Adequacy Planning Department, pp.4-5, sets three time tiers: "For large load coming online in 3 years or less: for those load projects that have the construction commitment or electric service obligation ... this load will be considered for inclusion." For 3-8 years out, projects "should either have cleared demonstrable project milestones to be considered certain or be de-rated", and "Absent a EDC/LSE provided probability factor, PJM will use a default factor of [50%] probability." On ramps: "Absent a EDC/LSE provided ramp rate, PJM will use a default 3 year ramp rate." Size floor 50 MW. Its revision log shows one amendment, 2025-08-26, "updated Rates and Agreement example to remove the Other agreements values for the near-term forecast." The live pjm.com URL now returns not-found; retrieved from the 2026-05-27 Wayback snapshot.
- The applied haircut, stated by PJM staff to stakeholders before publication. Load Analysis Subcommittee, 2025-11-24, "Load Adjustment Requests Summary for 2026 Load Forecast - Preliminary" (Molly Mooney). Slide 4, "Evaluating Requests": "Worked to identify those that had ESO/CC and marked those as 'Firm'. Only these projects will be allowed to impact RPM / All other projects were labeled 'Non-Firm' / Investigated ramp rates ... and imposed minimum 36 month / Investigated utilization rate ... and imposed 70% unless otherwise supported." Slide 6, "Discounting 'Non-Firm'": "Levels of 'Non-Firm' were significantly beyond what could fit into a top-down framework", and non-firm was "further reduced to reflect National constraints." (LAS 2025-11-24 item 03)
- A 2030 cutoff appears in the per-zone treatment, but it is not region-wide and should not be over-read. The sentence "Non-Firm prior to 2030 equal to zero and 2030+ applied 50% and national average scaling" appears on the slides for eight zones only: PL, DAYTON, DQE, APS, ATSI, JCPL, METED and SMECO-PEPCO (same deck, slides 15-22, 28). Three more (PS, NOVEC, REC-Dominion) are described as having "already had 50% applied in submitted data" for 2030+. The three largest data-center zones got bespoke treatment instead: Dominion ("modeled demand forecast is less than or equal to the total amount of project demand with ESA/CC so considered Firm", slide 23), AEP ("Non-Firm aggregate total is accepted as PJM found it to be de-rated by more than 50% from the volume of requests ... Non-Firm ramp rates extended to be in line with Firm ramp rates", slide 14) and COMED ("CC and financial deposit for all submitted projects considered Firm", slide 11). So the hinge observed at 2030 in Table 1 is consistent with the tiered rule structure rather than proof of any single zone rule.
- Slippage is ruled out for 2027-2029 and supported for 2026. Comparing like with like, the utilities' submitted requests across the two cycles (Table 2): the 2026 ask fell 1,530 MW (-9.9%), the 2027 ask was flat (+1.0%), and the 2028, 2029 and 2035 asks rose 16.5%, 27.0% and 45.1%. PJM's effective inclusion rate meanwhile fell in every target year from 2027 onward, from 82-87% in the Jan-2025 vintage to 60-70% in Jan-2026, while rising marginally for 2026 (81.5% to 82.7%). Front-end slippage is real and confined to 2026. The 2027-2029 cuts are the haircut.
- Manual 19 was NOT the vehicle, and this corrects the question's framing. Revision 37 (effective 2024-12-18) and Revision 38 (effective 2025-12-17, the version in force when the Jan-2026 report posted) both carry an Attachment B with no Firm/Non-Firm concept, no RPM-eligibility gate, no ramp-rate floor, no utilization factor and no duplicative-request discounting. Revision 38's own Current Revision page lists only "Attachment B: Clarify responsibilities of PJM and EDC/LSEs in the large load adjustment process" plus a cover-to-cover periodic review that extended the forecast horizon from 15 to 20 years. All of the haircut machinery appears for the first time in Revision 39, effective 2026-06-30, whose Current Revision page attributes the additions to "the January 16, 2026, Board Decisional Letter on Critical Issue Fast Path - Large Load Additions." (M19 Rev 39 · Rev 38 · Rev 37)
- The non-data-center share of the trim is an ordinary input revision, not an accounting change and not slippage. The plug-in-EV adjustment to summer peak (Table B-8c,
PJM RTO) was cut in every year: -218 MW in 2026, -913 MW in 2029, -1,658 MW in 2034. PJM's stated drivers for the residual are the S&P Global EV and behind-the-meter solar/battery forecasts and Moody's Analytics' September 2025 economic release (2026 Load Report, p.5). These are vendor-forecast and macro updates, and they are a real part of the trim that should not be labelled accounting. - PJM has since built the instrument that would detect real slippage, and it did not exist for this vintage. Manual 19 Rev 39 Attachment B now requires PJM to "assess the accuracy of past submissions relative to known actuals" and publish it each Spring. The first one, "Data Center Accuracy Report" (LAS, 2026-06-05), states the policy: "PJM will post an accuracy report of data center portion of Long-Term Load Forecast every May." That report is dashboard charts only, with underlying data in a companion Excel file on the load-forecast page; no slippage statistic appears in its text. (LAS 2026-06-05 item 04)
Table 1 — Jan-2026 minus Jan-2025, by target year
All rows are the PJM RTO row of the named sheet in each vintage's Load Report Tables workbook, compared on identical target years. B-9b = "Total Load Associated with Adjustments to Summer Peak Load." B-9 = "Adjustments Above Embedded to Summer Peak Load," the incremental amount layered onto the forecast. B-1 = total non-coincident unrestricted summer peak.
| Target yr | B-9b 2025LF | B-9b 2026LF | Δ B-9b | B-9 2025LF | B-9 2026LF | Δ B-9 | Δ B-1 total | Δ B-1 % |
|---|---|---|---|---|---|---|---|---|
| 2026 | 12,554 | 11,469 | −1,085 | 8,453 | 6,403 | −2,050 | −2,564 | −1.61% |
| 2027 | 17,721 | 15,856 | −1,865 | 13,668 | 10,785 | −2,883 | −3,735 | −2.27% |
| 2028 | 23,418 | 21,280 | −2,138 | 19,320 | 16,242 | −3,078 | −4,414 | −2.60% |
| 2029 | 29,483 | 27,361 | −2,122 | 25,334 | 22,290 | −3,044 | −4,564 | −2.59% |
| 2030 | 37,050 | 38,805 | +1,755 | 32,795 | 33,707 | +912 | −875 | −0.48% |
| 2031 | 45,361 | 46,638 | +1,277 | 41,101 | 41,477 | +376 | −1,630 | −0.85% |
| 2032 | 52,767 | 53,949 | +1,182 | 48,531 | 48,772 | +241 | −1,592 | −0.79% |
| 2033 | 55,683 | 60,258 | +4,575 | 51,509 | 55,089 | +3,580 | +1,887 | +0.92% |
| 2034 | 57,822 | 65,041 | +7,219 | 53,679 | 59,889 | +6,210 | +4,629 | +2.23% |
| 2035 | 59,413 | 68,968 | +9,555 | 55,239 | 63,796 | +8,557 | +6,949 | +3.31% |
MW. Negative = Jan-2026 lower than Jan-2025 for the same year. Δ B-1 % is computed from the Table B-1 PJM RTO base values (Jan-2025: 158,937 / 164,186 / 169,981 / 176,094 / 183,883 / 192,647 / 200,507 / 204,197 / 207,253 / 209,923; Jan-2026: 156,373 / 160,451 / 165,567 / 171,530 / 183,008 / 191,017 / 198,915 / 206,084 / 211,882 / 216,872). The sign flip on both adjustment measures occurs at 2030.
On the B-9 above-embedded measure, the large-load adjustment accounts for roughly 67-80% of the total near-term trim (2,050/2,564 in 2026; 3,044/4,564 in 2029), with the EV down-revision contributing another 9-20% (218/2,564 and 913/4,564). Treat those shares as arithmetic indications, not a formal variance decomposition — PJM re-estimates the whole model each vintage and removes embedded data-center load from history before layering adjustments, so B-9, B-8c and B-1 are not strictly additive.
Table 2 — The slippage test: submitted versus submitted, across two cycles
This is the comparison that discriminates. Columns 1 and 2 are what the utilities asked PJM for in each cycle, before any PJM processing. Columns 3 and 4 are what PJM included. The inclusion rate is the haircut.
| Target yr | Asked, 2024 cycle | Asked, 2025 cycle | Δ ask | Included 2025LF | Incl. rate | Included 2026LF | Incl. rate |
|---|---|---|---|---|---|---|---|
| 2026 | 15,398 | 13,868 | −9.9% | 12,554 | 81.5% | 11,469 | 82.7% |
| 2027 | 21,186 | 21,402 | +1.0% | 17,721 | 83.6% | 15,856 | 74.1% |
| 2028 | 27,809 | 32,391 | +16.5% | 23,418 | 84.2% | 21,280 | 65.7% |
| 2029 | 36,072 | 45,796 | +27.0% | 29,483 | 81.7% | 27,361 | 59.7% |
| 2030 | 51,943 | 60,117 | +15.7% | 37,050 | 71.3% | 38,805 | 64.5% |
| 2031 | 57,682 | 71,552 | +24.0% | 45,361 | 78.6% | 46,638 | 65.2% |
| 2032 | 61,255 | 81,463 | +33.0% | 52,767 | 86.1% | 53,949 | 66.2% |
| 2033 | 64,288 | 88,056 | +37.0% | 55,683 | 86.6% | 60,258 | 68.4% |
| 2034 | 66,296 | 93,554 | +41.1% | 57,822 | 87.2% | 65,041 | 69.5% |
| 2035 | 67,971 | 98,622 | +45.1% | 59,413 | 87.4% | 68,968 | 69.9% |
MW, PJM RTO summer peak. 2024-cycle asks are the sum of the eleven zone rows (DLCo, BGE, DEOK, PECO, PSEG, APS, ATSI, ComEd, PPL, AEP, DOM) in the 2024-10-25 LAS post-meeting workbook, whose header states "Below values show the amount requested for consideration not the amount included in the 2025 Load Forecast." That sheet has no RTO total row, so the sum is mine. 2025-cycle asks are the PJM RTO row of the "2026 DEMAND Requests" sheet in the 2025-09-16 LAS informational workbook (its own caveat: "Note these are supplied to PJM by EDC/LSE and are not Final Large Load Adjustments"). Included columns are Table B-9b.
Caveats, and which way they cut. The two snapshots differ in zone granularity: the 2024 workbook has one DOM row where the 2025 workbook splits DOM / NOVEC / ODEC / REC, and DAYTON, DQE, PEPCO, SMECO, JCPL and METED appear only in the later sheet. That makes the 2024-cycle column a likely undercount of the full 2025-cycle submitter set, which biases against the 2026 slippage finding rather than for it: a fuller 2024 baseline would make the 2026 ask decline larger, not smaller. The snapshots are also taken at different points in the cycle (October 2024 vs September 2025), and the 2025 workbook flags one later downward correction (REC-APS). B-9b includes a small amount of non-data-center adjustment, notably EKPC peak shaving at −10 MW and Dominion's negative voltage-optimization adjustment (Table B-9b, EKPC and DOM rows, 2026 workbook). None of that is material against a 9.7 GW swing in the 2029 ask.
Convergences and contradictions
- Vault and primary evidence converge on the mechanism, and the vault was right for the wrong reason. [[2026-05-17-power-cycle-v1]] already claimed stricter vetting caused the trim, citing a secondary source and dating it "late 2025." The primary record supports the mechanism for 2027-2029 and sharpens the dates: implementation guideline 2025-07-01, stakeholder presentation 2025-11-24, forecast published 2026-01-14. A correct conclusion resting on an unverified citation is still a citation risk, and this is the second power-layer claim tracing to the same footnote.
- The question's own framing contained a false premise, which is a finding rather than a quibble. "A Manual 19 revision" is the natural place to look for an ISO methodology change and it is the wrong place here. PJM changed the number first and amended the manual second, with a six-month lag and a Board Critical Issue Fast Path proceeding in between. Anyone monitoring PJM methodology by watching Manual 19 revision history would have read Rev 38's bland "clarify responsibilities" line in December 2025 and concluded nothing had changed.
- The two hypotheses are not mutually exclusive, and the honest answer assigns each a year range. Target year 2026 is submitter-side: the ask fell 9.9% and PJM's inclusion rate rose. Target years 2027 onward are PJM-side: the ask was flat to sharply higher while the inclusion rate fell 10 to 25 percentage points. The 2027-2029 band carries the deepest percentage cuts and therefore dominates the headline, which is why "mostly the haircut" is the right summary. Treating the whole trim as one cause in either direction would be wrong.
- One contradiction with the simple "delay, not cancel" reading. A haircut can only reduce, so it cannot explain the Jan-2026 vintage being 3.31% higher for 2035. That increase comes from a 45.1% larger ask for 2035, partly offset by a lower inclusion rate. The out-year raise and the near-term cut have different causes, and describing both as one rightward shift of a fixed quantity is imprecise. PJM simultaneously received a much bigger ask and applied a much stricter filter.
Synthesis for RDCO
The useful finding is that the Jan-2026 near-term trim carries almost no demand information in the years where it looks worst. For target years 2027-2029, the utilities either held their ask flat or raised it by up to 27%, and PJM's effective inclusion rate fell from the low eighties to the sixties. The published number went down because the scorer changed, not because the projects moved. The one real exception is the nearest year: submitters cut their own 2026 ask by 1,530 MW while PJM's inclusion rate for 2026 ticked up, so the 2026 reduction is a genuine front-end slip. One year of front-end slippage inside a cycle where the ten-year ask rose 45% is not a demand-softening signal. For power-cycle-v1.1, the practical effect is that the 2.6% cut to 2028-2029 that looked like the most alarming datapoint in [[2026-07-28-pjm-peak-load-forecast-power-cycle-corroboration]] should be removed from the thesis's evidence base. The EV and macro residual, roughly 20-33% of the trim, stays in as an ordinary input revision; it is just not about data centers.
Recommendation: (b) add a sixth founder-review trigger. Not (a) change the thesis: direction is untouched, and the structural-scarcity core in [[2026-05-18-power-cycle-v1-v2-honest-rerun]] never ran through PJM's forecast vintage. Not (c) do nothing: that leaves a real instrumentation hole, because the parent brief's timing concern was raised against a number that turns out not to mean what it looked like, and the current anchor set cannot tell the difference. The sixth trigger should be constructed so it would not have fired on the Jan-2026 trim, which means keying it to the submitted-side and contract-backed series rather than the headline forecast. The three artifacts that carry the signal publish on a fixed annual cadence: the September LAS submitted-requests workbook, the November LAS preliminary summary with its Firm / Non-Firm split, and PJM's new May Data Center Accuracy Report. Reviewable events are a year-over-year decline in Firm (ESO/CC-backed) MW, a sustained fall in the inclusion rate below the 60-70% band this cycle established, or realized data-center load landing materially below the Firm-only forecast in the accuracy report. Headline forecast-vintage deltas should be explicitly disqualified as trigger inputs. No trade, allocation change, sizing change or deploy is proposed here, and none should be read into this brief.
There is a second-order consequence worth naming because a bearish reading of the trim would miss it. The rule is not only that non-firm load gets derated; it is that only Firm impacts RPM. PJM now procures capacity against a deliberately conservative near-term load number while the utilities' own submitted load runs 1.2x to 1.7x higher than what is included (Table 2, 2026LF columns). If even part of the discounted volume arrives on the submitters' schedule rather than PJM's, the auctions will have under-procured against it. That is a tightening mechanism, not a loosening one. It does not belong in the thesis as evidence, because it is a hypothesis about a rule's consequences rather than an observation, but it is the reason the honest read of this finding is "no signal" rather than "bearish signal."
The methodological lesson has the longest shelf life and generalizes past PJM. A forecast series the thesis depends on had a structural break inserted into it by a one-page guideline that was never a manual revision, never a tariff filing, and whose live URL has since 404'd; the manual caught up half a year later. Pre-2026 and post-2026 PJM vintages are not comparable instruments. Combined with the parent brief's finding that marker-1 is undecidable because it never named a weather-normalization basis, the power layer now has two separate instrument-definition failures, both found by reading primary sources rather than by any trigger firing. The cheap fix is a rule rather than a trigger: any anchor keyed to a published series must name the exact table and vintage, and must carry a documented check for methodology breaks in that series. That is a harness change rather than a thesis change, and it is probably worth more than the sixth trigger.
Why this is in the vault
This closes the first open follow-up of [[2026-07-28-pjm-peak-load-forecast-power-cycle-corroboration]] with a primary-source verdict, which does three specific things to the live $20,000 power-cycle-v1.1 position: it removes the 2027-2029 portion of the Jan-2026 trim from the thesis's evidence base as a scorekeeping artifact while preserving the 2026 slip as a real but small submitter-side signal, it supplies the exact published artifacts and threshold band (60-70% inclusion rate, Firm MW direction) for a proposed sixth founder-review trigger, and it corrects the unverified footnote-[2] claim in [[2026-05-17-power-cycle-v1]] by dating and sourcing it (guideline 2025-07-01, LAS presentation 2025-11-24, Manual 19 codification only at Rev 39 on 2026-06-30).
Open follow-ups
- Does the "Firm" MW series carry predictive power the headline forecast does not? PJM publishes Firm vs Non-Firm splits at zone level in the November LAS decks and a May accuracy report comparing prior-vintage data-center forecasts to realized load. With two cycles of Firm data plus the accuracy report's companion workbook, it is testable whether ESO/CC-backed MW converts to metered load at a materially higher rate than non-firm, and at what lag. That test would set the sixth trigger's threshold empirically; this brief sets it by observation of a single cycle.
- What did Charles River Associates conclude about PJM's data-center forecast methodology? The LAS index lists "Charles River Associates Review of Data Center Forecast Methodology" at the 2026-07-13 and 2026-08-26 meetings, plus "Third-Party Review of Large Load Adjustment Forecast" at 2026-06-05, 2026-07-13 and 2026-08-26. Document titles were read from the LAS page index; contents not retrieved in this run. If the independent reviewer judged the 2026 haircut too conservative or too loose, that is a dated stakeholder-facing opinion on whether the Jan-2026 number under-states real demand, and it bears directly on the second-order tightening argument above.
- Not examined here: the 2027 vintage. PJM has posted 2027-cycle assumption documents (behind-the-meter solar/storage, EV, and an updated large-load template) to the LAS postings page, and Manual 19 Rev 39 now governs. Whether the 2027 forecast re-raises the near-term years as projects clear into Firm status is the real test of "delay not cancel", and it is not answerable until January 2027.
- Carried forward unresolved from the parent brief: marker-1 still has no weather-normalization basis, and ERCOT weather-normalized peaks have still never been pulled. Nothing here touches either.
Related
- [[2026-07-28-pjm-peak-load-forecast-power-cycle-corroboration]] — the parent brief whose first open follow-up this closes; source of the vintage deltas extended here
- [[2026-05-18-power-cycle-v1.1]] — the live thesis with $20k paper capital; the five founder-review triggers a sixth would join
- [[2026-05-17-power-cycle-v1]] — source of the unverified "stricter vetting" claim this brief substantiates, re-dates and bounds by year range
- [[2026-05-17-power-anchors-backfill-notes]] — the anchor backfill that first flagged the PJM gap in the power layer
- [[2026-05-18-power-cycle-v1-v2-honest-rerun]] — the backtest the position sizing rests on, which does not run through forecast vintages
- [[2026-08-29-data-center-opposition-permitting-tracker]] — the demand-side opposition channel, a different mechanism from this ISO-accounting channel
Sources
Retrieved and parsed in this run (2026-10-10):
- PJM 2026 Load Forecast Report, posted 2026-01-14 — Executive Summary p.4 (attribution + ESO/CC firm-commitment language), p.5 sidebar (−2,564 / −4,414 / −1,630 MW) and p.5 Load Adjustments table, p.6 (3.6%/yr 10-yr summer CAGR): https://www.pjm.com/-/media/DotCom/library/reports-notices/load-forecast/2026-load-report.ashx
- PJM 2026 Load Report Tables (XLSX) — Tables B-1, B-8c, B-9, B-9b,
PJM RTO/ EKPC / DOM rows: https://www.pjm.com/-/media/DotCom/planning/res-adeq/load-forecast/2026-load-report-tables.xlsx - PJM 2025 Load Report Tables (XLSX) — same tables, prior vintage: https://www.pjm.com/-/media/DotCom/planning/res-adeq/load-forecast/2025-load-report-tables.xlsx
- PJM Load Analysis Subcommittee, 2025-11-24, item 03, "Load Adjustment Requests Summary for 2026 Load Forecast - Preliminary" — slides 4 and 6, and per-zone slides 10-28: https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/2025/20251124/20251124-item-03---large-load-adjustment-requests-summary.pdf
- PJM LAS, 2025-09-16, post-meeting informational workbook, "2026 DEMAND Requests" sheet,
PJM RTOrow (Table 2, "Asked, 2025 cycle"): https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/2025/20250916/20250916-post-meeting---informational-only---large-load-adjustment-requests.xlsx - PJM LAS, 2024-10-25, post-meeting "Zonal Large Load Requests Summary" workbook, Sheet1 rows 4-14 (Table 2, "Asked, 2024 cycle"): https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/2024/20241025/20241025-post-meeting---zonal-large-load-requests-summary.xlsx
- PJM LAS, 2026-01-23, item 03, "PJM 2026 Long-Term Load Forecast" presentation — slide 25 "Evaluating Requests", slide 27 "Total Load Adjustment Comparison (Table B9b)", slide 28 "Processing Steps": https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/2026/20260123/20260123-item-03---pjm-2026-long-term-load-forecast---presentation.pdf
- PJM, "Load Adjustment Request Implementation," Resource Adequacy Planning Department, dated 2025-07-01, revision log 2025-08-26 — pp.4-5 (3-year ESO/CC gate, 50% default probability for 3-8 years, 3-year default ramp, 50 MW floor). Live pjm.com URL returns not-found; retrieved from Internet Archive snapshot of 2026-05-27: https://web.archive.org/web/20260527091614/https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/postings/load-adjustment-request-implementation.pdf
- PJM Manual 19: Load Forecasting and Analysis, Revision 39, effective 2026-06-30 — Current Revision p.4, Attachment B pp.26-32, Revision History p.46: https://www.pjm.com/-/media/DotCom/documents/manuals/m19.pdf
- PJM Manual 19, Revision 38, effective 2025-12-17 — Current Revision p.4, Attachment B p.26 (no Firm/Non-Firm, ramp or utilization provisions): https://www.pjm.com/-/media/DotCom/documents/manuals/archive/m19/m19v38-load-forecasting-and-analysis-12-17-2025.pdf
- PJM Manual 19, Revision 37, effective 2024-12-18 — Attachment B (same absence): https://www.pjm.com/-/media/DotCom/documents/manuals/archive/m19/m19v37-load-forecasting-and-analysis-12-18-2024.pdf
- PJM LAS, 2026-06-05, item 05a-2, "Manual 19 Attachment B redlines" (Rev 38 base confirmed from page header): https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/2026/20260605/20260605-item-05a---2-manual-19---attachment-b-redlines.pdf
- PJM LAS, 2026-06-05, item 04, "Data Center Accuracy Report" (annual May publication commitment; charts only): https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/2026/20260605/20260605-item-04---load-adjustment-accuracy-report.pdf
- PJM Load Analysis Subcommittee index (document titles for the CRA and third-party review items; those documents' contents not retrieved): https://www.pjm.com/committees-and-groups/subcommittees/las
Probed and confirmed unavailable:
https://www.pjm.com/-/media/DotCom/committees-groups/subcommittees/las/postings/load-adjustment-request-implementation.pdf→ PJM not-found page, although the URL is still live as a hyperlink inside the Jan-2026 Load Forecast Report PDF. Wayback used instead.- Retrieval note: pjm.com behind an Azure WAF returns HTTP 403 to bare-UA requests for
.xlsxand HTML paths. A full Chrome header set (Sec-Fetch-*,sec-ch-ua,Accept-Language) returns 200. Archived-year LAS materials are not linked from the committee page HTML; the Wayback CDX index was used to locate the 2024-cycle workbook.
Vault (read, not re-verified):
~/rdco-vault/06-reference/research/2026-07-28-pjm-peak-load-forecast-power-cycle-corroboration.md~/rdco-vault/01-projects/investing/theses/2026-05-18-power-cycle-v1.1.md~/rdco-vault/01-projects/investing/theses/2026-05-17-power-cycle-v1.md~/rdco-vault/01-projects/investing/anchors/power-layer/2026-05-17-power-anchors-backfill-notes.md~/rdco-vault/01-projects/investing/backtests/2026-05-18-power-cycle-v1-v2-honest-rerun.md~/rdco-vault/06-reference/research/2026-08-29-data-center-opposition-permitting-tracker.md
Paywalled/skipped: none encountered.