ESPRChecklistEU

ESPR Ecodesign Evidence Checklist

A source-cited checklist for turning each applicable ESPR delegated act into product evidence, supplier substantiation, technical documentation, DPP fields, and authority-ready records.

It is relevant when a product group becomes covered by an ESPR delegated act or when an existing ecodesign file needs to be refreshed against updated standards, methods, or product data.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Sections
8

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

ESPR evidence work starts with the applicable , not with a generic sustainability claim. For each covered product group, capture the product boundary, the performance and information requirements, the verification method, the DPP obligations, the conformity assessment module, and the records that manufacturers, importers, distributors, suppliers, notified bodies, customs, or market surveillance authorities may need to inspect.

Section 1

1. Extract the delegated act before collecting evidence

Create one evidence row for each product group or horizontal requirement covered by the applicable . The row should identify the covered product descriptions and commodity codes, the exact ecodesign requirements, the test, measurement or calculation methods, any harmonised standards or common specifications, the conformity assessment module, required manufacturer information, date of application, transitional period, and review date. Under Article 4(4), application is generally no earlier than 18 months after entry into force, but duly justified cases and partial repeals or amendments can use an earlier date.

Do not add product-specific thresholds, banned substances, DPP fields, labels, or application dates unless the or another cited source actually specifies them. ESPR is framework legislation; the concrete rules are adopted product-by-product or horizontally.

  • Evidence fields: title, CELEX or ELI URL, product group definition, commodity codes, requirement type, application date, transitional period, review date, and internal product families mapped to the scope.
  • Requirement extraction: separate Article 6 performance requirements from Article 7 information requirements, and flag any Article 4 additional obligations on technical documentation, market quantities, in-use data, digital tools, or supply-chain actors.
  • Approval gate: legal or product compliance confirms that the evidence row cites the binding and does not rely on a draft, consultation page, or working-plan priority as if it already imposed product requirements.
  • Change trigger: reopen the row when the is amended, harmonised standards are published or withdrawn, common specifications are adopted or repealed, or the product design, production process, supplier input, or declared conformity route changes.
Recommended next step

Turn ESPR requirements into audit-ready product evidence

Use Sorena to map ESPR delegated-act requirements to technical documentation, supplier records, DPP fields, standards coverage, and authority response packs.

Section 2

2. Map performance and information requirements to proof

For every requirement, record whether the proof is a measured value, a calculation, a design feature, a document, a label disclosure, a DPP data element, a supplier declaration, or a process control. ESPR requires ecodesign requirements to be verifiable, including by direct checks of the product or by technical documentation.

Keep the evidence matrix neutral until the defines the product-specific details. The regulation identifies product aspects such as durability, repairability, substances of concern, energy and resource efficiency, recycled content, remanufacturing, recyclability, environmental impacts, carbon footprint, and waste generation, but it does not itself turn every aspect into a requirement for every product group.

  • Performance proof: record the product parameter, threshold or non-quantitative requirement, measurement or calculation method, sample or model tested, test report, result, margin, reviewer, and affected product model.
  • Information proof: record the required audience, delivery channel, language or accessibility need, label or manual text, DPP field, free-access website or application link, and version control for the disclosed information.
  • Substances proof: where an information requirement applies, capture substance name or code, product location, concentration or range, safe-use instructions, and end-of-life information; record any delegated-act threshold or exemption separately.
  • Design-change proof: link each requirement to product design, manufacturing, software or firmware, service information, repair data, spare-parts process, or packaging controls so later changes trigger reassessment.
Section 3

3. Build the technical documentation file

The manufacturer's evidence file should make the product's conformity assessable against the . Keep it model-specific where the declaration is model-specific, and preserve the link between requirement, method, result, and document version.

Importers and authorised representatives also need access to conformity documentation for their ESPR roles. If the changes the retention period or requires digital availability of parts of the technical documentation, reflect that in the evidence register.

  • Core file: product description and intended use, design and manufacturing drawings or schemes, explanations needed to understand operation, and the applicable requirements from the .
  • Standards file: list harmonised standards, common specifications, or other technical specifications applied in full or in part; where not applied, describe the alternative solution used to meet the requirement.
  • Results file: design calculations, examinations, measurements, conformity comparison against the delegated-act requirement, test reports, and copies of information supplied under Article 7.
  • Declaration file: EU declaration of conformity, CE marking or any alternative conformity marking rule, responsible signatory, applicable Union acts, notified-body certificate or approval decision where relevant, and retention owner.
