Anyone procuring a high-risk AI system will sooner or later hear the same sentence: "We work to the European standards." What that sentence is worth in law is set out in three short Articles of the AI Act. Article 40 governs harmonised standards and the presumption of conformity attached to them. Article 41 lets the Commission adopt common specifications when those standards fail to arrive. Article 42 gives a presumption for two specific requirements: data from the setting in which the system is used, and cybersecurity.
Suppose a Dutch municipality buys a system that prepares applications for social assistance. The system ranks applications by the likelihood that further documents are needed and drafts advice per application; a caseworker decides. In the tender the municipality asks which standards the supplier applies. The answer: "We apply EN 18286, we are certified to ISO/IEC 27001 and we follow ISO/IEC 42001." The buyer and the privacy adviser want to know what that gives them, and what to ask where no standard yet exists for a requirement. The example is fictitious.
In short
A high-risk AI system that is in conformity with a harmonised standard, or part of one, whose reference has been published in the Official Journal of the European Union, is presumed to be in conformity with the requirements of Chapter III, Section 2, to the extent the standard covers them. For general-purpose AI models the same holds for the obligations of Chapter V, Sections 2 and 3 (Article 40(1)). Three limits follow from that sentence: no publication, no presumption; outside the coverage of the standard, no presumption; and a presumption is not a finding. When we searched EUR-Lex on 19 November 2026, one harmonised standard for AI had been published: EN 18286:2026 on quality management, by Implementing Decision (EU) 2026/2274 of 12 October 2026, published and in force on 14 October 2026. Article 41 lets the Commission adopt common specifications by implementing act when standards fail to arrive or fall short, with the same presumption; a provider that does not follow such a specification must justify that its solution is at least equivalent (paragraph 5). We found no such implementing act on that date. Article 42 gives a presumption for Article 10(4) where training and testing used data from the setting of use (paragraph 1), for the cybersecurity requirements of Article 15 where there is a certificate or statement under a scheme pursuant to Regulation (EU) 2019/881 (paragraph 2), and, since the Digital Omnibus on AI (Regulation (EU) 2026/1744), where Article 12(1) CRA, the Cyber Resilience Act, is met (paragraph 3). Where there is no standard, the provider itself describes how it meets the requirements (Article 17(1)(e) and point 7 of Annex IV). A standard does not replace a DPIA or your own assessment under Articles 25 and 32 GDPR.
This piece is about the legal mechanism: where a standard draws its effect from, how far that effect reaches and what applies when there is no standard. What EN 18286:2026 means in substance for quality management is covered in quality management under Article 17; what evidence to ask your supplier for about that standard, in the new AI quality standard. How the standardisation work at CEN and CENELEC is progressing is described in the acceleration of AI Act standards. How standards shape the choice of conformity assessment is explained in internal control or notified body, and how they reappear in the declaration, in the EU declaration of conformity and CE marking.
Where these Articles sit
Articles 40, 41 and 42 open Section 5 of Chapter III, on standards, conformity assessment, certificates and registration. They impose no requirements themselves. The requirements are in Section 2, Article 8 to Article 15: risk management, data, technical documentation, record-keeping, transparency, human oversight, and accuracy, robustness and cybersecurity. The provider's obligations, such as the quality management of Article 17, are in Section 3. Articles 40 to 42 say how a provider can show that it meets those requirements.
Two concepts come from Article 3. A harmonised standard is a harmonised standard within the meaning of the European standardisation regulation (point 27): a European standard adopted on the basis of a request made by the Commission for the application of Union harmonisation legislation (Article 2(1)(c) of Regulation 1025/2012). A common specification is a set of technical specifications providing means to comply with certain requirements of the AI Act (point 28). The same standardisation regulation says that compliance with a standard is not compulsory (Article 2(1) of Regulation 1025/2012). The Commission, too, writes on its page on AI Act standardisation that applying standards remains voluntary and that providers may choose any other framework to demonstrate compliance.
Article 40: harmonised standards
The route to a standard. The Commission issues standardisation requests covering all requirements of Section 2 and, as applicable, the obligations of Chapter V, Sections 2 and 3, on general-purpose AI models (Article 40(2), first subparagraph). It also asks for deliverables on reporting and documentation of energy and resource consumption, and consults the AI Board and stakeholders (also first subparagraph). It further requires that standards be clear and consistent with the standards for products under Annex I (second subparagraph). The current request is Implementing Decision C(2025) 3871 of 23 June 2025 to CEN and CENELEC. It asked for the standards and deliverables in Annex I to that decision to be drafted by 31 August 2025 (Article 1(1) of the decision) and expires on 28 February 2027 (Article 5 of the decision). According to the Commission it covers ten areas: risk management, governance and quality of datasets, record keeping, transparency, human oversight, accuracy, robustness, cybersecurity, quality management and conformity assessment. Whether that deadline was later adjusted we have not been able to establish; the decision anticipates, in its twentieth recital, that deadlines may need to be adjusted during execution.
From standard to legal effect. CEN and CENELEC draft the standard. The Commission then assesses, together with them, whether it complies with the request, and if so publishes its reference in the Official Journal without delay (Article 10(5) and (6) of Regulation 1025/2012). A Member State or the European Parliament can raise a formal objection; the Commission may then decide not to publish the reference, to publish it with restrictions, or later to withdraw it (Article 11(1) of Regulation 1025/2012). Only with publication in the Official Journal does the presumption of Article 40(1) arise.
The presumption. A system in conformity with a published harmonised standard or part of one "shall be presumed" to be in conformity with the requirements of Section 2, "to the extent that those standards cover those requirements or obligations" (Article 40(1)). Three limits follow from that sentence.
- Publication. A standard without a reference in the Official Journal gives no presumption, however good it is. That applies to international standards such as ISO/IEC 42001 and to draft standards. See also ISO/IEC 42001 versus the AI Act.
- Coverage. The presumption reaches no further than the requirements the standard covers. The standardisation request therefore asks CEN and CENELEC to describe in each harmonised standard the extent to which it covers one or more requirements (twelfth recital of C(2025) 3871). Whatever falls outside that coverage, the provider must substantiate in another way.
- Not a finding. The presumption is rebuttable. The Court of Justice put it this way in 2024: anyone who wishes to challenge the presumption for a product or service must demonstrate that it does not meet the standard, or that the standard is not fit for purpose (C-588/21 P, paragraph 76). It therefore changes what the provider has to demonstrate, but a market surveillance authority can still find that a system does not meet a requirement. Even a system that complies with the Regulation can be made subject to measures if it nevertheless presents a risk (Article 82(1)).
General-purpose AI models. For providers of such models the presumption works the same way. Until a harmonised standard is published, they may rely on codes of practice within the meaning of Article 56; a provider that does not adhere to an approved code (since the Omnibus: one the Commission has assessed as adequate under Article 56(6), see recital 41 of Regulation (EU) 2026/1744) and does not comply with a harmonised standard demonstrates alternative adequate means of compliance for assessment by the Commission (Article 53(4) and Article 55(2)). This is covered in vendor assurance for GPAI.
What the Digital Omnibus added. A final subparagraph was added to Article 40(2): the Commission requests the European standardisation organisations, without undue delay, to develop standardisation deliverables, including harmonised standards where appropriate, to facilitate joint compliance and the presumption of conformity with the requirements of Chapter III, Sections 2 and 3, and with the requirements of the Annex I harmonisation legislation (point 17 of Article 1 of Regulation (EU) 2026/1744). According to recital 21 of Regulation (EU) 2026/1744 this concerns operators that fall under both the AI Act and that product legislation, and those deliverables should help avoid duplicated testing and documentation.
What exists on 19 November 2026: EN 18286:2026
By Implementing Decision (EU) 2026/2274 of 12 October 2026 the Commission published the reference of EN 18286:2026, "Artificial intelligence: Quality management system for EU AI Act regulatory purposes". The decision appeared in the Official Journal on 14 October 2026 and entered into force that day (Article 2 of the decision). According to its third recital the standard concerns quality management systems for providers, including post-market monitoring processes. The decision refers to Article 40 in its first recital, but does not say for which requirements of the AI Act the standard gives a presumption, and attaches no restriction to the reference. The Commission writes on its standardisation page that the standard is designed to help providers comply with Article 17.
When we searched EUR-Lex on 19 November 2026 we found no other decision publishing references of harmonised standards in support of the AI Act. For the requirements of Section 2 themselves, such as risk management, data, record-keeping, human oversight and accuracy, there is therefore no harmonised standard yet.
An open point. Article 40(1) ties the presumption to the requirements of Section 2 and the obligations of Chapter V. Article 17 sits in Section 3. The standardisation request expressly asked for standards on Article 17 as well (tenth recital of C(2025) 3871), the Commission has published EN 18286 as a harmonised standard, and since the Omnibus Article 40(2) mentions Section 3 in connection with the presumption of conformity. Article 40(1) itself was not amended. The request itself describes the Article 40 presumption, in its fourth recital, as a presumption of conformity with the essential requirements of Articles 9 to 15. On the other side, the decision on EN 18286 states that the standard satisfies the requirements it aims to cover (fifth recital) and that compliance confers a presumption of conformity with the corresponding essential requirements (sixth recital). How far the presumption reaches for Article 17 is therefore, in our reading, not settled; we worked this out in the piece on Article 17. In practice: the standard is the most authoritative reference point for quality management there is, but do not present it as proof that Article 17 is complied with.
What a standard does and does not prove
| An applied, published harmonised standard | Does | Does not |
|---|---|---|
| Requirements the standard covers | Presumption of conformity for those requirements (Article 40(1)) | A finding that the system complies; the presumption can be rebutted |
| Requirements outside its coverage | Nothing | The provider substantiates those itself (Article 17(1)(e), point 7 of Annex IV) |
| Conformity assessment | For biometrics (point 1 of Annex III) the option of internal control, if standards or specifications cover all requirements of Section 2 and have been applied in full (Article 43(1)) | The assessment itself; that remains required (Article 16(f)) |
| Deployer obligations | Information to assess the supplier with | Compliance with Article 26 or Article 27; those obligations are the deployer's own |
| GDPR | At most one input to your own assessment | A DPIA (Article 35 GDPR) or compliance with Articles 25 and 32 GDPR |
| Standards without publication (ISO/IEC 42001, ISO/IEC 27001, drafts) | Support for the substantiation | A presumption under Article 40 |
For the systems in points 2 to 8 of Annex III, including the municipality's social assistance application, the provider carries out internal control under Annex VI, with or without a standard (Article 43(2)). For AI in products under Section A of Annex I: where the product legislation allows the manufacturer to opt out of a third-party assessment, it may use that option only if it has also applied harmonised standards or common specifications covering all requirements of Section 2 (Article 43(3), third subparagraph). That rule was already in the original text of the AI Act.
One more practical point: the Official Journal contains only the reference and the title of the standard, not the standard itself. The Court of Justice held in 2024 that harmonised standards form part of EU law by virtue of their legal effects, and that an overriding public interest justifies their disclosure on a request for access to Commission documents (CJEU 5 March 2024, Public.Resource.Org, C-588/21 P, paragraphs 80, 85 and 89). The AI Act standardisation request itself refers to that judgment (twenty-third recital of C(2025) 3871).
Article 41: common specifications
An exceptional fallback. The Commission may adopt, by implementing act, common specifications for the requirements of Section 2, or for the obligations of Chapter V, Sections 2 and 3, where two conditions are met together (Article 41(1)):
- the Commission has requested a harmonised standard, and the request has not been accepted by any European standardisation organisation, the standards have not been delivered within the deadline, the standards insufficiently address fundamental rights concerns, or the standards do not comply with the request (point (a)); and
- no reference to a harmonised standard covering those requirements has been published, and none is expected within a reasonable period (point (b)).
When drafting, the Commission consults the advisory forum of Article 67, adopts the act under the examination procedure of Article 98(2) (paragraph 1), and first informs the committee of Article 22 of Regulation 1025/2012 that it considers the conditions fulfilled (paragraph 2). Recital 121 of the AI Act calls common specifications an exceptional fallback solution, and asks the Commission to take technical complexity into account where that is the reason a standard is delayed (original text).
The same presumption, with a duty of its own. A system in conformity with a common specification is presumed to be in conformity with the requirements it covers (paragraph 3). If a harmonised standard covering the same requirements is later published, the Commission repeals the specification or the part concerned (paragraph 4). A Member State that considers a specification falls short informs the Commission with a detailed explanation, and the Commission amends the act if appropriate (paragraph 6). Paragraph 5 is the only part of these three Articles that directly requires something of the provider: if it does not comply with an adopted common specification, it must duly justify that its technical solutions meet the requirements to a level at least equivalent. The text does not say where that justification must be recorded. In our reading it belongs in the technical documentation, because point 7 of Annex IV asks there for the description of the solutions by which the provider meets Section 2.
The position on 19 November 2026. We found no implementing act on EUR-Lex establishing common specifications under Article 41. Whether the conditions are now met is for the Commission to assess. The deadline of the current request C(2025) 3871, 31 August 2025, has passed and most standards are not there, but point (b) also requires that publication is not expected within a reasonable period. As long as there is no specification, there is nothing to depart from, and paragraph 5 does not come into play.
What if there is no standard (yet)
For most requirements, that is the current situation. The Regulation has its own arrangement for it, and it rests on the provider.
- Quality management. The quality management system includes the technical specifications and standards the provider applies and, where the relevant harmonised standards are not applied in full or do not cover all requirements of Section 2, the means used to ensure that the system complies with those requirements (Article 17(1)(e)).
- Technical documentation. It contains a list of the harmonised standards applied in full or in part whose references have been published, and where none have been applied, a detailed description of the solutions adopted to meet Section 2, including a list of other relevant standards and technical specifications applied (point 7 of Annex IV). See technical documentation under Article 11.
- The declaration of conformity. It states the harmonised standards or other common specifications applied (point 6 of Annex V). If nothing is listed there, the provider used no standard and the substantiation has to come from the documentation.
- The state of the art. The requirements apply taking into account the intended purpose and the generally acknowledged state of the art (Article 8(1)). According to recital 121, harmonised standards should normally reflect that state of the art. Without a standard, the provider therefore has to show for itself what the state of the art is and why its choices fit it. More on this in Articles 7 and 8.
- Biometrics. For systems in point 1 of Annex III a notified body is required as long as there are no harmonised standards or common specifications, or as long as the provider has not applied them or has applied them only in part (Article 43(1), second subparagraph, points (a) to (c)).
International standards and draft standards are useful as support in that substantiation. They just give no presumption. The practical difference is that when a supervisor asks, the provider cannot point to the standard but has to explain why its own solution complies.
Article 42: three narrow presumptions
Paragraph 1: data from the setting of use. A system trained and tested on data reflecting the specific geographical, behavioural, contextual or functional setting within which it is intended to be used is presumed to comply with the relevant requirements of Article 10(4). That paragraph requires data sets to take into account, to the extent required by the intended purpose, the characteristics of that setting. The presumption needs no publication, but it is narrow: it concerns only paragraph 4. The data governance of paragraph 2 and the requirements of relevance, representativeness and freedom from errors in paragraph 3 fall outside it. Recital 122 of the AI Act speaks of a presumption for "the relevant measure" under the data governance requirement. See data and data governance under Article 10.
Paragraph 2: a European cybersecurity certificate. A system that has been certified, or for which a statement of conformity has been issued, under a cybersecurity scheme pursuant to Regulation (EU) 2019/881 whose references have been published in the Official Journal is presumed to comply with the cybersecurity requirements of Article 15, in so far as the certificate or statement covers them. Such schemes are adopted by the Commission by implementing act, on the basis of a candidate scheme prepared by ENISA (Article 49(7) of Regulation (EU) 2019/881), and certification is voluntary unless Union or Member State law provides otherwise (Article 56(2) of Regulation (EU) 2019/881). One example is the Common Criteria based scheme EUCC, adopted by Implementing Regulation (EU) 2024/482 and applicable since 27 February 2025, for ICT products. Two limits matter. The presumption covers only cybersecurity, not accuracy and robustness; recital 122 makes that clear. And it covers only what the certificate covers. Article 15(5) names AI-specific attacks, such as data poisoning, model poisoning and adversarial examples. In our reading a certificate for an ICT product or a component does not cover those by default. An ISO/IEC 27001 certificate is not a scheme pursuant to Regulation (EU) 2019/881 and does not give this presumption.
Paragraph 3: the Cyber Resilience Act. Where a high-risk system falls within Regulation (EU) 2024/2847 and the conditions of Article 12(1) CRA are met, it is deemed to comply with the cybersecurity requirements of Article 15 (paragraph 3, inserted by point 18 of Article 1 of Regulation (EU) 2026/1744). According to recital 19 of Regulation (EU) 2026/1744, this brings the rule of Article 12 CRA into the AI Act to make the interplay visible. Article 12(1) CRA sets three conditions, one of which is that the EU declaration of conformity under the CRA demonstrates that the level of Article 15 is achieved. The CRA applies from 11 December 2027 (Article 71(2) CRA). How that works out for cloud services and when the route is open is covered in accuracy, robustness and cybersecurity under Article 15.
What the Digital Omnibus on AI changed
Regulation (EU) 2026/1744 added the final subparagraph on joint standardisation to Article 40(2) (point 17 of Article 1 of Regulation (EU) 2026/1744), and inserted Article 42(3) (point 18). It also replaced Article 43(3) (point 19). The first subparagraph received a technical correction: for AI in products under Section A of Annex I, the quality management system of Article 17 is now assessed as well (recital 18 of Regulation (EU) 2026/1744). Under the second subparagraph, notified bodies notified under that product legislation may assess the AI systems under certain conditions, and apply for notification under the AI Act by 28 January 2028. The rule that a manufacturer can only work without a third party if it has applied standards or specifications covering all requirements of Section 2 was already there; new in the third subparagraph is that classification as high-risk under Article 6(1) does not force a third-party assessment that the product legislation does not require (recital 20 of Regulation (EU) 2026/1744). Where a system falls under both Section A of Annex I and Annex III, the provider follows the procedure of the product legislation (fourth subparagraph). Article 40(1) and (3), Article 41 and Article 42(1) and (2) were left unchanged. That follows from the list of amended provisions in Article 1 of Regulation (EU) 2026/1744 and from the consolidated text of 27 July 2026.
Main example: the municipality and the supplier's standards
The roles. The system helps assess whether someone is eligible for social assistance, an essential public assistance benefit; that falls under point 5(a) of Annex III. The supplier is the provider and carries conformity. The municipality is the deployer. It does not have to carry out a conformity assessment, but wants to know whether the supplier can, and it has its own obligations under Articles 26 and 27. In our reading, ranking applications from natural persons is profiling; the system is then always high-risk and the exception in Article 6(3) cannot be relied on (last subparagraph of Article 6(3)).
What the supplier's answer is worth. In our reading:
- "We apply EN 18286." That concerns the supplier's quality management, not the properties of the social assistance system. Ask which clauses it applies, for which system and version, and what evidence there is. See the new AI quality standard.
- "We are ISO/IEC 27001 certified." Useful for the organisation's information security, but not a certificate under Regulation (EU) 2019/881 and so no presumption under Article 42(2).
- "We follow ISO/IEC 42001." A management system standard without a published reference under the AI Act, and so without a presumption under Article 40.
For risk management, data, record-keeping, human oversight and accuracy, the answer therefore says nothing. There the supplier needs its own substantiation (Article 17(1)(e), point 7 of Annex IV).
What the municipality asks. In our reading, these four things:
- A coverage overview per requirement of Articles 9 to 15: which standard, which specification or which document of the supplier's own covers the requirement, and whether the reference of that standard is in the Official Journal.
- The data. On which data was the system trained and tested, and do they resemble the applications in this municipality? If the supplier relies on Article 42(1), it should be able to show why its data reflect the setting of use. The instructions for use contain, where appropriate, specifications for the input data or information on the data sets (Article 13(3)(b)(vi)), and the municipality itself ensures that its input data are relevant and sufficiently representative, to the extent it exercises control over them (Article 26(4)).
- Cybersecurity. Which tests did the supplier run against the attacks of Article 15(5), and does a certificate also cover the AI component? See Article 15.
- The declaration. Once the requirements apply, the EU declaration of conformity listing the standards or specifications applied (point 6 of Annex V).
In the tender. A municipality that, in an EU tender, refers to a standard in the technical specifications adds the words "or equivalent", and may not reject a tender where the tenderer proves by any appropriate means that its solution meets the requirements in an equivalent manner (Article 42(3)(b) and (5) of Directive 2014/24/EU). If it requires a certificate from a specific body, it also accepts certificates from equivalent bodies (Article 44(1) of Directive 2014/24/EU). In our reading it is therefore stronger to ask what the supplier demonstrates per requirement than merely to require a standard. Contract clauses are covered in AI procurement contracts and assessing an AI vendor.
The GDPR side. A standard under the AI Act does not replace your own assessment under the GDPR. If the processing is likely to result in a high risk, and in our reading that is to be expected when ranking social assistance applications, the municipality carries out a DPIA before the processing (Article 35(1) GDPR). Data protection by design and security of processing are the municipality's own obligations as controller, taking into account the state of the art (Article 25(1) GDPR and Article 32(1) GDPR). Even an approved GDPR certification mechanism is only an element for demonstrating compliance there (Article 25(3) GDPR and Article 32(3) GDPR), and it does not reduce the controller's responsibility (Article 42(4) GDPR). In our reading that applies all the more to an AI Act standard, which was not written for that purpose. As a public body the municipality also carries out a fundamental rights impact assessment (Article 27(1)); where the DPIA already meets an obligation, it may refer to those parts or include them (paragraph 4). If the system was already in use before 2 December 2027, the high-risk obligations apply by 2 August 2030 at the latest, or earlier on a significant change in design (Article 111(2)). See DPIA and FRIA side by side and the FRIA for municipalities.
Example 2: a bank with its own credit model
A bank develops its own model to assess the creditworthiness of individuals and uses it in its own lending process. That falls under point 5(b) of Annex III; the bank is provider and deployer at the same time. This example is fictitious too.
Quality management. As a financial institution subject to governance requirements under Union financial services law, the bank meets its quality management obligation by complying with those governance rules, except for Article 17(1)(g), (h) and (i): risk management, post-market monitoring and serious incident reporting. "To that end, any harmonised standards referred to in Article 40 shall be taken into account" (Article 17(4)). In our reading EN 18286:2026 therefore belongs in that assessment, even if the bank arranges its quality management through its existing governance.
Data from its own setting. If the model was trained and tested on applications from the bank's own Dutch customers and the bank uses it for those customers, in our reading it can rely on Article 42(1) for Article 10(4). If it later deploys the model in another market or for another customer group, that setting no longer matches the data, and in our reading it can no longer rely on the presumption for that use. So record per application which setting the data reflect.
Cybersecurity. An EUCC certificate for, say, a hardware module in the chain covers that component. For the AI-specific attacks of Article 15(5), in our reading the bank needs its own substantiation as long as no certificate or standard covers them.
Fundamental rights and GDPR. As deployer of a system under point 5(b), the bank carries out a fundamental rights impact assessment (Article 27(1)). The DPIA and the security obligation under the GDPR apply separately. See AI in credit decisions.
From when?
Articles 40, 41 and 42 sit in Section 5 of Chapter III. That Section is not among the exceptions in the third paragraph of Article 113, so it applies from 2 August 2026, the general date in the second paragraph. The requirements the presumptions concern apply later: from 2 December 2027 for systems under Article 6(2) and Annex III, and from 2 August 2028 for systems under Article 6(1) and Annex I (Article 113, third paragraph, point (c), as replaced by point 40 of Article 1 of Regulation (EU) 2026/1744). The reference of EN 18286:2026 has been in the Official Journal since 14 October 2026, but the standard only gains practical weight once Article 17 applies to a system. For general-purpose AI models the obligations of Chapter V have applied since 2 August 2025.
What to do now
As a deployer or buyer, such as a municipality:
- Ask per requirement, not per standard. Have the supplier state for each requirement of Articles 9 to 15 what it relies on, and whether the reference of that standard is in the Official Journal.
- Read "we follow the standards" as a question. ISO/IEC 42001 and ISO/IEC 27001 are useful, but give no presumption under Article 40 or Article 42.
- Ask about the data. Have the supplier show which setting training and testing reflect (Article 42(1)), and make sure your own input data are representative (Article 26(4)).
- In a tender, refer to a standard "or equivalent", and assess equivalent evidence.
- Do your DPIA and your fundamental rights impact assessment yourself. A supplier's standard is at most information for them.
As a provider:
- Build a coverage overview per requirement of Section 2, noting per row the standard, the status of its reference and what falls outside its coverage.
- Substantiate what no standard covers in the quality management system (Article 17(1)(e)) and the technical documentation (point 7 of Annex IV).
- Record which setting your data reflect if you want to rely on Article 42(1), and confine the conclusion to Article 10(4).
- Watch the Official Journal. A new reference switches a presumption on and can lead to the repeal of a common specification (Article 41(4)). If a specification arrives that you do not follow, write the Article 41(5) justification.
- Offering biometrics or AI in products? Check whether your route to a conformity assessment without a notified body depends on full application of standards (Article 43(1) and (3)).
Want to know which AI Act and GDPR obligations come into view for your use case, and what your role is? The case check lets you describe the use case in a few questions.
Frequently asked questions about harmonised standards and the presumption of conformity
Sources
Newsletter
Every Tuesday, the AI Act week ahead in 5 minutes
A practical briefing on deadlines, new guidance and enforcement, so you know what matters this week. No spam and you can unsubscribe in one click.
Practical and short · No spam · One-click unsubscribe