AI Law & the EU AI Act

AI Law & the EU AI Act The two-day seminar for everyone who uses AI and has to answer for it: you learn which risk class your system falls into, which duties follow from that and how to build an AI inventory that survives an audit. By the end you know what you must document — and what you had better not do.

AI Law & the EU AI Act at a glance

• Format: 2 days on site + self-learning track
• Level: basic
• Participants: max. 16 people
• Language: German (English on request)
• Certificate: AEI certificate of attendance
• Investment: €199.00 plus VAT

The EU AI Act is no longer a future topic. It applies, it applies in stages, and it hits not only providers of AI but also companies that use it. Whoever uses AI in customer service, has product texts generated or presorts applications is affected.

The uncertainty is understandable, but it is not a state you can stay in for long. The effort is manageable if you approach it early and in order: an inventory, a risk classification, documentation, a training. Whoever waits does the same thing later under time pressure.

This seminar works from duty to practice. You classify your systems into risk classes, derive the duties per role and build an inventory that lets you answer questions at any time. Legal classification and technical implementation are thought together.

What you take away

• A classification of your AI systems into the risk classes of the AI Act.
• The duties per role — provider, deployer, importer.
• An AI inventory template you can maintain yourself.
• An understanding of the interface with GDPR and copyright.
• A plan for documentation, training and approval.

Your learning objectives

• You classify an AI system into the correct risk class.
• You derive the concrete duties from your role.
• You recognise when personal data is involved and what that changes.
• You know which documentation an audit expects.
• You settle responsibility and training before a system goes live.

The levers at a glance

The role decides the duty. Whoever provides a system has different duties than someone who uses it. Many companies are both at the same time — and do not know it. The classification is the first and most important step.

The inventory is half the battle. Whoever knows which systems are in use, where they come from and what they are used for can answer almost any question. Whoever does not can answer none.

Transparency is not a weakness. A system that is recognisably AI creates fewer problems than one that pretends to be human. In the end the labelling duty protects both sides.

AI law is not a separate body of law. GDPR, copyright and advertising law still apply. Whoever looks only at the AI Act misses half the risks.

An AI tool you cannot explain is a risk, not a feature. If nobody in the company can say which model answers customer questions, which data it sees and who signed the contract, the problem is not the regulation — it is the missing overview. The inventory closes that gap first.

Who is this seminar for?

For people who introduce AI and carry the responsibility for it.

• E-commerce and marketing leads who use AI tools.
• Data protection and compliance officers before the first audit.
• Managing directors who want to know what is coming.
• IT and project leads who procure and operate systems.

No legal background is required. The rules are explained in plain terms during the seminar; the task is organisation, not legal advice.

The seminar is not a substitute for a legal assessment of an individual case. It enables you to ask the right questions and build the documentation.

Investment and dates

Participation costs €199.00 plus VAT, including the self-learning track, materials and certificate of attendance. There are six dates per year in Berlin, Hamburg, Cologne, Munich and live online, plus an in-house variant for teams. You will find all dates in the list on this page.

You do not need system access for the exercises. Anyone who brings a list of the tools in use can build the inventory during the seminar.

After the seminar

You keep the materials, an inventory template with all the fields an audit expects and a duty matrix per role. With that you can establish a reliable state within a month.

The matrix assigns the duties to each role and marks which of them must be documented. It does not replace legal advice, but it shows where you need some.

Keep the inventory alive: a new tool every quarter means a new row. Whoever updates on procurement rather than on request never has to reconstruct anything under pressure.

Two weeks after the seminar you receive a short follow-up: your inventory and the systems whose classification is still open.

For teams the seminar is available as an in-house event with your own systems. The procedure stays the same, the examples come from your company.

Programme: 2 days

Day 1 – The EU AI Act

• Risk classes
• Duties per role
• Personal data in AI systems
• Legal bases and contracts
• Who is liable for errors
• Documentation duties

Day 2 – Liability and responsibility

• Advertising with AI
• Copyright and related rights
• Creating an AI inventory
• Processes and training

Both days run from 09:00 to 16:15 with breaks in the morning, at midday and in the afternoon. Short self-checks sit between the blocks so you can test where you stand before moving on.

Each day has three parts: an introduction to the pattern, an exercise on your own systems and a review in the group. At the end of day one you classify one system; on day two your inventory stands.

The seminar includes a self-learning track. It contains the patterns from both days as short units with examples and one self-check each. You can work through it before the date to clarify terms, or afterwards to repeat what stuck and what did not.

Our approach

We work on your systems, not on a reading of the statute. At the start of each exercise you decide which system you are examining and in which role you face it; at the end stands a classification with a reason.

The exercises are short and repeat in variations. That is deliberate: legal classification is not learned by listening but by applying it repeatedly to your own case.

Every block ends with a sentence you could show a colleague: which system, which class, and which duty follows from it.

We work in pairs, in small groups and in plenary, with changing partners. Every participant gets feedback on their classification, not just on their question. Group level and participant count are deliberately limited: with 16 people no anonymous lecture is possible.