# An Energy Audit Can Calculate Its Savings Correctly and Still Be the Number Nobody Actually Realizes
Author: Nitin Verma
Author URL: https://insights.spans.co.in/author/nitin-verma
Published: 2026-11-07
Meta Title: Energy Audit Savings Estimate vs Realized Savings | Spans
Meta Description: An energy audit's payback calculation is a correct engineering estimate based on the baseline conditions measured at the time. Whether a plant actually realizes those savings after implementation depends on operating conditions nobody goes back to verify.
URL: https://insights.spans.co.in/energy-audit-savings-vs-realized-savings-wastewater

Every [energy audit](https://en.wikipedia.org/wiki/Energy_audit) commissioned for an [ETP](https://spans.co.in/effluent-treatment-plant-etp/) or [STP](https://spans.co.in/sewage-treatment-plant-stp/) ends with a number: replace this blower, retrofit that pump with a VFD, and the plant will save a calculated percentage of energy cost with a stated payback period. That calculation is correct, computed properly from the baseline consumption data and equipment specifications measured at the time of the audit. It does not confirm the plant actually realizes those savings after the project is implemented, because realized savings depend on whether operating conditions, load, duty cycle, hours of operation, still match what the audit measured, and nothing in the standard audit process goes back afterward to check.

![A flat dashed projected savings line, assumed and never rechecked, against a wavy actual conditions line that drifts away from it over two years, with no one measuring the gap](https://spans.co.in/images/blog/energy-audit-savings-vs-realized-savings-inline.png)

## A savings estimate and a savings outcome are different claims

An energy audit answers: given the baseline conditions measured during the audit, what should this measure save. It is a forward projection built on a snapshot, correct for the inputs available at that moment. Savings themselves can never be directly metered, because a saving is the absence of consumption that would otherwise have occurred, inferred only by comparing actual post-implementation consumption against what the baseline would have predicted under the same conditions. That comparison is exactly what most plants never perform. The audit's number gets treated as a permanent fact, cited in budgets and management reports years later, when it was only ever a projection tied to the specific operating conditions present during the baseline measurement, conditions that routinely shift as flow, influent load, and operating hours change over a plant's life.

## Why the gap between projected and realized savings stays invisible

Industry data on performance-contracted efficiency projects consistently shows actual savings falling short of the original estimate more often than not, with a meaningful share of projects realizing substantially less than projected and some realizing close to nothing, even though the original engineering calculations were performed correctly. The causes are rarely a flawed calculation. They are more often a baseline or operating assumption that no longer holds: the equipment running fewer or more hours than assumed, a different load profile than the one measured during the audit, or a shift in process conditions between the baseline period and ongoing operation that nobody expected and nobody checked for. None of this shows up as an obvious error anywhere, because the audit's math was sound for the conditions it measured. The gap only becomes visible if someone deliberately compares actual post-implementation energy use against what the baseline-adjusted model predicts, a structured discipline formalized internationally as [measurement and verification](https://en.wikipedia.org/wiki/International_performance_measurement_and_verification_protocol), and one that most plants stop practicing the day the retrofit is commissioned.

This is the same shape of mistake we described in [the piece on equipment depreciation versus remaining useful life](https://insights.spans.co.in/depreciation-vs-remaining-useful-life-wastewater-equipment): a correctly computed figure answers a narrow, specific question and then gets treated as though it answers a different, ongoing one it was never built to track. There, a depreciation schedule correctly allocated cost over an accounting period while getting read as a statement about physical condition. Here, an audit correctly calculated projected savings against a baseline snapshot while getting read as a permanent, self-verifying statement about what the plant is actually saving today. It is also a close relative of [the piece on dissolved oxygen setpoint control](https://insights.spans.co.in/do-setpoint-oxygen-transfer-efficiency-wastewater): both involve an energy-relevant trend that looks stable and unremarkable on the metric everyone is actually watching, while the number that matters, realized savings in one case, oxygen transfer efficiency in the other, drifts quietly in the background because nothing in the routine was built to track it.

Picture a plant that commissioned an energy audit showing a clear payback on a VFD retrofit for its main aeration blowers, calculated against the flow and duty cycle measured during a representative baseline week. The retrofit gets implemented, the capital cost gets booked against the projected payback, and the project is considered closed. Two years later, the plant's influent flow has grown meaningfully beyond what the baseline captured, changing the blowers' actual duty cycle in ways the original savings calculation never modeled. Nobody re-measures actual energy consumption against an updated baseline to check whether the original percentage savings still holds under current conditions, because nothing in the plant's reporting calls for it: the audit's number, calculated once, continues to appear in budget documents as though it were still being verified rather than having been calculated a single time under conditions that no longer exist.

This is not an argument against commissioning energy audits, which remain one of the few disciplined ways a plant identifies real efficiency opportunities in the first place, nor an argument that every audit's number is wrong. Most are not. The point is narrower: a correct calculation, performed once, is not the same claim as an ongoing verified fact, and a plant's budgeting and reporting practices rarely distinguish between the two once the project closes out. A quick specific-energy check against a [calculator](https://spans.co.in/tools/etp-energy-calculator/) using current flow and consumption figures, compared back against the audit's original baseline assumptions, is often enough to flag whether the gap between projected and actual has grown large enough to warrant a closer look.

## What actually confirming realized savings requires

The fix is not distrusting the audit's original calculation, which was almost certainly correct for what it measured. It is treating the audit's savings figure as a baseline-dependent projection rather than a permanent fact, and periodically comparing actual post-implementation energy consumption against what that baseline, adjusted for current operating conditions, predicts. This matters most for exactly the measures where the underlying load varies the most, aeration and pumping being the two clearest examples at most plants, since a baseline captured during one representative week is the piece of the original calculation most likely to have drifted by the time anyone looks again. A structured M&V approach does not need to be elaborate to be useful: even a simple annual comparison of actual specific energy consumption (energy per unit of flow or load treated) against the audit's baseline-adjusted projection catches a savings shortfall while there is still time to investigate why, rather than years later when the original project's numbers have long since stopped being questioned.

If your plant is still citing an energy audit's original payback figure without ever having gone back to check whether current operating conditions still support it, that gap is worth closing with [Spans' project engineering team](https://spans.co.in/contact/) before a budget built on a number nobody re-verified turns into a shortfall nobody can explain.


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---