A reporting manager at a multinational has three deadlines bearing down: an ESRS sustainability statement for the EU, an ISSB-aligned climate disclosure for two other jurisdictions, and a CBAM declaration for the steel her company imports. Three teams have quietly formed, each rebuilding the same Scope 1 figure from the same source data, each maintaining its own spreadsheet, each one number away from contradicting the others in public. She does not have three carbon footprints. She has one. This lesson is about reporting it once, into three frameworks, without breaking the thread back to evidence.

One Fact Base, Many Frameworks

The defining mistake of multi-framework reporting is treating each framework as a separate project with its own data. It feels safe, each team owns its output, but it is expensive and dangerous. Expensive because the same underlying facts get gathered, calculated, and verified three times. Dangerous because three independently maintained versions of the same number will eventually disagree, and a public contradiction between your ESRS statement and your ISSB disclosure is a credibility event an assurer and a regulator will both notice.

The practitioner's model is the opposite: one governed fact base, mapped into many frameworks. You build and verify the underlying facts once, the activity data, the emission factors, the Scope 1, 2, and 3 inventory, the policies and targets, then map each fact to the specific datapoint each framework requires. ISSB convergence makes this realistic: IFRS S1 and S2 are now adopted or planned across more than 30 jurisdictions representing over half of global GDP, built on a common architecture, so the overlap between regimes is large and growing. Treat that adoption figure as a number to verify for your own footprint, but the direction is clear: the frameworks increasingly ask for the same facts in different shapes.

You do not have three carbon footprints. You have one, reported three ways. The moment your three reports imply otherwise, one of them is wrong.

There is a governance dimension here that is easy to miss when you are focused on the numbers. Three independent reporting projects mean three sets of judgment calls, made by different people at different times, about the same underlying questions: where the boundary sits, which factor to use, whether a topic is material, how to handle a gap. Each project will resolve those calls slightly differently, and each will document them in its own file. When an assurer or a regulator looks across the filings, the inconsistencies are not just arithmetic, they are evidence that the company does not have a single, governed view of its own sustainability data. That impression is corrosive. A unified fact base, by contrast, forces the judgment calls to be made once, by an accountable owner, and recorded once, so the company speaks with one voice across every framework it reports into.

Where the Frameworks Overlap

Start with the overlap, because that is where the reuse lives. All three regimes ultimately price or report greenhouse gas emissions built on the GHG Protocol, so the core inventory is shared. Your gross Scope 1 emissions, calculated once from metered fuel use and dated emission factors, is the same physical quantity whether it lands in an ESRS climate datapoint, an IFRS S2 metric, or feeds the installation-level reasoning behind a CBAM figure. The activity data underneath, fuel volumes, electricity consumption, production output, is collected once and serves all three. The emission factors, with their provenance, are the same factors. Targets, transition plans, and governance descriptions overlap heavily between ESRS and ISSB.

This shared core is the saving. A factor verified once, with its named, dated source, is a factor you do not verify again for the next framework, you reuse it and carry its provenance with it. A Scope 1 figure reconciled once to source is reconciled for all three. The reuse that saves the most work is precisely the reuse of the verified, provenanced core inventory, because verification is the expensive part, and doing it once instead of three times is where the hours go.

Be precise about what "the saving" actually is, because it is not where teams instinctively look. The instinct is to save on data collection: gather the fuel bills once, the production volumes once. That saving is real but small, because data entry is cheap. The large saving is on verification and judgment, the slow, skilled work of tying each figure to its source, choosing the defensible method, confirming the boundary, labeling primary versus secondary, and assembling the evidence. That work is what consumes the weeks and the senior hours, and it is the work you genuinely only have to do once if your architecture lets a verified fact flow into many frameworks. A reporter who unifies data collection but still re-verifies every figure three times has captured the cheap saving and missed the expensive one.

Where the Frameworks Diverge

Reuse without understanding the divergences is how you map the wrong fact into the wrong slot. Three divergences matter most.

Double Versus Financial Materiality

ESRS runs on double materiality: a topic is reportable if it is significant from either the impact direction, how your company affects people and the environment, or the financial direction, how a sustainability matter affects your company's finances. ISSB runs on financial materiality alone: it asks what affects enterprise value. Why this matters for mapping: the financial-materiality conclusions can often be reused across both, but the impact-materiality conclusions are an ESRS-only layer that ISSB does not require and that you cannot manufacture from financial-materiality work. Map the financial lens across both; keep the impact lens as ESRS-specific. Collapsing the two is a common and serious mapping error.

Scopes and Boundaries

The frameworks share the Scope 1, 2, and 3 architecture, but they differ in emphasis and in boundary detail. CBAM cares about embedded emissions per tonne of a specific imported good from a specific installation, a narrow, product-level cut that is not the same object as your corporate Scope 3 category for purchased goods, even though both describe upstream emissions. A figure that is correct as a CBAM installation value is not automatically correct as an ESRS or ISSB inventory line, and vice versa. Map by meaning, not by name: two datapoints that sound alike can have different boundaries.

