Feature · Dates · Written by Yobel Tzegai · Last checked 22 October 2026

Which EU AI Act dates apply to my AI systems, and which requirements are already overdue?

In Complipath (complipath.io), a timeline lists seven AI Act dates and which of your systems each touches. Every requirement carries its own date from where its provision sits: Applies from before it, Applies since after it and a red Overdue when the date has passed and the requirement is not complete. Your role as provider or deployer decides which high-risk requirements a system gets.

Check your AI systems, free

What it does today, and its limits

A timeline of seven AI Act dates, each resting on a sentence a test holds against the pinned law texts, the dates ahead first, with a line under each saying which of your active systems it touches by the level your register records, confirmed or not; the list is written into the app and is not a live register of the law.

Illustration · not your dataSystem A hiring tool, made up · high-risk, and you are the providerRegistration (EU database) · Article 49 Applies since 2 August 2026 · OverdueRisk management system · Article 9 Applies from 2 December 2027

The key dates timeline

Seven dates on one timeline: 2 February 2025, 2 August 2025, 2 August 2026, 2 December 2026, 2 December 2027, 2 August 2028 and 2 August 2030. Dates still ahead come first, then the ones that have passed.
Under each date a line for you, worked out from the level your register records for each active system, confirmed or not. It names the systems the date touches, three and then a count, says all of them, or says that none does.
Each date rests on a sentence of the law, and a test in the app holds that sentence against the pinned Official Journal texts.
The timeline is written into the app, not read from a live register of the law. A date the law adds reaches it when the app is changed.

The dates up to 2 August 2026

2 February 2025: Chapters I and II, which include Article 4 and the Article 5 bans, with the exception of Article 5(1), first subparagraph, points (ba) and (bb), and Article 5(1a) and (1b), which apply from 2 December 2026 (Article 113, third paragraph, point (a)).
2 August 2025: Chapter V on general-purpose AI models, Chapter III Section 4, Chapter VII, Chapter XII and Article 78, with the exception of Article 101 (Article 113, third paragraph, point (b)).
2 August 2026: the general date, “It shall apply from 2 August 2026” (Article 113, second paragraph), which includes Article 50. Providers of content generators placed on the market before it have until 2 December 2026 for Article 50(2) (Article 111(4)).

The dates from 2 December 2026

2 December 2026: Article 5(1), first subparagraph, points (ba) and (bb), and Article 5(1a) and (1b) (Article 113, third paragraph, point (a), as amended), as well as the end of the Article 111(4) period.
2 December 2027: Chapter III, Sections 1, 2 and 3, with the exception of Article 6(5), for systems classified as high-risk under Article 6(2) and Annex III (Article 113, third paragraph, point (c)(i), as amended).
2 August 2028: the same Sections for systems classified as high-risk under Article 6(1) and Annex I (point (c)(ii), as amended by Regulation (EU) 2026/1744 (the Digital Omnibus on AI)).
2 August 2030: in any case, providers and deployers of high-risk AI systems intended to be used by public authorities shall take the necessary steps to comply with the requirements and obligations of the Regulation by then (Article 111(2), as replaced).

Applies from, Applies since and Overdue

Every requirement carries one date, derived from where its provision sits in the Regulation and never typed onto the row. A date still ahead reads Applies from; a date that has passed reads Applies since.
Overdue shows in red when that date has passed and the requirement is not marked complete. It joins a date to a status you set; it is not a finding that you have breached the Regulation.
It shows on the requirement's own page, in the system's to-do list, which also counts how many of its items already apply, and in the PDF of one system.
On a system whose recorded Annex I answers put it on the Article 6(1) route, the Chapter III rows carry 2 August 2028 instead of 2 December 2027.
The fold called Why this applies lists each date with the provision behind it. For a high-risk system it adds the Article 111(2) rule for systems already on the market, and where Article 50(2) applies, Article 111(4).

Which requirements, by role

The role comes from how a system is recorded: built in house gives provider, a fine-tuned third-party model gives provider and deployer, bought software or an API gives deployer. A role a person confirms replaces it. With neither, no high-risk requirements are created.
A provider's set: Articles 9 to 15, 17 and 49, plus Articles 16, 18, 19, 20, 43, 47, 48, 72 and 73.
A deployer's set: Article 26, and Article 27 only where Article 27(1) reaches the deployer, which the app asks once for the workspace where a system's citations do not decide it.
Article 50 rows come from the transparency duties found in the assessment, not from the role.
The list is arranged in three steps (build and document; before you place it on the market or start using it; after launch), five rows each before Show more, with an index by date that counts how many rows are done.

What it does not do

Overdue ignores the transitions. Article 111(4) gives providers of content generators already on the market until 2 December 2026 for Article 50(2), yet that row reads Applies since 2 August 2026, and Overdue if it is not complete.
It shows the Article 111(2) test on significant changes in that fold but applies it to nothing: no requirement is removed by it.
It follows Article 113 as written: Chapter III, Section 5 (Articles 40 to 49, including registration) keeps 2 August 2026 while Sections 1 to 3 move. The amending Regulation does not say how Section 5 works meanwhile, and the app does not either.
The timeline lists seven dates. The date for providers of general-purpose AI models placed on the market before 2 August 2025, 2 August 2027 (Article 111(3)), is not one of them.

Which plan

Every plan. The date and Overdue never depend on the plan; the plan decides only the step-by-step guidance on a requirement's page. The Annex I check, which can change a system's route, is on Starter and up.

Starter

€499 a month

Prices exclude VAT.

Up to 20 AI systems
Evidence and the audit log
Your first system is free, with no end date

Check your AI systems, free

All plans

Questions

What does Overdue mean in Complipath?

The requirement's application date has passed and the requirement is not marked complete. It joins a date to a status you set. It does not say you have breached the Regulation, and it does not apply transitions such as Article 111(4) for content generators already on the market, which runs to 2 December 2026.

Why do two requirements on one system show different dates?

Article 113 gives Chapter III, Sections 1, 2 and 3 their own dates, 2 December 2027 for Annex III systems, and leaves Section 5, which holds conformity assessment and registration in Articles 43 and 49, on 2 August 2026. The app derives each row's date from where its provision sits.

Does my role change which requirements I get?

Yes. A provider of a high-risk system gets Articles 9 to 15, 17 and 49 plus 16, 18, 19, 20, 43, 47, 48, 72 and 73. A deployer gets Article 26, and Article 27 where Article 27(1) reaches it. The dates come from where each provision sits, not from the role.

Which plan includes it?

Every plan, the free one included: the app lists it for every plan. Free holds one AI system, with no end date. Starter is €499 a month for up to 20 AI systems. Prices exclude VAT. Growth and Scale are not available yet, and nothing here waits for them.