COMMERCIAL IN CONFIDENCE — LICENSEE USE ONLY — PACK-AIMS-ART4-001 v1.0
U
UNUS London
EU AI Act Compliance Series · Article 4 · Staff Training Documentation
EU AI Act Article 4 Compliance Pack:
Staff Training Documentation for Regulated Sectors
A five-part documentation bundle providing the training log template, verification checklist, overdue monitoring procedure, guidance note, and regulator evidence cover sheet required to demonstrate compliance with the EU AI Act Article 4 AI literacy obligation.
Document ID
PACK-AIMS-ART4-001
Version
1.0
Issue Date
2026-09-01
Obligation In Force
2025-02-02 (NOW)
Companion Register
REG-AIMS-LIT-001
Retention Period
7 years minimum
Part A — Guidance Note
Article 4 AI Literacy: The Legal Obligation and What It Requires
This guidance note sets out the operative content of Article 4, its enforcement timeline, the evidence it demands, and how the companion register (REG-AIMS-LIT-001) satisfies that demand.
EU AI Act Art. 4 · Reg. (EU) 2024/1689 ISO/IEC 42001:2023 Cl. 7.2 ITIL 4 · Workforce & Talent Management IEC 82079-1:2012 (Notices)

1. The Statutory Text

Article 4 of Regulation (EU) 2024/1689 (the EU AI Act) entered into force on 2 February 2025. There was no grace period. The obligation reads:

⚠ Warning — Active Regulatory Obligation

Article 4 is not a forthcoming obligation. It is in force now. Any organisation that has deployed AI systems and has not documented its staff AI literacy position is already in breach, even where those systems are general-purpose tools (email, drafting assistants, scheduling AI) rather than Annex III high-risk systems.

2. Three Operative Elements

Element 1 — "Providers and deployers"

The obligation falls on both the entity that provides the AI system and the entity that deploys it. For regulated sectors, the deployer is almost always the regulated firm itself — the law firm, the financial institution, the healthcare trust. The deployer cannot delegate compliance to its AI vendor.

UK application: The EU AI Act does not apply directly in the UK post-Brexit. However, SRA-regulated firms serving EU clients or operating under EU-connected mandates are subject to extraterritorial provisions. Moreover, the SRA's supervisory scope expressly covers AI governance and staff competence. Article 4 is the evidential standard that UK regulators will reference when framing their own supervisory questions.

Element 2 — "Sufficient level… shall be documented"

The phrase "to their best extent" does not grant discretion over whether to comply — it sets the effort standard. "Sufficient level" is relative to: the technical complexity of the AI system in use; the role of the staff member operating it; the context in which the system is deployed; and the population the system affects. What is "sufficient" for a partner reviewing a generative AI legal research tool differs from what is sufficient for a data entry clerk whose workflow is partially automated.

Crucially, sufficiency must be demonstrated. A policy stating that training "will be provided" does not constitute evidence of compliance. A log recording what training was provided, to whom, when, and at what assessed competency level does.

Element 3 — "Persons dealing with the operation and use of AI systems on their behalf"

The obligation extends to contractors, secondees, and third parties who operate the firm's AI systems. A firm that uses a managed AI service delivered by a contractor workforce must ensure that those individuals also meet the literacy threshold. Panel client governance frameworks increasingly replicate this requirement, exposing firms to dual regulatory and commercial risk.

Scenario: Halstead & Cole LLP deploys AIMS-SYS-003 (a legal research assistant) and AIMS-SYS-004 (a document drafting accelerator). COLP Priya Anand is required to confirm, when Pemberton Capital LLP issues its AI governance questionnaire, that all fee earners using those systems have completed and evidenced AI literacy training. Without REG-AIMS-LIT-001, no such confirmation can be made with regulatory integrity.

3. The Three-Phase Enforcement Timeline

