Talk to us
Model & AI

The AI Act, per system and per obligation

You already have models in production and a framework that approves and monitors them. Some of those controls will already count towards the AI Act. The hard part is showing which ones apply to which system, and closing the rest before an auditor or supervisor finds the gap.

The guidance keeps arriving, while the mapping still sits with a few experts and a lot of spreadsheets. Does your model governance answer the AI Act’s questions?

RegAI Helia holds the AI Act as one structured source, maps each requirement to the AI systems it applies to and the controls meant to satisfy it, and shows what is covered, what is not, and who is fixing it.

The AI Act broken into requirements you can act on

What applies depends on how a system is classified and which role you hold for it. Regulatory Nexus holds the AI Act as one requirement tree, each item traceable to the article it came from.

1
Requirements, not articles
One article often holds several obligations. Each becomes its own item to assign and track.
2
Obligations follow the classification
The risk tier and use case decide what applies, so the classification is part of the mapping.
3
Provider or deployer
The same system carries different duties depending on the role you hold for it.
4
One requirement, every team
Data science, risk, legal and compliance work from the same requirement, so nobody keeps their own version.

Your policies and controls against the AI Act, with the reasoning

Assess your policies against the AI Act, or your controls against control objectives derived from it. RegAI Helia shows which objectives you already meet and where the gaps are, with the reasoning behind it.

1
Reuse what you already have
Model risk, data governance and change management controls already answer part of the Act. You see exactly which part.
2
Gaps become work
Assign any finding to a colleague as a work item with a due date, so every gap has someone resolving it.
3
Suggested remediation
Where a policy or control falls short, RegAI Helia drafts the missing wording. Your experts approve, edit or reject it.

Every obligation belongs to a system

Policies and controls cover the organisation. The AI Act also asks questions of each AI system: how it is classified, which role you hold, and whether its documentation meets what applies. Your AI inventory carries the mapping.

Register and classify
Each system is recorded with its role, risk tier and any general-purpose AI component, plus the obligations that follow.
Assessed on its own documentation
Add the system’s documentation, and RegAI Helia checks it against the requirements that apply to that system.
Gaps per system
Findings stay with the system and its owner, ready to edit and assign, so you always know which systems are exposed.

Standards and guidance are still landing

Harmonised standards are still being finalised, and guidelines and supervisory expectations keep arriving. Horizon Scanning flags each change and gives it an owner, so nothing new slips past.

1
Change flagged at source
New AI Act guidance, consultations and standards are picked up as they publish.
2
An owner for every change
Each relevant change is triaged, assigned and reviewed.
3
One audit trail
RegAI Helia proposes, your experts decide. Every classification, override and approval is traceable to the person who made it.

Next up

Each obligation attaches to the systems and controls that carry it in Regulatory Nexus.

Let us take you further

Schedule a 30 min call. No slide decks. Just a practical assessment of your needs and how we can help.

Book a demo