Ask the Grid
Create free workspace

Reports & recurring briefings

Set up a recurring brief about a decision you make. On your schedule the grid agent reads the market data behind it, analyzes what changed, and writes you a short issue by email and on Ask the Grid.

Open Reports
Status
Live
Access
Free account
Reading time
10 minutes
Updated
Oct 12, 2026

A report is a recurring brief about a decision you make, written like an analyst's note rather than a fixed table. You choose what it is for, the market, what it covers and when it arrives. On that schedule the grid agent reads the data, compares it with the previous issue, and writes what changed and what to watch. Each issue goes to your inbox and stays on the report's page with every earlier one. Sending it to other people, reviewing an issue before they receive it, and a public web page are optional, under Share.

Daily market briefings lead with what is new, materially changed, continuing, or resolved since the previous issue. Several connected findings compare the past session, published forecast revisions, regional prices, physical conditions, operator events, and relevant news. Sections and supporting exhibits follow the findings rather than a fixed daily checklist. A chart earns its place when timing, shape, uncertainty, or a comparison helps explain a decision; editions on uneventful days can be shorter and need no chart. The email carries the selected morning read, while the full issue can include additional evidence. The analyst explains their implications for preparation and the evidence that would change the view; ordinary conditions receive calm analysis. Forecasts retain their source and issuance time, and detailed methodology remains in the full issue.

On this page5 sections
  1. Start a report
  2. Your reports and what is shared with you
  3. Review an issue before others receive it
  4. Read an evidence-backed issue
  5. Deliver, share and revisit each issue

Start a report

A report is an agent that runs on a schedule. Say what it should watch and when, and it is drafted for you.

New report asks what the agent should watch and when, with a typed ERCOT hub briefing request and starter prompts.
Describe the decision and schedule, then draft the report agent before starting it.

Ask for it in a sentence

Choose New report and say what to watch and when, or pick a starter prompt. The agent drafts the brief type, market, coverage, schedule, audience and instructions, then states its assumptions. It asks only for details needed to run, such as which assets to watch or a supported cadence. New reports currently run on ERCOT; requests for another market are marked in the draft and still watch ERCOT.

  1. 1Open Reports and choose New report.
  2. 2Say what the agent should watch and when, or pick a starter prompt.
  3. 3Read the sentence on the card. Change When, Covers or Sends to in place, or open Adjust details for the title, the kind of brief, who it is written for and its instructions.
  4. 4Choose On demand for a one-time report, or Daily, Weekly, or Monthly for a recurring schedule, then Start.

The card

Read the card's summary, first delivery time and issue outline before starting. Change When, Covers or Sends to in place, or open Adjust details for the full setup. Monthly reviews run on the day of the month they started. Start over returns to the question; Set it up manually opens all the details. Reports proposed by the agent or from a saved collection use the same card. For an ERCOT collection, choose Create report in its actions menu to start with its assets. Back returns to that collection; creating from Reports returns to the filtered report list.

After you start it

The report page confirms its first delivery. Choose Write the first issue now to start immediately, or change settings under Manage. Free accounts can keep 1 report scheduled; Enterprise accounts can keep 40. Pause a report to make room; its earlier issues remain available. If an account holds more active schedules than its plan allows, the newest pause before their next issue, the owner gets one email, and the report page says why.

Your reports and what is shared with you

Reports lists Your reports and Shared with you. Each report has its own page and a Manage page for its owner.

Your reports and Shared with you

Use the Your reports and Shared with you tabs above the list. Your reports shows coverage, schedule, next delivery and latest issue status. Search by name or market, narrow to Needs attention, Scheduled or Paused, and order by Recent, Name or Next issue. Shared with you searches received issues and sorts by Recent or Name. Use the Collection filter to see the reports covering one collection, and the folder button beside it to open that collection. A long list shows 25 reports at a time with Show more. Filters stay in the address when you reload. The house briefings offer Read the latest and Get it by email.

The report's page

Select a report name to read it; choose Manage to change its controls. Back to reports returns to your list filters. The report page shows its purpose, coverage, schedule, next run and latest issue. Owners also see a run log: sent issues, skipped runs, held reviews, failures with Retry, and runs waiting for cleared day-ahead results. Filter it with All, Sent, Skipped or Failed. Other readers see published issues and dated explanations for days without one. Older issue links remain valid; numbered links such as /reports/<report>/3 open the same issue.

Run now, pause, or resume

Choose Run now on the report page or under Manage, Runs. Generation continues in the background; email delivers the completed issue when enabled. Manage changes the name, schedule and email, or pauses new runs while keeping the archive. Skip the issue when nothing material happened records a skipped run when readings stay within their usual range. On-request issues have a daily account limit; scheduled issues do not.

When an issue does not go out

A failed run never sends a partial issue. Missing data is retried within three hours of delivery time; a rejected issue is retried once. If no issue is ready, the owner receives one email with the reason and next run time. The run log shows Failed and offers Retry.

Review an issue before others receive it

Under Manage, Share, turn on Review before sending and each issue waits for you to approve it before anyone else receives it.

Waiting for your review

With Review before sending enabled, the owner's email offers Approve and send, Edit on Ask the Grid and Skip this issue. Approve and Skip require confirmation; opening the email link alone changes nothing. Find pending issues under Manage, Runs. An optional review deadline either sends an untouched issue or leaves it unsent, as you choose.

Edit before it goes out

Preview the web, email and phone editions. Edit a heading or paragraph, or ask the agent to revise one section. Its revision preserves figures and citations and reports whether it succeeded. Send yourself a test email, then approve delivery by email and on Ask the Grid, or on Ask the Grid only.

Held issues

