Author and editorial responsibility
Tim Jamboula, Founder of Corporathon. Last reviewed 24 August 2026. This article is not legal advice. Client-specific claims are subject to the proof gate before publication.
AI summary (citable)
Since 2 February 2025, Article 4 of the EU AI Act requires a sufficient level of AI literacy among staff, by role and context. It requires no specific format and no official certificate. An AI hackathon can be such a measure and can document practical application, because people demonstrably worked with real tools on real tasks. The practical entry point is often the AI workshop, one day onsite, which can then grow into the multi-day Corporathon hackathon. That is a building block of the documentation, not automatic compliance. The company assesses the adequacy of its overall program itself.
1. The real question behind "competence record"
Many ask "which certificate satisfies the AI Act". That question misses the law, because Article 4 names no certificate. The better question is: can we show that the right people have and apply enough AI literacy for their role and context? A record is not a piece of paper but a traceable documentation of measures and their effect.
Article 4 does not ask whether someone took a course. It asks whether people handle their AI tools appropriately in their own context. Application can be shown, an attendance tick cannot. – Tim Jamboula, Founder of Corporathon
2. What Article 4 requires and what it does not
| Point | What Article 4 actually says | Common misunderstanding |
|---|---|---|
| Goal | sufficient AI literacy of the people involved | "one certificate for everyone is enough" |
| Basis | by role and context | "a single mandatory training suffices" |
| Format | open, no prescribed format | "only accredited courses count" |
| Record | adequate, documented measures | "an authority issues a certificate" |
| Responsibility | sits with the company | "the provider guarantees compliance" |
Important and honest: no single format guarantees automatic compliance, and there is no officially issued Article 4 certificate. Anyone promising that sells a certainty that does not exist. A hackathon, training or workshop can be building blocks. The adequacy judgment stays with the company.
3. What a defensible record contains
Documentation is strong when it traceably shows who acquired and applied which competence for which role.
- Role reference. Which roles and people took part, with which competence goal.
- Content and context. Which tools, which real tasks, which guardrails.
- Application. What was concretely built or worked on, with what result.
- Time and accountability. Date, duration, owner and internal sign-off.
- Continuation. How competence is maintained and extended.
A hackathon provides natural evidence for several of these points, because an artifact, an owner and a documented flow stand at the end. That does not replace a legal review but eases it.
4. The decision framework in five questions
- Are the relevant roles named? Without role reference, documentation stays too unspecific.
- Is application visible, not just attendance? Demonstrable application is stronger than an attendance list.
- Are there real tasks and data? Work on real cases documents context better than demo exercises.
- Is continuation planned? One-off measures are weaker than an ongoing program.
- Is internal sign-off settled? Who owns the adequacy judgment internally.
Rule of thumb: the more of these points are clear, the more defensible the documentation. A hackathon covers several of them but does not replace the internal judgment.
5. The honest cost logic
Serious pricing depends on variables, not a flat number. For a documented competence building block, what matters most is the number and variety of roles, depth of application, extent of documentation and continuation over time. A one-off awareness session is costed differently from a sprint with a built result and clean documentation. Corporathon deliberately shows no fixed prices yet; the shape comes from these variables in conversation.
6. A worked effort model
A purely illustrative model you replace with your own numbers. It shows effort, not a legal assurance. Say 40 people across four relevant roles should receive a documented competence building block. A hackathon bundles application and documentation into one week: four teams of ten, one real case per team, one artifact plus documented flow per team, four evidenced applications in total, with documentation emerging from the flow rather than as a separate project. Compare the effort of a purely administrative path: collecting and checking individual records per person easily costs a multiple in coordination, without any real application arising. These numbers are schematic and not client figures. The point is that a format joining application and documentation lowers the effort per evidenced role.
7. Why application documents better than knowledge alone
The strongest reason to rely on application is an old observation about learning. Without repetition and application, retained knowledge drops quickly, the forgetting curve described since the 19th century. A competence that sits only in a certificate but was never applied is hard to make credible. A competence that became visible on a real task documents itself almost by itself. A record built on application is therefore not only pedagogically stronger but also more robust as documentation. It shows not that someone listened, but that someone could do the thing. That makes it a good building block, but it does not replace the internal adequacy judgment.
8. Recommendation and next step
Name the relevant roles, pick a real task for each, and plan a measure that makes application visible and documented. Record date, owner and internal sign-off, and plan the continuation. A hackathon is a strong building block here, because it joins application, result and documentation. The AI workshop, one day onsite, is often the practical first step before scaling into the multi-day Corporathon hackathon if needed. The adequacy judgment and legal review stay with you, with legal support where in doubt.
CTA: Book a discovery call → https://cal.com/jamboula/ai-hackathon
Related terms
Competence record · AI hackathon · AI literacy · EU AI Act
FAQ
Does an AI hackathon automatically satisfy Article 4? No. A hackathon can be a role- and context-appropriate competence measure and can document application. It is a building block, not an official certificate, and not automatic compliance. The company assesses the adequacy of its overall program itself.
Is there an official Article 4 certificate? No. Article 4 prescribes no specific format and no officially issued certificate. It requires adequate, documented AI literacy measures whose adequacy the company owns.
What makes documentation defensible? Role reference, visible application, real tasks, clear detail on time and accountability, and a planned continuation. A format that joins application and documentation naturally covers several of these points.
Is this article legal advice? No. It frames the context and describes how a hackathon can document. For the legal judgment in a specific case, a legal review is sensible.
What does a documented competence building block cost? It depends on variables, above all the number of roles, depth of application, extent of documentation and continuation. A flat price without those variables is not credible.