“2027 Delivery, Safety Software Changed”: What Belongs in the Machinery Compliance Review?
Qualify an EU machinery compliance request by fixing the delivery event, software or safety-function change, technical-documentation gap and Article 25 route before proposing an assessment.
Signals to watch
- A named machinery model or robot-cell version has a 2027 factory-acceptance, shipment or EU commissioning event
- Software, programming logic or a safety function changed, but the risk assessment and technical documentation do not yet trace the change
- The requester cannot show whether Annex I applies or which Article 25 conformity-assessment route supports the delivery
A 2027 delivery, a changed safety function and an incomplete technical file belong in one assessment request only when they refer to the same machinery configuration and the same EU market event. Start with a before-and-after change package: identify the product and version, what the software or safety function did before, what it does now, which hazards may be affected, what evidence exists and which conformity route is being considered. Do not begin by promising a notified body or calling the change a substantial modification.
That distinction matters to a machinery-regulation agency’s business-development lead following authorised OEM, robotics, automation and distributor Telegram groups. A useful Signal combines a 2027 factory-acceptance, shipment or commissioning date with a safety PLC, interlock, protective-stop or control-logic change and a missing risk-assessment update, technical file or route decision. Finding it one day late can mean missing the evidence meeting where owners and timing are fixed. It does not prove buyer authority, the legal route or a purchase.
Definition: fix the event before naming the regime
Regulation (EU) 2023/1230 is the EU Machinery Regulation. Its consolidated text, which includes the corrigendum, says that it applies generally from 20 January 2027. The Commission’s machinery page says machinery placed on the EU market before that date remains subject to Directive 2006/42/EC. The original Official Journal text displayed 14 January 2027 before correction, so the consolidated date should be used.
“Delivery in 2027” is therefore not a legal classification. It could mean a factory-acceptance test in December 2026, shipment in January, customs arrival in February, installation in March or putting into service later. A framework contract may cover multiple machines and versions. The first record should name one unit or controlled series, the manufacturer, the intended use, destination Member State, software version and the precise event that is thought to place it on the market or put it into service. Legal counsel or the competent conformity specialist should confirm which event controls.
This is also where substantial modification needs careful use. Article 3(16) defines it as an unplanned physical or digital post-market or post-service change. It must create a new hazard or increase risk and require the specified new or additional protective measures, including relevant safety-control-system changes. Article 18 then treats the person carrying it out as manufacturer for the affected machinery or product under the Regulation’s conditions.
An ordinary software update is not automatically a substantial modification. A planned safety-logic revision made by the original manufacturer before initial market placement may be part of the original design and conformity work instead. Record the timing, who planned the change and its safety effect; do not turn the label into the conclusion.
Why a before-and-after package makes the request quotable
An email saying “software updated; technical file needs checking” conceals most of the work. A useful package puts the old and new states side by side:
- exact machine, related product or partly completed machinery, including model, serial range and software build;
- original intended use, reasonably foreseeable misuse and declared operating limits;
- old and new control behaviour, with changed inputs, outputs, safety functions, parameters and fault responses;
- the trigger for the change, the person controlling it and whether it occurred before or after market placement or putting into service;
- affected hazard analysis, safety-requirement specification, validation evidence and residual-risk information;
- current technical-documentation index, with each item marked current, previous-version only, missing or not reviewed; and
- the market event and date that the assessment must support.
Use artifacts, not assurances. “Safety PLC validated” should point to a controlled validation report for the named software version. “No new hazard” should point to the revised risk assessment and the boundaries reviewed. “Technical file exists” should resolve into drawings, control-circuit descriptions, calculations, test results, instructions, declarations and the other applicable Annex IV material.
Article 10 requires the manufacturer of machinery or a related product to prepare Annex IV Part A technical documentation, apply the relevant Article 25 procedure, draw up the EU declaration of conformity and affix CE marking when conformity has been demonstrated. For partly completed machinery, Article 11 instead connects Annex IV Part B technical documentation with assembly instructions and an EU declaration of incorporation. These are different deliverables; the group poster’s use of “machine” does not decide which one is involved.
Technical documentation and the relevant declaration generally remain available to market-surveillance authorities for at least 10 years. Relevant source code or programming logic may be requested where needed to check essential health and safety requirements. An initial inquiry need not include a repository; it should identify the controlled logic, verification records and evidence owner.
Trace the change into the Article 25 route
Annex I is a classification step, not shorthand for “notified body required.” Article 25 separates three branches:
- Annex I Part A: use EU type-examination followed by conformity to type, full quality assurance or unit verification. Simple internal production control is not listed.
- Annex I Part B: internal production control is possible only when the machinery is designed and constructed in accordance with the category-specific harmonised standards or common specifications covering all relevant essential health and safety requirements. If that condition is not met, one of the other listed procedures is required.
- Not listed in Annex I: Article 25(4) provides the internal-production-control route.
The change package should therefore name the proposed Annex I category, quote the product facts supporting it and show the standards or specifications relied on. If coverage is partial, outdated or not yet checked, keep the route provisional. A request for “a notified-body quote” may actually contain an unresolved product classification, a missing standards-coverage analysis or a documentation repair. Those are distinct scopes.
The CRA critical-product assessment article similarly separates an everyday label from an Annex category. The UK PSTI statement analysis shows how one unsupported line can reveal a larger evidence job; the official-source ladder keeps the binding source and access date visible.
Example: a robot-cell update before a 2027 acceptance meeting
Consider a composite, deliberately incomplete group thread, not a customer case or a legal conclusion:
“Cell ships early 2027. New gripper means we changed safe-speed logic. FAT evidence call tomorrow; risk file is still on the old build. Need EU gap review.”
The sales lead can identify one potentially time-sensitive combination: a 2027 event, a safety-control change and version-mismatched evidence. The next action is to request the machine and software identifiers, the old and new functional description, intended market event, Annex I analysis, applicable standards, risk-assessment revision and current validation report. Unknowns remain: whether “ships” is the relevant market event, whether the original manufacturer planned the change, whether the change occurred before market placement, whether it creates a new hazard or increases risk, whether the cell or one component is the assessment object, and which conformity route applies.
Those records let the agency scope a document review, risk-assessment update, software-safety validation review or route analysis. Without them, it can quote bounded discovery, not a conformity result. Early discovery buys time before the evidence meeting; it does not predict compliance or commercial qualification.
TOP Prospect can surface, merge, deduplicate and rank fragments from Telegram groups the user deliberately connects and is authorised to access, while retaining original text, source, time, an AI summary and reasons for human review. It cannot inspect a machine or its software, decide whether a substantial modification occurred, classify Annex I, select the Article 25 route, certify CE compliance, contact the poster or read private or unauthorised sources. Public plan information is available on the pricing page.
Key Facts
- Regulation (EU) 2023/1230 applies generally from 20 January 2027; transition depends on the actual market event, not the phrase “2027 delivery.”
- A substantial modification under Article 3(16) is not any software change; timing, manufacturer planning, safety effect and required protective measures all matter.
- Article 18 can place manufacturer obligations on the person carrying out a substantial modification.
- Machinery or related products and partly completed machinery have different Annex IV documentation and declaration paths.
- Annex I Part A, Annex I Part B and non-Annex-I machinery do not share one conformity-assessment route.
- Technical documentation and declarations generally need to remain available for at least 10 years.
FAQ
Does every software update count as a substantial modification?
No. Article 3(16) requires an unplanned physical or digital change made after machinery was placed on the market or put into service, an effect on safety through a new hazard or increased risk, and the specified need for new or additional protective measures. A planned pre-market design update does not meet that definition merely because software changed.
Does a 2027 delivery automatically fall under Regulation (EU) 2023/1230?
No. The Regulation applies generally from 20 January 2027, while machinery placed on the EU market before that date remains under Directive 2006/42/EC according to the Commission. The exact product, placing-on-the-market or putting-into-service event, contract structure and transition facts need to be checked.
Does Annex I machinery always require the same notified-body route?
No. Annex I Part A uses one of the Article 25(2) procedures and does not offer simple internal production control. Part B permits internal production control only when the applicable harmonised standards or common specifications cover all relevant requirements and are correctly applied; otherwise one of the other listed procedures is required.
What should the first gap-assessment package contain?
It should identify one product and version, the dated EU market event, the before-and-after change, affected hazards and safety functions, current risk assessment, Annex I classification, candidate Article 25 route, technical-documentation inventory, evidence owners and unresolved assumptions.
Reviewed by TOP Prospect Editorial Team on 16 August 2026. Legal facts were checked against the consolidated Regulation (EU) 2023/1230 and the European Commission machinery page listed above; a competent specialist must apply them to the actual product and market event.
Frequently asked questions
Does every software update count as a substantial modification?
No. Article 3(16) requires an unplanned physical or digital change made after machinery was placed on the market or put into service, an effect on safety through a new hazard or increased risk, and the specified need for new or additional protective measures. A planned pre-market design update does not meet that definition merely because software changed.
Does a 2027 delivery automatically fall under Regulation (EU) 2023/1230?
No. The Regulation applies generally from 20 January 2027, while machinery placed on the EU market before that date remains under Directive 2006/42/EC according to the Commission. The exact product, placing-on-the-market or putting-into-service event, contract structure and transition facts need to be checked.
Does Annex I machinery always require the same notified-body route?
No. Annex I Part A uses one of the Article 25(2) procedures and does not offer simple internal production control. Part B permits internal production control only when the applicable harmonised standards or common specifications cover all relevant requirements and are correctly applied; otherwise one of the other listed procedures is required.
What should the first gap-assessment package contain?
It should identify one product and version, the dated EU market event, the before-and-after change, affected hazards and safety functions, current risk assessment, Annex I classification, candidate Article 25 route, technical-documentation inventory, evidence owners and unresolved assumptions.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
