Skip to content
EU AI Act · EU-AI-ACT-ART-53-GPAI-TRANSPARENCY

EU AI Act Article 53(1)(a)(b) - Obligations for providers of general-purpose AI models: technical documentation and transparency

Maintain Annex XI model documentation and Annex XII downstream integration information, subject to the limited Article 53(2) open-source exception

HIGHRecord-keeping dutyGovernanceBinding regulationIn forceEnforceable from 2 August 2025

Where this comes from

Provision: Article 53(1)(a)(b) - Obligations for providers of general-purpose AI models: technical documentation and transparency

Instrument: EU Artificial Intelligence Act (Regulation (EU) 2024/1689)

Citation: Article 53(1)(a)(b), Regulation (EU) 2024/1689

Text version: Regulation (EU) 2024/1689, consolidated 27 July 2026; original OJ L 12 July 2024 and amendment (EU) 2026/1744

Checked against the source: 6 September 2026

Read the official text ↗

Who it applies to

GPAI model provider in scope (Art. 2, Art. 3(63)) — all of these:

  • Project involves providing a general-purpose AI model (GPAI)
  • GPAI assessed Union model scope: YES

Article 53(2): systemic risk or release conditions not met — any one of these:

  • GPAI assessed Article 51 classification: YES
  • GPAI assessed open-release conditions: NO

What engineering work it implies

  • Annex IV Technical Documentation as CodeCovers part of it

    A /docs/ai-system/ skeleton carrying the nine Annex IV sections, versioned with the code, plus a CI check that fails the build when a model version changes without a...

Sample acceptance criteria Landfall generates for this obligation:

  • Version Annex XI and Annex XII records separately, with authority requests and downstream information-delivery evidence
  • Minimise personal data and document an actor-specific retention basis or justified organisational policy
  • An open-weights label without the required licence and published information cannot exempt documentation
  • An open-source systemic-risk model retains documentation duties
  • Provide attributable evidence for the cited provision and model version, with source version, review date and the applicable transition assessment

Evidence an auditor expects

  • Policy documentDocument reviewReviewed kept up to date; refreshed on each significant model change

    Model technical documentation under Art. 53(1)(a) and Annex XI

    Documentation drawn up and kept up to date BEFORE the model is placed on the Union market, covering the training process, training data and evaluation results, at the level of detail set by Annex XI, and available to the AI Office and national competent authorities on request

  • Contractual documentDocument review

    Downstream integration documentation under Art. 53(1)(b) and Annex XII

    The information and documentation made available to providers of AI systems who intend to integrate the model, sufficient to enable them to understand its capabilities and limitations and to comply with their own obligations — the Annex XII items, plus evidence of how downstream providers actually receive it (developer portal, licence pack, model card)

Questions people ask

Does EU AI Act Article 53(1)(a)(b) - Obligations for providers of general-purpose… apply to my service?
It applies when Project involves providing a general-purpose AI model (GPAI); GPAI assessed Union model scope: YES; and at least one of: GPAI assessed Article 51 classification: YES; GPAI assessed open-release conditions: NO.
When does this become enforceable?
EU AI Act Article 53(1)(a)(b) - Obligations for providers of general-purpose… is enforceable from 2 August 2025. Its current status is: in force.
What evidence does an auditor expect?
Model technical documentation under Art. 53(1)(a) and Annex XI; Downstream integration documentation under Art. 53(1)(b) and Annex XII.

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations