Utility Rate Case Preparation as a Production System

Why Rate Case Preparation Fails Without a Production System

A rate case is among the most document-intensive proceedings in regulated industry. A single filing can involve thousands of pages of workpapers, years of financial history, engineering studies, and witness testimony — all of which must cohere into a narrative that a public utility commission can follow, question, and ultimately accept. Yet most utilities still approach this process as a project, not a system.

The project mindset produces uneven results. Staff assemble evidence in silos, regulatory counsel reconciles inconsistencies at the last moment, and the resulting filing carries embedded gaps that intervenors exploit. Each rate case starts nearly from scratch, institutional knowledge walks out when experienced staff retire, and audit-trails are reconstructed after the fact rather than generated in real time.

A production system changes the operating logic entirely. Evidence assembles continuously, not episodically. Agents hold the methodology steady across every workpaper, every witness statement, and every exhibit. Compliance with commission filing requirements is verified before the filing leaves the building, not during discovery.

Understanding What a Public Utility Commission Actually Reviews

Before designing any evidence-assembly architecture, a regulatory team must internalize what a commission is evaluating. Commissions assess three foundational questions: whether the utility has properly identified its costs, whether those costs are prudently incurred, and whether the proposed allocation among customer classes is just and reasonable.

Each question carries its own evidentiary burden. Cost identification requires complete and reconciled accounting records tied to the test year. Prudency review requires contemporaneous documentation showing that capital expenditures followed a reasonable decision process at the time they were made. Rate design requires load research data, class revenue requirements, and an allocation methodology that withstands cross-examination.

The commission does not simply accept the utility's characterization of these issues. Staff analysts, the attorney general's office, and industrial intervenors will each probe for inconsistency. An exhibit that cites a different total than the supporting workpaper will become a contested issue. A witness who cannot explain how a cost was allocated will create a record of confusion that opposing counsel will amplify.

The practical implication is that the evidence standard for a rate case is not just accuracy — it is traceable accuracy. Every number must resolve to a source, and every source must be retrievable during hearings that may occur many months after the filing date.

Mapping the Evidence Architecture Before the First Agent Fires

Successful agentic rate case preparation begins with a complete map of the evidence architecture. This is not a technology exercise — it is a regulatory strategy exercise. The team must identify every exhibit class in the filing, the data source that feeds each exhibit, the transformation logic applied to that data, and the witness who will sponsor each piece of evidence.

This mapping exercise typically surfaces three categories of problem. First, data sources that have never been formally reconciled to each other — for example, a plant-in-service ledger that has not been tied to depreciation records since the last rate case. Second, transformation logic that exists only in a senior analyst's spreadsheet and has never been formally documented. Third, witnesses who will be asked to sponsor exhibits they did not prepare, creating testimony risk.

Once the evidence map exists, agents can be assigned to specific workflows. The goal is that no agent operates on data it cannot trace to a documented source, and no agent applies a transformation that has not been encoded as an explicit, auditable rule.

Building the Test Year Normalization Layer

The test year is the financial period that defines the rate case. A commission will scrutinize how the utility has handled known-and-measurable adjustments — items that fall outside normal operations during the test year but are expected to recur or resolve during the rate-effective period. Getting this right is foundational to everything else.

An agent assigned to test year normalization must do several things in sequence. It must ingest the general ledger for the full test period and identify accounts requiring adjustment. It must apply the utility's stated adjustment methodology consistently and flag any account where the adjustment exceeds a defined materiality threshold. It must produce a reconciliation that ties the normalized total back to the as-filed financial statements.

Each of these steps must generate a timestamped record. The record is not optional documentation — it is the compliance foundation. When commission staff requests support for a specific adjustment, the agent's log is the answer. The log shows what data was used, when it was processed, what rule was applied, and what the output was. Nothing in that chain should require reconstruction during discovery.

