FinOps reporting
A report survives
being argued with
The test of a cost report is not whether it looks finished. It is whether the number holds up when the engineer who owns the resource disagrees with it — which is why every figure names its object, its evidence and its assumption.
The short answer
What gets reported
Every engagement returns two artifacts: a multi-tab workbook with one tab per finding domain, and a three-page executive summary. Both are stamped with the check-set version they were produced under.
Numbers reconcile across them by construction — the summary quotes the workbook’s roll-up rather than a separately calculated figure, because two documents disagreeing by a few per cent is how a report loses a room.
Two artifacts
Aimed at two different rooms
The workbook
One tab per domain. Check ID, named object, owner tag, evidence, recommended action, the risk of taking it, and the annualized value both theoretical and realization-adjusted.
The executive summary
Three pages: the number and where it sits, how the estate breaks down and what was measured, and the practice gaps that let the spend accumulate unattributed.
The comparison
What was fixed, what came back, what is new because your estate changed, and what is new because the platform changed. Those are different problems with different owners.
Ask for the sample pack
Judge the depth of the reporting before granting any access.