Skip to content
FinOps workspace
COST LEDGER / OFFICIAL RELEASE

FOCUS 1.3: commitments, allocation and data freshness

Published and reviewed: 1 October 2026

Scope my cloud cost review

FOCUS 1.3 was ratified on 5 December 2025 and introduced by the FinOps Foundation on 11 December.

Illustrative server cabinets in a mint-lit room
Illustration, not customer infrastructure.
On this page
  1. What FOCUS 1.3 changed
  2. A separate dataset for commitments, with its own access rules
  3. Allocation: measured, supplied or inferred
  4. Freshness: when is a month really closed
  5. Documents to prepare
  6. Primary sources

What FOCUS 1.3 changed

The FOCUS Steering Committee ratified version 1.3 on 5 December 2025. The FinOps Foundation described it in an article dated 11 December 2025. Four changes matter to a buyer.

  • A supplemental Contract Commitment dataset separates contract terms (start and end dates, remaining units, descriptions) from cost and usage rows.
  • Allocation columns let a data generator expose how it split the cost of shared resources such as Kubernetes pods or database instances.
  • Recency and completeness metadata: providers timestamp a dataset and flag whether its data is final or subject to revision.
  • Service Provider Name and Host Provider Name distinguish who sells a service from who hosts the underlying resource, which also clarifies reseller relationships.

The Foundation also marked the Provider and Publisher columns as deprecated, to be removed from the specification starting with version 1.4.

A separate dataset for commitments, with its own access rules

The Foundation notes that the Contract Commitment dataset is kept apart on purpose, so that permissions can be set for it separately given the likely sensitivity of its contents. That is a useful model for a purchase: cost and usage rows can be shared with analysts, while commitment terms stay with finance and procurement.

When a provider offers commitment reporting, ask which keys join the commitment records to consumption, and have them run one test: total cost before the join must equal total cost after it. The FOCUS implementation checklist gives the acceptance wording for this test.

Allocation: measured, supplied or inferred

The new allocation columns show the method a data generator used, beside the result. For a product team that receives a showback figure for a shared cluster, three cases should be distinguished: the split was supplied by the generator, it was calculated by your reporting tool, or it is an assumption someone typed into a rule. Ask which case applies to each shared cost line, how idle capacity is treated, and who approved the method.

The specification describes what a generator can expose. Whether your accounts receive those columns is a separate fact to check on a sample export. See the showback versus chargeback guide for how a split becomes a charge to a team.

CaseWhere the method livesWhat to ask
Supplied by the data generatorThe allocation columns of the exportWhich method it used, and whether idle capacity is included
Calculated by your reporting toolThe tool's allocation ruleWho approved the rule
Assumption typed into a ruleA spreadsheet or a tool settingWho owns it, and when it was last reviewed

Freshness: when is a month really closed

With recency metadata, a pipeline can tell a final delivery from one that may still be revised. The Foundation's own problem statement is that practitioners might only discover missing rows well after month-end close. Ask a provider how it marks an incomplete period in dashboards, how a corrected delivery replaces the earlier one, and what a finance user sees while a period is still open.

Documents to prepare

  • One sample export per provider with its declared FOCUS version, column list and delivery timestamp.
  • The list of commitments you hold (savings plans, reservations, committed use discounts) with end dates, from the provider consoles.
  • A statement of which team may see commitment terms.
  • The current allocation rules for shared clusters and databases, with their owner.

The Foundation's article also describes a conformance program for data generators planned for 2026. Until a provider shows results for your accounts, treat support for 1.3 as a claim to be tested on real data.

Primary sources

The FinOps Foundation article introducing FOCUS 1.3, read in full for this page:

Continue your review

Request a quote for my project

Describe your project in a few lines and receive a quote from a specialist.

Request my quote
Get my FinOps quote