EU AI Act Article 12: event logging, line by line

Q: How do i produce an Article 12 evidence package today?

Drop the high-risk AI system's execution trace at warrant.build/demo. Warrant produces a PDF mapped to Article 12 paragraph 2 per action — a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.

01 · § 1 · TECHNICALLY ALLOW

The load-bearing verb.

High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system. Regulation (EU) 2024/1689 · Article 12(1) · 13 June 2024

The sentence does three things. It binds the system, not the operator's process. It uses shall in the operative regulatory sense. It scopes the logging horizon to the lifetime of the system, wider than any retention floor.

Placement matters. Article 12 sits inside the requirements the provider must satisfy before placing the system on the Union market. Article 16(c) reads those requirements back as a provider obligation. Article 99(4)(a) reads Article 16 back as a fineable failure. Three steps from one sentence in Article 12(1) to the EUR 15 million ceiling.

"The text is the spec. The artefact is the deliverable. Everything between is engineering."Warrant Compliance · 2026-05-07

Paragraph 2 sets out what the logging capability has to enable. Paragraph 3 attaches detail to remote biometric identification systems. The four sub-clauses, paraphrased and indexed:

§ 2(a)

Identification of situations that may result in the system presenting a risk under Article 79(1) or substantial modification under Article 3(23). IMPLICATION · the agent must emit a typed risk-classification span on every decision, not just on errors.

§ 2(b)

Facilitation of the post-market monitoring referred to in Article 72. IMPLICATION · logs must be addressable by deployment ID, model version, and time window, not just by request.

§ 2(c)

Monitoring of the operation of high-risk AI systems referred to in Article 26(5). IMPLICATION · the deployer, not just the provider, must be able to query the chain.

§ 3

For Annex III(1)(a) biometric ID systems · period of each use, the reference database checked, the matched query, identification of natural persons in verification. IMPLICATION · this is where the artefact stops being a generic event log and starts being a structured record.

02 · ANNEX III SCOPE

Scope · Annex III high-risk systems.

The article does not bind every AI system. It binds high-risk AI systems. The classification rule sits at Article 6 and Annex III.

Article 6(1) treats an AI system as high-risk when it is a safety component of a product covered by Union harmonisation legislation listed in Annex I, or is itself such a product subject to third-party conformity assessment. Paragraph 1 application begins 2027-08-02.

Article 6(2) treats an AI system as high-risk when it falls inside any Annex III use case. Annex III enumerates eight areas · biometrics, critical infrastructure, education, employment, access to essential services, law enforcement, migration and border control, and administration of justice.

The practical filter in May 2026 · does the production AI agent take a decision, produce a recommendation, or score a person in any Annex III area. If yes, Article 12 attaches on 2026-08-02. Credit-scoring agent under Annex III(5)(b). Recruitment screening under Annex III(4)(a). Risk-pricing in life and health insurance under Annex III(5)(c).

03 · AUTOMATIC RECORDING

What automatic recording means in practice.

The phrase automatic recording of events rules out three deployment patterns common in 2025 and 2026. A logging path that depends on a developer remembering to call a log function after each action does not satisfy. A redaction layer that rewrites prompts before they reach durable storage does not satisfy. A retention policy that rotates the application log every 30 days while the system stays in service for years does not satisfy.

A record that satisfies Article 12 has to be and contain specific things. It must be issued with logging enabled from the moment the system is placed on the market. It must capture every event paragraph 2 makes relevant, automatically, over the lifetime of the system. And it must be surfaceable to a national competent authority on request under Article 21, in readable form.

ISSUE

Provider places the system on the Union market or puts it into service. Article 16(c) attaches Article 12 from this moment.

OPERATE

Deployer uses the system per its instructions. Article 26(5) requires the deployer to keep automatically generated logs to the extent under their control.

LOG

Every event relevant to risk identification, post-market monitoring under Article 72, and operational oversight under Article 26(5) is captured automatically.

AUDIT

On request from the national competent authority under Article 21, the provider produces the logs in readable form.

04 · RETENTION

Retention requirements.

Article 19(1) sets the floor. The provider keeps logs automatically generated by the high-risk AI system for a period appropriate to the intended purpose, of at least six months, unless provided otherwise under applicable Union or national law, in particular Union law on the protection of personal data.

Sectoral law pushes actual retention longer. MiFID II Article 16(7) requires five years for orders and decisions to deal. MDR Article 10(8) requires ten years, fifteen for implantable devices. A six-month rolling window destroyed twelve months ago is not an answer to a regulator's request twelve months and one day after the event.

05 · SUBSTANTIAL MODIFICATION

Substantial modifications and what triggers fresh logging.

Article 3(23) defines substantial modification as a change after placing on the market that is not foreseen in the initial conformity assessment, and as a result of which compliance with Section 2 of Chapter III is affected, or that modifies the intended purpose.

