Article 14 requires that oversight measures be built into system design and implemented effectively — with a named owner, defined intervention capability, and documented limitations.
EAB structures human oversight documentation as a governance record — five evidence-backed elements, each tracked to completion, each attributed to a responsible person.
It has components — and each component must be documented separately. EAB tracks each element to a completion state with evidence and attribution.
A named individual is responsible for human oversight. The oversight owner is not a role label — it is a specific person with documented responsibility. Unowned oversight is an obligation gap.
At what points in the system's operation is human review performed? Review points are documented as structured records — not described generically. Each point has a defined trigger and a review responsibility.
The ability to intervene — to override, halt, or correct system outputs — must be documented and evidenced. It is not enough to claim it exists. EAB requires evidence that the intervention mechanism is real and accessible.
Article 14 requires that oversight limitations be known and recorded. Where oversight cannot be fully effective — due to speed, volume, or technical constraints — the limitation is documented, not hidden.
Each oversight element has its own evidence record. Training records for the oversight owner. Procedural documentation for review points. Technical records for intervention capability. Each artefact is linked and timestamped.
The oversight documentation record is finalised by supervisor approval and retained as a governance artefact. It cannot be retroactively modified to describe oversight that did not exist at the time of operation.
When a market surveillance authority asks for evidence that Article 14 oversight is in place and effective, the answer is in the governed record.
The AI System Owner completes the oversight documentation workspace — naming the responsible person, documenting review points, and describing the operational oversight arrangement. Each element is tracked separately.
Intervention capability is described and evidenced. Known limitations — where oversight cannot be fully effective — are documented explicitly. Limitations acknowledged in the record are stronger governance than silence.
Evidence is uploaded and linked to each oversight element — not collected in a folder, but attached structurally. The supervisor sees evidence in context: which element it supports, when it was uploaded, and who uploaded it.
Oversight documentation completeness is a required element of supervisor approval. The approval record captures which oversight evidence was present at sign-off. The oversight record is then sealed — immutable as a governance artefact.
Saying a human supervises the system is not enough. Article 14 requires documented oversight with evidence. EAB makes it structural.
EU-hosted · Anchored to CELEX 32024R1689
Tell us about your organization and what you’re looking to address. We’ll follow up with the relevant information.
