ESPR Delegated Act Intake By Product Group

Start with the product as it is sold or put into service in the EU, then map it to the ESPR concepts that control later analysis. ESPR defines a product as a physical good placed on the market or put into service, and defines a product group as products serving similar purposes with similar use, functional properties, and consumer perception.

Do not assume that a broad product family is already regulated. The intake should separate the product group watchlist from the later delegated-act applicability decision.

Use watchlist status when the product group is only prioritised, under study, or mentioned in working-plan material. That status is useful for preparation, but it is not the same as a binding product obligation.

The Commission adopted the 2025-2030 working plan on 16 April 2025. It schedules work on final products including textiles and apparel, furniture, tyres and mattresses; intermediate products including iron and steel and aluminium; and horizontal repairability and recyclability requirements, while carrying forward energy-related product work. Record its indicative adoption dates as monitoring dates, not compliance dates.

When a delegated act is available, the intake record should become a clause-by-clause capture of what the act actually says. Article 8 lists the minimum content that delegated acts must specify, so use it as the review checklist.

The delegated act may also state that no performance requirement, no information requirement, or neither type is set for specific product parameters. Preserve that negative decision instead of filling the gap with a generic sustainability control.

A delegated act can require a digital product passport and must specify the product-group details rather than leaving teams to invent a generic DPP schema. The intake should capture the DPP level, data carrier, access rights, update actors, update process and availability period. It should also map applicable controls from the 2026 harmonised DPP standards and the registry registration arrangements without treating those horizontal instruments as product-field rules.

Article 7 also requires attention to substances of concern and other information for customers, repairers, treatment facilities, and sustainable product choices where relevant. Treat those as delegated-act data requirements, not as a universal public data dump.

After product scope and DPP fields are captured, classify the ecodesign requirement as a performance requirement, an information requirement, or both. ESPR requires delegated-act requirements to be relevant to the product group and verifiable.

Do not convert every Annex I parameter into a requirement. Use Annex I as the controlled vocabulary for product aspects and parameters, then mark only the ones selected in the delegated act.

Keep the evidence file small enough to audit: source, clause, product mapping, requirement mapping, owner, test or data source, approval, and next review trigger. If the delegated act is not yet adopted, store preparation evidence separately from compliance evidence.

The intake should never publish unsupported product-group dates, penalties, DPP fields, performance thresholds, or transition rules. If a claim is only supported by a preparatory report, consultation, standard, or project deliverable, label it as preparation or technical context rather than a binding ESPR obligation.