Aurorisk FR

Chapter 1 · Lesson 1.4

Roles and obligations: provider, deployer, importer

Qualification gives the risk level; the role gives the obligations. The same organisation can have several roles depending on the system.

RoleWhoMain obligations (high risk)
ProviderDevelops a system (or has it developed) and places it on the market under its own nameRisk management system, data quality, technical documentation, logs, instructions for use, human oversight, accuracy and robustness, conformity assessment, marking, post-market monitoring (Art. 9 to 17, 43 to 49, 72, 73)
DeployerUses a system under its own authorityUse in line with the instructions, human oversight by competent people, quality of input data, monitoring, log retention, informing workers and affected people, reporting incidents (Art. 26)
Importer, distributorMakes available in the Union a system from a provider outside the Union, or distributes itCheck the system’s conformity before making it available (Art. 23 and 24)
You can become a provider without intending to

A deployer is treated as a provider if it puts its name on a high-risk system, substantially modifies it or changes its purpose to make a high-risk use of it (Art. 25).

The AI Act rolesThree roles linked by arrows: the provider designs and places on the market, the importer or distributor makes available in the Union, the deployer uses under its own authority. A dotted arrow leads back from the deployer to the provider: Article 25 turns a deployer into a provider in three cases.Providerdesigns, places on the marketunder its own nameImporter, distributormakes availablein the UnionDeployeruses underits own authorityArt. 25: the deployer becomes a provider if it puts its name on the system,substantially modifies it or changes its purpose towards a high-risk usedocumentation, conformity,marking, monitoringcheck conformitybefore making availableinstructions, human oversight,logs, information
The role gives the obligations. Aubépine is a deployer for CV screening; it would become a provider by modifying the tool or selling it under its own name.

Qualification sheet for the running case

Case: Aubépine Recrutement, a fictional 45-person SME, uses CV-screening software based on a language model supplied by a vendor, and a chatbot to answer candidates.

SystemQualificationAubépine’s roleWhy
CV screeningHigh risk (Annex III, point 4, selection of candidates)DeployerThe vendor is the provider; the exception in Art. 6(3) does not apply, because the system ranks and profiles candidates
Candidate chatbotTransparency (Art. 50)DeployerIt talks to people: they must know they are talking to an AI
Underlying language modelGeneral-purpose modelNone (user of the service)Its obligations fall on its provider; the contract must provide access to the relevant information

The file Analyse_risque_IA_gabarits.xlsx contains the blank qualification grid (sheet “1-Qualification”).

Key takeaways

The role (provider, deployer, importer) determines the obligations. A deployer can become a provider if it modifies the system or puts its name on it. CV screening is high risk; the chatbot falls under transparency.

Sources: Art. 3, 16, 23, 24, 25, 26 and Annex III of Regulation (EU) 2024/1689. For a real case, have the qualification confirmed by a lawyer.