ESPR
How to Read a Draft Delegated Act
How to read a draft ESPR delegated act: where drafts appear, what to look for in each section and how to extract the data-field list from the annex
When the first draft delegated act for your product group appears, two things happen at once: buyers start asking "when, and which data?", and a legal text of dozens of pages and annexes lands on your desk. What a delegated act is and how it is adopted is covered separately; this article is about the next step: how to read the draft and what to extract from which section.
Written for ESPR delegated acts, the method carries over to CPR and PPWR implementing acts, which use a similar skeleton.
Where does a draft appear?
An ESPR delegated act leaves traces in three places before adoption. The "Have your say" portal is where the Commission opens the draft to public feedback and announces the feedback window. The Ecodesign Forum — ESPR's consultation body of member states and stakeholders — shares earlier versions and working documents in its meeting papers. After adoption the text sits in the Commission's delegated-act register and, during Parliament's and Council's scrutiny, in the interinstitutional register. The earliest signal of all is the JRC's technical study; see JRC preparatory study.
The skeleton: what to look for where
| Section | Look for | What it means for you |
|---|---|---|
| Subject matter and scope | Product definition, exclusions, CN/PRODCOM codes where given | Is your product in, and which variants are out |
| Definitions | "Placing on the market", "model", "batch", "economic operator" | Granularity and the liable party follow from here |
| Ecodesign requirements | The split between performance thresholds and information requirements | Does the product design change, or only the data |
| DPP provisions | Carrier, access tiers, granularity, registry entry | The requirement list for the technical architecture |
| Conformity assessment | The module: internal production control or third party | Testing and documentation cost |
| Market surveillance and verification tolerances | Which test at inspection, which tolerance | How your declared values will be checked |
| Final provisions | Entry into force and application dates, transitional rules | Your calendar |
The main text is usually short and "applies" the annexes, where the real content sits: read it once from start to finish, the annexes selectively.
Extracting the data-field list from the information-requirements annex
The information-requirements annex usually gives each data point with the same structure: parameter name, unit or format, access tier, level (model, batch, item) and, where relevant, a reference test method. Transfer that structure into a table and add a "where is this data today?" column to every row; the result is a gap map that fits the DPP data fields framework.
Tie the access-tier column to your access rights design and the level column to your granularity decision. Read the performance-requirements annex separately: thresholds and test methods live there, and some may force a design change.
Reading the dates correctly
A draft carries three dates, commonly confused:
- Entry into force — the text legally exists shortly after Official Journal publication; it creates no obligation.
- Application date ("applies from") — the day the requirements bind; usually 18–36 months after entry into force. This is your date.
- Staged dates — some parameters apply later (carbon data in a second phase, for example); read the annex footnotes.
And there is draft status: a text at the "Have your say" stage is not adopted and its dates can move; after adoption the transition period is fixed. For the cross-sector calendar see the DPP timeline by sector.
Feedback and checklist
The feedback window is short and individual submissions carry limited weight; a submission through a sector body or exporters' association, backed by data and test-cost examples, gets attention — exporters' associations and SME support describes those channels. Use this checklist while reading:
- Do our product and all its variants fall within the scope definition; is there an exclusion?
- Who is the liable economic operator: us, the EU importer or an authorised representative?
- Do we have a data source for every field in the information-requirements annex?
- Does the current product meet the performance thresholds; is the test method defined?
- Are the access-tier and granularity provisions compatible with our existing system?
- Is the time between today and the application date enough for a supplier data round?
- Through which association channel, and by which date, do we submit our feedback?
For legal context see the ESPR guide; for the basis of the passport provisions, ESPR Articles 9–13.
Frequently asked questions
Where can I follow a draft ESPR delegated act?
The Commission's "Have your say" portal and Ecodesign Forum meeting documents show a draft first; the JRC preparatory study comes even earlier.
What does "applies from" mean in a delegated act?
The date on which the requirements become binding. Entry into force only means the text legally exists; the application date is what binds you.
Can I submit feedback on a draft on my own?
Yes, the portal is open to everyone. But a submission through a sector body or exporters' association, backed by data and cost examples, has far more impact.
