How procurement officers can complete the operator practicum

Public sector procurement officers complete the operator practicum by reviewing a procurement agent's held work for two weeks: requisitions, quote comparisons, supplier onboarding, tender clarification replies, contract variations and invoice matches. Each decision needs a reason. Nineteen in twenty must be correct and no red line missed, and a Pryme assessor signs off the log.

Why is public procurement a distinctive practicum?

Two things set it apart. Public bodies carry extra duties of transparency and fair treatment, so a reply that helps one bidder more than another is not just bad practice but a breach of the process. And the money is public, so every approval may be examined later by auditors or the public. A procurement agent can draft clarifications, compare quotes, check supplier documents and match invoices, but it cannot be the one who decides whether the process was fair.

The practicum is half of Certified Pryme Operator; the written exam is the other. If your organisation uses Pryme you work its live queue; if not, a simulated public procurement queue in a free workspace. The general format is in what the operator practicum is.

What will the queue contain?

• Purchase requisitions from departments, with the agent's proposed route (direct order, quotes, or tender).
• Quote comparisons the agent has scored against stated criteria.
• Draft replies to bidders' clarification questions during a live tender.
• New supplier onboarding files with insurance, registration and bank details.
• Contract variations: extra scope, extended dates, price changes.
• Invoices matched to orders and receipts.

Provenance helps you weigh each document. The organisation's finance and contract registers are sealed. A supplier's registration confirmed with the registering body is signed. A department's description of its need is declared. A bidder's emailed question, or a supplier's emailed bank change, is external.

The steps

1. Agent, depth 1: reads the requisition or document and links it to budget, contract and supplier records.
2. Agent, depth 2: drafts the route, comparison, reply or variation and holds it, naming the deciding bound.
3. You: check the rule behind the route, such as thresholds and the requirement for competition.
4. You: check fairness: would this reply or decision treat every bidder the same?
5. You: decide: approve, edit, reject or escalate to the head of procurement or the budget holder.
6. You: write the reason.
7. Named approver: signs off awards, variations above your authority and payments.
8. Agent, depth 1: files each verdict in the append-only record for the assessor.

Which red lines must you never miss?

• Splitting a requirement into smaller orders to stay below a competition threshold.
• Sending a clarification answer to one bidder and not the others, or one that reveals another bidder's information.
• Approving a variation that changes the contract beyond what the original award allowed, or beyond your authority.
• Onboarding a supplier, or changing their bank details, on unverified documents.
• Approving an award where an evaluator has a declared conflict of interest that was not handled.

Any one fails the practicum.

What does a worked decision look like?

An illustrative case. A department raises three requisitions in a week for laptops from the same supplier, each just under the threshold for quotes. The agent, looking at each one alone, drafts direct orders. You look across the queue, see the pattern, and reject all three with the reason "same requirement split across three requisitions; combined value above quote threshold; returned to department to run quotes". That decision protects the department and the organisation, and it shows the assessor you read the queue as a whole.

How should you write reasons?

State the rule and the evidence. "Clarification answer adds no information beyond the published specification; to be issued to all bidders; approved." A practicum log template for procurement officers gives you a parallel record format.

Which controls protect the process and you?

• Held awards and variations. Evidence: the named approver.
• Provenance tags. Evidence: whether supplier details are signed or merely emailed.
• Uniform clarification replies. Evidence: the distribution list on each reply.
• Append-only record. Evidence: a trail an auditor can reconstruct, which public bodies need.

What should you measure?

Correct decisions over total, by item type. Split requisitions caught. Clarifications edited for fairness. Time to process requisitions.

Where does it usually go wrong?

Judging each item alone. Procurement risk often shows across items, not in them. Read the queue as a whole at least once a day.

Rewriting clarifications so heavily that they add new information. If the answer changes the requirement, it needs the head of procurement. Team leaders and recruiters face different queues with similar fairness duties in how team leaders complete the practicum and how recruiters complete it.

Where the Academy fits

Pryme Intelligence Academy runs the practicum to the same standard on live and simulated queues. Its Operator modules on human review and when something goes wrong prepare you for exactly these decisions. The AI operator certification guide explains what the issued certificate proves to an employer.