AI training for employees: a four-week learning plan

Choose an approved task with an identifiable source and a responsible business owner. For example, use a synthetic enquiry and an approved reply rule. Decide who prepares the draft, who checks it and what requires escalation. Avoid beginning with a tour of tools while the permitted work remains undefined.

Ask participants what they already know and where they need help. Check that the learning format is accessible to them, that their approved accounts work and that they can open the exercise material. Agree how questions can be raised privately as well as during the group discussion.

Prepare the intended result before asking anyone to use AI. For a reply exercise, specify which facts can be repeated, which commitments are prohibited without approval and which information is missing. This reference answer should help the facilitator judge the work; it should not require everyone to produce identical prose.

Use the AI usage policy as the source for local rules. If the policy does not settle a question, send it to its owner. Do not ask participants to invent a company rule simply to finish an exercise. Keep that unresolved question visible in the worksheet.

Agree session lengths with your team and check whether they allow enough practice. Reserve separate space for preparation, guided practice, feedback and correction; enter the actual duration after the session.

The proposed weeks are stages, not attendance requirements. A familiar task may need less explanation, while a changed approval process may require more practice. If a stage exposes missing rules, resolve them before asking staff to apply the process independently. Moving to the next calendar slot is not evidence that the previous problem disappeared.

Use the following table to agree ownership and outputs. We recommend these learning objectives and checks based on the Bundesnetzagentur's guidance.

Start with a walkthrough of the chosen task. Show the approved account, the permitted input and the destination of the draft. Ask office staff to explain which source they would use and when they would stop. Management should resolve questions about authority; IT should resolve questions about the configured environment.

Use an invented policy scenario: the team may draft replies from approved service notes, but may not enter original customer records into an unapproved tool. Ask participants to identify what they can do with a supplied synthetic enquiry. The expected result is a permitted route and an explicit question wherever the policy is incomplete.

Record uncertainty without turning it into an individual failure. If participants disagree about which environment is approved, the owner should clarify the instruction and demonstrate the correct access. Retain the annotated scenario and the unresolved questions as evidence of the activity.

End the stage with a usable local instruction: permitted task, permitted input, source, reviewer and escalation contact. Have the responsible people confirm its content before it is used in the next exercise.

Ask staff to prepare a reply from supplied material. In the synthetic case, a customer requests an appointment, but the provided status says the request is awaiting a decision. The prompt should ask for a draft that acknowledges the request without confirming the appointment and lists what must still be clarified.

Management defines an acceptable output: it should reflect the supplied status and make no unsupported promise. Office staff provide the task, source material and format. IT prepares the approved exercise environment and ensures the inputs match what the team is allowed to use.

Compare the draft with the source sentence by sentence. Ask participants to mark the origin of each factual statement. If the draft adds a commitment, remove it and discuss which instruction or review step should catch the problem. Keep the original draft, the checked version and the reason for the correction in the exercise record.

Do not use a fluent answer as the only acceptance criterion. The exercise is complete when the participant can explain the source boundary and the remaining gap. Adjust the instruction if the same misunderstanding appears across the group.

Provide a deliberately incorrect draft for a synthetic case alongside the source. Include an unconfirmed appointment and an incorrect recipient. Ask participants to choose between correcting, rejecting and escalating the work, and to explain why.

Management decides which proposed commitments require a stop. Office staff check the recipient, factual claims and permitted next action. IT demonstrates the agreed reporting route and checks whether the configured restrictions match the working instructions. If a technical check cannot be completed, record that limit rather than marking it successful.

Separate a language correction from an authority question. Staff can propose clearer wording, but an unresolved booking decision still belongs to its owner. The next step might be to request that decision and prepare a revised draft afterwards.

Use the draft and sign-off guide to define what the human reviewer must see. The practical competency check is whether participants identify the relevant evidence and response. Use it to identify support needs.

Give participants a fresh case with the same working instructions and a changed detail. For example, the appointment is now approved but the recipient remains unresolved. Ask them to complete the permitted parts and explain why sending still needs clarification. This checks whether they use the evidence rather than memorise the earlier answer.

Have management assign an owner to each remaining question. Office staff should know where to find the current instructions and how to request help. IT should record the relevant configuration reference and which changes would trigger another review of the material.

We recommend including a new tool, changed data rules, a different approval step and recurring reported errors among those triggers. Decide a suitable review arrangement for the actual task and revisit it when experience shows a gap.

Write a handover note that states what is ready, what is restricted and what still needs support. Do not call the entire process approved merely because everyone attended. If the task remains unclear, keep it within supervised practice until its owner resolves the missing instruction.

Treat funding as a separate eligibility decision before commissioning work. For Austria, the KMU.DIGITAL advisory FAQ publishes programme validity until 31 December 2026, but warns that budget exhaustion can interrupt availability. As of October 2026, that published validity does not establish an open application window for your booking.

The same advisory FAQ requires programme-approved experts and excludes costs incurred before application. Its advisory funding is not evidence that this employee learning plan is reimbursable. The implementation FAQ additionally requires a previously paid-out funded consultation. Check supplier status, the training component and current availability for the actual project.

For Germany, the Federal Employment Agency's overview labelled 2025 lists more than 120 hours for the ordinary employee further-training route, an approval requirement under AZAV, and an exclusion for legally required employer training in its explanation of measure objectives. Other routes differ. This older overview does not establish a current entitlement for a short internal programme.

Check current conditions with the responsible programme administrator before relying on funding. The DACH funding guide helps organise the wider application questions. Keep the training itself connected to introducing AI: approved task, checked work, updated instructions and a named person who follows up.