Artifact GuideEU AI Act

EU AI Act Duties for general-purpose AI models

If you provide a , Article 53 sets documentation, copyright and training-summary duties.

Models with systemic risk have extra evaluation, risk, incident and cybersecurity duties under Article 55.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 21, 2026
Overview

General-purpose AI (GPAI) models have a separate legal framework from system risk categories. Check whether you provide the model itself or build an application using someone else's model. Using a supplier's model alone does not make you its model provider.

Section 1

1. Are you the model provider?

A provider develops a , or has it developed, and places it on the market under its own name or trademark. A customer, reseller or application developer can have other duties without holding that role.

GPAI duties have applied since 2 August 2025; Commission enforcement powers apply from 2 August 2026. Models placed on the market before 2 August 2025 have a compliance transition to 2 August 2027. The 2026 amendment does not postpone these dates.

A non-EU provider must appoint an EU authorised representative by written mandate before EU market placement, unless the Article 54 qualifying open-source exception applies. That exception is unavailable for models with systemic risk.

The representative checks that Annex XI documentation exists, keeps a copy for 10 years after market placement, provides it to authorities on request and cooperates with them.

  • Classify the model and any application built with it separately.
  • Record release through an API, download, library or the provider's own system.
  • For purely internal use, assess whether it is essential to a third-party product/service or affects people's rights before concluding that the market-placement trigger is absent.
  • Save the first EU market-placement date and the evidence for any transition.
  • For a non-EU provider, retain the representative mandate, contact details, documentation location, request log and retention date.
Section 2

2. Complete the four Article 53 duties

Providers need model technical documentation, information for application developers integrating the model, a copyright policy and a public training-content summary.

The technical file must go beyond a short model card. Annex XI covers purpose, use policies, release method, architecture, parameters, input and output types, licence, training/testing, data sources and preparation, compute, training time and known or estimated energy use where relevant.

  • Technical documentation: keep training/testing details and evaluations up to date and ready for the AI Office or national authorities on request (Article 53(1)(a)).
  • Integrator information: provide at least the Annex XII information to downstream providers intending to build systems with the model (Article 53(1)(b)).
  • Copyright policy: comply with EU copyright and related-rights law, including identifying and respecting rights reservations under Article 4(3) of Directive (EU) 2019/790 (Article 53(1)(c)).
  • Training summary: publish a sufficiently detailed summary of training content using the AI Office template (Article 53(1)(d)).
  • Cooperation: assist the Commission and national authorities as necessary when they exercise their AI Act powers.
Section 3

3. Check open-source and modification rules

The Article 53 open-source exception covers only technical documentation and integrator information. The licence must permit access, use, modification and distribution, and parameters, weights, architecture and usage information must be public.

Copyright policy and the public training summary remain required. Models with systemic risk cannot use this exception.

Commission guidance treats a modifier as a provider of the modified model when the change significantly affects generality, capabilities or systemic risk. Fine-tuning alone does not settle that question.

  • Check the licence and all required public information; public weights alone are insufficient.
  • Keep copyright and training-summary records for qualifying open-source models.
  • For modifications, record changed tasks, capabilities, evaluations, training compute and data sources.
  • For systemic-risk models, complete Article 53 documentation and Article 55 controls even if the model is open-source.
Section 4

4. Check systemic risk and the extra duties

A GPAI model has systemic risk if it has high-impact capabilities assessed using appropriate tools, indicators and benchmarks, or the Commission designates it for equivalent capabilities or impact.

Article 51 presumes high-impact capabilities when training compute exceeds 10^25 floating-point operations. If that condition is met or you know it will be met, notify the Commission without delay and within two weeks.

Article 55 adds evaluations, EU-level risk assessment and mitigation, serious-incident tracking/reporting without undue delay, and adequate cybersecurity for the model and its physical infrastructure.

  • Keep any substantiated argument for exceptional non-classification despite meeting the high-impact-capability condition.
  • Run and document model evaluations, including adversarial testing, against systemic-risk scenarios.
  • Maintain risk sources, mitigations, residual-risk decisions, cybersecurity controls, incident triggers and corrective measures.
  • Use the Commission's systemic-risk GPAI serious-incident template for relevant incident information and corrective measures.
Section 5

5. Give integrators usable information

Annex XII information must help application providers understand the model's capabilities and limits and meet their own duties. Include tasks, integration options, use policies, distribution, software/hardware dependencies, versions, architecture, parameters, input/output formats and limits, licence and relevant training, testing and validation data.

For Code of Practice signatories, the Transparency chapter adds access commitments: provide contact details, current documentation for integrators and necessary additional information within a reasonable time. The deadline is no later than 14 days after a request, except in exceptional circumstances.

  • Prepare an integrator version separately from authority-only and trade-secret material.
  • Provide a clear contact channel for Article 53 information requests.
  • Link fields to the model registry, release notes, data records, licences, use policies, evaluations and security reviews.
  • Version the package with each model release so users can identify what they relied on.
