Annex III high-risk AI systems: what falls in scope and how to validate classification
As of 18 November 2026 · checked against Regulation (EU) 2024/1689 and Regulation (EU) 2026/1744
Information only, not legal advice. Classification under Annex III has direct legal consequences. Confirm any concrete decision with qualified counsel and the competent national authority.
Annex III of Regulation (EU) 2024/1689 is the operative list that determines whether an AI system is high-risk by virtue of its intended purpose. If your system is listed, you inherit the full Chapter III obligations: risk management, data governance, technical documentation, logging, human oversight, conformity assessment, post-market monitoring. The obligations apply to Annex III systems from 2 December 2027. The Digital Omnibus moved that date from 2 August 2026, see the deadline timeline. This page maps the eight Annex III areas, walks through the Article 6(3) derogation that lets some providers escape, and shows how to document the classification decision.
The eight Annex III areas
| Area | Examples | Typical builders affected |
|---|---|---|
| 1. Biometrics | Remote identification, emotion recognition, biometric categorisation | IDV vendors, access control, retail analytics |
| 2. Critical infrastructure | Safety components in the management and operation of critical digital infrastructure, road traffic, and the supply of water, gas, heating or electricity | SCADA vendors, OT integrators |
| 3. Education and vocational training | Admission scoring, assessment, monitoring of prohibited behaviour | EdTech, proctoring, LMS analytics |
| 4. Employment and HR | Recruitment screening, promotion, termination, task allocation | ATS vendors, performance tooling, gig dispatch |
| 5. Access to essential services | Credit scoring, risk assessment and pricing in life and health insurance, public benefits eligibility, emergency call triage | FinTech, InsurTech, govtech |
| 6. Law enforcement | Profiling, evidence reliability, risk assessment of natural persons | Public-sector vendors |
| 7. Migration and border control | Risk assessment of persons entering, polygraph-type tools, examination of asylum, visa and residence permit applications (verification of travel documents is excluded) | Public-sector vendors |
| 8. Administration of justice and democratic processes | Assisting a judicial authority in researching and interpreting facts and law, influencing the outcome of elections or voting behaviour | Legaltech for courts, political campaign tooling |
Article 6(3): the narrow derogation
Even if the intended purpose maps to Annex III, the system is not classified as high-risk if it does not pose a significant risk of harm. Article 6(3) lists four alternative conditions. Meeting any one of them is enough:
- The system performs a narrow procedural task only.
- It is intended to improve the result of a previously completed human activity.
- It detects decision-making patterns or deviations from prior patterns and is not meant to replace or influence the previously completed human assessment without proper review.
- It performs a preparatory task to an assessment relevant for the use cases listed in Annex III.
An Annex III system that performs profiling of natural persons is always high-risk, whatever the conditions say. A provider that invokes Article 6(3) must document the assessment before placing the system on the market, hand the documentation to the authorities on request (Article 6(4)), and register the system (Article 49(2)).
Validating the classification: a working procedure
A defensible classification process produces three artefacts: a written decision, a register entry, and a review trigger. The procedure below is our suggestion. The Regulation does not prescribe one.
- Step 1: Intended purpose statement. Pin down what the system is sold to do, not what it could do. Quote the spec, the marketing copy, the contract.
- Step 2: Annex III map. Walk each of the eight areas. Record the answer per area, not just the conclusion.
- Step 3: Article 6(3) test. Only relevant if Step 2 returns a hit. Apply each of the four conditions, including the profiling exclusion.
- Step 4: Reviewer sign-off. A second person, ideally outside engineering, signs the decision.
- Step 5: Trigger registration. Bind the decision to the spec version. If intended purpose changes, the classification must be redone.
What the EU database expects
Article 49 requires providers of high-risk Annex III systems, and deployers that are public authorities, to register in the EU database the Commission maintains under Article 71. Systems under Annex III, point 2 are registered at national level instead (Article 49(5)). Annex VIII, Section A lists what providers submit, among others:
- Name and contact details of the provider and, where applicable, the authorised representative.
- Trade name and an unambiguous reference that allows identification and traceability.
- A description of the intended purpose, and a basic description of the data used and the operating logic.
- Status: on the market or in service, no longer on the market, recalled.
- Notified body certificate details, where applicable, and a copy of the EU declaration of conformity.
- The Member States where the system is placed on the market, put into service or made available.
- For a system registered under the Article 6(3) route (Annex VIII, Section B): the condition relied on and a short summary of the grounds.
Common misclassifications we see
- Treating an HR analytics dashboard as low-risk because it is read-only: it still informs Annex III area 4 decisions.
- Assuming a drafting assistant is out of scope because it is general software: used by or for a court to research and interpret facts and law, it lands in area 8(a).
- Stretching Article 6(3) to cover a profiling feature: the profiling exclusion is non-negotiable.
- Forgetting that a deployer who substantially modifies a high-risk system, or turns a system into a high-risk one by changing its intended purpose, becomes a provider under Article 25(1).
Sources
- Regulation (EU) 2024/1689, Articles 6, 25, 49, 71 and Annexes III and VIII: EUR-Lex
- Regulation (EU) 2026/1744 (Digital Omnibus), Article 113 dates: EUR-Lex
→ See live Annex III updates: https://aiactradar.com
→ Subscribe to webhook: https://docs.aiactradar.com/quickstart