Skip to main content
Sign in See the demo
Artificial intelligence

EU AI Act: what actually changes for AI tools in business in 2026

13 July 20266 min read

Five waves of application, each starting on its actual date: 1 August 2024, 2 February 2025, 2 August 2025, 2 August 2026 (the purple wave), then high risk spread out towards 2027 and 2028.

In short.
The European AI regulation regulates by risk, not by technology: it is the use that determines the obligations, not the tool. The timetable is staggered until 2027. For a deployment in a company, the practical issue lies in classifying the use and in the documentation that goes with it.

Forget the 450-page text. Here, without jargon, is what the world’s first major AI law actually requires of your company, and by when.

The EU AI Act is no longer a distant project. It is a regulation in force, applying in stages, and several of its obligations already concern companies that use AI, not just those that develop it. Yet many executives have only a hazy view of it: a huge, technical text whose impact on day-to-day work is not very clear.

This article has a simple goal: to translate the law into concrete obligations, to tell you what already applies, what is coming in 2026, and what you should do right now. Without needless legal jargon.

The principle: regulation by risk, not by technology

The first thing to understand: the AI Act does not regulate “AI” as a whole. It classifies uses by their level of risk, and imposes increasing obligations as the risk rises.

Four categories. Uses posing an unacceptable risk (generalised social scoring, manipulation, certain forms of biometric surveillance) are banned outright. High-risk uses — AI deciding on credit, sorting CVs, involved in education, health or critical infrastructure — are allowed but subject to strict requirements: documentation, human oversight, traceability, risk management. Limited-risk uses — a chatbot, a content generator — are mainly subject to transparency obligations. Finally, the vast majority of systems, posing minimal risk, are subject to no new obligation.

The first question to ask is therefore not “am I concerned?” but “which category does each of my uses of AI fall into?”.

The actual timetable (updated mid-2026)

The regulation entered into force on 1 August 2024, but its obligations kick in in waves. Here is where things stand.

Already applicable since February 2025: the ban on unacceptable-risk practices and — an often overlooked point — an “AI literacy” obligation: organisations must ensure that the people who use their AI systems have a sufficient level of competence to do so in an informed way.

Applicable since August 2025: the obligations on providers of general-purpose AI models (the large GPAI-type models) and the setting up of European governance (the AI Office, etc.).

2 August 2026: the big deadline: this is the date on which most of the remaining rules become applicable and actual enforcement begins. Above all, it marks the entry into application of the transparency obligations (Article 50): clearly informing users that they are interacting with an AI, and identifying AI-generated content.

The recent nuance to know: the timetable for high-risk systems has been relaxed. Following a political agreement in May 2026 (the “Digital Omnibus”), the application of these rules has been postponed and is now conditional on the availability of the reference technical standards. In practice, the deadlines for high-risk uses are spread out towards the end of 2027 and 2028 depending on the category, and the obligation to mark AI-generated content has been moved to the end of 2026. In other words: the spirit of the law does not change, but the legislator has given itself — and you — a little more time on the heaviest points.

This flexibility should not be read as a general reprieve. The transparency and literacy obligations are very much in place.

What it actually changes for you

Beyond the dates, what really weighs on a company that uses AI tools (without developing them)? Four things.

Knowing what you use. The AI Act assumes you have an inventory of your AI systems — including third-party tools and AI components embedded in your software. You cannot classify the risk of what you do not know about. It is the first workstream, and it is often behind schedule.

Transparency. If you use a conversational agent with customers, or if you publish AI-generated content, you will have to say so. The era of invisible AI is over.

Traceability and justification. For sensitive uses, it will no longer be enough for the AI to produce an answer: you will need to be able to explain how it produced it, from which data, with what human oversight. A black box that spits out a result without justification becomes a compliance risk.

Accountability. The regulation provides for dissuasive penalties, calculated as a percentage of worldwide turnover for the most serious breaches. Compliance is therefore not just good practice: it is a financial exposure to be managed.

The positive side effect: trust becomes an asset

The AI Act is often presented as a constraint. That reading is incomplete. In reality, the regulation imposes exactly what demanding buyers were already asking for: AI that is transparent, traceable and explainable, with data kept under control.

For a company, being able to prove that its AI tools respect these principles becomes an argument for trust with its customers, its regulators and its partners. Compliance, done well, does not slow you down: it reassures and sets you apart.

This is precisely the philosophy of tools designed from the outset for regulated environments. Optivalue.ai is a good illustration: the French platform handles compliance and security questionnaires with a standard of rigour that matches the spirit of the regulation — each answer cites its source (document, page, date), the system abstains rather than invents when no data supports a claim, and data can remain hosted under sovereign control. Where the AI Act calls for transparency, traceability and control over data, this type of architecture delivers them by design rather than as a patch. It is a smart way of turning a regulatory obligation into an operational advantage.

Your minimum roadmap

If you were to remember five actions to launch now, here they are.

First, map all your uses of AI, internal and through suppliers. Next, classify each one by risk level. Then train your teams in the informed use of these tools (the literacy obligation is already in force). Check your transparency obligations for everything that is in contact with the public. And finally, favour explainable and traceable tools, able to justify their answers — that will be your best insurance on the day of an inspection.

Key takeaways

The EU AI Act is not a distant wave: it is a tide rising in stages, and several of its obligations are already here. The good news is that becoming compliant mostly means adopting good practices that serious organisations were already aiming for: knowing what you use, saying so, tracing it, explaining it.

Companies that approach the subject in 2026 not as a legal chore but as an opportunity to make their use of AI more reliable will gain a head start. The others will discover, at the worst possible moment, that an AI you cannot explain is an AI you cannot defend.

This article is provided for information purposes and does not constitute legal advice. The timetable and obligations of the EU AI Act are evolving; for your specific obligations, refer to the official texts of the European Commission and to a qualified professional.

Adopt AI that is ready for compliance

Optivalue.ai was designed for regulated environments: sourced and explainable answers, abstention when there is no evidence, sovereign hosting (SaaS, private cloud or on-premise). Everything you need to approach the EU AI Act with a head start.

Discover Optivalue.ai →Test the platform on your own documents.

Back to top

A quote is easier to discuss after a demonstration on your own documents.