Date Provision Obligation Status
2 Feb 2025 Article 4 — AI Literacy All deployers shall ensure and document sufficient AI literacy for staff operating AI systems. No grace period applies. ● ACTIVE NOW
2 Dec 2026 Article 50 — Transparency Certain AI systems must disclose their AI nature to users. Includes GPAI model obligations on providers. ● 15 months
2 Dec 2027 Annex III — High-Risk (standalone systems) High-risk AI systems listed in Annex III face full conformity obligations including fundamental rights impact assessment. ● 27 months
2 Aug 2028 Annex III — High-Risk (embedded systems) High-risk AI embedded in regulated products face the same obligations; extended timeline to allow product update cycles. ● 35 months
⚡ Caution — Gateway Obligation

Article 4 is a gateway obligation. Regulators auditing an organisation's Annex III high-risk compliance will treat the absence of Article 4 literacy records as evidence that the broader compliance programme lacks adequate foundations. Failure to establish REG-AIMS-LIT-001 now undermines every subsequent compliance assertion made in 2027 and 2028.

4. ISO/IEC 42001:2023 Clause 7.2 — Competence

ISO/IEC 42001:2023, the international standard for AI management systems, requires at Clause 7.2 that organisations:

  • a)Determine the necessary competence of persons doing work under its control that affects its AI management system performance;
  • b)Ensure those persons are competent on the basis of appropriate education, training, or experience;
  • c)Where applicable, take actions to acquire the necessary competence and evaluate the effectiveness of those actions;
  • d)Retain appropriate documented information as evidence of competence.

ISO/IEC 42001 provides the framework. REG-AIMS-LIT-001 is the evidence instrument that converts framework into regulatory proof. Clause 7.2(d) is satisfied by a populated, COLP-verified training register. It is not satisfied by a training policy alone.

5. ITIL 4 Service Management Mapping

Under ITIL 4's Workforce and Talent Management Practice, Article 4 compliance is correctly categorised as a recurring service demand event rather than a one-time project. This has three operational implications:

Recurring Demand

Each new AI system deployment creates a training demand event. The service catalogue entry for AI literacy training is triggered by system onboarding, not by regulatory deadline.

12-Month Refresh

Literacy is not a one-time certification. A 12-month refresh cadence is the minimum viable standard for fast-moving AI system contexts. WF-LIT-003 automates overdue detection.

Retroactive Logging

Where evidence exists (vendor attendance records, email confirmations, policy acknowledgements), retroactive logging is permissible. A firm that has been training staff informally may have more to log than it realises.

6. The Evidence Gap

⚠ Warning — The Distinction That Matters

The policy tells regulators what the firm intends. The training record tells them what the firm did. When a regulator asks for evidence under Article 4 or a panel client issues a Section 7 AI governance questionnaire, only the second document answers the question. A firm with a well-drafted AI literacy policy and no training log has demonstrated intent, not compliance.

The five evidence fields that REG-AIMS-LIT-001 must capture to satisfy an Article 4 inspection are:

Minimum Evidence Fields — Article 4 Regulatory Inspection
Field
Regulatory Purpose
Required
staff_code
Identifies the individual; allows inspector to cross-reference against HR records and AI system access logs.
REQUIRED
ai_system_ref
Links training to a specific deployed system. General AI awareness training does not satisfy Art. 4 for a system-specific deployment.
REQUIRED
completed_date
Establishes that training preceded or closely followed system deployment. A date in 2023 cannot evidence compliance with a 2025 deployment.
REQUIRED
competency_assessed
Demonstrates that literacy was assessed, not merely that attendance was recorded. One of: Foundational / Operational / Proficient / Advanced.
REQUIRED
colp_verified
Provides the COLP/DPO sign-off that the record was reviewed by a responsible officer — the institutional assurance layer.
REQUIRED
ℹ Note

Part B of this pack provides the complete training log template with all REG-AIMS-LIT-001 fields, field-by-field completion guidance, and the competency assessment matrix. Part C provides the COLP verification checklist and sign-off protocol.

