The first harmonised standard under the AI Act does not tell a model how to behave. It tells the company behind the model how to run itself.
EN 18286 is a standard for a quality management system. It covers the processes a provider runs around a high-risk AI system, not a test the system has to pass. Its reference appeared in the Official Journal on 14 October 2026. From that day, a provider that applies it is presumed to meet the quality management requirements of the AI Act that it covers.
So the first concrete yardstick of the AI Act is a management document. That matters to any organisation that builds high-risk AI, and to any organisation that buys it.
How EN 18286 reached the Official Journal
The Commission adopted Implementing Decision (EU) 2026/2274 on 12 October 2026. The Official Journal carried it two days later. Its annex lists one standard: EN 18286:2026, Artificial intelligence, Quality management system for EU AI Act regulatory purposes. The European standardisation bodies CEN and CENELEC drafted it. The decision entered into force on publication, and the presumption of conformity runs from the same date.
On 19 October the Commission announced the publication. It tied EN 18286 to Article 17 of the AI Act. That article requires providers of high-risk AI systems to put a quality management system in place. According to the Commission, EN 18286 is the only AI quality management standard with a presumption of conformity.
The route was quick by standardisation measures. The draft, prEN 18286, entered public enquiry on 30 October 2025, the first harmonised AI standard to reach that stage. Less than a year later, the final reference sits in the Official Journal.
Why a management standard came first
The Commission asked CEN and CENELEC for standards in ten areas. They include risk management, data quality, human oversight, accuracy, robustness and cybersecurity. Quality management is one of the ten, and it arrived first. The Commission’s standardisation page calls quality management and risk management strong candidates to become market benchmarks.
That order makes sense. Every technical requirement in the AI Act needs an owner, a check and a record. A quality management system is where those three live. Without one, a model card or a risk register is a document that nobody has to keep current.
The decision also spells out the scope. EN 18286 answers the request for quality management systems for providers of AI systems. That request explicitly includes post-market monitoring processes. The standard therefore reaches past the launch date into the years in which a system is in use.
What presumption of conformity means
Using a harmonised standard is voluntary. A provider can meet Article 17 in another way. The difference lies in the burden of proof. A provider that applies EN 18286 is presumed to meet the requirements the standard covers. A provider that chooses its own route has to show by other means that it meets them.
For a regulator or a buyer, that difference is practical. “We follow EN 18286” is a claim anyone can check against a published text. “We have our own approach” opens a longer conversation.
EN 18286 and ISO/IEC 42001
Organisations that have invested in ISO/IEC 42001 will ask whether that work counts. The Commission says EN 18286 sits on top of existing international standards rather than replacing them. It names ISO/IEC 42001, ISO 9001 and sectoral systems such as ISO 13485 for medical devices. Providers in regulated sectors can fold EN 18286 into what they already run. They do not need a parallel system.
The reverse also holds. An organisation without ISO/IEC 42001 can use EN 18286 to extend its current quality management system. It can also use it to build its first one.
There is a catch. An ISO/IEC 42001 certificate shows good management. On the Commission’s account, however, it does not bring the presumption of conformity; only EN 18286 does. A provider that relies on its 42001 certificate alone still has to answer the AI Act’s quality management requirements separately.
What changes if you buy rather than build
The Commission addresses EN 18286 to providers of high-risk AI systems. It also addresses organisations that intend to place such systems on the EU market or put them into service. If you build a high-risk system yourself, EN 18286 is your standard.
If you buy one, EN 18286 still helps. It gives procurement a reference point with legal weight. Until 14 October, a buyer had no harmonised standard to hold a supplier’s quality claims against. Now there is one. Four questions follow from it:
- Does your quality management system follow EN 18286? If not, how do you show that it meets Article 17?
- Have you built EN 18286 into a system you already run, such as ISO/IEC 42001 or ISO 9001?
- Which post-market monitoring processes cover our use, and what will you tell us when they find a problem?
- Who in your organisation owns the quality management system, by name or by role?
The third question is the one for a deployer. EN 18286 covers post-market monitoring, and a supplier’s monitoring helps you only if its findings reach you. Some incidents cross the AI Act’s reporting threshold and some do not. Our piece on AI incident reporting below the serious incident line covers both.
The timetable behind EN 18286
The Commission places the publication ahead of the high-risk requirements, which it dates to December 2027 and August 2028. The presumption is available now, more than a year early.
That lead time is shorter than it looks. A quality management system takes longer to make true than to write down. People need responsibilities, processes need to run and records need to build up. Documentation dated the week before the deadline proves little. A year of evidence that the system has been running proves a great deal more.
The Commission expects further harmonised standards but gives no dates for them. For the other nine areas, providers will work from drafts and from the text of the AI Act for some time yet. For quality management, the wait is over.
The question for an organisation with a high-risk AI system on its roadmap has changed. It is no longer what the standard will say. It is who will own EN 18286, and when that work starts.