ESPREvidenceEU

ESPR evidence for durability, repairability, and recyclability

This page helps structure evidence before and after an ESPR delegated act defines the exact product-group requirements.

Separate framework-level ESPR signals from binding product-specific requirements, test methods, supplier inputs, and DPP disclosures.

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

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

Do not apply one fixed durability, repairability, or recyclability test list to every product. ESPR identifies these as product aspects and lists possible evidence parameters, but an Article 4 decides which requirements, methods, thresholds, disclosures, and dates apply to a product group. Before that act is identified, prepare data and evidence structure without presenting planning assumptions as conformity criteria.

Section 1

Start with the delegated-act dependency

ESPR Article 4 empowers the Commission to set ecodesign requirements through delegated acts. A durability, repairability, or recyclability evidence file should first identify whether a covers the product group, which requirements it sets, and when those requirements apply.

Do not write product-group limits, scores, test methods, or pass/fail thresholds into the evidence model until the or an incorporated standard, common specification, transitional method, or reliable method supports them.

  • Record the product group and product description used for the delegated-act check.
  • Track whether the sets , information requirements, both, or no requirement for the relevant product parameter.
  • Capture the 's conformity assessment module, verification format, technical-documentation elements, and application timing instead of relying on a generic ESPR calendar.
  • Keep open issues explicit when a product group is only in policy planning or work-programme material and no binding requirement set is available.
Section 2

Separate performance evidence from information evidence

ESPR separates from information requirements. Performance evidence supports whether the product meets minimum, maximum, or non-quantitative requirements for parameters such as durability, repair and maintenance, and design for recycling. Information evidence supports what must be communicated to customers, treatment facilities, authorities, or other actors.

For this topic, the evidence model should map each claim to one of those tracks. A repairability score, durability score, end-of-life disassembly information, spare-part availability field, material-composition field, or recycling-capability disclosure may be an information requirement even when a separate performance limit also exists.

  • Durability evidence may cover guaranteed lifetime, technical lifetime, mean time between failures, real-use information, and resistance to stresses or ageing mechanisms when the uses those Annex I parameters.
  • Repairability evidence may cover spare-part availability, delivery time, affordability, modularity, compatibility with common tools, repair instructions, disassembly and re-assembly characteristics, and access to product data or needed hardware and software when the applicable rule calls for them.
  • Recyclability evidence may cover recyclable materials, safe access to recyclable or hazardous components, material composition and homogeneity, high-purity sorting, standard component or material coding, process complexity, and non-destructive disassembly. These are Annex I planning parameters, not automatic duties for every product.
  • Information evidence can include customer maintenance and repair information, treatment-facility disassembly and recycling information, and substance-of-concern tracking when those requirements apply.
Recommended next step

Turn ESPR evidence into a product data map

This ESPR evidence guide helps map delegated-act requirements, supplier inputs, technical documentation, and DPP disclosures before publishing product claims.

Section 3

Build the technical-documentation file around verification

The evidence file should show how each durability, repairability, or recyclability requirement can be verified. ESPR requires ecodesign requirements to be verifiable and allows verification by direct product checks or technical documentation. Article 39 then points tests, measurements, and calculations to harmonised standards or other reliable, accurate, and reproducible methods that meet the 's requirements.

For internal production control, Annex IV describes technical documentation that makes conformity assessable. For this page's subject matter, that means keeping the delegated-act requirement, applied standard or method, design and manufacturing records, calculations, measurement results, test reports, and the copy of information supplied under Article 7 together.

  • Requirement trace: article or annex, affected product parameter, and whether the obligation is performance, information, or both.
  • Method trace: harmonised standard, common specification, transitional method, or other reliable method used for the specific measurement, calculation, or examination.
  • Result trace: design calculations, examinations, measurements, conformity comparison, test report, and reviewer approval.
  • Disclosure trace: customer-facing, treatment-facility, website, manual, label, product, packaging, or DPP field that carries the required information.
Section 4

Treat supplier and value-chain data as controlled evidence

Many durability, repairability, and recyclability fields depend on upstream materials, components, software, spare parts, maintenance services, and end-of-life information. ESPR defines supply-chain and value-chain concepts and, when a specifies Article 38 obligations, supply chain actors must provide available relevant information free of charge, allow assessment where information is not provided, and enable verification by notified bodies and authorities.

Supplier evidence should therefore be requestable, versioned, and tied to the exact product, component, material, service, or facility it supports. It should not be converted into a public claim unless the evidence owner can show the requirement, method, data source, and allowed disclosure route.

  • Request component and material facts needed for repair, disassembly, substance tracking, and recycling evidence.
  • Record whether the supplier data is manufacturer-provided, supplier-declared, facility-derived, test-derived, or authority-verified.
  • Keep escalation steps for missing supplier data, including document or facility access where Article 38 is specified by the .
  • Protect confidential business information while preserving enough evidence for conformity assessment and market surveillance.
Section 5

Control test configuration and post-sale performance

Durability evidence must describe the marketed product, not a test-only configuration. Article 40 prohibits products designed to detect testing and improve the measured result, test instructions that manually alter performance for a better result, and designs that worsen regulated or functional performance shortly after the product enters service.

Software and firmware changes belong in the evidence file when they can affect a regulated product parameter or user-facing function. Article 40 permits worsening beyond margins set by the applicable only with the customer's explicit prior consent, and an update may never make the product non-compliant with the requirements that applied when it was placed on the market or put into service.

  • Record the hardware, software, firmware, settings, conditioning, sample selection, and test instructions used for each result.
  • Compare the tested configuration with the version placed on the market and explain every difference.
  • Assess updates against the same conformity method and any acceptable margins specified by the .
  • Keep consent evidence where an allowed update reduces performance, and block any update that would make the product non-compliant.
Section 7

How was this evidence guide prepared and reviewed?

Sorena AI mapped this guide to Regulation (EU) 2024/1781, especially Articles 4 to 10, 38 to 40, Annex I, and Annex IV, and checked the implementation framing against European Commission and CEN-CENELEC material. The regulation and an applicable are the binding sources. Commission explanations, standards-body material, and CIRPASS outputs provide implementation context but do not create product-specific conformity duties.

AI assisted with source comparison, drafting, and organisation. No named human legal or conformity-assessment reviewer is claimed. Before using the guide for a product, confirm the adopted , its application date and transitional provisions, the current harmonised-standard or common-specification status, and any later amendments. Source review current as of 24 July 2026.

  • Use the regulation and adopted to decide scope, duties, methods, evidence, and dates.
  • Use standards only for the requirements and versions they cover; a standard reference is not blanket proof of conformity.
  • Use Commission, CEN-CENELEC, and CIRPASS material as explanatory or implementation support and label assumptions that remain non-binding.
  • Reopen the evidence file after product, supplier, software, firmware, method, standard, or delegated-act changes.
Primary sources

References and citations

cirpassproject.eu
Referenced sections
  • CIRPASS source support identifies DPP implementation challenges around value-chain data quality, standards, and stakeholder collaboration.
"Digital Product Passport"
single-market-economy.ec.europa.eu
Referenced sections
  • Commission DPP consultation page describes the DPP as a way to store and share product sustainability, durability, and environmental information with consumers, businesses, and public authorities.
"sustainability, durability and other environmental aspects"
data.europa.eu
Referenced sections
  • Binding source used for the delegated-act dependency, product parameters, verification, DPP, supply-chain, testing, and technical-documentation rules.
"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 Ecodesign Evidence Checklist
Checklist for collecting ESPR ecodesign evidence from delegated acts, technical documentation, supplier substantiation, DPP mapping, standards, and market surveillance records.
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.