Who should care?
APAC teams whose AI systems, vendors, clients, users, or outputs touch the EU should check whether their workflows create EU AI Act obligations.
EU AI Act readiness
A practical readiness review for APAC teams with EU clients, users, operations, or AI outputs used in the EU.
APAC teams whose AI systems, vendors, clients, users, or outputs touch the EU should check whether their workflows create EU AI Act obligations.
Current AI tools, workflow purpose, data categories, users, model or vendor context, human review, output destination, and likely risk category.
Some obligations already apply, 2 August 2026 is the broad application date, and Commission updates now point to high-risk milestones on 2 December 2027 and 2 August 2028. The practical answer is an exposure register before deadline pressure arrives.
An AI usage register, exposure notes, ownership, review points, and a shortlist of workflows to approve, restrict, or escalate.
It can. The Act can apply to non-EU providers and deployers where AI outputs are used in the EU, so APAC teams with EU-facing workflows should classify exposure early.
No. Some obligations already applied in 2025, the broad application date is 2 August 2026, and official Commission timelines now describe high-risk milestones on 2 December 2027 and 2 August 2028. The safe first step is workflow inventory and exposure classification.
Private AI review
Full Cal.com scheduler