Skip to main content
MetroMinds
Platform
Solutions
Tools
Insights
Pricing
Book a demo Log in
AI register and EU AI Act

You can only govern the AI you have found.

MetroMinds analyses your application portfolio to find where AI is used, including AI built into vendor software, and records each system in an AI register aligned with the EU AI Act.

Every system in the register records what the EU AI Act asks you to know:

  • Its purpose and the business capability it supports
  • Your role as provider or deployer
  • Risk category and Annex III area
  • Human oversight and an owner by role, never by name

The deadlines moved. The work did not.

  1. Prohibited practices and AI literacy apply.
  2. Obligations for general-purpose AI models apply.
  3. 22 October 2026
  4. Obligations for high-risk systems in Annex III apply, after the Digital Omnibus.
  5. Obligations for high-risk AI in regulated products (Annex I) apply.

The extra time is best used for the inventory. Classification depends on what each system is used for, and that starts with knowing where it is.

Timeline of EU AI Act milestones: prohibited practices and AI literacy from 2 February 2025, general-purpose AI models from 2 August 2025, Annex III high-risk systems from 2 December 2027 and high-risk AI in regulated products from 2 August 2028.
Source: Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744.

Find the AI you already use.

Much AI arrives without a project: a vendor release adds a ranking feature, a business tool switches on an assistant. MetroMinds analyses your application portfolio and flags where AI is present, so nothing stays outside the register.

  • Applications and vendor modules with AI features
  • The business capability and process each one supports
  • A first indication of the Annex III area, for review by your experts

From application list to register entry

  1. Analyse. Your application portfolio is checked for AI features, including those that arrived with a vendor release.
  2. Review. Your experts confirm the purpose and the first Annex III indication.
  3. Register. Each finding becomes a register entry with an owner, ready for oversight and monitoring.

The Annex III indication is a starting point for your experts, not a legal classification. Whether a system is high-risk depends on its intended purpose and how it is used.

Check one of your use cases

High-risk AI does not look different. Its purpose does.

A first screen of the MetroMinds Library flags 333 of 4,980 use cases, about one in fifteen, that touch an area listed in Annex III. Most employment-related ones sit outside HR. Technically they look like the rest; what decides the classification is the intended purpose.

122
of the 333 sit in operations and delivery.
56
sit in Human Capital and Culture, the capability HR owns.
21
sit in Technology, Data and AI.

So the people who own high-risk AI are often operations managers who may never think of it as an HR or IT system.

Bar chart of Library use cases flagged per Annex III area of the EU AI Act: 333 of 4,980 use cases, about one in fifteen.
Source: MetroMinds Library, 4,980 use cases (August 2026). Benchmark ranges are based on real-world implementations.

From register entry to daily practice.

Human oversight.

Name competent people with the authority to oversee each high-risk system.

Monitoring and logs.

Monitor operation and keep automatically generated logs for at least six months.

Informing people.

Inform workers before first use, and inform people affected by decisions the system supports.

Impact assessment.

Run a fundamental rights impact assessment where the Act requires it, for example for credit scoring and public services.

MetroMinds supports your compliance work. It does not replace legal advice.

See the AI register with your own applications.