Part B — Training Log Template
AI Literacy Training Record: Per-Staff, Per-System Log
Complete one record per staff member per AI system per training event. All Required fields must be populated before the record is eligible for COLP verification. Log reference: REG-AIMS-LIT-001.

Training Record — REG-AIMS-LIT-001

Section 1 — Record Identity Auto-generated on submission
Field
Entry
Status
record_id
Auto-generated (e.g., LIT-2025-00047)
AUTO
firm_id
Enter your organisation's firm identifier (e.g., HCLLP-001)
REQUIRED
created_at
Auto-populated on submission (ISO 8601 format: YYYY-MM-DD HH:MM:SS UTC)
AUTO
logged_by
Staff code of the person logging this record (may differ from subject)
REQUIRED
Section 2 — Staff Identification
Field
Entry
Status
staff_code
Unique staff identifier from HR system (e.g., ANAND001)
REQUIRED
staff_name
Full name of the staff member (for reference; primary key is staff_code)
REQUIRED
role_title
Job title / role at time of training (e.g., Compliance Officer for Legal Practice)
REQUIRED
department
Business unit, practice group, or team (e.g., Risk & Compliance; Corporate)
OPTIONAL
employment_type
Employee / Contractor / Secondee / Consultant (Art. 4 covers all who operate systems on behalf of the deployer)
REQUIRED
Section 3 — AI System Reference
Field
Entry
Status
ai_system_ref
Select: AIMS-SYS-001 · AIMS-SYS-002 · AIMS-SYS-003 · AIMS-SYS-004 · AIMS-SYS-005 · AIMS-SYS-006 · AIMS-SYS-OTHER
REQUIRED
ai_system_name
Common name of the system (e.g., "Legal Research Assistant", "Document Drafting Accelerator")
OPTIONAL
system_version
Version or release of the AI system at time of training (if known)
OPTIONAL
deployment_context
Brief description of how the system is used in this person's role (max 200 characters)
OPTIONAL
Section 4 — Training Event Details
Field
Entry
Status
training_format
Select: In-Person Workshop · Online Module · Vendor Briefing · Internal Briefing · Self-Study · Assessment Only
REQUIRED
training_title
Full title of the training programme or module as it appears on the certificate or attendance record
REQUIRED
training_provider
Name of provider organisation (e.g., "UNUS London", "AI Vendor Name", "Internal L&D")
REQUIRED
training_duration_hrs
Duration in decimal hours (e.g., 1.5 for 90 minutes; 0.5 for 30-minute briefing)
OPTIONAL
completed_date
Date training was completed — format: YYYY-MM-DD (e.g., 2025-04-15)
REQUIRED
refresh_due_date
Auto-calculated: completed_date + 12 months. Override if system-specific refresh cycle applies.
AUTO
Section 5 — Competency Assessment
Field
Entry
Status
competency_assessed
Select one assessed level — see matrix below
REQUIRED
assessment_method
Select: Written Assessment · Practical Demonstration · Manager Observation · Quiz / MCQ · Attendance Record Only
OPTIONAL
assessment_score
Numeric score if applicable (e.g., 84 for 84%); leave blank if attendance-only
OPTIONAL

Competency Level Reference Matrix

