Define the system
Start by naming the AI feature, users, decision impact, data categories, vendors, and the team member responsible for maintaining the review record.
Planning guide
EU AI Act Timeline for 2026
The EU AI Act is not a distant policy topic anymore. Small AI teams need to classify use cases, document systems, and prepare transparency controls before customers or investors ask for proof.
Note: This page is educational and should not be treated as legal advice.
Key timeline
| Date | What it means for AI builders |
|---|---|
| 2024-08-01 | The EU AI Act entered into force. |
| 2025-02-02 | Prohibited AI practices became an immediate screening priority for teams planning EU use cases. |
| 2025-08-02 | General-purpose AI, governance, and related preparation milestones became more relevant for model providers and downstream AI product teams. |
| 2026-08-02 | Most AI Act rules are expected to apply, with phased exceptions and later dates for some high-risk/product-integrated obligations. |
| 2027-2028 | Some high-risk and product-integrated AI obligations may follow later phase-in dates. Check the official Commission timeline for the exact category. |
Practical preparation checklist
- Write the intended purpose of every AI feature.
- Identify whether the system affects access, rights, safety, or eligibility.
- Check whether the system falls into a high-risk sector.
- Add a transparency notice for chatbots and generative AI interfaces.
- Keep records of model providers, data sources, safeguards, and human oversight.
Official source
Last reviewed: 2026-07-03.
European Commission: AI Act regulatory framework
EU AI Act Article 5 prohibited practices
practical AI compliance self-assessment
Practical notes for EU AI Act Timeline for 2026
EU AI Act Timeline 2026 | Practical Planning Guide is maintained for founders, product managers, compliance owners, agencies, and small teams building AI workflows who need AI governance workflow. The goal is to help visitors complete a real task and leave with an AI inventory, risk note, disclosure draft, vendor question set, policy outline, or review workflow report, not only read a generic summary.
Separate triage from advice
Use the generated output as first-pass operational triage. Legal, medical, hiring, credit, education, biometric, and public-sector uses still need specialist review.
Keep evidence
Save the output, assumptions, date, source links, and reviewer notes so the team can explain why a risk level, disclosure, or vendor question set was chosen.
Before relying on this page
- Review high-impact use cases manually.
- Keep policies and disclosures aligned with the real product behavior.
- Re-run the workflow when vendors, data, or user impact changes.
Review record
How to use EU AI Act Timeline for 2026 in an AI compliance file
A compliance tool is useful when it leaves a traceable record. The output should name the AI system, explain the assumptions, and show what the team still needs to verify with product, legal, security, or vendor owners.
Describe the real system
Record the feature name, user group, decision impact, data sources, vendor dependencies, and the human owner. A generic "chatbot" label is rarely enough. A hiring assistant, support summarizer, medical triage bot, and product recommender can have very different risk profiles even if they all use language models.
Separate signal from conclusion
Treat this page as first-pass triage. It can flag high-risk areas, transparency duties, missing evidence, and questions to ask a vendor. It should not be treated as legal approval, clinical advice, hiring approval, credit approval, or permission to launch without human review.
Save evidence and changes
Save the generated result with the date, reviewer, source links, and unresolved questions. Update the record when the model, data, users, product flow, vendor, or region changes. This keeps the site useful for actual operators rather than only being a static explanation page.
Evidence checklist
- Document what the AI system does and what it does not do.
- Record whether the system influences employment, education, credit, public benefits, healthcare, biometric identification, safety, or other high-impact outcomes.
- Keep vendor documentation, model notes, data descriptions, user notices, human oversight notes, and monitoring plans together.
- Re-run the review when the product behavior changes, not only when the law changes.
- Use specialist review for high-impact or regulated workflows before relying on any generated text.