FAQEU

EU AI Act Do you need a notified body?

Some high-risk AI systems need an independent assessment by a . Others use the provider's internal assessment. Article 43 and the applicable product law determine the route.

Check the high-risk classification first, then the standards used, assessment evidence, declaration, CE marking and registration.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 21, 2026
Overview

A high-risk classification does not automatically require a , the organisation authorised to carry out specified independent conformity checks. Annex III biometric systems have conditional route choices. Annex III points 2-8 use internal control. Covered products follow their product-law route. Keep the classification and route decision with the release records.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

Which systems need a notified body?

For Annex III point 1 biometric systems, a provider may choose Annex VI internal control or Annex VII notified-body assessment when it demonstrates compliance using the relevant harmonised standards or, where applicable, common specifications. Articles 40 and 41 set the standards and specifications rules.

Annex III point 1 is the biometrics category. It covers specified remote biometric identification systems, biometric categorisation systems using sensitive or protected characteristics or inferred attributes, and emotion recognition systems, subject to the precise Annex III wording and exclusions. It should not be confused with every system that processes a face, voice, or other biometric data.

For those biometric systems, Annex VII becomes mandatory if relevant standards and specifications are unavailable, a relevant is unused or only partly applied, or available common specifications are unused. It also applies to the restricted part where a harmonised standard was published with a restriction.

Annex III points 2-8 use Annex VI internal control. Article 43 requires no notified-body involvement for that route.

For high-risk AI systems covered by Union harmonisation legislation in Section A of Annex I, Article 43(3), as replaced by Regulation (EU) 2026/1744 from 27 July 2026, keeps the conformity route under the applicable product law and makes the AI Act Section 2 requirements part of that assessment. If that product law permits assessment without a third party when all relevant harmonised standards are applied, inclusion of a high-risk AI safety component does not by itself force third-party assessment. If the same system is also listed in Annex III, the product-law route controls.

For Article 6(1) systems related to Annex I Section B products, amended Article 2(2) limits which AI Act provisions apply directly. Use the relevant sector law instead of assuming the Annex VI/VII route applies. For Section A systems, amended Article 43(3) also includes Article 17 quality-management assessment in the product procedure.

  • Start with the legal basis for high-risk classification: Annex III point 1, Annex III points 2-8, or Annex I Section A product legislation.
  • Record which harmonised standards or common specifications were applied in full, applied in part, unavailable, or published with restrictions.
  • Use Annex VII when Article 43 makes notified-body assessment mandatory for the route, not simply because the system is high risk.
  • A after assessment triggers a new . For systems that continue to learn, Article 43(4) excludes changes predetermined at the initial assessment and included in the technical documentation; record the limits of those planned changes.

Does EN 18286:2026 remove the need for a ?

No. Implementing Decision (EU) 2026/2274 cited EN 18286:2026 on 14 October 2026, with a presumption of conformity limited to covered requirements. Annex ZA maps Article 17(1) quality management system requirements and the first sentence of Article 11(1), with conditions; Article 17(2)-(4) remain uncovered. EN 18286 alone does not cover all Chapter III Section 2 requirements or establish the Annex III point 1 conditions for Annex VI internal control. Where Article 43 requires Annex VII, notified-body assessment of the quality management system and technical documentation still applies. The citation does not change application dates. See the harmonised standards and quality-management guide for the coverage conditions and evidence map.

Do all high-risk systems need a ?

No. Article 43 sends Annex III points 2 to 8 high-risk AI systems to Annex VI internal control without notified-body involvement. For Annex III point 1 systems, the provider may choose Annex VI or Annex VII when it applies the relevant harmonised standards or common specifications, but must use Annex VII in the circumstances listed in Article 43(1). Annex I product-law systems follow the conformity route in the applicable product legislation.

What should the route decision record?

It should identify the system, intended purpose, high-risk basis, Article 43 route, standards or common specifications relied on, whether Annex VI or Annex VII applies, any used, and whether a or planned change would reopen the assessment.

When do conformity-assessment duties apply?

Regulation (EU) 2026/1744, published on 24 July 2026 and entering into force on 27 July 2026, sets different dates for Chapter III Sections 1 to 3, except Article 6(5). The duties apply from 2 December 2027 to systems classified as high-risk under Article 6(2) and Annex III, and from 2 August 2028 to systems classified as high-risk under Article 6(1) and Annex I. Article 111 contains separate transition rules for systems placed on the market or put into service before the applicable date.