Section 6

6. Choose how to demonstrate compliance

The GPAI Code of Practice is voluntary and has been assessed as adequate by the Commission and AI Board. Providers can use it to demonstrate compliance, or use other permitted routes.

Harmonised standards can provide a presumption of conformity for the obligations they cover. Providers using neither an assessed adequate code nor harmonised standards must demonstrate alternative adequate means for Commission assessment.

The Code is not a copyright safe harbour. Its Copyright chapter states that adherence does not establish compliance with EU copyright law or limit court enforcement.

Is a foundation model the same legal term as GPAI?

The Act uses . Use that definition when deciding whether Articles 53 and 55 apply; foundation model is a market term.

What does Article 53 require?

Up-to-date technical documentation, information for system developers integrating the model, an EU copyright policy, a public training-content summary using the AI Office template, and cooperation with authorities. Check the limited open-source exception.

When do Article 55 duties apply?

When the model is classified as having systemic risk under Articles 51 and 52. Providers then need evaluations and adversarial tests, systemic-risk mitigation, serious-incident reporting and cybersecurity protection.

  • Use the Transparency and Copyright chapters for Article 53 if you sign and implement their commitments.
  • Use Safety and Security for systemic-risk models under Article 55, or voluntarily apply equivalent controls.
  • Keep the signature, implemented commitments, model records, copyright measures and safety/security evidence, or the alternative means used.
  • Map the evidence to Article 53 or 55 even when using the Code.
Primary sources

References and citations

eur-lex.europa.eu7 citations
Referenced sections
  • Primary legal text for GPAI model definitions, Article 53 baseline duties, Article 55 systemic-risk duties, Annex XI, Annex XII, and systemic-risk classification.
  • Primary legal text defining providers, general-purpose AI models, systemic risk, and Chapter V obligations.
  • Article 53 and Annexes XI-XII set the baseline GPAI provider documentation, downstream-information, copyright-policy, and training-summary duties.
Show 4 more
  • Article 53(2) states the limited open-source exception and expressly excludes systemic-risk GPAI models from it.
  • Articles 51, 52, and 55 define systemic-risk classification, notification timing, and the additional duties for GPAI models with systemic risk.
  • Annex XII lists the minimum downstream transparency information for providers integrating GPAI models into AI systems.
  • Articles 53 and 55 explain use of codes of practice, harmonised standards, and alternative adequate means of compliance.
"general-purpose AI model"
More quoted passages
"Obligations for providers of general-purpose AI models"
"This exception shall not apply"
"greater than 10^25"
"Transparency information"
"alternative adequate means of compliance"
digital-strategy.ec.europa.eu3 citations
Referenced sections
  • Commission page describing the voluntary GPAI Code of Practice and its Transparency, Copyright, and Safety and Security chapters.
  • Commission page explaining that the Safety and Security chapter is for GPAI models subject to Article 55 systemic-risk obligations.
  • Commission page identifying the Code as a voluntary tool, recording the Commission and AI Board's adequacy assessment, and distinguishing the Transparency, Copyright, and Safety and Security chapters.
"voluntary tool"
More quoted passages
"Safety and Security"
digital-strategy.ec.europa.eu3 citations
Referenced sections
  • Commission guidance page for interpreting the scope of GPAI model provider obligations, significant modifications, open-source conditions, application dates, and EU SEND submissions.
  • Commission page explaining that its GPAI guidelines clarify who is expected to follow provider obligations.
  • Commission guidance page summarising its position on significant modifications and open-source GPAI conditions.
"scope of obligations"
More quoted passages
"clarify the scope of the obligations"
"significant modifications to AI models"
ai-act-service-desk.ec.europa.eu2 citations
Referenced sections
  • Official article page used for third-country GPAI provider authorised-representative appointment, mandate, cooperation, and retention evidence.
  • Supports third-country GPAI provider appointment, written mandate, verification, cooperation, document-access, and 10-year retention duties.
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission explanatory notice and template for the Article 53(1)(d) public summary of GPAI model training content.
  • Commission explanatory notice and template for the public training-content summary required by Article 53(1)(d).
"summary of training content"
More quoted passages
"Public Summary of Training Content"
digital-strategy.ec.europa.eu2 citations
Referenced sections
  • Commission reporting-template page for serious incidents involving GPAI models with systemic risk.
  • Commission page for the reporting template covering serious incidents involving GPAI models with systemic risk.
"serious incidents"
More quoted passages
"serious incidents involving general-purpose AI models"
ec.europa.eu2 citations
Referenced sections
  • Copyright chapter support for maintaining a Union copyright-policy document and respecting rights reservations, with the caveat that Code adherence is not copyright-law compliance by itself.
  • Copyright chapter caveat that Code adherence does not itself constitute compliance with Union copyright law.