Level
Description
Typical Roles
Foundational
Understands what AI systems are and their general capabilities. Can identify when they are interacting with an AI-assisted process. Does not operate AI systems directly.
Administrative staff, support roles, reception
Operational
Can use designated AI systems in their role within defined parameters. Understands system limitations and when to escalate outputs for human review.
Paralegals, associate lawyers, analysts, case handlers
Proficient
Can configure, adapt, and quality-assure AI system outputs. Understands bias risks, hallucination, and appropriate reliance. Can train others in safe use.
Senior associates, managers, L&D leads, DPOs
Advanced
Can evaluate, procure, and govern AI systems. Understands regulatory obligations under EU AI Act, data protection law, and sector regulation. Accountable for AI governance.
Partners, COLPs, CIOs, Heads of Risk, Board members
Section 6 — Evidence Reference
Field
Entry
Status
evidence_description
Describe the evidence held (e.g., "Vendor attendance certificate — Acme AI Foundations v2 — 15 April 2025")
REQUIRED
evidence_link
URL or file path to stored evidence document (SharePoint, DMS, or HR system reference)
OPTIONAL
evidence_type
Select: Certificate · Attendance Register · Email Confirmation · Policy Acknowledgement · Internal Assessment Record · Other
OPTIONAL
notes
Any additional context — e.g., "Retroactive log — training occurred pre-AIMS deployment; evidence: vendor email DD/MM/YYYY"
OPTIONAL
Section 7 — COLP/DPO Verification (Completed by Verifier — See Part C) Read-only for record submitter
Field
Entry
Status
colp_verified
TRUE / FALSE (default: FALSE pending verification)
AUTO
colp_verified_by
Staff code of the COLP or DPO who verified this record
AUTO
colp_verified_date
Date and time of COLP verification (ISO 8601)
AUTO
record_status
Completed / Verified / Overdue / Refresh Required — auto-updated by WF-LIT-003
AUTO
ℹ Retention Note

Training records shall be retained for a minimum of seven (7) years from the completed_date, in accordance with UK Companies Act 2006 record retention obligations and aligned to the EU AI Act's supervisory inspection windows. Records may be destroyed thereafter unless a regulatory investigation is ongoing or the individual is the subject of a professional disciplinary proceeding.

Part C — COLP/DPO Verification Checklist
Training Record Verification: Five-Point Review Protocol
This checklist is completed by the Compliance Officer for Legal Practice (COLP), Data Protection Officer (DPO), or designated responsible officer. Complete one checklist per record verification session. SLA: within 5 working days of training record submission.
5 Verification Points
5 days Verification SLA
WF-LIT-002 Automation Workflow
COLP / DPO Authorised Verifiers
⚠ Warning — Verification Authority

Only the designated COLP, DPO, or an officer formally delegated in the firm's AI governance policy may complete this checklist. Peer verification (e.g., the training record subject verifying their own record) is not permissible and will be flagged as a compliance gap by WF-LIT-003. Delegation must be documented and the delegate's staff code must appear in colp_verified_by.

Verification Record Header

Record ID Being Verified
Staff Code (Subject)
AI System Ref
Verification Date

Five-Point Verification Checklist

Review each point against the submitted training record. Mark each point as PASS, FAIL, or QUERY (requires further evidence before a determination can be made). A single FAIL result means the record cannot be verified and must be returned for correction.

Verification Checklist — REG-AIMS-LIT-001 · WF-LIT-002 Protocol
Ref
Verification Point
Result
V-01
Training Status Confirmation The record status is "Completed" and the completed_date is populated. The record has not already been verified (colp_verified = FALSE). Duplicate or retroactively edited records are flagged for investigation.
V-02
AI System Reference Validity The ai_system_ref corresponds to an active, deployed AI system in the firm's system register. General AI training logged against a retired or undeployed system reference is not a valid Article 4 record for current compliance purposes.
V-03
Evidence Adequacy The evidence_description references a document that exists and is retrievable. Where an evidence_link is provided, the verifier shall confirm the link resolves to the claimed document. Attendance records, certificates, or email confirmations constitute acceptable primary evidence. Internal notes alone do not.
V-04
Competency Level Appropriateness The competency_assessed level is appropriate for the staff member's role and the AI system in question. A partner assessed as "Foundational" for a system they govern daily is a discrepancy requiring investigation. Refer to the competency matrix in Part B if uncertain.
V-05
Refresh Date Compliance The refresh_due_date is correctly calculated (completed_date + 12 months minimum, or system-specific cadence where documented). If the refresh_due_date has passed at the time of verification, the record cannot be verified as current — a new training event is required before this record can contribute to active compliance status.

Verification Outcome and Sign-Off

