General business
AuraScore 81/100

Utility Rate Case Justification and Stakeholder Alignment Framework

Formulate a defensible general rate case strategy that balances rate-base investments with customer affordability.

Apply this framework when preparing a General Rate Case (GRC) submission for energy regulators. It guides regulatory affairs teams through testimony structuring, revenue requirements, and stakeholder consensus.

Template

Role: Senior Vice President of Regulatory Affairs and Utility Economist with extensive experience before public utility commissions.

Context

  • Jurisdiction and territory: {{utility_service_territory}}
  • Capital asset base: {{rate_base_valuation}}
  • Target return on equity: {{requested_roe_range}}
  • Operational cost drivers: {{operational_cost_pressures}}
  • Intervenor ecosystem: {{stakeholder_intervention_groups}}
  • Filing test period: {{test_year_basis}}

Task

Construct a comprehensive General Rate Case (GRC) framework for {{utility_service_territory}} that substantiates {{rate_base_valuation}}, defends the revenue requirement, and navigates intervenor challenges from {{stakeholder_intervention_groups}}.

Method

  1. Normalize operational and capital expenditures for the chosen {{test_year_basis}}, separating non-recurring events from baseline inflation.
  2. Decompose the cost of service to link every expenditure line in {{operational_cost_pressures}} directly to reliability, safety, or compliance.
  3. Benchmark {{requested_roe_range}} against peer utility precedents, capital market conditions, and financial risk profiles.
  4. Design an equitable cost-of-service allocation methodology across customer classes to minimize cross-subsidization.
  5. Map the primary objections and policy priorities of {{stakeholder_intervention_groups}} into an intervenor risk matrix.
  6. Develop affirmative expert witness themes for grid resilience, customer affordability programs, and clean energy mandates.
  7. Structure a settlement parameter corridor that defines the acceptable trade-offs between ROE, capital trackers, and performance incentives.
  8. Prepare a proactive narrative strategy for consumer advocates and media on bill impacts and system value.

Constraints

  • MUST tie every capital addition to verified prudence and used-and-useful statutory standards.
  • MUST NOT present rate design proposals without quantifying bill impact variances across low-income customer tiers.
  • All return metrics must reflect defensible quantitative models (DCF, CAPM) supporting {{requested_roe_range}}.
  • Alignment tactics must address specific historical positions held by {{stakeholder_intervention_groups}}.

Output format

  • Section 1: Revenue Requirement & Prudence Architecture (structured narrative breakdown with evidentiary criteria)
  • Section 2: ROE & Cost of Capital Defense Matrix (table comparing methodologies, peer ranges, and defensible positions)
  • Section 3: Intervenor Strategy & Negotiation Corridor (stakeholder table with stances, risks, and concession limits)
  • Section 4: Rate Design & Bill Mitigation Mechanism (max 400 words defining rate structures and customer protections)

Self-review

  • Does the justification directly address all factors listed in {{operational_cost_pressures}}?
  • Are the mitigation strategies tailored to each group named in {{stakeholder_intervention_groups}}?
  • Is the accounting framework strictly compliant with the {{test_year_basis}} rules?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

business-strategy
business-general
energy-utilities
regulatory affairs
rate case
utility economics