Commitment Coverage
What is Commitment Coverage?
Commitment coverage is the percentage of eligible cloud usage or spending that is covered by commitment discounts, such as reserved instances, savings plans or committed use discounts, rather than billed at on-demand rates.
Updated November 2026 · 5 min read
Commitment coverage shows how much of an organization's eligible cloud usage benefits from commitment discounts. If an organization spends the equivalent of $1 million a month on eligible compute at on-demand prices, and $700,000 of that usage is covered by reserved instances or savings plans, its coverage is 70%. The remaining 30% is billed at on-demand rates. Coverage is one of the most widely used rate optimization metrics in FinOps, alongside commitment utilization and effective savings rate.
Coverage indicates how much savings opportunity remains. Low coverage on steady workloads usually means the organization is paying more than necessary. Very high coverage, however, can mean commitments are being used to cover usage that may not last, increasing the risk of paying for unused commitments. For IT financial management, commitment coverage helps the FinOps team and finance decide how much more to commit and track progress toward rate optimization goals.
Definition of Commitment Coverage
Commitment coverage is calculated by dividing the amount of eligible usage covered by commitments by the total eligible usage, typically measured in on-demand equivalent cost over a period such as an hour, day or month. It can also be measured in usage units, such as instance hours.
Eligible usage means usage that could be covered by the commitment types in use, such as compute instances, databases or containers. Services that no commitment covers are usually excluded.
Calculating Coverage
The basic formula is covered usage divided by total eligible usage. For example, if eligible compute usage would cost $500,000 at on-demand prices and $375,000 of it is covered by savings plans and reserved instances, coverage is 75%.
Coverage can be measured by cost or by usage hours. Cost-based coverage is more common, since it reflects financial impact and works across different instance types.
Coverage can be reported at the organization level and broken down by service, region, account or team to show where gaps remain. Team-level coverage is especially useful when commitment benefits are allocated back to teams, since it shows which teams are paying closer to on-demand rates.
Coverage vs Utilization
Coverage measures how much eligible usage is covered by commitments. Commitment utilization measures how much of the purchased commitments is actually used.
The two must be considered together. High coverage with low utilization suggests the organization has committed to more than it uses. High utilization with low coverage suggests room to commit more safely.
The effective savings rate combines both effects, showing the overall discount achieved compared with on-demand pricing.
Importance of Commitment Coverage in IT Financial Management
For most organizations, raising commitment coverage on steady workloads is one of the largest and fastest ways to reduce cloud costs. Coverage shows how much of that opportunity has been captured.
It also provides a clear target for the central FinOps team. Unlike many FinOps measures, coverage is largely under the central team's control, since it depends mainly on purchasing decisions rather than on changes engineering teams must make.
Because coverage is easy to explain, it is a useful measure for reporting progress to finance and leadership. A single number, such as 75% of eligible compute covered, is easy to track from month to month and to compare with a target.
Identifying Savings Opportunity
Uncovered eligible usage is billed at on-demand rates, which are the highest available. Coverage reports show how much spending is uncovered and where, helping the FinOps team decide what to buy next.
Breaking coverage down by service and region reveals gaps, such as databases or newer regions that have not been included in commitment purchases.
Tracking coverage over time shows whether purchases are keeping pace with growth, or whether new usage is being added at on-demand rates.
Setting the Right Target
There is no universal ideal coverage level. Organizations with stable, predictable usage can safely target high coverage, while those with rapidly changing or uncertain usage should leave more room on demand.
Workloads running on spot instances or scheduled to run only part of the day are usually excluded from coverage targets, since commitments are not the right tool for them.
Targets should be set with engineering and finance input, reflecting planned changes such as migrations, modernization and optimization work.
How to Improve Commitment Coverage
Improving coverage involves analyzing usage, purchasing commitments in stages and monitoring the results alongside utilization.
Increases in coverage should be made carefully, since commitments last for one or three years. A mistake made in a single large purchase cannot easily be undone, while small, regular purchases allow the team to correct course as it learns.
Analyzing and Purchasing
Review eligible usage over several months to identify the steady baseline that runs most of the time. Commit to cover that baseline first.
Use provider recommendations as a starting point, adjusting them for known changes. Prefer flexible commitment types, such as Compute Savings Plans, where usage may shift between instance types or regions.
Purchase in regular increments, such as monthly or quarterly, rather than in one large purchase, so coverage rises steadily without overshooting.
Monitoring and Reporting
Track coverage weekly or monthly, alongside utilization and effective savings rate. Investigate drops in coverage, which often indicate new workloads or expiring commitments.
Report coverage by team and service, so that teams can see how much of their usage benefits from discounts. Teams with low coverage may have new or changing workloads worth discussing before the next purchase.
Set reminders before commitments expire, since coverage falls immediately when they lapse, returning usage to on-demand rates.
Examples of Commitment Coverage in IT Financial Management
The examples below show commitment coverage used to guide decisions.
Both use illustrative figures. The first raises coverage, and the second lowers a target that had been set too high.
In each, coverage was considered together with utilization. That combination kept savings real.
Raising Coverage Safely
A company's eligible compute spending is $800,000 a month at on-demand prices, and only 35% is covered. Analysis shows that about $600,000 is steady baseline usage.
Over six months, the FinOps team buys savings plans in monthly increments, raising coverage to 72% while utilization stays above 98%. At an average discount of about 30%, monthly compute costs fall by about $90,000 as more usage moves to discounted rates. The team sets a target of 75% and reviews it each quarter as usage changes.
Coverage That Was Too High
Another company reports 95% coverage, but utilization has fallen to 82% after engineers optimized several large workloads, reducing usage.
The FinOps team pauses new purchases, lets some commitments expire without renewal and adjusts its target to 80% coverage, accepting a little more on-demand spending in exchange for less unused commitment. Over the next two quarters, utilization recovers to 96%, and the effective savings rate improves because less money is spent on commitments that go unused.
Conclusion
Commitment coverage is the percentage of eligible cloud usage covered by commitment discounts rather than billed at on-demand rates. It shows how much rate optimization opportunity has been captured and where gaps remain.
In IT financial management, coverage guides commitment purchases and tracks the progress of rate optimization. Covering the steady baseline first, buying in increments, setting targets that reflect usage stability and monitoring coverage together with utilization help organizations maximize savings without over-committing.
Related terms
Savings Plans
Savings plans are a cloud pricing option in which customers commit to a fixed hourly spend on compute for one or three years, receiving discounted rates on eligible usage up to that amount.
Reserved Instances
Reserved instances are a cloud pricing option in which customers commit to using a specific type of compute capacity for one or three years in exchange for a significant discount compared with on-demand rates.
Commitment Utilization
Commitment utilization is the percentage of purchased cloud commitments, such as reserved instances, savings plans or committed use discounts, that is actually used by eligible usage during a period.
Effective Savings Rate
Effective savings rate (ESR) is the percentage saved on eligible cloud usage compared with what it would have cost at on-demand rates, combining the effects of commitment coverage, discount depth and unused commitments.