EU AI Act readiness

The AI Act dates, as amended in July 2026 Six dates in order: prohibitions and AI literacy from 2 February 2025, general-purpose model rules from 2 August 2025, most rules from 2 August 2026, a new prohibition from 2 December 2026, Annex III high-risk rules from 2 December 2027 and rules for AI in regulated products from 2 August 2028. 2 February 2025 Prohibitions, AI literacy. 2 August 2025 General-purpose model rules. 2 August 2026 Most rules, transparency. 2 December 2026 New prohibition; labelling transition. 2 December 2027 High-risk, Annex III areas. 2 August 2028 High-risk AI in regulated products.
As of November 2026; the Commission’s timeline governs.

The dates moved in July 2026, and the work did not get smaller: an organization still has to know which AI systems it has, in which role, and what each one is evidenced to do.

The short version

EU AI Act readiness is working out which role an organization has for each AI system, which obligations and dates apply to it, and preparing the inventory, documentation and controls those obligations rest on.

Which role you have, whether a system is high-risk and what that requires are legal questions for your counsel; we prepare the inventory, the technical evidence and the controls they work from. As of November 2026 the points below are from the Act, the amending Regulation and the Commission’s AI Act page and timeline.

The dates

The AI Act entered into force on 1 August 2024; its prohibitions and AI literacy provisions apply from 2 February 2025, its rules for general-purpose AI models from 2 August 2025, and most other rules, including the transparency obligations in Article 50, from 2 August 2026.

Regulation (EU) 2026/1744, the Digital Omnibus on AI, entered into force on 27 July 2026; it moved the rules for high-risk AI systems in the areas listed in Annex III to 2 December 2027 and for high-risk AI embedded in regulated products to 2 August 2028. The Commission reports it in its news item of 27 July 2026. The Commission proposed it on 19 November 2025 and a political agreement followed on 7 May 2026; the amending Regulation is now in force.

The Omnibus also added a prohibition on AI systems that generate non-consensual intimate material or child sexual abuse material, which applies from 2 December 2026, and gave providers of generative systems already on the market until 2 December 2026 to comply with the labelling duty in Article 50(2).

Your role for each system

A provider develops an AI system or has one developed and places it on the market or puts it into service under its own name or trademark, while a deployer uses an AI system under its own authority outside a personal non-professional activity; the Act can also reach providers and deployers outside the Union where the system’s output is used in the Union.

We map the role system by system, from the AI use inventory, and hand the map to your counsel.

Which role a party has A decision from what the organization does with an AI system. If it develops the system, or has it developed, and puts it on the market under its own name, it is a provider. If it uses the system under its own authority, it is a deployer. A party can be both. What does the organization do withthe AI system? Develops it and puts it on the marketunder its name Provider duties apply Uses it under its own authority Deployer duties apply
The roles come from the Act’s definitions; counsel confirms them.

What the Act asks for

The Commission lists nine prohibited practices, among them harmful manipulation, social scoring, untargeted scraping to build facial recognition databases and emotion recognition in workplaces and schools; the first eight have applied since February 2025 and the ninth applies from December 2026.

For high-risk AI systems the Commission lists requirements including risk assessment and mitigation, quality of the data feeding the system, logging, documentation, information to the deployer, human oversight, and robustness, cybersecurity and accuracy.

As replaced by the Omnibus, Article 4 requires providers and deployers to take measures to support the development of AI literacy of their staff and of other people who operate or use AI systems on their behalf, without a duty to guarantee any specific level of literacy.

The transparency duties from August 2026 include telling people when they are dealing with an AI system and making AI-generated content identifiable, as the Commission describes them.

What we prepare

For a Canadian supplier, the earlier article on the EU AI Act and Canadian suppliers sets out how the Act reaches suppliers outside the Union and how a security review overlaps with it; it deliberately gives no dates, which this page does.

How the work is bounded

The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.

SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.

Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.

Questions we are asked

What does EU AI Act readiness cover?

EU AI Act readiness is working out which role an organization has for each AI system, which obligations and dates apply to it, and preparing the inventory, documentation and controls those obligations rest on.

When do the AI Act’s rules apply?

The AI Act entered into force on 1 August 2024; its prohibitions and AI literacy provisions apply from 2 February 2025, its rules for general-purpose AI models from 2 August 2025, and most other rules, including the transparency obligations in Article 50, from 2 August 2026.

What did the Digital Omnibus on AI change?

Regulation (EU) 2026/1744, the Digital Omnibus on AI, entered into force on 27 July 2026; it moved the rules for high-risk AI systems in the areas listed in Annex III to 2 December 2027 and for high-risk AI embedded in regulated products to 2 August 2028.

What happens to AI literacy?

As replaced by the Omnibus, Article 4 requires providers and deployers to take measures to support the development of AI literacy of their staff and of other people who operate or use AI systems on their behalf, without a duty to guarantee any specific level of literacy.

What is the difference between a provider and a deployer?

A provider develops an AI system or has one developed and places it on the market or puts it into service under its own name or trademark, while a deployer uses an AI system under its own authority outside a personal non-professional activity; the Act can also reach providers and deployers outside the Union where the system’s output is used in the Union.

What does the Act require of high-risk systems?

For high-risk AI systems the Commission lists requirements including risk assessment and mitigation, quality of the data feeding the system, logging, documentation, information to the deployer, human oversight, and robustness, cybersecurity and accuracy.

Do you decide whether our system is high-risk?

Which role you have, whether a system is high-risk and what that requires are legal questions for your counsel; we prepare the inventory, the technical evidence and the controls they work from.

Tell us which AI systems you run

Say which systems you build, buy or use, and where their output is used. The reply says what a scope would cover. Related: the European Union page.

Discuss a scope