Skip to content
EU Machinery Regulation

A machine thatlearns is amachine thatwas never tested.

From 20 January 2027 the Machinery Directive is replaced by a Regulation, and the replacement says something the Directive could not: that a machine may arrive on site behaving one way and, months later, behave another. Self-evolving behaviour, safety software and cybersecurity enter machinery law for the first time.
Applies from
20 January 2027
Replaces
Directive 2006/42/EC
Form
Regulation, directly applicable
New ground
Autonomy, software, cyber
What changed

A Directive became a Regulation, and the gap between twenty-seven laws closed.

The Machinery Directive had to be transposed by each Member State, which is why a machine compliant in one market could meet a different reading in another. A Regulation applies directly and identically across the Union. For a manufacturer that is one conformity story instead of twenty-seven, and for anyone underwriting the product it is one legal standard against which a failure is judged.

What it requires

Annex I, Part A

AI in a safety function means a notified body, not self-declaration

The high-risk list gained two categories written for machine learning: safety components with fully or partially self-evolving behaviour, and machinery with embedded AI systems performing safety functions. Part A machinery cannot be self-certified. The route to market runs through a third party.

Annex III

Software is a safety component

The essential health and safety requirements were extended to treat safety-related software as part of the machine rather than as something loaded onto it. A software update is a change to a safety component and is governed as one.

Annex III, 1.1.9

Protection against corruption

A machine that communicates, wirelessly or otherwise, must not be made hazardous by that communication, and its safety software must be protected against unintended and deliberate modification. Cybersecurity stopped being an IT concern and became an essential safety requirement.

Annex III

Every intervention in safety software is logged, and kept five years

The control system must record evidence of every intervention in the safety software, conscious or otherwise, and the logs must remain available for at least five years after modified software is uploaded. For the first time, what a machine's safety logic was on the day of an accident is a documented fact rather than a reconstruction.

The premise

Conformity is assessed on a machine that has not finished changing

Conformity assessment describes a machine at a moment. A system whose behaviour evolves is not the machine that was assessed, and the Regulation is the first to say so out loud. What follows from that — who answers for behaviour nobody specified — is the question the next decade of product liability turns on.

Source

Regulation (EU) 2023/1230 of the European Parliament and of the Council of 14 June 2023 on machinery and repealing Directive 2006/42/EC. References are to the Regulation and its Annexes as published in the Official Journal. Nothing on this page is legal advice, and conformity for a given machine is a question for a notified body and counsel, not for a website.
Technology

Underwriting isan informationproblem. We treatit as one.