Ten common false statements about ISO/IEC 42001 and what it says
Ten statements about ISO/IEC 42001 that the standard does not make: Annex A and B, human oversight, audit duration, the EU AI Act. With references.
In short
Many statements about ISO/IEC 42001 are not in the standard. The most common error: guidance from Annex B presented as a requirement of Annex A. Requirements are in clauses 4 to 10 and in Table A.1; Annex B gives implementation guidance. Ten widespread statements, each with its reference and the correct version.
Auf Deutsch lesen: deutsche Fassung
“The standard expressly requires that.” I hear this sentence in audits, read it in quotes and find it in training slides. Often it is true. Surprisingly often it is not.
I audit against ISO/IEC 42001 and I teach it. That is why I read statements about the standard with the text next to me, my own included. In November 2026 I did this systematically and looked up statement after statement in ISO/IEC 42001, in ISO/IEC 42006 and in the Official Journal of the EU.
This article shows the ten statements that were most frequent or had the most consequences. You will find them, in these or similar words, on many websites, in quotes and in presentations. Anyone building or auditing an AI management system should know them before an auditor asks.
The error behind most errors: Annex A is not Annex B
The standard has two annexes that are easy to confuse. Annex A contains the controls in Table A.1, 38 of them, each in one or two sentences. Annex B gives implementation guidance for each control, often half a page long. Annex B is labelled normative as well. But it is worded with “should”, and the standard itself says that an organisation may extend or modify this guidance or replace it with its own implementation, and does not have to justify excluding it (B.1).
This is where most errors arise. The guidance is more concrete and easier to quote than the brief control. So people write “A.10.3 expressly requires” and mean something that is in B.10.3, with a “should” in front of it. In a text nobody notices. In an audit they do: a nonconformity needs a requirement, and guidance is not one.
The test is simple. If the sentence is in clauses 4 to 10 or in Table A.1, it is a requirement. If it is only in Annex B, it is a suggestion for how to meet the requirement. You may quote both. You just have to say which of the two it is.
The ten statements at a glance
| No. | How it is often put | What the standard says | Reference |
|---|---|---|---|
| 1 | A.10.3 requires documenting how supplied systems are integrated and distinguishing suppliers by risk | A.10.3 requires a process to ensure that the use of supplied services, products or materials fits the organisation’s own approach. The rest is guidance | A.10.3, B.10.3 |
| 2 | A.6.2.4 requires release criteria and acceptable error rates | A.6.2.4 requires defining and documenting verification and validation measures and specifying criteria for their use. Error rates appear only in the guidance | A.6.2.4, B.6.2.4 |
| 3 | A.6.2.8 requires defining the scope of logging | A.6.2.8 requires determining in which life cycle phases event logs are enabled, at the least when the system is in use | A.6.2.8, B.6.2.8 |
| 4 | The standard requires human oversight | There is no separate control for it. Human oversight appears in the guidance of Annex B | A.9.3, B.9.3 |
| 5 | Annex A has 38 controls in 9 objectives | 38 controls is correct. There are nine topic areas (A.2 to A.10) and ten objectives, because A.6 has two | Table A.1 |
| 6 | With the certificate you conform to the EU AI Act | ISO/IEC 42001 is not listed as a harmonised standard. So far only EN 18286:2026 is listed | Implementing Decision (EU) 2026/2274 |
| 7 | The certification audit takes two to five days | The minimum starts at 3.5 auditor days, at 5 for developers of AI and at 6.5 for multiple roles, in each case before adjustments | ISO/IEC 42006:2025, Table A.1 |
| 8 | Top management must approve the Statement of Applicability | What is required is approval of the risk treatment plan and the residual risks by the designated management | 6.1.3 |
| 9 | 8.2 is a separate risk process, and 8.3 is where controls are selected | 8.2 performs the assessment under 6.1.2 at planned intervals. 8.3 implements the plan under 6.1.3 and verifies its effectiveness. Selection happens in 6.1.3 | 6.1.2, 6.1.3, 8.2, 8.3 |
| 10 | All other standards in the family are guidance | ISO/IEC 42006 sets requirements for certification bodies. ISO/IEC 22989 is the terminology standard that ISO/IEC 42001 refers to normatively | ISO/IEC 42001, clause 2 |
Four statements with consequences in an audit
Not every one of these errors costs the same. Four of them can do real damage in an audit or in a quote.
Human oversight. The sentence “the standard requires human oversight” is among the most common of all. The term does not appear in Table A.1. It appears in the guidance of Annex B and as a possible objective in Annex C. What the controls require is something else: defining objectives for the responsible use of AI (A.9.3) and using the system as intended and documented (A.9.4). If you define human oversight as an objective, you then have to evidence it. If you do not, you are not in breach of the standard. For high-risk systems the EU AI Act requires oversight anyway, but that is a different set of rules.
Audit duration. Rules of thumb such as “two to five days” or “at least four days” circulate for the certification audit. ISO/IEC 42006 calculates differently: by the number of people in the AI life cycle and by role. In the smallest band of up to ten people it is 3.5 auditor days for organisations that provide or use AI, 5 days for organisations that develop AI and 6.5 days for multiple roles. Annual surveillance is about one third of that. Anyone who budgets two days is budgeting past the standard.
Conformity with the EU AI Act. A presumption that a product meets the requirements arises only through harmonised standards whose reference is published in the Official Journal. Since 14 October 2026 a single standard has been listed there: EN 18286:2026 on the quality management system of providers. ISO/IEC 42001 is not listed. A certificate under ISO/IEC 42001 is good groundwork and a strong signal to customers. It is not evidence under the EU AI Act.
Approval and the risk process. The standard requires that the designated management approves the risk treatment plan and the residual risks (6.1.3). Having the Statement of Applicability approved at the same time is sensible. You must not present it as a requirement of the standard. It is similar with clauses 8.2 and 8.3: they carry out what was defined in 6.1.2 and 6.1.3. Anyone who asks in an audit about the procedure for risk assessment opens clause 6, not clause 8.
How such sentences come about
Behind almost every one of these statements is one of three sources.
- The good piece of guidance. Annex B is concrete, Annex A is brief. Whoever wants to explain reaches for the concrete sentence and forgets the “should”.
- The other translation. Besides the official German version DIN EN ISO/IEC 42001:2026-08 there are older, unofficial translations with different terms for the AI policy and for suppliers. Anyone who knows both mixes them easily.
- The rule-of-thumb number. “Three years”, “two to five days”, “nine objectives”. Such numbers are roughly right, travel from text to text and are never looked up again.
Then there is time. What was correct when written may be outdated today. ISO 9001:2026 replaced the 2015 edition in September 2026, and clause 10 is numbered differently there. The International Accreditation Forum ceased operations on 1 January 2026, and recognition is continued by the Global Accreditation Cooperation. You only find such changes if you go back to the source regularly.
Three rules for clean references to a standard
Three rules apply to every text on this website. They work just as well for your policies and procedures.
- Every statement about a requirement gets its reference, and I check whether it is in clauses 4 to 10, in Table A.1 or only in Annex B. If it is in Annex B, the text says “the guidance recommends”.
- In German I quote the official German version with its terms. One deliberate exception: that version uses a different word for controls than everyday practice and ISO/IEC 27001 do, and I keep the established one.
- The status is dated. What applies today is recorded on a separate page with verification dates, and changes in law and standards are noted in the text.
The current status of the EU AI Act and the standards, each point with its source and verification date:
Status of the EU AI Act and the standardsWhat to take away
Apply the same test to your own documents. Take your AI policy, your procedures and your training slides and search for sentences such as “the standard requires” or “in accordance with A.x”. Look up every reference. Three outcomes are possible.
- The requirement is there. Good, the reference is correct.
- It is only in Annex B. Then you have written yourself an obligation that the standard does not demand. You are allowed to. Your auditor will simply hold you to your own rule.
- It is nowhere. Then delete the reference before someone else finds it.
The same applies to quotes and claims from your suppliers. If a provider writes that its system is “compliant with the EU AI Act under ISO/IEC 42001”, you now have the follow-up question: under which harmonised standard?
You quote a standard with its reference. And you say whether that reference contains a requirement or guidance.
What you can do on Monday: take a document you wrote yourself and look up the first five references to a standard. The hour is well spent before someone else does it in an audit.
Primary sources
- ISO/IEC 42001:2023, AI management systems, clauses 2, 6.1.2, 6.1.3, 8.2, 8.3, Annex A (Table A.1) and Annex B (iso.org)
- ISO/IEC 42006:2025, requirements for bodies providing audit and certification of AI management systems, Annex A, Table A.1 (iso.org)
- Implementing Decision (EU) 2026/2274 on the harmonised standard EN 18286:2026, Official Journal of the EU, 14 October 2026
- Der KI-Auditor, status of the EU AI Act and the standards
Frequently asked questions
What is the difference between Annex A and Annex B of ISO/IEC 42001?+
Annex A contains the 38 controls in Table A.1. Which of them apply is set out in the Statement of Applicability. Annex B gives implementation guidance for each control. It is also labelled normative, but an organisation may adapt the guidance or replace it with its own implementation (B.1).
Does ISO/IEC 42001 require human oversight of AI systems?+
There is no separate control for it. Human oversight appears in the implementation guidance of Annex B. What is required is defining objectives for responsible use (A.9.3) and using the system as intended (A.9.4). For high-risk systems the EU AI Act requires oversight.
What is the minimum duration of an ISO/IEC 42001 certification audit?+
For the initial audit, ISO/IEC 42006:2025 gives 3.5 auditor days in the smallest band of up to ten people in the AI life cycle for organisations that provide or use AI, 5 days for developers and 6.5 days for multiple roles. These are minimums before adjustments.
Does an ISO/IEC 42001 certificate make you compliant with the EU AI Act?+
No. ISO/IEC 42001 is not listed as a harmonised standard under the EU AI Act. Since 14 October 2026 only EN 18286:2026 has been listed. A certificate is groundwork and a signal to customers, but it creates no presumption of conformity.
How many controls does Annex A have?+
38 controls in nine topic areas from A.2 to A.10. The topic areas have ten objectives in total, because A.6 has two.
Author & expert review: Lars Zimmermann · ISO/IEC 42001 Senior Lead Auditor & Senior Lead Implementer · ISO/IEC 27001 Lead Auditor & Lead Implementer (PECB)
Last updated: 11 November 2026. Researched and reviewed to the best of our knowledge; not a substitute for individual legal advice.
Questions about your own case?
In a free 15-minute intro call we assess where you stand on ISO 42001, ISO 27001 and the EU AI Act, honestly and without a sales pitch.