| Planning question | Suggested working document |
|---|---|
| Who uses what? | Inventory of tools and tasks |
| Which precautions should people learn? | Checking examples and data rules |
| What needs another look? | Questions and follow-up actions |
Where should your organisation start?
List the tools people use, their tasks, the data involved and the people who may be affected. Summarising public material raises different questions from processing employee information. The learning plan should reflect that difference.
For each use, identify an owner, define permitted data and agree who checks the result. This working document connects learning to the organisation’s actual work.
What could a useful session cover?
A session can combine an explanation of how assistants work, examples of their errors and an exercise related to participants’ roles. Make checking visible: find the source, spot a missing point or reject an unsupported answer.
Prepare an invented or approved example. Participants should be able to practise without putting confidential information into an unapproved tool. The guidance taught should match the tools the organisation uses.
How can you document the work?
You can record the audience, the need identified, the date, materials and unresolved questions. This is an organisational suggestion, not an evidence template automatically accepted by an authority.
A follow-up after practice can expose needs the first session did not reveal. Updating a rule or example is then part of the work.
What is the scope of this guide?
This guide offers an educational explanation and preparation ideas. It does not replace an assessment of the obligations applying to your systems and organisation. High-risk systems may involve additional requirements.
The WeGoTo proposal will specify the programme and documents. No compliance certification is offered.
A starting point for your own record
Download a blank CSV to record roles, tools, learning needs and actions. This is a working template, not a compliance certificate.