For compliance leads who just wrote the AI policy

The policy document or the policy people actually know

You just finished writing the AI policy. It sets out the rules, who owns what, and where to escalate. Now the harder question: does anyone on your team actually know what it says about the tools they use, and could you show that if someone asked?

The policy document

Sets out the rules, in writing, before anyone has to guess.
Assigns ownership: who decides, who signs off, who escalates.
A concrete answer when a client or internal auditor asks whether you have an AI policy.
One write-up, not an ongoing programme.

The lived policy

People can name the rules that apply to their own tools, not just the document's table of contents.
Every assignment is recorded with the answers given and the rule version it was checked against, so it can be replayed later.
New joiners meet the policy through the same route, sector-specific and matched to the AI systems they actually use, via the intake at /start.
When the policy or the law changes, the evidence log records the change and the training content sent back for review.
Evidence is exportable at the organisation level, not scattered across inboxes and shared drives.

See the public log of legal changes

What article 4 actually asks for

Article 4 has applied since 2 February 2025. Since 27 July 2026, Regulation (EU) 2026/1744 confirms that it asks providers and deployers to take measures that support the development of AI literacy, taking the context into account. It does not require guaranteeing that any specific person reaches a set level, and it prescribes no course length, test or certificate. A policy document is one measure. It states the rule. Training against that document, so each role can point to what applies to their own tools, is what turns the measure into something you can actually show.

When the document is simply enough

If your organisation genuinely uses almost no AI yet, a policy that mostly exists to set boundaries before adoption starts can carry the weight on its own. The escalation route matters more than a trained population when there is barely a population using anything yet. Add the lived layer once real usage grows, or once a client, manager or new hire starts asking what the policy actually means for the tool on their desk. Wait too long and the document describes a company that no longer matches the one using the tools.

From document to evidence

LearnWize does not replace the policy, it makes it demonstrable. The onboarding at /start asks about sector, the AI systems already in use, and roles, then builds a role-based route from your own policy content. Every assignment is recorded with the answers given and the rule version it was checked against, so it can be replayed later. The AI register connects each system to the people who use it. Depth follows risk, not job title, across 15 sectors. When the policy or the law changes, the evidence log records the change and the training content sent back for review, so you can show what was updated and why, not only what the document says.

See what this looks like for your organisation

The 5-minute scan maps your AI use to the roles around it and shows where your evidence is thin.

AI Act evidence routes

Pick the route that matches your AI Act evidence question.

Focused pages per question: from mandatory Article 4 literacy and training records to sector evidence and an audit-ready dossier.

AI literacy evidence

How to make AI literacy demonstrable for HR, Legal, Compliance, IT, and management.

View route

AI literacy evidence dossier

The evidence chain from role and use case to scenario practice, scores, certificates, and reporting.

View route

AI literacy training records

Document completion, scores, validity, refresh cadence, and management evidence.

View route

Mandatory AI literacy

What Article 4 asks from teams that use, buy, manage, or oversee AI systems.

View route

The lived policy

People can name the rules that apply to their own tools, not just the document's table of contents.

Every assignment is recorded with the answers given and the rule version it was checked against, so it can be replayed later.

New joiners meet the policy through the same route, sector-specific and matched to the AI systems they actually use, via the intake at /start.

When the policy or the law changes, the evidence log records the change and the training content sent back for review.

Evidence is exportable at the organisation level, not scattered across inboxes and shared drives.

See the public log of legal changes

What article 4 actually asks for

When the document is simply enough

From document to evidence