Regulation (EU) 2024/1689 · Artificial Intelligence Act ● Annex III: — days

AI Act Grandfathering: Which Existing Systems Are Exempt Until When (Article 111)

We deployed it before the Act" is half true. Transitional law is per-obligation, not per-system: three dates carve the legacy estate into slices, and two of the duties on your running systems already apply today.

Renomira Team · 9 min read

The most common transitional-law error on the AI Act is treating grandfathering as a switch. It is not. Article 111 and the application schedule carve the estate into obligation-by-obligation slices: the same system can be legacy for documentation, fully in force for transparency, and already exposed on prohibitions — simultaneously.

A historic tower clock — transitional deadlines for legacy systems
Photo: BORGATO Pierandrea / CC BY-SA 4.0 via Wikimedia Commons

The other error is assuming “bought it in 2024” settles anything. What matters is what the system does, when it was placed or put into service, and which duty you are asking about. This guide maps the slices, with the dates that actually apply.

The dates that carve the legacy estate

Slice Date What it governs
2 Feb 2025 Already passed Prohibited practices (Art. 5) and AI literacy (Art. 4) — no grandfathering anywhere
2 Aug 2026 Already passed General applicability: GPAI duties, penalties (Art. 99), transparency (Art. 50)
2 Dec 2026 Next End of the Article 50 legacy line for systems placed or put into service before 2 Aug 2026 — disclosure and marking duties bite here
2 Dec 2027 Next Annex III high-risk deployer/provider duties (Art. 26, Art. 27 FRIA, registration, Art. 72 monitoring) — moved from 2 Aug 2027 by the Digital Omnibus
2 Aug 2028 Upcoming Art. 6(1) systems — AI as safety component of Annex I products

Two rules cut through every row. Prohibitions never grandfathered — a system doing a banned thing in 2024 was doing a banned thing from 2 February 2025. And the register starts now: classification reasoning for existing systems is due before the high-risk dates, because everything at 2 Dec 2027 keys off knowing which systems are in scope.

What is genuinely deferred

For systems placed on the market or put into service before the relevant application date, the heavy regime waits for its slice:

  • Annex III high-risk obligations — documentation-driven deployer duties, FRIA, registration, post-market monitoring — start 2 December 2027 for legacy systems. This is the real runway extension: fourteen additional months versus new deployments.
  • Article 50 transparency for legacy systems — systems already in service before 2 August 2026 get until 2 December 2026 to bring disclosure, synthetic-content marking and provenance practices in line. That is weeks away, not a future project — it is the nearest deadline in the transitional calendar.

“Placed on the market or put into service” is the operative phrase. A system you merely configured differently, extended to new purposes, or substantially modified may not qualify as the same legacy system at all: material modification re-enters the new-deployment track. The question is not “when did we buy it” but “when did this configuration enter service, and has its purpose moved since?”

What was never deferred

Three obligations on a running estate are live right now, regardless of legacy status:

  1. Article 5 screen — prohibited practices since 2 Feb 2025. A legacy emotion-inference feature is still a prohibited feature.
  2. Article 4 literacy — since 2 Feb 2025. Staff operating legacy systems need a sufficient level of it, documented.
  3. Article 50 transparency — in force since 2 Aug 2026 for new systems; legacy systems must be aligned by 2 Dec 2026. Customer-facing chatbots must disclose; synthetic media must be marked.

Plus the commercial layer that transitional law does not touch at all: enterprise questionnaires have asked for register and classification evidence since day one of procurement, and a legacy answer does not complete their form.

Working the estate: a four-pass sweep

  1. Inventory by obligation, not by age. One row per system: what it does, when placed/put into service, materially modified since?
  2. Screen the reds first. Article 5 pass over everything — deferred or not, a hit is a removal ticket.
  3. Close the 2 Dec 2026 gap. Every customer-facing interaction-disclosure and synthetic-marking change that is pending belongs to the nearest deadline. Audit the surfaces this week: chat, generated content, any voice or image synthesis facing users.
  4. Build the 2 Dec 2027 lane. For Annex III systems: classification records now, vendor documentation chased early (vendor response is the longest lead item), worker consultation booked ahead of go-live duties, monitoring plans drafted. The date is deferred; the dependencies are not.

The trap in the middle

Teams read “grandfathered until 2027” as “revisit in 2027.” But the classification that determines the 2027 lane must exist before 2027 — and a system reclassified upward in, say, March 2028 discovers its obligations applied from the date its facts triggered them, not from the date the discovery happened. Legacy status defers duties for systems correctly assessed; it never defers the assessment.

How to check your own position in four minutes

The free exposure scan asks twelve questions about your AI usage and governance and returns an exposure score, your ranked exposures with the exact article that fired, and your first three moves — mapped to the dates that apply. Confirm your email and the full report unlocks.

Frequently asked questions

Does the EU AI Act apply to AI systems we already had before it came into force?

Partially, and per obligation. Transitional provisions (Article 111) defer the Annex III high-risk regime for existing systems to 2 December 2027 and give legacy systems until 2 December 2026 to align with Article 50 transparency duties. Prohibited practices (Article 5) and AI literacy (Article 4) have applied since 2 February 2025 with no grandfathering — and classification work for the deferred duties is needed before their dates arrive.

What is the difference between “placed on the market” and “put into service”?

Placed on the market means the system is first made available in the EU — a purchased vendor product. Put into service means it is first used under your own control — an internally built system going live. Transitional dates key off whichever happened for your system; substantial modification or a changed intended purpose can move a system out of legacy treatment into the current regime.

Do legacy chatbots have to disclose they are AI?

Yes. Article 50 interaction-disclosure duties have applied since 2 August 2026, with systems already in service before that date required to align by 2 December 2026. If your chatbot tells users it is automated and escalates to a human when asked, you are done; if it plays human, the December line is the deadline that matters.

Is our old AI system exempt from registration and FRIA until 2027?

The Annex III deployer duties — including registration where applicable, Article 27 FRIA for the entities Article 26(7)… the triggers, and post-market monitoring — start for legacy systems on 2 December 2027, so the execution waits. The classification that determines whether those duties apply at all does not wait: it is the prerequisite everything else queues behind, and buyers already ask for it.

What happens if we substantially modify a grandfathered system?

Material modification — new intended purpose, architecture change with behavioural effect, rebranding as your own — can end legacy treatment and pull the system into the current regime immediately. Keep modification records with dates and a classification note each time; the legacy claim is only as strong as the evidence that the system in production is the same system that entered service.

Next step

Put this guide to work on your own estate.

Run the free exposure scan to see which of these articles actually apply to your company — 12 questions, four minutes, no card. Confirm your email and the full report unlocks.

  • Free forever plan
  • No credit card
  • EU-hosted · GDPR-native
Run a free scan Sign up free

Build a live AI register in minutes — upgrade only when you need the audit pack.

AI Act grandfathering existing systemsAI Act legacy systems exemptionArticle 111 transitional provisions AI Actdoes AI Act apply to systems already in useAI Act existing software compliance dateAI Act legacy chatbot disclosureput into service before AI Act

Keep reading