Section 4

4. Substantiate supplier and supply-chain inputs

Supplier substantiation should be tied to the product parameters and information fields in the . Use supplier data to support, not replace, the manufacturer's conformity evidence.

Where a specifies Article 38 obligations, supply-chain actors must provide relevant information free of charge, allow manufacturer assessment when information is not provided, and enable notified bodies or competent authorities to verify the accuracy of relevant activity information.

  • Supplier request: identify the supplied material, component, service, process, or data element; cite the delegated-act requirement; request the data format, method, sampling basis, date, and supporting documents.
  • Supplier response: retain declarations, test reports, certificates, bills of material, material composition data, production-process data, traceability identifiers, and any stated limitations or exclusions.
  • Escalation path: if the supplier cannot provide information, record whether manufacturer assessment of documents or facilities is needed and who can approve use of the input while evidence is incomplete.
  • Verification link: mark supplier data that may need verification by a notified body, competent national authority, market surveillance authority, or internal quality audit.
Section 5

5. Map evidence to the digital product passport

Treat DPP mapping as a requirement-by-requirement exercise. The applicable decides the data to include, the carrier, placement, model/batch/item level, access rights, update rights, availability period, and how the passport is accessible before sale, including distance selling.

Separate evidence used to prove conformity from data intended for passport access. Some compliance documentation may be included in the DPP under Annex III, but only the applicable tells the team which fields are required for that product group.

  • DPP scope: record whether the passport is at model, batch, or item level, and connect that level to the product identifier used in the technical documentation and declaration of conformity.
  • DPP access: identify which actors can access each data field, including customers, repairers, recyclers, market surveillance authorities, customs authorities, and other actors named in the .
  • DPP data quality: assign owners for accuracy, completeness, updates, authentication, integrity, privacy, and the back-up copy that Article 10(4) requires the placing operator to make available through a DPP service provider when a DPP applies.
  • DPP customs link: where the product is covered, retain the unique registration identifier and commodity code evidence needed for registry and customs checks once the relevant systems apply.
Section 6

6. Record standards, methods, and common specifications

The evidence checklist should show exactly which method was used for each requirement. ESPR allows tests, measurements, and calculations to use harmonised standards or other reliable, accurate, reproducible methods that reflect the generally recognised state of the art and satisfy the applicable .

Presumption of conformity depends on coverage. A standard, EU Ecolabel criterion, or common specification supports only the requirements it actually covers; keep a coverage note rather than treating a standard reference as blanket compliance.

  • Method field: requirement, method source, version, scope covered, lab or calculation owner, sample basis, uncertainty or assumptions, and evidence artifact.
  • Harmonised standard field: OJEU reference status, standard parts applied, requirements covered, requirements not covered, and fallback method for uncovered requirements.
  • Common specification field: implementing act reference, reason it applies, requirements covered, and removal plan if a harmonised standard later replaces the common specification.
  • Standards watch: monitor CEN and CENELEC ecodesign and DPP standardisation activity, including material efficiency and DPP framework work, without treating non-mandatory guidance as a legal requirement.
Section 7

7. Prepare market surveillance and corrective-action evidence

Close the checklist with the records an authority can ask for. ESPR gives market surveillance authorities routes to request conformity information, evaluate products presenting a risk, require corrective action, restrict products, withdraw or recall them, and act on formal non-compliance such as missing CE marking, missing or incorrect declaration, or incomplete technical documentation.

Keep enforcement evidence factual. Member States set their own penalty rules. They must make at least fines and time-limited exclusion from public procurement procedures available, but the ESPR does not set one Union-wide fine amount.

  • Authority request pack: technical documentation, EU declaration of conformity, DPP access evidence, product identifiers, economic-operator contacts, supplier traceability, quantities and exact models supplied, and response owner.
  • Distance-selling pack: manufacturer name and contact, EU responsible economic operator where needed, product picture, type, and other identifiers shown clearly and visibly in the product offer.
  • Corrective-action pack: suspected non-compliance, affected markets, affected models, root cause, authority notifications, withdrawal or recall decision, corrective action, retest or reassessment evidence, and closure approval.
  • Formal non-compliance pack: CE marking status, notified-body number where required, declaration completeness, technical documentation completeness, manufacturer/importer information, and any administrative requirement from the .
