Daptic announces $22M funding to bring compliance into product development. Learn More
Request Demo
Expert Authored

Regulatory change management: a step-by-step process for product teams

A regulatory change management process in eight steps: scope from your products, track the right sources, triage changes and tie each to parts and owners.
Eight checked chips arranged in a circle, each naming a step of regulatory change management from defining scope to review, on an indigo gradient background.
November 10, 2026

Marc HaddadMarc HaddadForward Deployed Regulatory Engineer

 

Regulatory change management is the process a manufacturer uses to turn each new or amended rule into a dated task against a specific product. A repeatable process scopes from your products and markets, watches official sources, triages each change, traces it to part numbers, gives it an owner and a deadline, and keeps evidence of every decision.

Key points

 

  • Rules keep moving: A regulation is announced years before it changes your product, and it keeps moving after publication, as corrections, amending acts, delegated and implementing acts, and standards lists all change what you have to do.
  • Start from the product: Run change management from the product, not from the source. Scope is products by markets by topics, and every change should end on a part number with an owner and a deadline.
  • Where teams slip: Teams rarely miss a whole law. More often they ignore a proposal until it is adopted, or an adopted change never gets linked to the products it hits.
  • Plan to the application date: Plan around the date of application, not entry into force.

What is regulatory change management?

 

Regulatory change management is the routine that turns a new or amended rule into a dated task against a specific product. It exists because a law arrives in stages rather than all at once. Over several years it is proposed, adopted, published, corrected, amended and supplemented, and several of those steps change what your product needs. This routine is one part of what product compliance covers for a manufacturer.

 

The table below shows those stages for one law: the EU Machinery Regulation, Regulation (EU) 2023/1230, which replaces the Machinery Directive 2006/42/EC. In the table, OJ is the Official Journal of the European Union, where EU law is published.

 

Date Stage Status
April 21, 2021 Commission proposal, COM(2021) 202 Proposal
June 14, 2023 Signed by Parliament and Council Adopted
June 29, 2023 Published in OJ L 165 Adopted
July 4, 2023 Corrigendum in OJ L 169 corrects 14 dates Adopted
July 19, 2023 Entry into force (Article 54) In force
January 20, 2024 Rules on notified bodies apply (Articles 26 to 42) Applies
July 27, 2026 Amended by Regulation (EU) 2026/1744 to align with the AI Act In force
September 7, 2026 Implementing Decision (EU) 2026/2015 published: adds standards under the Directive and repeals the Directive’s standards list from January 20, 2027 Adopted
October 20, 2026 National penalty rules apply (Article 50) Applies
By end of 2026 First list of harmonised standards under the Regulation Expected (Commission)
January 20, 2027 Regulation applies and the Directive is repealed (Articles 51 and 54) Adopted, not yet applicable

Which regulatory dates matter for your product?

 

The date of application matters most, because that is when a law’s obligations reach your product. Each row in the table is a different kind of event:

 

  • Entry into force: the date the law exists.
  • Date of application: the date its obligations reach your product.
  • Transition provisions: rules that decide what happens to stock and certificates. A unit placed on the market (first made available in the EU) under the Directive before January 20, 2027, can still be sold, and EC type-examination certificates stay valid until they expire.[1] Those certificates are issued by a notified body, an independent assessor designated by an EU country. Every unit placed on the market from January 20, 2027, must conform to the Regulation, even if the design hasn’t changed.[1]
  • Delegated acts: acts that let the Commission amend or supplement the law,[2] for example by changing the Annex I list of machinery that may need third-party assessment.[1]
  • Implementing acts: acts that set uniform conditions for applying the law,[2] such as common specifications where standards are missing.[1]
  • Harmonised standards: voluntary standards that give a presumption of conformity only once their reference is published in the Official Journal.[3] That means your product is presumed to meet the requirements the standard covers.

 

For a machine builder, the date to plan around is January 20, 2027. Entry into force in July 2023 changed nothing on the shop floor, and the October 2026 date changed enforcement, not design.

What are the steps in a regulatory change management process?

 

