Collect complete vendor intake
Structured intake requires scope, spend estimate, risk category, and mandatory vendor documents before routing.
Owner: Procurement operations lead; executive accountability with COOCOO · Vendor Request Processing
Move vendor request processing from fragmented updates to an owned, governed operating loop.
Mechanism
Structured intake requires scope, spend estimate, risk category, and mandatory vendor documents before routing.
Owner: Procurement operations lead; executive accountability with COOWorkflow logic assigns legal, security, finance, and business approvals based on request type and spend thresholds.
Owner: Vendor governance manager; executive accountability with COOThe agent checks required policy artifacts and automatically requests missing documentation from requestors.
Owner: Compliance analyst; executive accountability with COOHuman control
Enforce non-bypass gates for required legal and security artifacts.
Use spend and impact scoring to prioritize queue order.
Add final owner verification before onboarding handoff release.
FAQ
At minimum capture business owner, spend estimate, service category, data sensitivity, intended go-live date, and the vendor documents required for the first review lane.
High-risk security reviews, policy exceptions, and non-standard contract terms should retain explicit human approval even if the workflow automates enrichment and routing.
Create a visible exception path with named approvers, temporary controls, and an audit trail. Hidden side-channel requests are where process quality collapses.
Returned requests for missing information is usually the sharpest early signal because it shows whether intake quality improved before downstream teams feel the benefit.