Evidence is what turns "we think we covered this" into something you can actually show later.
1. Why proof matters
Article 4 is about taking measures to ensure AI literacy. If you ever need to explain what you did, proof helps. That can matter in internal governance, customer questionnaires, procurement reviews, or regulator questions.
Most SMEs do not need a huge evidence architecture. They need a clean record that can be reviewed quickly.
2. What the record should contain
| Field | Why it is useful |
|---|---|
| Organisation name | Shows which legal or operating entity the record belongs to. |
| Name or identifier of learner | Shows who actually completed the training. |
| Role track or context | Shows that training matched real use rather than being generic. |
| Completion date | Shows when the measure took place. |
| Curriculum scope | Shows what was actually covered. |
| Attestation or assessment note | Strengthens the case that the training was more than passive exposure. |
3. Why PDF is practical
A PDF training record is not legally magical. It is just practical.
- easy to archive
- easy to share internally
- easy to attach to diligence or audit requests
- harder to misread than a loose collection of screenshots
If the PDF also includes a curriculum summary and a clear export date, it becomes more useful later.
4. What not to over-engineer
- Do not build an enterprise LMS rollout just to solve one obligation.
- Do not collect more personal data than you need.
- Do not create proof that nobody can review quickly.
- Do not keep only a policy PDF and call that evidence.
The right proof for most SMEs is lean, role-aware, and easy to regenerate when needed.