BRSR and CSRD: the data layer no one is building yet

Indian and European disclosure frameworks are converging on the same requirement from different directions: product-level environmental data, built bottom-up from primary measurement. Most sustainability software is still built the other way round, aggregating site totals downward using allocation factors.

Top-down was fine until it wasn't

Allocating a site's annual energy across product lines by production volume produces a number. It is defensible for a corporate-level disclosure and indefensible the moment a customer asks for the embedded footprint of a specific part, which is exactly what CBAM declarations and increasingly customer sustainability clauses require.

What bottom-up actually needs

• Consumption metered at a resolution finer than the site — line at minimum, asset where it matters.
• Production data time-aligned with consumption data, which is harder than it sounds when they live in different systems with different clocks.
• A bill of materials that resolves to the same part identifiers the energy data is attributed against.
• Supplier data for upstream scope, in a structured form rather than as a PDF attachment.
• Lineage, so a figure in a filing can be traced back to the readings that produced it.

The gap nobody is building

Reporting tools are good at the last mile: the disclosure format, the assurance workflow, the submission. The layer underneath — reconciling meter data, production records, and material masters into something a per-product figure can be computed from — is where the work actually is, and it is a data engineering problem rather than a sustainability one.

Why this matters sooner than expected

The reporting cadence is tightening and the boundary is widening at the same time. Annual site averages satisfy fewer requirements each cycle, and the plants that will cope are the ones that started metering and reconciling before the disclosure required it.