EU AI Act Enforcement: The High-Risk Dates After the Digital Omnibus
From 2 December 2027, organisations deploying high-risk AI systems in the European market face mandatory compliance obligations, with fines that dwarf even GDPR penalties. AI in regulated products follows on 2 August 2028, and the Article 50 transparency duties already apply. Here is what your board needs to know, and what your engineering teams need to build.
Updated 28 October 2026: this post first said high-risk enforcement starts in August 2026 and described the Digital Omnibus as a proposal. The Omnibus is now law: Regulation (EU) 2026/1744, in force since 27 July 2026. It moved the Annex III high-risk obligations to 2 December 2027 and Annex I to 2 August 2028. Article 50 transparency still applies from 2 August 2026. The title, timeline and checklist have been corrected to match.
The timeline you cannot ignore
The EU AI Act did not arrive all at once. It has been phased in deliberately, and each milestone narrows the window for organisations that have yet to act.
The AI Act, Regulation (EU) 2024/1689, enters into force. Its obligations then apply in phases.
Social scoring, manipulative AI, real-time biometric surveillance banned. Fines up to €35M or 7% turnover.
Foundation model transparency, training data summaries, copyright compliance. Systemic risk models face adversarial testing.
Regulation (EU) 2026/1744 enters into force and moves the high-risk application dates to December 2027 and August 2028.
People must be told when they are interacting with an AI system, and AI-generated content must be identifiable.
Generative AI systems already on the market before 2 August 2026 must mark their outputs as AI-generated.
Conformity assessments, CE marking, EU database registration. National authorities empowered to enforce and fine. Moved back from the date in the original 2024 text by the Digital Omnibus.
AI in medical devices, vehicles, industrial machinery and other products covered by EU product-safety law. Moved from 2 August 2027 by the Digital Omnibus.
The Digital Omnibus on AI, Regulation (EU) 2026/1744 of 8 July 2026, was published in the Official Journal on 24 July 2026 and entered into force on 27 July 2026. It moved the high-risk obligations to 2 December 2027 for Annex III systems and to 2 August 2028 for AI in products covered by Annex I. Deferred, not cancelled: the Article 50 transparency obligations have applied since 2 August 2026, and the oversight, logging and risk management work below is still what an assessor will ask you to evidence.
What counts as "high-risk"? More than you think
The high-risk classification catches a broad swath of enterprise AI use cases. If your organisation deploys AI in any of the following domains, your systems likely fall under the Act's most demanding requirements.
AI-driven screening, resume filtering, performance evaluation, promotion recommendations
Creditworthiness assessments, insurance risk profiling, fraud detection influencing individual decisions
AI managing energy grids, water systems, telecommunications, transport
Automated grading, admissions decisions, learning path recommendations
Predictive policing, evidence evaluation, migration processing
Eligibility determinations for public benefits, emergency dispatch prioritisation
The classification challenge is real. A significant minority of enterprise AI systems are clearly high-risk, while a substantial additional share have ambiguous classifications requiring formal assessment. If you have not inventoried your AI systems yet, you are already behind.
The Act applies to non-EU companies serving EU customers. US-based organisations deploying AI systems whose outputs are used in the EU are within scope.
The four articles that will define compliance
For CISOs and compliance officers preparing board-level briefings, four articles establish what amounts to a continuous compliance obligation – not a one-time certification exercise.
The compliance gap: frameworks tell you what, not how
Organisations seeking structure have turned to ISO/IEC 42001 and the NIST AI Risk Management Framework (AI RMF 2.0). ISO 42001 provides a plan-do-check-act framework aligning with roughly 40–50% of the Act's high-level requirements.
NIST AI RMF offers complementary voluntary guidance whose four core functions – Govern, Map, Measure, Manage – map well to the Act's risk management articles. Organisations operating in both markets can build programmes that satisfy both without duplicating effort.
But neither framework specifies how to generate the verifiable evidence that Articles 9, 12, and 14 require at the operational level. They tell you to log, monitor, and maintain human oversight. They do not tell you how to produce tamper-evident records that prove you did these things when a regulator comes asking.
For AI agents making thousands of decisions per day, this is not a process problem. It is an infrastructure problem. Manual compliance is impossible at agent scale.
What a compliant architecture looks like
The Act's requirements point toward a specific set of architectural capabilities. Organisations that build these in from the ground up will find compliance far less expensive than those retrofitting after the fact.
Article 12 requires automatic logging over the system's lifetime. Tamper-evident records, where each event is cryptographically linked to its predecessor so that retroactive modification is detectable, are a strong way to show those logs can be trusted. The VOLT protocol specifies this approach: every event recorded with SHA-256 hashing, linked via a prev_hash chain, and packaged into portable Evidence Bundles.
Human oversight must be a structural property of the orchestration layer. The AOCL protocol defines an 11-layer control pipeline where every policy decision (allow, deny, escalate to human) is auditable.
GDPR Article 22 and the EU AI Act are separate regulations enforced by different authorities, but they create complementary obligations. When a customer asks why an AI system made a particular decision, you need a complete, verifiable record of the inputs, processing steps, policy constraints, and output.
Static risk assessments fail at agent scale. An orchestration layer with full observability across every processing stage – from ingress through execution and response assembly – provides the continuous monitoring pipeline that Article 9 envisions, feeding anomaly detection back into the risk model automatically.
The cost of inaction
The penalty structure is designed to command attention. But fines are only part of the equation – the Act empowers authorities to order the withdrawal of non-compliant AI systems from the EU market entirely. For enterprise vendors, losing access to 450 million consumers is the existential risk.
Your compliance checklist before December 2027
The Annex III high-risk obligations apply from 2 December 2027, and Annex I products from 2 August 2028. Article 50 transparency applies already. Here is a prioritised action plan.
The regulatory direction is clear
The EU AI Act is first, but not last. NIST AI RMF, Brazil's AI Bill, China's algorithm regulations: the global direction is toward mandatory AI accountability.
Organisations that build compliance-ready infrastructure now are not just preparing for December 2027. They are building the foundation every major market will eventually require. The question is no longer whether to invest in verifiable, auditable, human-overseen AI systems. It is whether you can afford to reach the high-risk deadline without them.