EU AI Act 2026: What Developers Need to Know
By Dorian Laurenceau
š Last reviewed: April 24, 2026. Updated with April 2026 findings and community feedback.
The European Union's AI Act is now in full effect, representing the world's first comprehensive legal framework for artificial intelligence. With major compliance deadlines arriving throughout 2025-2027, every organization developing or deploying AI in Europe must understand and implement the requirements.
This comprehensive guide breaks down the EU AI Act for developers and technical teams, covering risk classifications, specific obligations, and practical compliance steps.
<!-- manual-insight -->
EU AI Act in year two: what compliance teams have learned vs what the guidance documents said
The AI Act entered into force in August 2024; the first real obligations (prohibitions, literacy) took effect February 2025; GPAI obligations August 2025; high-risk rules staged through 2026-2027. We're now deep enough into implementation that the gap between written guidance and operational reality is visible. Threads on r/GDPR, r/compliance, and the EU-facing business communities show what's actually happening.
Where the Act is working as intended:
- āThe prohibited-practices list is straightforward. Social scoring by public authorities, emotion recognition at work and school, biometric categorisation by sensitive attributes: the prohibitions are clear and organisations are complying. See Article 5 of the AI Act.
- āThe GPAI model obligations have teeth. The frontier labs (OpenAI, Google, Anthropic, Mistral, Meta for EU-facing releases) are producing the technical documentation, training data summaries, and systemic-risk assessments required. The Code of Practice negotiation produced something workable.
- āArticle 4 literacy requirements are reshaping training programmes. See our detailed analysis in AI literacy requirements.
Where implementation is messier than the guidance suggests:
- āHigh-risk system classification is operationally hard. The list in Annex III is clear in principle; in practice, determining whether a specific system is high-risk requires legal interpretation that most organisations can't do in-house. Expect more enforcement actions as national authorities take positions.
- āThe interaction with GDPR is underdocumented. Both regulations apply to AI systems processing personal data. When they conflict (e.g., transparency requirements vs trade secrets), no clear precedence exists yet. Compliance teams are making judgment calls that may be second-guessed.
- āSME exemptions and proportionality are generous on paper and stingy in practice. The text says requirements scale with organisation size and risk; in practice, SMEs are often held to enterprise standards by vendors who won't customise.
What's changed for non-EU companies:
- āExtraterritorial reach is real. If your AI output affects EU residents, you're in scope. This has driven concrete product changes at major US vendors.
- āThe Commission's enforcement posture is cooperative but tightening. Year one was guidance-heavy; year two is beginning to see enforcement actions. Waiting for enforcement before acting is a losing strategy.
Resources that matter for operational compliance:
- āThe official AI Act text and explainer ā the best single reference.
- āCNIL, ICO, and DPA guidance ā national regulators are producing sector-specific guidance that often clarifies what the Act left abstract.
- āIndustry association templates ā for SMEs without dedicated legal teams, trade-association templates are a practical starting point.
The honest framing: the AI Act is a serious regulatory regime that's being enforced with increasing rigour. It's not a checkbox exercise, and "we'll deal with it when enforcement actions start" is a strategy that has already cost some organisations. Getting ahead of it with documented, risk-based compliance programmes is cheaper than reacting.
Timeline of Obligations
The AI Act enters into force in phases:
| Date | What Takes Effect |
|---|---|
| Feb 2, 2025 | Prohibited AI practices banned |
| Aug 2, 2025 | GPAI model obligations begin |
| Aug 2, 2026 | High-risk AI system rules apply |
| Aug 2, 2027 | Embedded AI systems in regulated products |
Current Status (January 2026): Prohibited practices are already illegal. GPAI obligations are in effect. High-risk requirements take effect in 7 months.
Risk Classification System
The AI Act creates a risk-based framework with four tiers:
Prohibited AI (Unacceptable Risk)
Banned since February 2, 2025:
ā Prohibited Systems (Banned since Feb 2, 2025):
- āSubliminal manipulation, AI that manipulates beyond person's consciousness, causes or risks significant harm
- āExploitation of vulnerabilities, Targeting age, disability, social situation to materially distort behavior
- āSocial scoring by public authorities, Evaluating trustworthiness over time leading to detrimental treatment
- āReal-time remote biometric identification, In public spaces for law enforcement (limited exceptions for serious crimes)
- āEmotion inference in workplace/education, Except for medical/safety purposes
- āUntargeted facial image scraping, Building databases from internet/CCTV
- āBiometric categorization, Inferring sensitive attributes (race, politics, etc.)
High-Risk AI
Fully regulated from August 2, 2026:
Systems considered high-risk fall into two categories:
Category 1: Safety Components
- āAI in medical devices
- āAI in vehicles
- āAI in machinery
- āAI in toys
- āAI in aviation
- āAI in marine equipment
Category 2: Specific Use Cases
- āBiometric identification/categorization
- āCritical infrastructure management
- āEducation access and assessment
- āEmployment and HR decisions
- āEssential services access (credit, benefits)
- āLaw enforcement applications
- āMigration and border control
- āJustice administration
Limited Risk
Systems requiring transparency:
- āChatbots (must disclose AI nature)
- āEmotion recognition systems
- āBiometric categorization
- āDeepfakes and AI-generated content
Minimal Risk
All other AI systems-no specific obligations beyond existing law.
General Purpose AI (GPAI) Requirements
Since August 2025, providers of general-purpose AI models face specific obligations:
All GPAI Models
Requirements for ALL foundation models:
1ļøā£ Technical Documentation
- āTraining and testing processes
- āEvaluation results with methodology
- āKnown limitations
2ļøā£ Information for Downstream Providers
- āCapabilities and limitations
- āIntended and unintended uses
- āIntegration guidance
3ļøā£ Copyright Compliance
- āPolicy for respecting copyright
- āOpt-out mechanism compliance (for EU training)
- āSummary of training data
4ļøā£ Transparency
- āPublish sufficiently detailed summary
- āEU AI Office template available
Systemic Risk GPAI
Additional requirements for models with systemic risk (10^25 FLOPs training threshold or designation):
Additional requirements for SYSTEMIC RISK models:
1ļøā£ Model Evaluation
- āAdversarial testing
- āRed teaming for vulnerabilities
- āDocument and mitigate risks
2ļøā£ Incident Tracking
- āMonitor and report serious incidents
- āNotify AI Office within 24 hours
3ļøā£ Cybersecurity
- āAdequate protection measures
- āModel weight security
4ļøā£ Energy Reporting
- āTraining compute consumption
- āEnergy usage data
Who qualifies? GPT-5, Claude 4, Gemini 3 and similar frontier models.
High-Risk AI Obligations
Starting August 2, 2026, high-risk AI systems must comply with comprehensive requirements:
Risk Management System
# Conceptual implementation of risk management
class AIRiskManagementSystem:
def __init__(self, ai_system):
self.system = ai_system
self.risks = []
self.mitigations = []
def identify_risks(self):
"""
Continuous process to identify:
- Known and foreseeable risks
- Risks from intended use
- Risks from reasonably foreseeable misuse
"""
return self.analyze_system()
def implement_mitigations(self, risks):
"""
For each identified risk:
- Design mitigation measures
- Test effectiveness
- Document decisions
"""
for risk in risks:
mitigation = self.design_mitigation(risk)
if not self.test_mitigation(mitigation):
self.escalate(risk)
def monitor_continuously(self):
"""
Post-deployment monitoring for:
- New emerging risks
- Mitigation effectiveness
- Incident patterns
"""
pass
Data Governance
Requirements for training, validation, and testing data:
| Requirement | What It Means |
|---|---|
| Relevance | Data appropriate for intended purpose |
| Representativeness | Reflects deployment population |
| Completeness | Sufficient for the use case |
| Bias examination | Actively look for and address biases |
| Gap identification | Document data limitations |
| Error-free | Reasonable measures to ensure quality |
Technical Documentation
Prepare and maintain documentation covering:
Technical Documentation Requirements:
1ļøā£ General Description
- āIntended purpose
- āSystem architecture
- āInterfaces with other systems
- āSoftware versions
2ļøā£ Development Process
- āDesign specifications
- āDecisions made and rationale
- āTraining methodologies
- āTesting procedures
3ļøā£ Performance Metrics
- āAccuracy measures
- āRobustness testing
- āBias evaluation
- āCybersecurity measures
4ļøā£ Monitoring System
- āHow performance is tracked
- āLogging capabilities
- āUpdate procedures
Transparency for Users
Deployers (those who use high-risk AI) must:
User Transparency Requirements:
1ļøā£ Inform Affected Persons
- āThat they are subject to high-risk AI
- āPurpose of the system
- āHow decisions are made (to extent possible)
2ļøā£ Meaningful Explanation
- āWhen requested by affected person
- āExplain the decision's main reasoning
- āWithin 30 days of request
3ļøā£ Human Oversight
- āPersons assigned to oversee
- āCompetent to perform oversight
- āAuthority to override or reject
Human Oversight
High-risk AI must be designed for effective human oversight:
Human Oversight Design Requirements:
1ļøā£ Interface Design
- āEnable operator to understand capabilities/limitations
- āCorrectly interpret system output
- āOverride or interrupt operation
2ļøā£ Operator Capabilities
- āDecide not to use in particular situation
- āDisregard or reverse system output
- āIntervene or stop operation
3ļøā£ Documentation
- āClear instructions for operators
- āTraining requirements specified
- āEscalation procedures defined
Conformity Assessment
Before deployment, high-risk systems must undergo:
- āSelf-assessment for most high-risk categories
- āThird-party assessment for biometric identification and critical infrastructure
AI Literacy Obligation
New requirement effective February 2025:
Article 4 - AI Literacy:
Organizations deploying AI must ensure staff have sufficient AI literacy to:
- āUnderstand AI capabilities and limitations
- āUse AI systems appropriately
- āMake informed decisions about AI outputs
- āRecognize potential risks and biases
This applies to all organizations deploying AI, not just high-risk systems.
Implementation:
- āTraining programs for AI users
- āDocumentation and guidelines
- āCompetency assessments
- āRegular updates as technology evolves
Practical Compliance Steps
Step 1: Classify Your AI Systems
For each AI system, determine:
- āIs it prohibited? (Stop immediately if yes)
- āIs it high-risk? (Full compliance by Aug 2026)
- āIs it limited risk? (Transparency requirements)
- āIs it minimal risk? (Voluntary codes of practice)
For GPAI models:
- āAre you a provider? (Documentation + info requirements)
- āDoes it have systemic risk? (Additional requirements)
Step 2: Gap Analysis
Compare current practices to requirements:
| Requirement | Current State | Gap | Priority |
|---|---|---|---|
| Risk management | Informal | Major | High |
| Technical docs | Partial | Moderate | High |
| Data governance | Basic | Major | High |
| Human oversight | Exists | Minor | Medium |
| Transparency | Ad hoc | Major | High |
| AI literacy | None | Major | Medium |
Step 3: Prioritized Implementation
Priority 1 (Immediate):
- āEnsure no prohibited practices
- āBegin risk management system design
- āStart documentation
Priority 2 (Q1-Q2 2026):
- āComplete technical documentation
- āImplement data governance
- āEstablish human oversight
Priority 3 (By August 2026):
- āConformity assessment
- āRegistration in EU database
- āFull compliance verification
Penalties
Non-compliance carries significant fines:
| Violation | Maximum Fine |
|---|---|
| Prohibited AI | ā¬35M or 7% global turnover |
| High-risk obligations | ā¬15M or 3% global turnover |
| Other provisions | ā¬7.5M or 1.5% global turnover |
| Incorrect information | ā¬7.5M or 1% global turnover |
For SMEs and startups: Fines calculated proportionally to size.
Resources
Official Sources
- āEU AI Office: Central coordinating authority
- āAI Act text: Official Journal of the European Union
- āGuidance documents: AI Office templates and guides
Implementation Support
- āRegulatory sandboxes in member states
- āAI Pact for voluntary early compliance
- āStandards development (ISO, CEN/CENELEC)
In Brief
- ā
The EU AI Act is active now-prohibited practices banned, GPAI rules in effect
- ā
Risk classification determines obligations-know which category your AI falls into
- ā
High-risk requirements begin August 2026-seven months to achieve full compliance
- ā
GPAI providers face specific obligations-documentation, transparency, copyright compliance
- ā
AI literacy is now mandatory-staff must be trained to use AI appropriately
- ā
Penalties are significant-up to ā¬35M or 7% of global turnover
- ā
Start compliance now-the timeline is tight for comprehensive requirements
Navigate AI Regulation and Ethics
The EU AI Act represents a new era of AI governance. Understanding the regulatory landscape-and the ethical principles behind it-is essential for anyone building or deploying AI systems.
In our Module 8, AI Ethics & Safety, you'll learn:
- āThe global AI regulatory landscape
- āEthical frameworks for AI development
- āBias detection and mitigation
- āTransparency and explainability principles
- āHuman oversight design patterns
- āRisk assessment methodologies
These skills prepare you for responsible AI development in a regulated world.
Learn AI, from prompts to agents
Module 8 ā Ethics, Security & Compliance
Navigate AI risks, prompt injection, and responsible usage.
Dorian Laurenceau
Full-Stack Developer & Learning DesignerFull-stack web developer and learning designer. I spent 4 years as a freelance full-stack developer and 4 years teaching React, JavaScript, HTML/CSS and WordPress to adult learners. Today I design learning paths in web development and AI, grounded in learning science. I founded learn-prompting.fr to make AI practical and accessible, and built the Bluff app to gamify political transparency.
One practical AI workflow in your inbox
Methods, resources and new exercises. Free, unsubscribe at any time.
āRelated articles
FAQ
What is the EU AI Act?+
The EU AI Act is the world's first comprehensive AI regulation. It categorizes AI systems by risk level (unacceptable, high, limited, minimal) and imposes corresponding requirements.
When does the EU AI Act take effect?+
The Act entered into force August 2024. Key deadlines: AI literacy (Feb 2025), prohibited AI (Feb 2025), GPAI rules (Aug 2025), high-risk systems (Aug 2026-2027).
What AI systems are prohibited under the EU AI Act?+
Banned systems include social scoring, predictive policing, emotion recognition in workplaces/schools, untargeted facial recognition scraping, and AI exploiting vulnerabilities.
Does the EU AI Act apply to non-EU companies?+
Yes. The Act applies to anyone placing AI systems on the EU market or whose AI outputs affect EU residents-regardless of where the company is based.