List the required tools
Ask for the exact applications, plans and permissions. Distinguish training fees from software costs. A demonstration may use features that some participants cannot access on their current accounts.
Choose what can be shared
Use your organisation’s approved information-handling rules. Prepare fictional or cleared examples when appropriate, and agree how participants can ask questions without uploading sensitive material to an unsuitable service.
Rehearse the setup
Have a participant try logging in and opening the exercise environment. Identify who handles access problems. Confirm whether installation, administrator approval or a practice tenant is required.
Preserve the review step
Decide how the example output will be checked and who can approve its use. This guide is a preparation checklist; it does not replace your organisation’s security review or establish that a particular tool is approved.
Run an access check before training
| Prepare | Who should confirm | What completion looks like |
|---|---|---|
| Accounts | Learner and tool administrator. | Each participant can sign in through the approved route. |
| Permissions | Your administrator and instructor. | The exercise environment opens with the intended features. |
| Examples | The owner of the data and the instructor. | A useful example is approved for the training environment. |
| Fallback | Instructor and organiser. | A supplied example or alternative task is ready if access fails. |
Keep the access test separate from claims about a learner’s skill. Resolve setup issues before the paid teaching time where possible.
Put the brief to work
Use the same task, headcount, tools and timing when you contact providers. That makes their answers easier to compare.