A compliance officer's practicum log records each sign-off decision on an AI agent's held work over two weeks: customer communications, complaint classifications, possible breaches and policy exceptions. Each entry names the rule or policy relied on, the officer's decision and reasoning, a second reviewer's independent decision, and whether a red line was involved. The example is from a sample lender.
What makes a compliance practicum different?
The officer is reviewing for a different question from everyone else in the chain. An operations reviewer asks "is this right for the customer and the business?" A compliance officer asks "does this meet the rules, and if something went wrong, have we recorded and escalated it properly?" So the log needs a column most practicum logs lack: the rule or policy the decision rests on.
Volume is modest and items vary. A fortnight might bring 80 to 120 decisions, many of them short. The items that matter most are the rare ones: a possible breach that has to be escalated, or an exception request that sits outside policy. The run of the two weeks is covered in how to run a two-week practicum for compliance officers.
What does the AI agent hand the compliance officer?
In a typical deployment:
- Customer communications: letters, messages and web text drafted at depth 2 and held for compliance sign-off before use.
- Complaint classification: the agent proposes whether a contact is a complaint and its category.
- Breach candidates: the agent flags events from the record that may be reportable, and drafts the breach log entry.
- Exception requests: a team asks to step outside a policy for one case, and the agent drafts the request with the facts.
- Disputed refusals: a team challenges a refusal and asks compliance to rule.
The practicum log template
Header
- Officer; second reviewer with a current certificate; dates; scope; bar of at least 95 correct in every 100 and no missed red line.
- Red lines: approving a customer communication that is unclear, unfair or misleading; failing to escalate a potentially reportable breach the same day; approving an exception outside the officer's authority.
Entry fields
- Entry number and date.
- Item type.
- What the agent drafted or flagged, with its verdict and deciding bound.
- Rule or policy relied on: internal policy reference, and the regulatory expectation in substance.
- Facts and their provenance: sealed (the system of record), signed, declared or external.
- Officer's decision: approve, amend, reject, escalate.
- Officer's reasoning.
- Second reviewer's decision, recorded before reading the officer's.
- Match: yes, no or defensible.
- Red line involved: none, caught or missed.
- Debrief note.
A worked example
Take a sample consumer lender in the UK, where the FCA's Consumer Duty sets the expectation of good outcomes for retail customers. Values are illustrative.
| No. | Item | Agent's draft or flag | Officer | Reviewer | Match | Red line |
|---|---|---|---|---|---|---|
| 31 | Customer letter | Arrears letter saying "legal action will follow" if no payment in 7 days | Amend: legal action is possible, not certain; add help options and contact routes | Amend, same points | Yes | Caught |
| 32 | Complaint classification | Contact classed as a "query" about a fee | Reclassify as a complaint: the customer says the fee was not disclosed | Same | Yes | None |
| 33 | Breach candidate | 40 customers sent an arrears letter after their plan was agreed | Log as minor; no escalation | Escalate today: possible customer harm, assess reportability | No | Missed |
| 34 | Exception request | Waive the early settlement fee for a customer in hospital | Approve, within authority up to 500 | Approve | Yes | None |
Entry 33 fails the bar. The officer read the agent's draft breach entry, which described the event accurately, and accepted its "minor" rating without asking what the customers experienced. The debrief note reads: "Rate on customer impact first, volume second."
Entry 31 shows a skill specific to compliance review of agent drafts. The agent's language was copied from an older template in its sources; the fix belongs in the knowledge as well as in this letter. The officer's debrief note adds a request to retire the old template.
How do compliance logs connect to others?
Compliance officers often review the same items other roles approved first, so their logs sit alongside procurement and lending logs in the same organisation. Compare the practicum log for procurement officers, where the red lines centre on supplier due diligence, and the log for loan officers, which shares the communications risk. A lender running both practicums can align them using how to run a two-week practicum for loan officers.
Where the Academy fits
Pryme Intelligence Academy's Certified Pryme Operator requires two weeks of real review decisions, at least 95 in every 100 correct with no missed red line, signed off by a Pryme assessor. Compliance teams that lead regulated, multi-agent deployments may look further, to the Architect track. The guide to AI literacy and certification for people who work with agents explains both.
Questions people ask
Who should the second reviewer be?
A senior compliance officer with a current certificate, ideally not the officer's line manager. For breach items, the person who decides reportability should see the entry too.
Does the officer need to know how the agent works?
Enough to read a verdict, its deciding bound and the provenance of each fact. Without that, an officer cannot tell whether a problem is in the draft, the source or the agent's limits.
If a compliance officer passes, are they accountable for what the agent produces?
They answer for what they sign off. The broader question is covered in are compliance officers accountable for an AI agent's mistakes.