Law / European Union

AI Act, Articles 74(12) and (13) and 77 (market surveillance access to documentation, data sets and source code, and the access of authorities protecting fundamental rights)

Regulation (EU) 2024/1689, Article 74(12) and (13), and Article 77

An AI governance rule binding public and private bodies.

Private right of action
No
How the hook was established
express
What makes it apply
Market targeting, Operator establishment, Place of effect
Obligation class
Governance
Audit expectation
on_request
Who audits it
Regulator

As of .

What it requires

  • This duty takes effect on for a high-risk AI system classified under Article 6(2) and Annex III, and on for one classified under Article 6(1) and Annex I (Article 113, third paragraph, point (c), as replaced by Regulation (EU) 2026/1744), other than a system related to a product covered by the Union harmonisation legislation listed in Section B of Annex I, to which, under Article 2(2), only Article 6(1), Article 60a and Articles 102 to 112 apply, and Articles 57, 58 and 59 apply only in so far as the requirements for high-risk AI systems under this Regulation have been integrated in that Union harmonisation legislation; a system already placed on the market or put into service before its date is reached only once its design changes significantly, or by if it is intended for use by public authorities.
  • If you are the provider of a high-risk AI system, grant the market surveillance authorities full access to the documentation and to the training, validation and testing data sets used for the development of the system, where relevant and limited to what is necessary for their tasks, including, where appropriate and subject to security safeguards, through application programming interfaces or other technical means enabling remote access (Article 74(12)); this is without prejudice to the powers provided for under Regulation (EU) 2019/1020.
  • Give a market surveillance authority access to the source code of your high-risk AI system upon its reasoned request, but only when access to the source code is necessary to assess the system's conformity with the requirements of Chapter III, Section 2 and testing or auditing procedures and verifications based on the data and documentation you provided have been exhausted or proved insufficient (Article 74(13)).
  • If you are the provider or deployer of an AI system, a market surveillance authority may request from you the information or documentation that a national public authority or body protecting fundamental rights has requested from it under Article 77(1); Article 77(1a) has the authority obtain that information or documentation, including by requesting it from the provider or the deployer, where necessary and without undue delay.

These lines are LexLint's reading of the law's text, as of .

Who enforces it

Settledness

As of
Open questions
When is testing or auditing based on the data and documentation a provider supplied 'exhausted or proved insufficient' under Article 74(13), so that a market surveillance authority may ask for the source code?

What it makes you log

Who may demand the log

Regulator

Logging duty

Article 74(12) gives market surveillance authorities full access to the documentation and to the training, validation and testing data sets used for the development of a high-risk AI system, which a provider cannot open unless it has kept them. The Article names no log, sets no retention period and says nothing of what the documentation must contain; those are the subjects of Articles 11, 12, 18 and 19. Article 74(13) adds access to the source code on a reasoned request.

Kind
Implicit
As of
Provision
Article 74(12)
Trigger
high_risk_systems

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Where relevant and limited to what is necessary to fulfil their tasks, and without prejudice to the powers under Regulation (EU) 2019/1020, market surveillance authorities must be granted full access by providers to the documentation and to the training, validation and testing data sets used for the development of high-risk AI systems, including, where appropriate and subject to security safeguards, through application programming interfaces or other technical means enabling remote access.

Market surveillance authorities must be granted access to the source code of a high-risk AI system upon a reasoned request, and only when access to the source code is necessary to assess the system's conformity with the requirements of Chapter III, Section 2 and testing or auditing procedures and verifications based on the data and documentation the provider supplied have been exhausted or proved insufficient.

Any information or documentation a market surveillance authority obtains under Article 74 is treated in accordance with the confidentiality obligations of Article 78.

Under Article 77(1), as replaced by Regulation (EU) 2026/1744, national public authorities or bodies that supervise or enforce the respect of obligations under Union law protecting fundamental rights, including the right to non-discrimination, have the power to request and access from the relevant market surveillance authority any information or documentation created or maintained pursuant to the Regulation, in accessible language and machine-readable format by electronic means, where access is necessary for effectively fulfilling their mandates within the limits of their jurisdiction.

Under Article 77(1a), inserted by Regulation (EU) 2026/1744, the market surveillance authority must grant the public authority or body referred to in Article 77(1) access to such information or documentation, including by requesting it from the provider or the deployer, where necessary and without undue delay.

Where the documentation is insufficient to ascertain whether an infringement of obligations under Union law protecting fundamental rights has occurred, the public authority or body referred to in Article 77(1) may make a reasoned request to the market surveillance authority to organise testing of the high-risk AI system through technical means, which the market surveillance authority must organise with the close involvement of the requesting authority or body within a reasonable time.

Article 74(12) and (13) and Article 77 concern high-risk AI systems, and the Digital Omnibus on AI (Regulation (EU) 2026/1744) moved Chapter III, Sections 1 to 3, which hold the Article 6 rules that classify a system as high-risk, to for a system classified under Article 6(2) and Annex III and to for one classified under Article 6(1) and Annex I. The Omnibus also rewrote Article 111(2) so that the Regulation reaches the operators of a high-risk AI system placed on the market or put into service before the date Chapter III applies only if, from that date, the system's design changes significantly, and the providers and deployers of a system intended for use by public authorities must take the necessary steps to comply by .

Article 74(12) and (13) and Article 77 do not apply to a high-risk AI system related to a product covered by the Union harmonisation legislation listed in Section B of Annex I, to which, under Article 2(2), only Article 6(1), Article 60a and Articles 102 to 112 apply, and Articles 57, 58 and 59 apply only in so far as the requirements for high-risk AI systems under this Regulation have been integrated in that Union harmonisation legislation.

Articles 74 and 77 sit in Chapter IX, to which Article 113 gives no date of its own, so they apply to the authorities from the Regulation's general application date of .

When LexLint raises it

When your app profile says your app makes high-risk automated decisions or processes biometric data.

Back to the example  ·  Lint your app