Question 2

What does internal control require?

Under Annex VI, the provider checks its own evidence. It must verify that the quality management system meets Article 17, examine the technical documentation against Chapter III Section 2, and check that design, development and post-market monitoring match that documentation.

Prepare the technical documentation before market placement or first use and keep it current. Article 11 requires enough information for authorities and notified bodies to assess compliance. Annex IV lists the contents: purpose, versions, development, data, oversight, testing, cybersecurity, risk management, standards, declaration and monitoring.

  • Maintain Article 17 quality-management records covering regulatory strategy, design control, development, validation, standards, data management, risk management, post-market monitoring, serious-incident reporting, authority communications, record keeping, resources, and accountability.
  • Keep Article 11 and Annex IV technical documentation current with the system version, intended purpose, interfaces, data, testing, human oversight, cybersecurity, risk management, standards, declaration of conformity, and post-market monitoring plan.
  • Retain the Article 18 evidence set for 10 years after the high-risk AI system is placed on the market or put into service.
  • Link release gates to the provider duties in Article 16: , EU declaration of conformity, CE marking, and Article 49 registration before market placement or service.

Is internal control self-certification?

The provider performs the checks without a . It must still verify the Article 17 quality management system, examine the technical documentation against the high-risk requirements, and check that design, development and monitoring match the file. Keep evidence of those checks.

Which documents must be ready before release?

At minimum, the provider should have the Article 11 technical documentation, Article 17 quality-management documentation, applicable logs and test evidence, the conformity route decision, the Article 47 EU declaration of conformity, CE-marking evidence, and Article 49 registration evidence where registration applies.

Question 3

What does a notified body assess?

Under Annex VII, a reviews both the provider's quality management system and the system's technical documentation. The application identifies the provider and all AI systems covered by that management system. Include technical documentation for each system, Article 17 management-system records, procedures to keep it effective, and a declaration that the same application was not filed with another body.

The body may ask for evidence or tests and carry out tests itself. If other reasonable means are insufficient, it may seek access to training and trained models, subject to intellectual-property and trade-secret protection. It issues a Union technical documentation assessment certificate if the system conforms, or refuses with reasons.

Approval brings continuing surveillance, including periodic audits of the quality management system. Notify the body of intended changes to that system or the covered-system list, and of AI-system changes that could affect compliance or intended purpose.

  • Prepare one package for the quality management system and one for the AI system technical documentation.
  • Do not lodge the same Annex VII application with multiple notified bodies at the same time.
  • Plan how the provider will supply further evidence, testing, data-set access, or model access if the requests it within the limits of Annex VII.
  • Track certificate conditions, supplements, refusal reasons, surveillance audit reports, and notified-body change decisions as controlled release records.

Can we choose any ?

For Annex VII assessment, Article 43 permits provider choice within the body's notified scope, subject to the authority routes. The relevant market surveillance authority acts as for systems intended for law-enforcement, immigration or asylum authorities, or Union institutions, bodies, offices or agencies. For systems within amended Article 75(1) AI Office competence that require third-party assessment, Article 75(1e) makes the AI Office responsible and provides for designated notified bodies acting on the Commission's behalf.

What should procurement ask before appointing one?

Ask which AI Act activities the body is notified for, its identification number, scope, evidence intake requirements, assessment timeline assumptions, certificate and surveillance process, subcontractor use, confidentiality handling, and how it treats intended changes or substantial modifications.

Question 4

What must be ready after the assessment?

Prepare an EU declaration of conformity for each high-risk system under Article 47. It may be written, machine-readable, physical or electronically signed. Identify the system, state compliance with Chapter III Section 2, include Annex V information and translate it for relevant authorities. Keep it current and available to national competent authorities for 10 years.

Article 48 requires CE marking for high-risk AI systems. For digital high-risk AI systems, a digital CE marking can be used only when it is easily accessible through the system interface or through an accessible machine-readable code or other electronic means. Where a was responsible for the Article 43 , its identification number follows the CE marking and is also indicated in promotional material that mentions CE conformity.

