Hael
Sign inRequest a demo
EU AI Act

Meet every EU AI Act obligation for every system.

The binding law behind the questions buyers ask. Hael classifies every system against Article 6 and Annex III, and produces the Annex IV technical file, the Article 27 FRIA, the Article 9 risk assessment and the Article 14 human-oversight plan — the substantive documents a regulator opens. Most organisations meet the Act's evidence expectations through an ISO/IEC 42001 management system; Hael runs both from the same record.

app.hael.ai / registry / AGT-014
HAEL BANK · ISOLATED
EU AI Act · classified from the record
IN SCOPE
Customer Decisioning Agent
Owner · AI Governance · M. Okafor · System AGT-014
HIGH RISK
Obligations
Art. 9  Risk management system
MAPPED
Art. 10  Data governance
MAPPED
Art. 11  Annex IV technical documentation
MAPPED
Art. 14  Human oversight
MAPPED
Art. 15  Accuracy & robustness
HELD OPEN
Art. 72  Post-market monitoring
PENDING
Generated · Annex IV technical file · v4SOURCED
What it demands

What the Act demands of high-risk AI.

The Act sorts AI systems into prohibited, high-risk, limited-risk and minimal-risk tiers. High-risk systems — including much AI used in credit, employment, insurance and essential services — carry the substantive load.

For a high-risk system the obligation is not to list the documents. It is to hold them, keep them current, and produce them on request.

Obligations · 9 articles
MAPPED
Art. 9  Risk management
A risk-management process maintained across the lifecycle of the system.
Art. 10  Data governance
Training, validation and test data governed for relevance, representativeness and known biases.
Art. 11  Technical documentation
The Annex IV technical file held before deployment and kept current.
Art. 12  Automatic logging
Automatic record-keeping over the operational life of the system.
Art. 13  Transparency to deployers
Instructions sufficient for the deployer to use the system correctly.
Art. 14  Human oversight
The system designed so a human can effectively oversee its use.
Art. 15  Accuracy, robustness, cybersecurity
Performance thresholds met and adversarial conditions considered.
Art. 50  Transparency duties
Disclosure where users interact with AI or with AI-generated content.
Art. 72  Post-market monitoring
An active monitoring plan, with serious-incident reporting under Art. 73.
Closed vocabulary · sourced from the Act
What Hael does for it

Three things Hael does for the EU AI Act.

01
Classifies
Each system is classified against Annex III in plain language — risk tier, role (provider or deployer), and which obligations apply.
02
Generates
The Annex IV technical file, fundamental-rights impact assessment, conformity record, post-market monitoring plan and incident report — produced from the record and sourced line by line.
03
Keeps current
When the system changes or the Act amends, the affected obligations and documents flag for review. Nothing silently expires.
app.hael.ai / registry / AGT-014
AGT-014 · OBLIGATION → CONTROL → RECORD
MAPPED
Art. 9 · Risk management
CTRL-614 · M. Okafor
SOURCED
Art. 10 · Data governance
training data provenance
SOURCED
Art. 11 · Technical documentation
Annex IV generated
SOURCED
Art. 14 · Human oversight
CTRL-227 · R. Adeyemi
HELD OPEN
Art. 15 · Accuracy & robustness
monitoring plan live
SOURCED
Art. 72 · Post-market monitoring
incident path · INC-2026-031 closed
LIVE
THE SAME CONTROL, EVIDENCED BY THE SAME ARTEFACTS, ACROSS EVERY REGIME
The record through-line

One record. The Act, alongside every other regime.

A system is registered once. Its obligations under the EU AI Act, ISO/IEC 42001, NIST AI RMF and GDPR are expressed against the same control set — mapped to the same record, evidenced by the same artefacts.

Artefact proof

The Annex IV technical file, generated and held.

Each section of the Annex IV file is sourced to the record entry behind it. Where the record is silent, the section is held open — never inferred.

app.hael.ai / documents / Annex IV technical file
v4 · 12 Jun 2026
Annex IV technical file · EU AI Act
SEALED
§1  General description of the AI system
Registry · AGT-014 · purpose, scope, intended deployers
SOURCED
§2  Detailed description of elements & development process
Model card v3 · training data record · vendor record
SOURCED
§3  Monitoring, functioning and control
Oversight control record · Art. 14 design notes
SOURCED
§4  Risk management system (Art. 9)
Risk management file v3 · residual-risk attestation
SOURCED
§5  Performance, accuracy and robustness (Art. 15)
Open — REQ-04812 attestation outstanding from Risk Operations. The record is silent on the current threshold; the section is held until attestation is filed.
HELD OPEN
§9  Post-market monitoring plan (Art. 72)
Monitoring plan v1 · draft pending Art. 73 incident workflow sign-off
SOURCED
Every section cites the record entry behind it
Related frameworks

Govern this alongside everything else.

One system, one record, governed against every framework at the same time. Map an obligation once; satisfy it everywhere it recurs.

Free check

See where you stand on EU AI Act, free.

Answer a few questions and get an indicative view of what EU AI Act expects of your AI systems and where you stand today — no sign-up to see your result.

Indicative, not legal advice.
EU AI Act · indicative readiness
HAEL FREE TOOLLIVE
Applicability
Applies to your AI use
MAPPED
What's expected
Risk classification · governance · documentation · oversight
4 PILLARS
Where you stand
Banded result · pointed to the gaps that matter most
SOURCED
Result
On-screen, free · optional PDF
FREE
Effort
Pre-scoped to EU AI Act
~ 5 MIN
INDICATIVE · NOT LEGAL ADVICE
See it on a real record

See a high-risk system meet the Act, end to end.