How to keep procurement officers ready for an AI agent’s 90-day recertification

Procurement officers need to know, each cycle, which orders the agent can now raise alone and which suppliers it can onboard. Every 90 days the procurement agent is recertified on your own requisitions and supplier files. Its purchase order rights, its catalogue and its onboarding checks can change. Brief the delta, practise on split orders and new suppliers, and sample early.

What changes for procurement officers?

A procurement agent usually reads requisitions, contracts and the supplier master at depth 1. It drafts requests for quotation and scores returned bids into a comparison at depth 2. It raises purchase orders from the approved catalogue and framework contracts at depth 3, within the organisation's own limits. It collects supplier onboarding documents and runs checks, but adding a new supplier or changing a supplier's bank details is held for a named person. Contract award stays with officers and the approval board.

Recertification re-runs the agent's cases on recent activity. Typical changes include a narrower catalogue, a lower purchase order limit for certain categories, or a new refusal on requisitions that look like one purchase split to stay under a threshold. Officers then see more requisitions and need to understand why.

Take, for example, a facilities team that requests two cleaning orders of 4,000 each on the same day from the same supplier, against a threshold of 5,000 for a competitive quote. Under the previous certificate the agent raised both. After recertification it refuses the second and names the bound that decided: the organisation's own limit on aggregated spend. The officer who picks up the refusal needs to know that this is new, and what the correct route is.

Provenance runs through supplier onboarding. A supplier's own description of its insurance cover is declared. An insurance certificate confirmed with the insurer is signed. Once a supplier is onboarded, its record in the supplier master is sealed. A bank-detail change sent by email is external and cannot authorise a payment.

Who owns the cycle?

The procurement manager owns officer readiness. The builder owns recertification. The finance director or equivalent owns the organisation's own limits, such as purchase order values. The category managers own the catalogue.

Steps for each cycle

1. Agent, depth 1: report the cycle. Requisitions read, RFQs drafted, orders raised and held, suppliers onboarded and held, refusals, with the deciding bound for each.
2. Person (senior officer): sample orders raised by the agent against catalogue, contract and limits.
3. Person (category managers): confirm catalogue changes due in the next cycle.
4. Person (builder): recertify on recent activity, including any split-order cases found.
5. Person (procurement manager and builder): write the change note: catalogue scope, order limits by category, onboarding checks and new refusals.
6. Agent, depth 2: draft practice cases, including a split requisition and a new supplier with a weak document, checked by the senior officer.
7. Person (procurement manager): brief officers; each explains their decision on each case.
8. Person (senior officer): sample orders and onboarding decisions in the first fortnight.

What should procurement officers practise?

Split requisitions. The agent may refuse to raise two orders that together cross a threshold. Officers should recognise the pattern and know that the right answer is the correct approval route, not a third order.

Supplier evidence. Practise telling declared, signed and external evidence apart in an onboarding file, and decide what to ask for when a key document is only declared.

Bid comparisons. The agent's scoring follows the published criteria. Officers should check the scoring against the bids, because a missed clarification can change a score.

Bank-detail changes. Walk through a supplier email asking for new bank details. The route is verification with a known contact at the supplier, recorded.

Pryme Intelligence Academy's Operator track, which covers human review and teaching the agent, is one way for officers who approve held orders to hold a checkable certificate.

Controls and the evidence they leave

• Order sample each cycle. Evidence: the sample and findings.
• Catalogue change list. Evidence: the category managers' confirmed list.
• Change note. Evidence: dated note agreed with finance.
• Named approval on held orders and new suppliers. Evidence: approvals in the append-only record.
• Practicum for new officers. Evidence: the practicum log template for procurement officers.

What to measure

Orders raised outside catalogue or contract (aim for none from the agent). Time from requisition to order, before and after the cycle. Supplier bank-detail changes made without verification (none). And refused split requisitions, which show whether the control is catching what it should.

Where does readiness slip?

The catalogue changes without the agent being recertified on it, so orders for new items are held and officers cannot see why. Align catalogue releases with the cycle.

Officers override refusals by raising orders by hand. The refusal is the control; overriding it moves the risk to the officer.

Approval rights are informal. Whether officers need a certificate to approve held orders is the organisation's decision; see do procurement officers need a certificate to approve AI agent actions. Who answers for mistakes is covered in are procurement officers accountable for an AI agent's mistakes. Compliance teams run a parallel cycle; compare keeping compliance officers ready for recertification and the guide to AI literacy and certification for people who work with agents.