Set the vendor coordination scope
Track Vendor Coordination Items starts with a written boundary. Name the event, the source, the owner, the evidence, and the point where the work must stop. A clear rule keeps coordination separate from priority, budget, and management decisions.
The main risk is that a vendor request can wait without an owner or a service date. Record the source and time before changing a status.
Capture the evidence
A usable record includes vendor, request, owner, due date, status, and evidence. Keep the source beside the record so another reviewer can reconstruct what happened.
The vendor manager confirms the decision or exception. The coordinator can log the request, check completeness, and route exceptions, but should not fill a gap with an assumption.
| Evidence | Purpose | Owner |
|---|---|---|
| Source record | Shows what was known | Coordinator |
| Current state | Shows the next action | Coordinator |
| Decision note | Shows who approved | Accountable owner |
Separate preparation from judgment
Decisions about contract and service decisions remain with the authorized owner. Use three labels: proceed under the rule, pause for missing evidence, and escalate for a decision.
Run the review
Review open requests, age, and missing evidence. Sort by age, owner, and exception reason. For example, a vendor renewal approaches without a named owner. Record what evidence was available and who owned the next step.
Pilot one workflow
Start with one vendor. Test the checklist on a small batch and review exceptions with the owner. Expand only after the workflow produces a reviewable record.