High-Risk AI Systems under the EU AI Act: Classification and Obligations

How the EU AI Act classifies high-risk AI: the Annex I and Annex III routes, the Article 6(3) exception, provider and deployer duties, and the applicable deadlines.

Two routes into the high-risk category

"High-risk" is not a judgement call about how powerful a system is. Article 6 defines two closed routes, and a system is high-risk if it takes either of them.

Route 1 — Annex I, embedded in a regulated product. The AI system is a safety component of a product, or is itself a product, covered by one of the Union harmonisation acts listed in Annex I — machinery, medical devices, lifts, toys, radio equipment, civil aviation, motor vehicles and others — and that product must undergo third-party conformity assessment under those rules. See Annex I.

Route 2 — Annex III, stand-alone use cases. The system falls into one of eight listed areas: biometrics, critical infrastructure, education and vocational training, employment and worker management, access to essential private and public services, law enforcement, migration and border control, and administration of justice and democratic processes. See Annex III.

Both routes converge on the same requirements in Chapter III. The difference lies in the conformity assessment path and in the applicable deadline.

The Article 6(3) exception, and its price

An Annex III system is presumed high-risk, but the presumption is rebuttable. Under Article 6(3) a system is not high-risk if it does not pose a significant risk of harm to the health, safety or fundamental rights of natural persons — in particular where it:

• performs a narrow procedural task
• improves the result of a previously completed human activity
• detects decision-making patterns or deviations from prior patterns without replacing or influencing human assessment without proper review
• performs a preparatory task to an assessment relevant to the listed use cases

There is a hard carve-out: a system that performs profiling of natural persons is always high-risk, whatever else it does.

The exception is not free. A provider relying on it must document the assessment before placing the system on the market, and remains subject to the registration obligation in Article 49(2). Documentation must be produced on request. In practice, invoking Article 6(3) means committing to a defensible written analysis — not to silence.

What providers must do

Chapter III, Section 2 sets out the substantive requirements. They apply across the whole lifecycle, not at a point in time.

On top of the requirements, providers carry the obligations in Article 16: quality management system, conformity assessment, CE marking, registration in the EU database, corrective action, and cooperation with authorities.

What deployers must do

Deployer duties under Article 26 are lighter but not trivial:

• use the system in accordance with the instructions for use
• assign human oversight to people with the competence, training and authority to exercise it
• ensure input data is relevant and sufficiently representative for the intended purpose, to the extent the deployer controls it
• monitor operation and suspend use plus inform the provider and authorities where risks arise
• keep the automatically generated logs under the deployer's control
• inform workers and their representatives before putting a system into service in the workplace

Certain public bodies and private entities providing public services must also carry out a fundamental rights impact assessment under Article 27 before first use.

When a deployer becomes a provider

Article 25 is the most commonly missed provision in the whole Regulation. A deployer, distributor or importer takes on the full provider obligations if it:

• puts its own name or trademark on a high-risk system already on the market
• makes a substantial modification to a high-risk system
• modifies the intended purpose of a system — including a non-high-risk system — such that it becomes high-risk

Buying a general-purpose tool and repurposing it for CV screening is enough to trigger this. See providers vs deployers for the decision tree.

The deadlines that actually apply

The 2026 Digital Omnibus reshaped this timeline, and older guides still quote the superseded dates.

Systems already on the market before the applicable date are covered by the transitional provisions in Article 111 — but a substantial modification after that date pulls them into scope. Check the full deadline timeline and the omnibus changes.

Where to start

1. Inventory every AI system in use, including embedded vendor features that were never procured as "AI".
2. Run each through the two Article 6 routes — not through intuition.
3. For Annex III hits, decide whether Article 6(3) applies and write the assessment down.
4. For confirmed high-risk systems, establish who is provider and who is deployer for each one.
5. Work the gap against the Chapter III requirements table above.

The AI risk classifier walks the classification logic, and the compliance checklist covers the obligation set once classification is settled.