How compliance analysts can complete the operator practicum

Switch from testing controls to making the decisions they protect. The practicum gives a compliance analyst two weeks of an agent's held banking work to decide, item by item, with a reason for each. You pass with nineteen correct decisions in twenty and no missed red line, such as approving a reply that ignores a customer's disclosed vulnerability. A Pryme assessor signs it off.

Why does the practicum feel different to a compliance analyst?

Compliance work usually sits one step back. You sample decisions, test controls and report on whether the first line is doing its job. The practicum puts you in the first line. Each held item needs a decision now, and a queue that waits while you research is itself a failure of service.

The practicum is the second half of Certified Pryme Operator, after the written exam. If your bank uses Pryme you can do it on the live workspace; otherwise, and if you are between roles, a simulated queue in a free workspace is used, as doing the operator practicum without a job explains. The explainer on what the operator practicum is covers its design, and the guide to AI operator certification shows the full route.

What will the queue contain?

• servicing replies and account changes drafted by the agent;
• refunds and fee reversals, some above the bank's limit;
• refusals you need to confirm were correct;
• an action blocked at the platform floor, which no reviewer can release;
• customer messages showing vulnerability or possible coercion;
• documents from outside presented as proof, such as an emailed letter from a "solicitor";
• outbound customer messages making claims about products or rates;
• routine items that should simply be approved.

Approve the routine items promptly. An analyst who escalates everything has not shown judgement.

How do you decide each item?

1. Agent, depth 1: has read the request, record and permitted procedures, each stamped with provenance: sealed, signed, declared or external.
2. Agent, depth 2: has drafted the reply or change. Check it against the procedure and the customer's circumstances.
3. You: decide: approve, edit, hold, escalate or reject.
4. You: write a one-line reason.
5. Refusals: where the agent refused, confirm which bound decided and whether that was right. Do not look for a way around a correct refusal.
6. Withheld actions: recognise them. They are refused on purpose at the platform floor for every agent at every depth; the right decision is to route the customer's need through the proper process.
7. Assessor: reviews your decisions, reasons and red-line record.

Which red lines should you expect?

• A reply that ignores a disclosed vulnerability or signs of coercion.
• A contact change and payment request approved together without verification.
• An action authorised by an external document alone. An external claim cannot authorise a payment.
• A refund or transfer above the limit released without authority.
• Attempting to work around a withheld action or a correct refusal.

One missed red line ends the attempt, however accurate the rest.

How long should a reason be?

Shorter than a compliance finding. One line, naming the evidence and, where relevant, the bound:

• Weak: "Reviewed against policy; no issues identified at this stage."
• Strong: "Rate quoted matches approved product sheet; approved."
• Strong: "Request relies on emailed letter from third party; external; held for verification."
• Strong: "Refused at bank's own refund limit; correct; routed to approver."

Save longer thinking for a private notes file. It is useful for interviews later, and it keeps the queue moving now.

What should you track over the two weeks?

Keep a list of items where you hesitated, and check each evening which rule decided them. Compliance analysts often hesitate on items that are simply routine, out of habit. If most of your hesitations end in "approve", trust yourself more in week two. With 200 decisions, nineteen in twenty allows ten wrong; none may be a red line.

The operator practicum preparation checklist helps you plan: time blocked, red lines learned, a log ready.

Where do compliance analysts usually slip?

• Researching instead of deciding. The evidence in the case is what you decide on.
• Over-escalating. Escalation without a reason counts against you as surely as a wrong approval.
• Treating a withheld action as a policy question. It is a platform decision, not a customer setting, and not for the reviewer to reopen.
• Writing findings, not reasons.

KYC analysts and business analysts meet the same standard with different habits; see how KYC analysts can complete the operator practicum and how business analysts can complete it.

Where the Academy fits

Pryme Intelligence Academy's Operator certificate gives a compliance analyst first-line evidence to sit alongside second-line experience. For analysts who later want to design oversight for regulated, multi-agent deployments, the Architect track follows Builder and ends in a board review with two Pryme assessors.