What is a good tag coverage?

There's no standard target. Aim for the point where the untagged remainder is too small to change any team's numbers, and give that remainder an owner.

Why can tag coverage go above 100%?

Because credits and refunds were included: untagged negative lines shrink total cost below tagged cost. Measure positive charges only.

Is tag coverage the same as tag compliance?

Not quite. Coverage asks whether cost carries a tag; compliance also asks whether the value is valid against your standard, such as an approved team name. Cost can be covered and still non-compliant.

Allocation & accountability

Tag coverage

Tag coverage is the share of cloud cost that carries a given tag, such as team, over a period: tagged cost ÷ total cost. The rest is untagged cost that nobody can allocate, so tag coverage shows how much of the bill your allocation actually reaches.

In plain English

Think of a library's catalogue. Coverage is the share of books with a label on the spine. The unlabelled ones are still on the shelves, but nobody can find them or say whose they are.

Formula and worked example

Tag coverage = tagged cost ÷ total cost

Total cost: = all charges in the period, excluding credits and refunds
Tagged cost: = the part of total cost on resources that carry the tag key

Worked example. Northwind Labs in March, for the team tag (the cost allocation example).
Total cost, excluding credits and refunds	$115,000
Cost with a team tag	$110,000
Cost with no team tag	$5,000
Tag coverage for team	95.7%

Coverage is per key: the same month could be 95.7% for team and 60% for cost-center. Track the keys your allocation depends on, and look at which services hold the untagged $5,000.

Why tag coverage matters

Every allocation report has a hidden footnote: the cost it could not assign. Tag coverage puts a number on that footnote, so you can see whether showback and chargeback cover the whole bill or only most of it.

It is also one of the easiest FinOps numbers to improve week by week. Breaking untagged cost down by account, service and resource shows exactly where to start.

Common mistakes

Counting resources instead of cost. 95% of resources tagged can still leave a large share of spend untagged if the untagged 5% are the expensive ones. Measure coverage by cost.
Including credits and refunds. Negative lines can push coverage above 100% or hide untagged spend. Measure positive charges only.
Averaging across tag keys. One coverage number for all tags hides the key that matters. Track coverage for each key your allocation uses.
Chasing cost that cannot be tagged. Some charges, such as support and taxes, aren't tied to a taggable resource. Allocate them by rule and report them separately, rather than letting them drag coverage down for ever.

Where to find it in AWS, Azure and Google Cloud

Where to find Tag coverage by cloud provider
Cloud	What it is called	Where to find it
AWS	Untagged cost	Cost Explorer grouped by a tag key shows untagged cost as its own group. The AWS Config required-tags rule and tag policies in AWS Organizations help keep coverage up.
Azure	Untagged cost	Cost analysis grouped by a tag shows untagged cost separately. Azure Policy can require tags on new resources, and Cost Management tag inheritance fills gaps from resource groups and subscriptions.
Google Cloud	Unlabelled or untagged cost	Query the billing export to BigQuery for rows without the label or tag you allocate by, grouped by project and service.

How CloudYali helps

CloudYali Tag Governance shows tagged and untagged spend, coverage and its daily trend for each tag key across AWS, Azure, Google Cloud and Databricks, counting positive charges only, so credits and refunds cannot inflate the number.

See the feature Read how it works in the docs

Allocation & accountability
Cost allocation tags
Cost allocation tags are key-value labels, such as team=checkout, attached to cloud resources so their cost can be grouped by owner, product or environment. On AWS a tag key only reaches billing data after it is activated for cost allocation, and tag keys and values are case-sensitive.
Allocation & accountability
Cost allocation
Cost allocation is assigning every part of the cloud bill to the team, product or customer responsible for it, using accounts, tags and agreed rules for shared costs. It turns one invoice into numbers each owner can act on, and it is the basis for showback, chargeback and unit economics.
Allocation & accountability
Showback
Showback is reporting each team's allocated cloud cost back to that team, for visibility and accountability, without moving money between budgets. It shows owners what their choices cost so they can act on it, and unlike chargeback it is not entered into the company's accounts.
Allocation & accountability
Chargeback
Chargeback is billing each team or business unit for its allocated cloud cost, so the cost lands in that team's budget in the company's accounts. It uses the same allocation as showback, but money actually moves, which is why the rules for shared and unallocated cost must be agreed first.

Frequently asked questions

What is a good tag coverage?
There's no standard target. Aim for the point where the untagged remainder is too small to change any team's numbers, and give that remainder an owner.
Why can tag coverage go above 100%?
Because credits and refunds were included: untagged negative lines shrink total cost below tagged cost. Measure positive charges only.
Is tag coverage the same as tag compliance?
Not quite. Coverage asks whether cost carries a tag; compliance also asks whether the value is valid against your standard, such as an approved team name. Cost can be covered and still non-compliant.