2026-05-23 EU AI ACT ~11 min

EU AI Act deadline: 2 August 2026. Seventy-one days.

The high-risk provisions of Regulation (EU) 2024/1689 enter application on 2 August 2026. That date is fixed and there is no transition period for placing high-risk systems on the EU market after it. This page is the deadline in concrete terms: three application dates, who is affected, what the penalty structure looks like, and a ten-week plan for the time still on the clock.

High-risk obligations apply
2 August 2026
71 days from today (2026-05-23)
Regulation (EU) 2024/1689 · Article 113

One regulation, three application dates

The AI Act is often discussed as a single 2026 deadline. It is not. Article 113 of the regulation phases obligations across three dates, each binding a different population of providers and deployers. Knowing which date binds you is the first step in deciding what to ship between now and then.

DateWho it bindsWhat enters application
2 Aug 2025All providers and deployers; general-purpose AI model providersProhibited practices (Article 5), AI literacy obligations (Article 4), governance bodies, the GPAI model obligations of Chapter V
2 Aug 2026High-risk providers and deployers under Annex III (Article 6(2))The core compliance regime: risk management (Art 9), data governance (Art 10), technical documentation (Art 11), automated logging (Art 12), transparency (Art 13), human oversight (Art 14), accuracy and robustness (Art 15), quality management system (Art 17), conformity assessment (Art 43)
2 Aug 2027High-risk systems classified by Article 6(1) — AI as safety component in products already covered by harmonised EU product law (Annex I)Same regime as 2026, applied via the conformity-assessment infrastructure of each underlying product directive

The bulk of enterprise AI sits in the middle row. Credit-scoring models, recruitment screening, exam scoring, biometric identification, critical infrastructure controllers, law-enforcement support tools, migration and asylum systems, justice-administration models — all of these are Annex III. All of them have 71 days as of the date of this article.

Are you affected? A short decision path

The Act binds two populations differently: providers (you place a system on the EU market or put it into service in the EU under your own name or trademark) and deployers (you use a system in a professional context). The obligations are not symmetric. A provider faces conformity assessment, technical documentation, and post-market monitoring. A deployer faces fundamental-rights impact assessments and Article 26 use obligations.

  1. Do you place an AI system on the EU market, in any form? If yes, you are a provider for that system. Distributors and importers who modify a system substantially can become providers under Article 25.
  2. Is the intended purpose listed in Annex III? Critical infrastructure, education and vocational training, employment and worker management, essential private and public services (including credit scoring), law enforcement, migration and asylum, administration of justice and democratic processes, biometric identification not prohibited under Article 5. If yes and the system is not excluded by Article 6(3), it is high-risk.
  3. Is the system a safety component of a product in Annex I? Medical devices, machinery, lifts, toys, in-vitro diagnostics, civil aviation, agricultural and forestry vehicles, marine equipment, railway. If yes, it is high-risk under Article 6(1) and the 2027 deadline applies, but the 2026 deadline still applies to GPAI obligations and to any Annex III intended purposes.
  4. Is it general-purpose AI? Trained on broad data, capable of performing a wide range of distinct tasks. Then Chapter V obligations applied on 2 August 2025; you are already inside the regime. If your model has systemic risk under Article 51, additional duties apply.

The honest answer for most enterprise AI vendors selling into Europe is: yes, somewhere in your portfolio there is at least one Annex III system, and the 2026 date binds you.

What the deadline actually triggers

"Enters application" is a Regulation-specific phrase. It means that on 2 August 2026, market surveillance authorities in every Member State can act. From that date:

The compliance posture changes overnight. Before 2 August 2026 the obligations exist on paper. From 2 August 2026 they exist in practice, with state machinery behind them.

Article 99: the penalty structure

Penalties are tiered. The headline number is €35 million or seven percent of global annual turnover, but that maximum applies only to a narrow set of infringements. The full structure:

TierTriggered byMaximum penalty
99(3)Non-compliance with the prohibition of practices in Article 5 (prohibited AI)€35 million or 7% of worldwide annual turnover, whichever is higher
99(4)Non-compliance with most provisions binding providers, importers, distributors, deployers, notified bodies, authorised representatives (including Articles 9, 12, 13, 14, 17, 26, 43, 47, 72, 73)€15 million or 3% of worldwide annual turnover, whichever is higher
99(5)Supply of incorrect, incomplete, or misleading information to notified bodies or national competent authorities€7.5 million or 1% of worldwide annual turnover, whichever is higher

The €15M / 3% tier is the one most relevant to a provider that intended to comply but did not finish the work. Article 12 logging gaps, Article 17 QMS gaps, Article 43 conformity-assessment irregularities, Article 72 post-market monitoring failures all fall here. SMEs and start-ups receive proportionate reductions under Article 99(6), but the proportionality is calibrated by the supervisory authority, not waived.

Note on enforcement timing. The Act does not say "no penalties until the supervisory infrastructure is mature." Market surveillance authorities are designated by the national-implementation deadline. The fact that an authority is new does not lift the obligation; it shifts the discovery path. Audits triggered by complaint, by serious-incident reports under Article 73, or by post-market monitoring under Article 72 are the most likely first surfaces.

