Review state

A passed review date marks material for review and does not make a dated historical fact false; expired overrides and unsupported assertions presented as current remain integrity failures.

As of 2026-09-29: 2,390 curated rows in 39 families — 2,388 current, 2 due for review, 0 undated.

Due for review

1 family

Clean-energy obligation assertions 2 of 297 assertions

  • commission decision on the 2026 Clean Energy Compliance Reportceta-20169-determination-cecr-2022-2025· claude-w14· checked 2026-09-22
    6 days overduereview after 2026-09-23
  • commission review of Avista's 2026 Clean Energy Compliance Report: written comments invitedceta-20169-event-cecr-comments-2026· claude-w14· checked 2026-09-22
    6 days overduereview after 2026-09-23

Every curated family

Counts partition each family's rows. A row's due date is its own review date where the file records one, otherwise the date it was checked plus the family's declared cadence; the basis column says which and why.
FamilyRowsCurrentDueUndatedCadenceBasis
Cited source correctionspipeline/config/overrides.yaml0 overrides0—0filed datesreview_after sets the due date; created is the date the row was last readAn override past review_after fails the build (overrides.py), so a release that passed never lists one due; the count is the corrections in force
Field notescontent/stories4 stories4—0filed datesreview_after sets the due date; authored is the date the row was last readreviewed stays null until editorial acceptance (W42); authored is the date the note was written
Clean-energy obligation assertionspipeline/config/crosswalks/clean_energy_obligations.csv297 assertions29520filed datesreview_after sets the due date; checked is the date the row was last readA row past its review date stays on the utility's page as filed, marked review_due
Named-load facilitiespipeline/config/crosswalks/named_loads.csv3 facilities3—0filed datesreview_after sets the due date; checked is the date the row was last read
Named-load assertionspipeline/config/crosswalks/named_load_assertions.csv25 assertions25—0filed datesreview_after sets the due date; checked is the date the row was last read
BPA supply-account assertionspipeline/config/crosswalks/supply_accounts.csv103 assertions103—0filed datesreview_after sets the due date; checked is the date the row was last readA row past its review date stays on the utility's page as read, marked review_due; its pinned document does not change
BPA customer (BES id) linkspipeline/config/crosswalks/bpa_customer.csv2 links2—0filed datesreview_after sets the due date; checked is the date the row was last readOne reviewed link per utility, read at the pinned BPA workbook cell that lists it; a utility without one gets no supply account
BPA supply account: bill tracepipeline/config/crosswalks/supply_bill_trace.csv7 rows7—0180 daysverified_on plus a declared 180-day cadence sets the due date: tariff sheets change with rate cases and periodic riders; review twice a year
BPA supply account: FERC coverage linespipeline/config/crosswalks/supply_ferc_records.csv6 lines6—0filed datesreview_after sets the due date; checked is the date the row was last readRead from PUDL's FERC extracts, the eCFR and FERC's CID listing on the date given; PUDL's EQR snapshot is overwritten monthly
Expectations ledger: forecastspipeline/config/crosswalks/forecasts.csv2 forecasts2—0365 dayschecked plus a declared 365-day cadence sets the due date: utilities file integrated resource plans every two years with interim updates; review yearly so no vintage is missed
Territory identity: Washingtonpipeline/config/crosswalks/wa_ecology_utility.csv65 rows65—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: EIA-860 and EIA-861 publish annually; review against each new annual edition
Territory identity: Oregonpipeline/config/crosswalks/or_odoe_utility.csv42 rows42—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: EIA-860 and EIA-861 publish annually; review against each new annual edition
Territory identity: Idahopipeline/config/crosswalks/id_gis_utility.csv28 rows28—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: EIA-860 and EIA-861 publish annually; review against each new annual edition
Territory identity: Montanapipeline/config/crosswalks/mt_coop_utility.csv25 rows25—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: EIA-860 and EIA-861 publish annually; review against each new annual edition
Expectations ledger: rowspipeline/config/crosswalks/expectations.csv223 rows223—0365 dayschecked plus a declared 365-day cadence sets the due date: utilities file integrated resource plans every two years with interim updates; review yearly so no vintage is missed
Expectations ledger: run familiespipeline/config/crosswalks/forecast_families.csv4 families4—0365 dayschecked plus a declared 365-day cadence sets the due date: reviewed yearly against the publisher's current page or edition
Ownership parent chainspipeline/config/crosswalks/ownership_parents.csv22 rows22—0365 dayschecked plus a declared 365-day cadence sets the due date: parent chains come from annual Form 10-K and equivalent filings
Ownership paths: reviewed plantspipeline/config/crosswalks/ownership_paths_plants.csv2 plants2—0365 dayschecked plus a declared 365-day cadence sets the due date: parent chains come from annual Form 10-K and equivalent filings
Ownership transferspipeline/config/crosswalks/ownership_transfers.csv2 rows2—0365 dayschecked plus a declared 365-day cadence sets the due date: parent chains come from annual Form 10-K and equivalent filings
Hydro identitypipeline/config/crosswalks/hydro_identity.csv265 rows265—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: reviewed yearly against the publisher's current page or edition
Curated display names and aliasespipeline/config/crosswalks/aliases.csv254 rows254—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: EIA-860 and EIA-861 publish annually; review against each new annual edition
HIFLD line ownerspipeline/config/crosswalks/hifld_line_owners.csv64 rows64—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: reviewed yearly against the publisher's current page or edition
Retail tariff sheetspipeline/config/crosswalks/retail_tariffs.csv16 schedules16—0180 daysretrieved_on plus a declared 180-day cadence sets the due date: tariff sheets change with rate cases and periodic riders; review twice a yeareffective_date is the sheet's own date, a historical fact, never a review date; retrieved_on is when the sheet was read
Retail tariff componentspipeline/config/crosswalks/retail_tariff_components.csv91 rows91—0180 daysverified_on plus a declared 180-day cadence sets the due date: tariff sheets change with rate cases and periodic riders; review twice a year
Bills printed on tariff sheetspipeline/config/bill_cases.yaml1 examples1—0180 daysverified_on plus a declared 180-day cadence sets the due date: tariff sheets change with rate cases and periodic riders; review twice a year
FERC Form 1 respondentspipeline/config/crosswalks/ferc1_utilities.csv6 rows6—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: FERC Form 1 is filed annually
FERC Form 1 sellerspipeline/config/crosswalks/ferc1_sellers.csv217 rows217—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: FERC Form 1 is filed annually
Balancing authority anchorspipeline/config/crosswalks/ba_anchors.csv12 rows12—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: reviewed yearly against the publisher's current page or edition
BPA pathspipeline/config/crosswalks/bpa_paths.csv31 paths31—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: reviewed yearly against the publisher's current page or edition
BPA line keys for repeated codespipeline/config/crosswalks/bpa_line_keys.csv18 pins18—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: BPA reloads the layer weekly and every build reports pins that stop matching (geometry.bpa_line_key_drift); review yearly otherwise
BPA line dossier statementspipeline/config/crosswalks/bpa_line_evidence.csv8 statements8—0filed datesreview_after sets the due date; checked is the date the row was last readA row past its review date stays on the line's page as stated, marked review_due; a later edition of its document may restate it
Cap-and-Invest auctionspipeline/config/crosswalks/cca_auctions.csv22 auctions22—090 daysreviewed_on plus a declared 90-day cadence sets the due date: Washington holds Cap-and-Invest auctions quarterly
Large-load tariff registrypipeline/config/crosswalks/large_load_tariffs.csv22 rows22—0180 daysreviewed_on plus a declared 180-day cadence sets the due date: tariff sheets change with rate cases and periodic riders; review twice a year
Notable lifecycle eventspipeline/config/crosswalks/notable_lifecycle_events.csv26 events26—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: reviewed yearly against the publisher's current page or edition
Request to generator dispositionspipeline/config/crosswalks/queue_generator_links.csv263 rows263—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: EIA-860 and EIA-861 publish annually; review against each new annual editionchecked is when the identity source was read; an unresolved row can resolve with a newer EIA edition or a new public document
Fuel Mix Disclosure claimantspipeline/config/crosswalks/wa_commerce_claimant.csv77 rows77—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: Washington Commerce publishes Fuel Mix Disclosure annually
Oregon DEQ supplier namespipeline/config/crosswalks/or_deq_supplier.csv50 rows50—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: Oregon DEQ reissues its electricity supplier workbook annually
Cap-and-Invest utility namespipeline/config/crosswalks/wa_ecology_cca_utility.csv56 rows56—0365 daysreviewed_on plus a declared 365-day cadence sets the due date: Ecology publishes no-cost allowance allocations annually
Dataset descriptions: publisher cadencepipeline/config/datasets.yaml29 datasets29—090 dayscadence.checked plus a declared 90-day cadence sets the due date: release schedules quoted from publisher pages go stale within a quartercadence.checked is the date the publisher's release pages were read; the cadence facts are quoted as of that date

Not covered

  • efsec facilitiespipeline/config/crosswalks/efsec_facilities.csv
    no reviewer or date column; each row cites its EFSEC facility page and nothing records when it was read
  • obligation uncertaintiespipeline/gridmap/build/obligations.py
    source caveats (UNCERTAINTIES) carry a status and a research anchor but no checked date
What the four states mean
  • current: the due date (review_after as filed, or the checked date plus the family's declared cadence) has not passed
  • review due: the due date has passed: listed under items_due, presented as filed and marked
  • undated: no checked or review date on the row
  • undated cadence: checked date only: no review cadence declared; current until one is declared

Release 20260929T050546Z-51ae0f7d3c78