Skip to content
All articles
AI regulation and governance

High-risk AI: what the Act classifies, and what it does not

“High-risk” does not mean an AI system that could cause harm. It means a system that meets the classification rules of Article 6: two routes into the category and one route back out.

BastionUpdated 4 min read

Route one: embedded in a regulated product

Article 6(1) makes a system high-risk where both of two conditions are met:

(a) the AI system is intended to be used as a safety component of a product, or the AI system is itself a product, covered by the Union harmonisation legislation listed in Annex I; (b) the product whose safety component pursuant to point (a) is the AI system, or the AI system itself as a product, is required to undergo a third-party conformity assessment, with a view to the placing on the market or the putting into service of that product pursuant to the Union harmonisation legislation listed in Annex I.

Regulation (EU) 2024/1689, Article 6(1)

This is the route of medical devices, lifts, toys and other regulated products. Since the AI Omnibus, paragraphs 1a to 1c of Article 6 narrow it: a system used only for non-safety aspects such as user assistance or convenience is not a safety component. An internal document assistant is not in it.

Route two: the Annex III use cases

Article 6(2) is short: “In addition to the high-risk AI systems referred to in paragraph 1, AI systems referred to in Annex III shall be considered to be high-risk.” Annex III lists use cases, in areas such as employment, education, essential services, law enforcement and the administration of justice. The classification therefore follows the intended purpose of the system, not the brand of the model and not the size of the company.

The route back out: four conditions in Article 6(3)

Under Article 6(3), an Annex III system “shall not be considered to be high-risk where it does not pose a significant risk of harm to the health, safety or fundamental rights of natural persons, including by not materially influencing the outcome of decision making”, where any of four conditions is met:

  • the AI system is intended to perform a narrow procedural task
  • the AI system is intended to improve the result of a previously completed human activity
  • the AI system is intended to detect decision-making patterns or deviations from prior decision-making patterns and is not meant to replace or influence the previously completed human assessment, without proper human review
  • the AI system is intended to perform a preparatory task to an assessment relevant for the purposes of the use cases listed in Annex III

One sentence closes the route for any system that profiles people: “Notwithstanding the first subparagraph, an AI system referred to in Annex III shall always be considered to be high-risk where the AI system performs profiling of natural persons.”

The same model can therefore sit in two categories. Summarising a CV for a human reviewer and ranking candidates for rejection are not the same system in the eyes of the Regulation, even if the weights are identical.

When the high-risk rules apply

High-risk routeRules apply fromSource
Annex III use cases, Article 6(2)2 December 2027, an extended dateEuropean Commission
AI embedded into regulated products (Annex I), Article 6(1)2 August 2028, after an extended transition periodEuropean Commission
When the high-risk rules apply, from the European Commission's timeline

Both dates are extensions. They come from the AI Omnibus, in force since 27 July 2026, while the Act itself “became applicable on 2 August 2026”.

Why private deployment does not change the answer

Moving a model onto an internal server does not alter its intended purpose. An application inside Annex III stays inside Annex III on your own hardware, with the same documentation, human oversight and risk controls required.

For any deployment that looks close to Annex III, the classification should be reviewed against the current text and applicable guidance, not against a generic checklist, including this one.

With Bastion

What Bastion changes

Bastion is a private AI system delivered as one sealed box that runs inside your building. One monthly fee covers the hardware, the model, the hardened operating system and support, and nothing your team types leaves the building.

Bastion is infrastructure. It does not decide whether a use case is high-risk and cannot remove a classification.

It makes the obligations easier to evidence. Which model, which version, where it ran, who reached it and when it was updated are facts about one box at a known location, not answers to request from a cloud supplier.

Questions this article answers

What makes an AI system high-risk under the EU AI Act?
Article 6 gives two routes. Either the system is a safety component of, or is itself, a product covered by the Annex I harmonisation legislation and subject to third-party conformity assessment, or it falls within one of the Annex III use cases.
Can an Annex III system avoid the high-risk classification?
Article 6(3) says yes, where it does not pose a significant risk of harm and meets one of four conditions, such as performing a narrow procedural task or improving the result of a previously completed human activity. The exit is closed to any system that profiles natural persons: such a system is always high-risk.
When do the high-risk rules start to apply?
The Commission's current timeline gives 2 December 2027 for the Annex III use cases and 2 August 2028 for high-risk AI embedded in regulated products. Both were extended by the AI Omnibus, in force since 27 July 2026.

On the record

  1. 1
  2. 2
  3. 3

    European Commission

    AI Act. Regulatory framework for AI

    read 2026-09-22