Skip to content
RateBase

Methodology

Coverage, source hierarchy, observation stages, review, and publication.

Coverage

Current publication includes investor-owned electric and natural-gas base-rate cases from 2020 forward in Arizona, Florida, Georgia, Illinois, Louisiana, Michigan, New Jersey, New York, North Carolina, Ohio, Oregon, Pennsylvania, Texas, Virginia, and Wisconsin. Record-level source depth is disclosed through optional directory columns and on case pages. Data-center and large-load tariffs use a separate public contract.

Source hierarchy

Final commission orders and official docket records control. Procedural orders, utility applications, testimony, settlements, investor-relations material, and SEC filings follow in descending order of authority. Secondary sources are for discovery, not publication support.

Metric stages

Utility request, staff/I&E, consumer advocate, small-business advocate, other intervenor, utility rebuttal or rejoinder, settlement, recommended decision, and authorized values remain separate. Every material observation identifies its party, stage, scope, date, unit, and direct source. A settlement is not authorized until the Commission approves it.

Date basis

Every material date carries a basis: official Commission, company filing, statutory backstop, proposed settlement, procedural inference, or analyst estimate. Conditional dates retain their condition text, and multi-step rates retain each step. A suspension expiration is not a decision date; a proposed effective date is not an actual effective date.

Update cadence

Source surfaces are checked according to their configured cadence. Only the adapter capabilities listed in RateBase's capability report produce normalized candidates automatically; other detected changes enter a manual mapping queue. A final order or rates-effective event can trigger an earlier profile review, but every detected change remains a staged candidate until explicit publication approval.

Adapter capabilities

The level below describes what each adapter can normalize into a reviewable candidate. Discovery-only adapters detect source changes; they do not create approved facts or economics automatically.

AdapterCapabilityActive endpointsTyped proposals
fl_fpsc_rateDocument metadata1document, citation
ga_psc_docketEvent proposals3document, citation, event
il_icc_rateEvent proposals1document, citation, event
legacy_sourceDiscovery only33None
manual_researchDiscovery only149None
mi_mpsc_rateDiscovery only1None
nc_ncuc_rateEvent proposals2document, citation, event
nj_bpuDocument metadata0None
nj_bpu_docketDiscovery only1None
official_rate_listingDocument metadata6document, citation
oh_pucoDiscovery only1None
pa_pucEvent proposals0document, citation, event
pa_puc_activeEvent proposals1document, citation, event
pa_puc_docketEvent proposals0document, citation, event
tx_puctDiscovery only1None
tx_rrc_gasDiscovery only1None
va_scc_caseDiscovery only1None

The complete machine-readable report, including configured endpoint counts and notes, is available in the public data downloads.

Publication workflow

Automated collection creates source-run candidates. Explicit approval writes canonical relational records transactionally; database audits then generate the site and public downloads. Material automated updates never publish directly.

To report a correction, identify the case, field, proposed value, and the supporting official source. The public correction route is published with the repository; submissions without source evidence are evaluated but do not replace approved data.