Minimal risk AI defined by what it doesn’t require
Minimal risk is the largest of the EU AI Act’s four tiers by volume, and the least understood, because it’s defined mostly by what it doesn’t require rather than what it does. This piece focuses on that one tier in depth, for how it fits alongside the other three, see EU AI Act risk classification: The 4-tier system explained.
If an AI system isn’t banned under Article 5, doesn’t fall into one of the eight Annex III high-risk domains or an Annex I regulated product, and doesn’t interact with people in a way that triggers Article 50 transparency duties, it lands here by default. Spam filters, recommendation engines, AI-enabled games, and most internal process automation fit this description. No risk management system, no technical documentation dossier, no conformity assessment, no CE marking. That doesn’t mean an organisation building or using one of these systems has zero obligations under EU law. Generally, GDPR, consumer protection, and product liability rules don’t disappear just because the AI Act stays quiet, and it doesn’t mean the classification is permanent. What follows is what minimal risk actually exempts an organisation from, what it doesn’t, and the one Act-wide obligation that reaches even here.
Getting to minimal risk classification: The process of elimination
| Question | If yes | If no, check next | |
|---|---|---|---|
| Is the system’s intended use listed as a prohibited practice under Article 5? | Prohibited. Stop. | Continue | |
| Is it a safety component of an Annex I regulated product, or listed in Annex III? | Likely high-risk | Continue | |
| Does it interact with people in a way they could mistake for human, or generate synthetic content? | Limited risk: Article 50 transparency applies | Continue | |
| None of the above? | Minimal risk | / |
What “No compliance work” actually covers
| Obligation | Required for minimal-risk systems? | Where it comes from | |
|---|---|---|---|
| Risk management system | No | Article 9 (high-risk only) | |
| Data governance requirements | No | Article 10 (high-risk only) | |
| Technical documentation dossier | No | Article 11 (high-risk only) | |
| Automatic logging | No | Article 12 (high-risk only) | |
| Human oversight design | No | Article 14 (high-risk only) | |
| Conformity assessment | No | Article 43 (high-risk only) | |
| CE marking | No | Article 48 (high-risk only) | |
| EU database registration | No | Article 49 (high-risk only) | |
| Fundamental Rights Impact Assessment | No | Article 27 (specific deployer categories only) |
In practice, this is the shortest compliance list on the entire site, because it’s a list of things that simply don’t apply. A team building an internal scheduling tool or a product recommendation engine is not going to find itself drafting Annex IV technical documentation, because that requirement never reaches this tier.
The one obligation that reaches every AI system anyway
Article 4 requires providers and deployers to take measures ensuring a sufficient level of AI literacy among their staff and anyone else operating AI systems on their behalf. Unlike every requirement in the table above, this one is not tied to risk classification at all. It has applied since 2 February 2025, to every provider and deployer, for every kind of AI system, minimal risk included. The Digital Omnibus softened the wording from an obl,igation to “ensure” literacy to “support the development of” it, but the underlying expectation, documented and proportionate training for the people actually working with the system, remains.
In practice, a company running nothing but a minimal-risk recommendation engine still needs to be able to show that the people operating it have a basic, proportionate understanding of what it does and where its limits are. That is a considerably lighter lift than a conformity assessment, but it is not nothing.
What minimal risk classification doesn’t exempt an organisation from
General EU and national law does not pause because the AI Act does not apply. GDPR still governs any personal data the system processes. Consumer protection and product liability rules still apply to whatever the system is embedded in. Sector-specific regulation, financial services rules, employment law, does not care whether the AI Act classifies the tool as minimal risk.
Article 95 also encourages, without requiring, providers and deployers of non-high-risk systems to adopt voluntary codes of conduct, facilitated by the AI Office and the member states, applying some or all of the Chapter III, Section 2 requirements on a voluntary basis. No enforcement consequence attaches to skipping this, but it is worth knowing it exists, particularly for systems that interact with large numbers of people even without crossing into a regulated tier.
Classification is also not a one-time event. If a minimal-risk system is redeployed for an Annex III use case, or substantially modified in a way that changes its risk profile, the classification has to be reassessed. For example, a recommendation engine repurposed to screen job candidates does not carry its old minimal-risk label with it into that new use.
How Deeploy applies to minimal risk systems
The systems that cause the most trouble are rarely the ones classified high-risk from day one. They are the minimal-risk tools that quietly get repurposed into a higher-risk context without anyone updating the classification. Deeploy’s system inventory and monitoring make that drift visible, so a tool’s actual use in production stays matched to the classification it was originally given, rather than the two quietly drifting apart. Deeploy monitors and governs AI systems efficiently in line with the EU AI Act – all oversight in one platform.
Frequently asked questions
Spam filters, recommendation engines, AI-enabled games, and most internal process automation are common examples, provided they are not repurposed into one of the Annex III high-risk domains or embedded in an Annex I regulated product.
Effectively one: Article 4's AI literacy duty, which applies to every provider and deployer regardless of risk tier. The Chapter III high-risk requirements, risk management, documentation, conformity assessment, and the rest, do not apply.
Yes. The AI Act not applying to a system does not exempt it from GDPR, consumer protection law, product liability rules, or sector-specific regulation, all of which apply independently of AI risk classification.
Yes. If the system is redeployed for a use covered by Annex III, or substantially modified in a way that changes its risk profile, the classification must be reassessed. Minimal-risk status is not permanent.
No. Article 95 encourages providers and deployers of non-high-risk systems to adopt voluntary codes applying some of the high-risk requirements on their own initiative, but there is no enforcement consequence for not doing so.
There is no external sign-off for minimal-risk classification. The provider or deployer determines this itself, based on the same Article 6 classification logic used for every other tier, and should document that reasoning in case it is ever questioned. A risk tier self-assessment can be conducted through this tool: https://deeploy.ai/eu-ai-act-hub/self-assessment/