PLD software and AI exposure checker

Software product liability readiness

Screen standalone software, embedded software, and AI systems for the revised liability rules.

Saved answers stay inside these labels: kind_band, service_band, commercial_band, foss_band, movement_band, timing_band, role_band, base_band, found_band, soft_band, update_band, learn_band, integrate_band, safety_band, modified_band, control_band, purpose_band, hazard_band, risk_band, foresaw_band, version_band, design_band, change_band, test_band, defect_band, file_band, trace_band, keep_band, owner_band, handling_band, stock_band, date_band, map_band, digital_band, evidence_band, nation_band, plan_band

What kind of digital product is this?Can the product be updated or upgraded?Can behaviour change through machine learning?Is there a commercial activity?Is the software integrated into another product?Does it have a safety-related function?

What this checks

This screen is liability readiness only. It asks whether commercial software or an AI system, including a product with updates or learning behaviour, needs a digital-product review or an update and change review. It does not repeat AI Act duties or CRA lifecycle rules. A non-commercial setting is not treated as an exclusion; that narrow open-source rule lives on the scope checker.

Who should use this

Product and software teams separating liability readiness from AI Act and machinery safety work.

How results work

Updates or learning behaviour open an update and change review. A complete commercial product without those signals can be likely in scope. Anything unknown stays in review.

Dates used in this screen

Member States must transpose Directive (EU) 2024/2853 by 2026-12-09. The new liability framework is for products placed on the market or put into service after 2026-12-08. Earlier products remain with the previous framework. National transposition is not filled in here.

Official sources

Use the current text of Directive (EU) 2024/2853, the 2026 corrigendum, the Commission pages on defective-product liability, and national transposition information when it is published. The older product liability directive remains the prior framework.

Limitations

Safety-related functions and product integration stay a digital-product review. They do not become an AI Act classification.

How to read the screen

Start with known facts

Record whether the software stands alone, is embedded, or is an AI system.

Leave gaps open

Mark updates, learning, commercial distribution, integration, and safety functions separately.

Readiness is not a judgment

Use the related AI Act and CRA tools when the question is compliance, not liability readiness.

Questions

Does an update change the result?

Yes. Update, upgrade, or learning behaviour moves a complete commercial product into an update and change review.

Is non-commercial software out of scope here?

No. This screen sends it to a digital-product review. The narrow exclusion is only on the scope checker when every fact is known.

Does this store documents or names?

No. Only the selected categories and the ruleset version can be saved.

Where do national rules fit?

If implementation in a Member State matters and is not verified, the result stays a national-law check. No national date is invented.