Regulation (EU) 2024/1689 — the EU AI Act — establishes harmonized rules for AI systems placed on the market, put into service or used in the EU. It takes a risk-based approach: certain practices are prohibited, high-risk AI systems carry extensive requirements, certain systems carry transparency obligations, general-purpose AI models have their own regime, and all providers and deployers have AI literacy obligations.
This page explains how VERITRAIL controls and evidence relate to the main obligation areas. It is a readiness guide, not legal advice. Whether and how the Act applies to a given system depends on facts and legal analysis that VERITRAIL does not perform.
Important: verify timelines and current text
The Act applies in stages. As originally published in the Official Journal, the main milestones were: entry into force in August 2024; prohibited practices and AI literacy applying from February 2025; general-purpose AI model obligations from August 2025; most remaining provisions, including Annex III high-risk requirements and Article 50 transparency, from August 2026; and high-risk systems that are safety components of products covered by Annex I legislation from August 2027.
These dates may have changed. In 2025 the European Commission published "Digital Omnibus" proposals that would amend aspects of the AI Act, including the timing of high-risk obligations. Applicability timelines must be verified against the current Official Journal text and any adopted amendments. VERITRAIL has not verified post-2025 changes, and this page should not be relied on for dates.
Provider or deployer? Start with roles
Obligations depend heavily on your role for each AI system:
| Role | Who it is, in short | Main obligations for high-risk systems |
|---|---|---|
| Provider | Develops an AI system (or has it developed) and places it on the market or puts it into service under its own name or trademark | Risk management, data governance, technical documentation, logging capability, transparency to deployers, human-oversight design, accuracy/robustness/cybersecurity, quality management system, conformity assessment, registration, post-market monitoring, serious incident reporting |
| Deployer | Uses an AI system under its authority in a professional context | Use according to instructions, assign competent human oversight, ensure relevant input data, monitor operation, keep logs under its control, inform affected workers and individuals where required, cooperate with authorities; certain deployers must carry out a fundamental rights impact assessment (Art. 27) |
A deployer, distributor or importer can become a provider — for example by putting its name or trademark on a high-risk system, making a substantial modification, or changing a system's intended purpose so that it becomes high-risk (Art. 25). VERITRAIL captures role per system and responsibility allocation with vendors (AO-09, EI-08, GL-11); the role determination itself is a legal question.
VERITRAIL controls cited
- AO-07 Regulatory and contractual obligations registerNIST AI RMF: GOVERN 1.1ISO/IEC 42001: 4.1, 4.2, 6.1EU AI Act: Art. 6, Art. 26
- AO-09 Third-party AI accountabilityNIST AI RMF: GOVERN 6.1, GOVERN 6.2ISO/IEC 42001: A.10.2, A.10.3EU AI Act: Art. 25, Art. 26
- EI-02 AI risk classification and tieringNIST AI RMF: MAP 1.1, MAP 1.5, GOVERN 1.3ISO/IEC 42001: 6.1.2, A.5.2EU AI Act: Art. 6
- GL-11 Vendor AI due diligence and contract controlsNIST AI RMF: GOVERN 6.1, MAP 4.1ISO/IEC 42001: A.10.3, A.10.4EU AI Act: Art. 25
Framework mappings are indicative VERITRAIL interpretations (Control Library v1.0.0); they are not legal advice and do not establish conformity or compliance.
Obligation areas and VERITRAIL controls
The mapping below uses the article references in VERITRAIL Control Library v1.0.0. It is indicative: implementing the listed controls supports readiness work but does not by itself satisfy any article.
| Obligation area | Article | Applies chiefly to | VERITRAIL controls (indicative) | Evidence VERITRAIL helps you hold |
|---|---|---|---|---|
| AI literacy | Art. 4 | Providers and deployers | AO-05 | Role-based curriculum and completion records |
| Prohibited practices | Art. 5 | All operators | AO-10 | Prohibited/restricted use list; intake screening records |
| High-risk classification | Art. 6 | Providers (and deployers assessing role) | EI-02, EI-12, AO-07 | Classification facts; legal review records |
| Risk management system | Art. 9 | Providers of high-risk systems | AO-04, GL-01, GL-02, GL-03, GL-05, GL-10, GL-12, IS-06 | Risk assessments; approvals; residual-risk acceptance; periodic review |
| Data and data governance | Art. 10 | Providers of high-risk systems | EI-06, IS-02, IS-03, IS-04, IS-05 | Data source register; quality checks; bias testing; privacy assessment |
| Technical documentation | Art. 11 | Providers of high-risk systems | GL-06, EI-04, EI-05, EI-07, EI-10, SE-05 | Technical documentation pack; system profile; model and component registry |
| Record-keeping | Art. 12 | Providers (logging capability) | SE-08 | Log configuration; tamper-evidence; retention settings |
| Transparency to deployers | Art. 13 | Providers of high-risk systems | IS-08, SE-11, EI-04 | Instructions for use; capability and limitation statements |
| Human oversight | Art. 14 | Providers (design) and deployers (operation) | IS-09, IS-13, IS-11, IS-12, IS-15 | Oversight design; approval rules and records; kill-switch tests |
| Accuracy, robustness and cybersecurity | Art. 15 | Providers of high-risk systems | GL-05, IS-01, IS-07, IS-10, IS-11, IS-12, IS-14, IS-16, SE-12 | Validation results; adversarial test reports; threat models; drift monitoring |
| Quality management system | Art. 17 | Providers of high-risk systems | AO-01, AO-02, AO-12, SE-01, SE-07 | Policy; forum records; control testing; management review |
| Deployer obligations | Art. 26 | Deployers of high-risk systems | AO-03, EI-01, EI-03, GL-07, GL-08, IS-09, SE-04, SE-08 | Inventory; oversight assignments; monitoring; logs; incident records |
| Fundamental rights impact assessment | Art. 27 | Certain deployers | GL-02, AO-11 | Impact assessment; stakeholder input |
| Transparency for certain AI systems | Art. 50 | Providers and deployers of in-scope systems | IS-08 | Disclosure text and placement |
| Post-market monitoring | Art. 72 | Providers of high-risk systems | SE-09, GL-08, SE-12 | Monitoring plan; monitoring outputs |
| Serious incident reporting | Art. 73 | Providers (deployers inform providers) | SE-04 | Incident procedure; incident log; notification decision records |
VERITRAIL controls cited
- AO-05 AI literacy and role-based trainingNIST AI RMF: GOVERN 2.2ISO/IEC 42001: 7.2, 7.3, A.4.6EU AI Act: Art. 4
- AO-10 Prohibited and restricted AI use policyNIST AI RMF: GOVERN 1.1, MAP 1.1ISO/IEC 42001: A.9.4, A.2.2EU AI Act: Art. 5
- GL-02 Pre-deployment risk and impact assessmentNIST AI RMF: MAP 1.1, MAP 3.1, MAP 5.1, MEASURE 1.1ISO/IEC 42001: 6.1.4, 8.4, A.5.2, A.5.3, A.5.4EU AI Act: Art. 9, Art. 27
- IS-08 Transparency and AI disclosuresNIST AI RMF: MEASURE 2.8, MEASURE 2.9ISO/IEC 42001: A.8.2, A.8.5EU AI Act: Art. 13, Art. 50
- IS-09 Human oversight designNIST AI RMF: GOVERN 3.2, MAP 3.5ISO/IEC 42001: A.9.2, A.6.2.6EU AI Act: Art. 14, Art. 26
- SE-04 AI incident management and reportingNIST AI RMF: MANAGE 4.3, MANAGE 2.3ISO/IEC 42001: 10.2, A.8.4EU AI Act: Art. 73, Art. 26
- SE-08 Immutable action loggingNIST AI RMF: MEASURE 2.8, MANAGE 4.1ISO/IEC 42001: A.6.2.8EU AI Act: Art. 12, Art. 19, Art. 26
- SE-09 Post-market monitoring planNIST AI RMF: MANAGE 4.1ISO/IEC 42001: 9.1, A.6.2.6EU AI Act: Art. 72
Framework mappings are indicative VERITRAIL interpretations (Control Library v1.0.0); they are not legal advice and do not establish conformity or compliance.
What is not covered
- General-purpose AI model obligations (for GPAI model providers) are not mapped in Control Library v1.0.0. Organizations that provide GPAI models need separate analysis.
- Conformity assessment procedures, CE marking and registration mechanics are referenced only where an VERITRAIL control supports the underlying evidence (for example GL-03 and GL-04 relate to Art. 43; EI-01 to Art. 49).
- Sector and product legislation referenced by Annex I (for example medical devices or machinery) has its own requirements outside VERITRAIL's scope.
- Penalties, authority procedures and national implementation are outside VERITRAIL's scope.
A readiness workflow
- Inventory and screen. Register every AI system with EU exposure (EI-01) and screen against prohibited practices (AO-10).
- Capture classification facts. Domain, purpose, decision impact, affected parties and autonomy for each system (EI-02, EI-04). Route potential high-risk and Article 50 cases to legal review (AO-07).
- Record your role. Provider, deployer or both, per system; responsibility allocation with vendors (AO-09).
- Assess and close gaps against the obligation areas relevant to your role, using the gap-analysis method.
- Operate and evidence. Logging, oversight, monitoring, incident handling and documentation, maintained continuously.
The self-assessment produces indicative EU AI Act readiness indicators for selected themes (Art. 4, 9, 10, 11–12, 13 and 50, 14, 15, 72–73). The EU AI Act readiness checker, which will go deeper by role, is planned.