The trigger is not retraining alone. The trigger is whether the change pushes the system outside the conformity assessment. A model-version bump that swaps the foundation model from one frontier provider to another is, on most readings, a substantial modification. A prompt-template change that broadens the intended purpose from internal classification to external customer-facing decisions is one.

Article 25(1)(c) treats any person who makes a substantial modification as a provider, with all Article 16 obligations, including a fresh Article 12 logging perimeter and a fresh Article 19 retention clock.

06 · ART. 99 PENALTIES

Penalty exposure under Article 99(4).

The penalty regime sits in Article 99. The structure is a three-tier ceiling. Paragraph 3 covers prohibited practices under Article 5 at EUR 35 million or 7 percent. Paragraph 4 covers operator obligations including Article 16, which incorporates Article 12, at EUR 15 million or 3 percent. Paragraph 5 covers misleading information to notified bodies.

An operator running an Annex III system without Article 12 logging is exposed to the 3 percent ceiling from the day the system is in service after 2026-08-02. National competent authorities under Article 70 set the actual fine within that ceiling, taking into account the criteria in Article 99(7). Multi-Member-State deployments can face parallel proceedings.

07 · FIELD MAPPING

How Article 12 sub-clauses map to evidence fields.

12(1)

Automatic recording over the lifetime of the system. FIELD · trace.actions[*] (per-action subject, inputs, outputs, ts) rendered as a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.

12(2)(a)

Identifying risk situations under Article 79(1). FIELD · trace.actions[*].risk_assessment (deviation_from_intended_purpose, drift_indicators, modification_flag).

12(2)(b)

Facilitating post-market monitoring under Article 72. FIELD · trace.actions[*].outcome (post_market_observable, deployer_reportable_event) plus per-trace post-market roll-up.

12(2)(c)

Monitoring under Article 26(5). FIELD · trace.actions[*].oversight (reviewer_id, review_outcome, intervention_record, justification).

16(c)

Provider obligation, read with Article 99(4) penalty exposure. FIELD · per-trace evidence package — a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.

Sample EU evidence package · Warrant registerINDEPENDENTLY VERIFIABLE WITHOUT CONTACTING WARRANT

→ /v/7de85ceaeac42a47

08 · FAQ

Questions a compliance officer asks first.

Does Article 12 apply to a provider established outside the European Union?

Yes. Article 2(1)(a) extends the regulation to providers placing high-risk AI systems on the Union market or putting them into service in the Union, irrespective of where the provider is established. Article 22 requires the non-Union provider to designate an authorised representative in the Union before the system is made available.

What is the difference between Article 12 logs and the technical documentation under Article 11?

Article 11 governs static technical documentation drawn up before the system is placed on the market and lodged for conformity assessment under Article 43. Article 12 governs runtime event logs generated automatically over the lifetime of the system. National competent authorities read both under Article 21.

How long must Article 12 logs be retained?

Article 19(1) sets a floor of at least six months, appropriate to the intended purpose, unless other Union or national law requires longer. Sectoral law often does. MiFID II runs five to seven years. MDR runs ten to fifteen years for implantable devices.

Are general-purpose AI models in scope for Article 12?

Article 12 targets high-risk AI systems. General-purpose AI model providers carry their own record-keeping under Articles 53 and 55, applicable from 2025-08-02. A GPAI model used inside a high-risk system is pulled into the Article 12 perimeter through the integrating provider.

Does a substantial modification reset any clocks under Article 12?

Yes. Article 25(1)(c) treats the modifier as a provider of the modified system. A fresh Article 12 logging perimeter, a fresh Article 43 conformity assessment, and a fresh Article 19 retention clock all start.

What is the maximum financial penalty for non-compliance with Article 12?

Article 16(c) routes Article 12 through provider obligations, and Article 99(4) applies. The fine is up to EUR 15,000,000 or, if the offender is an undertaking, up to 3 percent of total worldwide annual turnover for the preceding financial year, whichever is higher.

How do Article 12 logs interact with the GDPR right of access?

Recital 70 confirms the AI Act applies without prejudice to Regulation (EU) 2016/679. If a log contains personal data, GDPR Article 15 access runs against the controller. Pseudonymisation of subject identifiers in the log is the operative pattern.

How do i produce an Article 12 evidence package today?

Drop the system's execution trace at warrant.build/demo. Warrant produces a PDF mapped to Article 12 paragraph 2 per action — a record mapped to a specific EU AI Act obligation, independently verifiable without contacting Warrant.

09 · READ THE SOURCE

Read the source directly.

Authored by Warrant Compliance, the regulatory-analysis function at Warrant. [email protected]. Editorial commentary on regulatory text. Not legal advice. The verbatim quotation of Article 12(1) reflects the official English-language text of Regulation (EU) 2024/1689 as published in the Official Journal of the European Union on 12 July 2024.