In accordance with or based on: one word, two audit scopes
Write “in accordance with ISO 19011” in your procedure and a guideline becomes your own requirement. The certification body must then audit against it.
In short
“In accordance with” is a statement of conformity: you declare that you comply with a standard in full. “Based on” only names an orientation. Since ISO/IEC 17021-1 obliges the certification body to take your own documentation as an audit criterion too, this one phrase decides what you are audited against.
Auf Deutsch lesen: deutsche Fassung
Update of 15 October 2026. When I wrote this text, no harmonised standard for the AI Act had yet been listed in the Official Journal. Since 14 October 2026 there is the first one: EN 18286:2026, Implementing Decision (EU) 2026/2274. It concerns the quality management system of providers of high-risk AI systems. This changes nothing at the core. Whoever writes “in accordance with the EU AI Act” claims conformity with the entire legal act, and there is still no presumption for that. The two passages below, in the section on AI management systems and in the questions, state the position as at 15 October 2026.
In every second procedure I get to see there is a sentence like this: internal audits are conducted in accordance with ISO 19011. The sentence looks harmless. It is the most expensive one in the whole procedure. Whoever writes it has extended their own audit scope without noticing, and the certification auditor may take them at their word. A difference of a few words decides what is measured against in the next audit.
The certification auditor does not only audit the standard
Most people assume that in a certification audit the standard is audited and nothing else. That is wrong, and demonstrably so. Certification bodies work to ISO/IEC 17021-1, which is the standard against which they themselves are accredited. Its clause 9.2.1.4 defines what the audit criteria must consist of, and names two sources: the requirements of the normative document used as the basis, and the processes and documentation of the management system that the audited organisation has developed itself. That is not at the auditor’s discretion. The clause is worded as a must.
ISO 19011 takes the same line. Term 3.8 defines audit criteria as a set of requirements against which objective evidence is compared. The second note to it lists everything that can be such a requirement, and there policies, procedures and work instructions are explicitly named alongside legal requirements and contracts. Term 3.24 makes it finally unambiguous: a specified requirement is one that has been stated, for example in documented information.
Your own procedure is an audit criterion. Not because an auditor is strict, but because the accreditation standard says so.
Something follows from this that is regularly overlooked in everyday work: you are co-writing your own audit yardstick. Every sentence in your documentation that makes a stipulation becomes a question in the audit. Whoever writes that suppliers are evaluated annually is asked where last year’s evaluation is. Whoever writes that every training course ends with an effectiveness check is asked for the check. That is not harassment. It is exactly the process that an audit describes.
But the matter also has a flip side, and it works for you. Under ISO 19011, term 3.11, an audit finding is the result of the evaluation of evidence against audit criteria. So no criterion, no finding. If an auditor objects to something that is neither in the standard nor in your own documentation, the yardstick is missing, and the objection does not hold. The appropriate reaction to that is not a debate, but a friendly question: against exactly which criterion is this a nonconformity? Whoever knows their own documents can ask this question without friction. Whoever does not know them debates opinions.
That is exactly why tidying up your own wording is not a chore for document control, but preparation for the next audit. You determine what is talked about. Everything you commit to, you can evidence; nothing you have not committed to needs to be evidence. Both together are the difference between an audit that gives you something and one that you sit out.
ISO 19011 is a guideline, not a catalogue of requirements
Now comes the part that makes the matter expensive in the first place. ISO 19011 has been available in its fourth edition since May 2026; it replaces the 2018 version and has been technically revised; what was extended above all is the guidance on remote audits, and Annex A now covers virtual locations. More important than any of these changes, however, is the first line of the scope, and it has always read the same: the document provides guidance. It is a guideline.
A guideline contains recommendations, not requirements. That is why nobody can certify you to ISO 19011, and that is why nobody can write a nonconformity against ISO 19011 either. There is nothing in it to fulfil. As long as you treat the standard as what it is, it is non-binding and still useful.
The moment you write “in accordance with”, that tips over. You pull the recommendations of the guideline into your own documented information and thereby make them your requirement. After that the auditor does not audit the standard, he audits your commitment. And your commitment then reads, in essence: we comply with everything that is recommended there. What can fall due as a result is a whole list:
- an audit programme with defined objectives, not just an annual plan with dates
- the risks and opportunities of the audit programme evaluated and documented
- competence criteria per auditor defined, evaluated and maintained
- the audit programme monitored, evaluated and improved, with evidence of this
- audit reports with the contents that the guideline provides for them
None of this is unreasonable. A company that runs its audit programme this way runs it well. The point is a different one: it has to be your decision and not the by-product of a wording that someone took over from a template four years ago. Whoever commits must be able to deliver.
What really distinguishes the two wordings
“In accordance with” is a statement of conformity. You are claiming conformity with a document, and with all of it. “Based on” is a statement of origin. You are saying where your approach comes from, without committing yourself to every single recommendation. Both are legitimate. They simply mean different things, and that is exactly the distinction hardly anyone makes consciously.
It is easiest to see in three sentences that describe the same procedure and produce three different audit scopes:
- Internal audits are conducted in accordance with ISO 19011. The auditor may treat every recommendation of the guideline as your own stipulation.
- Internal audits are conducted based on ISO 19011. The auditor audits what else you have stipulated, not the guideline.
- Audit planning follows the approach in ISO 19011, clause 5. The evaluation of competence is governed by procedure QM-07. You name what you adopt, and the audit scope is fixed.
The third variant is the one that holds best in the audit, and it is at the same time the most honest. It says which part you make your own, instead of pointing wholesale at a document that contains dozens of pages of recommendations. The same goes for everything else in your documents that begins with “in accordance with”: legal provisions, customer requirements, industry rules. Whoever names the yardstick should have read it beforehand.
A side effect that is easily overlooked: the phrase is not only in the procedure. It is in quotations, in service descriptions, on websites. And under ISO 19011, term 3.8, contractual obligations are audit criteria as well. What you commit to towards a customer can come back to you in that same customer’s second-party audit.
With AI management systems it gets expensive faster
The same mechanism applies to ISO/IEC 42001, with one difference: the material is new, and the documents are only just being written. Almost every company that builds an AI management system draws up an AI policy in line with Annex A.2.2. What is in this policy is an audit criterion from the day of its approval. Whoever writes in it that every use of AI is assessed in advance has committed to an advance assessment, and for every use, including the one nobody thought of when writing.
Added to this is a particular feature of the standard that amplifies the effect. Clause 6.1.3 requires a Statement of Applicability: a list of the necessary controls with the justification for why they were included or excluded. This statement is the densest collection of self-commitments that a management system produces. Every line in it is a commitment, and every commitment is auditable. I have yet to experience an audit in which it was not opened.
And then there is the sentence that can now be read on many vendor websites: our system is developed in accordance with the EU AI Act. The same trap, only with a legal consequence instead of a nonconformity. Whoever claims conformity with a legal act must be able to evidence it. The presumption of conformity that would help here exists via harmonised standards and via common specifications, which do not exist so far. Only a single standard is listed so far: EN 18286:2026 on the quality management system of providers of high-risk AI systems, since 14 October 2026 (Implementing Decision (EU) 2026/2274). It does not establish a presumption for the remaining requirements of the AI Act. “We are guided by the requirements of the AI Act” says the same thing, without the claim.
Naming a standard costs nothing. Naming it with the words “in accordance with” costs the evidence.
What you can check tomorrow morning in twenty minutes
The effort is laughably small measured against what it prevents. Search your document control system for the phrases “in accordance with” and “according to”, plus every standard abbreviation you use. In an SME system that is rarely more than twenty to thirty hits. Go through them one by one and ask three questions:
- Have I read the document I am pointing to here, and in the version that currently applies?
- Can I evidence every requirement from it if someone asks tomorrow?
- Did I want to claim conformity here at all, or did I only want to say where my approach comes from?
For every hit where one of the three answers is no, you change a phrase. “In accordance with” becomes “based on”, or you name the clause that you actually adopt. That is a change to documented information like any other: increment the version, approve, distribute. Half an hour for the whole inventory is realistic.
A case from a company I supported shows how quickly this tips over. There the audit procedure contained the usual sentence with “in accordance with ISO 19011”. In the surveillance audit the auditor asked for the competence criteria for the internal auditors, because the guideline deals with this in detail and the procedure had referenced it. There were none. There was a course certificate from 2019 and good will. A wording turned into a nonconformity, and the cause was not a lack of competence, but a phrase.
The remedy is unspectacular and costs no consultancy: in your documentation, name only yardsticks that you know and can keep to. Everything else belongs in the justification, not in the stipulation. And if you have ten minutes this afternoon: open your internal audit procedure and read the first paragraph. Does it say “in accordance with”?
Primary sources
Frequently asked questions
Is an auditor even allowed to audit against my own documentation?+
He is in fact obliged to. ISO/IEC 17021-1 stipulates in clause 9.2.1.4 that the audit criteria comprise both the requirements of the normative document and the processes and documentation that the organisation has developed itself. ISO 19011 supports this through the term audit criteria, which explicitly includes policies, procedures and work instructions. A nonconformity against your own stipulation is therefore a perfectly normal nonconformity.
Can I receive a nonconformity against ISO 19011?+
Not directly. ISO 19011 is a guideline and contains recommendations, not requirements; the scope says so in its first sentence. Indirectly, very much so: if your own documentation references the standard with “in accordance with”, its recommendations become your specified requirement, and that can be audited against. The nonconformity is then formally against your procedure, and in substance against the guideline.
Do I now have to write “based on” everywhere?+
No, and as a blanket approach that would also be weak. The better solution is to name the clause that you really adopt, for instance the approach to audit programme planning. Then the audit scope is fixed and you do not look as though you were trying to talk your way out. “In accordance with” is right where you actually fulfil the requirement in full and can evidence it, so certainly for a binding management system standard.
Does this also apply to statements on our website or in a quotation?+
Yes. ISO 19011 explicitly lists contractual obligations in the definition of audit criteria. What you commit to towards a customer can come back to you in that customer’s supplier audit, and with statements about legal acts there is also the unfair competition law side. For the EU AI Act the following applies in addition: a presumption of conformity exists via harmonised standards whose reference is published in the Official Journal, and via common specifications, which have not been adopted so far. Since 14 October 2026 only EN 18286:2026 has been listed (Implementing Decision (EU) 2026/2274), and it concerns only the quality management system of providers of high-risk AI systems.
Author & expert review: Lars Zimmermann · ISO/IEC 42001 Senior Lead Auditor & Senior Lead Implementer · ISO/IEC 27001 Lead Auditor & Lead Implementer (PECB)
Last updated: 10 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.