Presumption of conformity
The legal effect created by compliance with a harmonised standard listed in the Official Journal. A provider that complies with the relevant harmonised standards covering Article 17 (once EN 18286 is listed) is presumed by the competent authorities to have met the requirements of Article 17, without needing to separately demonstrate how each requirement is met. The presumption is rebuttable: a competent authority may present evidence that the standard was not correctly applied, or that the requirements are nonetheless not met despite standard compliance, and the presumption can be challenged. Harmonised standards also cover only the specific requirements mapped in Annex ZA of the standard; any Article 17 requirement not covered by the harmonised standard must still be demonstrated separately.
Defined in 4 GAGE programs, which carry 10 distinct definitions of it. The wording above is taught in EU AI Act Implementation Expert.
How each discipline defines it
The same term does different work depending on who is using it. These are the definitions as each program teaches them, unedited.
The legal benefit available to a provider whose system conforms to a harmonized standard that has been cited in the Official Journal of the EU as supporting a specific Article requirement. When a harmonized standard covers the relevant requirement (for example, Article 17 quality management, once prEN 18286 is published as a harmonized standard and cited in the Official Journal), a system meeting the standard is presumed to conform to the covered requirement. A critical caveat for current compliance planning: until a standard is formally cited in the Official Journal, relying on a draft or enquiry-stage standard (such as prEN 18286 in its current state) carries no formal presumption of conformity. A draft standard can be used as supportive evidence of a quality approach, and NCAs may treat it favorably in practice, but it does not trigger the legal presumption. Technical files built around draft standards should acknowledge this distinction explicitly, so that the NCA reviewer understands the reliance is on the standard's technical content as best-practice evidence, not on the legal presumption mechanism. (see Topic 4.0)
The legal benefit, under the EU AI Act, of following a designated harmonized technical standard: a provider that meets the standard is presumed to meet the underlying legal requirement it operationalizes. China's TC260-published GB and GB/T standards serve a similar practical function, giving a provider a concrete technical path to satisfying the GenAI Measures and Labeling Measures, but China's system has no formal "presumption of conformity" doctrine of its own; meeting a GB or GB/T standard is strong evidence of compliance, not a codified legal shield the way EU harmonized standards are.
A legal mechanism by which conforming to a designated standard makes you presumed to comply with the corresponding legal requirement. It is the one common bridge by which a voluntary standard gains legal force, and it exists only because a law chooses to grant it; it is typically limited to a specific requirement and is rebuttable.
the EU AI Act mechanism by which a GPAI provider who follows an approved Code of Practice (such as the GPAI Code of Practice) is presumed to meet the corresponding legal obligations, reducing the administrative burden of proving compliance through other means.
The legal effect created by compliance with a harmonised standard listed in the Official Journal. A provider that complies with the relevant harmonised standards covering Article 17 (once EN 18286 is listed) is presumed by the competent authorities to have met the requirements of Article 17, without needing to separately demonstrate how each requirement is met. The presumption is rebuttable: a competent authority may present evidence that the standard was not correctly applied, or that the requirements are nonetheless not met despite standard compliance, and the presumption can be challenged. Harmonised standards also cover only the specific requirements mapped in Annex ZA of the standard; any Article 17 requirement not covered by the harmonised standard must still be demonstrated separately.
Where it is taught
The exact lessons this term appears in. The first 7 topics of every program are free with a free account.
- Standards versus law: what certification buys you and what it never will · The World's Rulebooks, AI Governance: Applied Mastery
- Quality Management System (Article 17) · High-Risk AI Requirements: The Technical File, EU AI Act Implementation Expert
- Assembling the Technical File · High-Risk AI Requirements: The Technical File, EU AI Act Implementation Expert
- Harmonized Standards and Presumption of Conformity · Standards and Conformity Assessment, EU AI Act Implementation Expert
- Common Specifications When Standards Lag · Standards and Conformity Assessment, EU AI Act Implementation Expert
- Claiming Conformity: What You Can and Cannot Assert · Standards and Conformity Assessment, EU AI Act Implementation Expert
- Conformity Assessment Routes (Articles 43 to 47) · Standards and Conformity Assessment, EU AI Act Implementation Expert
- National Competent Authorities and Multi-State Deployment · Governance, Sandboxes, and SME Support, EU AI Act Implementation Expert
Terms it appears with
Not an alphabetical neighbourhood: these are the terms taught in the same lessons, ranked by how often they appear together.