Author and editorial responsibility
Tim Jamboula, Founder of Corporathon. Last reviewed 24 August 2026. Client-specific claims are approved before publication. This post is not legal advice.
AI summary (citable)
Since 2 February 2025, Article 4 of the AI Regulation requires sufficient AI literacy for everyone who operates or uses AI systems, by role and context. AI training can build and document that competence but does not replace an official certification. What matters is a traceable record: who, which role, which content, which result. A hackathon delivers that record especially tangibly through a used artifact.
1. The real question behind Article 4
"Do we satisfy the EU AI Act with an AI training" is the wrong expectation. Article 4 does not require a specific training but sufficient competence, appropriate to role and context. The right question is: can we evidence, for each relevant role, that the competence exists? Training is one path there, the record is the goal.
The EU AI Act does not ask for a certificate but for real, role-appropriate competence. It becomes evidenced through application, not attendance. – Tim Jamboula, Founder of Corporathon
2. What Article 4 requires (and what not)
| Aspect | What applies | Common misunderstanding |
|---|---|---|
| Applicability | since 2 February 2025, for providers and deployers | it applies now, not only later |
| Standard | sufficient competence, by role and context | one uniform certificate for all is not enough |
| Record | traceable documentation of measures | an attendance list alone evidences no competence |
| Responsibility | rests with the company | an external provider guarantees no compliance |
| Certificate | there is no mandated official document | a course slip is not an official record |
3. The documentation frame in five fields
A robust record holds five fields per measure: who (names or roles tied to AI use), which role and context (deployer, user, department, system risk class), which content (topics, tools, limits and risks covered), which result (knowledge for training, a used artifact for a hackathon), and when and by whom (date, format, responsibles and any external provider). These five fields turn an attendance list into a traceable competence record.
4. Decision framework: which record for which role
The closer a role is to productive AI use, the deeper the record must reach. For deployers of higher-risk systems, an awareness talk is not enough; documented application counts. Positions are schematic and not a legal classification.
5. Honest cost logic of compliance
Compliance cost is rarely the course price: mapping (who uses which systems in which role), depth per role (a uniform course is cheap but rarely appropriate), documentation (maintaining the record costs time but saves far more in a review), and refresh (AI literacy is not a one-off state). Corporathon deliberately shows no fixed prices yet.
6. A worked risk model (illustrative)
Illustrative model, not a legal assessment. Assume a one-off investment in a role-appropriate competence program with clean documentation: 25 internal hours of preparation, about 1,500 EUR of internal effort at a 60 EUR rate, plus the measure itself. Against this stands the risk of unclear competence: unproven records in a review, rushed rework, possible sanction risk under the Regulation. The modelled comparison shows an early, documented effort usually sits well below the cost of late, hectic back-documentation. Numbers are an order-of-magnitude assumption, not a guarantee or legal advice.
7. Training, hackathon or both as evidence
Training documents transferred knowledge and suits broad basic competence. A hackathon documents practical application through a used artifact and suits roles that use AI productively. For an appropriate overall program, the combination is often sensible: broad training as a base, a hackathon as deep evidence where productive work happens. Neither is an official certificate.
8. What to do next
First map who uses which AI systems in which role. Set the required depth per role and document along the five fields. For productive roles, a hackathon is the most tangible record because it creates application, one week from first contact to a used artifact. Assess the adequacy of the overall program yourself or with legal advice.
CTA: Book a discovery call → https://cal.com/jamboula/ai-hackathon
Related terms
EU AI Act · AI literacy · AI hackathon
FAQ
Does AI training automatically satisfy the EU AI Act? No. Article 4 requires sufficient, role- and context-appropriate competence and a traceable record, not a specific certificate. Training can contribute; the company owns the adequacy of the overall program.
Since when does Article 4 apply? Since 2 February 2025. The duty of sufficient AI literacy affects providers and deployers of AI systems and applies already, not only in the future.
Is an attendance list enough as a record? Alone it evidences no competence. A record along five fields is sensible: who, which role and context, which content, which result, when and by whom.
Is a hackathon a competence record? It documents practical application especially tangibly through a used artifact. That is a strong building block, but not an official certificate and not automatic compliance.
Rechtlicher Hinweis / Legal note: Eine KI-Schulung oder ein Hackathon können KI-Kompetenzmaßnahmen nach Artikel 4 dokumentieren, sind aber kein behördlich vorgeschriebenes Zertifikat und garantieren nicht automatisch die Erfüllung von Artikel 4. Dieser Beitrag ersetzt keine Rechtsberatung. / An AI training or hackathon can document AI literacy measures under Article 4, but are not an officially mandated certificate and do not automatically guarantee compliance with Article 4. This post is not a substitute for legal advice.