28 ngày cho đến khi Luật AI của EU có hiệu lực
Tìm hiểu thêm →

EU AI Act Article 17: Quality Management System (QMS)

Article 17 requires providers of high-risk AI systems to put a quality management system in place and to document it in written policies, procedures and instructions. It is the organisational backbone that ties together every other high-risk obligation. This page lists the QMS elements you must document and flags the harmonised standard still being drafted to support it.

Article 17 Deep Dive

EU AI Act Article 17: Quality Management System (QMS)

Article 17 requires providers of high-risk AI systems to put a quality management system in place and to document it in written policies, procedures and instructions. It is the organisational backbone that ties together every other high-risk obligation. This page lists the QMS elements you must document and flags the harmonised standard still being drafted to support it.

Đã cập nhật lần cuối: 4 tháng 7, 2026

What the QMS Requirement Is

Providers of high-risk AI systems must establish a quality management system that ensures compliance with the AI Act, documented in a systematic and orderly manner as written policies, procedures and instructions.

The QMS is proportionate to the size of the provider's organisation, and for providers that are already subject to sectoral quality-management obligations under other Union law, the AI Act requirements can be integrated into the existing system rather than duplicated. The point is not paperwork for its own sake: the QMS is how a provider demonstrates that compliance is a repeatable, governed process rather than a one-off effort.

Elements the QMS Must Document

Article 17(1) enumerates the aspects the quality management system must cover, at least:

  • Regulatory compliance strategy — including for conformity assessment and for managing modifications to the high-risk system
  • Design and development procedures — techniques, procedures and systematic actions for design, design control and design verification
  • Development and quality control — procedures for development, quality control and quality assurance of the system
  • Examination, test and validation — procedures to be carried out before, during and after development, and how frequently they are performed
  • Technical specifications and standards — the standards applied, and where harmonised standards are not applied in full, the means used to meet the requirements
  • Data management — systems and procedures for data acquisition, collection, analysis, labelling, storage, filtering, mining, aggregation and retention
  • Risk management — the Article 9 risk management system
  • Post-market monitoring — setting up, implementing and maintaining a post-market monitoring system under Article 72
  • Incident reporting — procedures for reporting serious incidents in line with Article 73
  • Communication and accountability — handling of communication with authorities and other parties, record-keeping, resource management, and an accountability framework defining management and staff responsibilities

The Harmonised Standard Is Still Emerging

To support Article 17, a dedicated harmonised standard on the AI quality management system is being developed under the Commission's standardisation request to CEN-CENELEC.

That work is progressing under the reference prEN 18286 (an AI quality management system standard). It is still a draft: the 'pr' prefix marks a work-in-progress European standard that has not yet been published or cited in the Official Journal, so it does not yet confer a presumption of conformity. Providers should design their QMS to the Article 17 text now and track the standard as it matures — building to the draft can reduce rework, but it is not a substitute for the legal requirement and should not be relied on as if already in force.

Standard references and publication status change over time; always verify the current status of prEN 18286 and any related harmonised standards against the Official Journal before relying on them.

How AIAgentree helps

A quality management system has to retain evidence that its procedures were actually followed. AIAgentree supplies the traceable decision-and-oversight record that the data-management, record-keeping and accountability elements of a QMS must retain:

  • Tamper-evident decision records give the record-keeping and accountability framework a defensible source of truth for how decisions were made and who was responsible
  • Human-oversight and approval workflows document the examination, review and sign-off steps your QMS procedures require, with who-approved-what captured automatically
  • Audit-fit retention, precedent search and exports over REST, MCP, A2A and OpenTelemetry (with Python and TypeScript SDKs and EU data residency in Germany) let the QMS produce records on demand — you can trial it on the 25-trace free tier

Frequently Asked Questions

Who has to maintain a quality management system under Article 17?

Providers of high-risk AI systems. The QMS is a provider obligation and must be in place to support conformity assessment and the ongoing compliance of the system throughout its lifecycle.

Does the QMS have to be a separate system?

No. Where a provider is already subject to quality-management obligations under other Union law (for example in regulated sectors), the Article 17 elements can be integrated into that existing quality management system rather than run in parallel.

Is prEN 18286 mandatory?

No. prEN 18286 is a draft European standard for AI quality management systems being developed to support Article 17. As a draft it is not yet published or cited in the Official Journal and does not confer a presumption of conformity. The binding requirement is the Article 17 text itself.

How is the QMS different from the technical documentation?

The Annex IV technical documentation describes a specific high-risk system and its conformity; the QMS is the organisation-wide set of policies and procedures that governs how the provider designs, tests, monitors and reports across its systems. The QMS produces and maintains the documentation.

Is the QMS scaled to company size?

Yes. Article 17 states the quality management system is to be proportionate to the size of the provider's organisation, so smaller providers can implement it in a way that fits their scale while still covering all the required elements.

Continue exploring the EU AI Act guide

EU AI Act Compliance Guide

The complete guide to EU AI Act compliance for AI agents — start here.

Article 12 — Record-Keeping & Logging

What every high-risk AI system must log, and how to capture it.

Article 14 — Human Oversight

Designing effective human-in-the-loop controls for AI decisions.

Annex III — High-Risk AI Systems

Which AI use cases the Act classifies as high-risk.

EU AI Act Compliance Checklist

A step-by-step checklist to reach and document compliance.

Compliance Cost Calculator

Estimate your EU AI Act compliance effort and cost.

Deadlines & Timeline

Key enforcement dates, including the August 2, 2026 deadline.

Fines & Penalties

Penalty tiers up to €35M or 7% of global annual turnover.

Transparency Obligations (Art. 13 & 50)

Disclosure duties for AI systems and their outputs.

Risk Management & Conformity Assessment

Build a risk management system and assess conformity.

GPAI Obligations

Rules for providers of general-purpose AI models.

EU AI Act for US Companies

Extraterritorial scope and what US providers must do.

Omnibus Update

The latest changes to the EU AI Act timeline and rules.

Penalty Calculator

Estimate your maximum fine under the Article 99 tiers.

Article 11 + Annex IV

What technical documentation the EU AI Act requires.

Article 26: Deployer Obligations

What deployers of high-risk AI must do, including log retention.

Article 10: Data Governance

Data quality, bias mitigation, and governance duties.

Article 4: AI Literacy

The staff AI-literacy duty in force since February 2025.

Deployer vs Provider

Who bears which obligation — and when a deployer becomes a provider.

FRIA (Article 27)

Who must run a Fundamental Rights Impact Assessment, and how.

Who Does It Apply To?

Scope, operators, and the extraterritorial reach of the EU AI Act.

Post-Market Monitoring

Articles 72–73: ongoing monitoring and incident reporting.

ISO 42001 vs EU AI Act

How the voluntary standard and the binding law fit together.

NIST AI RMF vs EU AI Act

A practical crosswalk between the framework and the law.

EU AI Act for Healthcare

High-risk medical AI, MDR/IVDR interplay, and clinician oversight.

EU AI Act for Financial Services

Credit scoring, insurance pricing, and existing financial regulation.

EU AI Act for HR & Employment

Hiring AI as high-risk, plus NYC LL144 and EEOC overlap.