Decide the case in front of you, then note the pattern. For two weeks you work an agent's held banking items, deciding each with a reason. You pass with nineteen correct decisions in twenty and no missed red line, such as releasing a refund above the bank's limit. Your instinct for root causes helps, but only after the decision.
Why is the practicum different for an analyst?
Business analysts are used to studying a process from above: mapping it, finding where it breaks, proposing changes. The practicum puts you inside the process. You work a queue of individual items an agent could not finish, and each needs a decision now: approve, edit, hold, escalate or reject. Analysis paralysis costs time, and a queue that waits is itself a problem.
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 a simulated queue in a free workspace is used, to the same standard. A Pryme assessor signs off the result. The explainer on what the operator practicum is covers the design, and the guide to AI operator certification shows where it fits.
What will a retail banking queue contain?
- drafted replies to customer servicing questions;
- contact detail changes and card orders;
- fee refund requests above and below the bank's limit;
- complaint summaries prepared for a case handler;
- drafts that cite a procedure which has since changed;
- refusals by the agent that you need to confirm were right;
- messages showing vulnerability or possible fraud;
- a run of similar holds that hints at a problem in the agent's sources.
Most items should be approved as drafted. The analyst's trap is to find something to improve in each one. Improvement is welcome; it is not the same as a wrong draft.
How do you work each decision?
- Agent, depth 1: has read the request, the customer record and permitted procedures. Check provenance: the procedures library is sealed, the customer's account of events is declared, an attachment from outside is external.
- Agent, depth 2: has drafted the reply or change. Read the evidence it cites.
- You: decide, within a reasonable time.
- You: write a one-line reason.
- You: if the case points to a wider cause, add a separate pattern note. Keep it apart from the decision.
- Agent, depth 4, held: refunds and money movements wait for a named approver. Decide whether release conditions are met.
- Assessor: reviews your decisions, reasons and red-line record.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Reading | Pulls stamped sources | 1 | Judging source strength |
| Servicing replies | Drafts | 2 | Approve, edit or hold |
| Routine changes | Completes within limits | 3 | Sampling |
| Refunds above limit | Prepares and holds | 4, held | Authorised release |
| Out-of-scope requests | Refuses, naming the bound | none | Confirming the refusal |
| Pattern across many holds | Logs every verdict | 1 | Your pattern note and proposed change |
Which red lines apply in a banking queue?
A single miss ends the attempt:
- A contact detail change followed by a payment request, approved without verification.
- A refund or transfer above the limit released without the right authority.
- A reply that ignores a disclosed vulnerability.
- An action authorised by an external document, such as an emailed letter claiming to be from a solicitor.
- Overriding a refusal that rightly blocked an out-of-scope action.
How should an analyst write reasons?
Analysts often write too much. One line is enough; put the extended thinking in your pattern notes.
- Weak: "Approved after review of the process flow."
- Strong: "Fee charged in error per account history; refund within limit. Approved."
- Strong: "Draft cites old overdraft procedure; source superseded; edited to current rule and flagged for source update."
What should you track during the fortnight?
Keep two lists. The first is your decisions and the ones you were unsure of; review them each evening. The second is your pattern notes: repeated corrections, stale sources, limits that seem wrong. At the end, the second list is valuable evidence of the analyst's contribution, and good material for interviews, but it does not count towards the nineteen in twenty. The first list does.
Plan steady time each day. A practicum squeezed around requirement workshops produces hurried decisions.
Time yourself on the first day. If most items take you several minutes, you are analysing rather than reviewing. Aim for a steady pace where routine items take moments and only the hard ones take longer.
Where do business analysts usually slip?
- Spending too long per item. Decide, note, move on.
- Editing drafts that were fine. Changing correct wording to preferred wording is not an error, but it wastes time and can introduce one.
- Mistaking a pattern for a decision. "Process is unclear" is not a decision on the customer's request.
- Underrating red lines. Analysts sometimes treat them as edge cases. In the practicum, they decide the outcome.
Colleagues in risk roles bring a different instinct to the same queue; see how fraud analysts can complete the operator practicum and how compliance analysts can complete it. For market context, read AI operations careers for business analysts in Singapore.
Where the Academy fits
Pryme Intelligence Academy's Operator track is the key to the Builder track, where people design, train and certify agents. For an analyst who wants to shape how agents work, the practicum is the necessary first proof that you understand how reviewers use them day to day.
Questions people ask
Will my pattern notes be assessed?
The standard is about your decisions and red lines. Pattern notes are still worth keeping: they show how you would improve the agent, which employers value.
Can I skip the practicum if I plan to be a builder?
No. Each track is the key to the next, so Operator, including the practicum, comes before Builder.
What if I disagree with how a case is set up?
Decide it on the evidence given and note your concern. The practicum tests decisions on the case as presented.