Module 4 · Lesson
From day-ahead positions to real-time balance
- 30 minutes
- Intermediate
- Editorial status: Phase 1 Complete
- Market-neutral + ERCOT case
Market question. A system expected 7,500 MW of net load day-ahead but must cover 8,100 MW in real time while 300 MW of generation is unavailable. What changed physically, what must the operator dispatch, and what can a price alone tell a participant about settlement?
Step 1
Treat day-ahead as a forward position and operating plan
Day-ahead processes use forecasts, bids, offers, resource constraints, and a network model to establish next-day awards or schedules under market-specific rules. They support commitment and risk transfer before delivery, but they do not freeze the physical system. Load, renewable production, topology, and generator availability can all change before the operating interval.
Define net load here as gross load minus wind and solar output included in the scenario. It is the amount left for other resources, imports, storage discharge, or demand response before accounting for losses and other modeled details.
net load = gross load − modeled renewable outputWorked example
Day-ahead expectation
The synthetic day-ahead forecast is 10,000 MW of gross load and 2,500 MW of renewable output:
10,000 − 2,500 = 7,500 MWThis 7,500 MW is a forecast-based system need, not a claim about one participant's award or an observed ERCOT interval.
- ForecastCurrent stage
- Day-ahead positionUpcoming
- Updated conditionsUpcoming
- Real-time outcomeUpcoming
Use the balanced case to locate the sequence: forecast formation, day-ahead outcome, updated conditions, real-time dispatch, metering, and settlement. Exact timing and products vary by market.
Step 2
Decompose the real-time tightening
In the tight synthetic scenario, real-time gross load is 10,200 MW and renewable output is 2,100 MW:
10,200 − 2,100 = 8,100 MWThe system's net-load requirement is therefore 600 MW above the day-ahead expectation. Decompose it rather than calling the entire move “load forecast error”:
| Driver | Day-ahead assumption | Real-time outcome | Tightening |
|---|---|---|---|
| Gross load | 10,000 MW | 10,200 MW | +200 MW |
| Renewable output | 2,500 MW | 2,100 MW | +400 MW net load |
| Net load | 7,500 MW | 8,100 MW | +600 MW |
| Forced outage | 0 MW | 300 MW unavailable | +300 MW effective need |
The 300 MW forced outage does not change the arithmetic definition of net load. It reduces dispatchable supply. Combining the 600 MW net-load increase and the 300 MW availability loss gives 900 MW of effective tightening relative to the day-ahead balance:
600 MW net-load increase + 300 MW outage = 900 MW effective tightening- ForecastCurrent stage
- Day-ahead positionUpcoming
- Updated conditionsUpcoming
- Real-time outcomeUpcoming
“Effective tightening” is a teaching diagnostic, not a market settlement quantity. It indicates how far the real-time dispatch problem shifted toward more or higher-cost available supply. The price effect depends on the offer stack, constraints, reserves, and applicable pricing rules.
Pause and predict
Which statement correctly classifies the 900 MW effective tightening?
Step 3
Separate dispatch, price, and settlement
The operator's real-time problem is physical: use the current feasible set of resources to balance actual load and maintain reliability. The real-time energy price is an economic output of that constrained dispatch and pricing process. Settlement is participant-specific accounting: it applies market rules to awards, schedules, meter quantities, locations, products, and prices.
These statements prevent three common category errors:
- A day-ahead award is not the same thing as actual physical generation or consumption.
- A system-level 900 MW tightening is not automatically one participant's imbalance.
- A real-time price does not by itself determine a participant's profit or loss; quantity, location, day-ahead position, contract terms, uplift, and settlement rules matter.
A useful but bounded two-settlement intuition
A common analytical intuition is to value a day-ahead scheduled quantity at the day-ahead price and value deviations from that schedule at a real-time price. Use that only as a starting framework. Metering, losses, uplift, ancillary services, virtual positions, make-whole payments, and market-specific charge types can materially alter an actual settlement statement.
Pause and predict
A participant is 50 MWh long day-ahead relative to its metered real-time load. Can the system's 900 MW tightening alone determine its settlement outcome?
Apply the mechanism
Using the synthetic case, report day-ahead net load, real-time net load, net-load forecast error, outage tightening, and total effective tightening. Then state what additional information is required to interpret a participant's settlement.
Takeaways
- Day-ahead establishes forward positions and an operating plan; real time balances actual conditions.
- Net-load error and generator outage are different mechanisms even when both tighten dispatch.
- The synthetic case moves from 7,500 MW to 8,100 MW net load and loses 300 MW of supply, for 900 MW of effective tightening.
- Physical dispatch, market price, and participant settlement are linked but not interchangeable.
Selected sources
Sources and model boundaries
- Federal Energy Regulatory Commission: Energy PrimerRetrieved 2026-08-03.
A broad federal primer; it does not substitute for market-specific tariff and operating-rule analysis.
- ERCOT: Wholesale Markets 201Retrieved 2026-08-03.
Training material is introductory and does not replace ERCOT protocols, guides, or settlement statements.
- ERCOT: Market PricesObserved: Operating day 2026-01-24; corrected RTM files approved 2026-06-01.Retrieved 2026-08-03.
ERCOT publishes observed prices and correction archives. January 24, 2026 analysis must use corrected RTM files; prices alone do not reconstruct dispatch, offers, constraints, losses, adders, or settlements.