Prepare a training session when AI access differs across the team
Prepare around what participants can actually open and complete. Check the target task in their approved setup, identify access gaps before the session and provide a fallback that preserves the learning objective.
Ger Perdisatt, Acuity AI Advisory
2 min read
Define the task before checking the buttons
Write down what participants should be able to do by the end: for example, prepare a checked supplier-update draft from an approved practice pack. Identify the inputs, the checks and the final destination. This lets you distinguish a missing convenience feature from a gap that prevents the exercise altogether.
Ask the internal tool owner to confirm the permitted setup. Do not infer someone’s access from a licence name, a trainer’s screen or a screenshot from a previous course. The useful evidence is a participant successfully opening the required tool and practice material with their own work account.
Choose a fallback that still teaches something
If file upload is unavailable, an approved fictional text excerpt may support the same evidence-checking lesson. If no assistant access is available, participants can review a prepared flawed output against the source pack. Label that activity accurately and schedule the missing hands-on step later.
Do not work around an access restriction by using a personal account or sending business files to an unapproved service. If the fallback changes the task substantially, split the session or change the exercise. The organiser should be able to explain what each group practised and what remains outstanding.
Editorial guidance informed by Acuity's work with teams. Examples are fictional and client materials stay private. To record who owns an AI use and when it is reviewed, see AI Register.