ESPR standards and common specifications without overclaiming

ESPR is a framework regulation. For products regulated through Article 4, the delegated act supplies the concrete ecodesign requirements, DPP decision, methods, conformity-assessment procedure, and documentation expectations.

Build the standards register from the legal requirement outward: product group, delegated-act clause, technical requirement, cited harmonised standard or common specification, applied clauses, evidence, and any uncovered remainder.

Article 41 creates three distinct presumptions: for test, measurement, or calculation methods; for DPP compliance with Articles 10 and 11; and for product ecodesign requirements set by a delegated act. In each case the standard's reference must be published in the Official Journal.

The presumption reaches only the requirements covered by the cited standard or part. Record the standard version and clauses used, the corresponding legal requirement, exclusions or restrictions in the citation, and the route used for every uncovered requirement.

A common specification is not any industry specification with that label. Under Article 42, it is a technical solution established by a Commission implementing act for products covered by an Article 4 delegated act.

The Commission may use this route only after requesting a harmonised standard when the request was not accepted, the standard missed the deadline, or it did not comply with the request, and no suitable Official Journal reference exists or is expected within a reasonable period. If a later harmonised standard is cited for the same requirements, the Commission must repeal the overlapping common specification or part.

Commission Implementing Decision (EU) 2026/1736 took effect on 15 July 2026 and published the Official Journal references for six harmonised DPP standards. A DPP conforming to them receives the Article 41(2) presumption for the requirements in ESPR Articles 10 and 11 that those standards cover.

The decision does not decide which products need a DPP, the model, batch, or item level, the product data fields, access groups, carrier placement, or availability period. Those choices still come from the applicable product legislation.

Use a traceability table that lets a reviewer move from the delegated-act requirement to the cited harmonised standard or common specification, the applied clause, and the exact test, calculation, DPP control, or declaration reference.

If the team does not use a cited harmonised standard or common specification, or uses only part, the technical documentation must describe the alternative solutions adopted to meet the applicable requirements. The record should not claim a presumption for requirements outside the applied coverage.

Do not use a standard number to announce product scope, DPP fields, thresholds, penalties, application dates, or market restrictions. Those claims need the applicable legislation.

Record four statuses plainly: binding legal requirement, cited harmonised-standard route, Article 42 common specification, and other technical material. Only the middle two can create the ESPR presumptions described on this page.