Article 49 registration is separate from CE marking and must be checked before release. Providers or authorised representatives register themselves and Annex III high-risk AI systems in the EU database before placing them on the market or putting them into service, except for point 2 of Annex III, which is registered at national level. Providers also register systems they concluded are not high risk under Article 6(3). Public authorities, Union institutions, bodies, offices, agencies, and persons acting on their behalf have deployer registration duties for covered Annex III systems before use.

Article 46 lets a market surveillance authority authorise a specific high-risk system for a limited period before assessment is complete. The reasons must meet its exceptional public-security, life-and-health, environmental or key-infrastructure conditions. Complete assessment without undue delay. The authority must grant the permission. For Annex I Section A products, Article 46(7) limits the exception to the applicable product-law route.

  • Attach the Article 47 declaration to the system record and include Annex V content such as system identification, provider identity, responsibility statement, conformity statement, standards or common specifications, notified-body details where applicable, and signature information.
  • Confirm the CE mark location: interface, machine-readable code, packaging, or accompanying documentation, depending on the system form.
  • When a was involved, include its identification number after the CE marking and in CE-conformity promotional material.
  • Submit and maintain Article 49 and Annex VIII registration information where the system or deployer falls within the registration rules.

Does CE marking replace registration?

No. CE marking indicates conformity with the AI Act and applicable Union law, while Article 49 requires registration for specified high-risk AI systems and certain deployer uses in the EU database or, for Annex III point 2 systems, at national level.

What should a launch reviewer check?

Check that the Article 43 route is complete, technical documentation and quality-management records are current, the EU declaration of conformity is signed and retained, CE marking is correctly applied, notified-body certificate details are captured where applicable, and Article 49 registration duties have been completed or marked not applicable with the legal reason.

Primary sources

References and citations

ai-act-service-desk.ec.europa.eu2 citations
Referenced sections
  • Official AI Act Service Desk page summarising Article 49 registration before market placement, service, or covered deployer use.
  • Official AI Act Service Desk article explaining Article 49 registration duties for providers and certain deployers.
"Registration"
cencenelec.eu2 citations
Referenced sections
  • Official standards-body publication announcement for the provider QMS standard.
  • Official publication announcement for the provider QMS standard; the later decision controls its citation status.
eur-lex.europa.eu2 citations
Referenced sections
  • Articles 1-2, recital 6 and the Annex establish the 14 October 2026 citation and its effect limited to covered requirements.
  • Articles 1-2, recital 6 and the Annex establish the 14 October 2026 citation and presumption limited to covered requirements.
etsi.org2 citations
Referenced sections
  • Technical standards context for conformity assessment, quality-management evidence, testing, and technical documentation for AI-enabled systems.
  • Technical context explaining that conformity assessment can be third-party or internal-control based and focuses on technical documentation.
"technical documentation"
webgate.ec.europa.eu2 citations
Referenced sections
  • European Commission Single Market Compliance Space page for checking notified bodies by legislation and related notified-body listings.
  • European Commission Single Market Compliance Space page for checking notified bodies by legislation.
"Notified Bodies"
eur-lex.europa.eu
Referenced sections
  • Primary legal source for Article 43 conformity assessment routes, Annex IV technical documentation, Annex V declarations, Annex VI internal control, Annex VII notified-body assessment, CE marking, and registration annexes.
"Conformity assessment"
eur-lex.europa.eu
Referenced sections
  • Primary annex for notified-body assessment of quality management systems, technical documentation, certificates, changes, and surveillance.
"assessment of the technical documentation"
eur-lex.europa.eu
Referenced sections
  • Primary legal text for the Article 43 split between Annex VI internal control, Annex VII notified-body assessment, Annex I product-law conformity routes, and the content of Annexes VI and VII.
"Conformity assessment"
eur-lex.europa.eu
Referenced sections
  • Primary legal text for EU declarations of conformity, CE marking, notified-body identification numbers, and registration duties.
"EU declaration of conformity"
eur-lex.europa.eu
Referenced sections
  • Binding amendment published on 24 July 2026, entering into force on 27 July 2026, which replaces Article 43(3), clarifies product-law conformity routes, and moves the Chapter III application dates to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems.
"The classification of a product as a high-risk AI system"
Show all related guides (34)

When must you disclose AI use? | EU AI Act

