Documents connect the commercial chain to the technical facts
Supplier documentation can explain the identity, expected performance and authorised use of a component. In a product liability investigation, it is evidence to interpret rather than a collection of certificates that automatically establishes safety. A specification describes an agreed requirement; an inspection report describes an examination; an invoice describes a transaction. Each may be useful, but they answer different questions.
The component and supply-chain liability framework requires a connection between the supplied component, integration, alleged defect and damage. Documentation helps reconstruct that connection where several businesses designed, manufactured or handled the item. The starting point is a clear question: which fact needs establishing, and which document could reliably establish it? Collecting every available file without that structure can obscure the important gaps.
Establish provenance and revision before relying on content
Record the document's author, date, version, recipient and purpose. A supplier's draft specification can differ from the version approved for production. An unsigned template may show the expected inspection process without proving it was performed. A current website datasheet may contain revised operating limits that were not communicated when the affected component was supplied.
Preserve the native record and relevant attachments where practical, alongside an accessible reading copy. If an email refers to a drawing number, obtain the actual revision rather than assuming the latest drawing is the referenced one. Explain any uncertainty about authenticity or completeness. An attractive document title does not compensate for an unknown source or an inability to connect the record to the affected product.
Link each record to the actual component
Match supplier references to the manufacturer's internal part codes, batch numbers and finished-product identifiers. A certificate covering a broad product family may not cover the relevant revision or factory. Where several suppliers provide interchangeable parts under one internal code, record which source supplied the unit or batch under investigation. Do not let the procurement database silently erase that distinction.
Some links are indirect. A material certificate may identify a bulk batch later divided between assemblies. A software delivery record may identify an archive incorporated into several builds. Establish the transformation between the original supply and the installed component. The separate guide to component traceability in liability investigations explains how these links can be reconstructed and where a traceability gap limits the conclusion.
Separate commitments from measured performance
A specification or statement of conformity can explain what the supplier represented, but it does not prove every supplied item met the stated characteristics. Test and inspection records provide a different kind of evidence. Check whether they concern the actual item, a production sample or an earlier design. The distinction matters when the alleged defect is intermittent or limited to one production batch.
Conversely, a measured departure from a purchasing requirement does not automatically establish a legally defective product. Article 7 of Directive (EU) 2024/2853 requires assessment of the safety that a person is entitled to expect or that law requires, considering all circumstances. Explain whether the departure affected safety in the actual configuration. Commercial non-conformity and product defectiveness can overlap without being interchangeable conclusions.
Use instructions to reconstruct integration responsibility
Article 8's component provisions concern defective components integrated or interconnected within manufacturer control that caused the product to be defective. Approval records, installation instructions and interface correspondence can help establish how integration was authorised. They may show that the product manufacturer selected an operating range, requested a change or accepted a particular limitation. Record the exact scope of that approval.
Article 11(1)(f) also makes finished-product design and instructions relevant to a component manufacturer's claimed exemption. The question is whether the defectiveness is attributable to those matters, not merely whether an instruction document exists. Compare the instruction with the supplied component and failure mechanism. A supplier may have followed one instruction while departing from another, so a single approval signature rarely answers every causal question.
Read missing and inconsistent records carefully
A missing inspection sheet can justify further inquiry, but it does not invariably prove an inspection failed or a component was defective. The record may have been held by another actor, archived under another reference or never created. State which explanation is supported. Likewise, two inconsistent documents require comparison of their dates and roles before one is characterised as a correction or concealment.
Article 9 provides conditional court-controlled disclosure, subject to necessity, proportionality and confidentiality safeguards. Article 10 provides specified rebuttable presumptions, including consequences linked to failure to disclose relevant evidence under Article 9(1). Those provisions should not be reduced to a rule that any incomplete supplier file automatically proves liability. The procedural conditions and the relevance of the missing evidence remain important.
Produce a document account that another reader can follow
A useful evidence schedule identifies each material record, the fact it supports and any limitation. Keep the original source distinct from an investigator's summary. Record whether a statement comes from a contemporaneous production record, a later interview or an inference drawn from several sources. This helps prevent a reconstructed explanation from gradually being described as a directly observed fact.
Check chronology as well as content. The corrected Directive scope applies to products placed on the market or put into service after 8 December 2026. Supplier delivery, finished-product market and later update records can have different dates. The final account should show what documentation establishes about the relevant product and actors while leaving national law, covered damage and unproved causal links visible for separate assessment.
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.
- Supplier specifications with revision history
- Delivery and acceptance documents linked to batches
- Integration instructions and approval correspondence
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 2, 4, 7, 8, 9, 10, 11 ↗
- 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.