Factors and Methods

Method and factor requirements can differ. A spend-based estimate that is defensible for a non-material ESRS Scope 3 category may not satisfy what a CBAM declaration needs, where actual installation values or correctly applied published defaults are the only acceptable bases. Reuse the underlying activity data, but check that the method and factor meet each framework's bar before you let a figure cross over.

The mental model that keeps this straight is to separate the activity data from the figure built on it. The activity data, how many tonnes of steel you imported, how much fuel a site burned, is a fact about the world, and it is reusable everywhere because it does not depend on a framework. The figure derived from that data, by applying a method and a factor, is a framework-shaped object, because the method and factor that are acceptable depend on the framework and the materiality of the line. So the reuse that is always safe is at the activity-data layer. The reuse at the derived-figure layer is conditional: it is safe only when the method and factor that produced the figure also satisfy the framework you are mapping into. A practitioner who reuses activity data freely and reuses derived figures only after a method-and-factor check is reusing exactly as much as is defensible, and no more.

Assurance Expectations

One further divergence shapes how hard each figure has to work. The frameworks sit inside different assurance and verification regimes. A CBAM actual value depends on supplier data verified by a recognised body at the installation. An ESRS figure sits inside the company's sustainability-statement assurance engagement, most often limited assurance today and trending toward reasonable. An ISSB-aligned disclosure may face its own jurisdictional assurance expectation. The underlying fact can be shared, but the level and form of verification a framework demands of it can differ, so a figure that clears one framework's bar is not automatically cleared for another's. Map the fact, but confirm the verification standard travels with it.

Mapping Without Breaking Traceability

The whole point of mapping once is lost if the map itself is not traceable. Each framework's datapoint must still trace back to the same verified fact and its evidence, otherwise you have not unified your reporting, you have just hidden three silos behind one spreadsheet. The discipline is a mapping that records, for each framework datapoint, which fact in the governed fact base it draws from, and confirms that the fact's boundary, method, and factor satisfy that framework's requirement.

This is where AI is a strong, and safe, accelerator, used the way the rest of the program uses it. A model can propose mappings at scale: given your fact base and the datapoint lists for ESRS, ISSB, and CBAM, it can suggest which fact feeds which datapoint across hundreds of items far faster than a person. That is a genuine speed-up on tedious cross-referencing. But a proposed mapping is exactly as trustworthy as a proposed tag or a drafted number, which is to say it is a hypothesis. The model will sometimes map by name and miss a boundary difference, route an impact-materiality conclusion into an ISSB financial slot, or carry a spend-based factor into a CBAM line it cannot support. The human verifies each mapping against the divergences above: same fact, same boundary, acceptable method, before it is accepted.

And the traceability has to survive the mapping. When a fact is reused across three frameworks, its provenance, the source, the factor, the verifier, travels with it into each. If the ESRS, ISSB, and CBAM figures all draw from one verified Scope 1 fact, an assurer pulling any of the three should land on the same evidence. That single shared evidence trail, rather than three divergent ones, is both the efficiency and the defensibility, the same move achieving both, exactly as the goldmine of this program promises.

The Mapping Is Itself an Auditable Artifact

It helps to treat the mapping not as a mental shortcut but as a deliverable that lives in the file. Concretely, it is a record that, for every framework datapoint across ESRS, ISSB, and CBAM, names the single fact in the governed fact base it draws from and notes the checks that justified the link: that the boundary matches, that the method and factor meet the framework's bar, that the materiality lens is the right one. Built this way, the mapping is something an assurer can examine directly. They can ask "show me where this ISSB metric comes from" and you can point at the fact and the check, the same way you point at the source behind a number. A mapping that exists only in people's heads, or as an undocumented set of copy-paste moves between spreadsheets, gives the assurer nothing to test and gives your successor nothing to inherit.

This is also what makes the architecture survive change. When a fact is restated, a corrected diesel figure, a re-verified supplier value, you update it once in the fact base, and the documented mapping tells you exactly which datapoints in which frameworks depend on it and must be re-derived. Without that mapping, a restatement becomes a frightened hunt across three reports for everywhere the old number might be hiding. With it, a restatement is a controlled, traceable propagation from one corrected fact to every place it legitimately feeds. The mapping turns a multi-framework restatement from a crisis into a process.

A Worked Example: One Scope 1 Figure, Three Reports

The multinational's verified Scope 1 figure for FY2025 is 121,400 tCO2e, reconciled once to metered fuel use and dated factors, with its provenance packet. Watch it map well, and watch the silo alternative fail.

