Information forms part of product safety
A product can raise a defectiveness question because its warnings or instructions do not provide the safety information reasonably needed for its use. Article 7(2)(a) of Directive (EU) 2024/2853 expressly includes labelling and instructions for assembly, installation, use and maintenance among the circumstances to assess. The question is not whether a manual is long or professionally presented, but whether the product provides expected or legally required safety in context.
The overall defectiveness test includes the product's physical and digital characteristics as well as its information. A warning is therefore one part of the assessment. Its presence does not automatically excuse an unsafe design, and its absence does not automatically establish liability. Identify the risk, the information allegedly needed and the connection between that information and the incident.
Identify the information actually supplied
Preserve the manual, label, packaging insert and relevant screen messages for the affected version. A current website may present revised instructions that were unavailable at purchase or at the time of the incident. Record issue dates, document numbers, language versions and how updates were delivered. Where possible, preserve the original rather than relying only on an unattributed screenshot.
Availability differs from existence. A technical file held by a manufacturer does not necessarily communicate a risk to a user. A warning encountered only after a hazardous step may arrive too late to affect behaviour. Installation, maintenance and ordinary operation may involve different people, so determine which person needed which information and when. Avoid assuming that whoever bought the product also installed or operated it.
Read the message in its setting
Content and prominence both matter to understanding. A warning may accurately name a hazard while using terminology its intended users cannot reasonably understand. A small qualification can also conflict with prominent claims elsewhere. Review the whole communication, including pictograms, controls, advertising and packaging. The discussion of product presentation explains how these elements can shape safety expectations together.
Instructions should be examined against the tasks they address. Assembly steps may matter to structural stability; cleaning instructions may affect electrical protection; maintenance intervals may affect a protective mechanism. Identify the precise alleged omission rather than criticising the document generally. A missing cosmetic-care recommendation is a different matter from an omitted instruction needed to avoid a foreseeable serious hazard.
Foreseeable use and intended users
The product's intended purpose provides context, but reasonably foreseeable use is an independent circumstance under Article 7. Labelling an action prohibited does not by itself establish that it was unforeseeable. Equally, a manufacturer need not be treated as having anticipated every imaginable intervention merely because a warning could theoretically have been written about it. The analysis needs an account of realistic behaviour and the risk involved.
The specific needs of the intended user group also matter. Information for a product aimed at children, older users or people with particular functional limitations should be assessed in that context. Do not infer that every user in a broad group has the same capabilities. Identify the relevant task and communication need, such as readability, comprehensibility or the ability to distinguish a safety signal from an ordinary status message.
Explain how information could affect the event
An information allegation should identify the causal pathway. What would adequate information have communicated, when would it have reached the relevant person and what action could it have supported? These are factual questions requiring evidence, not an automatic assumption that any additional warning would have prevented any injury. Witness accounts, supplied documents and the sequence of operations may be relevant.
The opposite assumption is also unsafe. Evidence that a person did not read one part of a manual does not necessarily settle the role of a label or missing on-screen warning. Different communication channels have different purposes. Describe what was seen, what was available and what remains uncertain. This allows a court or technical reviewer to distinguish communication shortcomings from unrelated causes.
Compliance and revisions have limited meanings
Mandatory labelling or instruction requirements can be relevant to defectiveness. For Article 10(2)(b)'s rebuttable presumption, the claimant must demonstrate non-compliance with mandatory product-safety requirements intended to protect against the risk of the damage suffered. A preferred style guide or an internal documentation policy is not automatically such a requirement. The exact provision, product scope and risk connection must be identified.
A later manual revision can provide useful evidence about what changed, but improvement alone does not prove the earlier product defective. Article 7(3) rejects defectiveness based solely on the availability of a better product, including updates or upgrades. Preserve the revision explanation and surrounding records rather than treating any new warning as an admission resolving all earlier incidents.
Keep information, defect and liability distinct
A complete review states the affected product version, the relevant hazard, the supplied information and the alleged shortfall. It also records how the information fits with design safeguards and realistic use. If translation or accessibility is disputed, preserve the actual language and format rather than relying on a summary of what the message was intended to say.
Article 10 still separates defectiveness, damage and causation, with specified evidential presumptions and a right of rebuttal. A deficient instruction may support a safety allegation without establishing the amount or category of harm. The applicable national implementation and procedure also require attention before an individual dispute is evaluated. The aim is a coherent explanation of the safety role of information, grounded in the actual product and event.
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.