Misuse is a description needing evidence
Product misuse can mean many different things: using an item for another purpose, ignoring an instruction, fitting an unsuitable part, altering a safety device or operating in an unusual environment. Those situations should not be collapsed into one legal conclusion. Under Directive (EU) 2024/2853, reasonably foreseeable use is relevant to defectiveness. Conduct described as misuse can therefore require analysis of whether it was realistically predictable and how it affected safety.
The product defectiveness framework asks whether expected or legally required safety was provided in all the circumstances. It does not establish a universal rule that any departure from a manual defeats liability. Nor does it say manufacturers must prevent every imaginable harmful action. The product, behaviour, safeguards and alleged damage must be identified before drawing conclusions about their relationship.
Describe the departure rather than naming it
Record the actual action: the accessory fitted, load applied, guard removed, setting selected or maintenance omitted. Identify the instruction or technical limit said to have been departed from and preserve its relevant version. Statements such as customer error or abnormal operation are hypotheses until linked to evidence. They can conceal important differences between a deliberate modification and a minor handling mistake.
Check who performed the action and when. An alteration may have occurred before acquisition, during servicing or after the incident. The present condition does not necessarily reveal the incident-time state. Photographs, maintenance records, configuration histories and witness accounts can help establish a chronology. Where timing is uncertain, state that uncertainty rather than assuming the alteration existed throughout the product's life.
Intended purpose and foreseeable behaviour
A product's intended use matters, but Article 7 also requires reasonably foreseeable use to be considered. Recital 46 explains this through intended use, ordinary use indicated by construction and lawful, readily predictable human behaviour. The foreseeable-use assessment therefore examines realistic behaviour rather than treating a manufacturer's chosen label as the complete test.
Warnings can be evidence that a risk was anticipated without resolving whether the overall safety was sufficient. Their content, visibility and practicality matter alongside design. At the same time, a behaviour being physically possible does not establish that it was reasonably foreseeable. Evidence of the product's presentation, common tasks and operating environment helps distinguish an ordinary risk scenario from an exceptional intervention.
Ask how the conduct affected safety
A departure from instructions may be irrelevant to the alleged failure. An unrelated cosmetic change, for example, does not necessarily explain an internal electrical fault. The technical account needs to show a mechanism connecting the conduct to the product's unsafe condition or the resulting damage. Identify the affected components, sequence and alternative explanations rather than relying on temporal coincidence.
Several causes can interact. An unsafe design might increase the consequences of a predictable mistake, or a substantial unauthorised modification might create a risk absent from the supplied product. These possibilities require different evidence. Separate what the product was originally designed to do, what was changed and what occurred in the incident. Do not assume that proof of one contribution erases all other contributions.
The injured person's conduct has a separate role
Article 13 distinguishes damage caused jointly by product defectiveness and a third party's act from damage involving the fault of the injured person or a person for whom that person is responsible. Under its second paragraph, liability may be reduced or disallowed where damage is caused both by product defectiveness and by that fault. This is not expressed as an automatic result whenever the word misuse appears.
Applying that provision requires the relevant conduct, fault and contribution to the damage to be considered under the applicable framework. The person operating the product may not be the injured person. The person responsible for a modification may be another business. Keep those identities distinct. An investigation that labels every user's action as the claimant's conduct can misstate both the facts and the legal question.
Presumptions do not remove the factual inquiry
The obvious-malfunction presumption in Article 10(2)(c) requires demonstrated damage caused by an obvious malfunction during reasonably foreseeable use or ordinary circumstances. Disagreement about use may therefore be important to that route. It does not follow that failure to use that particular presumption defeats every way of proving a defect. The ordinary proof rule and other specified presumptions remain separate questions.
Article 10 also preserves rebuttal. Records showing unusual configuration or intervention may bear on a proposed inference, but their significance needs explanation. A missing record is not proof of misuse, and an uncertain use history is not proof of safe design. A reasoned assessment states what the evidence supports and identifies where technical or factual questions remain unresolved.
Keep the conclusion proportionate
A useful misuse analysis identifies the behaviour, its foreseeability, its effect on safety and its alleged contribution to the damage. It should distinguish a disputed observation from an established fact and an engineering explanation from a legal conclusion. Preserve the actual instructions and relevant product state so another reviewer can assess the account independently.
National implementing law, applicable dates and procedure still require attention before an individual dispute can be evaluated. An educational explanation should not conclude that a particular person has lost a claim merely because an action departed from intended use. The relevant law asks more precise questions about defectiveness, causation, responsibility and, where applicable, the injured person's fault.
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, 13 ↗
- 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.