The EU AI Act entered into force on 1 August 2024 and applies in stages. Prohibitions and AI literacy have applied since 2 February 2025, general-purpose AI model rules since 2 August 2025, and the transparency rules and enforcement since 2 August 2026. The high-risk rules were delayed by the Digital Omnibus: Annex III systems from 2 December 2027 and AI inside Annex I regulated products from 2 August 2028 (verified October 2026).
The EU AI Act does not switch on all at once. It applies in phases, and for most enterprises the phases that matter are still ahead. The prohibitions and AI-literacy provisions already apply, general-purpose AI model obligations have begun, and the transparency duties started on 2 August 2026. The obligations that touch the largest number of organisations — those for high-risk AI systems — were pushed back in July 2026 by the Digital Omnibus on AI, to 2 December 2027 for Annex III systems and 2 August 2028 for AI inside regulated products.
| Date | What applies (as amended by Regulation (EU) 2026/1744) | Status on 30 October 2026 |
|---|---|---|
| 1 August 2024 | The AI Act enters into force | Done |
| 2 February 2025 | Prohibited practices; AI literacy (softened in 2026 to supporting staff literacy) | Applies |
| 2 August 2025 | General-purpose AI model obligations; governance bodies and penalties framework | Applies |
| 27 July 2026 | Digital Omnibus on AI in force | Done |
| 2 August 2026 | General date of application; Article 50 transparency duties; enforcement by the AI Office and national authorities | Applies |
| 2 December 2026 | Article 5 bans on AI generating child sexual abuse material or intimate imagery without consent; end of the watermarking grace period for systems placed on the market before 2 August 2026 | Next |
| 2 August 2027 | General-purpose AI models placed on the market before 2 August 2025 must comply; at least one AI regulatory sandbox per Member State | Upcoming |
| 2 December 2027 | High-risk obligations for stand-alone Annex III systems (originally 2 August 2026) | Delayed |
| 2 August 2028 | High-risk obligations for AI in products covered by Annex I (originally 2 August 2027) | Delayed |
| 2 August 2030 | High-risk systems intended for use by public authorities and placed on the market before the high-risk rules applied | Upcoming |
| 31 December 2030 | AI components of the large-scale EU IT systems listed in Annex X | Upcoming |
Dates are taken from Articles 111 and 113 of the consolidated text and the implementation timeline on the Commission’s AI Act Service Desk (verified October 2026).
This is not a legal guide, and nothing here is legal advice. It is an operational readiness view for deployers: organisations using AI systems in regulated contexts, who need to know what lands when and what infrastructure makes each obligation demonstrable. Where the obligations assume traceability, human oversight, and record-keeping, an on-premises platform is often the most direct way to hold the evidence yourself rather than depend on a provider for it.
Is EU AI Act enforcement delayed?
Partly, and the part that was delayed is the part most enterprises were preparing for.
What went ahead on 2 August 2026. The Act became generally applicable. The Article 50 transparency rules started, the AI Office and the market surveillance authorities of the Member States took over enforcement, and the Commission’s power to fine providers of general-purpose AI models under Article 101 began, because Article 113 held that article back when the rest of the general-purpose AI chapter applied in August 2025. The prohibitions and AI-literacy rules, in force since February 2025, now have authorities behind them.
What was delayed. The Digital Omnibus moved the high-risk rules, not the Act as a whole:
| Obligation | Original date | Date after Regulation (EU) 2026/1744 | Delay |
|---|---|---|---|
| Stand-alone high-risk systems in Annex III | 2 August 2026 | 2 December 2027 | 16 months |
| High-risk AI in Annex I regulated products | 2 August 2027 | 2 August 2028 | 12 months |
| Watermarking for generative systems already on the market | 2 August 2026 | 2 December 2026 | 4 months |
Will there be another delay? Nothing in force says so. The Omnibus is now part of the Act, and moving a date again would need a new amending regulation passed by the Parliament and the Council. Plan to the dates in the table above, and check the consolidated text on EUR-Lex before each planning cycle rather than relying on commentary.
The practical reading for a deployer: the deadline moved, the obligations did not. Article 26 still lists the same duties for deployers of high-risk systems, and an organisation that starts in 2027 will have less time than it had in 2026.
EU AI Act implementation timeline for 2025 and 2026
The two years since entry into force did most of the setting up. Here is what each one meant in practice.
2025. On 2 February the Article 5 prohibitions took effect, banning practices such as manipulative techniques that cause significant harm, social scoring and untargeted scraping of facial images, alongside the AI-literacy duty. On 2 August the general-purpose AI chapter applied to model providers, Member States had to designate national competent authorities and adopt penalty rules, and the EU-level bodies, the AI Board, the Scientific Panel and the Advisory Forum, had to be in place.
2026. The Commission proposed the Digital Omnibus in November 2025, a political agreement followed on 7 May 2026, and the regulation entered into force on 27 July 2026. Six days later, on 2 August, the Act became generally applicable without its high-risk chapter. AI literacy was rewritten so that providers and deployers must take measures to support it, without having to guarantee any person’s level. The year closes on 2 December 2026 with the new prohibitions and the end of the watermarking grace period.
If you are reading this in late 2026, three things should already be true in your organisation: no system in use falls into a prohibited category, staff who operate AI have had role-appropriate literacy support, and every user-facing assistant or generative workflow meets Article 50. Our Article 50 guide covers that last one in detail, and the prohibited practices list covers the first.
First, know your role and your risk category
Two questions determine what applies to you before any date does.
Are you a provider or a deployer? A provider develops a system or places it on the market under its own name. A deployer uses a system under its own authority. Most enterprises adopting AI are deployers — and deployers of high-risk systems have their own obligations, including operating the system according to instructions, ensuring human oversight, monitoring operation, and keeping logs. If you fine-tune or substantially modify a system, you may take on provider obligations too. This distinction, and where it moves under private deployment, is explored in Human Oversight in AI Systems: EU AI Act Requirements.
Is the system high-risk? The heaviest obligations attach to high-risk systems — broadly, those listed in Annex III (areas such as employment, essential services, law enforcement, and critical infrastructure) and those that are safety components of regulated products under Annex I. Many enterprise systems are not high-risk and carry lighter, mainly transparency-oriented duties. Getting the classification right is the first readiness task; over- and under-classifying both carry cost.
The important point for planning: the obligations follow the risk category and your role, not the hosting model. Running on-premises does not reduce what the law requires. What it changes is your ability to produce the evidence yourself.
The phases, and what each one asks of a deployer
Phase 1 — In effect: prohibitions and AI literacy (from 2 February 2025)
The Act’s prohibited practices and the AI-literacy obligation already apply. For a deployer this means two things are due now: confirming that no system in use falls into a prohibited category, and ensuring staff who operate or oversee AI have a level of AI literacy appropriate to their role.
Readiness: maintain an inventory of AI systems in use with a documented risk classification for each, and run role-appropriate AI-literacy enablement for operators and overseers.
Phase 2 — In effect: general-purpose AI and governance (from 2 August 2025)
Obligations for general-purpose AI model providers have begun, national competent authorities are being stood up, and the EU-level governance structures are operational. Deployers are mainly affected indirectly — through the documentation and instructions that GPAI and system providers must now supply.
Readiness: collect and retain provider documentation for the models and systems you deploy. If you route across multiple models, know which models you use and keep their documentation on file — a task made easier when model routing is an explicit, catalogued decision rather than a hidden default.
Phase 3 — In effect: transparency duties and enforcement (from 2 August 2026)
The Article 50 transparency obligations kept their original start date. People must be told when they are interacting with an AI system unless it is obvious, deployers of emotion recognition or biometric categorisation must inform the people exposed to it, and deepfakes and certain AI-generated text must be disclosed as such. Providers of generative systems must mark synthetic output in a machine-readable way; systems already on the market before 2 August 2026 have until 2 December 2026 to add that marking.
Readiness: list every user-facing assistant and generative workflow you run, and confirm each one discloses that it is AI and carries whatever content marking your provider supplies.
Phase 4 — Next: high-risk systems under Annex III (from 2 December 2027)
This is the phase most enterprises are preparing for. The Digital Omnibus moved the core obligations for stand-alone Annex III high-risk systems (employment, credit scoring, essential services, education, law enforcement, border control and similar uses) from 2 August 2026 to 2 December 2027.
For a deployer of a high-risk system, the operational obligations include using the system in line with the provider’s instructions, ensuring meaningful human oversight, monitoring operation and reporting serious incidents, and keeping the logs the system automatically generates.
Readiness: this is where infrastructure does real work — see the checklist below.
Phase 5 — Later: high-risk in regulated products under Annex I (from 2 August 2028)
Obligations for high-risk AI that is a safety component of products already covered by EU harmonised legislation, such as medical devices, machinery and vehicles, now apply from 2 August 2028 instead of 2 August 2027. This mainly concerns organisations building or deploying AI inside regulated physical or software products.
Readiness: the same control base as Phase 4, integrated with the existing product-safety and conformity processes those sectors already run.
What the Digital Omnibus changed
The Commission proposed the “Digital Omnibus” in late 2025. Parliament and Council adopted it as Regulation (EU) 2026/1744 on 8 July 2026; it was published in the Official Journal on 24 July and entered into force on 27 July 2026, a week before the original high-risk date would have bitten.
The changes that matter to a deployer:
- High-risk dates moved. Annex III systems now follow 2 December 2027, and AI in Annex I products follows 2 August 2028.
- Transparency did not move. Article 50 still applied from 2 August 2026, with a four-month grace period for watermarking on systems already on the market.
- AI literacy was softened. Providers and deployers must support the development of AI literacy among their staff rather than guarantee a specific level.
- A new prohibition was added. From 2 December 2026, Article 5 also bans AI systems used to generate non-consensual intimate imagery and child sexual abuse material.
For planning, the direction of the obligations is unchanged. The deferral changes when, not whether, and organisations that paused their high-risk programmes in 2026 now have roughly fourteen months to build the control base properly instead of in a rush. Always confirm dates against EUR-Lex, because the Act can be amended again.
What each date means for providers and deployers
| Date | Providers must | Deployers must |
|---|---|---|
| 2 February 2025 | Stop placing prohibited systems on the market; support staff AI literacy | Stop using prohibited systems; support staff AI literacy |
| 2 August 2025 | General-purpose model providers: technical documentation, information for downstream providers, copyright policy, public training-content summary | Collect the documentation providers now supply |
| 2 August 2026 | Mark synthetic output in a machine-readable way; design chatbots to disclose that they are AI | Disclose deepfakes, emotion recognition and biometric categorisation to the people exposed |
| 2 December 2027 | Annex III systems: risk management, data governance, logging capability, conformity assessment, registration | Annex III systems: follow instructions, assign human oversight, monitor, keep logs, inform workers and affected people |
| 2 August 2028 | Annex I products: the same high-risk duties, inside existing product conformity routes | Annex I products: the same deployer duties |
Two roles can sit in one company. Fine-tuning or substantially modifying a system, or putting your own name on it, can turn a deployer into a provider for that system, with the left-hand column applying from the same dates. For what a missed date costs, see our breakdown of AI Act fines; for non-EU firms, the guide to the Act’s reach outside the EU explains when it applies at all.
Deployer log retention: the six-month minimum
Article 26(6) is the deployer duty that most directly becomes an infrastructure requirement. Deployers of high-risk systems must keep the logs the system generates automatically, to the extent those logs are under their control, for a period appropriate to the system’s intended purpose and of at least six months, unless Union or national law, in particular data protection law, provides otherwise (verified October 2026). For Annex III systems the duty applies from 2 December 2027.
Three phrases in that sentence decide how you design for it:
- “Under their control.” If a hosted provider keeps the logs, your evidence depends on its retention settings and export features. When the system runs in your own environment, the logs are under your control by default, and so is the duty.
- “At least six months.” Six months is a floor, not a target. A credit or employment decision can be challenged long after that, and sector record-keeping rules may require more.
- “Unless … data protection law.” Logs of a high-risk system often contain personal data, so the GDPR’s storage limitation applies too. The answer is a written retention rule per log type, not keeping everything forever.
| Log type | Minimum under Article 26(6) | Design considerations |
|---|---|---|
| System event logs generated by the high-risk system | Six months | Tamper-evident storage, access restricted to named roles |
| Human-oversight records: who reviewed, approved or overrode | Not set by Article 26(6); keep with the decision | Retain as long as the decision can be challenged |
| Prompts and outputs containing personal data | Six months if part of the system’s logs | Minimise or redact at capture; justify any longer period |
| Incident and malfunction reports | Not set by Article 26(6) | Keep with the incident record and provider correspondence |
The deployer readiness checklist, mapped to on-premises controls
The high-risk deployer obligations translate into a small set of capabilities. Each is easier to demonstrate when you own the infrastructure that produces the evidence.
- System inventory and classification. A living register of AI systems in use, each with a documented risk category, purpose, owner, and the provider documentation on file. This underpins every other obligation.
- Human oversight that is real, not nominal. Defined points where a person can review, approve, or intervene in a high-risk workflow — with the authority and information to do so meaningfully. On-premises deployment lets you place oversight gates exactly where policy requires. See Human Oversight in AI Systems.
- Automatic logging, retained. High-risk systems generate logs; deployers must keep them. Owning the log store means retention, access control, and integrity are yours to set — covered in AI Agent Observability: Logs, Traces, and Audit Trails.
- Traceability of decisions. The ability to reconstruct what a system did, on which data, using which model, and who approved the outcome — the decision-receipt pattern turns raw logs into reviewable records.
- Monitoring and incident reporting. Operational monitoring that can surface serious incidents and malfunctions in time to report them, with a defined path for doing so.
- Documentation that assembles into evidence. The classifications, oversight designs, logs, and provider records need to come together into a coherent pack when an authority asks — the goal of the EU AI Act evidence pack approach, and the architecture behind it in EU AI Act-Ready On-Premises AI Architecture.
No platform delivers compliance out of the box, and none can guarantee it. What owning the infrastructure gives a deployer is direct control over the six capabilities above — the operational substance the obligations assume — rather than a dependency on a third party to produce your evidence for you.
How VDF AI supports deployer readiness
VDF AI is designed for private, on-premises, and air-gapped deployment, which keeps the logs, audit trails, human-oversight points, and documentation for high-risk systems inside infrastructure you control. VDF AI Networks and VDF AI Agents let you place human-in-the-loop approval gates where policy requires, record decisions as traceable receipts, and retain governed logs on your own terms. It does not make an organisation compliant — that depends on your classifications, controls, and documentation — but it provides the operational foundation those obligations assume.
Start from the two questions — your role and your risk category — build the control base now, and keep checking the consolidated text on EUR-Lex, since the Omnibus shows the timeline can still move.
Related EU AI Act guides
The timeline is the backbone; these pages cover the obligations it schedules.
- Check whether your use case is in scope with the EU AI Act compliance checker.
- Sector deadlines: banks and insurers, HR and recruitment.
- Transparency from August 2026: Article 50 for enterprise AI.
- What a deployer must evidence for oversight: human oversight requirements.
Further reading
- Regulation (EU) 2026/1744 on EUR-Lex
- AI Act implementation timeline, AI Act Service Desk
- Article 113, entry into force and application
- Article 111, systems already on the market
- Article 26, obligations of deployers
- Regulatory framework for AI, European Commission
- EU AI Act-Ready On-Premises AI Architecture
- Human Oversight in AI Systems: EU AI Act Requirements
- The EU AI Act Evidence Pack for On-Prem AI
- AI Decision Receipts for Regulated Workflows
Preparing for the high-risk phases? See VDF AI’s approach to governed on-premises AI or book a demo.