Procurement officers log each purchasing decision they make on an AI agent's work during a two-week practicum: the request, its value against thresholds, the agent's recommendation, the supplier evidence and its provenance, the officer's decision and reason, the head of procurement's independent call, and any red line. Template below, then four sample entries from a manufacturer.
What does the agent prepare, and what does the officer decide?
In a typical procurement deployment, the agent validates requisitions against budget and category at depth 1, compares quotes and drafts a recommendation at depth 2, assembles supplier onboarding packs, and flags contracts approaching renewal or notice dates. Raising a purchase order within catalogue rules may run at depth 3; committing spend outside those rules is held for a named officer.
The officer's decisions fall into four kinds: which supplier, whether a new supplier is fit to onboard, whether a renewal should proceed, and whether a request can bypass competition. Each has its own failure. The setup for the two weeks is in how to run a two-week practicum for procurement officers.
Which red lines go in the header?
- Onboarding without completed due diligence. Any supplier activated with a check outstanding.
- Accepting a split order. Two or more requisitions that together cross a competition threshold, approved separately.
- Treating supplier claims as verified. A certificate, insurance document or accreditation supplied by the supplier and not confirmed with the issuer.
- Committing spend above authority.
Red line 3 is where provenance matters most. A supplier's PDF of their insurance certificate is external. Confirmation from the insurer, or from a registry that holds the record, is signed. The agent can tell the difference and labels it; the practicum checks whether the officer reads the label.
The practicum log template
Header: officer; head of procurement or delegate with a current certificate; categories in scope; competition thresholds; officer's practicum authority; dates; bar of at least 95 correct in every 100 and no missed red line.
| Field | Entry |
|---|---|
| No. and date | |
| Request reference | |
| Category | |
| Value and threshold | Below, at or above |
| Related requests in the last 30 days | Same requester, category or supplier |
| Agent's recommendation and verdict | |
| Supplier evidence and provenance | Sealed, signed, declared or external |
| Officer's decision | Approve, return, run competition, escalate |
| Reason | |
| Head of procurement's decision | |
| Match | Yes / no / defensible |
| Red line | None / caught / missed |
The "related requests" column exists for red line 2. The agent can pull it from the record; the officer has to look at it.
Four sample entries
Take a sample food manufacturer with a competition threshold of 25,000. Values are illustrative.
Entry 41. Packaging film, 18,000, three quotes. Agent recommends the lowest. Supplier is approved and its food-contact certification is confirmed with the issuing body (signed). Officer: approve. Head: approve. Match: yes.
Entry 42. Maintenance contract, 14,000, single quote. Related requests: the same requester raised 13,500 for the same contractor nine days earlier. Officer: approve; each is below threshold. Head: return; together 27,500 crosses the threshold; run competition. Match: no. Red line 2: missed.
Entry 43. New cleaning supplier, onboarding pack complete except public liability insurance, supplied as a PDF (external). Agent: holds activation. Officer: request confirmation from the insurer before activation. Head: same. Red line 3: caught.
Entry 44. Software licence renewal of 22,000 with notice due in 10 days. Agent flags low usage: 40 of 120 licences used. Officer: renew at 60 licences after checking with the budget holder. Head: same. Match: yes.
Entry 42 fails the bar. Neither request looked wrong on its own; the column built to catch it was there, and unread.
How do procurement logs relate to compliance and lending?
Compliance officers review some of the same decisions after the fact; the practicum log for compliance officers shows the exceptions they see. Loan officers share the authority and evidence disciplines in a different context; see the log for loan officers. Organisations using Pryme Intelligence Academy can run this log as the record of the Certified Pryme Operator practicum; the guide to AI literacy and certification for people who work with agents has the wider picture.
Questions people ask
Should catalogue purchases the agent raised on its own be logged?
No, only decisions the officer makes. Sample a few at the debrief to check the officer knows what the agent does unaided.
What if a budget holder pressures the officer to approve quickly?
Log the pressure in the note. Pressure is part of the job, and the practicum should show how the officer handles it.
Is the officer accountable for a bad supplier the agent recommended?
For suppliers they approved, yes, alongside the organisation's own process. See are procurement officers accountable for an AI agent's mistakes and do procurement officers need a certificate to approve AI agent actions.