HKGpipi

VERIFICATION

A saving is verified after the change.

Expected savings are estimates. HKGpipi measures the post-change billing result and compares it with the agreed baseline before reporting a verified saving.

Decision rule

Estimate before deployment.Measure after deployment.

01 · Definitions

Three terms keep the outcome honest.

Expected saving
An estimate of the economic effect before an approved change is deployed.
30-day measurement view
The observed post-change billing result during the current 30-day measurement view.
Verified annualised saving
The measured post-change saving, normalised where required and expressed as an annualised value under the agreed verification basis.
Measurement boundary

A 30-day measurement view is a post-change measurement context. It does not mean the whole engagement finishes in 30 days, that every AWS workload requires exactly 30 days, or that the contractual methodology is universally fixed.

02 · Verification model

Reconcile the result against an agreed basis.

The baseline and treatment of relevant workload changes are agreed before outcome-based implementation begins.

Before changeBaseline spend
After changeNormalised post-change spend
Measured resultVerified saving
Verified saving may be expressed as an annualised value. The agreed basis accounts for relevant changes that would otherwise distort the comparison.

03 · Normalisation

Why post-change spend may need context.

Factors that may need to be accounted for when interpreting post-change spend include:

  • Workload-volume changes
  • Unrelated infrastructure changes
  • Pricing changes
  • Commitment effects
  • Architectural changes outside the approved remediation

04 · Measurement

Expected becomes verified through reconciliation.

Illustrative reconciliationExpected compared with verified annualised saving
Expected annualised saving£184,000
Verified annualised saving£176,420

Illustrative reconciliation: expected annualised saving £184,000; verified annualised saving £176,420; variance to expected −£7,580 (−4.1%).

  1. Deployment
  2. Day 0
  3. 30-day measurement view
  4. Verified annualised result

05 · Boundaries

What verified does not mean.

  • The pre-change estimate was exact.
  • Every AWS billing movement is attributed to one remediation.
  • Workload demand remained unchanged.
  • A saving is guaranteed before deployment.

06 · Commercial boundary

Verification is also a commercial boundary.

For outcome-based implementation, the contractual verification basis is agreed before implementation begins. The 25% fee applies to savings that meet that agreed definition.