EU Product Liability Directive Readiness Checklist

EU Directive-level explanationUpdated 16 October 2026By ProductLiability.help editorial desk

Define what readiness is intended to achieve

A readiness checklist for Directive (EU) 2024/2853 should help an organisation identify affected products, legal questions and evidence gaps. It is not a certification scheme or a guarantee that no liability will arise. The Directive does not prescribe one universal document bundle called a readiness file. The appropriate records depend on product functions, supply relationships, control and the issues that an incident could raise.

Begin with the Directive explanation and identify who owns the research. Separate product-safety operations from compensation analysis, while keeping their evidence connected. A completed spreadsheet is useful only if its entries are traceable to actual products, current legal sources and records that can be retrieved. Assign responsibility for correcting gaps rather than treating a checked box as proof of compliance.

Check scope and dates

Inventory the products actually supplied, including relevant software and digital elements. Identify the first market-placement or first-use evidence for each product group and the facts needed for product-specific investigation. The corrected Article 2(1) concerns products placed on the market or put into service after 8 December 2026. Article 22's transposition deadline is 9 December 2026. Keep those rules distinct.

Create a separate national-law research record where a country-specific assessment is needed. Include official adopted legislation, publication, commencement and transition provisions. A proposal, consultation or notification should be labelled accurately. Do not record a Member State as implemented merely because the EU deadline is approaching or because a professional summary describes expected legislation.

Map products, components and functions

Identify physical products, software, related services and significant components. Record how they interact and which functions depend on them. A vendor's marketing label may not answer the Article 4 classification question. For cloud-dependent products, distinguish software supply, a service needed for product functions and general infrastructure. Keep technical diagrams connected to contractual and actual supply records.

Check whether the current inventory describes the deployed product or only the latest planned release. Historical versions can matter after an incident. Preserve the identifiers needed to distinguish them, including firmware, configuration and component revisions. The overview of the Directive's changes explains why digital-product scope and continuing control make that historical picture important.

Identify operators and control

Record the legal entities performing the relevant manufacturing, integration, import and distribution activities. Include the manufacturer's location and the conditional EU actor routes in Article 8 where relevant. Do not assume that a contract heading or customer-facing brand fully identifies the statutory role. Own-brand supply and substantial modification may need particular analysis.

For updates and services, identify who can supply, approve, integrate or modify them. Preserve authorisation and consent records as well as technical permissions. The ability to supply updates can be relevant to manufacturer control. A practical map should distinguish a manufacturer's approved component from a third-party addition that is merely technically possible, rather than treating all compatibility as authorisation.

Make relevant evidence retrievable

Locate safety tests, instructions, design and production records, release history, incident logs and supplier information. Record retention arrangements and access responsibilities without inventing a universal retention period under this Directive. Preservation may be subject to national procedure and other legal requirements. The aim is to avoid losing the incident-time state while keeping collection lawful, proportionate and appropriately restricted.

Article 9 disclosure is court-controlled and contains safeguards. Article 10 presumptions have defined conditions and remain rebuttable. A readiness programme should understand those mechanisms without describing them as a blanket obligation to disclose every internal record on demand. Map documents to questions such as product condition, harm, causation and control so their relevance can be explained.

Test the workflow with a fictional incident

Document where the exercise failed: a missing supplier identifier, an overwritten log or uncertainty about who approved a release each calls for a different remedy. Assign a responsible person and a practical follow-up action. Repeat the exercise when a material change gives a reason to check the workflow again.

Use a scenario to check whether teams can identify the product, retrieve the correct version and reconstruct a change without overwriting evidence. Record competing explanations and the distinction between an observed failure and an unsafe defect. Confirm that personal injury, property damage and data loss would be classified separately, including the different professional-use exclusions in Article 6.

The Record Mapper can organise a browser-local checklist without receiving case documents. Keep actual evidence in suitable controlled systems. End the readiness review with owners, unresolved questions and dated sources, including national-law items requiring further work. Preparation improves the quality of a later investigation; it does not decide defectiveness, compensation, liability or a legal deadline in advance.

Records that help the review

Use the following as a practical starting point. Select and preserve records appropriate to the product, incident and applicable procedure.

Product, component, service and operator inventory
National-law status research with official sources
Version, approval, deployment, safety and incident records

Independent educational information at EU Directive level. National implementing law and procedure require separate review.

Primary sources and legal scope

This page explains the EU Directive framework. Check national implementing law, the corrected temporal scope and relevant procedure before applying it to a case.

Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.