Measuring realized versus identified savings.

Here is why the gap opens, how to measure realized savings honestly, and how to report a number that survives scrutiny.

Why do identified and realized savings drift apart?

Several mechanisms pull the realized number below the identified one, and naming them is the first step to closing the gap.

• Recommendations expire. A rightsizing recommendation from AWS Compute Optimizer, Azure Advisor, GCP Recommender, or the OCI Cost Analysis console reflects a moment in time. Wait a quarter and the workload has changed, so the modelled saving no longer applies.
• Partial implementation. A plan to move every eligible instance to Graviton or gp3, or to lift commitment coverage to a target, often ships at half the intended scope. Half the action delivers a fraction of the identified saving.
• Growth masks the cut. Usage almost always rises. A genuine reduction can coincide with a larger bill because the estate grew underneath it, which makes the saving invisible unless measured against a baseline.
• Commitments shift, not remove, cost. A Savings Plan, Reservation, Committed Use Discount, or Universal Credits purchase lowers the rate but adds a commitment liability. Counting the gross rate cut without netting the commitment is double counting.

None of these means the work was wasted. They mean the headline identified figure was never the realized figure, and reporting it as if it were is what damages trust.

How do you measure realized savings honestly?

Realized savings is a comparison against a baseline, not a raw bill movement. The defensible method has three parts. First, set a baseline: the spend that would have occurred without the action, which usually means holding unit cost at its pre action level and applying actual usage, so growth is separated from optimization. Second, attribute: tie each change in spend to a specific action, using the billing data, the Cost and Usage Report on AWS or the FOCUS aligned export on Azure, GCP, and OCI, so the saving has an owner and a cause. Third, reconcile: confirm the realized number against the actual invoice, including the net effect of any commitment purchased, so the figure ties to money that left the business.

The honest realized number is almost always smaller than the identified estimate, and that is the point. A program that reports a smaller verified number repeatedly is trusted; one that reports large unverified numbers once is not.

What belongs in a savings ledger?

The instrument that holds all of this together is a savings ledger: a running record of every optimization action with its identified estimate, its implementation status, and its verified realized result. Each row carries the action, the owner, the date, the baseline assumption, the cloud and service, the identified figure, the realized figure once it appears in the bill, and the commitment liability if any. The ledger turns savings from an anecdote into an auditable series, lets you compute a realization rate (realized divided by identified) that improves as the program matures, and gives finance one place to verify the number. It is the difference between saying we think we saved a lot and showing exactly what was done, when, and what the bill confirmed.

A worked example

How should realized savings be reported upward?

Report the realized number, against the agreed baseline, net of growth and net of commitment liability, attributed to named actions and reconciled to the bill. Show the identified figure alongside it as the pipeline, and the realization rate as the measure of execution. This framing gives a CIO and a CFO a number they can defend in their own reporting, and it reframes the conversation from how much did you claim to how reliably do you deliver. That reliability is what earns a savings program a durable mandate rather than a one off project, which is the territory of the wider FinOps operating model.

Make your savings number auditable

We help enterprises measure realized savings against defensible baselines across AWS, Azure, GCP, and OCI, and report a number finance will credit. We take zero provider commissions and answer only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on either a Fixed Fee or a no risk Gainshare basis, where our fee is tied to verified savings. Book a strategy call to scope it for your estate, and follow more in The Cloud Spend Navigator.