"copyright policy"
More quoted passages
"does not constitute compliance"
ec.europa.eu2 citations
Referenced sections
  • Transparency chapter support for model documentation, downstream-provider information, request channels, and information quality controls.
  • Transparency chapter describing model documentation, downstream-provider information, and request handling for signatories.
"model documentation"
More quoted passages
"Providing relevant information"
eur-lex.europa.eu2 citations
Referenced sections
  • Binding 2026 amendment checked to confirm that the GPAI application and pre-existing-model transition dates remain unchanged.
  • Supports the statement that the 2026 amendment did not postpone the existing GPAI application and transition dates.
Show all related guides (34)

EU AI Act serious incident reporting steps

Check serious-incident harm, preserve evidence and choose the reporting deadline and recipient for high-risk AI systems and systemic-risk GPAI models.

EU AI Act timeline and phased deadlines

See which AI Act rules apply now and what comes next. Check high-risk dates, older-model transitions and the difference between legal and standards dates.

EU AI Act vs ISO/IEC 42001

Compare AI Act legal duties with ISO/IEC 42001 management-system requirements. See which records can be reused and what certification does and does not cover.

EU AI Act vs NIST AI RMF

Compare AI Act legal duties with the voluntary NIST AI RMF. Map risk records to specific requirements and identify legal steps that need separate evidence.

EU AI Act: Check whether the Act applies

Use five checks to establish AI Act scope, exclusions, your role, risk categories and evidence for the decision.

EU AI Act: Choose a high-risk assessment route

Choose between provider-run internal control, notified-body assessment and a product-law procedure before release.

EU AI Act: Classify a tool before approval

Classify an AI tool or model before purchase or release. Check EU scope, prohibited uses, high-risk rules, transparency and GPAI duties.

EU AI Act: Compliance checklist

Check each AI tool, decide which duties apply, and give every action an owner and evidence link.

EU AI Act: Conformity assessment

Some high-risk systems use a provider-run assessment. Others need an authorised independent assessor or a product-law assessment.

EU AI Act: Does it apply to you?

Check whether the AI Act applies to your system or model, identify your provider or deployer role, and keep evidence for the decision.

EU AI Act: High-risk requirements

High-risk providers must meet system requirements before supply. Deployers must use and monitor the system under the provider's instructions.

EU AI Act: High-risk system checklist

Check the system's risk controls, data, documentation, logs, instructions, human oversight and testing before release.

EU AI Act: Is your use case high-risk?

Find high-risk AI examples in recruitment, banking, education, healthcare, public services and products. Check Article 6 conditions and exceptions.

EU AI Act: Plan your compliance work

Build a compliance plan for each AI tool: your role, the duties that apply, the evidence needed and the person responsible.

EU AI Act: Standards and quality management

Use EN 18286:2026 to organise provider quality-management procedures and keep evidence that they work for each high-risk system.

EU AI Act: Technical file and evidence templates

Build the technical file and provider records for a high-risk AI system, with owners and evidence links for each field.

EU AI Act: When must you disclose AI?

Check Article 50 chatbot notices, synthetic-output marking, biometric notices, deepfake disclosures and public-interest text exceptions.

EU AI Act: Which AI uses are banned?

Check Article 5 prohibited AI practices, the narrow exceptions, evidence to retain and the new content prohibitions from 2 December 2026.

Are you the provider or the deployer? | EU AI Act

Check provider, deployer, importer and distributor roles, when changes create provider duties, and how model and system responsibilities differ.

Do you need a notified body? | EU AI Act

Find the assessment route for high-risk AI, when a notified body is required, and which declaration, CE-marking and registration records you need.

Does this tool count as AI? | EU AI Act

Check whether software counts as AI, how models differ from systems, when embedded AI is high-risk, and which scope and role evidence to keep.

How do you monitor AI after release? | EU AI Act

Understand high-risk AI monitoring under Article 72: the provider plan, deployer feedback, logs, corrective action, incidents and change reviews.

Is this industry use high-risk? | EU AI Act

See which industry AI uses fall under Annex III, when Article 6(3) can apply, and what providers must document and register.

What belongs in the technical file? | EU AI Act

See what Article 11 and Annex IV require in high-risk AI technical documentation, from system identity and testing to monitoring and retention.

What must general-purpose model providers do? | EU AI Act

Check general-purpose model duties, systemic-risk classification, open-source conditions, copyright, training summaries, incidents and application dates.

When must you disclose AI use? | EU AI Act

Check AI interaction notices, technical content marking, biometric notices, deepfake and text disclosures, exceptions, accessibility and deadlines.

When must you report a serious incident? | EU AI Act

Check serious-incident outcomes, reporting roles, 15-, 10- and two-day deadlines, authority recipients, corrective action and the separate model route.

Who needs a rights impact assessment? | EU AI Act

Check who needs an Article 27 fundamental rights impact assessment, what it must cover, and how privacy assessments, notification and registration fit.