Short answer
The answer, before the reasoning
A first EU Voluntary Standard cycle should be planned in two tracks. The 90-day track creates a usable, controlled first output: scope, module option, dataset, evidence register, gap log, review and release decision.
The 12-month track turns that one-off exercise into a repeatable reporting system with quarterly data capture, stronger evidence, better definitions and response history. The realistic first-year result is not a perfect sustainability report; it is a defensible report or counterparty pack, a controlled dataset and a prioritised improvement plan.
Direct answer
Figure 1. Branded implementation visual for First EU Voluntary Reporting Cycle: A 90-Day and 12-Month Roadmap.
Why a roadmap matters
First-time voluntary reporters often try to do two things at once: answer an urgent customer or bank request and design a permanent sustainability reporting system. If the project is not sequenced, the team can spend months debating future architecture while the immediate requester remains unanswered.
The EU Voluntary Standard is useful because it gives the first cycle a defined perimeter. The Basic Module can support a minimum reporting output. The Comprehensive Module can be added where banks, investors or corporate clients need more information. A roadmap prevents the team from collecting everything at once and instead focuses on what is decision-useful, supportable and approved.
Two implementation tracks
The two tracks should run together. The first provides a usable answer; the second prevents the organisation from repeating the same scramble next year.
In practice
| Track | Purpose | Best output |
|---|---|---|
| 90-day track | Create a first controlled response or report. | Report skeleton, completed core datapoints, evidence register, gap log and release decision. |
| 12-month track | Make the process repeatable. | Quarterly data routine, improved methodology, owner network, response history and next-cycle controls. |
In practice
The 90-day roadmap
| Period | Main actions | Output |
|---|---|---|
| Days 1-15: scope and purpose | Classify requesters, decide reporting period, legal entity or group basis, module option and intended outputs. | Scope note and project charter. |
| Days 16-30: datapoint map | Map B1-B11 and, where relevant, C1-C9 to owners, systems and evidence sources. | Applicability matrix and owner list. |
| Days 31-45: data collection | Collect general information, energy, GHG, pollution, biodiversity, water, waste, workforce, safety, pay, governance and policy information. | Minimum dataset with evidence IDs. |
| Days 46-60: gaps and estimates | Classify missing items as unavailable, estimated, not applicable, voluntary or omitted under a permitted basis. | Gap log and estimation methodology. |
| Days 61-75: drafting | Prepare the report, counterparty pack or lender pack using approved wording and cross-references. | Draft output and disclosure index. |
| Days 76-90: review and release | Run technical, legal/confidentiality and management review; approve release version and response history. | Final first-cycle output and improvement plan. |
In practice
The 12-month roadmap
| Quarter | Focus | Practical result |
|---|---|---|
| Q1 after release | Post-cycle lessons. | List of data gaps, slow owners, weak definitions and request pain points. |
| Q2 | System and evidence design. | Updated data dictionary, folder structure, release rules and training for owners. |
| Q3 | Interim data refresh. | Partial update of energy, HR, incident, policy and request-response data. |
| Q4 | Pre-close readiness. | Known estimates, year-end evidence plan, review calendar and publication decision. |
| Next cycle | Controlled repeat. | Comparatives, fewer manual gaps and a clearer claim about the selected option. |
Quick wins in the first month
Create a one-page project charter: purpose, users, module option, period and release route.
List all existing customer and bank ESG requests from the last 24 months.
Assign one owner for each major data family: company profile, environment, HR, health and safety, governance and policy.
Create a single evidence register before collecting new data.
Use a response log from day one, even if the first output is small.
Agree a vocabulary for not applicable, unavailable, estimated, voluntary and omitted.
Handling data gaps without derailing the cycle
The first year will have gaps. That does not mean the project has failed. The question is whether gaps are visible, classified and improved. A gap that is documented with an owner, reason, estimation method and improvement action is easier to defend than a blank cell hidden in a spreadsheet.
In practice
| Gap type | Meaning | First-year response |
|---|---|---|
| Not applicable | The condition for the datapoint is not met. | Record the reason and retain evidence. |
| Unavailable | The datapoint applies but data is not yet available. | Disclose limitation where relevant and create an improvement action. |
| Estimated | Data is available only through a reasonable method or assumption. | Document methodology, inputs and review. |
| Voluntary non-selection | Information is outside the selected module or voluntary layer. | Record status so users do not mistake it for missing data. |
| Confidential omission | Information is withheld under a permitted basis. | Record rationale, approval and disclosure of the use of exemption where required. |
Publication and release decisions
The standard recognises that the primary function of the report is to inform actual or potential business counterparties, and the undertaking may decide to make the report public. The roadmap should therefore include a release decision, not assume one universal publication route.
Public report: appropriate when information is stable, non-confidential and useful to several users.
Counterparty pack: useful where customers need controlled answers and evidence references.
Lender pack: useful where banks need energy, emissions, workforce, incidents, risks and governance information.
Restricted evidence access: appropriate for source documents, personal data, calculations and confidential records.
Hypothetical example: 90 days without overbuilding
A 120-employee logistics services undertaking receives a bank request in March and two customer questionnaires in April. It chooses Option A for the first cycle and identifies two likely Comprehensive datapoints that may be useful for lenders later. The 90-day project produces a Basic Module report, a lender annex with voluntary notes clearly labelled, an evidence register and a list of data improvements for fuel, employee turnover and health and safety.
The company does not claim that the first report is assured. It does not build Scope 3 modelling before it has stabilised fuel and electricity data. In the 12-month track it adds quarterly utility and HR extracts, trains two data owners and creates a response history so the sales team stops rewriting answers.
In practice
Common planning mistakes
| Mistake | Consequence | Fix |
|---|---|---|
| Starting with design rather than data | Beautiful report with weak evidence. | Build dataset and evidence first, then design output. |
| Trying to complete every possible datapoint | Slow, expensive and confusing. | Start from selected option, purpose and applicable datapoints. |
| Waiting for perfect data | No useful response to market requests. | Classify gaps and publish a controlled limitation where appropriate. |
| No release decision | Public, lender and customer versions diverge. | Define outputs and audiences early. |
| No 12-month owner | Next year becomes another emergency project. | Assign ongoing owner and quarterly rhythm. |
Realistic first-year output
A credible first cycle usually includes: a selected option statement, a controlled report or response pack, an applicability matrix, an evidence register, a data dictionary, a response history, a list of limitations and a prioritised improvement plan. It does not need to include full automation, external assurance, complete multi-framework mapping or an annual report design exercise.
The best first-cycle outcome is learning without loss of control.
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.
