First UK SRS S2 Reporting Cycle: A 12-Month Implementation Plan

Educational practitioner guidance. Not legal or assurance advice. Verify the current UK SRS text, applicable reporting rules and entity-specific facts before acting.

The project should begin with the required output and release date, then work backwards through board approval, audit committee review, management representations, technical review, data cut-off, model freeze and evidence availability. UK SRS S1 requires disclosures for the same reporting period and at the same time as the related financial statements. This means that a climate programme cannot be scheduled independently from the financial close and annual-report process.

A good first-cycle plan also distinguishes three dates: the reporting-period end, the climate data cut-off, and the publication date. Some climate evidence will be available only after year-end; some data may require estimates; and subsequent events may affect the disclosure before release. The programme therefore needs estimate policies, late-data procedures and a final subsequent-events review rather than simply demanding that every source system closes on the financial year-end.

The illustrative 12-month plan overlaps reporting basis, risks, scenarios, GHG, financial effects, controls and drafting so that critical dependencies close before board approval.

A workstream can be “on schedule” while still being technically incomplete. To prevent false progress, apply the same six gates to material workstreams: scope, method, data, control, disclosure and approval. The specific evidence differs, but the logic remains stable.

Each workstream should pass six evidence-based stage gates before it is treated as reporting-ready.

The first month is not for drafting. It is for deciding what report is being prepared. The organisation should approve the reporting entity, period, materiality process, UK SRS S1 foundation, report location, publication timing, legal and regulatory status, NFSIS/SECR overlaps, intended compliance claim and responsibility model. If the entity may use a UK provision, the programme should identify the condition, comparative consequences, disclosure wording and final approval owner at this stage.

Appoint an executive sponsor, reporting owner, technical lead, programme manager and named data owners.

Create a paragraph-level requirements universe covering UK SRS S1 foundations and UK SRS S2.

Confirm the financial reporting entity and prepare a value-chain and metric-boundary map.

Assess current statutory and regulatory routes, including NFSIS, SECR and current FCA rules, separately from future proposals.

Approve the report location, cross-reference policy, release timetable and document versioning protocol.

Create issue, judgement, estimate, provision, claims and update-trigger registers.

Agree the first materiality and risk workshops and secure finance, risk and business-unit participation.

Climate risk identification should start early because it drives scenario coverage, metrics, targets, financial effects and the final narrative. Use business models, value-chain relationships, assets, locations, products, suppliers, customers, financing and dependencies as inputs. Evaluate physical and transition risks and climate opportunities across defined time horizons, then integrate the output into the overall risk management system rather than keeping a separate workshop list.

1. Define short-, medium- and long-term horizons and relate them to planning cycles, asset lives and strategic decisions.

2. Identify climate drivers, exposed activities and transmission mechanisms using reasonable and supportable information.

3. Assess likelihood and magnitude using the entity’s risk method, with climate-specific adaptations where needed.

4. Identify opportunities through a controlled process rather than treating them as unchallenged growth narratives.

5. Prioritise climate risks relative to other enterprise risks and document risk appetite, thresholds and escalation.

6. Assign owners, monitoring indicators, decision triggers and links to scenario and financial-effects workstreams.

7. Record changes from the previous risk assessment, even in a first UK SRS cycle if the entity has existing TCFD/NFSIS processes.

By the end of month 4, the risk register should be sufficiently stable to define material scenario coverage and financial pathways. It does not need to be frozen permanently; new information can change the assessment. The control is a documented change process, not a claim that the first workshop identified every future risk.

The scenario workstream should define the purpose, material risks covered, scenario sources, physical and transition pathways, time horizons, geographies, assumptions, variables, analytical method, limitations, governance and connection to financial effects. A first-year qualitative or semi-quantitative approach can be proportionate where it is commensurate with exposure and available skills, capabilities and resources, but it still needs specific assumptions, results and decision relevance.

The GHG workstream normally has the longest data dependency. It should begin with organisational-boundary and method decisions, not a request for spreadsheets. Reconcile the GHG population to the financial reporting group, associates, joint ventures, leases, acquisitions and disposals. For Scope 3, assess all 15 categories and document relevance, calculation method, data sources, estimates, limitations and improvement actions.

Financial institutions should start financed-emissions design early because portfolio data timing, coverage, attribution factors, classification and counterpart data create additional dependencies. Where paragraph B59A is relevant because same-period financed emissions are impracticable, build the required explanation into the plan: why same-period information is impracticable, the method, inputs and assumptions used, and the plan and timeline for reporting same-period information.

Metrics should be selected after material climate matters and management decisions are sufficiently clear. The workstream should cover the cross-industry categories, relevant industry-based metrics and entity-specific metrics needed to explain performance. The UK amendment makes specific reference to the IFRS S2 Industry-based Guidance optional; it does not remove the need for industry judgement or disclosure of the sources and industries actually applied.

