Short answer
The answer, before the reasoning
The most common EU Voluntary Standard mistakes come from treating the standard either as a casual questionnaire or as a miniature ESRS report. The practical fixes are to map every request to the selected module and Annex II, classify each datapoint status, keep gross metrics separate from offsets, describe only real policies and practices, maintain evidence for every claim, and control whether information is public, counterparty-specific or restricted.
A blank cell, vague policy claim or mixed Option A/B statement is usually a control issue, not a drafting issue.
Direct answer
Figure 1. Branded implementation visual for Common EU Voluntary Standard Mistakes: Value Chain Cap, Modules, Missing Data and Claims.
Why mistakes cluster around the first cycle
The EU Voluntary Standard is deliberately proportionate, but proportionate does not mean informal. Teams often underestimate it because it is voluntary and overstate it because it sits near ESRS and CSRD in the same policy ecosystem. Both reactions create risk.
The standard has modules, datapoint categories, an if-applicable principle, confidentiality provisions, a publication choice, and a value chain cap limited to Annex II. Mistakes arise when those controls are not converted into a working dataset and response process.
Mistake 1: misreading the value chain cap
A frequent error is to say that a CSRD-reporting customer can never ask for anything beyond the whole Voluntary Standard, or that a protected undertaking must always provide everything in Annex I. Both are too simple.
The cap is defined by Annex II for the relevant purposes of sustainability reporting under the Accounting Directive. Requesters should also apply a necessity test: they should not ask for all cap information if they do not need all of it. Requests for other legal purposes or voluntary commercial sharing require separate analysis and documentation.
In practice
| Weak practice | Better practice |
|---|---|
| Treat the whole Voluntary Standard as the cap. | Map the request to Annex II and identify whether it is in-cap, above-cap or outside the cap purpose. |
| Assume every Annex II item must be requested. | Request only information needed for the reporting purpose. |
| Decline everything above cap without explanation. | Clarify purpose, scope and voluntary options while preserving the relationship. |
Mistake 2: mixing Option A and Option B claims
B1 requires the undertaking to disclose which reporting option it has selected: Option A, Basic Module only, or Option B, Basic plus Comprehensive Module. A common first-year problem is to prepare a Basic Module report, answer a few Comprehensive datapoints voluntarily, and then describe the whole output as if Option B has been applied.
The fix is simple: keep the compliance statement precise. If the organisation applies the Basic Module and provides selected additional information voluntarily, say so. Do not create a mixed claim.
Mistake 3: using 'not applicable' to hide missing data
Not applicable means the condition for the datapoint is not met. It does not mean that the data owner has not responded, the system cannot export the information, or the organisation has not yet built the calculation.
In practice
| Status | Use when | Do not use when |
|---|---|---|
| Not applicable | The specified circumstance does not exist. | Data exists but has not been collected. |
| Unavailable | The datapoint applies but information is not available. | The datapoint is inconvenient. |
| Estimated | A reasonable method is used because precise data is not available. | No method or assumption exists. |
| Voluntary | The datapoint is outside the selected option or voluntary layer. | The information is essential under the chosen option. |
| Omitted under permitted basis | Confidentiality, trade secret, classified or legally protected information rules are met. | The organisation simply prefers not to disclose. |
Mistake 4: inventing policies to look mature
The standard asks for practices, policies and future initiatives in a way that can accommodate different maturity levels. Teams sometimes convert informal practices into polished policies that have never been approved, or describe ambitions as if they were approved initiatives.
A stronger approach is to separate: current practices, approved policies, future initiatives and management intentions. A modest but accurate statement is better than an inflated governance claim.
Mistake 5: putting offsets into gross emissions
For emissions, the standard refers to estimated absolute gross GHG emissions, including Scope 1 and location-based Scope 2. Gross emissions should not be reduced by offsets or certificates simply to make the figure look better. Contractual instruments or renewable certificates may be useful information, but they should not obscure the required gross metric.
The control is to keep the emissions calculation, contractual instrument evidence and any voluntary climate claim in separate fields.
Mistake 6: weak evidence behind strong claims
Common weak claims include 'we are committed to sustainability', 'we have robust controls', 'our suppliers follow human rights principles' or 'we have no incidents' without evidence, boundary or review. Evidence is not only for auditors. It helps the company avoid repeated rework and inconsistent answers.
In practice
| Claim type | Evidence to retain |
|---|---|
| Company profile | Registration, sites, activities, employee basis and group structure. |
| Policy or practice | Approved document, owner, version, implementation evidence. |
| Metric | Source extract, calculation file, unit, period, boundary and reviewer. |
| Target | Approval record, baseline, year, units, scope and actions. |
| No incident | Incident register, legal review where relevant and reporting boundary. |
Mistake 7: confusing public report, counterparty pack and evidence access
The standard allows the undertaking to decide whether to make the report public. That does not mean every piece of evidence should be public. A strong reporting system separates the public or shared statement from restricted supporting records.
This distinction matters for personal data, complaints, trade secrets, site-level operational information, commercial relationships and methodology files. The report can be controlled and useful without exposing the full evidence folder.
Fix model: the datapoint status ledger
The practical fix for most mistakes is a datapoint status ledger. For each datapoint, record: module, paragraph or disclosure, Annex II status, applicability, owner, data source, evidence ID, confidentiality status, review status, release status and response history.
This ledger prevents a datapoint from drifting from missing to not applicable, from voluntary to essential, or from internal to public without approval.
Illustrative wording: correcting an overclaim
Weak wording: 'We comply with the full EU Voluntary Standard and provide all required ESG information to customers.'
Stronger wording: 'For the 2026 reporting period, the undertaking has prepared a voluntary sustainability report using Option A - Basic Module only. Selected additional information requested by lenders is provided in a separate lender pack and is not part of the Option A compliance statement. Datapoints marked unavailable or estimated are identified in the evidence register and improvement plan.'
The stronger version is not longer for its own sake. It separates option, purpose, voluntary information, limitations and evidence.
In practice
Myth versus reality
| Myth | Reality |
|---|---|
| The value chain cap means customers cannot ask any ESG question beyond the Basic Module. | The cap is Annex II-based and purpose-specific; other legal or voluntary information routes require separate analysis. |
| If data is missing, mark it not applicable. | Missing data is usually unavailable or estimated, not not applicable. |
| A policy statement can describe future intentions. | Approved policies, current practices and future initiatives should be separated. |
| A public report is mandatory. | The undertaking may decide whether to make the report public. |
| No assurance means no review is needed. | No mandatory assurance does not remove the need for internal review and evidence. |
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
Available as Guided Flex, Live Cohort, 1:1 Expert Mentorship or Corporate Programme.
