Skip to main content

Article 17 for Education AI: Quality Management System

How Article 17 (quality management system) applies to education AI: the 13 aspects, who is the provider, documentation, 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 sector-wide education regime; the hook is Annex III point 3, “Education and vocational training”, from 2 December 2027. A school or university that only uses a system is a deployer and has no Article 17 duty (exception: Article 25(1)). Fines go up to EUR 15 million or, for an undertaking, up to 3% of worldwide annual turnover, whichever is higher (Article 99(4)). Next step: check whether you are the provider of the system.

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. The Act lists 13 aspects, (a) to (m). Our grouping below shows (a) and three items that link to other duties of the Act first, then the other nine.

  • 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 education AI

Article 17 binds providers of high-risk AI systems only. The rows below show where education AI becomes high-risk and who is the provider.

  • Where education sits in the Act

    The Act has no sector-wide education regime. This site uses “education” for AI used in schools, universities, vocational training and exams. Such AI reaches the Act through Annex III point 3, headed “Education and vocational training”, and through the ban on inferring emotions in education institutions (Article 5(1)(f)). Point 3 does not name plagiarism detection, dropout prediction, adaptive learning platforms, learning dashboards or administrative chatbots; whether a system falls under it follows from the intended purpose (Article 3(12)). A system can also be high-risk under another point of Annex III.

  • Annex III point 3: four uses

    Annex III point 3 covers AI systems intended to be used: (a) to determine access or admission or to assign natural persons to educational and vocational training institutions at all levels; (b) to evaluate learning outcomes, including when those outcomes are used to steer the learning process of natural persons in educational and vocational training institutions at all levels; (c) for the purpose of assessing the appropriate level of education that an individual will receive or will be able to access, in the context of or within such institutions at all levels; (d) for monitoring and detecting prohibited behaviour of students during tests in the context of or within such institutions at all levels. Under Article 6(2), AI systems referred to in Annex III are considered high-risk. A provider that considers such a system not high-risk under Article 6(3) must document its assessment before the system is placed on the market or put into service, and must register it under Article 49(2). The derogation never applies where the system performs profiling of natural persons. Profiling means profiling as defined in Article 4, point (4), of Regulation (EU) 2016/679 (Article 3(52)).

  • 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 (Article 3(3)); this can be an education-technology vendor or a university that develops a system for its own use. A natural or legal person, public authority, agency or other body that uses a system under its authority, such as a school, university or examination body, is a deployer (Article 3(4)). 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)).

  • Dates

    Annex III point 3 applies from 2 December 2027 (Article 113, point (c)). A system placed on the market or put into service before that date is covered only if, from that date, its design undergoes significant changes. In the same paragraph, the “in any case” sentence says that providers and deployers of high-risk AI systems intended to be used by public authorities shall take the necessary steps to comply by 2 August 2030 (Article 111(2)). The Act does not state whether this also reaches systems placed on the market after 2 December 2027; ask counsel.

  • 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)).

  • 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 obligations of deployers who are natural persons using AI systems in the course of a purely personal non-professional activity (Article 2(10)). 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)).

  • Sectoral quality management systems

    Providers that are subject to obligations regarding quality management systems or an equivalent function under sectoral Union law may include the aspects of Article 17(1) as part of the quality management system under that law (Article 17(3)).

What the Act leaves open for education

  • No named standard, no education rule

    The Act names no standard or certification for the quality management system and has no education-specific rule. Article 17(1)(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.

  • 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.

  • Example: a table of the 13 aspects

    Example, not an Act requirement: a provider could list the 13 aspects in a table and mark the internal document that covers each.

Questions about Article 17 in education

Does a school that buys a grading tool need a quality management system?

Not under Article 17. It binds providers of high-risk AI systems. A school that only uses the tool is a deployer (Article 3(4)); it becomes the provider in the cases of Article 25(1).

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.

Does a university that builds its own admission tool become a provider?

Yes, if it develops the AI system, or has it developed, and puts it into service under its own name, also for its own use (Article 3(3)). It then carries the provider obligations of Article 16, including the quality management system in Article 17.

Related pages

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.