A data entry clerk can prepare for the AI operator exam in five weeks of four-hour weeks: Foundations first, then the eight Operator modules with their module tests, then one week of timed practice. The exam has 40 questions in 60 minutes, and the pass mark is four in five, so 32 correct.
What do you already know, and what is new?
You already know more of the exam than you think. Checking a record against its source is the habit behind provenance, the idea that every fact reaching an agent is stamped with where it came from. You already distinguish a weight printed on a weighbridge ticket from a weight someone told you on the phone. The exam just names the classes: sealed, signed, declared and external, strongest first.
What is new is the system around the record. You will need to explain depth (how far an agent may act), the five bounds of the minimum chain, the four verdicts, and why depth is earned through certification rather than switched on. The summary of what is on the AI operator exam sets out the full scope.
The five-week plan
The material is about 4 hours for Foundations and about 14 for Operator. Five weeks at roughly four hours a week is enough with a little to spare.
- You, week 1: Foundations, all six modules. On its own it carries little weight on a CV, but it is the key to the Operator track and earns a free badge with no expiry.
- You, week 2: Operator modules on how a governed agent decides and on human review. Then the module tests.
- You, week 3: teaching the agent, reading the workspace, keeping knowledge current. Do each lab in the free Build workspace. Pay attention to how a correction changes the agent's sources or brief, never the model itself.
- You, week 4: when something goes wrong, usage and billing, running the rhythm. Then retake the weakest two module tests.
- You, week 5: timed practice. Write ten questions a day from your notes and answer them at 90 seconds each. Sit the exam at the end of the week.
How do logistics records map to depth?
Most wrong answers on depth come from blurring "drafts" and "does". Anchor each depth to a record you have handled.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Reading a proof of delivery | Reads and classifies | 1 | Nothing unless unclear |
| Drafting a consignment record | Drafts and holds | 2 | Checking and approving |
| Posting a status from the carrier feed | Executes within bounds | 3 | Exceptions and sampling |
| Paying a carrier invoice | Prepares, held for approval | 4, held | A named approver |
| Changing supplier bank details from an emailed PDF | Refuses: external claim | refused | Verification by a person |
The last row tests two ideas at once. The emailed PDF is external, and an external claim cannot authorise a payment. And the verdict is refused, because the action falls outside the agent's bounds, not withheld. Withheld is reserved for actions the platform blocks for every agent at every depth.
How should you use the module tests?
Module tests are set in your own industry and role, so you will see shipment, invoice and customs situations. Mark each one, then sort your misses into three piles: vocabulary (you did not know the term), rules (you knew the term but not how it applies), and reading (you knew both but misread the question). Each pile needs a different fix: flashcards, rereading the module, or slowing down.
Clerks tend to score well on provenance and lose marks on the "when something goes wrong" module, which covers what happens when an agent's run clears no depth and drops to depth 1, and how a person handles the backlog. Give that module extra time.
Which controls must you be able to explain?
- Held drafts: stop a record entering the system of record until a named person approves; evidence is the approver's name.
- Provenance tags: show which fields came from where; evidence is the tag beside each field.
- Certificate lapse: an agent's certificate lapses after 90 days; a run that clears no depth drops it to depth 1 that day; evidence is the certificate status on the record.
- The append-only record: every verdict is filed, so a disputed delivery can be reconstructed months later.
What should you do on exam day?
Arrive rested and without a shift in front of you. Sixty minutes for 40 questions is 90 seconds each. Read the whole question, then every option; on verdict questions, two options often differ only in which bound decided.
Do not change answers on a hunch. Change one only if you can say what you misread.
What should you measure while preparing?
Your module test scores, and especially the second attempt on the weakest ones. Count how many questions in your own timed practice you finish in 90 seconds. If you are reliably above 34 out of 40 in practice and finishing on time, you are ready.
Where does preparation usually go wrong?
Studying only the definitions. Clerks are good at memorising codes, and it is tempting to treat depth levels as codes. The exam asks you to apply them to situations, so practise with scenarios from your own work.
Ignoring the practicum. The exam and practicum test the same understanding from two sides. Read how data entry clerks complete the practicum before week 5. Accounts payable clerks follow a close variant of this plan in preparing for the operator exam as an accounts payable clerk.
Questions people ask
Can I prepare in my lunch breaks?
Yes. Lessons can be read or played as audio, with highlights and notes, so short sessions work. Keep labs for a longer sitting, because they need concentration.
Is the certificate a licence to work in logistics?
No. Certified Pryme Operator is a professional certificate, not a government licence. It shows an employer you understand governed agents and have made review decisions to a standard; employers can check it at source.
What jobs should I search for afterwards?
Titles vary, so search by duties: review, exceptions, data quality, approvals and escalation. Guides for data entry clerks in the UK and the UAE show the range, and the AI operator certification guide explains what the certificate proves.