Check AI interaction notices, technical content marking, biometric notices, deepfake and text disclosures, exceptions, accessibility and deadlines.

When must you report a serious incident? | EU AI Act

Check serious-incident outcomes, reporting roles, 15-, 10- and two-day deadlines, authority recipients, corrective action and the separate model route.

Who needs a rights impact assessment? | EU AI Act

Check who needs an Article 27 fundamental rights impact assessment, what it must cover, and how privacy assessments, notification and registration fit.

Common questions, clear answers | EU AI Act

Clear answers on AI Act scope, risk categories, provider and user duties, general-purpose models, disclosures, rights, assessments and deadlines.

EU AI Act deadlines and compliance calendar

Find the AI Act deadline for your system or model. Check high-risk dates, transparency duties, older-model transitions and the evidence to prepare.

EU AI Act fundamental rights impact assessments

Check who needs an Article 27 fundamental rights impact assessment, what it must contain and how DPIA reuse, notification and registration work.

EU AI Act GPAI model evidence checklist

Collect model documentation, integration information, copyright records and training summaries. Add testing, incident and security records for systemic risk.

EU AI Act monitoring and serious incidents

Set up high-risk AI monitoring, identify serious incidents and check reporting deadlines, recipients, deployer escalation and corrective action.

EU AI Act penalties and fines

Check the AI Act fine tiers, smaller-organisation caps, GPAI provider fines and the facts authorities consider when deciding a penalty.

EU AI Act serious incident reporting steps

Check serious-incident harm, preserve evidence and choose the reporting deadline and recipient for high-risk AI systems and systemic-risk GPAI models.

EU AI Act timeline and phased deadlines

See which AI Act rules apply now and what comes next. Check high-risk dates, older-model transitions and the difference between legal and standards dates.

EU AI Act vs ISO/IEC 42001

Compare AI Act legal duties with ISO/IEC 42001 management-system requirements. See which records can be reused and what certification does and does not cover.

EU AI Act vs NIST AI RMF

Compare AI Act legal duties with the voluntary NIST AI RMF. Map risk records to specific requirements and identify legal steps that need separate evidence.

EU AI Act: Check whether the Act applies

Use five checks to establish AI Act scope, exclusions, your role, risk categories and evidence for the decision.

EU AI Act: Choose a high-risk assessment route

Choose between provider-run internal control, notified-body assessment and a product-law procedure before release.

EU AI Act: Classify a tool before approval

Classify an AI tool or model before purchase or release. Check EU scope, prohibited uses, high-risk rules, transparency and GPAI duties.

EU AI Act: Compliance checklist

Check each AI tool, decide which duties apply, and give every action an owner and evidence link.

EU AI Act: Conformity assessment

Some high-risk systems use a provider-run assessment. Others need an authorised independent assessor or a product-law assessment.

EU AI Act: Does it apply to you?

Check whether the AI Act applies to your system or model, identify your provider or deployer role, and keep evidence for the decision.

EU AI Act: Duties for general-purpose AI models

Check GPAI provider duties for documentation, integrator information, copyright and training summaries, plus extra requirements for systemic-risk models.

EU AI Act: High-risk requirements

High-risk providers must meet system requirements before supply. Deployers must use and monitor the system under the provider's instructions.

EU AI Act: High-risk system checklist

Check the system's risk controls, data, documentation, logs, instructions, human oversight and testing before release.

EU AI Act: Is your use case high-risk?

Find high-risk AI examples in recruitment, banking, education, healthcare, public services and products. Check Article 6 conditions and exceptions.

EU AI Act: Plan your compliance work

Build a compliance plan for each AI tool: your role, the duties that apply, the evidence needed and the person responsible.

EU AI Act: Standards and quality management

Use EN 18286:2026 to organise provider quality-management procedures and keep evidence that they work for each high-risk system.

EU AI Act: Technical file and evidence templates

Build the technical file and provider records for a high-risk AI system, with owners and evidence links for each field.

EU AI Act: When must you disclose AI?

Check Article 50 chatbot notices, synthetic-output marking, biometric notices, deepfake disclosures and public-interest text exceptions.

EU AI Act: Which AI uses are banned?

Check Article 5 prohibited AI practices, the narrow exceptions, evidence to retain and the new content prohibitions from 2 December 2026.