A compliance officer overseeing AI agents needs four competences: reading an agent's certificate and depth decisions, reviewing items held for compliance approval, testing controls by re-performing decisions, and reconstructing any verdict from the record. This plan maps each competence to learning, a practicum, the evidence it leaves, and renewal, so the officer can challenge the business with knowledge.
What is this plan for?
Compliance officers meet agents in two ways. As reviewers, they decide items the agent holds for compliance: customer communications, complaint outcomes, financial promotions, policy exceptions. As oversight, they challenge the business's decisions about the agent: is the depth earned, are the customer limits right, are the people approving held actions competent?
Both need hands-on understanding. An officer who has never decided a held item cannot judge whether a team's approval pattern looks healthy, and one who cannot read a certification result cannot challenge a request for more depth. A plain introduction to the discipline is in what is compliance training?; this plan is narrower. For the time involved, see how long it takes to train compliance officers to supervise AI agents.
How do you fill it in?
One row per competence. For each, describe the learning, the practice on real work, and the evidence it produces. The final column, "Used for", connects the competence to a decision the officer will actually take, which keeps the plan honest.
The template
| Competence | Learning | Practice on real work | Evidence | Assessed by | Used for | Renewal |
|---|---|---|---|---|---|---|
| Vocabulary and the decision chain | ||||||
| Reviewing compliance-held items | ||||||
| Testing controls | ||||||
| Reading certification and depth decisions | ||||||
| Reconstructing decisions from the record | ||||||
| Leading regulated multi-agent deployments (head of compliance only) |
A worked example
A hypothetical consumer credit firm's compliance team of four, overseeing a servicing agent and a collections agent. Values are samples.
| Competence | Learning | Practice on real work | Evidence | Assessed by | Used for | Renewal |
|---|---|---|---|---|---|---|
| Vocabulary and the decision chain | Foundations, about 4 hours | Explains the chain for five sample verdicts | Foundations badge | Foundations test | Every oversight conversation | No expiry |
| Reviewing compliance-held items | Operator track, about 14 hours | Two-week practicum on held customer letters and complaint outcomes | Certificate number | Pryme assessor: at least 95 in every 100 decisions correct, no missed red line | Approving held communications | Every 12 months |
| Testing controls | Operator modules on human review and reading the workspace | Re-performs 25 held decisions made by collections reviewers and compares | Control test workpaper | Head of compliance | Quarterly monitoring | Each quarter's test |
| Reading certification and depth decisions | Operator modules on how a governed agent decides | Reviews the Attest results behind the last depth change | Challenge memo | Head of compliance | Challenging depth increases | At each request |
| Reconstructing decisions | Operator module on when something goes wrong | Traces three complaints back through the record to the bound that decided | Trace notes | Internal audit | Complaint investigations | Annual |
| Leading deployments | Architect, about 30 hours plus capstone and board review | Capstone across both agents | Certified Pryme Architect | Two Pryme assessors | Owning the compliance view of the agent programme | Every 24 months |
The control-testing row is where compliance adds most. Re-performing 25 decisions means opening each held arrangement, deciding it independently, and comparing with what the reviewer did. If reviewers approve everything the agent drafts, the test shows it. If they refuse sound drafts, it shows that too. Neither pattern is visible from a dashboard of approval counts.
The certification row matters at the moment of challenge. When the business asks to move arrangement-setting from depth 2 to depth 3, the officer should read which of Attest's gates the agent cleared on the firm's own cases and by how much, and ask whether the people approving its held work are certified and current. Depth is earned, not configured, and compliance is often the function best placed to insist on it.
Plans for roles compliance officers often oversee are the training plan template for loan officers and the training plan template for procurement officers. Keep the team's own judgement aligned through calibration sessions for compliance officers, and see the team-wide approach in training teams for AI agents.
Where the Academy fits
Pryme Intelligence Academy offers each step in this plan: Foundations for the vocabulary, Operator for compliance reviewers, and Architect for the head of compliance leading a regulated, multi-agent deployment. Certificates are issued through VerifyDoc.ai, and a public register lists certified people by name, credential and expiry, which supervisors and auditors can check themselves.
Questions people ask
Should compliance officers approve held items at all?
Only items where compliance approval is the control, such as financial promotions or complaint outcomes. Approving routine operational items blurs the line between doing and checking.
How often should compliance re-perform reviewers' decisions?
Quarterly is common, and more often for depth 4 capabilities. Increase the sample after any incident or depth change.
What if compliance and operations disagree on a held item?
Record both views and escalate to the agent owner. Repeated disagreement on a type of item usually means the agent's brief or the customer limits need changing.