How a saving is proven

A saving is called verified only when CloudJaeger opened the change as a pull request, a person merged it, and the bill measured the changed resource before and after.

Until then a saving is an estimate: the Action Center counts it as identified, accepted or self-reported, never as verified.

A change your team marks done without a pull request is self-reported: it is counted at its estimate and never as verified or realized.

Rejecting a recommendation needs a reason, and an approval keeps the name of the person who gave it.

Coming: savings verified on real customer bills — the pull requests that feed the measurement are not switched on in production yet.

Coming: a check that the resource really changed in your cloud before a merged pull request is credited.

Coming: savings verified on Azure and Google Cloud — their billing data does not yet name each resource, so a change there cannot be measured on its own.

The bill is read for the 30 days before the merge and the 30 days after it, and both windows must be fully covered by settled bill before any figure is stated.

The newest 2 days of bill are left out, because providers still restate them.

A dollar is claimed only when the bill names the changed resource and no other merged change touched it in the same window.

When the bill only shows a whole service, the movement is reported but no dollar is claimed.

One resource's bill is read once, even when a payer account and the member account both hold a copy of it.

A window billed in a currency other than US dollars is not measured.

Coming: the same refusal for a bill that was converted to US dollars when it was uploaded.

A movement inside the noise floor, the larger of $1 a month and 2% of the baseline, is reported as no measurable change.

A saving is measured on the resource's usage priced on demand, not on usage a reservation, savings plan or committed-use discount covered.

The commitment is still paid after the change, so the part of the drop it covered is never claimed.

A resource that ran entirely under a commitment shows no measured saving, not a saving of $0.

Negotiated percentage discounts, such as an enterprise discount, move with usage and are included.

Coming: credit for a freed commitment that goes on to cover other usage.

A credit, refund or tax line on the resource is never counted as a saving.

A figure someone typed in, such as a commitment saving entered by hand, is shown but never added to the verified total.

A change that made the bill go up is shown as regressed and is never netted against savings.

When several merged changes touch one resource in the same window, none of them claims the dollar, so one movement is never counted twice.