Alethexis
  • Pricing
  • Trust

Stay ahead of the AI Act

Regulatory analysis, AI news and product updates. No noise.

I agree to receive communications from Alethexis: content about AI and regulation, and product news. I can unsubscribe at any time.

Data protection — newsletter

Controller: ALETHEXIS, S.L. (NIF B88758057). Purpose: to send you the Alethexis newsletter (content about AI and regulation, and product news). Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time. Recipients and transfers: we use providers acting on behalf of Alethexis for hosting, security and email delivery. No disclosure of your data to third parties for their own purposes is planned, except where required by law. Some providers may process data outside the EEA with the safeguards set out in the additional information. Rights of access, rectification, erasure, objection, restriction and portability: privacidad@alethexis.com. You may lodge a complaint with the Spanish Data Protection Authority (AEPD, www.aepd.es) or with the supervisory authority of your Member State (Article 77 GDPR). More information in the privacy policy.

Alethexis
Take the AI Act assessment (3 minutes)14-day free trial

Product

  • M1 Visibility
  • M2 Governance
  • M3 High-Risk Ready
  • Agentic Add-on
  • How it works
  • All features
  • Pricing
  • AI governance software

Solutions

  • For DPOs and consultants
  • Shadow AI
  • If you develop AI

Sectors

  • Dental Clinics
  • B2B Distribution
  • Food Distribution
  • Recruitment and HR
  • Private Education
  • Private Healthcare
  • Financial Services
  • Logistics and Transport
  • Professional Services and Consulting
  • Other sectors
  • All sectors

Resources

  • The Route: AI governance in 30 days
  • AI Act assessment
  • Templates
  • EU AI Act guide
  • Glossary
  • AI Act timeline
  • Blog
  • Changelog

Trust

  • Overview
  • Trust Center
  • Security
  • Accessibility

Company

  • About us
  • Contact
  • hello@alethexis.com
  • Partners

Legal

  • Legal Notice
  • Privacy Policy
  • Terms of Service
  • DPA (Data Processing Agreement)
  • Cookie Policy
  • Subprocessors & Service Providers Register
© 2026 Alethexis, S.L. · NIF B88758057 · C/ Tirso de Molina 36, 08940 Cornellà de Llobregat (Barcelona) · The enterprise standard. Built for SMEs.

Alethexis structures the governance, risk, operation and evidence of AI use. Using the platform does not constitute legal advice, nor does it by itself establish regulatory compliance.

LinkedIn · Contact · Product data in the EU 🇪🇺 · See the subprocessors & service providers register
By Rafael Luque Ocaña·3 August 2026

The AI Act's grace period: the article stopped stating the date

Article 111(2) sets a grace period for high-risk systems placed on the market before a given date. The Digital Omnibus rewrote the paragraph and removed the date: it now refers to Article 113, which gives two different dates depending on the annex.

There's a question that comes up as soon as a company realises one of its systems might be high-risk: does this apply to the system I already have running, or only to what I buy from now on?

The answer sits in Article 111(2) of Regulation (EU) 2024/1689, and it's the reason a high-risk system that was already on the market can fall outside the bulk of the obligations. It's also one of the articles where it's easiest to quote something it no longer says.

What the grace period sets out

In the original wording, Article 111(2) said — without prejudice to the Article 5 prohibitions, and leaving aside the systems in paragraph 1 of the same Article — that the Regulation applies to operators of high-risk systems placed on the market or put into service before 2 August 2026 "only if, as from that date, those systems are subject to significant changes in their designs."

Put simply: if the system was placed on the market or put into service before that date, the Regulation applies to its operators only if, as from that date, the system is subject to significant changes in its design; the Article 5 prohibitions apply in any case. And the "in any case" that closes the paragraph isn't a general exception: it reaches only the high-risk systems intended to be used by public authorities that were already on the market or in service before that cut-off — in the current wording, the date of application of Chapter III: 2 December 2027 for Annex III systems and 2 August 2028 for Annex I systems —, whose providers and deployers must comply by 2 August 2030 at the latest.

