Machinery Regulation 2027
What lies ahead for machine and plant manufacturers – and how to prepare
){kind=icon}
Picture this: One of your machines has been running smoothly at a customer's site for eight years. Three years ago, your service team installed a control system update; two years ago, they retrofitted a module; last month, they carried out the annual inspection. All of it documented – somewhere. A report in an email attachment, a timesheet in a folder, a photo on the phone of a technician who has since retired.
And now the market surveillance authority calls and wants to see complete, gap-free proof covering the entire history of your machine.
From January 2027, this is no longer a hypothetical scenario – it's a legal requirement. That's when the new EU Machinery Regulation takes effect, and it shifts the focus significantly: it's less about the moment a machine is first put into operation, and more about how completely you can prove that your machines stay safe and compliant throughout their entire life.
The good news first: you already do most of this documentation work. Every service call, every maintenance task, every modification generates reports, records, and timesheets. It's rarely about doing more. It's about making what you already do findable and verifiable.
And time is tighter than the deadline suggests. By January 2027, you don't have to retroactively catch up on everything – but your processes need to be in place. For every machine you deliver from that point on, the documentation obligation runs from day one: across its entire lifespan and for at least ten years beyond. Anyone who only introduces a system shortly before the deadline will have no established workflows in place – and from the very first machine under the new rules, they'll produce the same chaos of scattered attachments and phone photos all over again. Rolling out systems, migrating data, training staff: that's a process of months, not weeks.
What is the new Machinery Regulation, anyway?
Until now, Machinery Directive 2006/42/EC has applied. A directive is a kind of blueprint: each EU country had to translate it into its own national law – with minor variations from country to country.
The new Machinery Regulation 2023/1230, by contrast, is a regulation. And it applies immediately and identically everywhere – no national translation, no leeway. What's written in Brussels applies word-for-word in Cologne, Vienna, Warsaw, and Madrid.
This removes a layer of bureaucracy. But it also brings in plenty that's new. Here's the overview:
Topic | Old Machinery Directive (2006/42/EC) | New Machinery Regulation (2023/1230) |
|---|---|---|
Legal form | Must be transposed into law in each country | Applies directly across the entire EU |
Effective | since 2009 | from 20 January 2027 |
Software | barely regulated | explicitly covered, including digital changes |
Operating manual | paper only | for the first time, purely digital is permitted |
Modifications to machines | vaguely defined | clearly regulated, including digital interventions |
Cybersecurity | not covered at all | mandatory: appropriate protective measures |
The pattern is clear: the new regulation catches up with digital reality. In 2006, software, updates, and cybersecurity simply weren't major issues. Today, a software version helps determine whether a machine is safe – and that's exactly what the new regulation reflects.
When an update becomes a "substantial modification"
You're familiar with conformity assessment. Before a machine is delivered, you test it, document it, mark it with CE, and issue an EU declaration of conformity. Routine.
Here's the part many underestimate: your obligation does not end at delivery.
The regulation introduces the concept of "substantial modification" (Article 18). Put simply: if someone modifies a machine after it has been put into operation in a way that creates a new hazard or increases an existing risk – and the manufacturer had not anticipated this change in advance – then the obligation cycle starts over. New conformity assessment, new declaration of conformity.
Such a modification can be physical or digital.
In concrete terms, this can mean:
- a PLC update that affects the safety logic
- a safety-relevant software patch
- a control system retrofit
- a modification to the safety architecture
These are exactly the things your own service team does in the field all the time. You don't just build the machine – you maintain, modernize, and optimize it. In doing so, you may trigger the conformity assessment process yourself.
To put your mind at ease: routine maintenance and repairs explicitly do not count as substantial modifications. Replacing a worn-out motor with an identical spare part does not trigger a new conformity assessment. The line is drawn where "maintaining" turns into "modifying." But the basic principle is clear: the deeper an intervention reaches into a machine's safety, the more likely a fresh assessment becomes.
Ten years of proof – and what that means
This brings us to the heart of what's truly new in 2027: gap-free verifiability across the entire lifecycle.
A few of the most important obligations:
-
Keep records for ten years. You must keep the technical documentation and the declaration of conformity available for the authorities for at least ten years after the machine is placed on the market. On justified request, even the programming logic can be demanded.
-
Stay traceable. For ten years, you must be able to demonstrate whom you sourced parts from and whom you supplied.
Document maintenance. The operating manual must include information on inspections and maintenance, including intervals and wear criteria. -
Take the software version seriously. The installed software version counts as safety-relevant information. If it changes, that change is part of the conformity assessment.
Think back to the opening scenario: the report in an email attachment, the photo on the former colleague's phone. This is exactly where the real challenge lies. Not in any single obligation – but in keeping ten years of service, maintenance, and modification history in one place, securely and verifiably.
Where fieldux comes in
fieldux is a field service management tool. The new regulation places its focus on complete documentation across the entire lifespan. fieldux supports you exactly where most of the work used to pile up: in producing verifiable documentation across the full service lifecycle of your machines.
An important clarification: fieldux is not a compliance tool for the Machinery Regulation. The conformity assessment, the completeness of the documentation, the CE declaration, and your responsibility as the manufacturer all remain with you. But fieldux reliably takes over the bulk of the years-long proof work for service, maintenance, and modifications.
What fieldux does:
-
A gap-free service and maintenance history per machine: every job, every report, every certificate lives in fieldux – not in some inbox.
-
Digital inspection and test certificates with follow-up due dates, status, and signatures, ready to use as proof.
-
A change history: who changed what, and when? fieldux answers that question automatically in the background.
-
Signatures from technician and customer, with PDFs locked after completion – so the report stays exactly as it was.
The new centerpiece: the file explorer
The most exciting building block for lifecycle documentation is our new file explorer. It brings structure: documents are no longer attached to a single job, where no one can find them years later. They're stored where they make sense over time:
-
Per machine (asset): the complete history – reports, test certificates, timesheets (including versions), operating manual, declaration of conformity. The digital machine file.
-
Per customer: all documents belonging to a customer, in one place.
-
Per employee: the planner can store documents for each employee, and every employee can then access their attached documents directly in the app.
Instead of scattered individual files, the result is structured lifecycle documentation: accessible, downloadable, and exportable as a bundle.
With our first customer, we've already implemented an integration with Microsoft SharePoint, so the relevant documents can sync automatically.
Conclusion: Preparation doesn't begin in 2027 – it begins today
The new Machinery Regulation requires you to prove, without gaps, over ten years, that your machines stay safe and compliant.
Back to the beginning: the machine that's been running at a customer's site for eight years, and the call from the authority. With scattered email attachments, that call becomes a challenge. With a structured machine file, it becomes a five-minute task.
The conformity assessment remains your job. But the tedious, years-long proof work – you've already handled that with fieldux. And this is exactly where every month counts: those who structure their service and modification documentation now will start 2027 with established processes – and walk into any audit or liability case with confidence. Those who wait will run headlong into their first machine under the new rules, with the same scattered records they have today. The deadline is fixed and won't move. The only thing you can influence is how prepared you are when it arrives.
Don't want to miss any news?
Sign up for our newsletter and stay up to date!