Zum Hauptinhalt springen
QMS risk · EN 18286

QMS-03 Compliance strategy does not keep up with changes

Updated on 6 min Reviewed by: Cenedril Editorial
EN 18286EU AI ActISO/IEC 42001

A provider of an AI system that assesses health risks in applications for life insurers drew up its compliance strategy carefully, back then on the basis of drafts. Today the technical documentation still names an in-house specification as the route to demonstrating the quality management system, although EN 18286 has since been published in the Official Journal as a harmonised standard. The references to the AI Act quote the text as it stood before the amending Regulation (EU) 2026/1744. The cause is simple: watching for such changes was nobody’s job.

EN 18286 requires the provider, in clause 6.1.3, to consider at least four points when it decides on actions against risks to the QMS. The first is the strategy for regulatory compliance from clause 4.4. The risk behind it: the strategy was right when it was written and grows outdated while the legal framework moves on.

What is behind it?

The compliance strategy is the top-level plan: it sets out how the provider meets the requirements of the AI Act, which conformity assessment procedure applies, and how modifications, data, monitoring and incidents are managed. It rests on the regulatory requirements that the provider identifies and reviews systematically under clause 4.2. When this basis changes, the strategy is only as current as the process that works the change in.

What moves

  • Legal acts. The AI Act itself has already been amended by Regulation (EU) 2026/1744. Delegated and implementing acts come on top, such as the template for the post-market monitoring plan under Article 72.
  • Harmonised standards. Every reference in the Official Journal opens a new route to the presumption of conformity. EN 18286 has been one of them since Implementing Decision (EU) 2026/2274, and further standards for the requirements on high-risk systems are in preparation.
  • Common specifications and guidelines. The Commission can adopt common specifications by implementing act (Article 41) and issues guidelines on applying the Regulation (Article 96).
  • Sectoral law. For systems covered by the harmonisation legislation in Annex I, the requirements of the relevant product legislation change as well.

Where the process breaks

Often nobody is responsible. EN 18286 requires top management to assign the responsibility for identifying and reviewing regulatory requirements and the state of the art (clause 5.3). Just as often a change is noticed yet never reaches procedures and documentation: the strategy is updated, the chapter of the technical documentation listing the applied standards is left as it was. And where standards are cited without their edition, it is hard to tell later which version was meant.

Impact

An outdated strategy can lead to the wrong conformity assessment procedure, or to the provider relying on a presumption that the cited edition of a standard does not support. The EU declaration of conformity then names standards or legal texts that no longer fit. Conversely, a provider that misses a newly harmonised standard gives away an easier route to evidence and describes its own solutions with much effort. The gravest case is a new obligation that affects a system and that nobody implements, because from the day it applies the system no longer conforms.

Practical examples

Unnoticed harmonisation. A provider of assessment software for university admissions described an in-house specification for its QMS because no harmonised standard existed when it planned. After EN 18286 is published, the entry stays unchanged. At the next review, the team realizes that it has long applied the standard in large parts without invoking the presumption.

Citations without editions. A provider of safety components for industrial robots cites standards by number only in all its documents. When a new edition appears, nobody can show any longer which version the systems were tested against.

A change that never reaches practice. A provider of a candidate pre-selection system built on the foundation model of a sister company learns from a newsletter that the amending regulation sets a different recipient for serious incident reports for such systems. The legal team takes note, and the reporting route in the AI communication plan stays as it was.

Effective measures

The AI Provider Policy from the AI Compliance Starter Kit addresses this risk in these places:

  • Section 1 (Legal and normative basis): The legal basis is monitored continuously and reviewed systematically, and every change that touches a provider system is assessed. Its status feeds into the management review.
  • Section 4 (Strategy for regulatory compliance): Assessment procedure, handling of modifications and continuously learning systems are settled per system, and the results are recorded with a date.
  • Section 14 (Technical specifications and standards): For each system it is clear which standards apply. Where a harmonised standard is not applied in full, the technical documentation describes the chosen solution.
  • Section 22 (Control of documented information): Documents of external origin are kept with title, edition and location, legal acts in the AI legal register.
  • Section 24 (Roles and responsibilities): A dedicated role identifies regulatory requirements and the state of the art and reports changes to the AI officer.
  • Section 26 (Review and maintenance): When the legal basis changes, the policy is reviewed outside the annual cycle.

These ISO/IEC 42001 controls contribute as well:

Article 17(1)(a) of Regulation (EU) 2024/1689 names a strategy for regulatory compliance as the first aspect of the QMS, covering conformity assessment procedures and the management of modifications. Point (e) requires the provider to define the technical specifications and standards it applies and, where harmonised standards are not applied in full or do not cover every requirement, to describe the means by which the system still meets them. Both presuppose that the provider knows the current state. The management review under EN 18286 explicitly takes new or revised legislation and standards as inputs (clause 10.1). If you apply the standard, you rely on the presumption of conformity for Article 17(1) within the scope of Annex ZA (→ EN 18286: Quality Management System for AI Providers).

Sources

Frequently asked questions

What belongs to the compliance strategy under EN 18286?

At least meeting the essential requirements of Articles 9 to 15 of the AI Act, post-market monitoring, the handling of serious incidents, data management, the choice of conformity assessment procedure and the handling of modifications to the systems. The strategy follows the intended purpose and the application areas of the systems and exists as documented information.

How often should I check the legal situation?

EN 18286 requires a systematic review and sets no fixed interval. Ongoing monitoring by a named role plus a fixed check in every management review has proven useful. The AI Provider Policy also provides for a review of the policy as soon as the legal basis changes.

Do I have to apply a newly harmonised standard straight away?

Harmonised standards are voluntary, and applying one gives the presumption of conformity within the scope of its reference. If you do not apply such a standard, or apply it only in part, the technical documentation describes how you meet the requirement concerned instead. What matters is that the choice is made deliberately and recorded for each requirement.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.