Machinery Regulation vs EU AI Act Where machinery safety and AI compliance overlap
Classify the AI system under AI Act Article 6(1), but apply Regulation (EU) 2026/1744 before assigning duties. The amendment moves Machinery Regulation products to a sectoral route instead of applying most AI Act high-risk duties directly.
The Machinery Regulation applies from 20 January 2027. Regulation (EU) 2026/1744 entered into force on 27 July 2026 and requires machinery-specific AI health and safety requirements to apply through Machinery Regulation delegated acts by 2 August 2028.
Start with two classifications. Under AI Act Article 6(1), an AI system is high-risk through the product-safety route only when it is a of a covered product, or is itself that product, and the product must undergo third-party conformity assessment. Then apply the compliance route now in force. Regulation (EU) 2026/1744, the , moves Regulation (EU) 2023/1230 to the AI Act's sectoral track: machinery products remain classified under Article 6(1), but most high-risk requirements are to be reflected in Machinery Regulation Annex III through Commission delegated acts rather than applied directly under the AI Act. The amendment entered into force on 27 July 2026.
Side-by-side comparison
Machinery Regulation vs EU AI Act: supported overlap for machinery teams
This comparison stays within the machinery source support: use it when AI or machine-learning behaviour is part of a machinery safety function, software, cyber-safety control, or technical-documentation record.
Product-safety regime for machinery, related products and partly completed machinery. The file is built around EHSRs, risk assessment, conformity assessment, technical documentation, instructions, declarations and market-ready evidence.
Second framework
EU AI Act
AI-system classification regime. Under the adopted Digital Omnibus, Machinery Regulation products move to a sectoral track: Article 6(1) classification remains relevant, while corresponding health and safety requirements are added and assessed under the Machinery Regulation.
Machinery Regulation vs EU AI Act: supported overlap for machinery teams
Start with the product: machinery, related product, partly completed machinery, , or embedded system. Software can be part of the machinery analysis when it is a safety component or needed to verify EHSR compliance.
Apply the AI Act's own AI-system definition and scope. For Article 6(1), ask whether the AI is a or product covered by Annex I legislation and whether the product must undergo third-party conformity assessment. For Machinery Regulation products, apply the sectoral route in force under Regulation (EU) 2026/1744.
Use one intake record with separate conclusions for the machinery product, the AI system, the safety-component function, the conformity route, and the legal-status date. A failed Article 6(1) test is not a complete AI Act exclusion because another AI Act provision may still apply.
Machinery Regulation Annex I Part A includes safety components and embedded systems with fully or partially self-evolving behaviour using machine-learning approaches to ensure safety functions. Article 25 requires a conformity route involving a notified body for Part A categories.
AI Act Article 6(1) classifies an AI system as high-risk only when both its safety-component or product condition and the product's third-party conformity-assessment condition are met. The adopted Digital Omnibus does not remove that classification test for machinery.
Escalate Annex I Part A machine-learning safety functions early because the machinery conformity route can satisfy the second AI Act gate. Record the exact product category, route, and applicable Digital Omnibus status instead of assuming every AI-enabled machine has the same duties.
The machinery file must show applicable EHSRs, risk analysis, design and operation evidence, conformity assessment, technical documentation, instructions and declarations. Where relevant, source code or programming logic may be needed for authorities to check EHSR compliance.
AI classification and sectoral machinery work may use the same evidence only if the same system boundary, model version, safety function, control, and requirement are identified.
Create a cross-reference table. Each row should identify the document, product version, AI-system boundary, safety function, legal requirement, applicable delegated act or standard, and open gap.
Machinery sources identify cyber-safety provisions for safety control systems and compliance-related software and data, plus protection against corruption and reasonably foreseeable malicious attacks where they affect safety.
The AI Act classification record should not be used as the sole cyber-safety record. Cyber and software evidence must show how current and future machinery safety requirements are met.
Keep software architecture, update controls, logging, data-recording design, malicious-attack assumptions, and validation tests in the machinery evidence set. Link each record to the applicable Annex III requirement, delegated requirement, or standard.
Machinery conformity planning depends heavily on harmonised standards and the gap analysis against Regulation (EU) 2023/1230 EHSRs.
The machinery standardisation request context says machinery standards should take account of AI Act standardisation work where relevant. The adopted sectoral route makes that coordination part of the machinery implementation path.
When relying on a standard, document the Machinery Regulation requirement and any AI-derived delegated requirement it supports. A standard citation does not replace the product classification or legal-status assessment.
The Machinery Regulation's main provisions apply from 20 January 2027. Earlier dates apply to specified institutional and transitional provisions, not to the full manufacturer regime.
The AI Act generally applies from 2 August 2026. Regulation (EU) 2026/1744 entered into force on 27 July 2026, sets 2 August 2028 for high-risk systems embedded in products, and requires machinery-specific delegated requirements to apply by that date.
Use a status-controlled timeline: Machinery Regulation duties start on 20 January 2027, while the machinery AI sectoral requirements apply by 2 August 2028.
Under the Machinery Regulation, enforcement starts with whether the product falls in scope and whether the technical file shows compliance with the relevant EHSRs and conformity route.
Under the adopted sectoral route, authorities still need the Article 6(1) classification, but covered machinery AI health and safety duties are enforced through the Machinery Regulation requirements added by delegated acts.
Keep the enforcement record in one traceable chain: AI-system classification, machinery product scope, applicable Annex III and delegated requirements, conformity evidence, and corrective action.
The machinery file should be the master record for product scope, EHSR mapping, test evidence, instructions, declarations, and any source-code or programming-logic access needed for compliance checks.
The AI classification and delegated-requirement record can reuse machinery evidence only after it is labelled for the AI-system boundary, model version, safety function, and responsible economic operator.
Reuse evidence, not conclusions. If a record does not identify the product, AI system, version, requirement, and legal-status date, fix that traceability before relying on it.
If the product can be classified and assessed under the Machinery Regulation without any AI function analysis, stay in the machinery file first and document the EHSR route.
If the machinery contains an AI system, apply the AI Act screen. For the product-safety high-risk route, confirm both Article 6(1) conditions and then apply the Regulation (EU) 2026/1744 machinery sectoral route.
Use a three-step triage: decide the machinery scope and conformity route, classify the AI system, then record the law and delegated requirements in force on the relevant placement or putting-into-service date.
Supports AI-system scoping, Article 6 classification, and role-specific obligations.
Scope boundary
Machinery Regulation
Start with the product: machinery, related product, partly completed machinery, , or embedded system. Software can be part of the machinery analysis when it is a safety component or needed to verify EHSR compliance.
EU AI Act
Apply the AI Act's own AI-system definition and scope. For Article 6(1), ask whether the AI is a or product covered by Annex I legislation and whether the product must undergo third-party conformity assessment. For Machinery Regulation products, apply the sectoral route in force under Regulation (EU) 2026/1744.
Operational implication
Use one intake record with separate conclusions for the machinery product, the AI system, the safety-component function, the conformity route, and the legal-status date. A failed Article 6(1) test is not a complete AI Act exclusion because another AI Act provision may still apply.
Supports the AI-system scope screen and Article 6 high-risk classification rules.
High-risk product test
Machinery Regulation
Machinery Regulation Annex I Part A includes safety components and embedded systems with fully or partially self-evolving behaviour using machine-learning approaches to ensure safety functions. Article 25 requires a conformity route involving a notified body for Part A categories.
EU AI Act
AI Act Article 6(1) classifies an AI system as high-risk only when both its safety-component or product condition and the product's third-party conformity-assessment condition are met. The adopted Digital Omnibus does not remove that classification test for machinery.
Operational implication
Escalate Annex I Part A machine-learning safety functions early because the machinery conformity route can satisfy the second AI Act gate. Record the exact product category, route, and applicable Digital Omnibus status instead of assuming every AI-enabled machine has the same duties.
Article 6(1) supports the two-part high-risk test for AI used as a product safety component or as the product itself.
Trigger
Machinery Regulation
The machinery file must show applicable EHSRs, risk analysis, design and operation evidence, conformity assessment, technical documentation, instructions and declarations. Where relevant, source code or programming logic may be needed for authorities to check EHSR compliance.
EU AI Act
AI classification and sectoral machinery work may use the same evidence only if the same system boundary, model version, safety function, control, and requirement are identified.
Operational implication
Create a cross-reference table. Each row should identify the document, product version, AI-system boundary, safety function, legal requirement, applicable delegated act or standard, and open gap.
Supports the EHSR, technical-documentation, source-code and programming-logic evidence points.
technical documentation
Core obligations
Machinery Regulation
Machinery sources identify cyber-safety provisions for safety control systems and compliance-related software and data, plus protection against corruption and reasonably foreseeable malicious attacks where they affect safety.
EU AI Act
The AI Act classification record should not be used as the sole cyber-safety record. Cyber and software evidence must show how current and future machinery safety requirements are met.
Operational implication
Keep software architecture, update controls, logging, data-recording design, malicious-attack assumptions, and validation tests in the machinery evidence set. Link each record to the applicable Annex III requirement, delegated requirement, or standard.
Source for machinery cybersecurity aspects related to ISO 12100 risk assessment.
IT-security
Evidence record
Machinery Regulation
Machinery conformity planning depends heavily on harmonised standards and the gap analysis against Regulation (EU) 2023/1230 EHSRs.
EU AI Act
The machinery standardisation request context says machinery standards should take account of AI Act standardisation work where relevant. The adopted sectoral route makes that coordination part of the machinery implementation path.
Operational implication
When relying on a standard, document the Machinery Regulation requirement and any AI-derived delegated requirement it supports. A standard citation does not replace the product classification or legal-status assessment.
Commission machinery sector source for harmonised standards and implementation context.
machinery
Timing and deadlines
Machinery Regulation
The Machinery Regulation's main provisions apply from 20 January 2027. Earlier dates apply to specified institutional and transitional provisions, not to the full manufacturer regime.
EU AI Act
The AI Act generally applies from 2 August 2026. Regulation (EU) 2026/1744 entered into force on 27 July 2026, sets 2 August 2028 for high-risk systems embedded in products, and requires machinery-specific delegated requirements to apply by that date.
Operational implication
Use a status-controlled timeline: Machinery Regulation duties start on 20 January 2027, while the machinery AI sectoral requirements apply by 2 August 2028.
Binding source for the 2 August 2028 embedded-product date and the machinery sectoral route.
Enforcement
Machinery Regulation
Under the Machinery Regulation, enforcement starts with whether the product falls in scope and whether the technical file shows compliance with the relevant EHSRs and conformity route.
EU AI Act
Under the adopted sectoral route, authorities still need the Article 6(1) classification, but covered machinery AI health and safety duties are enforced through the Machinery Regulation requirements added by delegated acts.
Operational implication
Keep the enforcement record in one traceable chain: AI-system classification, machinery product scope, applicable Annex III and delegated requirements, conformity evidence, and corrective action.
Used for the separate AI Act reference identified in the machinery standardisation source support.
artificial intelligence
Overlap and reuse
Machinery Regulation
The machinery file should be the master record for product scope, EHSR mapping, test evidence, instructions, declarations, and any source-code or programming-logic access needed for compliance checks.
EU AI Act
The AI classification and delegated-requirement record can reuse machinery evidence only after it is labelled for the AI-system boundary, model version, safety function, and responsible economic operator.
Operational implication
Reuse evidence, not conclusions. If a record does not identify the product, AI system, version, requirement, and legal-status date, fix that traceability before relying on it.
Used for the separate AI Act reference identified in the machinery standardisation source support.
artificial intelligence
Practical decision rule
Machinery Regulation
If the product can be classified and assessed under the Machinery Regulation without any AI function analysis, stay in the machinery file first and document the EHSR route.
EU AI Act
If the machinery contains an AI system, apply the AI Act screen. For the product-safety high-risk route, confirm both Article 6(1) conditions and then apply the Regulation (EU) 2026/1744 machinery sectoral route.
Operational implication
Use a three-step triage: decide the machinery scope and conformity route, classify the AI system, then record the law and delegated requirements in force on the relevant placement or putting-into-service date.
Supports AI-system scoping, Article 6 classification, and role-specific obligations.
Practical decision rule
How to decide what to do next
If machine-learning behaviour ensures a safety function, apply the Machinery Regulation route and the AI Act Article 6(1) classification test, including the third-party conformity-assessment condition.
If the issue is software, source code, programming logic, data recording, malicious attacks, or protection against corruption, first ask whether it affects EHSR compliance and the machinery technical file.
If a harmonised standard is being used, check whether it supports Regulation (EU) 2023/1230 EHSRs and any AI-derived delegated requirement that applies to the product.
If the only claim is a generic AI feature with no machinery safety function, do not force it into the machinery sectoral route; complete the AI Act assessment on its own terms.
Supports the machinery sectoral route and the Machinery Regulation delegated-act mechanism.
1
Section 1
Classify the machinery product and AI safety function
Regulation (EU) 2023/1230 defines safety components broadly enough to include physical or digital components, including software, when they are designed or intended to fulfil a safety function and their failure or malfunction can endanger persons. It also identifies Annex I Part A categories for safety components, or embedded systems, with fully or partially self-evolving behaviour using machine-learning approaches to ensure safety functions.
For the AI Act product-safety classification, a safety function is only the first gate. Article 6(1) also requires third-party conformity assessment under the listed product law. Machinery Regulation Annex I Part A places safety components and embedded systems with fully or partially self-evolving machine-learning behaviour that ensure safety functions on a route involving a notified body. Under the adopted Digital Omnibus, that classification remains relevant, but the compliance requirements for covered machinery move into the Machinery Regulation through delegated acts.
Start with the machinery boundary: machinery, related product, partly completed machinery, , or embedded system.
For AI Act Article 6(1), document both the safety-component or product test and the third-party conformity-assessment test.
Record the legal-status checkpoint as well as the classification: Regulation (EU) 2026/1744 entered into force on 27 July 2026, so follow the machinery sectoral route and the delegated requirements adopted under Regulation (EU) 2023/1230.
Defines machinery scope, safety components including software, Annex III EHSRs, technical documentation, conformity assessment, and source-code or programming-logic access where relevant.
Binding amending regulation moving Regulation (EU) 2023/1230 to the AI Act sectoral track and requiring machinery-specific AI health and safety requirements through Machinery Regulation delegated acts.
Official adoption notice confirming the machinery exemption from direct AI Act applicability, the sectoral delegated-act route, and the 2 August 2028 embedded-product date.
2
Section 2
Evidence overlap to plan, not merge
The Machinery Regulation file should remain based on risk assessment against the essential health and safety requirements (EHSRs) and the resulting conformity evidence. For AI-enabled safety functions, useful shared records include the safety function description, machine-learning system boundary, foreseeable evolution in the machinery lifecycle, validation and test records, data-recording design, supervisory-function assumptions, cyber-safety analysis, and the standards or technical specifications used.
The same evidence should also identify the AI-system boundary, model version, data lifecycle, safety function, and requirement it supports. The adopted sectoral route reduces duplicate legal files, but it does not make unlabelled evidence reusable across different products, models, functions, or versions.
Keep the EHSR matrix, risk assessment, technical documentation, instructions, EU declaration, and conformity-assessment route in the machinery file.
Link AI-related evidence to the specific safety function: human-machine interface (HMI) adaptation, control-system behaviour, data recording, reliability, and protection against reasonably foreseeable malicious attacks where those points are relevant.
Record gaps where harmonised standards, common specifications, the current AI Act, or future Machinery Regulation delegated requirements need a different control, test, owner, or system boundary.
Supports the machinery evidence set: EHSRs, technical documentation, conformity assessment, instructions, declarations, and source-code or programming-logic access where needed to verify EHSR compliance.
Source for cybersecurity considerations related to ISO 12100 and machinery risk assessment.
machinery manufacturers
Recommended next step
Build the machinery AI evidence map
Classify the AI system, record the Digital Omnibus status, and tag each risk assessment, test, standard, software, cyber-safety, and technical-documentation record to the machinery requirement it supports.
The machinery standardisation material is important because harmonised standards cited in the Official Journal are the practical route to presumption of conformity under EU product law. The Machinery Regulation sources describe a gap-analysis effort for existing machinery standards and a Commission standardisation request to CEN and CENELEC for Regulation (EU) 2023/1230.
For AI and cyber topics, the standardisation request context points to coordination rather than substitution: machinery standards should take account of work under the AI Act and product-cybersecurity legislation where machinery products are also covered, so manufacturers can avoid duplicated work while still meeting each applicable act.
Amended Machinery Regulation Article 20(10) provides an interim standards route. Until machinery harmonised standards or common specifications for high-risk AI systems are referenced or adopted under Article 20, compliance with relevant harmonised standards referenced under AI Act Article 40, or common specifications adopted under Article 41, gives a presumption of conformity with the Machinery Regulation Annex III requirements for high-risk AI systems. Record the exact reference and the requirements it covers; a draft standard alone does not establish that presumption.
Check whether the machinery standard used has been assessed against Regulation (EU) 2023/1230 EHSRs, not only the old Machinery Directive.
Track whether AI-enabled safety-function evidence is covered by a cited harmonised standard, a common specification, or another technical specification.
Treat the standards bridge as an implementation aid; it does not remove the need for separate legal scoping under the AI Act.
Binding Machinery Regulation source for scope, safety components including software, Annex III EHSRs, technical documentation, conformity assessment, instructions, declarations, and source-code or programming-logic access where relevant.
Defines machinery scope, safety components including software, Annex III EHSRs, technical documentation, conformity assessment, and source-code or programming-logic access where relevant.
Supports the machinery evidence set: EHSRs, technical documentation, conformity assessment, instructions, declarations, and source-code or programming-logic access where needed to verify EHSR compliance.
Show 7 more
Supports the machinery scope boundary and the definition of safety components, including software.
Supports the Annex I Part A machine-learning safety-function categories and conformity-assessment implications.
Supports the EHSR, technical-documentation, source-code and programming-logic evidence points.
Supports software, source-code, programming-logic and safety-control evidence where relevant to EHSR compliance.
Supports the Machinery Regulation scope, product-safety evidence boundary, and 20 January 2027 application date.
Supports the machinery scope boundary and the requirement to show compliance through the technical file and conformity assessment.
Supports the Machinery Regulation decision gates for EHSRs, technical documentation, conformity assessment and safety components.
Binding amending regulation moving Machinery Regulation products to the AI Act sectoral track and requiring corresponding machinery AI health and safety requirements through delegated acts applying by 2 August 2028.
Binding amending regulation moving Regulation (EU) 2023/1230 to the AI Act sectoral track and requiring machinery-specific AI health and safety requirements through Machinery Regulation delegated acts.
Binding source for the 2 August 2028 embedded-product date and the machinery sectoral route.
Show 1 more
Supports the machinery sectoral route and the Machinery Regulation delegated-act mechanism.
Official adoption source for the machinery sectoral route and delayed embedded-product date.
Official adoption notice confirming the machinery exemption from direct AI Act applicability, the sectoral delegated-act route, and the 2 August 2028 embedded-product date.