Off-Contract Spend Flag
Maverick spend outside preferred vendors. Routes it to the category manager.
Spend goes to a non-preferred vendor in a category with an active preferred agreement, above the de-minimis threshold.
Maverick-spend exception logged in Coupa against the requester and category; preferred vendor surfaced in the requisition flow.
Every write is gated on an approver role you name. Nothing runs unattended.
- Identify the spend and the preferred alternative that was available at the time of purchase.
- Compute the delta against what the preferred agreement would have cost, which is the only number that matters here.
- Find out why: urgency, an item genuinely not covered, or a requester who does not know the agreement exists.
- Route to the category manager with the pattern rather than the individual purchase, since one-off maverick spend is noise.
- Close when the category compliance rate improves or the agreement is widened to cover the real need.
Preferred-vendor capture rate by category over a quarter, valued at the price delta.
The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.
The rest of Procurement
Run Off-Contract Spend Flag on your data.
Pick three playbooks from the catalog. We wire them against your system of record for the pilot.
Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly
Find out what your data has been hiding.
Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.