🇪🇺 Compliance Guide

EU AI Act
Compliance Overview

How AILS maps to EU AI Act requirements for AI systems operating in regulated laboratory environments — Article 9 through Article 17, clause by clause.

EU AI Act AI Governance Risk Management Human Oversight EU AI Act

Risk Classification

How the EU AI Act classifies AI use

The EU AI Act classifies AI systems by the risk they pose. Before reviewing the article-by-article controls, it helps to know that classification depends on how each organization uses AI — and why that matters for labs operating in or selling to the EU.

⚠️
Your risk classification depends on how you use AI
Under the EU AI Act, risk classification depends on the intended purpose and context of each AI use, so it is for each customer to determine for its own use of AI. AILS does not classify itself, or its customers, as high-risk or not. It provides the governance tooling that the Article 9–17 obligations call for: an AI agent register, human oversight, logging and a fundamental rights impact assessment (FRIA) workflow, so a customer can document its own classification and controls.
Art. 9 Risk Management System
Requires a continuous, documented risk management process covering identification, analysis, and mitigation of known and foreseeable risks throughout the AI system's lifecycle.
AILS The Risk Assessment module maintains a live risk register with assigned mitigations and status tracking. The AI Risk Scorer on batch release decisions logs every scoring event with the data inputs, model used, and human override record. Risk register exports are available for regulatory submission.
Art. 10 Data & Data Governance
Training, validation, and testing data must meet quality criteria. Data governance practices must be documented, and data provenance must be traceable.
AILS All AI agents in AILS operate on your live tenant data — no external training corpus. Data inputs to every AI decision are logged with source record IDs, enabling full provenance tracing from AI output back to the originating lab record. Per-tenant database isolation means no cross-contamination of training context.
Art. 11 Technical Documentation
Detailed technical documentation must be maintained before market placement and kept current throughout the lifecycle — covering system design, capabilities, limitations, and performance metrics.
AILS The AILS Architecture documentation, Vendor Validation Package (IQ/OQ/PQ), and System Test Agent reports collectively satisfy the Article 11 technical documentation requirement. All are generated from live system state and downloadable from your Compliance module.
Art. 12 Record Keeping & Logging
High-risk AI systems must automatically log events throughout operation to enable post-incident traceability. Logs must be retained for a period appropriate to the system's intended use.
AILS Every AI agent invocation is logged with: user ID, timestamp, model version, prompt context, and structured output. Logs are immutable, append-only, and retained for 5 years by default. The audit trail is exportable as PDF for regulatory submissions and is searchable by event type, user, or record.
Art. 13 Transparency & Provision of Information
Deployers must be provided with clear, adequate information to understand the system's capabilities and limitations and to use it as intended.
AILS Each AI agent in AILS has a defined scope statement visible to users, a confidence indicator where applicable, and an explicit disclaimer where AI outputs require human review before acting. The onboarding flow documents intended use, out-of-scope uses, and model limitations for each agent.
Art. 14 Human Oversight
High-risk AI systems must be designed to allow natural persons to effectively oversee functioning, intervene, and override outputs. AI decisions must not be automatically implemented without a human in the loop for consequential actions.
AILS No AI agent in AILS takes a consequential action autonomously. COA issuance, batch release, CAPA closure, and SOP approval all require an authenticated human signature. AI outputs are recommendations — QA controls the final action. Re-authentication is required before every critical signing event, not just session login.
Art. 15 Accuracy, Robustness & Cybersecurity
High-risk AI systems must achieve appropriate levels of accuracy and must be resilient against errors, faults, and adversarial interference throughout their lifecycle.
AILS The System Test Agent runs 1232 automated tests — including negative-path security checks, injection resistance tests, and boundary condition tests — and publishes a timestamped health report. Current score: 100/100. AES-256 encryption, account lockout, token rotation, and tamper-evident hashing are enforced at the infrastructure layer.
Art. 17 Quality Management System
Providers of high-risk AI systems must put in place a quality management system covering design, development, testing, deployment, and post-market monitoring.
AILS AILS ships with a 10-module QMS: CAPA, Deviations, SOPs, Management Reviews, Proficiency Testing, Training Records, Risk Assessments, Audit Logs, Equipment, and Disclaimers. The platform's own operations run on this QMS — making it a live demonstration of the Article 17 requirement, not a policy on paper.

Platform Evidence

Built for EU AI Act from the architecture up

Compliance isn't bolted on. Every Article 9–17 control maps to a running system — with logs, evidence, and exports ready for your EU market supervisory authority.

112AI Agents
1232Automated Tests
100/100Health Score
5yrAudit Retention
🧾

EU Data Residency

EU data residency (Frankfurt) is available on enterprise deployment. On standard deployments, data is hosted in North America.

👁️

Human-in-the-Loop by Design

No AI agent in AILS issues, approves, or closes a record autonomously. Every consequential action requires a signed human decision — enforced at the API, not by policy.

📜

AI Decision Audit Trail

Every AI agent invocation is logged with model version, inputs, outputs, and the human action that followed. Full traceability from AI recommendation to final record.

🔍

Explainable AI Outputs

Each AI agent result includes the data inputs that drove it. No black-box decisions. QA managers can review the evidence behind every AI recommendation before acting.

⚖️

Risk Register & Mitigations

The live risk register with assigned mitigations, status tracking, and export satisfies the Article 9 continuous risk management obligation directly.

🛡️

Post-Market Monitoring

The System Test Agent's monthly automated test runs are your post-market monitoring evidence — timestamped, scored, and archived automatically.


Selling into the EU? Let's talk compliance.

Book a 30-minute demo and we'll walk through the EU AI Act controls as they appear in a live AILS tenant — evidence exports included.

Also see: Security Architecture · Computer System Validation · ISO 17025 Readiness Checklist · Pricing