A second agent layer monitors the normalization for internal consistency. If a revenue normalization adjustment implies a particular load assumption, and a separate expense normalization uses a different load assumption, the consistency agent flags the conflict before the filing is assembled. This class of error — internally inconsistent adjustments — is a frequent intervenor target and can result in rejected adjustments if not resolved in the filing itself.

Cost-of-Service Study as a Coordinated Workflow

The cost-of-service study is the technical core of a rate case. It determines what it costs to serve each customer class, and that determination drives rate design. The study involves functionalization of costs to services, classification of costs by demand, energy, and customer characteristics, and allocation of classified costs to rate classes using load research data.

Each of these steps is a candidate for agent-driven execution. A functionalization agent reads the chart of accounts and applies the approved functionalization methodology, flagging any account where the mapping is ambiguous. A classification agent applies demand, energy, and customer fractions to each functionalized cost center, using factors derived from engineering studies that must themselves be documented in the record.

An allocation agent then distributes classified costs to customer classes using the utility's allocation factors, which are typically derived from load research conducted during or before the test year. The agent must carry the load research forward with full traceability — the allocation factor for a given class is not a number that appears in a workpaper without explanation. It is a computed value with a documented derivation.

Coordination across these three agent layers is where the system earns its value. The output of the functionalization agent is the input to the classification agent, and the output of classification is the input to allocation. Each handoff must be a verified transfer with a reconciliation check. A cost-of-service study where the three layers do not reconcile to the same total is not a filing — it is a draft.

Rate Design as a Downstream Production Step

Rate design follows cost-of-service but is not merely arithmetic. The commission must be satisfied that the rates proposed for each customer class recover the allocated revenue requirement without producing outcomes that are confiscatory or unduly discriminatory. That standard requires more than correct math — it requires a demonstration of reasonableness that anticipates commission questions.

An agent assigned to rate design begins with the class revenue requirements produced by the cost-of-service study and applies the utility's rate design principles — which may include minimum bill provisions, declining block structures, or demand charge design depending on the class. The agent must encode these principles explicitly, not approximate them from prior-year rates.

Rate design outputs must include impact analyses. Agents should automatically produce bill impact comparisons showing the effect of proposed rates on representative customers within each class, using actual billing data from the test year. These comparisons serve a dual purpose: they give commissioners the tangible information they need to evaluate rate reasonableness, and they give the utility's witnesses the exhibits they need to explain and defend the rate design under cross-examination.

A compliance agent then checks each proposed rate against the commission's filing requirements. This is not a general review — it is a checklist verification. The commission may require that residential rates include a specific cost comparison format, or that large commercial rates include a demand ratchet analysis. The compliance agent holds the filing requirements as a formal rule set and verifies that every requirement is satisfied before the filing package is assembled.

Depreciation and Plant Studies as Independent Evidence Threads

Depreciation studies and plant-in-service analyses run as parallel evidence threads that must be synchronized with the cost-of-service work. The depreciation study establishes the utility's allowed depreciation rates and determines the annual revenue requirement associated with recovering plant investment over time. Errors in this thread propagate through the entire filing.

An agent managing the plant-in-service record must reconcile the current plant ledger to the last rate case record, identify all additions and retirements during the intervening period, and verify that each addition has associated documentation of prudency. This is not an abstract verification — for major capital projects, the documentation may include board approval records, bid evaluations, and construction management reports.

The agent does not certify prudency; that determination belongs to regulatory counsel and witness testimony. But the agent ensures that the documentation exists, is retrievable, and is indexed to the relevant exhibit. A case where a major plant addition lacks retrievable prudency documentation is a case where the commission may disallow the investment, regardless of how correct the arithmetic is.

Depreciation rates themselves must be supported by an actuarial analysis that reflects the utility's actual plant mortality experience. Where an outside consultant has conducted the depreciation study, the agent must ensure that the study inputs tie to the plant records and that the study outputs are reflected correctly in the depreciation schedules embedded in the cost-of-service work.

