Begin with a specific safety allegation
Product defectiveness is assessed by comparing the safety provided by the product with the safety people are entitled to expect or that the law requires. Article 7 of Directive (EU) 2024/2853 makes this a contextual inquiry. The allegation should identify a safety shortfall, not merely say the product was poor quality or failed to perform. A charger that supplies power but exposes accessible parts to dangerous current raises a different question from one that charges slowly.
The defectiveness framework brings those circumstances together. An assessment then narrows them to the product and risk in question. State what protection was expected, what allegedly went wrong and which records support that account. Avoid making the incident itself the complete explanation. Injury can be real even when the responsible mechanism remains unresolved, and an unsafe condition can exist without having caused the damage under investigation.
Identify the product as it existed
Start with model, serial number, batch, hardware revision, software version and component configuration where relevant. Record the source for each identifier. A label photograph and a software log may describe different aspects of the same product; neither should be substituted for the other. Accessories and connected products can also affect safety, so preserve the combination rather than documenting only the principal device.
Timing belongs in the identity record. Distinguish manufacture, placing on the market, putting into service, installation, maintenance and incident dates. Article 7 also takes account of when the product left manufacturer control where that control continued after initial supply. These are not automatically identical dates. An invoice may help establish purchase but does not necessarily establish first market placement or the timing of a software change.
Gather the circumstances that affect expectations
Article 7 identifies presentation and characteristics, instructions, foreseeable use, later learning or new features, foreseeable interaction with other products, relevant timing, safety requirements, safety interventions, intended user needs and failure of a damage-prevention purpose. The assessment should explain their relevance rather than merely copy the list. For a protective alarm, failure to warn may be central. For a household appliance, cleaning instructions and accessible hot surfaces may matter more.
Presentation can raise or shape expectations, but the inquiry is objective rather than controlled by one purchaser's private assumptions. Recital 30 describes expectations of the public at large. Identify the product category and intended users, including particular needs that are reasonably relevant to safe operation. Advertising, packaging and instructions should be reviewed together because a prominent message can conflict with a qualification buried elsewhere.
Build a technical explanation that can be tested
Describe the proposed mechanism in steps. For an alleged overheating defect, distinguish generation of heat, failure of control, ignition and spread to damaged property. Different records answer different steps. A melted enclosure may show severe heat without proving whether the heat originated inside the product. Preserve possible external causes and explain why evidence supports or weakens them.
A useful comparison considers design intent, manufacturing condition and incident-time behaviour. The account of manufacturing defects explains why conformity to a drawing differs from safety under that drawing. Tests should identify their sample, method, limitations and assumptions. A report about a new exemplar may illuminate the design while failing to reproduce deterioration or configuration present in the affected unit.
Apply evidence rules without enlarging them
Article 10(1) starts with proof of defectiveness, damage and a causal link. Article 10 then supplies specific rebuttable presumptions. Failure by the defendant to disclose relevant evidence pursuant to Article 9(1) is one route to presuming defectiveness. Demonstrated breach of mandatory safety requirements protecting against the risk of the actual damage is another. Demonstrated damage caused by an obvious malfunction during foreseeable use or ordinary circumstances is a third.
Those routes are not an instruction to presume liability whenever information is missing, regulation is mentioned or a malfunction is alleged. Each has conditions. Article 10(3) separately addresses a causal-link presumption where defectiveness is established and the damage is typically consistent with the defect. Article 10(4) addresses excessive proof difficulties and demonstrated likelihood. Article 10(5) allows the defendant to rebut the presumptions.
Record a reasoned outcome and its limits
An assessment should identify what is established, disputed or unknown. Explain the evidence supporting the safety shortfall and how it relates to the product state. If a recall is relevant, match its scope; if compliance is relied on, state which hazard and requirement it addresses. A newer model is not enough by itself to establish that the earlier product was defective under Article 7(3).
Keep the legal conclusion proportional to the evidence. A technical report may establish a hazardous failure mode without identifying the legally responsible actor. A safety finding may justify corrective action without resolving compensation. National implementing law, scope and procedure still need checking before a particular dispute is assessed. The finished record should make those remaining questions visible rather than conceal them behind a single word such as defective. Preserve the source and date of each assessment so later readers can distinguish contemporaneous findings from conclusions reached after additional evidence became available.
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.
- Incident-time product identity and configuration
- Source documents and dated safety analysis
- Separate defect, damage and causation 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.
- Directive (EU) 2024/2853, consolidated text: Articles 7, 10 ↗
- Official Journal corrigendum, 7 May 2026: Article 2(1) ↗
Source register: corrected scope verified 16 October 2026. Article references identify the legal basis. No qualified legal review or national implementation status is claimed.