Scope & reliance: 🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Do not enter real personal data or real log contents: use synthetic or anonymised field names only. Rules cited from clause snapshot EUAIAct-Art12-Art19-logging-2026-09-02 (refs A1-A9), retrieved verbatim 2026-09-02 from the EC AI Act Service Desk (Regulation (EU) 2024/1689, official version of 13 June 2024). Dated observation: Annex III high-risk obligations have applied since 2026-08-02 (Art 113(2): "It shall apply from 2 August 2026."); Annex I product-safety high-risk systems (Art 6(1)) fall under the 2027-08-02 date and are out of this tool's gate. Deterministic logic · no inference · zero PII · runs offline · CC BY 4.0.

Draft-standard status (stated honestly): the Article 12 technical standard is still TWO DRAFTS as of 2026-09-02: prEN 18229-1 "AI trustworthiness framework - Part 1: Logging, transparency and human oversight" (CEN/CENELEC JTC 21) and ISO/IEC 24970 "Artificial intelligence - AI system logging" (ISO/IEC JTC 1/SC 42, DIS 2025 at FDIS ballot). Their clause text is paywalled and was not publicly retrievable on 2026-09-02; only catalog titles, stages and (for 24970) a public scope line were. This tool therefore maps against the Regulation's own text (Art 12, Art 19, Art 113) alone and derives no behavioural rule from either draft.

Scope Gate (Art 12(1) - clause A1)

System class as declared The tool does not classify your system. Whether the system is high-risk under Annex III is a declared fact; if in doubt, take professional advice.

The system technically allows automatic recording of events (logs) (Art 12(1))

Logging covers the entire lifetime of the system (Art 12(1))

Events are recorded automatically, at the latest when each event occurs (Art 12(2) chapeau)

Art 12(2) Event-Category Coverage (clauses A3-A5)

(a) Schema records events identifying situations that may present a risk within the meaning of Art 79(1), or a substantial modification under Art 43(4)

Typical fields: risk_flag, incident_ref, anomaly, model_version, threshold_breach, drift_signal.

(b) Schema facilitates post-market monitoring under Art 72

Typical fields: performance_metric, accuracy, precision, recall, periodic_stat, evaluation_window.

(c) Schema supports monitoring of the operation of the system as covered by Art 26(5) (deployer-side operational monitoring)

Typical fields: user_action, operator_id, override_event, session_ref, decision_context, instruction.

Your Log Schema - free structure input (deterministic cross-check aid)

Paste synthetic field names, a JSON sample or free-form lines. The tool runs a fixed, deterministic keyword map over the text and shows which Art 12(2) category each recognised field most likely serves. The mapping is a cross-check aid only - the checkboxes above remain the declared source of truth, and nothing is sent anywhere.

Art 12(3) Minimum Elements (clauses A6-A7)

The system is a high-risk remote biometric identification system per Annex III point 1(a) (Art 12(3) gate)

(a) Start and end date and time of each use of the system are recorded

(b) The reference database against which input data was checked is recorded

(d) The natural persons involved in verifying the results (Art 14(5)) are identified

Art 12(3) binds only the Annex III point 1(a) systems. Leave the gate unchecked for any other system class.

Retention (Art 19 - clause A8)

Declared log retention period, months

Applicable Union or national law provides for a different period (Art 19(1) exception - declared fact)

The provider is a financial institution within the meaning of Regulation (EU) No 575/2013 Art 4(1) point (25), or otherwise subject to internal-governance requirements (Art 19(2))

Logs are kept as part of the documentation kept under those internal-governance arrangements (Art 19(2))

EU AI Act Article 12 Log Schema Checker