Building Audit-Trails That Survive Discovery

The question of how can a utility prepare a rate case with coordinated agents that assemble cost-of-service evidence a public utility commission will accept comes down, in large part, to audit-trails. Commissions and intervenors have the right to request the support behind every number in the filing. That discovery process can extend months after the initial filing, and the utility must be able to produce the requested support promptly.

A production system generates audit-trails as a byproduct of normal operation. Every agent action is logged with the input state, the rule applied, the output, and a timestamp. That log is not stored separately from the filing — it is an indexed component of the filing package. When an information request arrives asking for the support behind a specific exhibit line, the response does not require reconstruction. The log entry is the response.

This architecture has practical benefits beyond compliance. When commission staff raises a question during the technical conference, the utility's witness can pull the exact derivation of a disputed number in real time. That capability changes the dynamic of the proceeding. Instead of committing to provide support in a subsequent information request response, the witness resolves the question in the room.

Audit-trail integrity also matters for the utility's own review process before filing. A quality assurance agent can traverse the full evidence chain, starting from filed exhibit totals and working back to source data, verifying that every transformation is documented and every intermediate output reconciles. This pre-filing review catches errors that would otherwise surface during discovery at maximum damage.

Readers familiar with related compliance disciplines will recognize parallels to how agentic systems handle audit documentation in other regulatory contexts — for instance, the SDWA compliance and EPA reporting framework for water utilities at https://www.labarna.ai/blog/sdwa-compliance-and-epa-reporting-for-water-utilities applies similar principles of continuous documentation to another category of evidence that must survive regulatory scrutiny.

Witness Preparation as an Agent-Supported Function

Expert witnesses are the human face of a rate case filing. Commissioners ask questions, witnesses answer, and the quality of those answers shapes the record. Witness preparation is therefore not optional polish — it is a core function of the filing process.

Agents can support witness preparation in several specific ways. A witness package agent assembles, for each witness, the complete set of exhibits they will sponsor, the workpapers behind those exhibits, and the cross-examination questions that prior rate cases in the same jurisdiction have generated. The witness does not receive a disorganized folder — they receive a structured briefing that maps their testimony to the underlying evidence in retrievable sequence.

A question-and-answer simulation agent can be populated with information request responses from prior proceedings and used to generate likely staff cross-examination questions based on the current filing's contested issues. This is not a prediction of what the commission will ask. It is a structured preparation tool that forces witnesses to articulate the logic behind their exhibits in the same terms the filing uses.

The witness preparation function also generates a secondary benefit: it surfaces internal inconsistencies that the evidence assembly process may have missed. When a witness cannot explain how a particular number was derived, that inability is itself a signal that the derivation may not be adequately documented. The agent escalates those instances to the regulatory team before the hearing, not after.

Information Request Management as a Production Function

Once a filing is submitted, the utility enters the information request cycle. Commission staff, the attorney general, and intervenors each submit data requests, and the utility must respond within the deadlines the commission establishes. Responses that are late, incomplete, or internally inconsistent with the filing create record problems that can affect the outcome.

An information request management agent tracks every request, maps it to the relevant exhibit and workpaper, assigns a draft response to the appropriate subject matter expert, and monitors the response against the deadline. This is workflow management, but it is workflow management where each step is timestamped and auditable.

The agent also checks draft responses for consistency with the original filing before they are submitted. An information request response that uses a different number than the exhibit it is supporting creates a record inconsistency that opposing counsel will identify and amplify. The consistency check is not a courtesy — it is a compliance function.

Where information requests require new calculations — for example, a request to show the revenue requirement impact of a different depreciation rate — a calculation agent can execute the analysis using the same methodology and data sources as the original filing. The result is a supplemental analysis that is methodologically consistent with the filing, not a separate analysis that introduces unexplained differences.

Integrating Energy Data and Load Research Into the Evidence Chain

