Skip to content

Risk classes

🎯 Learning goals

  • Understand how the AI Act classifies risk — and why “low risk” and “minimal risk” aren’t real categories
  • Know which AI systems are prohibited and which are high-risk
  • Understand transparency requirements and systemic risk for GPAIs
  • Understand the role of intended purpose and reasonably foreseeable misuse

A risk-based approach to protecting fundamental rights

Section titled “A risk-based approach to protecting fundamental rights”

The EU AI Act takes a risk-based approach, which is an important distinction from a lot of other regulations.

The point of the AI Act isn’t to classify all AI systems — it would be impossible to say anything about all text generation apps, or all machine learning algorithms. Rather, the point is to regulate the systems that most likely pose risks to people’s health, safety, and other fundamental rights.

Health and safety are easy to understand. Additional fundamental rights are laid out in the European Charter of Fundamental Rights. They include:

  • The right to good public administration, such as the right to be heard in matters that concern you
  • Protection of your personal data
  • The right to education and to access to vocational and continuing training
  • The right to work and to pursue an occupation you choose
  • The right to non-discrimination
  • Workers’ right to information and consultation

It is the protection of these rights, not the classification of AI systems, which is the intent of the Act.

The Act has decided that a few certain AI systems inherently pose more risk to these rights than others, and therefore they are directly regulated. In other cases, the Act specifically points to existing regulation that has to be followed in addition, such as GDPR.

There are only two categories of inherent, or pre-determined, risk classes: those with an unacceptable amount of risk, and those inherently high risk.

The very first sentence in Article 1 is, “Human dignity is inviolable. It must be respected and protected”. A fundamental right is respect for your physical and mental integrity. There are only a handful of AI systems that are deemed to have an unacceptably high level of risk, and are therefore prohibited — and many of them relate to manipulating or monitoring people them such that they can’t make decisions they otherwise would make, or restricting their access to opportunities to thrive.

Most forbidden AI systems aren’t relevant to how our customers use Intric. But it’s worth repeating the activities that would make an AI system prohibited:

  • Manipulate or deceive people in order to impair their decision-making
  • Exploit vulnerabilities
  • Evaluation or social scoring that leads to detrimental treatment of certain groups
  • Assess people’s risk of committing a crime
  • Create/expand facial recognition databases through untargeted scraping
  • Infer the emotions of people in workplaces or educational institutes
  • Biometric categorization used to infer things like race, political opinions, trade union membership, gender, religious beliefs
  • Some uses of real-time remote biometric monitoring by law enforcement

Claiming an exception to the high-risk classification

Section titled “Claiming an exception to the high-risk classification”

There are four clear exceptions, meaning if your AI system is classified as inherently high-risk, you can claim that in reality, it doesn’t pose a risk to health, safety, or fundamental human rights.

To be able to claim this exception, your system needs to meet one of the following criteria — and here we are copying the exact wording from the Act:

  • intended to perform a narrow procedural task;
  • intended to improve the result of a previously completed human activity;
  • 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; or
  • intended to perform a preparatory task to an assessment relevant for a high-risk system, excluding the systems that are already regulated.

Many machine learning algorithms to detect deviations in enormous datasets (due to human error or fraud), will be classified here. In fact, these exceptions primarily apply to AI systems that are not generative.

To claim an exception, you simply have to report this to an EU database. Aside from that, you don’t have any other requirements of high-risk system deployers or providers. If you claim an exception on false premises, your fine will be 750,000 EURO.

Note that if your AI system profiles people, you won’t be able to claim an exception.

Example: Your AI system analyzes completed case management times according to a selection of topic and case manager characteristics. No individuals are identifiable in this process, so the system is not a type of employee management. You use it to identify whether certain groups of citizens are receiving slower decisions, or whether certain topics seem more difficult for case managers, in order to prioritize future training. But! If you start to use this system to group certain employees are better or worse performing, it falls in the high-risk area.

