The trap of measuring per framework

Companies facing CSRD, BRSR Core, SB 253, and CBAM at the same time often respond by standing up parallel data-collection efforts, one per regulator. This is expensive and it produces inconsistent numbers: the purchased goods and services figure in your ESRS filing doesn't match the number a supplier-facing team quotes for BRSR Core, because two different teams built two different spreadsheets with two different assumptions about emission factors and boundaries.

The more durable approach is to measure once, at the GHG Protocol Scope 3 category level, with a documented methodology behind every number, and then treat each regulatory format as a mapping and presentation layer on top of that single dataset. The categories themselves - purchased goods and services, capital goods, upstream transport, use of sold products, and the rest of the fifteen - are the common language nearly every framework in this space either adopts directly or can be translated into.

Why category-level data is the right foundation

The GHG Protocol's Corporate Value Chain Standard already forces the discipline that regulators want: a full boundary across upstream and downstream activities, category-by-category accounting, and an explicit data quality hierarchy running from spend-based estimates up through average-data, hybrid, and supplier-specific primary data. If you build your inventory properly at this level - with the calculation method, activity data source, and emission factor set recorded for each category - you have already done the hard part that every downstream disclosure format ultimately requires: a defensible number with a traceable method.

What changes between frameworks is not the underlying activity, it's the packaging. ESRS E1 wants that data expressed through its own disclosure structure under CSRD's double materiality logic. BRSR Core wants a tighter subset of KPIs pulled from the same inventory. SB 253 in California wants a scope 3 figure with phased third-party assurance attached. None of them require you to re-measure purchased goods and services from scratch; they require you to present the same underlying number in their format, with their specific line items, definitions, and assurance expectations layered on.

Mapping, not duplicating

A practical architecture looks like this:

  1. Category-level inventory as the system of record. All fifteen Scope 3 categories, calculated with a stated data quality tier per category, refreshed on a single reporting cycle.
  2. A methodology register. For every category, document the calculation approach, activity data source, emission factor set, and any allocation logic. This register is what an assurance provider or regulator will actually interrogate, not the final published table.
  3. A mapping layer per framework. Each disclosure format gets a translation sheet showing exactly which category-level figures feed which line item, KPI, or table cell, plus any framework-specific adjustments (different consolidation boundaries, different reporting years, different rounding conventions).
  4. A single change-control process. When a supplier improves its data quality from spend-based to supplier-specific, that update flows through the category-level inventory once, and every framework mapping downstream inherits it automatically rather than requiring separate re-entry.

This is the same logic behind our Scope 3 Measurement & GHG Inventory work paired with CSRD & SEC-Ready Reporting and BRSR & BRSR Core Reporting: the inventory is built once, the outputs are formatted many times.

Where the mapping breaks down

This architecture works cleanly for frameworks that are fundamentally asking for the same thing GHG Protocol Scope 3 already measures. It works less cleanly for CBAM, which is not a corporate Scope 3 inventory exercise at all - it requires embedded-emissions calculations on specific imported products (iron and steel, aluminium, cement, fertilisers, hydrogen, electricity) using actual production-route data where available, falling back to conservative default reference values otherwise. A company's purchased goods and services category may draw on overlapping activity data, but CBAM's product-level, shipment-level calculation logic is a distinct methodology that needs its own workstream, which is why CBAM Export Readiness is treated separately from general Scope 3 inventory work.

The US SEC rule is a different kind of exception: since the Scope 3 requirement was dropped from the final rule and the rule itself has faced litigation and a voluntary SEC stay, companies preparing for it are effectively building only a Scope 1/2 disclosure layer, even though their broader inventory still needs Scope 3 for CSRD, California, or investor pressure. The mapping architecture still holds - Scope 3 data simply isn't the layer being asked for here yet.

Assurance is where the shortcuts get found

Several of these regimes are moving toward phased third-party assurance - SB 253 and BRSR Core both build this in over time, and CSRD carries assurance requirements as part of its broader structure. Assurance providers test whether the number in a specific disclosure table actually traces back to a documented calculation. A single, well-documented category-level inventory with clear mapping sheets survives that test far better than four independently built spreadsheets that happen to produce similar-looking totals. Building the mapping architecture now, before assurance requirements tighten, is cheaper than reconstructing an audit trail retroactively.