Load research is the empirical foundation for rate design, and its integrity affects every downstream calculation in the filing. Load data is typically collected over multiple years through interval metering programs and must be validated, weighted, and summarized into the class load profiles that drive cost allocation.

An agent managing the load research integration must validate the load data against the meter data management system, identify and handle missing intervals, and apply the utility's approved weighting methodology to produce class load profiles. Each of these steps must be documented because load research methodology is frequently contested by industrial intervenors who benefit from alternative allocation factors.

The energy accounting reconciliation is a related function. The total energy accounted for in the load research must reconcile to the total energy accounted for in the revenue and expense data used in the cost-of-service study. A gap in that reconciliation — even if the total energy is correctly stated in both places — creates a technical question that commission staff will pursue.

This domain intersects directly with broader challenges in energy data management that utilities encounter across multiple regulatory proceedings. The discipline of building a sovereign, owned data architecture for regulatory evidence — rather than depending on vendor-hosted systems that may change without notice — is increasingly central to how regulated utilities think about rate case risk. The approach also connects to environmental and compliance reporting frameworks, where data continuity across multi-year evidence chains is equally critical, as explored in the context of CSRD and ISSB climate reporting on sovereign infrastructure at https://www.labarna.ai/blog/csrd-and-issb-climate-reporting-on-sovereign-infrastructure.

Maintaining the Filing in a Living State

A rate case filing is not static. Between the initial filing and the final commission order, the record will be supplemented by information request responses, rebuttal testimony, and potentially a settlement agreement. The filing package must remain internally consistent through all of these additions.

A configuration management agent maintains the canonical state of the filing at every point in the proceeding. When a new exhibit is added or an existing exhibit is revised in response to an information request, the agent updates the filing index, verifies that the revision does not create a conflict with other exhibits, and logs the change with the reason and the authorized reviewer.

This living-state maintenance is where many utilities encounter their most costly errors. A revision made late in the proceeding that inadvertently introduces an inconsistency with an earlier exhibit — and is not caught before the final brief — can produce a disallowance or a condition on the rate order. A configuration management agent reduces that risk by treating every revision as a change event that triggers an automated consistency check across the full filing.

The living-state architecture also supports settlement negotiations. When commission staff and the utility enter settlement discussions, the ability to quickly model the financial impact of proposed adjustments — using the same cost-of-service methodology as the filing — accelerates resolution. An agent can execute scenario analysis against the filed methodology within hours of receiving a settlement proposal, giving the utility's negotiating team a quantified basis for evaluating each concession.

Deploying Sovereign AI Infrastructure for Rate Case Production

For utilities serious about building this kind of evidence infrastructure, the deployment model matters as much as the agent design. Rate case data — including plant records, financial statements, load research, and customer billing data — is among the most sensitive information a regulated entity holds. Deploying that data through vendor-hosted systems that the utility does not control creates regulatory risk, data governance risk, and long-term dependency risk.

Labarna AI is built as sovereign production intelligence, meaning every agent, every data pipeline, and every audit-trail mechanism is deployed under the client's ownership through Ghost Architecture. The utility owns the source code, the data, the agents, and the intelligence that accumulates over successive rate cases. That ownership matters for regulatory evidence because the utility can demonstrate to the commission exactly how its evidence was assembled — there is no black-box vendor between the utility and its own data.

Agentic AI deployment of this kind starts in the low tens of thousands for focused builds, scaling by agent count, integration complexity, and operational scope. For a utility facing a contested rate case with multiple agent layers spanning cost-of-service, depreciation, and rate design functions, the scope will be more substantial — but so will the reduction in external consulting expense and the improvement in filing quality that results from continuous evidence assembly rather than episodic project work.

For utilities uncertain where to begin, the Operational Intelligence Diagnostic is free and produces a full deployment blueprint within 48 hours. It maps the existing evidence architecture, identifies the highest-risk evidence gaps, and produces a sequenced deployment plan that an organization can act on immediately.