Section 8

How was this checklist prepared and reviewed?

Sorena AI mapped the checklist to Regulation (EU) 2024/1781, especially Articles 4 to 15, 27 to 30, 36, 38 to 45, 66 to 74, Annex III, and Annex IV. The regulation and an applicable are the binding sources. European Commission explanations and CEN-CENELEC material help interpret the implementation setting but do not create a product-specific threshold, evidence method, or deadline on their own.

AI assisted with source comparison, drafting, and organisation. No named human legal or conformity-assessment reviewer is claimed. Before releasing an evidence pack, confirm the adopted and its application date, amendments, transitional provisions, conformity route, and the current status and coverage of every cited harmonised standard or common specification. Source review current as of 24 July 2026.

  • Legal or product compliance confirms scope and the binding requirement source.
  • Engineering, laboratories, suppliers, quality, and sustainability owners supply the controlled evidence behind each row.
  • The manufacturer remains responsible for conformity; supplier declarations and non-binding guidance do not replace the manufacturer's assessment.
  • Reopen the checklist when the product, production process, supplier input, software or firmware, method, standard, or changes.
Primary sources

References and citations

single-market-economy.ec.europa.eu
Referenced sections
  • Commission news explains the DPP as an ESPR mechanism to store and share sustainability, durability, environmental, instruction, and conformity information with consumers, businesses, and public authorities.
"store and share relevant data"
commission.europa.eu
Referenced sections
  • Commission overview listing the types of ESPR ecodesign rules, including durability, reparability, resource efficiency, substances affecting circularity, recycled content, footprints, waste, and product sustainability information.
"performance and information rules"
data.europa.eu
Referenced sections
  • Binding source used for every legal checklist item, actor duty, evidence expectation, and enforcement consequence on this page.
"This Regulation shall be binding in its entirety"
Related guides

Explore more topics

