> For the complete documentation index, see [llms.txt](https://docs.gridstatus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridstatus.io/developers/guides/recipes/ercot-day-ahead-load-forecast-cutoff.md).

# Get Latest Forecast as of Bid Close

Get the latest ERCOT load forecast available as of day-ahead bid close

Pull ERCOT load forecasts by forecast zone as they were available at the 10:00 AM day-ahead bid close, then calculate daily maximums.

## Get hourly forecasts as of bid close

```python
hourly = client.get_dataset(
    "ercot_load_forecast_by_forecast_zone",
    start="2026-05-01",
    end="2026-05-08",
    publish_time="latest_before:-1 day@10:00:00",
    timezone="market",
)

print(hourly.head())
```

For each operating interval, `latest_before:-1 day@10:00:00` selects the latest forecast published at or before 10:00 AM market time on the prior day.

## Calculate daily maximums

```python
daily_max = client.get_dataset(
    "ercot_load_forecast_by_forecast_zone",
    start="2026-04-01",
    end="2026-05-01",
    publish_time="latest_before:-1 day@10:00:00",
    timezone="market",
    resample="1 day",
    resample_function="max",
)

print(daily_max.head())
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gridstatus.io/developers/guides/recipes/ercot-day-ahead-load-forecast-cutoff.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.