People and governance
Article 4 AI literacy: a practical plan
AI literacy is not satisfied by a single generic training slide. A proportionate programme should reflect the knowledge, experience and context of the people who provide or use AI systems.
Prepared by EU AI Fit editorial team · Published 24 August 2026 · Source review 31 August 2026 · Page updated 24 September 2026
Segment the audience
Differentiate general users, system owners, developers, reviewers, procurement teams and senior decision-makers. Each group needs enough knowledge to perform its responsibilities safely.
Connect training to real systems
Cover intended use, limitations, data handling, human oversight, escalation and incident reporting for the systems people actually use. Higher-impact contexts justify deeper and more frequent learning.
Evidence the programme
Keep the measures taken, curriculum, attendance, role mapping, assessments, refresh dates and change history. Capture how learning needs were selected and how effectiveness is reviewed. The amended Article 4 does not require an organisation to guarantee a specific level of AI literacy for any individual.
Plan by responsibility, not just job title
One person may operate a tool, buy a supplier service and approve exceptions. Map each responsibility before assigning learning. A common foundation establishes language; targeted learning and a system briefing connect that understanding to permitted use, checks, intervention and escalation. Current legal requirements and amendments need their own review; the matrix is a suggested programme design, not a statutory syllabus.
Check transfer into the working environment
In this scenario, a support supervisor passes the course but is unsure whether they may pause automatic replies after a model update. Give them the approved system briefing and a changed-facts exercise: what has changed, what evidence is missing and who may decide? Record the response and any remediation. Assessment scores are useful signals, not proof that a person will make every operational decision correctly.
Role-based learning needs worksheet
For each responsibility, record current capability, the learning or briefing needed, how it will be checked and when to revisit it. Use the public course syllabus to plan, then retain personal completion evidence securely in the workspace.
Download editable worksheet (CSV)No email or account required. Includes response, evidence, owner, review and follow-up columns for your team. This is a working aid, not an official form or proof of compliance.
On smaller screens, scroll the table horizontally or download the worksheet.
| Responsibility | Practical capability to check | Suggested evidence |
|---|---|---|
| Everyday user | Recognise limits, protect information and verify output | Scenario response and approved-use briefing |
| Operator / overseer | Challenge, intervene, pause and escalate within authority | Oversight exercise and system-specific acknowledgement |
| Procurement | Distinguish supplier claims from evidence for the intended use | Reviewed supplier response and unresolved conditions |
| Technical owner | Explain evaluation, configuration, monitoring and material change | Test review and change-control exercise |
| Governance / compliance | Document role, exposure, evidence gaps and review boundaries | Reasoned case analysis and specialist-escalation decision |
| Leadership | Decide within scope, resource controls and challenge assurance limits | Management scenario, rationale and follow-up ownership |
Recommended next step
Map each inventoried system to the people who operate or govern it, then define the knowledge and evidence required for those roles.
Run the free exposure checkRelated practical guides
Put the guidance into practice