EU Product Liability: Keep Software Release Evidence

Connect the approved release, product supplied and later updates in a record reviewers can follow

Published

Blue-and-gold illustration with twelve EU stars connects a software release folder and heating controller, a consumer-unit supply record, and versioned update documents under a magnifying glass, labelled Release, Supply and Update.

A homeowner reports water damage after a home-heating controller receives a software update. The manufacturer needs to establish which software reached that unit, what changed later and which records support that account. A release approval and a planned rollout do not establish what was installed in the customer’s home.

Keep the approved release, actual supply and completed update history connected. Preserve the supporting decisions and source records so product, service, records and legal staff can review the same chronology. That chronology helps an investigation; it does not decide whether software caused the reported damage or who is liable.

Check the EU scope and the applicable national law

Directive (EU) 2024/2853 includes software in its product definition. Article 2, as corrected by the May 2026 corrigendum, covers products placed on the market or put into service after December 8, 2026. Member States must transpose the directive by December 9, 2026. Check the national implementing law and the facts of the supply.

The regime concerns qualifying damage suffered by natural persons; it does not cover every business property loss. The directive excludes free and open-source software developed or supplied outside commercial activity. Article 9 addresses disclosure of relevant evidence in national court proceedings, subject to conditions including the claimant’s plausibility threshold, necessity, proportionality and protection of confidential information and trade secrets. The legal team determines what applies to the matter and how any disclosure must proceed. A prepared records set is not a public release of technical files.

Distinguish what was approved from what reached the unit

Give a release a stable reference that connects its approved test evidence, release decision, applicable hardware and instructions. Keep the reference to the exact build in the system that owns the software artifact. Capture the documents and identifiers needed to find that evidence later without relying on a folder called “latest”.

Then connect the supplied product or installation to the release it actually received. An approved fleet rollout, a scheduled service visit and a completed update are different records. Retain the source of each fact and its recorded time. A later device check can support what was observed then; it does not by itself establish the version present during an earlier event.

Practical records to connect for a software-containing consumer product; this is a records design, not a statutory document checklist.
RecordEvidence to connectQuestion it helps answer
Approved releaseExact build reference, release decision, test evidence and applicable hardware or instructions.What did the manufacturer approve for supply?
Actual supplyUnit or installation reference, supplied release and dated delivery or activation evidence.Which product and software reached this recipient?
Completed updatePrior and new release, service outcome and any dated device-version observation.What changed on this unit, and what remains uncertain?
Preservation and reviewAuthorised scope, captured source revisions, preservation results and decisions about review copies.Which records were retained, reviewed and released to an authorised recipient?

Keep the chronology useful across teams

  1. 1 · Connect

    Trace the specific unit

    Join release, supply and service records through stable references and their source evidence.

  2. 2 · Preserve

    Retain the authorised scope

    Apply the agreed records controls and track gaps or preservation failures with an owner.

  3. 3 · Review

    Prepare a controlled copy

    Let authorised staff inspect the evidence and record what may be shared through the applicable process.

A later summary should identify its author, preparation date and supporting sources. Keep it distinguishable from the contemporaneous release decision or service record. Where sources disagree, record the discrepancy and assigned investigation rather than replacing the earlier account with an unexplained reconstruction.

Worked example: a heating controller’s update history

Fictional product, records and dates; no conclusion about defect, causation or liability. Unit C-204 is a home-heating controller supplied to a consumer in the EU in January 2027. In June, the homeowner reports water damage. The manufacturer opens an investigation and asks its records team to assemble the release and service evidence for authorised review.

  1. Identify the approved release

    The records file connects C-204’s product variant to release R7, its exact build reference, test report, release decision and operating instructions. The original approval documents remain distinguishable from the investigation’s later summary.

  2. Confirm what was supplied

    The January supply record identifies C-204 and R7. A product-line rollout notice alone is not used to establish this unit’s version. Customer details remain in the restricted customer record, linked by a reference where reviewers need them.

  3. Separate the planned and completed update

    A service order scheduled R8 for May 20. Its completion record instead identifies June 12 and the change from R7 to R8 on C-204. A dated support check on June 13 also records R8. Those sources establish the documented sequence before the June 18 damage report; they do not establish that the update caused it.

  4. Preserve the agreed evidence

    The authorised owner defines the review and preservation scope. Records staff capture the relevant source documents and revisions, apply the agreed document retention and hold controls, and verify the results. A missing service attachment remains an assigned exception. Records still held in the source release or service system remain that system’s preservation responsibility under the agreed plan.

  5. Prepare the authorised review set

    The legal team reviews the chronology, source inventory and gaps. Staff prepare the approved copy with its source references, record the intended recipient and sharing decision, and retain the controlled originals. If C-205 lacks a completion record, the reviewer records that uncertainty rather than assuming the same rollout history as C-204.

Plan retention and access for the evidence itself

The records owner sets the applicable schedule and preservation decisions with the legal team. A newer release should not silently remove the retained evidence for an earlier supplied product. The retention, legal hold and backup guide explains the different purposes of those controls. Confirm protection of the relevant documents and versions, including any scoped copies remaining in connected systems.

Product engineers, service providers, customer support and legal reviewers may need different views. Restrict technical detail, customer information and review correspondence according to the agreed department and partner boundaries. Verify access to search results, document versions, downloads and exported review copies. A record’s presence in the review inventory is not permission to share it with every participant.

For a separate reporting task, the CRA manufacturer-reporting guide follows awareness, staged notifications and reporting confirmations. Keep the purpose and authorisation of each records set clear even when both use the same underlying release evidence.

Checklist for a product-history review

  • Confirm the product, recipient, relevant supply facts and applicable national law with the responsible owner.
  • Connect the approved build and supporting documents to a stable release reference.
  • Verify what the specific unit received, separately from the planned rollout.
  • Retain completed update evidence and dated observations without filling gaps by assumption.
  • Check preservation results, source-system responsibilities and access to review copies.
  • Retrieve the chronology and source records together, with discrepancies and sharing decisions visible.

Sources checked

Make the supplied product’s history traceable

Connect the approved release to the actual supply and completed updates. Preserve the underlying records, keep uncertainty visible and prepare review copies under the agreed authority. That gives reviewers a chronology they can inspect alongside the source evidence.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call