From 2 December 2027, a provider of a high-risk AI system listed in Annex III must have a quality management system that ensures compliance with the AI Act. That system is documented in a systematic and orderly manner in written policies, procedures and instructions, and includes at least thirteen aspects (Article 17(1) AI Act). The obligation sits in the list of provider duties (Article 16(c)). An organisation that only uses a system it has bought, the deployer, does not have to set up a quality management system. Its own obligations are in Article 26.
Suppose a mid-sized municipality develops, with its own data team, a model that pre-sorts applications for special assistance benefits. For each application the model gives the caseworker advice: grant directly, or investigate further first. It runs under the municipality's name, and there is no vendor placing the system on the market. The project lead asks: "We already have a privacy policy and a DPIA, don't we? What else is needed?" The answer: the municipality is the provider here, and Article 17 asks for a quality system around the whole system, from design to incident reporting. The example is fictitious.
In short
Article 17 has four paragraphs. Paragraph 1 requires providers of high-risk systems to have a documented quality management system covering at least points (a) to (m): from a compliance strategy and change management to data management, risk management (Article 9), post-market monitoring (Article 72), reporting of serious incidents (Article 73) and an accountability framework. Paragraph 2 makes implementation proportionate to the size of the organisation, since the Digital Omnibus (Regulation (EU) 2026/1744) in particular for SMEs, start-ups and small mid-cap enterprises, with no discount on rigour. Paragraph 3 lets providers with a quality system under sectoral Union law include the aspects in it. Paragraph 4 provides that financial institutions with governance requirements under Union financial services law fulfil the obligation by complying with those requirements, except for risk management, monitoring and incident reporting (points (g), (h) and (i)). Since 14 October 2026, EN 18286:2026 is a harmonised standard on quality management. The decision names no articles, and Article 40(1) refers to the requirements of Section 2, while Article 17 is in Section 3; how far the presumption of conformity reaches for Article 17 is, in our reading, not settled. For Annex III, Article 17 applies from 2 December 2027; for Annex I, Section A, from 2 August 2028.
This piece is about Article 17 and what a provider does with it. When you become a provider is covered in when do you become a provider. How the quality system returns in the conformity assessment is covered in internal control or a notified body. What ISO/IEC 42001 does and does not cover is in ISO 42001 and the AI Act.
Who must have a quality management system
The addressee is the provider. That includes a public authority that develops an AI system, or has it developed, and puts it into service under its own name (Article 3, point (3)). The municipality in the example is therefore the provider. A company or municipality that buys a system and uses it in accordance with the instructions for use is a deployer and is not covered by Article 17. That changes if it puts its name on the system, substantially modifies it or changes its intended purpose so that it becomes high-risk; it then becomes the provider (Article 25(1)).
A deployer can still ask about its vendor's quality system. That is a procurement question, not an obligation of its own: in our reading, a vendor that cannot show its change management, tests and incident procedure tells you something about the reliability of the figures in its instructions for use. How a municipality reads those figures and puts them in its contract is covered in our piece on Article 15.
Paragraph 1: the thirteen aspects
The system must "ensure compliance with this Regulation". That is broader than product quality: it covers all obligations the provider has. Paragraph 1 lists the aspects it includes at least.
| Point | What the Regulation requires | What it means for the municipality (our translation) |
|---|---|---|
| (a) | Strategy for regulatory compliance, including conformity assessment and management of modifications to the system | Who decides on a new model version, and when is a change large enough to require a new assessment (Article 43(4))? |
| (b) | Techniques, procedures and systematic actions for design, design control and design verification | Recorded design choices, such as which data the model does and does not use, and who reviews those choices |
| (c) | The same for development, quality control and quality assurance | Code review, version control and a four-eyes principle for what goes into production |
| (d) | Examination, test and validation procedures before, during and after development, and their frequency | A test plan with fixed moments, also after putting into service |
| (e) | Technical specifications and standards, and the means to comply with Section 2 where harmonised standards are not applied in full or do not cover everything | Which standards the municipality follows, and how it substantiates the requirements where there is no standard |
| (f) | Systems and procedures for data management, from acquisition and labelling to storage, filtration and retention | Where the historical case files come from, who labels them and how long they are kept |
| (g) | The risk management system of Article 9 | Risk management is part of the quality system |
| (h) | Setting up, implementing and maintaining post-market monitoring (Article 72) | How the municipality tracks whether the model keeps performing in practice |
| (i) | Procedures for reporting serious incidents (Article 73) | Who establishes an incident, who reports and within which period |
| (j) | Communication with national competent authorities, other relevant authorities (including those providing or supporting access to data), notified bodies, other operators, customers and other interested parties | A fixed point of contact for the supervisor and a route for signals from residents and caseworkers |
| (k) | Systems and procedures for record-keeping of all relevant documentation and information | One place where the documentation sits, with versions |
| (l) | Resource management, including security-of-supply measures | Enough people, computing capacity and budget, and what happens if an external component drops out |
| (m) | An accountability framework setting out the responsibilities of management and staff for all aspects | Who in the executive board, management and team signs off on what |
The right-hand column is our practical translation, not text from the Regulation. It does show where the project lead in the example goes wrong: a privacy policy and a DPIA touch on point (f) and part of point (g), but say nothing about design verification, change management or incident reporting.
"Documented in a systematic and orderly manner" has consequences. The provider keeps the documentation concerning the quality management system for ten years after the system has been placed on the market or put into service, at the disposal of the national competent authorities (Article 18(1)(b)). In the conformity assessment based on internal control, the provider first verifies that the quality system complies with Article 17 (Annex VI, point 2). If the provider follows the route with a notified body, that body assesses the quality system and carries out surveillance of it (Annex VII, points 3 and 5). For the municipality, internal control applies: Annex III, point 5 falls under Article 43(2).
How Article 17 connects with Articles 9, 10, 11, 12, 72 and 73
Article 17 adds few new substantive requirements. Above all, it obliges the provider to cast its other obligations in a controlled process. Three points refer directly to another article.
Article 9: risk management (point (g)). The risk management system is a continuous iterative process throughout the lifecycle (Article 9). Article 17 makes it part of the quality system, so that the outcomes of risk management return in design, testing and change management. How to set up risk management itself is covered in the Article 9 risk management system.
Article 72: post-market monitoring (point (h)). The provider sets up monitoring that is proportionate to the nature of the technology and the risks, and that actively and systematically collects, documents and analyses data on performance throughout the lifetime (Article 72(1) and (2)). The monitoring plan is part of the technical documentation; the Commission adopts guidance with a template by 2 September 2027 (paragraph 3). For the municipality this is concrete: how often is the advice compared with the final decisions, and what happens when the two drift apart?
Article 73: serious incidents (point (i)). The provider reports a serious incident to the market surveillance authority of the Member State where it occurred, immediately after establishing a causal link or its reasonable likelihood, and in any event not later than 15 days after the provider or, where applicable, the deployer becomes aware of it; in the event of a widespread infringement or a serious and irreversible disruption of critical infrastructure not later than 2 days, and in the event of a death not later than 10 days after that awareness (Article 73(1) to (4)). The quality system records who assesses and reports. How that chain works is covered in reporting serious incidents.
The other three articles run through the aspects of paragraph 1.
Article 10: data (point (f)). Training, validation and testing data sets must meet the quality criteria of Article 10(2) to (4) and Article 4a(1) (Article 10). Point (f) asks for the procedures by which the provider ensures this. Note one change by the Omnibus: the exception for processing special categories of personal data to detect and correct bias used to be in Article 10(5) and is now in Article 4a. See also data governance under Article 10.
Article 11: technical documentation (points (a), (d), (e) and (k)). The technical documentation demonstrates that the system complies with the requirements (Article 11(1)) and contains, among other things, the harmonised standards applied or, where none were applied, the solutions adopted (Annex IV, point 7), the relevant changes during the lifecycle (point 6) and the monitoring plan (point 9). The quality system is the process; the technical documentation is what that process delivers for each system.
Article 12: logging (points (d) and (k)). A high-risk system must technically allow for the automatic recording of events (Article 12), and the provider keeps the logs under its control for at least six months (Article 19(1)). In our reading, testing whether that logging works belongs to point (d), and retention belongs to point (k). For the municipality, which is provider and deployer at the same time, the interplay with the GDPR is covered in logs for high-risk AI.
Paragraph 2: proportionate to size, and what the Omnibus changed
Paragraph 2 says that the implementation of the aspects of paragraph 1 is proportionate to the size of the provider's organisation. The second sentence matters at least as much: providers shall in any event respect the degree of rigour and the level of protection required to ensure that their systems comply with the Regulation. A small provider may therefore have a lighter system, but not a system that achieves less.
The Digital Omnibus on AI, Regulation (EU) 2026/1744, in force since 27 July 2026, changed three things here. We checked them in the text of the Omnibus and in the consolidated text of the AI Act.
- Article 17(2) received an addition (Article 1, point (11), of the Omnibus). Proportionality now applies "in particular, if the provider is an SME, including a start-up, or an SMC". The notion of SME follows Recommendation 2003/361/EC, the notion of small mid-cap enterprise (SMC) Recommendation (EU) 2025/1099 (Article 3, points (14a) and (14b)). The sentence on rigour and level of protection remained.
- Article 63(1) was widened (Article 1, point (26)). Before 27 July 2026, only microenterprises could comply with certain elements of the quality system in a simplified manner. Now this applies to SMEs, including start-ups, provided they have no partner enterprises or linked enterprises within the meaning of Recommendation 2003/361/EC (Article 63; recital 28 of the Omnibus). SMCs are not included there. Which elements may be simplified is for the Commission to set out in guidelines; at the time of writing we are not aware of them. Article 63(2) provides that this is no exemption from other obligations, expressly including Articles 9, 10, 11, 12, 13, 14, 15, 72 and 73.
- The simplified technical documentation form was widened (Article 1, point (10)). SMEs and start-ups could already provide the elements of Annex IV in a simplified manner using a Commission form; this now also applies to SMCs (Article 11(1), second subparagraph). That is not part of Article 17, but it directly affects point (k).
A municipality is not an enterprise within the meaning of the SME Recommendation. In our reading, Article 63 therefore does not help it. The proportionality of paragraph 2 does apply to every provider, and recital 81 gives public authorities that put high-risk systems into service for their own use room to adopt and implement the rules for the quality system as part of a quality system adopted at national or regional level. A recital is not a free-standing obligation or exception. In our reading, it does indicate that a public authority may adopt the quality system rules as part of a quality system adopted at national or regional level. A municipality's own internal quality framework does not automatically qualify, and all aspects of paragraph 1 must be covered in any event.
Paragraph 3: an existing sectoral quality system
If the provider is already subject to a quality management obligation under sectoral Union law, it may include the aspects of paragraph 1 in that existing system (paragraph 3). The clearest example is a manufacturer of medical devices, which under Article 10(9) of the MDR (Regulation (EU) 2017/745) must already establish, document, implement and maintain a quality management system. Paragraph 3 removes nothing: all aspects of paragraph 1 must still be there, they may simply sit in one system. For products under Annex I, Section A, the quality system of Article 17 is assessed within the conformity assessment of the product legislation, applying parts of Annex VII (Article 43(3), as amended by the Omnibus). The Commission publishes guidelines by 1 August 2027 on the practical implementation of, among others, Article 17(3) in relation to that product legislation (Article 96(1)(g)). How that works out for medical AI is covered in medical AI under the AI Act and the MDR.
Standards: Article 40, EN 18286:2026 and ISO/IEC 42001
Point (e) asks the provider to record which technical specifications and standards it applies. Since 14 October 2026 there is a harmonised standard that deals directly with this subject: EN 18286:2026, "Artificial intelligence: Quality management system for EU AI Act regulatory purposes", whose reference was published by Implementing Decision (EU) 2026/2274. According to that decision, the standard was drafted under the standardisation request on quality management systems for providers, including post-market monitoring processes (recital 3), and satisfies the requirements it aims to cover (recital 5).
What that yields legally is less simple than it looks. Article 40(1) provides a presumption of conformity with "the requirements set out in Section 2 of this Chapter", to the extent the standard covers them. Article 17 is in Section 3. The decision names no articles and attaches no restriction to the reference. In our reading, how far the presumption reaches for Article 17 is therefore not settled. The Omnibus did add to Article 40(2) that the Commission is to request standards facilitating, for providers also covered by Annex I product legislation, the presumption of conformity with Chapter III, Sections 2 and 3 (Article 1, point (17), and recital 21 of the Omnibus). The legislator thus expects standards for Section 3, but Article 40(1) itself was not amended. So we do not write that whoever follows EN 18286 complies with Article 17. In our reading, the standard is nonetheless the most authoritative reference point available now, and paragraph 4 expressly provides that harmonised standards are taken into account for financial institutions. If a vendor asks you to rely on an EN 18286 claim, ask which clauses it applies, for which system and with what evidence.
ISO/IEC 42001 is an international standard for an AI management system at organisation level. It is not a harmonised standard under the AI Act; the implementing decision lists only EN 18286:2026. The European Commission's Joint Research Centre wrote in a policy brief that ISO/IEC 42001 is not aligned in objectives and approach with the AI Act, but does contain relevant clauses at the technical and organisational levels (JRC139430, 2024). In our reading, an existing ISO/IEC 42001 system can therefore be a starting point, but not a replacement for the aspects of Article 17 for each high-risk system.
The GDPR: accountability, design and security
The AI Act does not affect the GDPR, without prejudice to Articles 4a and 59 (Article 2(7), as amended by the Omnibus). If the provider processes personal data to develop the system, as the municipality does with its historical case files, three GDPR provisions run parallel to Article 17.
- Article 24 GDPR requires the controller to implement appropriate technical and organisational measures to ensure and to be able to demonstrate that processing complies with the GDPR; where proportionate, these include data protection policies (Article 24 GDPR). The idea is the same as in Article 17: policy on paper, and being able to show that it works.
- Article 25 GDPR requires data protection by design, already when determining the means of processing (Article 25 GDPR). That ties in with the design procedures of point (b) and the data management of point (f).
- Article 32 GDPR requires a level of security appropriate to the risk and a process for regularly testing the measures (Article 32 GDPR). That touches on the test procedures of point (d) and the resource management of point (l).
In our reading, the municipality can do much of this work once: a record of processing activities, a DPIA and a security policy that already exist belong in the documentation of the quality system. They do not replace it, because Article 17 also covers subjects on which the GDPR says nothing, such as conformity assessment and incident reporting to the market surveillance authority.
From when?
Article 17 is in Chapter III, Section 3. For high-risk systems under Annex III that Section applies from 2 December 2027, for systems under Section A of Annex I from 2 August 2028 (Article 113, third paragraph, point (c), as amended by Regulation (EU) 2026/1744). The municipality's system assesses whether residents are eligible for an essential public assistance benefit and, in our reading, falls under Annex III, point 5(a). Because the model profiles applicants, in our reading the municipality also cannot rely on the derogation in Article 6(3) (last subparagraph).
If the system was put into service before 2 December 2027, the high-risk obligations only apply if it undergoes significant changes in its design from that date; for systems intended to be used by public authorities, providers and deployers must comply with the Regulation by 2 August 2030 at the latest (Article 111(2)). For a municipality building now, that is no reason to wait: wrapping a quality system around an existing system afterwards is harder than building it in.
Example 2: the bank and paragraph 4
A bank that develops its own model to assess the creditworthiness of individuals is the provider of a high-risk system under Annex III, point 5(b). For the bank, paragraph 4 is the core. A provider that, as a financial institution, is subject to requirements on internal governance, arrangements or processes under Union financial services law is deemed to fulfil the quality management obligation by complying with those governance rules. Recital 158 mentions in this context, among others, credit institutions under Directive 2013/36/EU, insurers under Directive 2009/138/EC and insurance intermediaries under Directive (EU) 2016/97.
Three points are excepted, and the bank must therefore set those up under the AI Act itself:
- Point (g), risk management. Article 9(10) allows the risk management aspects to be part of, or combined with, the risk management procedures the bank already has under other Union law. Combining is allowed; skipping is not.
- Point (h), post-market monitoring. For Annex III, point 5 systems of financial institutions, the bank may integrate the elements of Article 72 into its existing systems and plans, provided the level of protection is equivalent (Article 72(4), second subparagraph).
- Point (i), serious incidents. The reporting procedure of Article 73 must be in place. Article 73(9) limits the reporting obligation for providers subject to Union instruments with equivalent reporting obligations. Whether that applies to a bank, the Regulation does not say in so many words; it requires an assessment of its own.
In addition, the bank keeps the technical documentation and the logs as part of the documentation kept under financial services law (Article 18(3) and Article 19(2)). Paragraph 4 only applies to institutions actually subject to such governance requirements. In our reading, a fintech without that status falls under the full Article 17, with the proportionality of paragraph 2 and, if it is a standalone SME, Article 63. As deployer of its own model, the bank also has obligations of its own, including a fundamental rights impact assessment (Article 27(1)). How existing banking rules relate to the AI Act is covered in the EBA mapping for the financial sector.
What to do now
- Establish whether you are the provider. Do you build a high-risk system yourself, have it built and put it into service under your name, or substantially modify it? Then Article 17 applies to you. If you only use a system you bought, it does not.
- Map your existing systems against paragraph 1. Quality policy, information security, privacy policy, a sectoral quality system or bank governance: mark for each of points (a) to (m) what is already there and what is missing.
- Set up the three links explicitly. Risk management (Article 9), monitoring (Article 72) and incident reporting (Article 73) are not outsourced to existing rules, not even for banks.
- Determine your size and status. Are you an SME without partner or linked enterprises, or a small mid-cap? Record that assessment, and follow the Commission's guidelines under Article 63 once they exist.
- Choose your standards deliberately. Record whether and how you apply EN 18286:2026, and how you substantiate the requirements where no standard exists (point (e)).
- Appoint owners. The accountability framework of point (m) is only worth something with names attached.
Unsure whether your system is high-risk and whether you are provider or deployer? With the case check you describe the application in a few questions and see which AI Act and GDPR obligations come into view.
Frequently asked questions about Article 17 AI Act
Sources
Newsletter
Every Tuesday, the AI Act week ahead in 5 minutes
A practical briefing on deadlines, new guidance and enforcement, so you know what matters this week. No spam and you can unsubscribe in one click.
Practical and short · No spam · One-click unsubscribe