Necessary storage is on. Analytics load only after consent. Learn more
Product updates
Every entry here is something you can use today. The date is the date it went live, and the second line says what it means rather than how it was built.
When a route is assigned, the platform records which answers, which rule version and which steps produced it. Months later you can show not only that someone was trained, but why exactly that route was the right one for their role and systems at that moment.
The awkward question in an audit is rarely did they train. It is why this, for this person.
Instead of adding modules where the catalogue was already deep, we measured which sector, role and level combinations came out with the least material and filled those first. The new modules cover the fundamental rights impact assessment, incident handling, enforcement and prohibited practices.
The route a rare role gets is now as substantial as the route a common one gets.
Transparency used to arrive as one generic module for everyone. HR, healthcare, finance, government, education and legal now each carry their own version, built around the situations those teams actually run into: a client-facing chatbot, an AI voice recording, a generated image in a campaign.
People recognise a duty faster in an example from their own working day than in a paragraph about the regulation.
Every one of the 35 competencies in the catalogue points at the EU AI Act obligations it teaches, pinned to a published release of the implementation graph. When one of those obligations changes materially, the platform names the competencies and modules that need a fresh look instead of leaving you to find out later.
A course quietly goes stale on the day the law moves. Now the staleness has a name, a date and a list.
Each module is written and then checked separately against the published implementation graph, with the reviewer working from the regulation rather than from the draft. The check runs on scope and duty holder as well as wording, because the wrong actor is a more expensive error than a clumsy sentence.
Content about a regulation is only worth as much as the review it survived.
Two people with the same title can sit at very different distances from an AI decision. The route now gets deeper when the systems in scope and the relation to the decision justify it, and stays short when they do not.
Nobody sits through material that does not concern them, and nobody skips material that does.
Every distribution to an external LMS carries its own duration and seat cap. When the cap is reached, the next person is refused rather than silently added, and central updates still reach everyone who is already in.
You keep control of scope without having to police it by hand.
Contractors, board members and new joiners often sit outside the LMS. A one-time secure link gets them into the right route without an account, and the link stops working after use, so access does not quietly linger.
The people hardest to reach through a system are often the ones closest to the risk.
LearnWize now speaks SCORM, LTI 1.3 and xAPI. Your L&D team publishes the module in the LMS people already use, with roster sync and scores flowing back, while the role mapping and the evidence file stay in LearnWize. Tested end to end against a real LMS, including teacher selection, automatic learner provisioning and scores returning to the course.
Two doors, one file. L&D does not have to migrate, and compliance does not have to reconstruct.
Organisation admins can pull the current state of the file themselves: which roles are covered, which people completed what, and which parts are still open. No support ticket, no waiting for a report.
An evidence file you can only get by asking is not a file you can rely on.
Register the AI systems in use, and the platform maps which roles work with them and which obligations that brings along. The result is a role by role view rather than a list of tools.
Governance tools prove systems. This is the part that shows which people can demonstrate they are ready.
Each certificate carries a public verification route, so a client, an auditor or a new employer can confirm it without a copy passing through email.
A certificate that cannot be checked is a claim, not evidence.