FinOps Framework 2025: define technology spending scopes
Published and reviewed: 1 October 2026
Scope my cloud cost reviewThe FinOps Framework 2025 update was published on 20 March 2025.

On this page
What the March 2025 update changed
The FinOps Foundation published Framework 2025 on 20 March 2025. Its main change is the addition of Scopes as a core element. The Foundation defines a FinOps Scope as a segment of technology-related spending to which practitioners apply FinOps concepts. The initial scopes named are Public Cloud, SaaS and Data Center, with Public Cloud staying the primary one. The Technical Advisory Council had approved the idea of Scopes in October 2024, and the March 2025 revision clarified the definition.
The wording changes follow from that. The definition of FinOps gains the words « and technology ». Four principles are reworded, the first change since the principles were written in 2019. Two domains lose the word « Cloud » from their names, and the capability « Cloud Policy & Governance » becomes « Policy & Governance ». The Foundation describes the framework as flexible and non-prescriptive, so nothing in the update obliges a company to widen what it manages.
A scope is a decision context, not a data source
The Foundation insists that a scope is not simply a type of infrastructure or a data feed. A scope can switch some capabilities on or off, include or exclude a persona, and change the thresholds attached to a metric, depending on business strategy. Practitioners may define their own, and the article mentions Private Cloud, Licensing and AI as scopes that practitioners had begun to define.
It supports this with the State of FinOps 2025 survey: optimization was the top priority for cloud, but it was not among the top five priorities for SaaS, AI, licensing or data centers. For a buyer, the consequence is direct.
Writing a scope matrix into the statement of work
Before signing, ask for a one-page matrix, with one row per scope in the engagement:
- the spending category and the source systems that hold its data (billing exports, SaaS admin consoles, contract repositories);
- the internal owner who can approve a change;
- the business question that started the scope, for example a margin target or a renewal date;
- whether the provider analyzes, implements, or operates a recurring process for this scope;
- explicit exclusions, such as license compliance opinions or statutory accounting.
A first purchase is easier to verify when it covers a scope whose data you already hold and whose owner can decide. Additional scopes can sit in a roadmap with their own acceptance criteria. The comparison of consulting and managed FinOps helps decide whether a scope needs a one-off review or a recurring service.
Documents to prepare
- A one-sentence definition of each scope you want examined, written by the person who asked the business question.
- The list of owners per scope, with the approver for production changes.
- Access arrangements for each data source. The read-only audit access guide covers least privilege and data boundaries.
- A baseline period and the currency in which finance reports it.
The Foundation's article also notes that the framework does not cap the scopes a company may create, and that a company with a hub-and-spoke practice can have different spokes handling different scopes. If your own organization works that way, name the spoke that owns each scope in the contract, so the provider knows whom to report to.
Primary sources
The FinOps Foundation article on Framework 2025, read in full for this page:
Continue your review
Get a quote for my cloud costs
A specialist in cloud cost control reads your request and proposes a quote.
Get my quote