Contents
- Deadlines already passed: what is enforceable right now
- August 2026: the most critical deadline for most businesses
- August 2027: legacy systems already in use
- How to prioritise: action map by company type
- Five steps to structure your compliance programme
- What does AI Act compliance cost?
- How Yeeply can help
The EU AI Act does not have a single compliance date. It follows a phased calendar with milestones that have already passed and others arriving in the coming months. Knowing exactly where your organisation stands — and what to do before which deadline — is what separates an efficient compliance strategy from a last-minute scramble.
This guide is practical: which deadlines are already enforceable, which arrive in 2026-2027, and how to structure the work based on the type of AI system you develop or use.
Deadlines already passed: what is enforceable right now
| Date | What enters into force | Who is affected |
|---|---|---|
| August 2024 | The AI Act as binding law | Everyone |
| February 2025 | Prohibited AI systems — already applicable | All who develop or use AI in Europe |
| August 2025 | Obligations for general-purpose AI models (GPAI): GPT, Gemini, Claude, etc. | Providers of models trained above 10^25 FLOPs |
If your company uses or integrates general-purpose models to offer as a service or embed in products, the August 2025 obligations already apply: technical documentation of the model, acceptable use policy and training data summary.
August 2026: the most critical deadline for most businesses
August 2026 activates requirements for high-risk systems. This is the most relevant deadline for companies developing or using AI in HR, finance, healthcare, education or critical infrastructure.
- Risk management system: identification, analysis and mitigation of risks throughout the system lifecycle
- Data governance: documented practices for quality, representativeness and bias in training, validation and test data
- Technical documentation: full description of the system, its purpose, data used, performance metrics and known limitations
- Event logging: automatic logs enabling reconstruction of the system’s behaviour
- Transparency to the deployer: clear instructions for use, system limitations and maintenance conditions
- Human oversight: technical mechanisms enabling people using the system to intervene, pause it or reject its outputs
August 2027: legacy systems already in use
High-risk systems already on the market before the AI Act enters full application have until August 2027 to comply, unless they undergo significant design or purpose changes. This gives legacy products extra time, but does not remove the obligation.
How to prioritise: action map by company type
| Profile | Priority action | Urgent deadline |
|---|---|---|
| You develop AI for third parties (provider) | Classify each system by risk. Prepare technical documentation for high-risk ones | August 2026 |
| You use third-party AI in HR, finance or healthcare (deployer) | Verify that the provider complies. Implement human oversight and usage logs | August 2026 |
| You offer or integrate language models (GPAI) | Model documentation, acceptable use policy, training data summary | Already required (Aug 2025) |
| You use AI only for internal automation with no impact on people | Verify it genuinely qualifies as minimal risk. No additional obligations | — |
Five steps to structure your compliance programme
- 1. Inventory: list all AI systems your company develops, uses or contracts, including third-party models embedded in your products
- 2. Classification: determine the risk category for each system. Most will be minimal or limited risk
- 3. Gap analysis: for high-risk systems, identify which requirements are not yet met
- 4. Remediation plan: prioritise by criticality and deadline, assign owners and budget
- 5. Continuous documentation: the AI Act is not a one-off project — logging and risk management requirements are ongoing
What does AI Act compliance cost?
It depends on how many high-risk systems you have and their complexity. For a company with one high-risk system already in production, compliance costs — documentation, technical adjustments, initial audit — can range from £30,000 to £130,000, depending on whether the system was designed with these requirements in mind or needs retrofitting.
Systems designed correctly from the start — with logging, documentation and human oversight built into the architecture — are significantly cheaper to certify than those requiring retrospective adaptation.
How Yeeply can help
At Yeeply we work with certified software development companies that already incorporate AI Act requirements into their design and documentation processes. Whether you have an existing system that needs adapting or are starting a new development, we can help you get it right from the start.
Use the Request a quote button at yeeply.com/en or write to sales@yeeply.com.
Tags
Related posts
What Is the EU AI Act and Does It Apply to Your Business? (2026 Guide)
Practical guide to the EU AI Act 2026: risk pyramid, who must comply, deadlines already in force and fines of up to €35M. What UK businesses developing or using AI need to know.
AI Governance in Software: What UK Enterprises Are Getting Right (and Wrong) in 2026
What good AI governance looks like in practice for UK enterprises: what companies are getting right, what they miss, and the regulatory landscape for 2026.
Custom Software vs Off-the-Shelf ESG Platform: A Cost Comparison for UK SMEs
Build vs buy for ESG reporting software: licence costs, integration reality, and when custom development makes more sense than an off-the-shelf platform.
AI Integration Costs for Enterprise Apps: What UK Businesses Actually Pay
Real figures for AI integration in UK enterprise apps: chatbots, document processing, fine-tuning. Plus the hidden costs nobody quotes upfront.
ESG Software Requirements: What UK Companies Need to Build Before the UK SRS Deadline
What software UK companies need to build or buy before the UK SRS deadline: data integration, reporting, audit trails and realistic timelines.
How Much Does a Penetration Test Cost in the UK? (2026 Prices)
Real penetration testing prices in the UK for 2026: from £3,000 for a basic web pentest to £80,000 for red team. What's included, what drives costs, and how to hire without overpaying.
How Much Does Enterprise App Development Cost in 2026? Real Prices by Project Type
Enterprise app development costs in 2026 vary widely by project type, technology, and team location. Here are real price ranges and what drives them up or down.
MVP in 6 Weeks: A Step-by-Step Guide for Companies That Want to Test Before Investing
An MVP in 6 weeks is achievable — if you know what to put in it. This guide covers the phases, what to cut, realistic costs, and how to measure whether it worked.
What AI Agents Actually Do in a Software Project (And What They Still Can’t)
AI agents in software development do real, concrete things — and have real, concrete limits. Here's an honest breakdown of what they handle today and what still needs a human developer.
A Practical Guide to Building an Enterprise App in 2026 Without Burning Your Budget
Building an enterprise app without burning your budget starts long before the first line of code. A step-by-step guide to phases, common mistakes, and managing the project without technical expertise.
