Intended operation does not necessarily mean safe operation
Yes. A product can work as designed and still fail to provide expected or legally required safety. Article 7 of Directive (EU) 2024/2853 examines safety in all the circumstances, including design and technical characteristics. It does not ask only whether the product follows its specification. A heating device may generate heat exactly as intended while exposing accessible surfaces to a risk that requires separate safety assessment.
The defectiveness framework therefore distinguishes function from safety. A product's ability to complete its main task can be relevant evidence, but it is not a universal answer to a safety allegation. Conversely, a product that fails to perform a promised function is not necessarily defective for product liability purposes. The alleged shortfall needs a safety dimension and, for compensation, a connection to covered harm.
Specifications describe choices, not their legal adequacy
A specification can establish how a product was meant to behave. It may define output, operating limits, materials, control logic and protective measures. Evidence that the supplied unit conformed to those choices helps distinguish a production departure from a design-level allegation. It does not establish that every choice provided the safety people were entitled to expect.
The discussion of design defects addresses that distinction. An unsafe condition can be common to all units following a specification. For example, the alleged concern might be the absence of a safeguard rather than a failed component. Identify the safety function and the relevant circumstances before treating conformity to drawings as decisive. The technical record should show what the design does and what risk that creates.
A feature may create risk through ordinary use
Examine the relationship between intended behaviour and the operating environment. A moving mechanism may perform its task accurately while creating a foreseeable entrapment risk. A connected control may execute valid commands while failing to handle a predictable loss of communication safely. These examples identify questions for analysis; they do not establish that any particular product or design is legally defective.
The relevant evidence includes foreseeable use, product presentation, instructions, intended-user needs and foreseeable interaction with other products. Article 7 expressly includes those matters. A narrow demonstration that the main function operates correctly may omit the very circumstances in which the alleged safety shortfall appears. Tests should therefore state which scenario they examine and which safety conclusions their method supports.
Performance failures can also be safety failures
Some products have the very purpose of preventing damage. Article 7(2)(i) requires their failure to fulfil that purpose to be considered. An alarm that powers on and displays a normal status may still raise a safety question if it cannot provide the warning on which users reasonably rely. Its visible signs of operation do not necessarily establish the performance of its protective function.
Equally, a failed protective function needs careful investigation. Identify the condition the product was intended to detect or prevent, its actual state and the circumstances in which it allegedly failed. A protective device may have limits relevant to the event. The assessment should establish those limits and the communicated expectations rather than assuming either unlimited protection or complete immunity whenever a limitation exists.
Compliance and warnings do not supply universal answers
Compliance with a particular requirement or successful completion of a test can support the assessment. Its significance depends on the relevant hazard and configuration. Article 7 still calls for all circumstances to be considered. A report addressing electrical insulation, for example, does not necessarily resolve an allegation involving mechanical access to moving parts. The evidence must answer the question actually raised.
Warnings also need context. An instruction can shape expected use and communicate residual risks without necessarily resolving a design-level safety shortfall. Assess its clarity, availability and practicality together with the design. Do not assume that a statement saying a product behaves as designed establishes that users were entitled to expect no further protection against foreseeable hazards.
Liability still requires the other elements
A product can be defective while functioning as specified without that fact alone establishing a particular claim. Article 10(1) separately requires defectiveness, damage and a causal link, subject to specified presumptions. The investigation must connect the alleged unsafe characteristic to the incident rather than only show that the design could create danger under some circumstances.
Preserve product identity, incident-time configuration, observations and alternative explanations. A component damaged by an external event may look like a failure of the product's own safety system. A design capable of causing harm may not have been the cause in the event examined. Stating these distinctions makes a supported safety concern more precise and avoids overstating technical findings.
How to frame the conclusion
A useful account says which function worked, which safety protection allegedly fell short and why that difference matters. Identify whether the product conformed to the applicable design revision and whether the allegation concerns that revision itself. Avoid using working or broken as substitutes for a description of the relevant behaviour. Safety often depends on interactions that neither word captures.
Article 7(3) also prevents a finding based solely on the existence of a better product, update or upgrade. Independent evidence of unsafe design remains a different matter. Applicable national implementation and scope must be checked before evaluating a dispute. The central distinction is durable: successful operation establishes something about performance, while defectiveness requires a reasoned assessment of safety.
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.