Records all AI training sessions delivered — who attended, which modules were covered, the delivery method, and the date. Paired with AUP acknowledgements, this document closes the training delivery evidence gap for SOC 2 CC1.4 and CC2.1.
Having training materials is not the same as having delivered training. SOC 2 assessors will ask for evidence that staff were trained — not just that training documents exist. This log records every training session as it happens, building the evidence trail that confirms the program is running, not just written.
This document works alongside the AUP Acknowledgement (Vol. 5). The AUP records that each person agreed to the policy. This log records that they were trained on how to apply it. Together they satisfy CC1.4 (commitment to competence) and CC2.1 (information and communication about internal controls).
The following modules are defined as part of the AI training program. Required modules must be completed by all staff before using any AI tool. Recommended modules are expected within 30 days of AI tool access being granted. Role-based modules apply to specific departments.
One row per staff member. Check off each required module as it is completed. The completion date column records when all required modules were finished — this is the date that counts for compliance reporting. Link to AUP acknowledgement record where applicable.
| NAME | ROLE / DEPT | PROMPT GUIDE | DATA SAFETY | AUP | IR OVERVIEW | ALL REQ. COMPLETE DATE | AUP ACK DATE | STATUS |
|---|---|---|---|---|---|---|---|---|
Every training session — live, recorded, or self-directed — gets a log entry here. A session can cover multiple modules. The log entry is the auditable record: what was delivered, who delivered it, who attended, and when.
Complete this form after each training session. Submissions are appended to the session log above. For async or self-directed modules, log when staff report completion or when the resource is distributed with a documented expectation of completion.