Product Liability Investigation Checklist

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

Begin with safety and preservation

A product liability investigation checklist should organise questions, not produce a liability score. Start with immediate safety and lawful preservation. Do not continue operating a potentially dangerous product merely to reproduce a symptom. Avoid destructive testing before a suitable examination plan exists. Record the condition as found, who has custody and what actions were taken to reduce risks or prevent further damage.

The product liability fundamentals connect product scope, defectiveness, damage, causation and responsibility. Use those as separate evidence categories. A folder full of documents is less useful than a record showing which question each document can answer. Mark uncertainties explicitly, including whether a record concerns the exact affected unit, a comparable unit or only a general product family.

Identify the product and incident-time state

Record model, batch, serial number, supply route and identifying photographs. For digital products, record software releases, dependencies, configuration and relevant deployment information. For a connected product, identify hardware, embedded software and any services needed for its functions. Preserve the incident-time state before a repair, rollback or update changes it, where this can be done safely and lawfully.

Do not assume that the currently advertised specification describes an older product. Instructions, warnings and marketing can change. Preserve the version supplied with the product and identify later revisions separately. If an inspection uses a substitute product, document why it is comparable and what differences may limit the result. These details help prevent an apparently precise technical finding from being applied to the wrong configuration.

Establish the legal and temporal scope

Record the countries connected to the parties, acquisition, marketing and damage. Keep court-jurisdiction questions separate from applicable-law questions. For EU Directive research, the corrected Article 2(1) concerns products placed on the market or put into service after 8 December 2026. National transposition is due by 9 December 2026. Those dates do not by themselves establish an individual Member State's current operative law.

Locate the applicable national legislation and its commencement and transition rules. Record first market placement, first use where relevant, modifications, the incident and discovery of harm separately. Articles 16 and 17 address limitation and expiry, but a checklist cannot calculate a case deadline. Missing dates should be flagged for prompt jurisdiction-specific review rather than filled with estimates that look authoritative.

State the alleged defect and damage separately

Describe the unsafe condition in technical and factual terms. Identify the safety expectation or requirement said to be relevant, the operating conditions and the evidence supporting the allegation. Keep observed symptoms separate from explanations. An overheating report, a test result and a conclusion about a defective design are different entries, even when they concern the same product.

Then record the harm. Article 6 contains categories and exclusions, so identify personal injury, property damage and data destruction or corruption separately. Record ownership and actual use where professional-use exclusions may matter. Damage to the defective item itself should not be silently combined with unrelated property damage. Keep supporting financial or medical records in an appropriately restricted location rather than placing personal information in a general research tool.

Reconstruct causation and alternatives

Create a chronology with sources for each event. Distinguish contemporaneous records from later recollections. Examine how the alleged defect could have produced the particular harm and what alternative mechanisms remain possible. Installation, external events, later changes and evidence destruction can all affect what can responsibly be concluded. An event after an update is a lead to examine, not proof that the update caused it.

The explanation of what must be proven in a claim separates the three core elements from conditional presumptions. If evidential assistance is being considered, record the exact legal route and its factual conditions. A technical complexity argument, for example, should not be used as a general substitute for identifying the alleged product defect or the damage involved.

Map actors and preserve a reviewable trail

Identify manufacturers, component suppliers, importers and other potentially relevant operators by their actual conduct. Record who integrated components, approved updates and controlled changes. Contracts help establish facts, but their labels do not settle statutory roles. For missing material, identify the holder, the issue it may answer and the lawful process for obtaining it. Article 9 disclosure is subject to court control and safeguards.

Use the Record Mapper to organise a browser-local checklist without uploading evidence. Keep originals secure, document copies and access, and preserve the reason for any necessary alteration. The final research record should show established facts, disputed allegations, competing explanations and unresolved legal questions. Its value lies in making the investigation reviewable, rather than presenting preparation as a finding of defect, compensation or responsibility.

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 and version identity with a sourced chronology
Evidence matrix for defect, damage and causation
Custody, preservation, access and missing-record log

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.