Metric
Effective Coverage %: the FinOps number that combines coverage and utilization.
Most cost dashboards report commitment utilization. That tells you whether you used what you bought — not whether you bought enough. Effective Coverage % is the single number that captures both.
Definition
One number, two halves
Your AWS commitment portfolio has two failure modes. You can under-commit (most of your spend stays on-demand) or under-utilize (you bought commitments you don't consume). Either one leaks money. Effective Coverage % is coverage × utilization — a single percentage that catches both.
Effective Coverage % = Coverage × UtilizationCoverage
$ eligible compute on commitments / $ eligible compute totalWhat fraction of your eligible compute spend was on a Reserved Instance or Savings Plan rather than on-demand. If your AWS compute is $100K and $30K of it ran on commitments, your coverage is 30%.
Utilization
$ commitment used / $ commitment purchasedOf the commitments you bought, how much did you actually consume. If you bought $30K of commitments and used $26K worth, utilization is ~87% — the other $4K is wasted commitment. Dollar-weighted across your portfolio.
Worked example
Why two organizations with the same utilization can have very different Effective Coverage %
| Org | Coverage | Utilization | Effective Coverage % | What it means |
|---|---|---|---|---|
| Org A | 95% | 70% | 66.5% | Over-committed but well-targeted. Most spend is on commitments, but a third of those commitments go unused. Best move: shorten commitment terms or shift to Savings Plans. |
| Org B | 40% | 95% | 38% | Disciplined utilization but under-committed. Almost everything they bought, they used — but 60% of compute is still on-demand. Best move: buy more. |
| Org C | 75% | 90% | 67.5% | Healthy on both axes. Slight room to improve utilization by tuning commitment portfolio toward more stable workloads. |
Note that Org A and Org C end up at roughly the same Effective Coverage % despite very different starting points. The metric tells you the level you're operating at; the breakdown tells you where to act.
Why one number
A single KPI finance can hold the engineering org to
Two numbers force the audience to do arithmetic in their head. Coverage and utilization both feel like high-percentage targets — "we're at 80% utilization" sounds good in isolation. Multiplying them together collapses the ambiguity. CFOs ask "how's our FinOps function doing?" and get one answer. Engineering platform leads track one trendline through the quarter. When the number moves, the breakdown tells you which half moved.
- Below 30%No active FinOps program. Most compute is on-demand at retail rates.
- 30–55%Commitment management is in flight but immature. Common at orgs in their first year of FinOps.
- 55–75%Active FinOps function with regular review cadence. Industry median for orgs with a dedicated FinOps role.
- 75%+Mature program. Likely using a tool to manage SP/RI laddering continuously.
Targets are rough heuristics; the right number depends on your workload mix. Steady-state workloads can hit 90%+; bursty workloads should aim lower so utilization stays healthy.
In CloudQuell
Live: computed from your CUR, weighted, broken down to the workload
- The composed Effective Coverage % KPI is live on the Commitments view — the top-line number above its coverage and utilization breakdown.
- Computed from your CUR: coverage on an on-demand-equivalent basis, utilization dollar-weighted across your commitment portfolio (Methodology v1.0).
- Weighted by dollars, not commitment count. One large under-utilized commitment moves the needle more than ten small ones.
- Underutilized commitments carry right-sizing guidance, and each commitment recommendation shows its projected impact on the number ("18% → 24%").
- Tracked over time as a 12-month trend chart, aggregated org-wide and broken down per integration so multi-account orgs can see which sub-account is dragging the average.
Connect a read-only IAM role for daily cost telemetry, commitment utilization, tag coverage — and Effective Coverage %, live on the Commitments view.