EU AI Act Art.17: Quality management system
Article 17 of the EU AI Act binds the operator (see the article). It requires Providers must put in place a quality management system that ensures compliance with the Regulation, documented systematically in written policies. This page states what it requires, who it binds and the evidence to keep. Browsing is free; the conformance kit is USD 499.
Specifics
| Instrument | Regulation (EU) 2024/1689 (the EU AI Act), as amended by Regulation (EU) 2026/1744 |
|---|---|
| Article | Art.17 |
| Binds | Operator (see the article) |
| Group | High-Risk Operator Obligations |
| Evidence items | 6 |
| Linked NIST AI RMF controls | 4 |
| Linked ISO/IEC 42001 controls | 12 |
| Last updated |
Who does Art.17 bind?
The article binds the operator (see the article). The Act places each duty on a named party in the value chain, so a system can carry a provider duty and a deployer duty at once. Confirm your own position against the text; this page names the party, it does not rule on your facts.
Applies with the high-risk regime: 2 December 2027 for stand-alone systems listed in Annex III, and 2 August 2028 for AI embedded in regulated products listed in Annex I (Article 113, as amended by Regulation (EU) 2026/1744). See the full timeline.
What does Art.17 require?
Providers must put in place a quality management system that ensures compliance with the Regulation, documented systematically in written policies, procedures and instructions, covering at least: a regulatory compliance strategy including conformity assessment and management of modifications; design, design control and design verification techniques; development, quality control and quality assurance techniques; examination, test and validation procedures before, during and after development and the frequency at which they run; technical specifications and standards to be applied and, where harmonised standards are not applied in full, the means used instead; data management systems and procedures spanning acquisition, collection, analysis, labelling, storage, filtration, mining, aggregation and retention; the Art.9 risk management system; the Art.72 post-market monitoring system; Art.73 serious incident reporting procedures; handling of communication with authorities, notified bodies, other operators and customers; record-keeping; resource management including security of supply; and an accountability framework setting out the responsibilities of management and staff for every one of those aspects. Implementation is proportionate to the size of the provider's organisation, but the degree of rigour required to make the systems compliant is not reducible.
This is our plain-language statement of the article, not the text of the regulation. Read the article: Art.17 (Regulation (EU) 2024/1689 on EUR-Lex).
What evidence should we keep for Art.17?
| Category | Evidence to keep |
|---|---|
| Quality management | The written quality management system covering all thirteen Art.17(1) aspects, with a cross-reference showing where each is addressed |
| Quality management | The accountability framework naming responsibilities of management and staff for each aspect |
| Quality management | Change management records for modifications to the high-risk AI system |
| Quality management | Test and validation procedures with their defined frequency, and completed records against them |
| Quality management | Where harmonised standards are not applied in full, the documented alternative means of meeting the Section 2 requirements |
| Quality management | For financial institutions, the mapping of which internal governance arrangements are relied on under Art.17(4), with evidence that points (g), (h) and (i) are still discharged separately |
What does a linked control mean here?
A linked control is a NIST AI RMF or ISO/IEC 42001 control that the held rule set records as a topical match, with a confidence and a one-line reason. It does not establish that meeting one requirement satisfies the other, it is not legal advice, and it is not certification. Where no control is recorded, the page says so and does not guess. Sources: the NIST AI RMF and ISO/IEC 42001.
Which NIST AI RMF controls line up with Art.17?
4 controls in the held rule set is recorded as a topical match for this obligation, each with its confidence and reason.
| Control | NIST AI RMF | Confidence |
|---|---|---|
AIRMF-GV-1.2 | The characteristics of trustworthy AI are integrated into organizational policies, processes, and procedures A written QMS carrying compliance strategy, design control, data management and accountability integrates these characteristics into procedure. | high |
AIRMF-GV-2.1 | Roles and responsibilities and lines of communication related to mapping, measuring, and managing AI risks are documented and are clear to individuals and teams throughout the organization The QMS accountability framework sets out management and staff responsibilities across the lifecycle. | high |
AIRMF-MP-1.6 | System requirements are elicited from and understood by relevant AI actors, and design decisions take socio-technical implications into account to address AI risks QMS design, design control and design verification techniques plus applied standards are the requirements regime. | high |
AIRMF-MS-2.13 | Effectiveness of the employed TEVV metrics and processes in the MEASURE function are evaluated and documented The QMS fixes test procedures and their frequency but does not evaluate whether the metrics still work. | medium |
Which ISO/IEC 42001 controls line up with Art.17?
12 controls in the held rule set is recorded as a topical match for this obligation, each with its confidence and reason.
| Control | ISO/IEC 42001 | Confidence |
|---|---|---|
A.2.2 | AI policy Quality management system documented in written policies covering AI development, deployment and compliance. | high |
A.2.3 | Alignment with other organizational policies Quality system integrates data, risk, security of supply and accountability across functions. | medium |
A.2.4 | Review of the AI policy Compliance strategy includes management of modifications but sets no review interval. | low |
A.3.2 | AI roles and responsibilities Accountability framework sets out responsibilities of management and staff for every quality aspect. | high |
A.4.2 | Resource documentation Quality system covers resource management including security of supply. | medium |
A.4.3 | Data resources Data management procedures span acquisition, collection, labelling, storage and retention. | medium |
A.6.1.2 | Objectives for responsible development of AI system Regulatory compliance strategy sets documented aims for development, but not development objectives. | medium |
A.6.1.3 | Processes for responsible design and development of AI systems Documents design, design control, design verification, development and quality assurance techniques. | high |
A.6.2.2 | AI system requirements and specification Quality system fixes technical specifications and standards applied, or equivalent means. | medium |
A.6.2.4 | AI system verification and validation Quality system fixes examination, test and validation procedures and their frequency. | medium |
A.7.2 | Data for development and enhancement of AI system Data management procedures are a documented part of the quality system. | medium |
A.7.6 | Data preparation Data procedures span analysis, labelling, filtration, mining and aggregation. | medium |
What does the conformance kit add for Art.17?
The kit renders this obligation into your own role checklist with the evidence register, the linked controls and a CSV export, for USD 499 one off. See what is in the kit or open it.