What Changes under the Machinery Regulation: A Product Team's Plan for 2027
Regulation (EU) 2023/1230 applies from 20 January 2027. Understand the changes in software safety, assessment routes, modifications, and instructions.
What should our machinery team prepare before 20 January 2027?
Identify which changes affect your product and turn the transition into assigned engineering and documentation work.
Picture a machine developed in 2026 and supplied in batches over the following year. Its enclosure is familiar. Its firmware keeps changing. A remote service connection has become part of the product because customers want faster support.
The calendar is about to matter to that machine. So are the software changes.
Regulation (EU) 2023/1230 applies from 20 January 2027, replacing Machinery Directive 2006/42/EC. For a product team, the transition is a reason to review the machine's behaviour, its assessment route, and the evidence behind the release. Changing the legal reference on a declaration is only one small part of that work. The European Commission's machinery page confirms the date and outlines the changes.
This article was reviewed on 8 October 2026. The examples are hypothetical. For the continuing end-to-end process, see the EU conformity assessment guide.
The date applies to products, not the start of your project
The regulation distinguishes placing on the market, meaning the first making available on the EU market, from putting into service, meaning first use for the intended purpose. Those definitions matter when planning the transition, including machinery made for a manufacturer's own use. Read Article 3.
A design begun under the directive does not give every future unit of that model permanent access to the old regime. Map the relevant dates and circumstances for the individual products you will supply or put into service. A project kickoff, purchase order, or completed design is not by itself proof of placing on the market.
Article 52 preserves the making available of products already placed on the market in conformity with the directive before 20 January 2027. It also provides that directive EC type-examination certificates and approval decisions remain valid until they expire. That does not remove the obligation to meet the regulation where it applies. Read Articles 51, 52, and 54.
The original published text contains incorrect application dates; use the corrected consolidated text linked here. The Commission explicitly notes the corrigendum in its machinery guidance.
For your plan, split the question into two tasks: establish the relevant market-entry or first-use event, then establish the requirements for that event. Keep the rationale with the product records.
Software and connections become explicit safety work
A remote support feature can look like an operational convenience. If it can alter safety-related parameters or software, it also belongs in the safety analysis.
Annex III includes protection against corruption in section 1.1.9 and updated requirements for control-system safety and reliability in section 1.2.1. The regulation also explicitly includes independently marketed digital components, including software, within its definition of safety components. Read Article 3(3) and Annex III.
The practical questions are specific. Which interfaces can influence safe operation? Who can change the relevant software or data? How will the team detect interference? What happens if an update fails? Which version was assessed, and what evidence supports that version?
Draw the connections alongside the physical machine. Include service tools, remote access, and update paths where they can affect safety. Then assign requirements and validation to the actual risks identified.
This work needs mechanical, controls, and software expertise together. A security review detached from the machine's behaviour can miss a dangerous consequence. A machinery review that treats software as an opaque box can miss how that consequence is introduced.
The machinery regulation addresses safety-related effects. It does not replace a separate applicability review of other legislation, including cybersecurity rules that may affect the product.
Evolving behaviour needs a lifecycle assessment
Consider a machine that adapts its behaviour after deployment. A demonstration of safe behaviour on the day of testing may leave unanswered questions about what happens after the system has changed.
The regulation's risk assessment provisions expressly address foreseeable hazards arising from intended evolution of fully or partially self-evolving behaviour or logic, for machinery designed to operate with varying levels of autonomy. Read Annex III, General Principles.
Identify what the product can change, what its allowed operating boundaries are, and how safety is preserved within those boundaries. Record the assumptions behind the assessment and the verification of protective behaviour.
Do not treat every software update as self-evolving behaviour. The point is to understand your particular architecture. A fixed control programme, an update installed by the manufacturer, and a system that changes its logic during operation create different questions.
Recheck your conformity assessment route
The directive's Annex IV categories become a different structure under the regulation: Annex I, Parts A and B. Article 25 links those categories to the available conformity assessment procedures.
- Part A: the available procedures require notified-body involvement.
- Part B: internal production control is available under the specified condition that relevant harmonised standards or common specifications cover all relevant EHSRs; otherwise a notified-body procedure is needed.
- Outside Annex I: the regulation provides for internal production control.
Part A includes specified categories involving self-evolving behaviour in safety functions. That is a reason to examine the category wording against the actual product, not to assume that every machine using AI follows the same route.
Document the new classification and procedure. If external involvement is required, establish the provider's relevant designation, needed documentation, sample availability, and review schedule. A previous lab relationship does not settle those questions.
Also recheck the legal basis and citation status of standards for the new regime. A familiar standard may remain technically useful while its regulatory status needs separate verification. As of this review, the Commission says a new Machinery Regulation list is being prepared and expected before the end of 2026. Check the published decisions when making the assessment; that expectation is not itself a citation. See the Commission’s machinery standards page.
Review changes after delivery against the substantial-modification definition
Article 3(16) defines substantial modification through physical or digital changes after placing on the market or putting into service. It includes conditions concerning whether the manufacturer foresaw the change, new hazards or increased risks, and the protective measures required. Article 18 sets out manufacturer obligations for the person carrying out such a modification. Read Articles 3(16) and 18.
Not every repair, replacement, or firmware update is automatically a substantial modification. Equally, calling a change “just software” does not settle its safety impact.
Give service teams and integrators a way to flag proposed changes before implementation. Record the original intended configuration, the proposed change, the affected hazards, and the assessment against the legal definition. Where the change qualifies, identify the resulting obligations and assessment work.
For product development, this also makes your original assumptions valuable. Clear records of intended updates and operating boundaries help later teams understand what the manufacturer planned and assessed.
Digital instructions need a delivery and maintenance plan
The regulation permits digital instructions, subject to conditions in Article 10(7). These include identifying how to access them, making them printable and downloadable for storage and access during a breakdown, and keeping them available online for the expected product lifetime and at least ten years after placing on the market. A user requesting paper instructions at purchase must receive them free within one month. Essential safety information must still be supplied on paper for machinery intended for, or foreseeably usable by, non-professional users. Read Article 10(7).
A QR code is therefore the entrance to a maintained system. Decide who keeps the address working, how customers find instructions for their model, how versions are preserved, and how paper requests are fulfilled. Test access in the circumstances where the user needs the information, including when the machine is unavailable.
The new EU declaration and technical documentation also need review against the regulation's required contents. Update references, responsibilities, and templates after the product assessment has established what they must contain.
Turn the transition into assigned work now
Use a short gap review with four outputs:
| Review | Record | Likely project consequence |
|---|---|---|
| Timing and scope | Product-specific applicability rationale | Establish which regime the release must satisfy |
| Safety and software | Affected hazards, requirements, and design assumptions | Plan design changes and validation where needed |
| Assessment route and standards | Category, procedure, external involvement, standards review | Reserve specialist and assessment capacity |
| Documentation and delivery | Technical-documentation changes, instructions, declaration, and access arrangements | Assign owners before release pressure builds |
Prioritise work with dependencies. A change to a safety function can affect design, testing, documentation, and external assessment. A new instruction-delivery process may need support operations and infrastructure that engineering does not own.
The transition becomes manageable when each affected requirement has an owner, an implementation decision, and the evidence needed to close it. The minimum conformity assessment workflow provides a way to track those connections. If your release is already close, use the compliance risk checklist to find missing evidence first.
Sources and scope
This is a product-planning explanation, not an exhaustive account of the regulation. Applicability, product category, and safety conclusions depend on the actual product. The sources were checked on 8 October 2026.
- Regulation (EU) 2023/1230, corrected consolidated text — Articles 3, 10, 18, 25, and 51–54; Annexes I, III, IV, and V.
- European Commission: Machinery — transition date, corrigendum, guidance, and notified-body resources.
- Machinery Directive 2006/42/EC, consolidated text — the regime preceding the regulation.