Create a data dictionary with metric purpose, unit, definition, boundary, period, source, formula, assumptions, estimates, owner, reviewer and change policy.

Document the entity’s industries and activities, candidate sources, metric selection, adaptations and non-use rationale.

Build a target register covering objective, metric, scope, base period, target period, milestones, absolute or intensity basis, gross or net basis, validation and review.

Recalculate prior-period or baseline information where required by an approved policy and explain material changes.

Connect capital deployment, internal carbon price, remuneration and opportunity metrics to actual management processes.

Prepare variance analysis for target performance, including missed milestones and remediation rather than silently revising the target.

Finance should start with the risk and opportunity register and create a bridge to revenue, costs, assets, liabilities, cash flows, financing and capex. Current effects should be distinguished from anticipated effects, and effects already recognised or reflected in financial reporting should be connected without asserting identical measurement bases. Quantification can use a single amount, a range or a controlled qualitative approach where the Standard’s conditions are met.

1. Identify the transmission mechanism and affected business activity for each material climate matter.

2. Map current effects to actual results and balance-sheet positions and anticipated effects to approved planning or scenario information.

3. Determine whether a useful single amount, range or controlled percentage can be provided.

4. Where separate quantification is not useful under the specified conditions, document the assessment and prepare the required qualitative and combined information.

5. Reconcile assumptions to budgets, forecasts, impairment, useful lives, provisions, valuations, tax, treasury and capital planning where relevant.

6. Obtain CFO challenge and record limitations, sensitivity, double-counting controls and changes.

Controls should not wait until the final draft. Design key controls as soon as methods and data flows exist, operate them during dry runs and test them before the year-end close. A first-cycle control assessment should focus on material disclosures, high-estimation areas, manual calculations, model governance, boundary changes, Scope 3, scenario assumptions, financial effects, targets and public claims.

Drafting should begin once the core analysis is stable, not after every number is final. Use a report architecture based on the UK SRS S1 foundation and UK SRS S2 four pillars, then maintain a paragraph-level disclosure matrix linking each requirement to applicability, rationale, boundary, owner, method, evidence, control, draft location, provision, reviewer and finding.

Prepare the basis of preparation, entity, period, materiality, source and location disclosures first.

Draft governance using actual mandates, information flows, challenge and decisions rather than generic board biographies.

Connect strategy, scenarios, resilience, transition activities, resources and financial effects.

Explain risk and opportunity processes and their integration into overall risk management.

Present metric definitions, GHG, targets, progress, changes and industry sources coherently.

Keep judgements, estimates, provisions and compliance wording in controlled records.

Use precise cross-references only to information available on the same terms and at the same time.

A mock review should ask for evidence rather than asking whether the team feels ready. Select high-risk disclosures and require the preparer to produce the source, methodology, calculation, boundary, owner, review, change history and approval within a defined time. The review should test both numerical and narrative information.

The final month should be an approval process, not a discovery phase. Data owners certify completeness and method use; technical reviewers close requirement-level findings; finance signs off connected information and financial effects; legal and the company secretary approve UK status and claims; internal audit or an independent reviewer reports control readiness; management provides representations; the audit committee considers unresolved matters; and the board approves the report and compliance statement.

1. Freeze the final disclosure matrix and list every critical or high-priority open item.

2. Complete subsequent-event and late-data assessments and approve any estimates.

3. Confirm final cross-references, referenced-document versions and release-time accessibility.

4. Obtain management representations over data completeness, methods, judgements, limitations and public claims.

5. Provide the audit committee and board with the provision analysis, unresolved findings and claim hierarchy.

6. Approve or return the report; do not allow production deadlines to convert an unresolved requirement into an implicit omission.

7. Publish the related documents at the same time, capture timestamps and archive the complete package.

8. Open the next-cycle remediation plan and update triggers immediately after release.

The group uses months 1-2 to lock the reporting basis and map existing disclosures. Months 2-4 update the climate risk register and define scenarios. Months 2-7 develop Scope 3, while an interim dry run identifies a material use-phase category and a data gap. Finance begins financial-effects work in month 4 using the updated risks and scenarios rather than waiting for final emissions. By month 8, the group has approved metric and target definitions, and internal audit starts control testing. The first complete draft is assembled in month 9, a mock evidence review in month 10 identifies weak target-boundary and scenario-governance evidence, and remediation closes before audit committee review in month 11.

The programme does not claim that prior NFSIS reporting is equivalent to UK SRS S2. It reuses governance, risk and scenario evidence after gap mapping; reconciles SECR energy and emissions to the UK SRS GHG boundary; and postpones any explicit and unreserved compliance statement until the final Scope 3 and provision analysis is approved.