A ten-week plan for the seventy-one days you have

The plan below assumes you are a high-risk provider, have already done an initial regulation read, and are now executing rather than scoping. If you have not yet done the read, the readiness assessment is the prior step.

Week 1Scope freeze. Inventory every AI system you place on the EU market. For each: is it Annex III, Annex I, GPAI, or excluded? The list is the work product; resist the urge to start fixing things before the list is closed.
Week 2Article 9 risk file. One risk register per high-risk system, signed and dated. Map known failure modes to mitigation measures and to test results. This document is the spine the next eight weeks attach to.
Week 3Article 12 logging. The automated logging requirement is the hardest to retrofit. Decide the log schema, retention path, integrity controls. Tamper-evident hashing is not strictly required but is the cheapest defensible posture. See our Article 12 crosswalk.
Week 4Article 13 instructions for use. Write the document a deployer will read. Intended purpose, accuracy and robustness levels, human-oversight provisions, foreseeable misuse. Short is fine; missing is not.
Week 5Article 14 human oversight. Procedure, training, override logs. The audit question is "can a competent person stop this system in production, and is that capability documented and tested." If yes for both, you pass.
Week 6Article 15 accuracy and robustness claims. The metric and threshold pair for each system, with the test set, the seed, the date, and the evidence trail. This is the area where pre-registration matters: claims made before evaluation are auditable, claims made after are post-hoc rationalisation. See how we structure this.
Week 7Article 17 QMS. The quality management system is not a new ISO certification; it is the documented coupling of Articles 9 through 16 to your engineering process. ISO 9001 or ISO/IEC 42001 alignment helps but is not required.
Week 8Article 43 conformity assessment. For Annex III systems the standard route is internal control under Annex VI. Biometric identification under Article 6(2) categories requires a notified body. Decide which route now, not in week ten.
Week 9Articles 47, 48, 71. Draft the EU declaration of conformity, prepare the CE marking, register the system in the EU database. These are paperwork tasks; do them only after the previous seven weeks have actually closed.
Week 10Article 72 post-market monitoring + Article 73 incident response. A monitoring plan, an incident response runbook, a reporting channel to the competent authority. Test the runbook with a tabletop exercise before the deadline lands.

What to do this week, before the ten-week plan starts

  1. Read Article 6 and Annex III, carefully. Most disputes about whether the Act binds a particular system resolve on the precise wording of Annex III. Twenty minutes here saves weeks of misaligned work.
  2. Identify your competent authority. Member-State designations under Article 70 are public. Knowing who you would report to under Article 73 changes how you write the incident-response runbook.
  3. Inventory current evidence. List every accuracy claim, threshold, and test result you have made publicly or to a customer in the past twelve months. Which of those can you reproduce from raw artefacts today? That number is your real baseline.
  4. Decide the conformity assessment route per system. Internal control under Annex VI is the default for Annex III. Anything involving biometric identification, the Article 6(2) sub-categories, or third-country notified-body recognition needs that decision now.
  5. Block ten weeks on the calendar. The plan above is doable in ten focused weeks. It is not doable in ten weeks done in parallel with three other initiatives.

Where this overlaps with PRML and falsify

PRML is the pre-registered ML manifest specification — an open spec for committing an evaluation claim (metric, comparator, threshold, dataset hash, seed) to a SHA-256 hash before the run. It is not a compliance product. It is a small piece of infrastructure that closes three specific gaps under the 2026 regime:

PRML does not close Article 9, 13, 14, 17, 26, 43, or 72. Those are organisational and procedural. PRML closes one specific kind of evidence problem and stays in its lane.

What to do next

FAQ

Is the 2 August 2026 deadline a hard date or is there a transition period?

It is the application date under Article 113. There is no general transition period for high-risk systems placed on the market after that date. Article 111 contains narrow grandfathering for high-risk systems already on the market before 2 August 2026, but it is conditional and time-limited.

If I am a non-EU provider, does the Act bind me?

Article 2 applies the regulation to providers placing systems on the EU market regardless of establishment. Non-EU providers must designate an authorised representative in the EU under Article 22 before placing a high-risk system on the market.

What counts as "placing on the market"?

Article 3(13) defines it as the first making available of an AI system on the EU market. Putting into service is a parallel concept for systems used in-house. A free or open-source release that is intentionally made available in the EU counts as placing on the market unless one of the Article 2(12) exceptions applies.

How do penalties scale for SMEs and start-ups?

Article 99(6) requires supervisory authorities to take the economic viability of SMEs into account and to consider proportionality. The maximum penalty caps apply, but actual penalties are calibrated. There is no automatic exemption.

Does GPAI compliance under the 2025 deadline cover me for 2026?

No. GPAI model obligations under Chapter V are a separate regime. If your portfolio contains both a GPAI model and an Annex III application, both regimes bind you on their respective dates.


About this page. Written by Cüneyt Öztürk, founder of Studio 11 Türkiye Ltd. Şti. and author of the PRML specification. Studio 11 runs the Falsify Sprint programme for ML evaluation evidence under the AI Act. This page is not legal advice. Article references are to Regulation (EU) 2024/1689 as published in the Official Journal of the European Union on 12 July 2024. Day count calculated from publication date of this article.