The silo failure. Three teams each build Scope 1 from the raw data. The ESRS team gets 121,400. The ISSB team, working a week later off a slightly updated diesel figure, gets 121,650 and never reconciles to the ESRS team. The CBAM declarant, meanwhile, mistakes the corporate Scope 1 total for installation-level embedded emissions and tries to use it on a steel line, where it has the wrong boundary entirely. Three numbers, three small errors, three public documents that do not agree. An assurer reconciling across the filings finds the 121,400 versus 121,650 discrepancy and the boundary mismatch, and now every shared figure is suspect.

The mapped success. The verified 121,400 lives in the governed fact base with its provenance. AI proposes the mappings: this fact feeds the ESRS gross Scope 1 datapoint and the IFRS S2 gross Scope 1 metric, both of which share the corporate-boundary meaning. The human verifies both mappings, confirms the boundaries match, and accepts them, the single fact now reported in two frameworks from one evidence trail. For CBAM, the human checks the model's proposal and rejects any attempt to route the corporate Scope 1 total into an installation-level embedded-emissions line, because the boundary is wrong; CBAM draws instead from installation-specific supplier data, mapped separately. The impact-materiality conclusions that drove the ESRS climate disclosure are kept ESRS-specific and not pushed into the ISSB financial-materiality assessment. When the assurer pulls the ESRS Scope 1 and the ISSB Scope 1, both resolve to the same 121,400 and the same evidence. The reports agree because they are the same fact, mapped, not three facts, rebuilt.

Same data, same deadlines. The silo version produced contradiction and triple work; the mapped version produced one verified fact, reused across frameworks, with the thread back to evidence intact in every report.

Standing the Architecture Up in Practice

None of this requires a grand platform or a multi-year programme to begin. The shift from silos to a mapped fact base is mostly a shift in discipline, and you can start with the figures that matter most. Pick the handful of facts that feed the most framework datapoints, the core GHG inventory lines, the headline targets, and govern those first: verify each once, attach its provenance, define its boundary and method explicitly, and write down which ESRS, ISSB, and CBAM datapoints it feeds. That single move, even applied to a dozen high-traffic facts, eliminates the most dangerous divergences, because the most-reused numbers are exactly the ones most likely to embarrass you if three versions disagree in public.

From there the human-and-AI division of labour is the familiar one. Let the model do the wide, tedious work: cross-reference your fact base against the full datapoint lists of each framework and propose the mapping across hundreds of items, flag where a single fact appears to feed datapoints in multiple frameworks, and surface the candidates for reuse. Then put every proposal through the same human gate, same fact, same boundary, acceptable method, correct materiality lens, and accept only what passes, recording the link. The model's speed makes the comprehensive mapping feasible; the human's judgment makes it correct; the recorded mapping makes it durable. This is the same pattern that governs grounded drafting, number verification, and tag confirmation elsewhere in the program, applied now to the relationships between frameworks rather than to a single figure.

What you are building, in the end, is a reporting function that knows its own facts. Ask such a function "what is our gross Scope 1, and where does it appear?" and it can answer in one breath, with the figure, its evidence, and every framework datapoint it feeds. Ask a siloed function the same question and you get three answers that almost agree, each defended by a different person from a different spreadsheet. The first function reports faster and defends better because it did the expensive work once and mapped it. The second pays for the same verification three times and still risks the contradiction that turns a clean reporting cycle into a credibility problem.

Key Takeaways

• You have one fact base, not three. Build and verify the underlying facts once, then map each into ESRS, ISSB, and CBAM. Three independently maintained versions of the same number will eventually contradict each other in public.
• The overlap is large and growing: all three regimes report GHG emissions on the GHG Protocol, so the core inventory, activity data, and provenanced factors are shared. ISSB is adopted or planned across 30+ jurisdictions representing over half of global GDP, a figure to verify for your footprint.
• The biggest saving is reusing the verified, provenanced core inventory, because verification is the expensive step. A factor or figure verified once is reused with its provenance, not re-verified per framework.
• ESRS uses double materiality, ISSB uses financial materiality alone. Reuse financial-materiality conclusions across both, but keep the impact-materiality layer ESRS-specific; collapsing them is a serious mapping error.
• Map by meaning, not by name. A CBAM installation-level embedded-emissions figure is not the same object as a corporate Scope 3 line, even though both describe upstream emissions. Boundaries differ behind similar-sounding datapoints.
• Method and factor bars differ. A spend-based estimate acceptable for a non-material ESRS category may not support a CBAM line that needs actual values or correct defaults. Check the method meets each framework before a figure crosses over.
• AI is a strong accelerator for proposing mappings at scale, but a proposed mapping is a hypothesis. The human verifies same fact, same boundary, acceptable method, before accepting, exactly as with tags and numbers.
• Traceability must survive the mapping: each framework datapoint traces to the same verified fact and one shared evidence trail. That single trail is both the efficiency and the defensibility, the same move achieving both.