This disclosure asks an organisation to explain the basis on which it has prepared its sustainability statements. In practice, that means setting out the main reporting choices, assumptions and boundaries used so readers can understand what is included, what is left out, and how the information has been put together. It is about making the reporting approach transparent rather than repeating the underlying data points.
The practical focus is on consistency and coverage: whether the statement reflects the whole organisation and its relevant activities, or only selected parts, and how any exclusions, estimates or judgement calls affect the picture. The aim is to help users judge comparability and completeness, especially where reporting does not cover every operation, site or entity in the same way.
This LRA educational guidance supports disclosure preparation. For the exact requirements, always refer to the official EFRAG source.
A quick mental checklist before you prepare this disclosure — tick each as you settle it.
Key datapoints to prepare
How to prepare it
Request the reporting basis and boundary details
Translate the disclosure into an internal business question — then adapt it to your organisation's own language.
Use your own reporting language first, then map it to the sustainability statement wording. Ask for the terms your team already uses for group scope, boundary, value chain coverage and any exceptions, rather than framework labels.
Please provide the ESRS 2:BP-1 basis of preparation, including consolidated/individual reporting basis, ESG boundary, financial boundary, value chain inclusion, compliance statement, relief used, related ESRS reference, justification and affected datapoints.
Why it fails: This uses framework labels only, which may not match how the owner works day to day. It also bundles too many technical terms without telling the owner what internal records to pull, which system to use, or how to explain differences in plain business language.
Please send the reporting pack details for [period]: the basis used for the group or entity view, the sustainability scope, the finance scope, any differences between those scopes, whether upstream or downstream value chain areas were included, and any exception or workaround used. Use your normal internal terms, attach the source file or system, and add a short explanation for any differences so we can map it into the statement.
Notes that turn data into a disclosure
LRA training templates — adapt them to your organisation, and check the official source before sign-off.
State whether the report is prepared on a group or single-entity basis, explain how the ESG and financial boundaries were set, note whether they differ, describe any value-chain coverage, and identify any reporting relief used together with the related ESRS topic and affected datapoints.
Explain what the boundary choices mean for the scope of the draft disclosure, including which parts of the business and value chain are covered and whether any differences between the ESG and financial scopes change how the figures should be read.
If the scope changes from one period to the next, point to changes in the reporting basis, boundary alignment, value-chain coverage, or use of relief, and explain how those shifts affect comparability and the figures reported.
Preparation tools & forms
Professional preparation tools for BP-1 — free with an LRA Community membership. Register once (it's free) and every download unlocks, together with the Disclosure Library, templates and the LRA AI-assistant.
For each claim, check the evidence
Evidence pack to prepare
Common reporting gaps
Mistakes to avoid when collecting the data
Where judgement is often needed
Illustrative examples
Synthetic, written by LRA — not from a company report, not text from any standard.
We report on a consolidated basis, using the same perimeter for our sustainability reporting and our financial statements; there are no differences to explain. Our reporting also brings in selected upstream and downstream activities, covering purchased materials, transport, product use and end-of-life handling, because those parts of the chain are relevant to the impacts we describe. - We state that our sustainability and financial perimeters are aligned, so no separate reconciliation is needed. - We include value-chain activity, with coverage across upstream and downstream links, and the description above sets out what is included. - We have applied the temporary relief for **anticipated financial effects** under **ESRS E1**, because the underlying estimates are not yet reliable enough for a full quantified disclosure; the affected items are the climate-related financial-effect datapoints in that standard.
Synthetic illustration for practitioner review only. It shows how a reporter might describe its reporting basis, value-chain scope, and a temporary relief in plain language without using the standard’s wording.
We report on an individual-company basis, while our sustainability reporting covers a wider operational perimeter than our statutory accounts, so the two boundaries are not the same. We also include parts of the value chain, but only upstream activity in this case, focused on suppliers and inbound logistics. - Our sustainability perimeter is broader than the financial one, and we explain the difference by pointing to entities and activities included for impact reporting but excluded from the accounts. - We include upstream value-chain activity only, with coverage limited to supplier sourcing and inbound freight. - We use the temporary relief for **anticipated financial effects** under **ESRS E1** and **ESRS E2**; the reason is that the relevant forward-looking estimates are still too uncertain for dependable quantified reporting, and the affected datapoints are the climate- and pollution-related financial-effect items in those standards.
Synthetic illustration for practitioner review only. It shows a different reporting pattern from the first example: individual reporting, a boundary mismatch, upstream-only value-chain coverage, and use of a temporary relief across two ESRS topics.
How companies report BP-1 in practice
Real reports where this topic is disclosed. These are report practice, not exact disclosure templates to copy.

Scenarios to work through
A group prepares one sustainability statement for the parent and its subsidiaries. The reporting team also has a separate management view for one overseas unit that is not part of the consolidated financial statements.
A preparer wants to include supplier labour issues and downstream product-use impacts in the statement, but the draft only covers the company’s own sites and employees. The team is unsure whether the wider chain should be brought in.
The draft sustainability statement uses a relief for one topic because the underlying information is not yet available in time. The team has named the topic but has not explained why the relief was used or which disclosures are affected.
A company has drafted a short statement saying it has prepared its sustainability information in line with the applicable European reporting rules. The wording does not say whether the statement covers all the needed disclosures or whether any parts were left out.
Related framework references
How this disclosure maps across the major reporting frameworks.
Questions this page answers
Start with the datapoints listed on the page: reporting scope basis, sustainability boundary, financial reporting boundary, any boundary difference flag and note, value chain inclusion flag, value chain scope and coverage note, compliance declaration, any relief applied, linked standard reference, relief rationale, and impacted datapoints. The page also gives a step-by-step preparation section to help you turn those inputs into a draft.
Use the page’s preparation steps to set out the basis you are reporting on, then record it consistently with the other scope and boundary datapoints. The page is designed to help you document the basis clearly rather than leaving it implicit.
The page expects you to flag whether the boundaries differ and add a short note explaining the difference. That helps the disclosure stay transparent and gives reviewers a clear trail from the reported scope to the underlying records.
The page asks for a value chain inclusion flag, the scope of what is included, and a coverage note. Together those fields show whether the value chain is in scope and how far the coverage goes, which is useful for assurance review.
The page includes an evidence pack with five items to support assurance readiness. Use it alongside the assurance claims section so you can show what was checked, what evidence supports it, and where the underlying records sit.
The page gives six claims to verify, each with a claim, risk and evidence prompt. Use them as a checklist to test the draft disclosure, identify weak spots, and assemble the supporting documents before sign-off.
The page lists common reporting gaps and mistakes so you can spot missing scope detail, unclear boundary explanations, or weak evidence before the draft is finalised. It is meant to help you correct issues early rather than after review.
The Download Centre includes a Prep & Assurance workbook in .xlsx format. Use it to organise the datapoints, track the assurance checks, and build a cleaner draft before you move to the final disclosure.
The Download Centre also includes a printable Library Card in .pdf format. It is a practical companion for keeping the key points, checks and references together while you prepare the disclosure.
The page includes draft-output support such as visualisation ideas, narrative starters and a content-index line. Use those prompts to convert the collected datapoints into a readable draft without having to start from a blank page.
Get your BP-1 tools — free
Your preparation tools are free for LRA Community members and students. Register once (it's free) and your download starts right away — plus the Disclosure Library, templates and the LRA AI-assistant.
You're in — your download is starting
Your file is downloading now. Your Community Cabinet — with the Disclosure Library, templates and the LRA AI-assistant — is ready too.
Open your Cabinet →