Skip to content

Perspectives

What UK SRS S2 assurance-readiness actually requires

A plain account of what the UK Sustainability Reporting Standards ask of a climate disclosure, and what 'ready to assure' means in practice — before anyone signs it.

Last reviewed June 2026 5 min read


UK SRS S1 and S2 were finalised on 25 February 2026 for voluntary use, and the FCA's CP26/5 consultation (published 30 January 2026, closed 20 March 2026) proposes to make UK SRS S2 climate disclosures mandatory for roughly 500–515 listed companies for financial years beginning on or after 1 January 2027. Broader S1 disclosures and Scope 3 are proposed on a comply-or-explain basis, and a policy statement is expected in autumn 2026. Alongside this the FRC's interim register of sustainability assurance practitioners is due by mid-2026 — which is what makes traceability commercially live, not just a virtue.

The intended date is not why we are writing about it. Firms are already being told, by their advisers, to run a gap assessment. What is not so clearly stated is what "ready to assure" actually looks like when the assurance regime lands. It has three parts, and the third is the one people underestimate.

One: complete against the standard, on the buyer's terms

Completeness sounds like an item-tick. It is not. The standard sets out required disclosures across governance, strategy, risk management, and metrics and targets — and a "complete" disclosure is one that speaks to each of them as the standard defines them, not as the company would prefer to describe them. The most common failure mode we expect to see is a disclosure that reads well, covers the ground the business wants to cover, and omits or reframes one of the required specifics in a way that reads consistent to a preparer but stands out to an assurer.

Ready-to-assure means someone has walked every required disclosure against the text of the standard, cross-referenced the treatment, and recorded where each is met — with a note wherever a required element is treated by narrative rather than by data, and why.

Two: internally consistent across the pack

A climate disclosure does not sit alone. It refers to the transition plan, the investor deck, the board risk register, the annual report narrative, and the underlying data model that produces the emissions numbers. It is astonishingly common for one of those to disagree with another — a 2030 target stated as 42% in the transition plan and 45% on an investor slide; a baseline year stated as 2019 in one place and 2020 in another; a materiality determination described differently in two documents that are both current.

These are the findings assurance work will flag, and they are extremely tedious to catch by hand. Any assurance-readiness that has not reconciled the pack against itself is not ready.

Three: source-bound and revision-current

This is the one that surprises people. Assurance is not about whether the disclosure is well-written. It is about whether every claim in it can be tied to a specific piece of source evidence — the row of the emissions model, the paragraph of the board minutes, the exact clause of the policy — and whether that source is authoritative, meaning current and non-superseded.

Regulated estates rarely have a single authoritative version of anything. There is usually a live document and one or more legacy versions that have not been formally withdrawn. A disclosure that cites a source that has been quietly superseded is a disclosure with a hole in it, whether or not anyone has noticed. The assurance regime, once it lands in earnest, will find these.

What "ready" therefore looks like

Three artefacts, produced together:

  • A completeness map against the standard — each required disclosure, treated or gapped, with the treatment referenced.
  • A cross-document consistency check — every quantitative claim traced across the pack, every contradiction listed and reconciled.
  • A source-bound evidence log — every claim tied to a specific document, revision and passage, with the current-versus-superseded question answered explicitly.

Not one of these is intellectually hard. All of them are unforgiving to do by hand under deadline, and all of them recur every cycle. That is why we built facilit8 — to produce all three as an ongoing service, alongside the disclosure itself, so the artefact that lands on the signatory's desk is one they can defend.


This piece rests on the state of UK SRS and the assurance regime as of June 2026. The mandatory application date, the scope in the final rules, and the assurance-regime detail are still moving; the position stated here should be re-checked against the FCA's autumn 2026 policy statement and the FRC's confirmed register before being relied upon.


More perspectives

Back to the index