Utilities are carrying more at once than they ever have. Aging infrastructure needs replacing. Grid modernization is accelerating. Electrification and large new loads are pushing demand up. Customer affordability is a live political issue in nearly every jurisdiction. And the regulatory environment around all of it is becoming more dynamic: new requirements, updated planning expectations, and more formalized reporting schedules are emerging across North America, increasing both the volume of information a utility must manage, and the rigor expected of it in a proceeding.

Capital Planning has Entered a New Era

Regulatory scrutiny is not new. The rate case has always been demanding. What has changed is the context around it. The environment in which utilities plan, file, and defend investments is more dynamic, more data-intensive, and more exposed to legal and political challenge than it was a decade ago.

The consequences of getting it wrong have changed too. A gap between what a utility files, plans, or forecasts and what it ultimately spends can be problematic, and even a disallowance risk. In one recent proceeding, tens of millions in proposed investment was cut after the direction of the case shifted. In another, a utility saw nearly a third of its capital plan reduced, with the turning point traced back to a single inconsistent discovery response.

Necessity is Not Enough

A new substation, a gas main replacement, a wildfire mitigation program, a feeder upgrade: each may be necessary from an engineering standpoint. Under regulation, necessity is the starting point, not the argument. The utility must demonstrate why the investment is prudent, how it aligns with regulatory and policy requirements, what it does to customers' bills, and why cost recovery should be approved. A compelling narrative still matters. It is no longer sufficient on its own.

Four Forces Raising the Bar

Load forecasting has become the first line of attack.

Hyperscale data centers have introduced a kind of uncertainty traditional load forecasts were never built for. A single development can add gigawatts to a service territory, and the timing and certainty of that load are often unclear. The IEA projects that global data center electricity consumption will more than double to around 945 TWh by 2030, with the United States accounting for the largest share of that increase. Forecasts built on steady, predictable growth now have to accommodate large, discrete uncertainties, and regulators know it. They are interrogating the assumptions behind these forecasts more closely than ever.

Intervenors are better resourced, and they read across filings.

Consumer advocates, industrial customers, and environmental organizations arrive with expert witnesses and independent analysis. More importantly, they cross-reference. A proceeding is no longer evaluated in isolation; it is examined against the full body of what the utility has said before. Inconsistencies that once went unnoticed are now found and used.

What worked in the last filing may not work in the next.

Approval standards shift. Documentation requirements grow. A change in commission membership can alter evidentiary expectations abruptly, even when the underlying plan has not changed. For utilities operating across multiple states, assumptions have to hold up in every jurisdiction at once, each with its own regulatory context. The margin for error keeps shrinking.

Elected officials face their own political pressure.

New U.S. federal efforts to regulate how data centers and other large electricity users connect to and impact the power grid, are focusing on how these large loads don’t create higher costs or reliability problems for existing customers. But household electricity and energy bills have risen sharply in many areas – over the last decade, some cases have seen rises of over 30%. This isn't just a technical challenge to a capital plan's merits – it's now a political one. Elected or politically appointed officials, have a direct incentive to be seen pushing back on utility spending.

A New Standard for Defensibility

At the heart of this is a change in what it means to defend a capital plan.

Explaining a decision used to be enough: present the context, outline the rationale, connect forecasts to investments and investments to benefits. Proving a decision requires more. Every claim tied to a specific, traceable input. Assumptions versioned over time so their evolution can be justified. The numbers in testimony matching, precisely, the numbers in the underlying models and prior filings.

The gap between explaining and proving shows up in predictable places. Between filings, where assumptions drift. Between teams, where engineering and legal are working from different versions of the same data. Between scenarios, where updates are applied inconsistently. And across time, where the numbers that were filed diverge from the numbers now believed.

Closing that gap is not a matter of working harder or producing more documentation. It requires a different approach to how evidence is structured, maintained, and used. The utilities most exposed to these pressures, those with multi-jurisdiction footprints, active filing calendars, or recent changes in commission leadership, are already moving. They are treating the assumptions underlying their capital plans as a structured asset, managed with the same rigor as the plan itself. That approach is now being formalized for broader adoption. At IFS Copperleaf, we call it Regulatory Intelligence.

How it Works: From Explaining to Proving

Regulatory Intelligence takes the structured data already underlying investment decisions in Copperleaf, the assumptions, scenarios, and benefit-cost logic, and organizes it into an evidence base that can be used directly in filings, discovery responses, and ongoing regulatory engagement.

Each assumption is recorded once, in a centralized register, and linked to its origin: a regulatory directive, a technical study, an analytical model. Every assumption is versioned. The system preserves what was used at the point of filing, what has changed since, and why. When a regulator or intervenor asks what the utility's position was at a specific moment, the answer is retrieved from a preserved version of the record, not reconstructed from memory and archived files.

When a discovery request arrives, the system identifies the relevant assumptions, analyses, and prior filings and assembles a draft response grounded entirely in the existing record, with citations back to the supporting data. Regulatory and legal teams review and refine it. They are no longer starting from a blank page or reconciling conflicting sources under deadline.

Because the same register supports both planning and regulatory work, numbers cited in a rate case align with those used in the IRP. Updates propagate systematically rather than selectively. The gaps between teams, scenarios, and time periods are reduced at the source.

This does not eliminate complexity. It gives complexity a structure, and structure is what makes it defensible. It also does not replace the judgment of regulatory teams or legal counsel, and it does not determine how a utility positions its case. It changes the starting point.

What it Looks Like on a Friday Afternoon

A discovery request lands late on a Friday. It asks how a specific assumption was derived and where it has been used across prior filings. In most organizations, that triggers days of pulling data from multiple systems, reconciling differences, and rebuilding an answer under deadline, with the risk of a new inconsistency riding along.

With a structured evidence base, the assumption is already versioned, already linked to its source, already connected to the filings it appears in. By Monday morning the team is reviewing a cited response, not building one. The effort moves from reconstruction to validation.

The same holds in the weeks before a filing, when the final stretch is spent refining how the plan is presented rather than rebuilding the evidence behind it. And it holds when an inconsistency is challenged across jurisdictions, where a versioned history lets the team show exactly how and why an assumption evolved. A potential vulnerability becomes a defensible position.

One Question Worth Asking

If an intervenor identified a discrepancy between your most recent IRP and your latest rate case filing tomorrow, how quickly could your team produce a clear, consistent, fully supported explanation?

For some utilities the answer is hours. For others it is days. For some it means rebuilding the analysis. That answer is increasingly the best measure of how prepared a utility is for the regulatory environment it now faces. The challenge is no longer just deciding where to invest. It is proving, with precision, why those investments deserve approval, and being able to prove it on demand.