Compliance guide
AI literacy obligations under the EU AI Act
The EU AI Act puts a literacy obligation on two distinct groups, providers and deployers. The wording is the same, but the practical programme differs. Here is how to read the obligation for your organization.
Last updated 2026-06-15. Informational only, not legal advice.
One obligation, two audiences
Article 4 names both providers (those who develop and place AI systems on the EU market) and deployers (those who use AI systems under their authority). Each must ensure a sufficient level of AI literacy among the people on their side who interact with the systems, whether that is a developer shipping a model, an analyst configuring a tool, or an end user running prompts.
What providers need to cover
- How the system was designed, trained, and validated.
- Known limitations, failure modes, and residual risks.
- Logging, monitoring, and incident-handling obligations.
- How customer-facing instructions translate into deployer obligations.
What deployers need to cover
- What the AI system does and the decisions it influences.
- How to read confidence, uncertainty, and refusal signals.
- Data-protection, IP, and confidentiality constraints on inputs.
- Human-oversight responsibilities and escalation paths.
- How to report issues back to the provider.
A defensible baseline
A defensible baseline has three parts: a documented programme that covers the topics above for the relevant audience, an assessment that confirms each person actually absorbed the material, and a record that links the named individual to a dated outcome on a specific version of the content. The Article 4 compliance guide walks through each of these end to end.
How QLANKR Certify helps
QLANKR Certify covers a provider- and deployer-relevant AI literacy baseline, scores the assessment deterministically, and produces a publicly verifiable record per person.