Docs

Article 14 Human Oversight: engineering checklist for high-risk AI systems

As of 18 November 2026 · checked against Regulation (EU) 2024/1689 and Regulation (EU) 2026/1744

Information only, not legal advice. This page is an engineering reference, not a compliance opinion. Confirm any compliance decision with qualified counsel.

Article 14 of the EU AI Act applies to every high-risk AI system under Article 6, whether it is high-risk through an Annex I product or an Annex III use case. It does not list specific UI controls or thresholds: it lists outcomes the human-oversight design must achieve. This page maps those outcomes to concrete engineering work: where in the system you intervene, what you log, and what you hand to the deployer.

What Article 14 actually requires

The provider builds the oversight surface; the deployer staffs and uses it. Article 26(2) puts the deployer obligation on top.

Implementation options by intervention point

Three points in the inference path are typically wired for oversight:

Intervention pointMechanismLatency budget
Before invocationHuman-in-the-loop gate; system serves a recommendation only.Seconds to minutes: synchronous
During invocationConfidence-based routing, soft holds, dual-control verification (Annex III(1)(a)).Sub-second: synchronous
After invocationOverride, recall, rollback; statistical sampling for review.Minutes to days: asynchronous

Engineering checklist

Logging requirements

Article 12 (automatic logging) and Article 14 reinforce each other. The oversight log is part of the Article 12 record. The Regulation does not prescribe a schema for it; Article 12(3) sets minimum fields only for remote biometric identification systems. An example of what such a record could hold:

{
  "event_id": "ovr_01HZY3K2T9P4MQR7N5B1A8",
  "occurred_at": "2026-04-27T14:22:18.412Z",
  "system_id": "hrs-credit-scoring-v3.2.1",
  "session_id": "sess_8f2c...",
  "operator_id": "u_4419",
  "operator_role": "reviewer",
  "model_version": "credit-risk-3.2.1",
  "input_hash": "sha256:9f8c...",
  "system_output": { "decision": "deny", "score": 0.83 },
  "confidence": 0.83,
  "operator_action": "override",
  "operator_decision": { "decision": "approve" },
  "justification": "Applicant submitted updated income documentation post-scoring.",
  "dual_control_required": false,
  "stop_invoked": false
}

Retention follows Article 19 for providers and Article 26(6) for deployers: at least six months unless Union or national law requires otherwise. The Regulation does not require a storage technique. Append-only storage with a cryptographic chain is our suggestion for making later tampering visible.

Common engineering anti-patterns

What to track on the regulatory side

Article 14 itself is stable, but its operational expectations are shaped by harmonised standards (CEN/CENELEC JTC 21), AI Office guidance, and the date from which the high-risk rules apply. The Digital Omnibus moved that date to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I products, see the deadline timeline. AI Act Radar emits events on the human-oversight topic for:

Sources

→ See live updates: https://aiactradar.com

→ Subscribe to webhook: https://docs.aiactradar.com/quickstart