Outcome: VERIFIED

All five verification points have been assessed as PASS. The verifier confirms the record is accurate, the evidence is adequate, and the competency level is appropriate. The record shall be marked colp_verified = TRUE in REG-AIMS-LIT-001.

Outcome: RETURNED

One or more verification points have been assessed as FAIL or remain QUERY after 5 working days. Record is returned to the submitter with the reason below. A corrected record must be re-submitted and re-verified before it contributes to compliance status.

Verifier Sign-Off
Verifier Name
Verifier Staff Code
Verifier Role / Title
Date of Verification
Outcome (circle):    VERIFIED   /   RETURNED
Reason for return / notes (if outcome = RETURNED)
Verifier Signature
ℹ WF-LIT-002 Integration Note

Where the firm operates the AIMS automation layer, the verification outcome shall also be submitted via the WF-LIT-002 COLP Verification Gate webhook (POST /webhook/lit/verify-record) using the x-aims-colp-key authentication header. The manual sign-off above serves as the primary audit trail; the digital submission updates REG-AIMS-LIT-001 automatically and triggers confirmation emails to the submitter and COLP.

Part D — Overdue Training Monitor Procedure
Daily Monitoring SOP: Detecting and Escalating AI Literacy Gaps
This Standard Operating Procedure defines the daily monitoring cycle for AI literacy compliance, the three compliance gap categories, and the escalation path when gaps are detected. ITIL 4 classification: Recurring Workforce Management Request. Automation reference: WF-LIT-003.
⚠ Warning — Active Gaps Create Active Regulatory Exposure

A staff member using an AI system while their training record is in "NOT LOGGED", "Overdue", or "Refresh Required" status creates an active Article 4 breach for every day that gap persists. The monitoring procedure below is not a best-practice recommendation — it is the minimum viable process for maintaining compliance once REG-AIMS-LIT-001 is operational.

1. Monitoring Schedule

Trigger
Daily — 08:00
Business days only (Mon–Fri). Excludes UK bank holidays.
Process Owner
COLP / DPO
Digest delivered to designated compliance inbox.
Automation
WF-LIT-003
n8n workflow; digest sent only when gaps > 0.

2. The Three Compliance Gap Categories

The monitoring procedure tracks three distinct gap states, each requiring a different response. These categories correspond to the status values in the vw_lit_compliance_gaps database view.

NOT LOGGED
A staff member is registered as a user of a deployed AI system but has no training record in REG-AIMS-LIT-001. This is an immediate Article 4 breach.
→ Immediate action required. Training must be scheduled within 5 working days. Interim access restriction should be considered for high-risk systems.
OVERDUE
A training record exists but the refresh_due_date has passed and no new training event has been logged. The existing record is expired and does not evidence current compliance.
→ Escalation to line manager and L&D. Refresh training required within 10 working days. COLP notified for risk register update.
REFRESH REQUIRED
The refresh_due_date is within the next 30 days. Training remains current but the upcoming expiry creates a forward-looking risk. Anticipatory action prevents the "Overdue" escalation.
→ L&D notification sent. Refresh training to be scheduled within 15 working days. No immediate breach.

3. Daily Monitoring Procedure — Step by Step

01
Automated Gap Detection (08:00 — WF-LIT-003 Node 02)

The daily schedule trigger fires at 08:00. The sp_flag_overdue_training() stored procedure is called against the REG-AIMS-LIT-001 database. This procedure updates the record_status field for all active records where: (a) completed_date exists but refresh_due_date has passed → status set to "Overdue"; (b) no training record exists for a registered AI system user → gap flagged as "NOT LOGGED"; (c) refresh_due_date is within 30 days → status set to "Refresh Required".

02
Compliance Gap View Query (Node 03)

The vw_lit_compliance_gaps view is queried to retrieve all records with status: NOT LOGGED, Overdue, or Refresh Required. Results are grouped by gap status and sorted by severity (NOT LOGGED first, Overdue second, Refresh Required third). If the query returns zero rows, no digest is sent and the workflow terminates cleanly (no-gap confirmation is logged internally).

