EN 18286 presumption: how an auditor would test it, row by row

A practical guide for quality managers, internal auditors and AI governance leads.

Most teams can show a policy. Far fewer can show an auditor that the policy ran on the day it was supposed to run, and that is the gap the EN 18286 presumption tests. This guide walks through what the presumption covers, how an auditor samples the evidence, how an ISO/IEC 42001 certificate fits in, and where teams usually get stuck.

Key takeaways

• EN 18286:2026 is the first harmonised standard under the AI Act. Its presumption of conformity started on 14 October 2026.
• It covers the thirteen rows of Article 17(1) and the Article 11(1) technical file. Article 17(2), (3) and (4) are not covered.
• Two rows carry a condition: the risk row needs a risk process that complies with Article 9, and the technical file needs every Annex IV item.
• An auditor tests each row by setting a population, a period, a sample, the attributes to check and a pass or fail rule.
• An ISO/IEC 42001 certificate does not give the presumption by itself. A reuse ledger shows what carries over.
• The publisher describes no certification scheme for the presumption, so "designed with reference to EN 18286:2026" is safe wording and "EN 18286 certified" is not.

What is the EN 18286 presumption of conformity?

The European Commission published EN 18286:2026 as the first harmonised standard under the AI Act through Implementing Decision (EU) 2026/2274. The decision entered into force on 14 October 2026. If your quality management system meets the standard for the rows it covers, the law presumes you meet the matching duties in Article 17(1) of the AI Act.

A presumption is a head start, not a finish line. It does not turn your system into a certified one, and it only covers the rows and conditions the standard names.

Think of it like a school pass mark. If your work reaches the mark, the teacher starts from a position of trust. The teacher can still check the work, and the mark only means something when the work behind it is real.

Which AI Act rows does EN 18286 cover?

What the presumption coversCoveredCovered with a conditionNot covered

• Art. 17(1)(a)Regulatory strategy
• (b)Design control
• (c)Development and QA
• (d)Examination and validation
• (e)Standards and means
• (f)Data management
• (g)Risk managementArticle 9 process must comply
• (h)Post-market monitoring
• (i)Serious incident reporting
• (j)Authority communication
• (k)Record-keeping
• (l)Resources and supply
• (m)Accountability
• Art. 11(1)Technical fileEvery Annex IV item present
• Art. 17(2), (3), (4)Proportionality, sectoral systems, financial institutionsNot covered by the presumption

Based on the rows in this article

Two conditions deserve special attention. The risk row only holds if your risk process complies with Article 9, and there is no harmonised standard for Article 9 yet, so you have to show that compliance yourself. The technical file row only holds if every Annex IV item is present in the file.

How does an auditor test a row?

Imagine a school fire drill. The teacher does not simply ask, "Do you have a fire plan?" The teacher picks a few classrooms, times how long each one takes to leave, and checks that every child was counted. A plan on paper counts for little if the drill never works.

Auditors test AI Act rows in the same way. Before they start, they set five things.

How an auditor tests a rowExample: point (i), incident reporting

1. 1PopulationEvery event the row applies toEvery incident and near miss logged in the year
2. 2PeriodThe time window tested1 January to 31 December
3. 3SampleHow many items they pickAll incidents if fewer than ten, otherwise a random ten
4. 4AttributesWhat they check in each itemClock start date, report date, deadline met
5. 5Pass or fail ruleWhat counts as an exceptionAny report sent after the deadline is an exception

Based on the example in this article

Here are three examples of how this plays out in practice.

Point (a), changes. Pick every substantial change to a high-risk system during the year. For each one, check that someone assessed it against your criteria and wrote the decision down. A change that went live without an assessment is a fail.

Point (g), risk. Pick two risks with different severity levels. Follow each one from identification, to the test that proved the fix worked, to the sign-off of whatever risk remains. A risk closed without test evidence is a fail.

Point (i), incidents. Run a mock incident once a year. Teams that practise the reporting clock find gaps that a paper process never shows, such as an unclear owner or a missing contact number.

What is the difference between ISO 9001, ISO/IEC 42001 and EN 18286?

Teams often ask whether they need all three. They do different jobs, and they work best together.

1. EN 18286:2026The presumption route for AI Act quality dutiesCited in the Official Journal
2. ISO/IEC 42001Management system for AI across the organisation
3. ISO 9001:2015Base layer for process and document control

Based on the comparison in this article

Do I still need ISO/IEC 42001 if I follow EN 18286?

Usually yes. The standards overlap, but they do not replace each other. EN 18286 includes Annex C, which maps its clauses to ISO/IEC 42001, and Annex B, which maps to ISO 9001:2015. These maps show where clauses line up. They do not prove that the requirements are identical, so a 42001 certificate does not give you the presumption by itself.

The useful question is how much of your 42001 work carries over. Three things decide the answer.

• Certificate scope. Does it cover every site and every AI system under the AI Act? A certificate that covers only the headquarters leaves the engineering office outside the scope.
• Your role. A certificate written for a developer may not cover you as a deployer, and the reverse can also be true.
• The risk process. Does your 42001 risk method meet Article 9? A general AI risk assessment may miss the health, safety and fundamental rights angle the AI Act asks for.

What carries over from 42001

• Policy and governanceYesAdd: a regulatory compliance strategy tied to the AI Act
• Document controlYesAdd: records structured against Article 17 and Annex IV
• Risk managementPartlyAdd: proof that the process meets Article 9
• Incident handlingPartlyAdd: a reporting clock that matches Article 73 deadlines
• Post-market monitoringPartlyAdd: evidence against row (h)
• Technical fileRarely in fullAdd: one complete Annex IV file per system version

