Level 2 · Decision guide·EU Voluntary Standard 2026 · Disclosure guides
How to Answer Customer and Bank ESG Questionnaires Using the EU Voluntary Standard
A controlled workflow for request triage, purpose classification, B/C and Annex II mapping, approved answer reuse, evidence links and response history.
Published passport
Current as at 10 August 2026
Reviewed by
Dr Ross KurinkoLinkedIn
Strategic ESG Advisor · IFRS S1 & S2 / GRI / ESRS expert
GRI Certified Global Trainer · PhD, University of Cambridge · ESG-AI expert
15+ years on FTSE 100 & Fortune Global 500 disclosures
Canary Wharf, London
LRA educational guidance · Not issued or endorsed by European Commission
Edition written against
—
Published
10 Aug 2026
Knowledge Hub guide
Last reviewed
10 Aug 2026
Short answer
The answer, before the reasoning
Use the voluntary standard as a controlled data and evidence model. Start by triaging the requester, entity, purpose, period and intended use.
Map each question to the Basic Module, Comprehensive Module, Annex II or an outside-standard item. Reuse only approved answers with their method, unit, boundary and evidence reference. Explain gaps and estimates transparently, approve confidential or voluntary extras, and retain the exact response and correction history.
Technical status
EDITORIAL STATUS
<p>The mapping logic is grounded in the Commission-adopted standard and Directive (EU) 2026/470. Before publication or operational use, confirm the final Official Journal text, national transposition, the requester’s stated purpose, applicable employee band and any separate lending, due-diligence or contractual basis.</p>
Why questionnaires create more risk than they appear to
A customer or bank questionnaire often arrives as a spreadsheet, portal or PDF with a short deadline. Because the format looks administrative, teams may delegate it to sales, procurement or finance and answer directly from memory. The result is a hidden reporting system: different emissions numbers, different employee counts, contradictory policy claims and no record of what was sent to whom.
The EU voluntary standard can reduce this duplication because it supplies common disclosures, definitions and a structured Basic and Comprehensive architecture. But it is not a universal answer sheet. The requester may have a different purpose, request information outside the standard, use another period or ask for evidence that should be restricted. A good process therefore separates controlled reuse from automatic reuse.
Quick orientation
Figure 1. Six controls turn an external questionnaire into a traceable reporting output rather than an uncontrolled spreadsheet exercise. London Reporting Academy learning visual.
In practice
| Question | Control answer |
|---|---|
| What should be classified first? | Requester, legal entity, purpose, intended use, period, deadline and confidentiality. |
| What should each question map to? | A specific B or C disclosure/datapoint, Annex II cap status, or outside-standard/above-cap status. |
| Does the cap apply to every request? | No. It is purpose-limited to Accounting Directive sustainability reporting requests. |
| Can approved report data be reused? | Yes, after checking period, unit, boundary, definition, applicability and recipient wording. |
| What if data are unavailable? | Explain the gap or use a transparent estimate where appropriate; do not enter zero as a placeholder. |
| What must be retained? | Submitted version, recipient, purpose, date, approval, evidence snapshot and correction history. |
Step 1: Triage the request before answering it
The response team should not start in the first questionnaire cell. It should first create a request record. At minimum, record the requester, recipient business function, supplier legal entity, group or site covered, reporting period, deadline, requested format, confidentiality terms and the person who will approve the response.
Ask how the requester intends to use the information. A large customer may need value-chain data for Accounting Directive sustainability reporting, but the same organisation may also ask questions for procurement qualification, human-rights due diligence, product compliance, risk management or a voluntary supplier programme. A bank may ask for credit risk, financed-emissions analysis, sustainable-finance eligibility or its own reporting. The answer to “why?” determines which legal and commercial rules are relevant.
In practice
| Triage field | Example entry | Why it changes the response |
|---|---|---|
| Requester / function | Customer sustainability reporting team | May indicate Accounting Directive reporting purpose. |
| Purpose | Value-chain sustainability reporting | Potential value-chain-cap analysis. |
| Supplier entity | UK Manufacturing Ltd, not the global group | Controls boundary and employee test. |
| Period | Year ended 31 December 20X6 | Prevents mixing current and prior-year data. |
| Intended use | Customer consolidated report and assurance evidence | Affects evidence and review expectations. |
| Access / confidentiality | Portal accessible to customer group and assurer | Determines whether restricted evidence is appropriate. |
| Deadline / update frequency | 30 days; annual update | Supports prioritisation and version planning. |
Step 2: Classify the request purpose
Purpose classification is the most important control because the value-chain cap is not a general ban on all sustainability questions. Under Directive (EU) 2026/470, the protected-undertaking right to decline applies to information exceeding the voluntary-standard limits when requested for sustainability reporting required by the Accounting Directive. The Directive expressly preserves other purposes, including Union due-diligence requirements, and does not create a supplier obligation to provide sustainability information.
In practice
| Purpose class | Typical request | Cap treatment |
|---|---|---|
| Accounting Directive reporting | Customer seeks value-chain information for its mandatory sustainability report. | Test protected status, employee band, exact Annex II mapping and above-cap rights. |
| Lending / credit risk | Bank assesses business resilience, covenant or credit exposure. | Not automatically within the cap; assess contract, law, proportionality and commercial choice. |
| Risk management | Customer or bank assesses supplier concentration or operational risk. | Outside the cap’s stated reporting purpose unless the same item is also requested for reporting. |
| Due diligence | Human-rights, environmental or product due-diligence request. | Separate legal/purpose basis; do not label automatically as capped or mandatory. |
| Procurement / supplier programme | Vendor onboarding, tender scoring or voluntary supplier development. | Commercial request; document necessity, proportionality and response decision. |
| Mixed purpose | One portal serves reporting, risk, due diligence and procurement. | Split or tag every field by purpose; do not allow one broad label to defeat the analysis. |
Rule
PURPOSE WARNING
<p>A requester’s name does not determine purpose. A bank can make a reporting request, a lending request or both. A large customer can request reporting, due-diligence and procurement information in the same workbook. Record purpose at field level where the questionnaire is mixed.</p>
Step 3: Map every question to B, C and Annex II
Mapping should be exact enough to support a legal and data-quality conclusion. “Climate” is not an adequate map. Link the question to the relevant disclosure and datapoint, the employee band, the selected reporting module, applicability, and whether the item appears in Annex II. A field may be in the voluntary standard but outside Annex II, which means it is not part of the cap.
Annex II at a glance
“Included” above means included in the cap for the relevant employee band; it does not mean that every supplier is automatically required to provide it, that every item applies in all circumstances, or that the requester should ask for the full maximum. The adopted regulation emphasises that reporting undertakings should request only what they need and should request less where the full set is unnecessary.
In practice
| Datapoint group | 10 employees or fewer | More than 10 employees |
|---|---|---|
| B1 basis and general undertaking information | Included | Included |
| B3 energy and estimated gross GHG emissions | Not in cap | Included |
| B6 total water withdrawal | Not in cap | Included |
| B7 circularity, waste and recycling/reuse | Not in cap | Included |
| B8 employee contract type and gender | Included | Included |
| B9 recordable accidents number and rate | Included | Included |
| B10 minimum wage, collective bargaining and training | Included | Included |
| C1 products/services, markets and main business relationships | Not in cap | Included |
| C5 employee turnover rate | Not in cap | Included |
| C6 code/human-rights policy and complaints mechanism | Not in cap | Included |
| C7 confirmed incidents in own workforce and value chain | Not in cap | Included |
Step 4: Build a master response library
The master response library is the operational bridge between the voluntary standard and external questionnaires. It stores answerable content as controlled data atoms rather than as paragraphs copied from old workbooks. One record may support the public report, a customer portal and a lender pack, while still retaining purpose-specific wording and access controls.
In practice
| Master field | Minimum content |
|---|---|
| Question concept ID | Stable code for the concept, independent of requester wording. |
| Standard mapping | B/C disclosure, paragraph/datapoint, applicability and Annex II status. |
| Approved answer | Current narrative or value, not a draft or prior recipient response. |
| Unit and method | Measurement unit, formula, estimation method, assumptions and factor source. |
| Boundary and period | Entity/site/group coverage, exclusions, reporting period and cut-off. |
| Evidence reference | Source system, file, policy, calculation or approval record. |
| Owner and reviewer | Person responsible for content and independent review. |
| Confidentiality | Public, counterparty, NDA-restricted or internal evidence. |
| Version and validity | Effective date, expiry, change trigger and superseded answer. |
Step 5: Reuse answers without losing context
Controlled reuse means the underlying approved fact is reused while the response format is adapted. Before reuse, confirm that the questionnaire asks for the same concept. “Employees”, for example, may mean headcount, full-time equivalent, average during the year, period-end number, own workforce or workers in the value chain. “GHG emissions” may mean Scope 1, Scope 2, Scope 3, location-based, market-based, gross or net.
Same period: do not answer a 20X6 request with a 20X5 figure without a visible note.
Same boundary: distinguish the undertaking, consolidated group, site and product boundary.
Same unit and method: convert only through an approved transformation and keep the source value.
Same status: identify measured, estimated, not applicable, unavailable or not requested.
Same evidence: link the answer to the evidence snapshot available when submitted.
Same claim strength: a policy exists, a process operates and a process is effective are different statements.
Step 6: Handle gaps, estimates and confidential information
A questionnaire deadline does not make missing data available. Where the undertaking has no reliable value, it should not enter zero, “N/A” without explanation or a figure copied from a different boundary. Use a controlled status such as not applicable, not collected, unavailable for the requested period, estimated, or withheld under a stated confidentiality process.
When an estimate is appropriate, retain the estimation method, inputs, assumptions, limitations, owner and review. The response should distinguish an estimated figure from a measured one. Where a requester seeks source evidence, provide the minimum sufficient support through a public document, redacted extract, secure data room, independent confirmation or methodology note, depending on sensitivity and purpose.
In practice
Sample response matrix
| External question | Purpose | Map / cap — Controlled response — Evidence / owner |
|---|---|---|
| Which reporting option and basis do you use? | Customer reporting | B1 · cap for both bands — Option B; individual basis; year ended 31 December 20X6. — Approved basis memo · Reporting owner |
| Total employees by contract type and gender | Customer reporting | B8 · cap for both bands — Provide approved period-end headcount table and definitions. — HRIS extract · HR owner |
| Scope 1 and Scope 2 emissions | Customer reporting | B3 · cap only >10 employees — Provide estimated gross emissions, method, boundary and limitations where relevant. — GHG workbook · Environment owner |
| Detailed product-level carbon footprint | Procurement / product claim | Outside B/C and Annex II as framed — Clarify product, methodology and intended use; negotiate separate work or decline unsupported claim. — LCA files · Product owner |
| Water withdrawal | Customer reporting | B6 · cap only >10 employees — Provide total withdrawal for the relevant boundary; explain estimation where site meters are incomplete. — Utility data · Operations owner |
| Human-rights policy and complaints mechanism | Customer reporting | C6 · cap only >10 employees — Provide approved policy link and factual description of mechanism. — Policy register · Legal/HR |
| Supplier due-diligence incidents | Due diligence | C7 may map, but purpose outside cap — Classify under separate due-diligence basis; protect personal and investigation data. — Case register · Legal/Compliance |
| Three-year revenue forecast under climate scenarios | Bank credit risk | Outside voluntary-standard datapoint as requested — Ask for rationale; provide approved qualitative risk information or separately authorised forecast if appropriate. — Finance model · CFO |
| Evidence of every energy invoice | Bank verification | Evidence request, not a disclosure datapoint — Offer sample, redacted extract or assurance evidence through controlled access. — Invoice repository · Finance |
Step 7: Approve exceptions and voluntary extras
Not every response requires senior approval. Establish thresholds. Routine reuse of current approved Annex II data may be approved by the response owner. New estimates, disclosures of incidents, personal data, legal interpretations, forward-looking financial information, voluntary above-cap information and deviations from the current reporting boundary should be escalated.
In practice
| Response type | Suggested approval |
|---|---|
| Current approved datapoint with unchanged scope | Data owner plus response reviewer. |
| New estimate or methodology change | Data owner, methodology reviewer and reporting owner. |
| Incident, complaint or human-rights information | Legal/compliance and privacy review. |
| Voluntary above-cap information | Commercial owner and reporting/legal approval; document that provision is voluntary. |
| Forecast or financial sensitivity | CFO or delegated finance authority. |
| Request refused or negotiated | Commercial relationship owner with legal/reporting input. |
Step 8: Keep the response history
The response history should make it possible to answer three questions months later: exactly what did we send, why did we send it, and which evidence supported it at the time? Retain the submitted workbook or portal export, recipient, purpose, date, version, approver, confidentiality terms, attachments, evidence snapshot and any later correction or clarification.
This is particularly important where a portal does not allow the supplier to download its response. Take a controlled export or screenshot record where lawful and practical, or keep a response log with the final values and narrative. Do not rely on the live portal as the only historical record.
Hypothetical example: one customer and one bank
Context. Apex Packaging has 84 employees. A major customer sends a 120-question supplier workbook for its sustainability report and procurement programme. A bank sends a separate climate and workforce questionnaire for annual credit review.
Triage and mapping. Apex labels 38 customer questions as Accounting Directive reporting, 42 as procurement or due diligence, 20 as duplicates and 20 as unclear. It maps the reporting questions to B1, B3, B6, B7, B8, B9, B10, C1, C6 and C7 and then tests the exact Annex II datapoints. The bank request is classified primarily as lending and risk management, not automatically as capped.
Response. Apex reuses approved period and boundary fields from its Option B reporting core. It asks the customer to remove duplicates and clarify mixed-purpose questions. It supplies current energy, emissions, water and workforce information, provides policy links, and uses restricted evidence for accident records. It explains that a product-level footprint is unavailable and proposes a phased assessment rather than entering a group-level estimate.
History. The submitted customer workbook and bank portal export are stored with mapping, approvals and evidence snapshots. When an HR data correction changes the gender split, the response owner checks both histories, sends a correction to the affected recipients and updates the master library.
Hypothetical scenario
ILLUSTRATIVE REQUEST CLARIFICATION
<p>“To ensure that our response is accurate and proportionate, please confirm the intended use of questions 41-58 and whether they are requested for your sustainability reporting under the Accounting Directive, procurement assessment, due diligence or another purpose. We have mapped the questions to the EU voluntary standard and identified several duplicate and outside-standard items. Once purpose is confirmed, we can provide the relevant approved information and explain any data limitations or restricted-evidence process.” Illustrative wording only; adapt to the contract, relationship and jurisdiction.</p>
Illustrative only. It shows how the decision is made, not wording that can be copied or relied on.
In practice
Weak versus stronger responses
| Weak response | Why it fails | Stronger response |
|---|---|---|
| “0” entered because the emissions value is unavailable. | Zero appears to be a measured fact and may be reused downstream. | Use “data unavailable for the requested period”, explain the gap and provide an approved estimate only if supportable. |
| “Yes” to “Do you have an effective grievance mechanism?” | Existence and effectiveness are different claims. | Describe the mechanism, scope, access route and available outcome evidence; avoid unsupported effectiveness claims. |
| A prior-year employee number copied without date. | The requester cannot understand period or comparability. | Give the period-end or average measure requested, define headcount/FTE and state the reporting date. |
| Full internal incident register uploaded as evidence. | Excess personal, legal and confidentiality exposure. | Provide an approved summary or redacted evidence under controlled access. |
In practice
Common mistakes and corrections
| Mistake | Consequence | Correction |
|---|---|---|
| Classifying purpose at workbook level only. | Mixed reporting and due-diligence items receive the wrong cap treatment. | Tag purpose at question or question-group level. |
| Mapping to a topic instead of a datapoint. | Above-cap status cannot be defended. | Record exact B/C paragraph and Annex II inclusion. |
| Using “N/A” for not collected, not applicable and confidential. | Recipient cannot distinguish the reason. | Use controlled status codes with explanatory notes. |
| Copying narrative from the public report without checking the question. | Answer may be technically true but non-responsive. | Map the question concept and adapt presentation, not the approved fact. |
| No submitted-version archive. | Later disputes or corrections cannot be reconstructed. | Retain export, attachments, approval and evidence snapshot. |
| Sales promises future data without owner approval. | Creates an unmanaged commitment. | Use phased-data wording with owner, scope and target date. |
Myth
“Once we have completed the EU voluntary report, every ESG questionnaire becomes a copy-and-paste exercise.”
Reality
The report creates a strong approved data core, but each request still needs purpose, definition, period, boundary, cap, confidentiality and intended-use checks. The goal is controlled reuse with fewer new judgements, not blind reuse with no judgement.
Readiness
Reader checklist
- The requester, recipient, entity, period, deadline and intended use are recorded.
- Each field has a purpose classification, including mixed-purpose fields.
- Each potential cap item maps to an exact Annex II datapoint and employee band.
- The response does not imply that the standard creates a universal supplier duty.
- Approved answers retain unit, definition, boundary, period, method and evidence.
- Unavailable data are not represented as zero or unexplained N/A.
- Estimates and methodology changes are visibly labelled and approved.
- Personal, incident and trade-secret evidence is access-controlled.
- Voluntary extras and above-cap responses have documented authority and conditions.
- The exact submitted response and all later corrections are retained.
Self-check
- Why is a bank questionnaire not automatically inside or outside the value chain cap merely because the requester is a bank?
- What is the difference between mapping a question to “climate” and mapping it to a specific Annex II datapoint?
- Which response-history fields would allow an assurance reviewer to reconstruct what the customer received?
Related learning path
Publication architecture: Must an EU Voluntary Sustainability Report Be Public?
Supplier response: How to Respond to an Above-Cap Sustainability Data Request Without Damaging the Customer Relationship.
Requester redesign: How Large Companies Should Redesign Supplier ESG Questionnaires Around the Value Chain Cap.
Status evidence: Protected Undertaking Self-Declaration: What Suppliers and Requesters Should Document.
Rule
USE OF THIS SECTION
<p>The following material supports technical review, CMS publication, AI retrieval and future updating. It is not intended to appear in full on the public web page.</p>
Take it with you
The checklists as a working spreadsheet
Every checklist and table on this page, with empty status, owner and evidence columns for your team to fill in and keep.
✓ LRA AI Assistant · Human-in-the-loop
Ask about this guide
It answers from this page, and reaches into the linked disclosure cards when your question is about the standard itself. Your first two answers are free without signing in.
Go deeper · EU Voluntary Standard 2026
ESG Reporting Full Stack
There is no standalone LRA course for this framework yet. The Full Stack programme covers the reporting system it sits in — materiality, data, drafting and assurance — with exercises on your own data.
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.