Google Cloud coverage is
in development

The bill of record. the BigQuery billing export, read with a role that carries no write permission is the only acceptable basis for a figure. Every rate a finding is priced at comes from there; where one is genuinely absent, the provider’s published price list is fetched at audit time, cited and labelled as list price rather than quietly assumed.

Commitments. Committed use discounts come in resource-based and spend-based forms that cover different things, and a commitment fee is not the same unit as the spend it offsets — conflating the two is the most common way a CUD figure ends up overstated. Coverage is measured per service against coverable spend.

The provider’s own recommendations. Active Assist recommenders are read as a cross-check and grounded against current inventory. An idle-address or idle-disk recommendation for something already deleted is shown and not counted.

What is deliberately out of scope. Nothing is written to your project at any point — no dataset created, no export configured, no labels applied. Where a capability would require a write, it becomes a prerequisite you perform, not a permission we ask for.