An issue the automated checks hold back waits for you with the reason. Send it yourself or leave it unsent. Issues built on your connected data stay private.

Read an evidence-backed issue

The October 8 ERCOT Morning Briefing showing its covered window, source cutoff, summary, and Share, Copy and Print / PDF actions.
The issue keeps its covered window and data cutoff beside the headline. This October 8 edition is a recorded example.

Follow the analytical structure

Check the issue number, covered window and data cutoff first. Read the summary, What changed since the last issue, notable readings beside their usual ranges, analysis and next watch items. The closing question opens the agent with the issue loaded. The full edition retains charts, sources, assumptions and methods.

Check the explanation for a price move

A brief can connect a notable price move with the findings and source observations available for that hour. Follow its citations to check the measurement time, forecast issuance time and method. A finding can support an explanation without proving a cause: a binding constraint alone does not establish a hub's exposure, and falling battery output does not establish exhausted stored energy. When the evidence leaves an alternative open, the explanation keeps that uncertainty attached.

Check the forecast behind the outlook

The report analyst uses the issue's frozen cutoff and prior-call scorecard. Ask what the preceding outlook got right or wrong to compare its recorded expectations and realizations. A latest live forecast is a separate investigation. Morning briefings use forecasts no older than two issue cadences that cover every complete requested hour. Source notes preserve model version and issuance time; performance scores compare the same model and version.

Read asset-to-hub comparisons

When an ERCOT report has an explicit resource-node and benchmark-hub path, its basis table compares those prices over matching intervals. Basis means node minus hub; RT-DA means real-time minus day-ahead at one location. Check the coverage and price basis beside the chart: real-time LMP comparisons are indicative, not final settlement or asset profit. A solar clock-hour comparison is not weighted by actual plant generation. The issue needs at least 95% matched price-interval coverage for every configured path before it can go out.

Check each watched asset

Custom morning briefings assess every saved asset against the evidence available at the issue cutoff. For ERCOT plants, verified owned resource-node links can supply local real-time and day-ahead price context. A nearby node is not a substitute for that identity, and local prices do not establish generation, battery dispatch, revenue or hedge performance. If requested output is unavailable, the issue explains which decision remains unresolved; missing output is not zero output.

Keep connected data private

Issues built on the owning account's connected data stay private. Public and unlisted reports are available only when every input preserves its source and privacy boundary.

Deliver, share and revisit each issue

An email edition of an Ask the Grid report with the issue title, current findings, and a link back to the complete report.
Email carries the short read and links to the full evidence. This October 8 edition is a recorded example.

Send published issues to Slack or Teams

Open the report's Manage → Schedule → Channel delivery and turn on the channels you want; they come from Settings → Connections in your workspaces. Each published issue posts its headline, period, data cutoff and TL;DR, with a Read full report button that keeps the report's access settings. Delivery runs separately from issue email and retries on its own. Drafts, skipped runs and held issues are not sent. Send latest issue posts the newest published issue now, and Recent deliveries shows what was sent or why it was not.

Email each issue

New reports email your verified account address; switch delivery under Manage, Schedule. Email includes the headline, summary, changes, notable readings, next watch items and up to two charts. Read the full issue opens the remaining evidence. Its closing question opens the agent with that issue loaded. Owner emails also link to Steer the next issue; recipient feedback appears under Manage, Runs.

Steer the next issue

Choose Steer the next issue below an issue or in the owner's email. Use More on, Less on or a short note to guide the next run. The report page lists active notes and lets you remove them. It keeps up to eight notes; a newer note on the same topic replaces the older one. Only the signed-in owner steers. Useful or Not useful works from the email link and appears under Manage, Runs; forwarding the link grants no editing access.

Send it to other people

Add colleagues by email under Manage, Share. Each person confirms the invitation with an account using that address, then receives new issues and can read the archive. An account can send fifty invitations in a rolling twenty-four hours. An address with a pending invitation, or one that already receives the report, is not emailed again; a revoked invitation can be sent once more within 24 hours, and the confirmation names any address that was skipped. Remove recipients or revoke pending invitations there. Recipients can stop emails from any issue. Share also chooses private, unlisted or public web access; public readers can subscribe.

Get a daily briefing by email

Ask the Grid writes the ERCOT Morning Briefing itself every morning, with every issue free to read without an account. Choose Get it by email on Reports or on the briefing's page, or during guided setup when you add its market; every email links back to the full issue and carries a link to stop the emails. Signed-out visitors to Reports find these briefings above the sign-in prompt, and the map's Live data panel links to its market's briefing.

Review overlapping email deliveries

Reports groups overlapping briefings for the same market with their delivery times and scopes. Keep both or switch off one email. Turning off a private report's email keeps its schedule and archive; pausing stops new issues. Similar coverage never cancels a delivery you chose.

Compare issues over time

Use the report's list of issues to return to the exact cutoff and evidence of an earlier run. A new issue can update the operating picture without silently revising what the prior issue knew. A forecast revision compares the prior and current published forecasts for the same delivery hours; it is different from comparing today's forecast peak with yesterday's realized or forecast peak. An individual hub's hourly price gap also has its own comparison: subtract the same-hour system move before evaluating its local threshold. A cross-hub median range applies to that median, not to every hub separately.

Did this guide get you unstuck?

One click is enough. No message or account required.

Related guides

Start hereToday & the Energy WireBegin with ranked live-grid conditions, then follow the supporting Radar desk, reporting, and original source.Save and monitorViews, Saved & sharingBegin from a reviewed live View, organize saved items into collections, import an existing list, and share an agent answer, a reproducible map scene, or an embed.Ask and investigateThe agentAsk about one market or compare several, inspect sources, attach map context, and continue from any claim or chart.