Inference Public

Working resource

Cloud cost and ownership worksheet

A blank worksheet for understanding what a set of AWS accounts or services costs, who owns each cost, and which changes are worth making.

Free to use and adapt · No registration · Use alongside your billing data

How to use it

Fill it in with a finance contact and an engineer who knows the service. Work on one agreed scope and period at a time. Keep three things separate throughout: the estimated opportunity of a change, the change actually implemented, and the observed financial effect.

A fall in cost caused by lower demand is not an efficiency gain, and a saving that weakens resilience may not be worth having. Record demand and service level alongside cost.

1. Scope

What this worksheet covers
ItemAnswer
Accounts or services in scope
Billing period
Exclusions (and why)
Discounts and commitments in place
Finance contact
Engineering contact

2. Baseline

Cost by service or team
Service or teamOwnerMonthly costHow it was allocatedConfidence

3. Shared costs

Networking, logging, security tooling, support and shared data services are often paid centrally.

Shared cost allocation
Shared costCurrent treatmentProposed allocation ruleAgreed by

4. Unallocated spend

Costs without an owner
CostAmountWhy it is unallocatedNext step

5. Forecast assumptions

Assumptions behind the forecast
AssumptionValueSourceOwnerReview date

6. Change backlog

Candidate changes
ChangeEstimated opportunityEffortRisk and dependenciesHow the effect will be verified

7. Verification record

Fill this in after a change has been implemented and has run for its verification period.

What actually happened
ChangeImplemented onObserved effectOver what periodDemand or service changes in the same period

Cost and ownership

Can you explain what the service costs to run?

A scoped review produces a reproducible baseline and a change backlog you can verify.

Discuss an AWS cost review