PJM Seven-Day Load Forecast

PJM's seven-day hourly demand forecast in long form: issued_at (when PJM published the forecast), event_time (the hour being forecast), area, and forecast_mw.

Load data PJM market

Query with the agent

Native record

forecast area x target hour x issue vintage

hourly (reissued through the day) publication cadence

Evidence

Forecast data

Forward-looking values with an explicit issue time

Time basis

Interval-start records

UTC · event_time

Overview

4.14M rows across 2,033 issue vintages and 25 areas, covering forecasts issued since 2026-05-21 and targets out to seven days ahead. Because issue time and target time are separate columns, this table can answer both 'what does PJM expect for tomorrow evening' and 'what did PJM expect for that hour twelve hours before it happened' — the second question needs the issue-time filter, and getting it wrong turns a forecast evaluation into hindsight. The area column mixes three levels of the same hierarchy: the RTO total (RTO_COMBINED), three regional aggregates (MID_ATLANTIC_REGION, SOUTHERN_REGION, WESTERN_REGION), transmission zones (AEP, COMED, DOMINION, ...) and Mid-Atlantic sub-zones (PSE&G/MIDATL, PECO/MIDATL, ...). Summing across areas double-counts, in some cases three times over.

Query contract

One area, one target hour and one issued_at is one forecast. For the current expectation, take the latest issued_at. For forecast accuracy, take the latest issued_at that is EARLIER than event_time — an issued_at after the target hour is hindsight, not a forecast.

Analysis rules

Never average or sum across issue vintages; pick one before aggregating anything.
The area column mixes three levels of the same hierarchy: the RTO total (RTO_COMBINED), three regional aggregates (MID_ATLANTIC_REGION, SOUTHERN_REGION, WESTERN_REGION), transmission zones (AEP, COMED, DOMINION, ...) and Mid-Atlantic sub-zones (PSE&G/MIDATL, PECO/MIDATL, ...). Summing across areas double-counts, in some cases three times over.

Related analysis

forecast error for a delivered hour · join pjm_load on event_time against area='RTO_COMBINED' rows from one issue vintage

Interpretation

Vintages only begin 2026-05-21. This table cannot evaluate forecast accuracy before that date, and an empty result for an earlier period means the vintage was never ingested, not that PJM published nothing.
Forecast rows exist for hours that have not happened. Do not describe a forward row as an observation.

Access

Query from your own tools

Use the guarded HTTP endpoint directly, or connect an MCP client and load the dataset contract with describe_data before calling query_data.

PJM MCP API reference

HTTP endpoint

POST /api/v1/datasets/pjm_load_forecast/query

Need the full history of this dataset in Snowflake, Databricks or your own storage? Data services delivers it on a schedule.

Schema4

Column

Type

issued_atDateTime64(6, 'UTC')

event_timeDateTime64(6, 'UTC')

areaLowCardinality(String)

forecast_mwNullable(Float64)

Sample data

issued_at	event_time	area	forecast_mw
2026-10-12 07:47:26.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 07:17:26.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 06:47:26.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 06:17:25.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 05:47:25.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 05:17:25.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 04:47:25.000000	2026-10-19 03:00:00.000000	AE/MIDATL	950
2026-10-12 04:17:25.000000	2026-10-19 03:00:00.000000	AE/MIDATL	951
2026-10-12 05:17:25.000000	2026-10-19 03:00:00.000000	AEP	15042
2026-10-12 06:17:25.000000	2026-10-19 03:00:00.000000	AEP	15051
2026-10-12 05:47:25.000000	2026-10-19 03:00:00.000000	AEP	15051
2026-10-12 07:47:26.000000	2026-10-19 03:00:00.000000	AEP	15055
2026-10-12 07:17:26.000000	2026-10-19 03:00:00.000000	AEP	15041
2026-10-12 06:47:26.000000	2026-10-19 03:00:00.000000	AEP	15041
2026-10-12 04:17:25.000000	2026-10-19 03:00:00.000000	AEP	15034
2026-10-12 04:47:25.000000	2026-10-19 03:00:00.000000	AEP	15042
2026-10-12 07:47:26.000000	2026-10-19 03:00:00.000000	AP	4994
2026-10-12 06:47:26.000000	2026-10-19 03:00:00.000000	AP	4994
2026-10-12 06:17:25.000000	2026-10-19 03:00:00.000000	AP	4983
2026-10-12 07:17:26.000000	2026-10-19 03:00:00.000000	AP	4994
2026-10-12 05:47:25.000000	2026-10-19 03:00:00.000000	AP	4983
2026-10-12 04:17:25.000000	2026-10-19 03:00:00.000000	AP	5004
2026-10-12 05:17:25.000000	2026-10-19 03:00:00.000000	AP	4995
2026-10-12 04:47:25.000000	2026-10-19 03:00:00.000000	AP	4995
2026-10-12 07:47:26.000000	2026-10-19 03:00:00.000000	ATSI	6504

Coverage

94.1% complete9 gap days143 days with data

Show coverage history

Coverage: 94.1%Days with data: 143Gaps: 9

2026

gaplessmore

Related load data

Related load data
Dataset	Description
7-Day Load ForecastPJM · hourly (7-day horizon)	PJM's seven-day-ahead hourly load forecast by forecast area, refreshed through the day. Rows are keyed by target time (event_time) with the issue time in evaluated_at_utc; take the latest vintage per target hour via an argMax over evaluated_at_utc. Forecast areas match the very-short-term feed (utility names, RTO_COMBINED for the system total). This is the table for tomorrow's peak and the week-ahead demand outlook. Source: PJM Market Data.
Day-ahead hourly demand bidsPJM · day publication	PJM's Day-ahead hourly demand bids. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Instantaneous LoadPJM · 5-minute	PJM metered load sampled every five minutes by area, where 'PJM RTO' is the whole-RTO system total and the remaining areas are the transmission-zone operating regions (AEP, COMED, DOM, PSEG, and so on). Because it posts within minutes, this is the live demand signal for PJM — system load, zonal load, and the shape of the daily peak — unlike the hourly metered-load tables that settle on a delay. Source: PJM Market Data.
PJM Hourly Actual LoadPJM · hourly	Actual hourly electricity demand in PJM, one row per hour with a system total and one column per load area. 75,672 hours, 2017-12 to now. Columns: system_mw plus aep_mw, ap_mw, atsi_mw, dayton_mw, deok_mw, dominion_mw, duquesne_mw, ekpc_mw, mid_atlantic_mw, northern_illinois_mw. system_mw is DERIVED as the sum of the ten areas, but unlike NYISO it has been checked: against PJM's own published RTO total over 517 overlapping hours the mean difference is 0.009% and the maximum 0.938%. Wide rather than long, so "load right now" and "the 10 load area shares of it" are one row, not 11. Every market's load table in this catalog shares the system_mw column and the same hourly grain, so a cross-market demand comparison needs no reshaping.