- Standards-body source used to identify relevant standardisation activity; it is not itself a product-specific legal requirement.
"develop technical standards"
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.
Structured answer sets in this page tree.
Cited legal and guidance references.
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.
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.
Use Sorena to map ESPR delegated-act requirements to technical documentation, supplier records, DPP fields, standards coverage, and authority response packs.
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.
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.
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.
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.
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.
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.
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.
"develop technical standards"
"store and share relevant data"
"performance and information rules"
"This Regulation shall be binding in its entirety"