03
COLP Digest Construction (Node 05)

Where gaps exist, the workflow constructs a structured digest. The digest header contains: date, total gap count, breakdown by status category, and the firm_id. Each gap record includes: staff_code, staff_name, role_title, ai_system_ref, gap_status, days_since_due (for Overdue), days_until_due (for Refresh Required). For NOT LOGGED gaps, the date the staff member was registered as a system user is included.

04
COLP Email Notification (Node 06)

The digest is delivered to the COLP's designated compliance inbox. The email subject line includes the gap count and highest-severity category to enable triage without opening: e.g., "REG-AIMS-LIT-001 Daily Digest — 3 gaps (2 NOT LOGGED, 1 Refresh Required) — 01 Sep 2026". The email is sent only when total_gaps > 0; the workflow is silent on zero-gap days.

05
COLP Response and Escalation (Human Step — within 24 hours of receipt)

Upon receiving the digest, the COLP shall: review each gap entry; for NOT LOGGED items — contact the relevant line manager and L&D team to schedule training within 5 working days and consider whether the staff member's AI system access should be restricted pending training completion; for Overdue items — initiate the refresh booking and update the risk register; for Refresh Required items — confirm that a booking is in the L&D pipeline. The COLP shall record the action taken against each gap in the risk register within the same business day.

06
L&D and Line Manager Notification (Human Step — same day as COLP action)

The COLP notifies the relevant L&D lead and line manager of each gap. Notification shall include: the staff member's name and code, the AI system reference, the gap status, and the required action deadline. For firms using the AIMS automation layer, a supplementary WF-LIT-001 pre-populated draft can be sent to the future training provider to accelerate logging on completion.

07
Gap Closure Confirmation (on training completion and COLP verification)

A gap is closed when: (a) a new training record is submitted via WF-LIT-001 and the completed_date populates; (b) the COLP verifies the record via WF-LIT-002; (c) the record_status updates to "Verified". The gap will no longer appear in the vw_lit_compliance_gaps view for that staff/system combination. The audit log (lit_audit_log) retains a full history of gap detection, escalation, and closure events for regulatory inspection purposes.

4. Escalation Thresholds

Threshold
Trigger Condition
Escalation Action
Level 1
1–3 gaps (any status) · COLP informed
COLP manages directly. Standard action within SLA.
Level 2
4–9 gaps OR any NOT LOGGED gap persisting > 5 working days
Risk register entry. Head of L&D formally notified. COLP reports to Managing Partner / Board within 5 days.
Level 3
10+ gaps OR NOT LOGGED gap persisting > 10 working days on an Annex III high-risk system
Formal incident raised. External legal counsel consulted. Consider voluntary disclosure to regulator. System access suspended pending resolution.
Critical
Regulatory inspection confirmed and gaps remain open in any category
Immediate crisis protocol. All open gaps are the primary litigation risk. Legal privilege advice obtained before any submission to regulator.

5. Record Keeping for This Procedure

The COLP shall maintain a Monitoring Action Log documenting: the date of each daily digest received, the gap count by category, and the action(s) taken. This log is a separate document from REG-AIMS-LIT-001 and serves as evidence that the monitoring procedure was operated in good faith. In a regulatory inspection, the Monitoring Action Log demonstrates proactive management, not merely passive record keeping.

Procedure Owner
Review Date
Version
Approved By
Part E — Regulator Evidence Pack
Cover Sheet Template: Article 4 Evidence Submission
This cover sheet is completed when submitting AI literacy evidence to a regulator, panel client governance team, external auditor, or ISO 42001 certification body. Attach the completed cover sheet as the first document in any evidence bundle. Complete in typed form — handwritten submissions are not recommended for regulatory inspection purposes.
⚡ Caution — Seek Legal Advice Before Regulatory Submission

