How to onboard a new procurement officer to an AI agent workspace

Procurement officers new to an agent workspace learn the thresholds before the tools. Week one covers the spend limits and approval routes the agent works within, the supplier list it reads, and how it scores quotes. Week two brings held orders, supplier checks and quote comparisons, each checked by a category manager. Award decisions stay with experienced staff.

What does the procurement agent do?

In a procurement team with agents, the agent typically raises catalogue orders from approved requisitions within spend limits (depth 3), drafts orders above those limits for a person to approve (depth 2), checks new suppliers against onboarding requirements, and compares quotes against each category's evaluation criteria. Contract award, supplier selection above thresholds and anything outside delegated authority stay with people.

So a new officer's work is mostly the held items: orders above limits, supplier checks with gaps, comparisons where the criteria need judgement, and anything the agent refused. How the role shifts is set out in what changes in a procurement officer's day when AI agents arrive. The head of procurement owns onboarding; a certified category manager coaches.

What does the fortnight look like?

1. Day 1. Person (head of procurement): explains thresholds and authority: the values at which an order needs approval, a quote set, or a formal tender, and who may approve at each level.
2. Day 1 to 2. Person (new officer): learns supplier data provenance. The approved supplier list from the procurement system is sealed. A certification checked against the issuing body is signed. A supplier's own statement is declared. A bank detail change by email is external and cannot authorise a payment.
3. Day 2 to 3. Agent, depth 2: drafts orders and comparisons, decided by the coach while the new officer follows each.
4. Day 4. Person (new officer): reviews supplier checks the agent completed, finding the gaps it flagged and any it missed.
5. Day 5. Person (new officer): practises on past requisitions with seeded cases: two orders that together breach a threshold, a removed supplier, a quote scored on price alone where delivery is weighted.
6. Week 2. Person (new officer): decides live held items, each checked by the coach.
7. End of week 2. Person (head of procurement): signs off approvals within the officer's delegated limit.

What should a new officer look for?

Split purchases. Two requisitions from the same cost centre for the same supplier a day apart may be one purchase broken up to stay under a threshold. The agent should hold these; the officer checks whether it did.

Stale supplier data. A supplier removed from the approved list may still appear in old catalogues. Report it so the source is updated.

Criteria that fit the category. Price-only scoring is wrong where delivery, quality or service carry weight. The officer checks that the agent used the category's criteria.

Bank details. Any change to supplier payment details is verified through a contact already on file, never from the request itself.

Declared interests. If the requester or approver has a relationship with the supplier that policy requires to be declared, the order needs a different approver. The agent cannot know about relationships nobody recorded. New officers should learn where declarations are kept and check them on held orders above their limit.

How should corrections be recorded?

With a reason: threshold misapplied, split purchase missed, stale supplier list, wrong criteria, or officer judgement. Threshold problems belong to the business's limits, changed only by the head of procurement; supplier problems belong to the source; method problems to the agent's brief. The reviewer onboarding checklist for the procurement team and the AI agent training plan template for procurement officers include these.

Which controls and evidence should onboarding leave?

• Seeded practice cases. Evidence: which the officer caught.
• Checked decisions in week two. Evidence: both names on each.
• Delegated limit recorded. Evidence: dated authority.
• Reasons by type. Evidence: reason codes by officer.

What should the head of procurement measure?

Split purchases the new officer caught. Orders raised with removed suppliers on their queue. Comparisons changed by the coach. After sign-off: a sample of approvals each month, and any audit findings on their orders.

Where does it usually go wrong?

Approving within the threshold without looking at the pattern. Each order is fine; together they are not.

Accepting declared certifications. A supplier's word is not evidence of a certificate. Check it with the issuer.

Moving too fast to award decisions. Award requires experience of the category and, in the public sector, of procurement rules.

Overriding the agent's refusals. A refused order often signals a real problem, such as a missing contract or a supplier outside the approved list. Pushing it through another route defeats the control.

Officers in compliance and lending follow related plans, for a new compliance officer and a new loan officer. The wider approach is in training teams for AI agents.

Where the Academy fits

Pryme Intelligence Academy's Operator track teaches how a governed agent decides and how to review its held work, with module tests set in the learner's own industry and role. A business can make an officer's approval rights depend on a current Certified Pryme Operator certificate, which anyone can check at source by number or QR code.