What changed, and why it's hard to spot

Regulation (EU) 2026/1744 — the Digital Omnibus, published in the Official Journal on 24 July 2026 — replaced that paragraph in its entirety. The current wording says the cut-off is "before the date of application of Chapter III referred to in Article 113".

Read it twice, because that's the whole story: the article no longer contains any date at all. Where there used to be a specific day, there's now a cross-reference.

And that has a practical consequence you don't see until you follow the cross-reference. Article 113, also amended, doesn't give one date of application for Sections 1, 2 and 3 of Chapter III, with the exception of Article 6(5). It gives two:

  • 2 December 2027 for high-risk systems under Article 6(2) and Annex III.
  • 2 August 2028 for those under Article 6(1) and Annex I — high risk in products regulated under other legislation, where the AI system is a safety component of the product, or the product itself, and that product must undergo a third-party conformity assessment; for Annex I, Section B products, Article 2(2) applies only Article 6(1), Article 60a and Articles 102 to 112, and Articles 57, 58 and 59 only in so far as the high-risk requirements have been integrated in that legislation.

So the grace-period cut-off isn't the same for everyone. It depends on which of the two routes makes your system high-risk. A recruitment ATS, which falls under Annex III, has one cut-off; a medical device with embedded AI — where the AI is a safety component or the product itself and must undergo a third-party conformity assessment — falls under Annex I and has another, eight months later.

Why this is the hardest kind of error to catch

It's worth pausing on the mechanism, because it explains a problem that goes beyond this one article.

When a rule changes a date, the error can be caught: it says "2 August 2026" and the correct date is something else, so whoever checks it against the source sees it. That's what happens with the Annex III date, which moved to 2 December 2027 and still circulates in its old version.

Not here. Here the date disappeared from the article. Anyone who knows Article 111(2) from reading it in 2025 will remember "2 August 2026," and that recollection will go on looking reasonable indefinitely: it doesn't contradict any visible text, because the text no longer states anything about dates. It only refers elsewhere. And that cross-reference, on top of it, splits in two.

It's a statement that expires without the sentence changing. No re-read gives it away: you have to go to the article, check that it no longer says what you remember, follow the cross-reference, and discover it leads to two different places.

The type-and-model nuance

There's a second detail of the grace period that tends to get lost, and which the Digital Omnibus itself clarifies in its recital 39: the decisive factor is the date on which the first unit of that type and model was placed on the market or put into service on the Union market for the first time, not the date of each individual unit.

In other words: if at least one individual unit of a high-risk system's type and model was lawfully placed on the market or put into service before the applicable date, the other units of that same type and model remain covered by the grace period, even if they are placed on the market later, as long as the design remains unchanged. What breaks the coverage isn't the installation date of each unit: it's a significant change in the design. Worth not confusing this transitional arrangement with the one for synthetic content marking under Article 50(2), which has its own date, its own subject and a different scope.

For a company with several deployments of the same product, the difference between the two readings is substantial.

What to do with this

Three checks, in this order.

First: know which annex each system falls under, if it falls under one at all. It isn't a formality: it determines which of the two cut-offs applies to you — just as under Article 50 it determines the subject, where the interaction notice turns out to be the provider's obligation and not the deployer's. If a system isn't high-risk under either route, this question is answered once, with a no.

Second: record the date the first unit of the type and model was placed on the Union market, not just the installation date. It's the data point that sustains the coverage, and it's exactly the one nobody writes down when buying software. Recovering it three years later, when someone asks, means digging through contracts and emails.

Third: note what counts as a significant change in the design, and who decides that. That's where the coverage gets lost, and it gets lost silently: nobody issues a notice on the day an update crosses that line. Worth also not confusing this timeline with the Article 50 transparency obligations, which apply from 2 August 2026 — with the Article 111(4) transitional period for the marking in paragraph 2 — and follow their own timeline.

What this article teaches about the others

