Article 17 for Autonomous Systems: Quality Management System
How Article 17 (quality management system) applies to autonomous systems: the 13 aspects, who is the provider, Annex I Section A and B, Annex III point 2, dates and fines.
Providers of high-risk AI systems must run a quality management system covering at least 13 aspects (Article 17(1)).
The Act has no “autonomous systems” category. Article 17 binds providers of Annex I Section A products from 2 August 2028 and of Annex III point 2 systems from 2 December 2027. It does not bind providers of vehicles, aircraft, rail or machinery in Annex I Section B (Article 2(2)). Fines go up to EUR 15 million or, for an undertaking, 3% of worldwide annual turnover, whichever is higher (Article 99(4)). Next step: check your role and your Annex I entry.
Article 17 lists 13 aspects the system must include
The system must be documented in a systematic and orderly manner as written policies, procedures and instructions. In our grouping, four aspects link to other duties of the Act; nine more follow.
- Art. 17(1)(a)Regulatory compliance strategy
A strategy for regulatory compliance, including compliance with conformity assessment procedures and procedures for managing modifications to the system.
- Art. 17(1)(g)Risk management system
The risk management system referred to in Article 9.
- Art. 17(1)(h)Post-market monitoring
Setting up, implementing and maintaining a post-market monitoring system under Article 72.
- Art. 17(1)(i)Serious incident reporting
Procedures for reporting a serious incident under Article 73.
- Art. 17(1)(b)–(f), (j)–(m)The other nine aspects
Design and design control; development, quality control and quality assurance; examination, test and validation procedures; technical specifications and standards; data management; communication with authorities, notified bodies and others; record-keeping; resource management; and an accountability framework.
- Art. 17(2)Proportionate to size, not to protection
Implementation must be proportionate to the size of the provider’s organisation, in particular for an SME, including a start-up, or a small mid-cap enterprise. Providers must still respect the degree of rigour and the level of protection needed for compliance of their high-risk systems.
How Article 17 applies to autonomous systems
Article 17 binds providers of high-risk AI systems only. The rows below show which autonomous systems it reaches and who is the provider.
Autonomous systems is not a category in the Act
The Act has no category called autonomous systems; its definition of an AI system refers to operation with varying levels of autonomy (Article 3(1)). This site uses the word for AI in vehicles, drones, robots and machinery, and for AI that helps manage road traffic. Such AI can be high-risk through three routes, and the route decides which high-risk rules apply: Annex I Section B (Article 2(2) limits the rules to a few articles), Annex I Section A (the Chapter III requirements from 2 August 2028, where the system is high-risk under Article 6(1)) and Annex III point 2 (the Chapter III requirements from 2 December 2027). Other rules do not depend on the route: Articles 4 and 5, Article 50, Article 53 for model providers and the other points of Annex III. Article 2(2) restricts only AI systems that are high-risk under Article 6(1) in Section B products. Find your high-risk route first.
Vehicles, aircraft, rail, marine equipment and machinery: Annex I Section B
Section B of Annex I lists, among others, motor vehicles (Regulations (EU) 2018/858 and 2019/2144), two- or three-wheel vehicles (Regulation (EU) No 168/2013), agricultural and forestry vehicles (Regulation (EU) No 167/2013), the rail system (Directive (EU) 2016/797), marine equipment (Directive 2014/90/EU), unmanned aircraft and their engines, propellers, parts and equipment to control them remotely, in so far as Regulation (EU) 2018/1139 covers them, and machinery (Regulation (EU) 2023/1230, moved from Section A to Section B by Regulation (EU) 2026/1744). For an AI system that is high-risk under Article 6(1) and relates to such a product, only Article 6(1), Article 60a and Articles 102 to 112 apply (Article 2(2)); Articles 57, 58 and 59 apply only in so far as the requirements for high-risk AI systems have been integrated in that Union harmonisation legislation. Articles 9 to 15, 17 and 26 are not among them. Instead, Articles 102 to 109 add to eight of these laws a rule that the Commission takes the requirements of Chapter III, Section 2 into account when it adopts the acts they name for AI systems. For machinery, Article 3(1) of Regulation (EU) 2026/1744 requires the Commission to adopt delegated acts that add health and safety requirements for such AI systems, reflecting Chapter III, Section 2 and Articles 17, 19, 72 and 73; those acts are to apply by 2 August 2028.
Section A products and Annex III point 2: Chapter III applies
Two hooks bring the Chapter III requirements into play. First, an AI system is high-risk under Article 6(1) if it is intended to be used as a safety component of a product covered by Annex I legislation, or is itself such a product, and that product must undergo a third-party conformity assessment under that legislation. Section A (items 2 to 12) covers, for example, lifts, cableway installations, recreational craft and medical devices; Chapter III applies to such systems from 2 August 2028 (Article 113, point (c)(ii)). A safety component is a component that fulfils a safety function or whose failure or malfunctioning endangers the health and safety of persons or property (Article 3(14)); AI used solely for non-safety related aspects such as performance optimisation, automation or convenience does not qualify, but AI whose failure would endanger health and safety does (Article 6(1a) and (1b)). A product that needs a third-party assessment solely because of risks other than health and safety, such as radio spectrum use or electromagnetic interference that does not affect health and safety, does not meet that condition (Article 6(1c)); this matters, for example, for radio equipment (item 6). Second, Annex III point 2 covers AI systems intended to be used as safety components in the management and operation of critical digital infrastructure, road traffic, or the supply of water, gas, heating or electricity; Chapter III applies to them from 2 December 2027 (Article 113, point (c)(i)). On its wording, point 2 names the management and operation of road traffic, not vehicles.
Provider and deployer
The provider develops the AI system, or has it developed, and places it on the market or puts it into service under its own name or trademark (Article 3(3)); this can be a product manufacturer or a software vendor. For a high-risk AI system that is a safety component of a Section A product, the product manufacturer is the provider if the system is placed on the market with the product under the manufacturer’s name or trademark, or put into service under that name or trademark after the product has been placed on the market (Article 25(3)). A fleet, plant or traffic operator that only uses the system is a deployer (Article 3(4)) and has no Article 17 duty. A deployer becomes a provider if it puts its name or trademark on a high-risk system already on the market, makes a substantial modification that leaves the system high-risk, or changes the intended purpose of a non-high-risk system so that it becomes high-risk (Article 25(1)).
Conformity assessment: sector law for Section A, internal control for point 2
For high-risk AI systems covered by the Union harmonisation legislation listed in Section A of Annex I, the provider follows the conformity assessment procedure required by that legislation; the requirements of Chapter III, Section 2 are part of that assessment, and the quality management system under Article 17 is also assessed (Article 43(3)). Where that legislation lets a manufacturer rely on an assessment without a third party, the manufacturer may use that option only if it also applied harmonised standards or common specifications covering all requirements of Section 2 (Article 43(3)). For high-risk systems referred to in points 2 to 8 of Annex III, providers follow the procedure based on internal control in Annex VI, which does not provide for the involvement of a notified body (Article 43(2)); the provider verifies that the established quality management system complies with Article 17 (Annex VI, point 2). Article 43 is not among the provisions that Article 2(2) lists as applying to Section B products. Notified bodies already notified under Section A legislation are to apply for designation under Chapter III, Section 4 by 28 January 2028 (Article 43(3)).
Sectoral quality management systems and Section A documentation
Providers of high-risk AI systems that are subject to obligations regarding quality management systems or an equivalent function under relevant sectoral Union law may include the aspects listed in Article 17(1) as part of the quality management system under that law (Article 17(3)). For a product with an AI system under Section A legislation, providers may also integrate the testing and reporting processes, information and documentation for the AI requirements into documents and procedures that already exist under that legislation (Article 8(2)). The Commission is to publish guidelines on the practical implementation of Article 8(2), Article 9(10) and Article 17(3) by 1 August 2027 (Article 96(1), point (g)). Article 17(3) does not list the sectoral laws it means; whether a provider’s duties under such a law amount to a quality management system or an equivalent function is not answered by the Act; ask counsel.
Dates
Annex III point 2 systems must meet Chapter III from 2 December 2027, and Section A systems from 2 August 2028 (Article 113, point (c)). For Section B systems, no date applies to Articles 9 to 15, 17 and 26, because those articles do not apply to them; Article 113, point (c)(ii), applies Chapter III, Sections 1 to 3, which include Article 6, to Annex I systems from 2 August 2028, and Articles 102 to 110 apply since 27 July 2026 (Article 113, points (c)(ii) and (d)). A system placed on the market or put into service before the date of application of Chapter III is covered only if its design changes significantly afterwards; in any case, providers and deployers of high-risk systems intended to be used by public authorities must take the necessary steps to comply by 2 August 2030 (Article 111(2)).
Fines
Breaches of provider obligations under Article 16 and of deployer obligations under Article 26 can be fined up to EUR 15 million or, for an undertaking, up to 3% of total worldwide annual turnover in the preceding financial year, whichever is higher (Article 99(4)). For SMEs, including start-ups, each fine is capped at whichever is lower (Article 99(6)). The same cap applies to small mid-cap enterprises (Article 3(14b), Article 99(6a)). Each Member State lays down rules on to what extent administrative fines may be imposed on public authorities and bodies established in that Member State (Article 99(8)). Article 99 is not among the provisions that Article 2(2) lists as applying to AI systems that are high-risk under Article 6(1) in Section B products.
Limits of the Act’s scope
The Act applies to providers that place AI systems on the market or put them into service in the Union, or place general-purpose AI models on the market in the Union, wherever they are established (Article 2(1), point (a)), and to providers and deployers in a third country where the output of the AI system is used in the Union (point (c)). It does not apply to areas outside the scope of Union law and does not affect Member States’ competences on national security, nor to AI systems used exclusively for military, defence or national security purposes (Article 2(3)). The Act does not apply to AI systems or AI models, including their output, specifically developed and put into service for the sole purpose of scientific research and development (Article 2(6)). It does not apply to research, testing or development before a system or model is placed on the market or put into service; testing in real world conditions is not covered by that exclusion (Article 2(8)). It does not apply to AI systems released under free and open-source licences, unless they are placed on the market or put into service as high-risk AI systems or as an AI system that falls under Article 5 or 50 (Article 2(12)).
What the Act leaves open for autonomous systems
No named standard, no rule specific to autonomous systems
The Act names no standard or certification for the quality management system and has no rule specific to autonomous systems. Article 17(1), point (e), refers to the technical specifications, including standards, to be applied and, where the relevant harmonised standards are not applied in full or do not cover all requirements of Chapter III, Section 2 (Articles 8 to 15), to the means used to ensure that the system complies with them. Quality rules in the sector law of a Section B product come from that law, not from Article 17 (Article 2(2)).
Ten-year retention is Article 18
The duty to keep the quality management system documentation for ten years after the system was placed on the market or put into service is in Article 18(1), not in Article 17.
Section A: requirements may be limited (Article 2(13))
For high-risk AI systems referred to in Article 6(1), the specific requirements or obligations in Articles 9 to 15 and 17 to 25 may be limited, where and to the extent that Union harmonisation legislation listed in Section A of Annex I lays down requirements or obligations providing an equivalent or higher level of protection and the limitation does not reduce the overall level of protection under the Act (Article 2(13)). The Commission is to adopt delegated acts specifying the systems concerned, the requirements that may be limited, the conditions and the scope by 2 August 2027. On a reading of Article 2(13), the Act itself does not say which requirements of a given Section A product are limited; the delegated acts are to do so; ask counsel.
Example: mapping the 13 aspects to existing documents
Example, not an Act requirement: a manufacturer that already keeps a quality management system under its sector law could list the 13 aspects in a table and mark the existing document that covers each.
Questions about Article 17 in autonomous systems
Does a vehicle or machinery manufacturer need an Article 17 quality management system?
Not under Article 17, for a high-risk AI system in an Annex I Section B product: Article 2(2) lets only Article 6(1), Article 60a and Articles 102 to 112 apply. For a Section A product or an Annex III point 2 system, the provider needs one.
Does a fleet or factory operator that buys an autonomous system need a quality management system?
Not under Article 17. It binds providers of high-risk AI systems. An operator that only uses the system is a deployer (Article 3(4)); it becomes the provider in the cases of Article 25(1).
Can a manufacturer’s existing sector quality system count?
In part. Article 17(3) lets providers that are subject to quality management obligations or an equivalent function under relevant sectoral Union law include the aspects of Article 17(1) in that system. The Act does not list the laws it means; ask counsel.
Does Article 17 require keeping records for ten years?
No. Article 18(1) requires the provider to keep the technical documentation, the quality management system documentation and other listed documents at the disposal of the national competent authorities for ten years after the system was placed on the market or put into service.
Related pages
EU AI Act Article 17: Quality Management System
Article 17 for all sectors: the 13 aspects, proportionality and fines.
EU AI Act Compliance for Autonomous Systems
The autonomous systems overview: which Act hooks apply to vehicles, aircraft, machinery and traffic AI.
Article 26 for Autonomous Systems: Deployer Obligations
Autonomous systems and Article 15: accuracy, robustness, cybersecurity, dates and roles.
Annex I High-Risk AI Systems: The Product-Safety Route
Annex I: which AI systems in regulated products are high-risk, with Section A and Section B.
Scanara prepares evidence from your repositories
Scanara reads your connected GitHub repositories and runs rule-based scans for standard AI and machine-learning patterns. It can miss non-standard code. Separately, it generates draft documentation from templates and your assessment answers as evidence for your compliance work. You make the classification decisions.