Based on the table in this article

A practical step is to build a reuse ledger with one line per Annex ZA item. Mark each line as "carries over", "needs extending" or "build new". Most organisations find that the strategy, the reporting clock and the per-system technical file need the most work.

Here is what the first lines of such a ledger can look like, built only from the rows above. The owners are examples; use your own.

Here is how a practitioner would put it. A 42001 certificate tells the market that your management system is sound. It does not tell an auditor that each AI Act row was tested against real records. Treat the certificate as the foundation of the house, not the finished house.

"Most teams are not short on policies. They are short on proof that the policy ran on the day it was supposed to run. That is the part we built Acuna GRC around."

We made the same point in our article on AI agents at the bank login: ISO/IEC 42001 supports the evidence, but certification does not by itself establish conformity with the AI Act.

Is there an EN 18286 certificate?

Not in the sense many people expect. CEN-CENELEC, which publishes the standard, describes no certification scheme for the presumption. Some certification bodies market "EN 18286 certification" services, and their marketing language should not be mistaken for the publisher's position. Any private certificate carries no legal effect beyond the conformity assessment the AI Act itself requires.

The defensible wording is that conformity with the standard is demonstrated within the AI Act conformity assessment, through internal control or a notified body, depending on the system.

Which EN 18286 edition should I buy?

The standard is sold by national standards bodies, and the substance is the same across editions, but you should buy the version that matches your working language and the market you document for.

Before you buy, confirm which edition your auditor or notified body will refer to. If your teams work across languages, agree in writing which version prevails.

What can I say about EN 18286 in writing?

This is where many organisations overreach, and a single sentence in a tender can create more exposure than the standard itself.

What happens if the reference is withdrawn?

The presumption lasts only while the Official Journal reference stands. If the Commission withdraws or restricts it, the presumption falls away and you must prove conformity directly. Keep evidence that stands on its own, not evidence that depends on the standard being cited.

Further harmonised standards are still in preparation, including risk management, cybersecurity and logging. Until they are cited, EN 18286 is likely to be the main presumption route for the quality management system, so plan around it and revisit the position at each JTC 21 milestone.

Key dates to plan around

1. 14 Oct 2026EN 18286 presumption starts
2. 2 Dec 2027Annex III high-risk obligations apply
3. 2 Aug 2028Annex I high-risk obligations apply

Based on the dates in this article

For the risk classes and the wider timeline, see our EU AI Act guide and how to classify a high-risk AI system.

Who runs the training behind this work?

Good evidence depends on people who can run the tests, and most of the failures we see come from teams who understood the standard on paper but had never sampled a real record or run a real incident drill. If your team needs that practical grounding, Abilene Academy offers PECB certified training in ISO/IEC 42001, AI governance, information security and data protection, taught in EN, FR, ES, DE, IT and more.

Abilene Academy is the only PECB Titanium Partner in Switzerland, which is the highest accreditation tier PECB awards. Its programmes report a 99% exam pass rate, and it has trained more than 2,500 professionals across 120+ countries, with 600+ organisations among its clients. The slogan says it well: Train with practitioners. Pass with confidence.

Where Acuna GRC fits

Acuna GRC is built for teams that need to show evidence, not just store documents. The practical question for most teams is where the records for each Annex ZA row live, who owns them, and whether an auditor can pull a sample without a week of chasing emails. Acuna GRC is designed to keep those records together, with a clear view of which sites and systems each framework covers, and it is itself ISO 27001 certified. It delivers in English, French and Spanish.

How to evidence it in Acuna GRC

• Population and period: an audit in Assure carries a Period from and a Period to, and its Records section groups the linked records as In period, Undated and Other periods. It hides nothing.
• Owner and proof: each record has a reference, a collection date and an owner. A record without a file or link shows the gap.
• Scope: frameworks, requirements and records can be assigned to scopes such as a site or a legal entity, which answers the certificate scope question above.
• Reuse across frameworks: Comply maps requirements from different frameworks to shared measures, so work done for ISO/IEC 42001 is linked rather than repeated.
• AI systems and incidents: the AI Governance module, available now, holds each AI system with its classification, impact assessments, named overseers and AI incidents. An incident or near-miss issue gets a timeline of dated steps, which is where a mock incident drill can leave its evidence.

AuditAssure

Internal audit: AI Act quality managementPeriod from 1 Jan 2026 to 31 Dec 2026 · Lead auditor: Aline RochatScope: Engineering office (Site)Internal

OwnerRecordsStatus

Art. 17(1)(a)Regulatory strategyMarie Dubois6 in periodCompliant

Art. 17(1)(g)Risk managementJonas Keller4 in periodPartially compliant

Art. 17(1)(i)Serious incident reportingMarie Dubois3 in period, 1 undatedPartially compliant

Art. 11(1)Technical fileJonas Keller0 in periodNot assessed

Linked records group as In period, Undated and Other periods, so the sample comes from the audit period.

Sample company · Brenvara AG

"A good platform should make the auditor's job dull in the best way. If they can pick a sample and find every record in minutes, your team can spend its time on the work that matters."

Ready to see how your evidence maps? Book a walkthrough of Acuna GRC, or start with the reuse ledger above and bring it to the call.

Book a walkthrough