CSRD readiness checklist

The CSRD thresholds guide handles scope and the Omnibus change map separates the instruments.

This guide focuses on operational gates rather than repeating a threshold table.

Keep the original-standard file where it explains a historical report rather than silently relabelling it as revised Original ESRS Revised ESRS.

A project should name uncertainty instead of concealing it behind a green status.

Barrow is fictional and no actual report, provider or compliance conclusion is implied.

The case separates document production from evidence readiness.

An attractive draft can be useful progress without establishing that its claims are sufficiently supported.

Historical IG1 can support understanding but is non-authoritative guidance for the 2023 standards rather than revised paragraph authority IG1 disclaimer EFRAG guidance status.

The materiality template provides a practical record.

Barrow’s fictional team splits a complete metrics section into separate unresolved definition and population reviews.

That makes the remaining work visible without inventing statutory completion percentages.

The ESRS datapoints guide explains why a workbook row and a reported fact are not automatically the same thing.

Barrow’s fictional reviewer retains the unadjusted source and the reporting adjustment separately.

A blank is not automatically zero, not applicable or immaterial; each treatment needs its own reason.

Barrow’s fictional draft describes a programme as effective although the source only establishes that it was launched.

The review therefore keeps the launch and the outcome claim as separate tasks.

The reporting principles guide develops supported and balanced wording.

The CSRD assurance guide explains the defined engagement perimeter.

A readiness checklist should not infer that one finished narrative removes other reporting work.

Barrow’s fictional drafting team leaves an unsupported outcome claim open rather than approving it because the sentence reads well.

The handover should show which wording is provisional and what evidence could change it.

Copy review and reporting review can be coordinated without treating them as identical decisions.

The draft list release describes human navigation rather than all facts every undertaking reports Draft list release.

A completed resource can show work performed without establishing compliance.

The draft XBRL taxonomy supports technical representation and does not make tagging mandatory at this stage EFRAG taxonomy release.

Technical validation is distinct from a management reporting decision and from assurance.

Ask for the export of open items as well as completed answers.

The CSRD architecture concerns a limited-assurance opinion over the relevant reporting information and process Accounting Directive Article 34 Directive 2026/470, Article 1(3).

The consultancy guide separates preparation deliverables from assurance.

Barrow’s fictional team hands over a versioned package and an open-issue register rather than declaring the organisation fully compliant.

Ask reporting software suppliers to preserve that distinction.

The standards homepage provides the wider comparison when the same source supports another reporting output.

The ESRS-40a guide separates the third-country reporting route, draft standard and source-version questions before a group commissions work.