How to teach procurement officers to bank corrections that improve an AI agent

Procurement officers bank a correction by recording why they changed the agent's purchase order, supplier check or quote comparison, then passing that reason to the agent owner as a change to the agent's sources, brief or the customer's own limits, followed by re-certification. Most procurement fixes belong in limits and approved-supplier sources, not in the brief.

What does the agent do in procurement?

A procurement agent raises purchase orders from approved requisitions within spend limits (depth 3 for routine catalogue buys), drafts orders for a person to approve above those limits (depth 2), checks new suppliers against onboarding requirements, and compares quotes against the category's evaluation criteria. Contract award and anything above delegated authority stay with people.

Officers correct it in familiar ways. It raises an order with a supplier who was removed from the approved list last month. It accepts three quotes for an item where the category policy needs a formal tender. It misses that two requisitions from the same cost centre, a day apart, together exceed the threshold that would need a second approver. It scores quotes on price alone where the category weights delivery time.

The cross-role picture is in AI agent skills by role.

Where does each procurement fix belong?

Teach officers three homes for a correction.

Customer limits hold thresholds and approval rules: the value above which an order needs a person, the value above which it needs a tender, and rules about split purchases. These are the business's own controls. When the agent got a threshold wrong, the limit is where the fix belongs, and changing it is a decision for the procurement head, not an officer.

Sources hold the approved supplier list, the catalogue, framework agreements and category evaluation criteria. When the agent used a removed supplier or an old price, the source is stale.

The brief holds method: how to compare quotes, what to check on a new supplier, when to hand back. When the agent applied the right rules in the wrong way, the brief needs clearer wording.

What are the steps?

1. Agent, depth 3: raises routine catalogue orders within limits from approved suppliers.
2. Agent, depth 2: drafts orders above limits, supplier checks and quote comparisons, citing sources and criteria.
3. Person (procurement officer): corrects and records a reason: limit misapplied, split purchase missed, stale supplier list, wrong criteria, method unclear, or one-off.
4. Agent, depth 1: groups reasons weekly by category and cost centre.
5. Person (category manager or procurement head): decides what to bank. Changes to limits need the procurement head.
6. Person (agent owner): makes the change, and Attest replays the agent against past requisitions and orders before go-live.
7. Person (category manager): checks the following weeks that the pattern stopped.

What do procurement officers need to learn?

How to spot split purchases. Agents read requisitions one at a time unless told otherwise. An officer who catches two orders that together breach a threshold should bank a method change: "check requisitions from the same cost centre and supplier within a set window before raising". This kind of correction stops maverick spending patterns, not just one order.

How to handle supplier data with provenance. A supplier's own declaration of certifications is declared; a certificate checked against the issuing body is signed. If the agent accepted a declared certification where policy needs a signed one, the fix is a provenance rule for supplier checks. Supplier bank details deserve extra care: an emailed change is external and cannot authorise a payment.

Where judgement stays human. Officers make calls about supplier relationships, negotiation and exceptional urgency. These are one-offs. The habits behind reviewing the agent are in how procurement officers review an AI agent's decisions, and the limits in what procurement officers should never let an AI agent do.

Which controls and evidence matter?

• Limits changed only by the procurement head. Evidence: approver name on every limit change.
• Approved supplier list from the system of record. Evidence: provenance on supplier facts.
• Split-purchase checks. Evidence: held verdicts for combined requisitions.
• Re-certification. Evidence: a dated certificate with scope and escalation gate scores.

What should procurement measure?

Repeat corrections per reason code. Orders raised with removed suppliers, which should reach zero. Split purchases caught by the agent compared with those caught by people. Time from a supplier removal to the agent's sources. And the share of depth 3 orders later amended.

Where does it usually go wrong?

Officers fix limits themselves by asking for a brief change: "let the agent approve up to a higher value for this category". That is a limit change dressed as a correction, and it bypasses the procurement head.

Supplier lists drift. Removals happen in a meeting, the list is updated weeks later, the agent keeps ordering. Link removal to the source update.

Quote comparisons get banked from one category to all. Weighting that suits facilities buying is wrong for IT. Lending teams face a similar threshold problem, covered in teaching loan officers to bank corrections, and compliance teams deal with policy-versus-practice drift, as teaching compliance officers to bank corrections explains.

Where the Academy fits

Pryme Intelligence Academy's Operator track teaches procurement officers to read the workspace, review the agent's work and teach it, with module tests set in their own industry and role. The Foundations track, free and about four hours, suits budget holders who approve orders but do not review the agent daily, giving them the vocabulary of depth and the decision chain.