Cost Allocation Tags: The Discipline That Holds

Cost allocation tags only work if 95%+ of resources are tagged. Discipline below that and the data is misleading.

Why tags matter

Untagged spend cannot be assigned to teams. The bill is a mystery; nobody is accountable.

One missing tag breaks the chargeback model.

Four-tag minimum

• 1. team (owning team name).
• 2. service (the application).
• 3. environment (prod/staging/dev).
• 4. cost-center (financial bucket).

Enforcement

Block resource creation without required tags. SCPs (AWS), Organization Policies (GCP), Azure Policies.

Existing resources: monthly tagging report; teams must tag or lose the resource.

Quarterly cleanup

Quarterly: report untagged resources by team. Streak counter shaming.

The discipline is sustained only with quarterly visibility.

Antipatterns

• Tag enforcement only at creation. Existing resources never tagged.
• Tags optional. 30% untagged within a year.
• Tag taxonomy that changes. Historical data unusable.

What to do this week

Three moves. (1) Apply this lever to your highest-spend workload. (2) Measure the dollar impact for one month. (3) Roll the practice out to the next two services if the savings hold.