This chapter holds ten documents a team copies rather than reads: the policies finance and engineering sign, the worksheets a budget is built on, the statements a team receives each month, and the checklists a review, a new account and an architecture decision run through. Every page carries the artifact itself, fields and all, with a short note on how to fill it and where its inputs come from; the explanation of why the document exists sits in the chapter the template belongs to, and each page links it.
What this chapter covers
The first section, Allocation and ownership, holds the documents that decide who pays for what. The tagging policy template names the mandatory keys, the allowed values, the owners and the enforcement per provider, with the exceptions and the review cadence; it is the written form of the rules in tagging policy. The showback report template is the one-page statement a team receives: owned cost, its share of shared cost, trend, drivers and open actions, each field with its source. The chargeback policy template is the internal policy finance signs before money moves between cost centres: scope, the rate basis, the keys for shared cost, timing and cut-off, disputes and exceptions. The cloud cost ownership RACI template is the matrix across engineering, finance and management for the recurring activities, with one person per role.
The second section, Planning and review, holds the documents of the monthly cycle. The monthly cloud cost review checklist is the agenda with its inputs, the checks per step, the owners, the outputs and the decisions log, on the cadence reporting cadence sets. The cloud budget template is the worksheet by team, environment and provider: drivers, price assumptions, the exchange-rate policy, commitments, growth, contingency and the review dates, the inputs annual cloud budget describes. The cost anomaly runbook template is the triage path for an anomaly: steps, owners, thresholds, communication, closure and the post-incident fields.
The third section, Decisions and controls, holds the documents a single decision produces. The commitment purchase decision record is one record per purchase: baseline usage, coverage target, term and payment, exchange rules, approver and review date, the questions choosing between commitment types answers. The cost controls for a new account or project checklist is what is switched on before the first resource: budgets and alerts, tags, exports, the free-tier watch, billing IAM, quotas and naming, per provider. The architecture review cost checklist is the question list per layer, compute, storage, network, data and AI, with the pricing-model choices, exit and portability, and the estimate's assumptions.
What this chapter is not: a second explanation of the subjects. A template page states what the document contains and how to fill it, and points to the handbook page that explains the subject; where a page here and a page there would say the same thing, the explanation stays there. The templates are provider-neutral where the subject allows it and name the three providers' mechanisms where it does not, as the tagging policy and the new-account checklist do. Every placeholder stands in angle brackets, so a copy shows what is still to be filled.
Key terms
- tagging policy: the rules for the keys and values every resource carries; the first template.
- showback and chargeback: showing a team its cost against moving the money; the report and the policy templates.
- RACI: the matrix of responsible, accountable, consulted and informed per activity; the ownership template.
- budget: the planned amount a period's cost is measured against; the worksheet template.
- budget alert: the message a threshold on actual or forecast cost sends; a field of the new-account checklist.
- anomaly: a cost movement outside the expected pattern; the runbook's trigger.
- commitment: a reservation or savings plan bought against future usage; the decision record's subject.
- cost owner: the person who answers for a cost line; a column of every template here.
- cost policy: a written rule a team agrees to follow; what the policy templates produce.
Neighbouring chapters
Before this chapter stands Savings patterns: its pages produce the lists the monthly review checklist works through and the proofs the showback statement carries, and its last section, the purchases nobody uses, is the reason the commitment decision record exists. The two chapters are a pair: one finds the saving, the other records the decision about it.
The chapters whose rules these templates write down are earlier: Allocation for the tagging policy, the showback statement and the chargeback policy (cost centres and team ownership), Governance for the RACI and the two checklists (roles and responsibilities, cost in the development lifecycle, cost in architecture and procurement reviews), Planning for the budget worksheet (budgets), Reporting for the review checklist and the runbook (anomaly detection), and Pricing and Optimisation for the decision record (commitment strategy). A template changes when its chapter's rule changes, never alone. The full list of chapters is in the handbook.