Home / Defined terms
18 terms
The words the register depends on
A register fails when two teams use the same word for different things. These are the terms this site uses, each defined in our words with a note on why it matters and how to use it.
Terms used across the register
| Ref | Term | Group |
|---|---|---|
| 3.1 | human oversight | Core |
| 3.2 | AI system | Core |
| 3.3 | provider | Roles |
| 3.4 | deployer | Roles |
| 3.5 | operator | Roles |
| 3.6 | affected party | People |
| 3.7 | automation bias | Behaviour |
| 3.8 | override | Control |
| 3.9 | intervention | Control |
| 3.10 | intended use | Scope |
| 3.11 | reasonably foreseeable misuse | Scope |
| 3.12 | AI system impact assessment | Assessment |
| 3.13 | AI management system | System |
| 3.14 | risk | System |
| 3.15 | event log | Evidence |
| 3.16 | transparency | Evidence |
| 3.17 | explainability | Evidence |
| 3.18 | nonconformity | Assurance |
Oversight, override, operator, affected party
If four terms are fuzzy, the register will be fuzzy. Human oversight is the activity of control and monitoring, not the existence of a committee. Override is the authority and the technical ability to set the output aside, with the decision recorded. Operator is the person at the screen who sees the output and decides. Affected party is the person whose interests can change.
Write those four into the policy first. The rest of the terms follow from them, and the unit pages use them consistently.
Where the terms come from
The public abstract of the FDIS supplies the definition of human oversight. The roles, the impact terms and the assurance terms come from the held standards and are stated in our words with the clause cited on the relevant unit. The FDIS body is not public, so no FDIS definition is quoted.