Cloud cost allocation stalls on shared services: the network, logging, and identity that nobody owns and everybody uses. Deciding the split rule in advance is what makes showback credible rather than a monthly argument.
Show unattributed spend prominently. Do not quietly spread untagged cost across teams. Showing it as its own line creates the pressure that gets resources tagged.
Pick one shared-cost rule and keep it. By headcount, by direct spend proportion, or evenly. Every method is arguable; changing it monthly is what destroys trust in the numbers.
Explain variance rather than report it. A 30% increase needs a cause: a new workload, a pricing change, a forgotten test cluster. The explanation column turns a bill into a management report.
Here's a preview. Unlock the free download to get all 3 sections (2 more below).
| Team | Application | Environment | This month | Last month | Variance | Variance reason | Budget | Over / under |
|---|---|---|---|---|---|---|---|---|
| Platform | CRM | prod | £4,210 | £4,180 | +1% | Normal | £4,500 | Under |
| Engineering | Build pipeline | dev | £2,890 | £1,640 | +76% | Test cluster left running after 18 Oct | £1,800 | Over |
More free templates IT teams use alongside this one.
Untagged cloud resources make cost attribution guesswork and orphaned resources invisible. Tagging only works if it is enforced at creation. Retrofitting tags across thousands of resources is a project nobody finishes.
Cost optimisation reports identify savings that are never realised, because nobody owns the change and nobody verifies it landed. This tracker follows each opportunity to a confirmed reduction on the bill.
An IT budget presented as a list of line items invites line-by-line cuts. Split into run, grow, and transform, it becomes a conversation about what the business is choosing to fund, which is a far better conversation to be in.
Choose one defensible basis (proportional to direct spend, by headcount, or by a usage metric such as log volume) and apply it consistently. The method matters less than its stability; changing it is what makes teams distrust the numbers.
Showback reports what each team consumed without moving money. Chargeback actually transfers the cost to their budget. Showback is the sensible starting point, because the data quality has to be trusted before anyone will accept a real charge.
Because spreading untagged cost silently across teams removes any incentive to tag resources. Shown as its own line, it creates visible pressure and is usually the fastest route to tagging compliance.