There are eight, and they work the same way for any product and any market.

 

  1. Define scope from the product: Build a matrix of products by markets by topics. Start from the bill of materials (the list of parts in each product) and the option codes, not from a list of laws. A machine sold with a remote-access gateway has a cybersecurity row, and the same machine without it doesn’t. Put a named owner on each product line.
  2. Pick sources for each cell: Choose the official journals, regulators, legislative files, standards bodies and notification systems that cover each product and market, as listed in the next section.
  3. Triage each item: Ask three questions. Does it touch a cell in the matrix? Is it proposed or adopted? Which dates apply: entry into force, application, transition, or the end of a standard’s presumption? Record the status exactly, because “Adopted, not yet applicable” is not “in force for products.”
  4. Assess impact down to parts and suppliers: For each relevant change, list the products, part numbers, supplier declarations, technical file sections, labels and instructions it touches. The technical file is the documentation that shows how a product meets the rules.
  5. Assign an owner and a deadline: Work back from the date that changes the product, allowing lead time for lab slots, notified body capacity and supplier redesign. If a change needs two teams moving at different speeds, give it two owners.
  6. Implement: Redesign, test, then update the technical file, the declaration of conformity (your signed statement that the product meets the rules), the labels and the instructions.
  7. Keep evidence: Record what you read, when, and which version, such as the date of the consolidated text. Write down every “not applicable” decision and the reason for it, because that record is your defence when an authority asks.
  8. Review: Re-run the scope whenever you add a product, market, supplier or option code, or a new act appears in a source you follow. A workable cadence is to check official journals weekly for your scope, check open proposals monthly, rebuild the scope matrix every quarter, and re-check each item after its named dates pass.

How do you track regulatory changes?

 

Follow the official sources behind each cell of your scope matrix, and filter what comes in by legal instrument and by scope, not by keyword. The sources fall into five groups:

 

  • Official journals: such as the EU Official Journal on EUR-Lex (the EU’s law database) and the US Federal Register
  • Regulators: their own pages
  • Legislative procedure files: files that follow a proposal through to adoption
  • Standards bodies: CEN and CENELEC (the European standards organisations), ISO and IEC (the international ones) and national bodies
  • Notification systems: systems that publish other countries’ draft rules

 

Notification systems give early warning because governments must use them before rules are final. Under the Agreement on Technical Barriers to Trade, members of the World Trade Organization (WTO) must notify proposed technical regulations that are not based on a relevant international standard and may significantly affect trade. They must do so “at an early appropriate stage,” while amendments can still be introduced, and allow reasonable time for comments.[4] Under Directive (EU) 2015/1535, EU Member States must notify draft national technical rules and hold them for three months.[5] In the US, proposed rules appear in the Federal Register for comment, and with some exceptions a substantive final rule is published at least 30 days before it takes effect.[6] The same approach extends to many countries at once, as covered in how to track regulatory change across 200+ jurisdictions.

 

Keyword monitoring brings in noise: searching “machinery” across European sources returns trade news, training qualifications and plant layoffs next to the one Commission decision that matters. It also misses things, because Annex III, point 1.1.9 of the Machinery Regulation is headed “Protection against corruption,” and a filter on “cybersecurity” would skip it.

How do you monitor proposed regulations before they are adopted?

 

Treat a proposal as a contingency: plan for it, even though you can’t file against it. The Machinery Regulation took nearly six years from proposal to application, but the design window is much shorter: a team that started at publication in June 2023 had already lost two years.

 

On June 26, 2026, Coreper, the committee of Member States’ ambassadors to the EU, confirmed the negotiated text of COM(2025) 504, a proposal that would make declarations of conformity for machinery digital. Parliament’s plenary vote is indicatively set for November 23, 2026. It is still a proposal, so treat it as a contingency and don’t change your documents to it yet.

Why does a regulation keep changing after it is published?

 

Because corrections, amendments and standards decisions keep arriving after the text appears in the Official Journal.

 

