Stolen Orbit
ENIT
Let’s talk
FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

AI team training plan

Build training around what people must do and recognise. A successful demonstration does not prove the team can handle an incorrect result.

By Stolen OrbitRevision

When to use it and what to produce

Before introducing an AI tool to a team and when procedures, permissions or review responsibilities change.

A role-based plan with exercises, approved materials, readiness criteria and a support channel after the session.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

Download the complete blank template (.md)

1. Start with roles

Separate users, reviewers and process owners. Each needs to know permitted actions and decisions that remain outside their responsibility.

See a worked example

Illustrative example: an internal assistant user must check a cited document; the reviewer must also recognise an expired source and stop the answer.

List roles, familiarity with the process and concrete tasks they will perform with the system.

State what a person must be able to do: find a source, correct a draft or report a failure.

Link applicable internal rules and prepare examples of information that must not enter the tool.

2. Prepare realistic exercises

Use authorised practice materials. Pair a successful case with an ambiguous case and one requiring a stop, including the complete correction path.

See a worked example

Illustrative example: an answer cites the wrong procedure. The participant opens the source, identifies the mismatch, rejects the draft and records the case for the owner.

Describe input, task and expected result for each case; avoid exposing unnecessary information.

Specify fields, sources and differences to inspect before using the result.

Practise requesting help, preserving the case reference and completing the task without AI.

3. Check independent use

Assess observable actions rather than attendance or satisfaction alone. Plan a supported period and a simple way to update operating instructions.

See a worked example

Illustrative example: after the exercise, the team handles initial cases with guided review. Recurring difficulties become a short addition to the operating instructions.

Define tasks to complete without assistance and mistakes that require further supervised practice.

Record contact, channel, agreed availability and the location of current instructions.

Specify when actual use is observed, which difficulties are collected and who updates training and procedure.

Pitfalls to avoid

  • Teaching features and commands without explaining the working process.
  • Using unauthorised live data in a demonstration.
  • Confusing attendance with the ability to recognise errors.

Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.