UK SRS Readiness Assessment

The useful output is a prioritised project decision rather than a percentage claiming that the organisation is almost compliant.

The FCA’s final rules use a comply-or-explain approach for listed issuers in scope from accounting periods beginning 1 January 2027, rather than making S 2 universally mandatory PS26/19, paragraphs 1.2 and 3.6 and made rules.

A voluntary preparation project and a listed-issuer reporting project can share workstreams while having different authority, timing and public-statement requirements.

Use UK SRS gap analysis for provision-level detail and the standards hub for reporting context, keeping this assessment focused on delivery gates.

The fictional Northmere Instruments group begins with an inherited IFRS checklist and asks the project team to confirm where it matches the intended UK report.

IFRS S1’s source-of-guidance wording and the UK text’s optional SASB reference illustrate why the team cannot simply rename the checklist IFRS S1, paragraphs 55 and 58 UK SRS S1, paragraphs 55 and 58.

IFRS S2’s 2025 text also includes amendment application provisions, while the UK team must check its own final S 2 text and any applicable rules IFRS S2, AppendixC UK SRS S2.

An editorial source register retains the exact document, paragraph reference and decision about how it informs the project.

Northmere’s fictional finance, operations and risk teams each hold part of the evidence, while the reporting coordinator cannot personally validate every underlying assumption.

The project therefore names owners for source records, methods, narrative judgements and approval rather than only owners for final report pages.

A readiness review asks whether those people have agreed the required deliverable and can identify the dependencies that may prevent it.

This does not prescribe a new committee or a particular meeting frequency, and the ESG governance guide covers the broader responsibility and escalation record.

Northmere’s fictional operations team can provide several totals but cannot yet show that their entity coverage matches the intended reporting group.

The project records the missing reconciliation as a delivery dependency rather than describing the totals as a completed climate-reporting workstream.

Scope 3 information may depend on different collection and estimation work from direct operational records, so the plan needs a named method and evidence handover.

Read scope 3 software for relevant collection tests, while choosing sustainability software according to the wider narrative and review workflow.

Northmere’s fictional finance team closes a group planning file before the sustainability team finalises several assumptions, so the first dry run exposes an unresolved interface.

The project creates a handover between the teams that identifies the assumptions under review and who can accept or revise them.

The IFRS Foundation’s materiality education illustrates judging relevant information but expressly does not amend the standards, so it can support discussion without becoming an additional readiness requirement IFRS Foundation, educational material status.

A readiness conclusion should state whether the connection works in practice, rather than merely saying that the two teams attended the same workshop.

Northmere chooses a representative climate topic and follows its evidence through governance, strategy, risks and metrics rather than rehearsing only the emissions table.

The reviewer asks whether the draft describes actual oversight and management activity or only a planned reporting process.

A current limitation may need further work, an applicable relief or a regulatory explanation, but those routes need separate analysis instead of being collapsed into a green readiness status.

The team uses the gap-analysis guide for the precise provisions and applicable explanation requirements, keeping this dry run focused on whether the handovers work.

Northmere’s fictional sponsor accepts the ownership map and source register but keeps the group-coverage reconciliation and finance interface open until the agreed evidence is available.

UK SRS S1 permits an explicit and unreserved compliance statement only where its requirements are met, with specific consequences for using the climate-first provision UK SRS S1, paragraphs 72–73A.

A readiness workshop, software implementation or consultant report therefore should not be described as certification that the future report will comply.

A consultancy brief can request this acceptance record and evidence handover while management retains responsibility for the intended reporting output.

Use the IFRS sustainability reporting software guide to test source versions, disclosure evidence and the S1/S2 reporting workflow.

The UK SRS consultancy buying guide helps specify the reporting basis, preparation work and evidence handover in an engagement brief.