Document facts before drawing conclusions
Documenting an alleged product defect means preserving an intelligible record of the product, the safety concern and the event. Begin with safe handling. Do not continue operating a potentially dangerous item merely to reproduce a symptom. Avoid changing its condition through unnecessary repair, cleaning, resetting or disassembly before an appropriate examination plan exists. Record any action needed to reduce immediate risk and who performed it.
The defectiveness framework concerns expected or legally required safety in all the circumstances. A useful record therefore does more than photograph a broken item. It identifies the alleged safety shortfall and distinguishes it from ordinary performance disappointment. It also keeps defectiveness separate from damage and causation, because evidence supporting one question does not automatically establish the others.
Identify the exact product and configuration
Preserve model, serial number, batch, manufacturer markings and relevant component identifiers. Photograph labels in context as well as close up. For software or connected products, record installed versions, settings, accessories and connected services where available. State the source of each identifier. A purchase description or commercial model name may not identify the internal revision involved in the event.
Record acquisition, installation, maintenance and update history without treating them as interchangeable dates. An invoice may establish a purchase, while first placement on the market requires different evidence. Note whether a release was installed or merely offered. A later device screen or current online account may display a state that changed after the incident, so identify when each record was obtained.
Preserve the observed condition
Photograph or describe the condition as found before it is altered, where safe and lawful. Capture the surrounding environment and connected items relevant to the event. Do not rely only on close-up damage images that omit the product's location or configuration. Record date, photographer and any known timing limitations. Preserve original files and avoid replacing them with annotated or compressed copies alone.
Keep a handling and custody record. Note who possessed the product, how it was stored and whether it was moved, opened, repaired or tested. Changes may be necessary, but their effect should be visible. A later observer should be able to distinguish incident damage from marks introduced during transport or examination. Where that distinction cannot be made, state the limitation plainly.
Build a sourced chronology
Separate the event sequence from later analysis. Record what witnesses saw, heard or did, using their own descriptions where appropriate. A witness may know that an alarm sounded without knowing which system generated it. A log may show a timestamp without establishing that the clock was accurate. Preserve such limits rather than turning uncertain observations into precise technical facts.
Connect each significant entry to its source: photograph, message, service record, log or account. Note inconsistencies and missing periods. A chronology should help test competing explanations, not select only facts supporting a preferred theory. The interval between an unusual symptom, shutdown, damage discovery and later examination can be important to distinguishing the origin of a failure from its consequences.
State the safety allegation separately
Describe the protection expected and the alleged shortfall. For example, distinguish an overheated surface from the proposed failure of a temperature-control mechanism. The first may be observed directly; the second may require technical evidence. Identify which part of the explanation is established, inferred or unresolved. Avoid using the word defect as if it proves the mechanism it is meant to describe.
Preserve relevant instructions, warnings, product descriptions and safety documents for the affected version. If a recall is relevant, match its scope and reasons to the product. The explanation of recalls as evidence shows why a notice can be significant without proving every individual incident. Keep the original notice and amendments rather than relying on a second-hand description of its meaning.
Keep damage and causation records distinct
Document the harm separately from the product condition. Property photographs, relevant repair records and appropriate injury documentation can address damage, while physical examination or logs may address the alleged mechanism. A damaged product does not alone show which losses fall within the applicable liability regime. Equally, evidence of an injury does not establish which product condition caused it.
Article 10 of Directive (EU) 2024/2853 starts with proof of defectiveness, damage and the causal link, subject to specified rebuttable presumptions. Missing information, regulatory concern or an unexplained malfunction should not automatically be presented as satisfying those provisions. If a presumption may be relevant, identify its exact conditions and which evidence addresses them. Record contrary evidence and possible external causes as well.
Plan examination without overstating findings
A testing plan should identify its purpose, method, sample and potential effect on the evidence. Destructive examination can prevent later inspection of the original condition. Record authorisation and preserve appropriate documentation of each stage. A test on another unit should state why that unit is comparable and what differences may limit the result. An exemplar cannot automatically reproduce every feature of the affected product's history.
The resulting file should let another reviewer follow the evidence from product identity through observations to the proposed safety explanation. Keep a clear list of missing records and unanswered questions. Applicable national implementing legislation, procedure and scope still require checking before assessing an individual dispute. Good documentation supports investigation; it does not itself establish liability or predict a compensation outcome.
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.
- Original product identifiers, configuration and incident-time software versions
- Dated photographs and custody or handling log
- Sourced incident, maintenance and update chronology
- Separate matrices for safety allegation, damage and causal mechanism
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.