EU AI Act Compliance

EU AI Act Article 21: Cooperation With Competent Authorities

Article 21 of the EU AI Act requires providers of high-risk AI systems to supply documentation and, where applicable, log access to competent authorities upon a reasoned request. Meeting this obligation depends on having conformity documentation and automatically generated logs organized and retrievable in advance, not assembled reactively after a request arrives.

Article 21 At a Glance

A quick reference to the legal basis and core scope of the obligation before the full breakdown below.

AspectDetail
Legal basisRegulation (EU) 2024/1689, Chapter III, Section 3
Core obligationProvide documentation and log access on reasoned request
ConfidentialityGoverned separately under Article 78
Applies toProviders of high-risk AI systems

What Article 21 Requires

Article 21 sits within Chapter III, Section 3 of the EU AI Act, which sets out obligations for providers and other parties involved with high-risk AI systems. Article 21(1) requires providers to give a competent authority, upon a reasoned request, all information and documentation necessary to demonstrate conformity with the requirements set out in Chapter III, Section 2. This documentation must be provided in a language the requesting authority can easily understand, or in an official EU language indicated by the relevant Member State. Article 21(2) adds a distinct obligation: providers must give the requesting authority access to the automatically generated logs referenced in Article 12(1), to the extent those logs are under the provider's control. The Act entered into force in August 2024, with obligations for high-risk AI systems phased in through 2026, which means organizations building toward compliance now need to treat Article 21 readiness as an ongoing operational capability rather than a one-time filing exercise.

Scope of Authority Requests: Documentation and Logs

The two categories of material an authority can request under Article 21 are conformity documentation and system logs, and each carries different preparation demands. Conformity documentation traces back to the technical documentation obligations in Article 11, which must already exist for a high-risk system to be placed on the market. The practical question for compliance teams is whether that documentation is current, complete, and translatable on short notice.

Log access under Article 21(2) is narrower in scope. It applies only to logs generated automatically under Article 12, and only to the extent those logs are under the provider's control. This control qualifier matters for any organization using third-party models, outsourced components, or agentic systems where actions may be executed by components outside direct organizational ownership. If a provider cannot access or reconstruct logs from a delegated component, it cannot fulfill this part of Article 21 for that component, which makes contractual and technical log-access arrangements across the AI supply chain a practical prerequisite rather than an afterthought.

Confidentiality and Shared Responsibility

Information a competent authority obtains under Article 21 must be handled according to the confidentiality obligations set out in Article 78, which compliance teams should understand before preparing any disclosure of sensitive technical or business information. Because Article 21 does not itself specify a fixed response deadline, any timeframe is set within the individual reasoned request, so internal service-level tracking against those request-specific deadlines is necessary rather than reliance on a single statutory clock.

Responsibility for Article 21 compliance also needs to be explicitly assigned in value chains involving multiple parties, since providers, deployers, and third-party component suppliers may each hold different pieces of the required documentation or logs. Preparing conformity evidence and rationale in advance, rather than assembling it only after a request arrives, is the more defensible posture and reduces the risk of incomplete or delayed responses.

Technical Readiness for Log and Documentation Access

Article 21 does not prescribe a technical log format, which leaves organizations to determine how their logging architecture satisfies both the Article 12 recording obligation and the Article 21 disclosure obligation. Several architectural choices directly affect how quickly and accurately a request can be answered.

  1. 1

    Centralized log aggregation

    Consolidating logs across AI systems and agents reduces the time needed to compile a complete response to a reasoned request.

  2. 2

    Agent identity and provenance

    Clear identity data for AI agents and components allows a logged event to be mapped back to the specific system or deployment responsible for it.

  3. 3

    Structured retention and retrieval

    Logs and documentation should be stored in a form that supports extraction and, where required, translation for non-native-language authorities.

  4. 4

    Separation of routine and regulatory access

    Access controls should distinguish day-to-day operational log use from the controlled disclosure process used for authority requests.

  5. 5

    Third-party control mapping

    Where AI functions rely on outsourced or third-party components, organizations need clarity on which party retains control of the relevant logs.

Building an Article 21 Response Capability

Practical steps for coordinating documentation, logs, and legal review before a reasoned request arrives.

  • Establish an internal process for triaging reasoned requests, including legal review of scope before any disclosure.
  • Keep Article 11 technical documentation current and ready for presentation in required EU languages.
  • Define retention periods and retrieval procedures for automatically generated logs so they remain available on demand.
  • Assign clear ownership across compliance, legal, and engineering teams for coordinating authority cooperation.
  • Formalize contractual log-access rights with vendors or subprocessors for any outsourced or agent-based AI functions.
  • Track any deadlines stated in individual reasoned requests, since Article 21 itself does not set a fixed statutory response time.

Why advance preparation matters

Because Article 21 sets no universal deadline, the operative timeframe comes from each individual request. Teams that already know where their documentation and logs live can respond within whatever window is specified, rather than negotiating for more time.

Prepare for Article 21 Requests Before They Arrive

Runtime logging, agent identity, and policy enforcement give compliance teams the audit trail needed to respond to competent authority requests accurately and on time.

Request a Demo