010 Coding Collective

010 Coding Collective

AI literacy: what Article 4 of the AI Act asks after the Digital Omnibus

Every organisation that uses AI has to work on its staff's AI literacy under Article 4 of the EU AI Act. What the Digital Omnibus changed in 2026, and how to handle it in practice.

AI AI Act AI Literacy Compliance Team training AI Policy

An obligation without a manual

Since February 2025, every organisation that uses AI must take measures on AI literacy. The law does not say how, and the Digital Omnibus rewrote the article in 2026.

Know who uses what, and for what

Start with a list of the AI tools in your organisation and the people who use them. Give each role the knowledge that fits how it uses AI, and record what you did.

A team that uses AI well

AI literacy is less a box to tick for a regulator than a team that knows what a model can do, where it fails, and who answers for the result.

The short answer

AI literacy is the knowledge and skill to use AI with judgement: knowing what a system can do, where it gets things wrong, and what those mistakes cost. Article 4 of the EU AI Act requires every organisation that builds or uses AI to work on it with its staff. It has applied since 2 February 2025, to everyone, including a small business whose only AI is ChatGPT or Copilot.

In July 2026 the Digital Omnibus rewrote Article 4. Organisations now have to take measures that support the development of AI literacy among their staff. The old promise of a sufficient level for every employee is gone. The duty is lighter, and it still applies.

What Article 4 asks of you

The AI Act distinguishes providers, who build an AI system or put it on the market, from deployers, who use one in their work. Article 4 covers both. Whether you build your own AI agent or run customer service through a chatbot, it applies to you.

The law prescribes no course, exam or certificate. It asks you to take three things into account:

1

Who uses the AI

The technical knowledge, experience and training of the people working with the system. A developer needs different knowledge than someone in accounts payable.

2

What it is used for

The context the AI runs in. Summarising internal notes asks less of people than a system that screens job applicants or advises customers.

3

Who it affects

The people or groups on the receiving end of the output. The more it affects customers, applicants or citizens, the more your team needs to understand what happens inside.

So the law treats AI literacy as tailored work. One standard course that everyone sits through in the same form is a weak answer to Article 4.

What the Digital Omnibus changed

The Digital Omnibus on AI is an EU regulation that simplifies parts of the AI Act and delays others. It was published on 24 July 2026 and took effect a few days later. For Article 4 it changed one sentence, and that sentence matters.

Original text After the Omnibus
What you must do Take measures to ensure, to their best extent, a sufficient level of AI literacy of their staff. Take measures to support the development of AI literacy of their staff.
What it hinges on An outcome: every employee at a sufficient level. An effort: visible, role-appropriate work on knowledge.
Who it covers All providers and deployers of AI systems. Unchanged: all providers and deployers of AI systems.
Since when 2 February 2025. Unchanged: the duty never paused.

The shift reads like legal fine print, but it is practical. You no longer have to prove that each person reached a given level. You do have to show that you work on it seriously and in proportion to how AI is used.

After the Omnibus, Article 4 does not ask for a diploma per employee. It asks for an organisation that can show its people know what they are doing when they use AI.

The Omnibus also pushed back the high-risk rules: to December 2027 for standalone systems and to August 2028 for AI built into regulated products. That delay does not touch Article 4. AI literacy was already required, and it stays required.

Enforcement and fines

Article 4 carries no fine of its own. The AI Act does not list it among the breaches with a set penalty. That does not make it optional. National market surveillance authorities can enforce from August 2026.

What matters more is what happens when something goes wrong. If an employee acts on AI output that turns out to be false, and your organisation did nothing about knowledge or rules of use, that counts when a regulator or court looks at the incident. AI literacy is then the difference between a mistake and negligence.

How to handle AI literacy in practice

You do not need to wait for guidance or a certification scheme. These steps give you something that works and that you can show:

1

List the AI your organisation uses

Which tools are in use, officially and unofficially? ChatGPT, Copilot, AI inside your CRM, a chatbot on the website, an in-house agent. Ask around: most AI use lives in browser tabs, not on a software inventory.

2

Tie each tool to roles and risk

Write down who uses each tool and for what. A tool that rewrites emails asks less than one that processes customer data or prepares decisions.