Separate from whether your AI system is high-risk, is whether the system has specific transparency requirements. When there would be a risk to someone if transparency was lacking, transparency is required. This basically refers to making it very clear to a user that what they are seeing, hearing, or interacting with, is an AI system.

If a system does any of the following, there are transparency requirements:

  • Interacts with a person
  • Generates text, audio, image, or video
  • Generates or manipulates image, audio, or video to constitute a deep fake. (Text is not included here)
  • Recognizes emotions or conducts biometric categorization
  • Generates text that is published to inform the public on matters of public interest

In practice, most GPAIs and systems that use them will automatically carry transparency requirements.

Deep dive — chatbots: In early training material, “chatbots” were listed as an example of an AI system that only required transparency — this was before GPAI-powered chatbots became widespread. Now, a chatbot would require only transparency if it was powered by a simpler language model. Think about when you try to contact customer service through a chat window; you write your question and then the chatbot responds with, ‘is one of these six topics what you are asking about?’ This is an example of a non-GPAI chatbot. It can’t talk to you like a chatbot can, but it does have a limited ability to analyze your questions. The company only has to be transparent to you that it is an AI system.

Rather than try to fit GPAIs into the above risk classification, the AI Act decided to use the idea of “systemic risks”. They write that some GPAIs could carry systemic risks if:

  • The GPAI is very capable, as indicated by a large amount of computation used in training,
  • The GPAI is widely used (as many hope to be) and therefore has a high impact on the market, or
  • The Commission determines that it has systemic risk.

In practice, most large language models classify as having systematic risk.

A model is not classified as having ‘low’ or ‘no’ systematic risk; the Act refers only to GPAIs and GPAIs with systemic risk.

Section titled “Decision-making is not related to risk class”

A lot of organizations hope that human-in-the-loop procedures, i.e. only AI decision-support and not full decision-making, can reduce the risk class. This isn’t how the logic of the Act works. High-risk designation doesn’t actually have anything to do with the decision-making and whether a human is involved or not. What matters more is whether your AI system is in an area considered to be inherently high-risk to health, safety, or fundamental rights.

But if you are the provider of a high-risk system, you must ensure that humans have the ability to understand the output, to intervene or stop the system — this is what is meant by “human oversight”.

In addition, if you are a public sector deployer of a high-risk system and your AI system is involved in decision support or decision-making that affects people, you have to inform the people affected.

After reading this session, if you can think of an AI system that meets none of the inherent risk classifications, that has no transparency requirements, is not a GPAI, and you can’t think of any way that intended use or misuse could threaten health, safety, or fundamental rights — then that system may be out of scope of the AI Act. Neither the provider nor the deployer has any requirements.

Remember that the European Commission does not intend to present an exhaustive list of all AI systems. The Commission expects that all actors will use their own reasoning.

Many examples of out-of-scope systems are ‘traditional’ machine learning algorithms:

  • Recommender algorithms on a streaming platform. The output is the order that content is presented to you.
  • An AI system used to control a non-player character in a game, or to generate dynamic game behavior.
  • The spam filter used by your email provider is a classic example of a machine learning algorithm using natural language processing. It doesn’t fall in any of the unacceptable or high risk areas. It is also not generating text, only a decision of whether an email is sent to your spam folder or your inbox, and no one is interacting with it, so there are no transparency requirements.
  • There are only two pre-determined risk classes in the Act: unacceptable risk (prohibited) and inherently high risk. “Low risk” and “minimal risk” are not categories in the Act.
  • High-risk classification is based on the area of operation, not the function performed or whether a human is in the loop.
  • Most GPAIs and systems built on them carry transparency requirements automatically.
  • Providers and deployers must identify risks related to intended purpose, reasonably foreseeable misuse, and vulnerable groups — but not every possible risk.
  • If a system is out of scope, neither the provider nor the deployer has any requirements.

Test your knowledge

6 questions · 100% correct to pass · Review your answers when done