VeritomeHelp Centre
/
Browse documentation
Using Veritome

Human oversight: Art. 14 measures and the deployer's Art. 26(2) duties

The Oversight domain of the Obligations register: who can intervene in each high-risk system, how the stop mechanism works, how automation bias is countered — the provider designs the measures, the deployer assigns and equips the people.

Updated Veritome documentation

Obligations, filtered to the Oversight domain, is the portfolio view of Article 14 (providers: design the system so that natural persons can effectively oversee it) and Article 26(2) (deployers: assign human oversight to people who have the necessary competence, training and authority, and give them the support they need).

What good looks like

For each high-risk system, the oversight record answers four questions:

  1. Who — named roles, not "the team", with the competence, training and authority to oversee the system.
  2. What they can see — the information that lets an overseer understand what the system is doing: confidence signals, logs, the instructions for use.
  3. What they can do — decide not to use the output, override or reverse a decision, intervene, or stop the system through a stop button or similar procedure (Art. 14(4)). The stop mechanism has to be real and reachable.
  4. Automation bias — the measures that keep people from over-relying on the output (Art. 14(4)(b)): sampling reviews, second-opinion thresholds, deliberate friction on high-impact decisions.

Provider vs deployer

The engine gives each side its own obligations. As a provider, the oversight measures are a design deliverable — built into the system or identified for the deployer to implement, described in the technical documentation and the instructions for use (see Suppliers: the value chain, agreements and the IFU handoff). As a deployer, your Art. 26(2) duties are operational: assign the people, train them, and keep the assignment current when staff change. Where the deployer is an employer, Art. 26(7) adds informing workers' representatives and affected workers before putting the system into use.

Open a row to work the checklist, attach evidence (the oversight procedure, training records, the runbook for the stop mechanism) and assign an owner.

  • The six-phase compliance journey — oversight work lands in the Implement phase.
  • AI literacy: satisfying Article 4 — Art. 4 training is what gives "competent people" a dated record behind it.