PrymeIntelligence

AI operator certification·Template

Operator practicum preparation checklist

An operator practicum preparation checklist: the workspace, time, red lines, reference notes and decision log to have ready before the two weeks start.

Before your two-week operator practicum starts, have five things ready: a working queue (live or simulated), protected time every day, a list of the red lines you must never miss, your reference notes from the modules, and a log for your decisions and reasons. The checklist below turns that into items you can tick off in the week before.

Why prepare at all for a practicum?

Because the standard is high and the clock is running. The practicum asks for two weeks of review decisions, nineteen in twenty correct and no missed red line, signed off by an assessor. A missed red line is the failure that matters most, and it usually happens when someone is rushing a queue they have not set up properly or reviewing in ten-minute gaps between other work.

Preparation is mostly about removing those risks before day one. If you are new to the idea, read what the operator practicum is first, and why the practicum is what makes an operator certificate worth having.

How do you use this checklist?

Work through it in the week before you start. Tick each item only when it is done, not planned. If you cannot tick something, such as protected time, move your start date rather than begin under strain. Keep the finished checklist with your decision log; your assessor may ask how you prepared.

People without a job that uses Pryme do the practicum on a simulated queue in a free workspace. If that is you, the guide on doing the operator practicum without a job covers the set-up.

The preparation checklist

Access and queue 1. Workspace open and you can sign in: [live employer workspace / free workspace with simulated queue] 2. Queue confirmed: you can see held decisions and act on them 3. Your role in the workspace lets you approve, amend, reject and escalate 4. You know where each decision record is stored and how to open one

Time 5. Daily review slot booked for all ten working days: [time] 6. Your manager or household knows those slots are protected 7. A backup slot each week in case one is lost

Red lines and rules 8. A one-page list of the red lines for your queue, written in your own words 9. The escalation route for each type of red line: who, how, how fast 10. The sector rules that apply to your cases, summarised briefly

Reference notes 11. Your notes on depth, the decision chain and the four verdicts 12. Your notes on provenance: which sources can be trusted for what 13. Your gap list from the module tests, with the fixes

Your log 14. A decision log ready: date, case reference, agent's proposal, your decision, reason, red line checked (yes or no) 15. A daily review slot of ten minutes at the end to check your own decisions

What do the red lines look like in practice?

They depend on the queue. In a bank's servicing queue, they might be any payment to a newly added payee, any action on an account flagged for possible fraud, and any message to a customer flagged as vulnerable. In a recruitment queue, they might be any rejection based on a protected characteristic and any personal data sent outside the firm. The guides for bank tellers and recruiters show the differences in detail.

Write them before you start, not during. A red line you have to look up mid-case is a red line you might miss.

A filled sample

A recruiter we will call Noor, working at an invented agency, prepares for a practicum on a simulated recruitment queue:

  • Access: free workspace with simulated queue; signed in and opened three sample decision records. Ticked.
  • Time: 8.00 to 9.30 every weekday before work; partner aware; backup slot Saturday morning. Ticked.
  • Red lines: (1) no candidate rejected for a reason linked to age, disability, pregnancy or other protected characteristic; (2) no CV or personal details sent to a client without the candidate's consent; (3) no offer terms sent without a person's approval. Escalation: to the simulated team lead, same session. Ticked.
  • Reference notes: one page on depth and verdicts; one on provenance, with the note that a candidate's own claim is declared, not verified. Ticked.
  • Gap list: usage reports and refused versus withheld, both revised. Ticked.
  • Log: spreadsheet set up with the seven columns. Ticked.

Noor's provenance note is a sharp one. A candidate's statement about their right to work is declared information; it is not a check, and an agent should not treat it as one.

Where the Academy fits

The practicum is the second half of Pryme Intelligence Academy's Operator certificate, after the written exam. A Pryme assessor signs off your decisions against the standard. If you do not have a job that uses Pryme, the simulated queue runs in a free workspace, so nobody is shut out for lack of an employer.

Questions people ask

Can I pause the practicum if something comes up?

Plan as though you cannot. If a real emergency happens, raise it with your assessor at once rather than rushing decisions to keep pace.

Does speed count?

Accuracy and red lines count. A slow, correct, well-explained decision is worth more than a fast one, so do not race the queue.

What happens if I miss a red line?

The standard requires none missed, so that run would not meet it. Log what happened and why, and talk to your assessor about next steps; the guide to AI operator certification explains how the whole route fits together.

Get certified to run governed AI agents.

Pryme Intelligence Academy: free lessons you can read or listen to, labs in a free workspace, and Certified Pryme Operator, a certificate any employer can check on VerifyDoc.ai.