A FinOps RACI is filled in by the cloud owner with the heads of engineering, finance and management, at the latest when the first saving is left lying because nobody was in charge, and after that at every change of the organisation; for each recurring activity it records who does it, who answers for the result, who is asked beforehand and who is told afterwards. The decision it records: exactly one accountable role per row. What a RACI is and which roles FinOps knows is on roles and responsibilities; this page is the matrix itself.
The template
Cloud cost ownership RACI <organisation>, version <1.0>, effective <date>, owner <cloud owner>
R does the work, A answers for the result and is exactly one role per row, C is asked beforehand, I is told afterwards.
| Activity | Cadence | Engineering team | Team lead | Cloud owner | Finance | Management | Procurement |
|---|---|---|---|---|---|---|---|
| Maintain the tagging policy and value list | quarterly | I | C | A, R | C | I | |
| Tag resources at creation | ongoing | R | A | C | |||
| Report tag coverage | monthly | I | A, R | I | |||
| Run billing exports and data access | ongoing | A, R | C | ||||
| Draw up the annual budget per team | yearly | C | R | C | R | A | |
| Update the monthly forecast | monthly | C | A, R | C | I | ||
| Answer a budget alert | on alert | R | A | I | I | ||
| Prepare and lead the monthly cost review | monthly | C | A, R | C | I | ||
| Produce the showback statement per team | monthly | I | I | A, R | C | ||
| Post the chargeback | monthly | I | C | A, R | |||
| Review recommendations and accept or reject | monthly | R | A | C | |||
| Implement a saving | after acceptance | R | A | I | I | ||
| Verify a saving in the invoice | following month | I | A, R | C | |||
| Determine commitment demand | quarterly | C | A, R | C | |||
| Approve a commitment purchase | per purchase | I | R | C | A from <amount> | C | |
| Monitor commitment utilisation | monthly | A, R | I | ||||
| Triage and resolve a cost anomaly | on alert | R | C | A | I | I from <amount> | |
| Close and review a cost incident | per incident | C | C | A, R | I | ||
| Create a new account or project with cost controls | per account | C | A, R | C | |||
| Cost part of the architecture review | per review | R | A | C | |||
| Negotiate contracts, private pricing and renewals | per contract | C | C | A | R | ||
| Grant and review access to cost data | quarterly | A, R | C | ||||
| Set budget alert thresholds per account | yearly | C | A, R | C | |||
| Watch free tier expiry, credits and refunds | monthly | A, R | I | ||||
| Check marketplace subscriptions and licence fees | quarterly | C | C | A, R | I | R | |
| Explain the variance against budget per cost centre | monthly | R | C | A | I | ||
<further activity> | <cadence> | <R, A, C, I> |
Escalation
| Case | First level | Second level | Deadline |
|---|---|---|---|
| Two roles claim a row's A | <cloud owner> | <management> | <5> working days |
An action is <30> days overdue | <team lead> | <cloud owner> | next review |
| A dispute against the chargeback stays open | <finance> | <management> | before posting |
Roles and people
| Role | Person | Deputy | Reached through | Since |
|---|---|---|---|---|
| Cloud owner | <name> | <name> | <channel> | <date> |
Team lead <team> | <name> | <name> | <channel> | <date> |
| Finance | <name> | <name> | <channel> | <date> |
| Management | <name, such as CTO or CFO> | <name> | <channel> | <date> |
| Procurement | <name> | <name> | <channel> | <date> |
Thresholds. Management is A for commitment purchases from <amount> of term value and is informed of anomalies from <amount> per day; below that the cloud owner decides.
| Version | Date | Change | Approved by |
|---|---|---|---|
<1.0> | <date> | first version | <management> |
How to fill it in
Columns: the six roles are functions, not people; one person can hold several columns, and the "roles and people" table resolves each column to a person, with a deputy. Who holds which role in an organisation is shown on cost ownership and accountability.
Rows: every row is an activity that a document of this chapter describes, on the same cadence as there. The review follows the monthly review checklist, the purchase the commitment purchase decision record, the anomaly the cost anomaly runbook. A row without a document gets one before it gets an A.
A: exactly one role per row, even where two roles are equally involved; the second becomes C. A row with two As has no owner, a row without one finds nobody at the first dispute. R: may appear more than once. C and I: sparingly; whoever is I in every row stops reading.
Thresholds: amounts, not percentages, so the row applies without recomputation; a commitment's term value is the monthly rate times the months.
How to adapt it
One team: team lead and cloud owner are often one person; the columns then merge, and the A for budget and chargeback stays with finance or the managing director so the team does not police itself. Several teams: the rows "tag", "recommendations" and "implement a saving" get one A per team; the matrix lists the team leads one by one.
One provider: no change to the rows; the cloud owner is usually also the account's administrator. Three providers: the rows "run exports" and "commitment demand" may have a different R per provider, the A stays one.
Startup: the founder or CTO holds management and finance; the matrix is then a dozen rows with two columns, and its value lies in the thresholds. Finance-led: finance is A for budget, forecast and chargeback and C in every row with amounts; the cloud owner stays A for data, coverage and verification. The personas the FinOps standard describes are mapped to the roles here on FinOps personas.
Sources
Read on 2026-10-21. FinOps Foundation, Personas and FinOps Practice Operations (CC BY 4.0), AWS Well-Architected, COST01-BP04 cost awareness in organisational processes, managing access to the AWS Billing console, assign access to Cost Management data in Azure, Cloud Billing access control, Google Cloud, foster a culture of cost awareness.