Building the Institutional Memory Layer

A rate case is not a one-time event. A utility typically files every three to seven years, and each subsequent case must reference and sometimes distinguish the last commission order. The evidence developed in one case — particularly plant studies, load research, and depreciation analysis — carries forward as a reference point for the next proceeding.

A utility that treats each rate case as a fresh project loses the institutional memory that accelerates the next filing and reduces the risk of inconsistency with prior commission findings. A utility that operates rate case preparation as a production system accumulates that memory in the system itself.

The institutional memory layer is an indexed archive of prior filings, commission orders, information request responses, and settlement agreements, linked to the agent workflows that produced the current filing. When a new filing begins, agents query this archive to identify commitments made in the last order, track whether those commitments have been fulfilled, and flag any proposed treatment in the current case that is inconsistent with a prior commission finding.

This is the compounding value of agentic infrastructure — it does not reset. Each rate case adds to the knowledge base, and the next filing begins from a higher level of evidentiary readiness than the one before it. Labarna AI's sovereign AI infrastructure model is specifically designed to deliver this kind of compounding intelligence, with agents that accumulate operational knowledge under client ownership rather than deprecating it when a vendor relationship changes.

Connecting Rate Case Production to Broader Regulatory Operations

Rate case preparation does not exist in isolation. A utility also manages annual compliance filings, environmental reporting, procurement audits, and federal energy regulatory obligations. The same evidence discipline that produces a strong rate case filing — traceable data, explicit transformation rules, timestamped audit-trails — is the foundation for all of these regulatory functions.

A utility that deploys coordinated agents for rate case production is building regulatory operations infrastructure, not just a rate case tool. The agent that reconciles plant records for the rate case is the same agent architecture that supports a plant audit or a used-and-useful analysis in a separate proceeding. The load research validation function supports both rate case cost allocation and annual energy forecasting.

Labarna AI's deployment model, operating under RAKEZ License 47013955 through TFSF Ventures FZ-LLC and founded on 27 years of payments and software experience, reflects exactly this logic. Those researching whether Labarna AI is legit — evaluating the organization behind the technology, the ownership structure, and the founder's track record — will find a verifiable registration, a documented Ghost Architecture model under which clients retain all source code and IP, and a positioning as production intelligence rather than advisory output. Labarna AI reviews and positioning are grounded in these specifics, not in testimonials or marketing claims.

The question of how a regulated utility sustains regulatory credibility over many proceedings is ultimately a question of infrastructure. Commissions develop institutional memory too — they remember which utilities file clean, consistent evidence and which ones require repeated supplemental responses. A production system that generates compliant, traceable evidence as a continuous output is the most durable answer to that question.

About Labarna AI

Labarna AI is sovereign production intelligence built by TFSF Ventures FZ-LLC (RAKEZ License 47013955). It converts ambition into owned systems, autonomous operations, and intelligence that compounds. Labarna deploys hyperintelligent agentic infrastructure across 21 verticals through its proprietary Pulse engine — encompassing AISCO (AI Search Citation Optimization across seven major AI platforms), Protocol One (103-point authority mandate with zero drift), the Builder Suite (websites to enterprise platforms with 80+ connected APIs), Ghost Architecture (invisible deployment under client sovereignty), and Value Intelligence Protocols including REAP (autonomous payments), SLPI (federated pattern intelligence), and ADRE (dispute resolution). AI was built to answer — Labarna was built to act.

Get Started with Labarna AI

Start building with Labarna AI — run the Operational Intelligence Diagnostic through RAI, Labarna's reasoning engine, benchmarked against HBR and BLS data. Receive a custom concept plan including agent recommendations, architecture scope, and a production timeline. Enter the system at labarna.ai. Responses arrive within 24-48 hours.

Originally published at https://www.labarna.ai/blog/utility-rate-case-preparation-as-a-production-system

Written by Labarna AI Research