The Article 111(2) grace period is a good example of why a date jotted down on a slide ages badly. Not because anyone got it wrong, but because the rule stopped expressing it as a date.

Anyone keeping this information in slide decks, emails and spreadsheets will end up with as many versions as copies, with no way of telling which one was revised after July 2026. Anyone keeping it in one place, where each system has its annex, the placing-on-the-market date of its type and model, and who's accountable for it recorded, will only have to update one thing when the calendar moves again — and the Omnibus proves that it does.

The difference isn't knowing more law. It's having the answer to "does this apply to us?" live in a single place, with the date of its last review next to it.

Dates in accordance with Articles 111 and 113 of Regulation (EU) 2024/1689, as amended by Regulation (EU) 2026/1744 (Official Journal of the EU, 24 July 2026, in force since 27 July 2026).

This article is for informational purposes only and does not constitute legal advice.

Frequently asked questions

What is the Article 111(2) grace period?

A transitional rule: for operators of high-risk systems placed on the market or put into service before the date of application of Chapter III, the Regulation applies only if, as from that date, the system is subject to significant changes in its design. The Article 5 prohibitions apply in any case.

What is the cut-off date?

The date of application of Sections 1, 2 and 3 of Chapter III: 2 December 2027 for Annex III high-risk systems and 2 August 2028 for Annex I systems (Article 113, third paragraph, point (c), as amended by Regulation (EU) 2026/1744). Providers and deployers of systems intended to be used by public authorities must in any case comply by 2 August 2030.

Does the date of each unit count, or that of the type and model?

According to recital 39 of Regulation (EU) 2026/1744, what counts is the date on which the first unit of that type and model was placed on the market or put into service on the Union market for the first time, provided at least one unit was lawfully placed before the cut-off and the design remains unchanged.

Sources

  • Regulation (EU) 2024/1689, Article 111(2), original wording
  • Regulation (EU) 2024/1689, Article 111(2) and (4), as amended by Regulation (EU) 2026/1744
  • Regulation (EU) 2024/1689, Article 113, third paragraph, point (c), as amended by Regulation (EU) 2026/1744
  • Regulation (EU) 2026/1744, recital 39
  • Regulation (EU) 2024/1689, Article 6(1)
  • Regulation (EU) 2024/1689, Article 2(2), as amended by Regulation (EU) 2026/1744

Last substantive review: 12 September 2026

Scope: Operators of high-risk AI systems placed on the market or put into service before Chapter III applies. Explains the Article 111(2) grace period, its cross-reference to Article 113 and the type-and-model test; does not cover Article 111(1) or (3).

Reviewed by Rafael Luque

Want to start from the beginning? The Route: AI governance in seven steps →

Drafted with AI support and published after human review. Editorial responsibility: Alethexis SL.

Related

  • Annex III high-risk applies from 2 December 2027
  • Marking synthetic content: whose obligation it is, and how far the transitional period reaches
  • What the Digital Omnibus changes in the AI Act
  • The article that didn't move: why 2 August is still a real date

Where to go next

Next read

Annex III high-risk applies from 2 December 2027

Next step

Take the AI Act assessment (3 minutes)

Get analysis like this in your inbox

Alethexis regulatory and product news. No noise.

I agree to receive communications from Alethexis: content about AI and regulation, and product news. I can unsubscribe at any time.

Data protection — newsletter

Controller: ALETHEXIS, S.L. (NIF B88758057). Purpose: to send you the Alethexis newsletter (content about AI and regulation, and product news). Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time. Recipients and transfers: we use providers acting on behalf of Alethexis for hosting, security and email delivery. No disclosure of your data to third parties for their own purposes is planned, except where required by law. Some providers may process data outside the EEA with the safeguards set out in the additional information. Rights of access, rectification, erasure, objection, restriction and portability: privacidad@alethexis.com. You may lodge a complaint with the Spanish Data Protection Authority (AEPD, www.aepd.es) or with the supervisory authority of your Member State (Article 77 GDPR). More information in the privacy policy.