How we turn a regulatory record into a brief you can trust.

A daily crawl, structured extraction, and a deadline methodology built so a lawyer never sees a wrong date presented as a right one.

The pipeline

Crawl

Daily crawl over the primary source for each market:

  • Texas: PUCT Interchange (all filings) and ERCOT stakeholder pages (NPRRs, protocol revisions, market notices). Live
  • California: The CAISO filings index plus referenced FERC ER/EL dockets. Beta
  • PJM: FERC eLibrary (primary), the Independent Market Monitor's filings, and PJM's published stakeholder/auction calendar. PJM's own JS-walled library is used as enrichment, not a dependency. Beta

Extract

Each filing is read in full — attachments included, not just the cover letter — and structured into:

  • Parties — filer, intervener, respondent
  • Positions — support / oppose / conditional with the specific ask
  • Dollar impacts — where stated in the filing
  • Deadlines — effective dates, hearing dates, comment periods
  • Cross-references — related dockets, CAISO initiatives, CPUC proceeding numbers where cited

PJM adds a numeric sub-schema for RPM/RTEP parameters with unit validation, so UCAP/ICAP distinctions can't silently corrupt a number.

Ground

Answers and summaries are grounded in the extracted corpus with citations back to the source filing. Claims that cannot be sourced to a specific document are dropped before delivery. No citation, no claim.

Compose

A daily brief at 6:00 AM CT, scoped to the dockets and topics you track, with urgency driven by real deadlines — not by filing volume or recency alone. The brief is personalized: only the proceedings you follow, summarized for your market.

Deadline methodology — why this matters

A wrong deadline shown confidently is worse than an honest "we don't know yet." Here is exactly how we handle dates.

Certain deadlines — shown directly

  • FERC rehearing windows — 30 days from the order date, by statute. We compute this directly from the order.
  • Requested/confirmed effective dates — stated in the filing, extracted as-is.
  • Published stakeholder and auction dates — from PJM's calendar and CAISO's published schedules. PJM has unusually clean confirmed dates; a large share of PJM deadlines shown are confirmed, not estimated.

Estimated deadlines — always labeled

Any date inferred by the model from filing language — not extracted from a primary-source calendar or a statutory formula — carries an estimated badge and a verify link. We never present a computed deadline as confirmed.

FERC protest/comment window — we don't guess it

The FERC comment and protest window lives in the FERC Notice — a separate document issued by FERC days after a filing posts — not in the filing itself. We do not compute or estimate the protest deadline from the filing date. Instead, we link you directly to the FERC Notice so you can confirm the window yourself. This is the right behavior, not a limitation.