Where a submission is made to a regulatory body as part of an enforcement investigation (as opposed to a routine audit or self-assessment), firms should obtain legal advice before submitting. This cover sheet is a presentation aid; it does not constitute legal advice and does not determine what must or should be disclosed.

Evidence Pack Cover Sheet

[ORGANISATION LEGAL NAME]
AI Literacy Compliance Evidence Pack
Compiled pursuant to EU AI Act Article 4 · Regulation (EU) 2024/1689
CONFIDENTIAL — PREPARED FOR REGULATORY/AUDIT PURPOSES

Section 1 — Submitting Organisation

Legal Name of Organisation
Registered Number (Companies House / SRA / FCA)
Registered Address
Sector / Regulatory Classification
Primary Regulatory Body
Compliance Contact (COLP / DPO / CCO)

Section 2 — Submission Details

Recipient (Regulator / Auditor / Panel Client)
Reference / Case Number (if applicable)
Date of Submission
Evidence Period Covered (From — To)
Total Number of Staff Covered
Total Number of AI Systems in Scope

Section 3 — Document Index

Tab
Document
Version
Pages / Records
A
AI Literacy Policy — [policy reference]
v______
______
B
REG-AIMS-LIT-001 Training Register Extract (all COLP-verified records in period)
v______
______ records
C
COLP Verification Checklists (sample or full set as requested)
—
______ records
D
Primary Evidence Samples (certificates, attendance records — see attached index)
—
______ items
E
AI System Register (list of deployed systems with AIMS-SYS references)
v______
______
F
Monitoring Action Log (overdue management evidence — COLP daily review)
—
______ entries
G
Additional documents as specified by requesting body
—
—

Section 4 — Compliance Status Declaration

The undersigned, being the [COLP / DPO / Chief Compliance Officer] of [ORGANISATION NAME], hereby confirms that:

  • The organisation has taken measures to ensure a sufficient level of AI literacy among staff and persons operating AI systems on its behalf, in accordance with Article 4 of Regulation (EU) 2024/1689.
  • The training records presented in this evidence pack are accurate and complete to the best of the signatory's knowledge as at the date of submission.
  • All records marked "COLP Verified" in REG-AIMS-LIT-001 have been reviewed by an authorised officer and the supporting evidence was available and adequate at the time of verification.
  • Open compliance gaps identified by the monitoring procedure (if any) are identified and described in the accompanying gap schedule, together with the remediation actions taken or planned.
  • The organisation understands that the submission of inaccurate, misleading, or incomplete information to a regulatory authority may constitute a regulatory breach independently of the underlying compliance position.
Signatory Name
Role / Title
Date
Signature
Organisation Stamp (if applicable)

Guidance: Presenting the Evidence Pack to a Panel Client

Panel clients issuing AI governance questionnaires (such as the Pemberton Capital LLP Section 7 questionnaire scenario) are not regulators and the submission does not carry formal legal privilege considerations. However, the same discipline applies: the training register extract and verification checklists should be presented as evidence of what was done, not as assertions of what the firm intends.

When the questionnaire asks: "What AI literacy training have staff completed?"

Provide the REG-AIMS-LIT-001 extract filtered to the systems relevant to the client's matter. Do not provide a policy document in response to a training completion question — it answers a different question.

When the questionnaire asks: "How does your firm ensure AI literacy obligations are met on an ongoing basis?"

Describe the three-workflow monitoring cycle (WF-LIT-001 intake → WF-LIT-002 verification → WF-LIT-003 daily monitoring) and provide the Monitoring Procedure (Part D of this pack) as a supporting document.

ℹ ISO/IEC 42001 Certification Note

Where the organisation is pursuing ISO/IEC 42001:2023 certification, this evidence pack satisfies the documented evidence requirement at Clause 7.2(d). Provide it to the certification auditor as tab D of the Clause 7.2 evidence bundle, together with the AI Management System competency needs assessment (if separately prepared).