AI literacy half-day

AI in daily work,
practised on real tasks.

A half-day for your staff. Everyone sees how AI works and where it gets things wrong, clarifies what may go in, and builds a prompt recipe for a task of their own that is still there next time. Afterwards, there is a certificate of attendance for your record.

Half day Remote or on site For all staff
Half day · Example agenda
01

The basics

How AI works and the four places where it gets things wrong

02

The rules

What may go in, where it runs, what you do with the result

03

The craft

The prompt recipe, shown on your AI platform

04

Your own case

A real task, two attempts, a saved recipe

05

Wrap-up

Open questions collected; the certificate follows

Example agenda, tailored to your organisation in a call beforehand.

Who it is for

For organisations that use AI
or plan to introduce it soon.

In many teams, most people already work with AI, but almost everyone starts from scratch every time. Good instructions are typed and never saved, and results are rarely checked. That is where the half-day comes in.

Mixed experience is intended

Some colleagues use AI every day, others have never tried it. There is no test and no grading, and nobody has to use AI afterwards.

Practice on your platform

We practise with the tool your organisation has approved. I prepare examples beforehand, such as an assistant with a made-up report that answers a question outside the document with: “That is not in the document.”

Rules along the path of a request

Instead of a catalogue of laws, we follow the path every request takes and connect it with your internal rules, such as a data traffic light. That makes it clear what may go in and what may not.

The building blocks

What the half-day covers.

01

How AI works

The path from your question to the answer, what the tool keeps in view at once (context window) and whether it learns from your input.

02

Where AI makes mistakes

Four kinds of error: invented, outdated, mixed up and people-pleasing. In an exercise, participants find them themselves in a made-up sample text.

03

The path of a request

Four questions organise the rules: what do you put in (data protection), where does it run (contract and location), what do you do with the result (EU AI Act, labelling) and who owns it (copyright).

04

The prompt recipe

Six elements: who I am, who the result is for, what must never appear, form and length, how I know it is good, and the instruction to check the result against the recipe itself.

05

Storing knowledge

Saved prompts, your own documents as a knowledge base and stored rules (skills), so that good instructions are still there next time.

06

Your own case

A first attempt without a recipe, then with one, check the result, second attempt, save. Plus one sentence on what you would not use the result for.

Process

From the first call to the certificate of attendance.

01

Prepare Beforehand

In a call beforehand, we go through your platform, your rules and where your team stands. If you like, I briefly talk to a few staff members first, so the examples come from your daily work.

02

Arrive Half day

Everyone notes down one routine task that comes back every week. We pick it up again later in their own case.

03

Understand Half day

Short input on the basics, kinds of error and rules, each with a moment to join in and a live demo on your platform.

04

Do Half day

Everyone works on their own case, with a recipe and a second attempt. Anyone without a case to hand takes a prepared case card. At the end, everyone briefly shares what did not work on the first try and what they changed.

05

Document Afterwards

Everyone receives a certificate of attendance, the materials to read up on and a short overview of the key steps on your platform. With the overview of the content, you can add the session to your record under Article 4 of the EU AI Act.

Setting

Format

A half-day, remote or on site with you. For all staff or team by team.

Equipment

Laptops with access to your AI platform.

Data

Practice follows your rules, with made-up examples in the exercises. Whatever may not go into the platform stays out of the participants’ own cases too.

Open questions

Anything that does not fit into the half-day goes on a list and is answered in the materials or passed on to your organisation without names.

Common pitfalls

What most often goes wrong in daily work.

Starting from scratch every time

Good instructions are typed and never saved. Next time they are missing, and the result is weaker again.

Treating the chat as the result

Long conversations lose sight of earlier parts. Whatever should apply needs to be saved, as a prompt or a stored rule.

Asking for confirmation

If you ask “Am I right?”, you usually get agreement. The better question is: “What speaks against this draft?”

The outdated document

The tool cannot know whether an attached document is the current one. That check stays with you.

Names and figures without guidance

Without a list of names, names get mixed up, and figures without a source are often invented. Both can be caught in the recipe beforehand.

Current facts without a search

Many tools do not look things up on their own. If something needs to be current, say explicitly that it should be looked up.

What your team takes away

A recipe of their own for everyone
and a certificate for your record.

A saved prompt recipe

Everyone has built, checked, improved and saved a recipe for a task of their own on your platform. It still works tomorrow.

A trained eye for errors

Everyone knows the four kinds of error and the sentences that catch them before the answer comes.

Clarity about the rules

The four questions along the path of a request, connected with your internal rules. With them, every new task can be checked for what may go in.

Materials and certificate

Materials to read up on, an overview of the key steps on your platform and, for every person, a certificate of attendance for your record under Article 4 of the EU AI Act.

And then?

If you like, I offer office hours after the half-day: open slots over a few weeks where staff can bring their own tasks. Individual topics can also be explored in a half-day of their own, such as law, stored rules and agents, or automation.

If a team wants to tackle a specific task with AI: Use-case workshop, a half-day per team →

For the decisions only leadership can make: AI workshop for leadership teams →

Questions about the half-day

How does the half-day relate to Article 4 of the EU AI Act?

Article 4 of the EU AI Act has applied since 2 February 2025 and requires organisations that use AI to take measures for a sufficient level of AI literacy among their staff. After the half-day, you receive a certificate of attendance and an overview of the content for your record. Please discuss with your lawyers how you assess your measures overall. Legal advice is not part of what I offer.

Is the half-day a test?

No. Nobody is graded or quizzed, and nobody has to use AI afterwards. Mixed experience in the room is intended, because experienced and new users learn from each other.

Which AI platform do we need?

Ideally the one your organisation already uses or plans to introduce, such as Microsoft Copilot, ChatGPT Enterprise or Langdock. The platform is the practice device. What participants learn works in any tool. If you do not have a platform yet, we find a solution for the exercises in the call beforehand.

Do participants need prior knowledge?

No. The half-day starts with the basics. Participants with more experience bring a more demanding task to their own case.

How are data protection and rules taught?

Along the four questions that come up with every request: what do you put in, where does it run, what do you do with the result and who owns it. For each question, I show what applies in general and what it means for you. I include your own internal rules, such as an AI policy.

Can the half-day be repeated or explored further?

Yes. As a second round for new colleagues, or as a half-day of its own on a topic the literacy half-day only touches on, such as law, stored rules and agents, image and audio, or automation.

What are the office hours?

Open slots over a few weeks after the half-day. Staff bring a task of their own, and we work on it together. Office hours are optional and agreed in advance.

How does the half-day differ from the workshop for leadership teams?

The leadership workshop is about the decisions only leadership can make. The half-day is for all staff and hands-on: basics, rules and practice with their own tasks. The two formats can be combined.

What does the half-day cost?

That depends on group size, preparation and format. You get a concrete quote after the first call.

Contact

Email me at info@slworks.de or book a free intro call right away.

Book an intro call

Loads the Cal.com booking calendar (USA). This transmits your IP address to Cal.com. More in the privacy policy (German).