Product Liability Across the Product Lifecycle

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

Liability research does not stop at sale

A product's history can matter before supply, during use and after later changes. Product liability research therefore follows the lifecycle rather than relying on a single sales date or a final inspection. The relevant questions include what was designed, what was actually manufactured, how the product reached its market, which software and services were involved, who controlled later changes and what condition existed when the alleged damage occurred.

This is an evidence framework, not a statement that every lifecycle activity creates liability. The product liability fundamentals still require scope, defectiveness, covered damage and causation to be assessed. A lifecycle chronology helps connect those elements to facts. It also prevents a current product configuration from being mistaken for the configuration that existed months or years earlier.

Design and development records

Design documentation can explain intended functions, safety assumptions and foreseeable interactions. For software, relevant records may include architecture, dependency selection and safety tests for a release. For physical products, drawings, material specifications and tolerance decisions may help describe an alleged mechanism. These materials should be linked to the actual revision under investigation rather than treated as a generic company-wide safety file.

A development decision may matter differently under a fault-based claim and a product-based defectiveness analysis. Following an internal approval process does not automatically prove that the resulting product was safe, and a missing form does not automatically establish causation. Preserve the underlying technical reasoning and the version of the product it concerns, so the legal inquiry can use the record for the proposition it actually supports.

Manufacturing and market placement

Manufacturing records can distinguish a design shared across a range from a batch-specific or unit-specific deviation. Serial numbers, component revisions and test results help locate the affected product in that history. Market records then establish how and when it was first made available in the Union. Article 4 distinguishes making available, placing on the market and putting into service; these definitions should not be replaced by a casual reference to launch day.

The corrected Article 2(1) of Directive 2024/2853 concerns products placed on the market or put into service after 8 December 2026. The Article 22 transposition deadline is 9 December 2026. These dates serve different purposes. A later retail sale or incident does not by itself show that the relevant product was first placed on the market under the new framework.

Installation, configuration and use

Installation can change the relationship between the supplied product and its operating environment. Preserve instructions, installer records, settings, connected equipment and the acceptance state. A product that depends on another device or digital service may behave differently across configurations. Article 7 includes reasonably foreseeable use and relevant interaction with other products among the circumstances informing defectiveness.

User conduct should be recorded factually. An investigator needs to know what happened before deciding whether it was foreseeable, contrary to instructions or relevant to the harm. Keep the instructions as supplied and record whether a later version changed the guidance. A warning written after the event should not silently become evidence of what a user was told at installation.

Updates and continuing manufacturer control

Connected products and software can change after initial supply. Article 4 defines manufacturer control through specified actions, authorisation, consent and the ability to supply updates or upgrades. Article 7 considers relevant timing and continuing control. Article 11(2) limits certain post-supply exemptions where defectiveness concerns software, related services, necessary safety updates or substantial modification within that control.

Record the release deployed, the approval route, rollout timing and installation outcome. A published update is not proof that a particular device received it. Nor does the mere technical possibility of using a third-party component settle whether the manufacturer authorised it. Version and control records provide the factual bridge between original supply and the product state at the incident.

Repair, modification and investigation

A repair, refurbishment or substantial modification may raise different legal questions. Article 8 addresses persons who substantially modify outside manufacturer control and subsequently make the product available or put it into service. Do not call every maintenance activity a new product, or assume that calling work a repair prevents a substantial-modification analysis. Record what function, purpose and risk actually changed and who authorised the work.

After an incident, preserve the relevant states and a sourced chronology before testing or replacement changes the evidence. The investigation checklist helps connect lifecycle records to defect, damage and causation questions. Limitation and expiry under Articles 16 and 17 require separate legal review: manufacturing, supply, control, harm and discovery dates are related evidence points, not interchangeable clocks with one universal deadline.

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.

Design, manufacturing, supply and first-use chronology
Version, update, repair and modification history
Evidence of who authorised or controlled each safety-relevant change

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.