IT/Technology

EU AI Act with aqua cloud
EU AI Act Compliance in 60 Days: QA-Led Roadmap

The EU AI Act compliance deadline for high-risk AI systems is 2 August 2026, with penalties reaching €35 million or 7% of global revenue. This roadmap covers system classification, evidence generation, and notified body handover in 60 calendar days. aqua cloud serves as the evidence platform, maintaining the artefact chain across Articles 9–15 and 17.

60 days

From classification to notified body handover

€35M

Maximum penalty exposure for prohibited practices violations

4 phases

Classify, build evidence infrastructure, generate evidence, audit

12+

Integrations with existing dev and QA toolchains

BEFORE

NO STRUCTURED EVIDENCE TRAIL

Without a centralised compliance platform, QA teams spend weeks gathering evidence that typically sits across Jira, Confluence, Excel, and shared drives. Each Article obligation then requires a separate effort to locate and verify before a notified body submission can begin.

By that point, organisations with a structured evidence chain in place are already months ahead.

Evidence scattered across disconnected tools with no consolidated compliance record
Requirement-to-execution traceability maintained in error-prone manual spreadsheets
Manual formatting required before every notified body submission, adding weeks of delay
No structured gap assessment means Article obligations go unowned until the final stretch

AFTER

AUDIT-READY IN 60 CALENDAR DAYS

This four-phase programme uses aqua cloud as the evidence platform throughout. QA teams avoid the consolidation effort that typically delays compliance work, because every Article 9–15 obligation is linked to a named, time-stamped artefact.

The full chain, from requirement to sign-off, is enforced by workflow and exportable in one click. Automated re-validation keeps that chain current as requirements change after the regulatory deadline.

The roadmap aligns aqua cloud onboarding with EU AI Act preparation from day one, with no sequential wait between tooling readiness and compliance work.

Single evidence chain from requirement to sign-off, enforced by aqua’s configured workflow
Annex IV Technical File exported in one click, with no manual assembly or formatting sprint required before submission
Change-driven re-validation keeps the evidence chain current through requirement updates after the regulatory deadline
Named human approvals captured with timestamp and role on every release; automated or blank approvals are blocked at workflow level

“Organisations that will have a complete evidence bundle by their first audit are those that started building their compliance programme months earlier. There's no room for delay. The platform you choose needs to make quality and compliance work traceable and auditable from day one, with re-validation built into the workflow.”

Stefan Gogoll,

Founder and CEO, aqua cloud

Stefan Gogoll,

Founder and CEO, aqua cloud

This Case Study Is Available by Email

Enter your email to access the complete success story from aqua. The download includes implementation details, measurable outcomes, regulatory insights, and more.