Use the timeline as a dated legal-status register for the AI Act's staged compliance deadlines.
For each milestone, record whether it comes from enacted law, a later political agreement, draft guidance, a consultation, or a voluntary code before assigning implementation work.
The EU AI Act applies in stages. Prohibited practices and AI literacy already apply, general-purpose AI model obligations entered into application in 2025, and 2 August 2026 remains the general for provisions not assigned another date. Article 50 transparency duties also begin then, subject to the limited marking grace period for systems already on the market. Regulation (EU) 2026/1744, the Digital Omnibus on AI or , was published on 24 July 2026 and entered into force on 27 July 2026, including later high-risk and sandbox dates. This roadmap keeps each legal stage and source status visible before work is rescheduled.
1
Section 1
Label legal status before using a date
A date is useful only when the team knows what created it. Regulation (EU) 2024/1689 and its amending Regulation (EU) 2026/1744 are binding law. An amendment changes that baseline only after the legislative act is completed, published, and in force. A political agreement records negotiated text but is not the final legal stage. Commission guidelines explain the Commission's interpretation but are not legislation. Consultations and drafts may change. Codes of practice are voluntary tools even when the underlying AI Act duty is binding.
The Act was adopted on 13 June 2024, published in the Official Journal on 12 July 2024, and entered into force on 1 August 2024, the twentieth day after publication. Most operator duties remained subject to the staged application dates in .
Keep both the adopted-law baseline and any later development in the register. Do not silently replace one with the other, and do not present a draft, consultation closing date, standards target, or political agreement as if it were an enacted operator deadline.
13 June 2024: the European Parliament and Council adopted Regulation (EU) 2024/1689.
12 July 2024: the Regulation was published in the Official Journal of the European Union.
1 August 2024: the Regulation entered into force; then stages when its provisions apply.
Binding adopted law: record the article, , affected actor, and any transition rule.
Later legislation: record adoption, Official Journal publication, entry into force, and exactly which provision changes.
Political agreement: record the announced date and the need to verify the final adopted text.
Guideline or code: record whether it is draft or final, binding or voluntary, and which legal duty it interprets or supports.
Month-only publication: preserve month-level precision instead of implying a verified day.
Already applicable: prohibited practices, AI literacy, and GPAI provider duties
Since 2 February 2025, Chapters I and II apply. Providers and deployers should therefore have an AI-literacy approach suited to the people operating or using their AI systems, and product or deployment review should stop or redesign uses that fall within Article 5 prohibited practices.
Since 2 August 2025, obligations for providers of general-purpose AI models have applied. A provider placing a model on the market after that date should already have the Article 53 documentation, downstream information, copyright policy, and public training-content summary workstream. Providers of models with systemic risk also need the Article 55 safety, evaluation, incident, and cybersecurity workstream.
Product and legal: maintain an Article 5 screen for releases, procurement, and changed uses.
People and system owners: document who needs AI literacy, what they need to understand, and why the training fits the system and affected persons.
model provider: maintain model scope, version, market-placement date, Article 53 evidence, systemic-risk assessment, and AI Office engagement.
Downstream provider: retain the model version and supplier information needed to understand capabilities, limits, and integration obligations.
Evidence: dated classification, owners, source, training record, provider documentation, copyright policy, public summary, and change trigger.
2026 readiness: general application, Article 50, GPAI enforcement, and sandboxes
sets 2 August 2026 as the Regulation's general for provisions not assigned another date. Article 50 transparency obligations also apply from that date. They can require an AI-interaction notice, machine-readable marking of synthetic output, notices for emotion recognition or biometric categorisation, and disclosures for deepfakes or certain public-interest text, depending on the actor and use. A limited transition applies to Article 50(2): providers of systems placed on the market before 2 August 2026 have until 2 December 2026 to implement marking and detection. The Commission published final Article 50 guidelines on 20 July 2026, after the final voluntary transparency code was published on 10 June 2026.
The Commission's enforcement powers for provider obligations also enter into application on 2 August 2026. Regulation (EU) 2026/1744 amended Article 57 to require Member States to make at least one AI regulatory sandbox operational, individually or jointly, by 2 August 2027. A sandbox supports supervised development and testing; it does not waive prohibited-practice rules or automatically prove conformity.
Every system owner: confirm scope, role, risk route, applicable date, and evidence location.
Providers and deployers: identify each Article 50 trigger and approve the notice, marking, disclosure, exception analysis, timing, language, and accessibility treatment.
providers: prepare for Commission information requests, evaluation, monitoring, and enforcement from 2 August 2026.
Sandbox candidates: document the testing purpose, authority route, participant responsibilities, safeguards, exit criteria, and what remains necessary before market placement or use.
2027 and 2028: transitions and amended high-risk dates
Article 111 gives providers of models placed on the market before 2 August 2025 until 2 August 2027 to comply.
Regulation (EU) 2026/1744 amended so Chapter III, Sections 1, 2, and 3 apply from 2 December 2027 for Annex III high-risk systems and 2 August 2028 for Article 6(1) and Annex I high-risk systems, except that Article 6(5) is not covered by those deferred dates. The amending Regulation was published on 24 July 2026 and entered into force on 27 July 2026.
Existing provider: identify every model placed on the market before 2 August 2025 and close Article 53 and, where relevant, Article 55 evidence before 2 August 2027.
Annex III owner: classify the intended purpose and exact Annex III area, then plan against the 2 December 2027 date in amended .
Product-regulatory owner: map Annex I product legislation, third-party assessment routes, and the 2 August 2028 date in amended .
Legal monitoring: retain Regulation (EU) 2026/1744, its Official Journal publication and entry-into-force dates, and the decision that reconciles old and new dates.
Do not postpone Article 5, AI literacy, , or Article 50 work because the high-risk dates were amended.
One row should let a reviewer understand the date without opening every linked document. Store the legal status and affected actor beside the action and evidence, then give one person responsibility for monitoring changes.
Review the row whenever a system changes intended purpose, model, market, operator role, affected group, integration, or risk classification, and whenever the controlling legal or guidance source changes status.
Keep chronology and applicability separate. A milestone can occur on a known date without creating an operator deadline, while one legal can create different work for providers, deployers, importers, distributors, product manufacturers, model providers, public authorities, and Member States.
Should a political agreement replace the adopted AI Act date in our compliance calendar?
Not by itself. Keep the adopted-law date and add the political-agreement date as a separate status-labelled development. Replace the legal baseline only after verifying the formally adopted text, its Official Journal publication, entry into force, and the provision it amends.
Does following a voluntary code of practice change the date of the underlying AI Act obligation?
No. A code may provide a recognised way to demonstrate compliance, but the legal duty and its come from the AI Act or later binding legislation. Record code participation separately from legal applicability.
What should happen when an official source gives only a publication month?
Store the precision as month-only. If the visual timeline requires a day for positioning, explain that the first day is a display convention and do not describe it as the verified publication day.
Milestone name, date, date precision, jurisdiction, and status: enacted law, political agreement, draft, consultation, final guidance, or voluntary code.
Controlling article or official source, short explanation, affected actor, affected system or model, and transition population.
Required action, accountable owner, internal readiness date, dependency, and release or deployment gate.
Evidence link, reviewer, approval date, unresolved interpretation, and next source-monitoring date.
Reassessment triggers for product, model, supplier, role, purpose, geography, guidance, standards, and legal amendments.
Track legal status, owners, actions, and evidence together
Use the visual timeline for chronology, then maintain one roadmap row per milestone with its legal status, affected systems and actors, internal readiness date, evidence, and change-monitoring owner.
Article 4 requires providers and deployers to take measures, to their best extent, to ensure sufficient AI literacy for staff and other persons operating or using AI systems on their behalf.
Commission list of implementation guidelines planned across high-risk classification and duties, transparency, incidents, FRIA, value-chain responsibilities, post-market monitoring, and SME simplification.
The Commission page records the 10 June 2026 publication of the final voluntary transparency code and the binding Article 50 duties it is intended to support.
Official announcement confirming publication of the final transparency guidelines on 20 July 2026 and the 2 August 2026 application date for Article 50 duties.
This source reports the revised high-risk dates and states that the classification guidelines remain draft; the targeted consultation closed on 23 July 2026 and final Commission adoption remains pending.
"Following the political agreement on the AI Omnibus"
Official page for the final voluntary code supporting Article 50 marking and labelling duties, including its 10 June 2026 publication and sign-up context.
Articles 50 and 113 support the transparency application date and general application baseline; Regulation (EU) 2026/1744 amends the sandbox deadline and adds the Article 50(2) transition.
"Transparency obligations for providers and deployers of certain AI systems"
Article 113 is the adopted-law baseline for entry into force and staged application; Article 111 provides transition rules for systems and GPAI models already on the market or in use.
Primary legal text for the original application-date baseline, transitions, AI literacy, prohibited practices, transparency, high-risk systems, GPAI models, and operator duties, read with Regulation (EU) 2026/1744 for amended dates.