On June 29, 2023, the Machinery Regulation was published with a date of application of January 14, 2027, and October 14, 2023, for its national penalty rules.[1] On July 4, 2023, a corrigendum (a formal correction) moved those dates to January 20, 2027, and October 20, 2026. Uncorrected copies still circulate, so work from the consolidated text on EUR-Lex, which folds in corrections and amendments.

 

Between 2023 and September 2026, the Directive’s list of harmonised standards was amended seven times, and Implementing Decision (EU) 2026/2015 repeals it from January 20, 2027.[7] Until a standard cited only under the Directive appears in the new list, it gives you no presumption of conformity under the Regulation. The Regulation itself has been amended twice, by Regulation (EU) 2024/2748 and Regulation (EU) 2026/1744, and most of its obligations apply from January 20, 2027.

How do you link a regulatory change to the products it affects?

 

Connect the change log to the bill of materials, so every open change names the part numbers it touches. When the change log sits with regulatory affairs and the bill of materials sits with engineering, a well-triaged change can fail to reach anyone who can act on it. Daptic tracks regulatory changes across the markets you sell into, flags the ones that touch your products and works out which requirements apply to each product in each market, so you can see each open change against the products it affects instead of joining the two by hand.

 

Whatever tool you use, the test is the same: for any open change, can you name the part numbers it touches? If you can’t, step 4 isn’t happening.

Example: applying the process to a packaging line

 

This composite example shows how one product team would use the steps. A maker of packaging lines for food plants offers an optional remote service gateway. In 2023, its regulatory team logged the Machinery Regulation and gave it to the safety engineer who owned the Directive files.

 

Two things fell through. First, the gateway option brought Annex III points 1.1.9 and 1.2.1 into scope, which meant controls software work that nobody had been assigned. Second, the technical files relied on standards cited under the Directive, and nobody had checked whether they would be cited under the Regulation.

 

When the team rebuilt its scope from option codes, the gateway became its own row with its own owner, and a lab slot was booked before January.

 

To do the same for your product, list its options and accessories and give its own row and owner to each one that changes which rules apply. Then check every standard in your technical file against the list that will apply on your date of application.

Frequently asked questions

What is the difference between entry into force and date of application?

Entry into force means a law exists, while the date of application is when its obligations reach your product. The EU Machinery Regulation entered into force on July 19, 2023, but most of its obligations apply from January 20, 2027.

How often should you check for regulatory changes?

A workable cadence is weekly for official journals in your scope, monthly for open proposals, and quarterly for rebuilding your scope matrix. Re-run the scope sooner when you add a product, market, supplier or option code.

Should you act on a proposed regulation before it is adopted?

Plan for it as a contingency, even though you can’t file against it. Waiting for adoption may cost you the design window: a team that started at the Machinery Regulation’s publication had already lost two years.

Is keyword monitoring enough to track regulatory changes?

No, because keyword searches bring in noise and miss relevant text, such as a Machinery Regulation requirement headed “Protection against corruption” that a “cybersecurity” filter would skip. Filter by legal instrument and by your scope matrix instead.

Are existing products grandfathered under a new EU regulation?

Only the units already placed on the market are. Under the Machinery Regulation, every unit placed on the market from January 20, 2027, must conform, even if the design hasn’t changed.

Notes and sources

 

  1. Regulation (EU) 2023/1230, OJ L 165, June 29, 2023, particularly Articles 6(2), 20(3), 50(1), 52 and 54.
  2. Treaty on the Functioning of the European Union (TFEU), Articles 290 and 291.
  3. Regulation (EU) No 1025/2012, Article 10(6)
  4. WTO Agreement on Technical Barriers to Trade, Articles 2.9 and 2.12
  5. Directive (EU) 2015/1535, Articles 5 and 6
  6. 5 U.S.C. 553, particularly § 553(b).
  7. Commission Implementing Decision (EU) 2026/2015, particularly Article 2.

 

Additional sources:

 

 

This article reflects Marc Haddad’s independent opinions, not necessarily those of Daptic.

Resources

Related Articles

Request a Demo Today