AI Assurance Institute Logo AI Assurance Institute

Who needs an EN 18286 quality management system

Article 17, high-risk providers, and the dates the duty applies

Article 17 of the EU AI Act requires providers of high-risk AI systems to put a quality management system in place. EN 18286:2026 is the European standard written for that system. Now cited in the Official Journal, conformity with the standard can support a presumption of conformity with Article 17.

The duty is not optional for the organisations providing high-risk AI systems. The date conformity with Article 17 matters is 2 December 2027. is depends on which high-risk route applies and on whether the system is already in use.

The core group: high-risk providers

The person who must operate the QMS is the provider — the natural or legal person that develops an AI system, or has one developed, and places it on the Union market or puts it into service under their own name or trademark (Article 3(3)).

That includes:

Deployers are not the addressees of Article 17. Neither are importers or distributors, except where Article 25 moves the provider role onto them. General-purpose AI model providers are not automatically subject to EN 18286 unless a system that uses the model is high-risk and they are the provider of that system.

Which systems make the provider a high-risk provider

High-risk under the Act is set out in Article 6.

Annex III systems (Article 6(2)): stand-alone systems in the listed areas — biometrics, critical infrastructure, education and vocational training, employment and worker management, access to essential private and public services, law enforcement, migration and border control, administration of justice and democratic processes. The high-risk obligations for these systems apply from 2 December 2027.

Annex I systems (Article 6(1)): AI that is a safety component of a product, or is itself a product, covered by the Union harmonisation legislation listed in Annex I. Those obligations apply from 2 August 2028.

A system that is not high-risk does not trigger Article 17. Using EN 18286 for a non-high-risk system is a choice, not a duty.

Systems already in use before the deadline

A high-risk system that was already placed on the market or put into service before the relevant application date is not automatically pulled into the full Chapter III regime. Under the transitional rule, it is caught when it is substantially modified. Systems intended for use by public authorities have a later outer date (2 August 2030).

Substantial modification (Article 3(23)) is a change after placing on the market or putting into service that was not foreseen or planned in the initial conformity assessment and that affects compliance with the Act, or that changes the intended purpose. When a person makes such a modification and the system remains high-risk, that person becomes the provider of the modified system (Article 25). The original provider is no longer the provider for that specific system. The new provider must have the Article 17 QMS and must complete the applicable conformity assessment before the modified system stays on the market.

The QMS has to exist from the start of the lifecycle

Article 17 is not a document that is written at the end of development. It is the system that controls the high-risk AI system across its life: regulatory compliance strategy, design and design control, development and quality control, examination and testing, technical specifications, data management, the Article 9 risk management system, post-market monitoring, serious-incident reporting, communication with authorities, record-keeping, resource management, and an accountability framework.

EN 18286 is written the same way. It is product- and lifecycle-centric. The controls run from the definition of the system through design, validation, placing on the market, operation, monitoring, modification and eventual withdrawal.

That is why the QMS cannot be bolted on after 2 December 2027 for a system that is already in design or already on the market and about to be changed. The records the conformity assessment and the market surveillance authority will ask for are records that should have been generated while the system was being built and while it was in use. A binder assembled after the fact does not recreate design control, validation, or a living post-market monitoring system.

What happens if the QMS is not in place when the date arrives

From 2 December 2027 (Annex III) or 2 August 2028 (Annex I), a high-risk system may not be placed on the market or put into service without the QMS, the technical documentation, the applicable conformity assessment, the EU declaration of conformity and the CE marking.

If a system that is already in use is substantially modified after those dates without a compliant QMS and a new conformity assessment, the modified system is not lawfully on the market. Market surveillance authorities can require the economic operator to bring it into conformity, to withdraw it, or to recall it. Continuing to make it available is an offence under the Act's penalty regime.

Starting the QMS after the deadline does not create a grace period for systems that need to stay on the market. The practical consequence is interruption: the system comes off until the QMS, the technical file and the assessment catch up. For a product that is already sold or already embedded in a customer's process, that interruption is the cost of starting late.

Authorised representatives and the QMS

Providers established outside the Union must appoint an authorised representative established in the Union before their high-risk systems are made available on the Union market (Article 22). The mandate must empower the representative to:

The legal duty to operate the Article 17 QMS stays with the provider. The authorised representative does not become the operator of the QMS by appointment. What the representative cannot do is verify the declaration, hold the technical file, or answer an authority if the provider has not built and maintained the QMS. An authorised representative that takes on clients placing high-risk systems on the Union market therefore needs those clients to have a functioning QMS, and needs contractual access to the evidence the QMS produces. Without that, the representative cannot perform the mandate and the provider cannot lawfully make the system available.

Other routes that still need the QMS elements

Financial institutions subject to internal-governance rules under Union financial services law are deemed to fulfil most of Article 17 by complying with those rules, with the exception of the risk-management system, post-market monitoring and serious-incident reporting (Article 17(4)). In both cases the substance of the missing pieces still has to be covered. The deeming does not remove the need for those three elements.

Proportionality applies. Article 17(2) says the implementation shall be proportionate to the size of the provider, in particular for SMEs, start-ups and small mid-caps. The required level of rigour and protection does not drop. A smaller organisation may have a simpler QMS; it may not have no QMS.

Who does not need EN 18286

Those organisations may still ask their supplier whether the supplier's QMS follows EN 18286. That is procurement diligence, not an Article 17 duty of their own.

Summary

The organisations that need the Article 17 QMS — and therefore the organisations for which EN 18286 is written — are providers of high-risk AI systems. That includes EU providers, non-EU providers (with an authorised representative), and anyone who becomes a provider through substantial modification or a change of purpose or branding. The QMS has to control the system from the start of its lifecycle. For Annex III systems the high-risk duties apply from 2 December 2027; for Annex I products from 2 August 2028. A system that is substantially modified after those dates without a compliant QMS and a new conformity assessment cannot lawfully stay on the market.

Note that authorised representatives do not operate the QMS, but they cannot perform their mandate unless their client-provider has one.