3

Give each role the knowledge it needs

Everyone should know that a model can be confidently wrong and that confidential data does not go into a public tool. People who act on AI output need to know how to check it. People who build AI need to know how to test and monitor it.

4

Agree on rules of use

A short AI policy: which tools are allowed, what data may and may not go in, and who answers for what happens with the output. One page people actually read beats twenty nobody opens.

5

Record what you did

Which sessions took place, who attended and which rules apply. After the Omnibus, that record is exactly what a regulator will want to see.

6

Revisit it when things change

A new tool, a new role or a new use case raises new questions. AI literacy is not a one-off training, it grows with how you use AI.

What AI literacy means for a team that builds with AI

We build software with AI and build AI applications for clients. For a development team, AI literacy is more concrete than for the rest of the organisation: it means knowing where models are weak and shaping the work around that.

A developer who accepts AI-written code without reading it is not AI literate, however fast they ship. They need to spot when a model invents functions or packages, when error handling hides failures, and when a change is too large to review. We describe what that looks like in code in AI slop: what it is and how to spot it.

If you build AI applications yourself, such as an agent that handles email or reads documents, the bar moves again. The team also needs to know how to test such a system, where a human stays in the loop, and how to notice when it drifts in production. How to design that human oversight is the topic of UX for AI: keeping humans in control.

For a development team, AI literacy is not a course about AI. It is a way of working in which every line that ships has been read by someone.

Conclusion: lighter, not less important

Since February 2025, Article 4 of the AI Act has required every organisation that uses AI to work on its staff’s AI literacy. The Digital Omnibus softened that in 2026, from a guaranteed level to demonstrable effort that fits who uses AI and for what. List your AI use, give each role the knowledge it needs, agree on rules and keep a record. That covers the law, and more to the point, it keeps your team from using AI in ways it later regrets.

This article is a practical explanation, not legal advice. For questions about your own situation, talk to a lawyer who knows the AI Act.

Frequently Asked Questions

What is AI literacy?

AI literacy is the skill, knowledge and understanding needed to use AI with judgement. You know what an AI system can do, where it makes mistakes and what those mistakes can mean for you and others. The AI Act uses the term in Article 4.

Is AI literacy mandatory?

Yes. Since 2 February 2025, every organisation that builds or uses AI systems must take measures on the AI literacy of its staff. Since the Digital Omnibus of July 2026, those are measures that support the development of AI literacy, rather than a guaranteed level per employee.

Does Article 4 apply to small businesses?

Yes. Article 4 applies to all providers and deployers of AI systems, whatever the size of the organisation or the risk of the system. If your team uses ChatGPT, Copilot or any other AI tool for work, it applies to you. What counts as reasonable depends on how and why you use AI.

What did the Digital Omnibus change?

The Digital Omnibus on AI rewrote Article 4. The old text required measures to ensure, to the best extent, a sufficient level of AI literacy. The new text requires measures that support its development, which turns the duty into an obligation of effort. The Omnibus also delayed the high-risk rules, but that does not affect Article 4.

Is there a fine for ignoring AI literacy?

Article 4 has no fine of its own. National authorities can enforce it from August 2026. And if something goes wrong with AI in your organisation, having done nothing about knowledge and rules counts against you.

Do you need an AI literacy certificate?

No. The AI Act prescribes no certificate, exam or specific course. What counts is that you take measures that fit your staff and how they use AI, and that you can show what you did.

How do you show that you work on AI literacy?

Keep a list of the AI tools in your organisation and who uses them, a short AI policy with rules of use, and a record of training sessions and who attended. Update it when new tools or use cases come in.

Want your team AI literate?

In a tailored workshop your team learns what AI can do, where it fails and how to use it responsibly, with the tools you actually use.

Let's discuss your project

From AI prototypes that need to be production-ready to strategic advice, code audits, or ongoing development support. We're happy to think along about the best approach, no strings attached.

010 Coding Collective free consultation
free

Free Consultation

In 1.5 hours we discuss your project, challenges and goals. Honest advice from senior developers, no sales pitch.

1.5 hours with senior developer(s)
Analysis of your current situation
Written summary afterwards
Concrete next steps