What readiness actually is
EU AI Act readiness is the state of knowing two things about the AI features you ship: (1) what risk tier they fall into, and (2) the concrete gaps between your system and the obligations the Act attaches to that tier. For a product or legal lead launching into the EU, readiness is a score plus a remediation report — not a badge.
ClauseGuard describes a system and returns a risk-tier classification and a gap report mapped to EU AI Act obligations. The output is decision-support that helps you see where you stand; it is not a conformity sign-off.
Why "ready" is a spectrum, not a switch
The Act does not flip a system from "non-compliant" to "compliant" at a single point. It layers obligations by tier: prohibited practices (Art. 5), high-risk duties (Art. 9–17), and transparency duties (Art. 50). Readiness means knowing which layers apply and closing the gaps in each. Most teams discover they are partially ready — some obligations met, others unowned.
The three questions readiness answers
- What tier? — Annex III listing, prohibited practice, or transparency duty determines the obligation set.
- What gaps? — which articles (Art. 9 risk management, 14 oversight, 15 robustness…) you cannot yet evidence.
- Who owns it? — for high-risk uses, the deployer carries most duties (Art. 26), not the model provider.
What readiness tooling cannot do
A readiness score reduces obvious blind spots and makes obligations visible. It is not a guarantee that the system is compliant, and it is not a legal opinion or a certificate. Conformity is the deploying organization's responsibility across the full system.
Authoritative references
- EU AI Act (Reg. 2024/1689), Art. 5 / 6 / 9 / 14 / 15 / 26: https://eur-lex.europa.eu/eli/reg/2024/1689/oj
- AI Act explorer: https://artificialintelligenceact.eu/
- European Commission AI policy: https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai