TransitionEU

EU Machinery Regulation (EU) 2023/1230 Timeline and Transition

A migration playbook to 14 January 2027.

Focus: portfolio classification, route planning, evidence modernization, and notified body readiness.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 21, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 21, 2026

Overview

Transition is not just a legal-reference update. Regulation (EU) 2023/1230 changes route selection, software evidence, digital-document controls, and the meaning of substantial modification. The corrigendum also matters because it fixes the operative dates. This page gives you a product-family migration plan that matches the law and the real execution work.

Section 1

1) Timeline snapshot with the corrected dates

Use these dates as the top row of the portfolio migration tracker.

14 June 2023 adopted, 29 June 2023 published, and 19 July 2023 entered into force.
14 January 2024: Articles 26 to 42 started to apply.
20 July 2024: Article 6(2) to (6), (8) and (11), Article 47, and Article 53(3) started to apply.
14 July 2025: Member State Article 6 data reporting deadline.
20 July 2026: Commission Article 6 report deadline.
14 January 2027: main application date and repeal of Directive 2006/42/EC.

Recommended next step

Turn EU Machinery Regulation (EU) 2023/1230 Timeline and Transition into an operational assessment

Assessment Autopilot can take EU Machinery Regulation (EU) 2023/1230 Timeline and Transition from planning deadlines, owners, and milestones from this page to a reusable workflow inside Sorena. Teams working on EU Machinery Regulation (EU) 2023/1230 can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Assessment workflow

Open Assessment Autopilot for EU Machinery Regulation (EU) 2023/1230 Timeline and Transition

Start from EU Machinery Regulation (EU) 2023/1230 Timeline and Transition and turn the guidance into owned tasks, evidence requests, and review checkpoints.

Explore next step

Talk to Sorena

Talk through EU Machinery Regulation (EU) 2023/1230

Review your current process, evidence gaps, and next steps for EU Machinery Regulation (EU) 2023/1230 Timeline and Transition.

Explore next step

Section 2

2) Transition principle: migrate by product family, not by document

A family-based migration keeps route choice, risk assessment, software evidence, declarations, and instructions aligned. A document-only migration leaves contradictions in the shipped pack.

The output should be one decision record per family, not a loose collection of updated PDFs.

Inventory product variants, safety functions, embedded or downloadable software, connected services, and intended users.
Freeze a directive-era baseline pack before you start rewriting it for the Regulation.
Define migration acceptance criteria: route approved, technical file indexed, declarations updated, and digital access controls tested.

Section 3

3) Route discovery comes first

Do not wait for late-stage CE release to classify Annex I. Part A and Part B logic changes timelines, notified body use, and evidence depth.

The route decision memo should be versioned because it controls the rest of the program.

Check whether the family is machinery, a related product, or partly completed machinery.
Classify Annex I Part A, Annex I Part B, or not listed, and record the rationale and standards coverage assumptions.
For Part B families, document why Module A is or is not available based on full standards or common-specification coverage of the relevant EHSR.

Section 4

4) Modernize the evidence system, not just the technical file headings

Annex IV requires a retrievable evidence system. That includes software logic on reasoned request where needed, plus sensor-system descriptions and validation records in the relevant cases.

If the evidence cannot be exported quickly, the technical file is not operational.

Map each applicable Annex III requirement to the hazard log, protective measure, test evidence, and owner.
Separate engineering evidence, software-integrity evidence, and declaration artifacts, but keep them tied by a common index.
Add document-access and version-retrieval tests to the migration exit criteria.

Section 5

5) Digital instructions, declarations, and legacy support

Digital delivery is allowed in defined situations, but the access conditions are strict enough that teams should treat them as product requirements.

The transition plan should also include legacy products placed on the market before 14 January 2027.

Instructions in digital format must be printable, downloadable, and savable for use during breakdowns.
Users can ask for paper instructions free of charge within one month, and non-professional-use machinery must still include essential safety information in paper form.
For partly completed machinery, assembly instructions and the declaration of incorporation can be digital, but online access must remain available for 10 years.

Section 6

6) What done looks like

Mark a family migrated only when the workflow is stable, not merely when the wording is refreshed.

Scope memo, Annex I memo, and Article 25 route memo approved.
Annex III risk assessment updated for software, autonomy, and foreseeable misuse.
Annex IV evidence index complete and retrievable.
DoC or DoI, instructions, and digital access controls matched to the final configuration.
Substantial-modification triggers and software change controls are operating in production.

Primary sources