ESPR and DPP connection: delegated acts, identifiers, and access
How ESPR connects ecodesign information requirements to Digital Product Passports, including delegated acts, data carriers, identifiers, access rights, registry, and architecture choices.
ESPR Applicability Test for Products and DPP Readiness
A cited ESPR applicability test for physical product scope, exclusions, delegated-act dependency, economic operator triage, DPP readiness, unsold goods, and evidence.
ESPR compliance checklist for delegated acts and DPP readiness
A cited ESPR checklist for monitoring delegated acts, mapping product requirements, preparing technical documentation, and building DPP and unsold-goods evidence.
ESPR compliance program operating model
Build an ESPR operating model for product-group intake, delegated-act monitoring, supplier evidence, DPP governance, release gates, and authority response.
ESPR compliance: delegated acts, DPP and evidence
Practical ESPR compliance guidance for mapping product delegated acts, Digital Product Passport dependencies, unsold goods duties, technical documentation, standards, and market-surveillance evidence.
ESPR deadlines and compliance calendar
Cited ESPR calendar for framework dates, delegated-act dependency, working-plan monitoring, unsold-goods disclosure, and DPP readiness limits.
ESPR delegated act intake by product group
A product-group intake checklist for ESPR delegated acts, covering product identification, DPP data, ecodesign requirements, conformity evidence, transition dates, and source limits.
ESPR delegated act intake workflow
A source-based intake workflow for ESPR delegated acts: trigger checks, product-group scope, requirement extraction, DPP impacts, release gates, owners, and evidence outputs.
ESPR delegated acts FAQ: product rules, DPP impact, and monitoring
Standalone FAQ on ESPR delegated acts, why product-group duties depend on them, what teams should monitor, and how they shape Digital Product Passport information.
ESPR delegated acts watchlist for product and DPP teams
Track the adopted ESPR 2025-2030 working plan, indicative delegated-act years, product scope, DPP dependencies, evidence owners, and unresolved legal details.
ESPR destruction ban and unsold goods FAQ
What ESPR says about preventing destruction of unsold consumer products, annual disclosure, the Annex VII apparel and footwear ban, and cited derogation evidence.
ESPR destruction of unsold goods: disclosure, ban scope, and records
Cited ESPR guide to unsold consumer product disclosure, destruction-ban scope, records, derogations, and national enforcement limits.
ESPR DPP information mapping workflow
Map ESPR delegated-act information requirements into DPP data elements, source systems, access levels, identifiers, carriers, validation evidence, and unresolved design decisions.
ESPR durability, repairability, and recyclability evidence
Build ESPR evidence for durability, repairability, and recyclability without inventing product-group tests before the applicable delegated act is known.
ESPR ecodesign requirement types: performance, information, and DPP links
Official source guide to ESPR ecodesign requirement types, product parameters, delegated-act dependency, DPP links, and evidence implications.
ESPR FAQ: scope, delegated acts, DPP, unsold goods
Standalone ESPR FAQ answers on product scope, delegated acts, Digital Product Passports, unsold goods, product priorities, standards, surveillance, and source limits.
ESPR harmonised standards and common specifications
How ESPR uses harmonised standards, common specifications, and the six DPP standards cited in Decision (EU) 2026/1736.
ESPR Information Requirements to DPP Mapping
Map ESPR information requirements into Digital Product Passport data classes, source systems, access rules, carrier choices, validation checks, and evidence records.
ESPR Information Requirements, Labels, and Disclosure
Source-cited ESPR guide to delegated-act information requirements, product labels, digital product passport access, data carriers, and unsold-goods disclosure.
ESPR market surveillance FAQ: evidence, DPP data, and authority requests
Standalone FAQ on ESPR market surveillance: technical documentation, conformity evidence, DPP data, authority response, delegated-act limits, and national penalties.
ESPR market surveillance technical documentation checklist
Source-cited ESPR checklist for technical documentation, conformity evidence, DPP records, and responses to market surveillance authority requests.
ESPR penalties and fines: Member State rules and evidence
ESPR penalties guide explaining Article 74, why fine amounts depend on Member State law, and which conformity and market-surveillance records matter.
ESPR Product Priorities and Delegated Acts Tracker
Track the ESPR 2025-2030 product priorities, indicative adoption years, delegated-act status, DPP dependencies, owners, and evidence.
ESPR product priorities FAQ: working plan and delegated acts
Standalone FAQ on ESPR product priorities, the Commission working plan, delegated-act dependency, monitoring points, and limits of preliminary source material.
ESPR requirements: delegated acts, ecodesign, DPP, and evidence
ESPR requirements explained as a framework for delegated acts, ecodesign performance and information rules, Digital Product Passports, unsold goods, technical documentation, and market surveillance.
ESPR Timeline: Fixed Dates and Delegated-Act Phasing
A cited ESPR timeline separating fixed framework milestones from product-specific application dates, DPP readiness, unsold-goods duties, surveillance, and evaluation.
ESPR unsold goods disclosure FAQ
Standalone FAQ on the ESPR Article 24 duty to disclose discarded unsold consumer products, its relationship to the destruction ban, records, and source limits.
ESPR unsold goods disclosure tracker
Track ESPR unsold-product disclosures under Regulation (EU) 2026/2 and destruction-ban derogations under Regulation (EU) 2026/296.
ESPR vs Batteries Regulation Comparison
Compare ESPR delegated-act planning with the Batteries Regulation product-specific regime, including DPP overlap, battery passport evidence, timing limits, and source boundaries.
ESPR vs Ecodesign Directive
Compare ESPR with the earlier Ecodesign Directive across scope, legal form, delegated acts, DPP requirements, unsold goods, transition rules, and evidence.
ESPR vs GPSR: Sustainability vs Product Safety
A scope-bounded comparison of ESPR sustainability and product-information requirements against GPSR product-safety context, with evidence and DPP reuse limits.
ESPR vs PPWR Comparison
Compare ESPR product ecodesign and Digital Product Passport duties with PPWR packaging design, labelling, conformity, producer-responsibility, and waste obligations.
ESPR vs REACH and RoHS Comparison
Compare ESPR ecodesign, sustainability, information, and digital product passport requirements with separately sourced REACH and RoHS substance-control context.
EU ESPR DPP obligations FAQ
Standalone FAQ on Digital Product Passport obligations under ESPR, covering delegated acts, identifiers, carriers, access rights, data governance, and supplier evidence limits.
What ESPR is and why it matters
An official source explainer of the EU Ecodesign for Sustainable Products Regulation, including scope, delegated acts, DPPs, unsold goods, and enforcement limits.
Which products are in scope of the EU ESPR?
Standalone FAQ on ESPR product scope, excluded products, delegated-act dependency, working-plan monitoring, and the digital product passport link.