Can One Climate Dataset Support UK SRS S2, IFRS S2, ESRS E1, TCFD and CDP?

Educational practitioner material. Illustrative examples and wording require adaptation and technical review.

Organisations typically fall into one of two inefficient models. In the first, each framework has its own spreadsheet, emissions total, scenario narrative and target register. This creates duplicated work and conflicting facts. In the second, one “universal” climate report is copied into every channel. This is faster initially but often misses framework-specific requirements and encourages unsupported compliance claims.

A better model has three layers: a common governed source layer; a framework adjustment layer; and controlled publication outputs. The source layer is stable. The adjustment layer records differences in scope, method, materiality and timing. Each publication carries its own approval, assurance and claim status.

The master model stores common facts and evidence in six layers, then generates separate UK SRS S2, IFRS S2, ESRS E1, TCFD and CDP outputs through controlled adapters.

Layer 1 - Reporting entity, locations, value chain and period

The foundational table identifies legal entities, business units, facilities, assets, products, investees, counterparties and value-chain stages. Required attributes include ownership, financial consolidation status, operational-control status, lease status, geography, industry classification, acquisition or disposal date, reporting period and responsible owner.

This allows one source record to be selected differently by a UK reporting entity, an IFRS reporting entity, an EU undertaking, a CDP organisational boundary or a legacy TCFD report. Boundary adjustments should be generated from attributes and rules, not hidden manual overrides.

Layer 2 - Climate impact, risk and opportunity register

Each climate issue record should distinguish the physical or transition driver, the external impact pathway, the financial transmission channel, affected stakeholders, assets or value-chain stages, time horizon, likelihood, magnitude, evidence and response. The register then stores separate materiality conclusions for UK SRS/IFRS S2, ESRS impact materiality, ESRS financial materiality and any CDP routing or response relevance.

The design prevents a common error: converting an impact into a financial risk before it is recorded, or ignoring an impact because a current financial effect has not been quantified.

Layer 3 - GHG ledger

The GHG ledger contains the source activity, unit, gas, factor, GWP, Scope, Scope 3 category, calculation method, location-based and market-based Scope 2 fields, consolidated-group/investee status, estimate quality, supplier evidence, base year and restatement history. It should produce absolute gross emissions before any removals or credits.

A reusable ledger retains all methods required by the output profiles. It does not overwrite a location-based result with a market-based result, or delete a category because one framework offers a transition relief. Changes to factors, GWP values, organisational boundary or base year are processed through a controlled restatement workflow.

Layer 4 - Scenarios, resilience and financial-effects bridge

This layer links scenario assumptions and asset-level exposures to business consequences and financial planning. It records scenario source, pathway, time horizon, geography, variables, strategic cycle, model owner, uncertainty, vulnerabilities, adaptive capacity and response. A financial bridge maps results to revenue, operating costs, capex, assets, liabilities, financing and cash flows.

One scenario analysis can support several outputs, but the materiality and disclosure questions differ. UK SRS S2 and IFRS S2 focus on resilience and prospects. ESRS also operates through double materiality. TCFD may require a subset of the same governance, strategy, risk and metric information. CDP may request more granular questionnaire fields or scoring evidence.

Layer 5 - Transition actions, targets, credits and industry metrics

The transition-action register stores each lever, activity, owner, timing, resource, expected gross reduction, dependency, affected stakeholder, status and evidence. The target register stores gross or net status, base year, boundary, milestones, validation, performance and revisions. The removals and credit registers remain separate from gross emissions.

Industry and sector metrics should be linked to business activities and classifications rather than hard-coded into one report. UK SRS S2 requires industry-based metrics relevant to the business. IFRS S2 also requires industry-based metrics and consideration of its industry guidance. TCFD alone does not contain all of these additional requirements, and CDP or ESRS fields do not automatically substitute for them.

Layer 6 - Evidence, controls, approvals and version history

Every reported datapoint or narrative claim should link to source evidence, preparer, reviewer, approval, methodology version, retention rule, access classification, issue log, correction and assurance status. The system should distinguish evidence that is public, evidence available to an assurer and restricted confidential evidence.

This layer makes the model audit-ready and AI-ready. It also prevents an output adapter from presenting a pending estimate, unapproved scenario or obsolete target as current information.

The adjustment register is the control that converts common data into a defensible output. It should exist for every material topic and every metric. A simple framework-to-field map is not enough; the record must explain the reason for the adjustment and preserve the source value.

IFRS S2 incorporates and builds on the TCFD recommendations. The IFRS Foundation explains that applying IFRS S1 and IFRS S2 meets the TCFD recommendations, but IFRS S2 includes additional requirements such as industry-based metrics, planned use of carbon credits and further information on financed emissions and Scope 3. A system designed only around the four TCFD pillars and eleven recommended disclosures can therefore be too shallow for UK SRS S2 or IFRS S2.

Some entities will still need a TCFD-labelled output because a local rule, contract, legacy report or stakeholder request refers to TCFD. The safest architecture is to generate that output from the richer master model while recording the exact local basis and claim.

CDP can act as both an input channel and an output adapter. Its questionnaire prompts data collection and may expose gaps before annual-report drafting. Its response and score are nevertheless governed by CDP’s own cycle and methodology. Store each CDP answer with questionnaire year, question ID, routing, period, unit, evidence, confidentiality status and submission version. Then map it to the master record rather than making the CDP response the source of truth.

1. Inventory every required output, legal route, framework edition, reporting entity, period, publication date, assurance perimeter and proposed claim.

2. Define the master climate data model and controlled terminology before selecting software or rebuilding spreadsheets.

3. Create entity, facility, value-chain and industry-classification tables linked to the financial consolidation system.

4. Migrate GHG calculations into a ledger with source, factor, method, Scope, category, estimate and restatement attributes.

5. Build an impact/risk/opportunity register with separate materiality lens fields and approvals.

6. Connect scenarios, transition actions, targets, credits and financial effects through persistent IDs.

7. Configure framework profiles and an adjustment register for boundary, period, methods, reliefs, assurance and claims.

8. Test each output against the framework requirements using representative cases, including acquisitions, missing Scope 3 data and target revisions.

9. Run a cross-channel consistency and evidence-readiness review before any board or submission deadline.

10. Lock the published version, retain the transformation and approval record, and trigger updates when a framework or source record changes.

The model succeeds because every output can be reconciled back to a source record and forward to a framework requirement. Differences are visible and explained rather than eliminated by manual editing.

Designing the model around final questionnaire fields instead of persistent source facts and evidence.

Using “Scope 3 total” without category, method, estimate and boundary attributes.

Losing historical methodology versions and being unable to reproduce a published figure.

Applying one materiality conclusion to UK SRS, IFRS S2 and ESRS without separate lens decisions.

Treating TCFD as fully equivalent to IFRS S2 or UK SRS S2.

Treating CDP routing or scoring as a reporting-standard requirement or relief.

Failing to version the revised ESRS, the December 2025 IFRS S2 amendments or future UK regulatory profiles.

Recording assurance as a yes/no field without subject matter, criteria, level, period and boundary.

Allowing public claims to be generated automatically without legal and governance approval.

Start with a minimum viable master model covering entity, GHG, climate issues, scenarios, transition actions, targets and evidence. Test it on the current reporting cycle and three difficult cases before scaling: an acquisition, a material Scope 3 estimate and a public target revision. Only then automate output generation or AI-assisted drafting.