Reading the ESPR Working Plan

Regulation (EU) 2024/1781 does not itself require a passport for any specific product. It creates the framework and empowers the Commission to bring product groups into scope through delegated acts.

The working plan is how the Commission signals which groups it intends to address and roughly when. For anybody planning a programme it is the most useful document available, provided its status is understood correctly.

What the working plan is and is not

The distinction matters because teams routinely treat the working plan as either binding or irrelevant, and it is neither.

The third row is where planning should focus once a group is named. A draft delegated act contains the attribute list, and although it changes during consultation, it changes far less than teams hope. Waiting for adoption before starting work wastes the most useful preparation window available.

How groups get prioritised

The criteria are set out in the regulation, and understanding them lets you estimate where your products sit without waiting to be named.

• Environmental impact — the total footprint of the group across the EU, not per unit.
• Improvement potential — how much difference requirements could plausibly make.
• Volume placed on the market — a high-impact niche product ranks below a moderate-impact ubiquitous one.
• Existing measures — whether a group is already regulated adequately by other instruments.

The second criterion explains apparent anomalies. A product group with a large footprint but little scope for improvement ranks below one with a smaller footprint where design changes could achieve a great deal.

Horizontal requirements reach further

The regulation permits requirements that apply across product groups rather than to one, and this is the mechanism most often overlooked in planning.

A horizontal requirement on, say, reparability or recycled content could apply to a wide set of products whose specific group has no delegated act. Concluding that your products are out of scope because your group is not named misreads how the framework can operate.

How to read it for your own planning

The practical question is what to do with the information, and the answer differs depending on where your products sit.

The last position catches the most organisations by surprise. A component supplier to a named product group faces the requirement through customer demands long before any obligation attaches to them directly, and customer deadlines are usually tighter than regulatory ones.

The eighteen-month reality

A delegated act typically applies eighteen months after adoption. That sounds generous and is not, for reasons that become obvious once a programme starts.

Most of that period is consumed by supplier data collection, which runs at the pace of contract renewals and supplier capability rather than at the pace of your project plan. A supplier asked for substance data at homogeneous material level for the first time will take months to respond, and some will not respond at all.

This is why the preparation that matters most is independent of the specific attribute list. Establishing which internal system is authoritative for each kind of data, and opening the supplier conversation, are useful whatever the delegated act eventually requires.

What to do regardless of position

A short list of preparations holds value across almost every plausible delegated act, which makes them safe investments before any obligation is confirmed.

Establish product identity and a resolvable identifier scheme. Build a material-level bill of materials. Map which internal system owns which attribute. Open the substance and footprint conversation with suppliers. None of these depends on the final attribute list, and all of them are on the critical path whatever it says.

The common objection is that this commits budget before an obligation exists. The counter is that every one of these items has independent value — a material-level bill of materials serves packaging reporting and producer responsibility fees today, and attribute ownership mapping resolves data disputes that already cost time.