When to use it
- A team is preparing to move from sourcing research into a formal event.
- Stakeholders need a go/no-go checkpoint.
- The sourcing package needs approval before supplier outreach.
Event readiness
Sourcing Event Readiness Checklist
Event readiness prevents teams from launching a formal process with unclear scope, weak evidence, incomplete supplier discovery, or unreviewed assumptions.
Version 1.1. Last reviewed July 11, 2026.
Overview
Confirm the sourcing packet is ready before moving into formal bidding, negotiation, renewal, or vendor-management work.
Event readiness prevents teams from launching a formal process with unclear scope, weak evidence, incomplete supplier discovery, or unreviewed assumptions.
Example artifact
How this playbook shows up in the sourcing packet.
This playbook produces a reviewable artifact that connects to the starter-kit workflow. It should capture source notes, assumptions, owners, status, open questions, and the decision gate for the next sourcing stage.
When it is not sufficient
It does not replace RFP drafting, legal review, pricing evaluation, renewal negotiation, vendor risk, security review, or final approval. It confirms the sourcing inputs are ready for those later steps.
Decisions supported
- Whether the sourcing packet is ready.
- What must be corrected before the next phase.
- Which owner must approve the move forward.
Inputs required
- Completed intake
- Category profile
- Market scan
- Supplier discovery grid
- Cost-driver log
- Shortlist rationale
Included artifacts
- Readiness checklist
- Missing-information log
- Stakeholder alignment notes
- Approval gate checklist
- Sourcing package summary
Example prompts and questions
- Is scope stable?
- Are assumptions visible?
- Are sources documented?
- Have decision owners reviewed the packet?
- What is not ready?
Illustrative use case
Illustrative example: before launching a facilities sourcing event, the sourcing lead confirms scope exclusions, supplier universe, after-hours coverage questions, cost-driver assumptions, and business-owner approval.
Common mistakes
- Launching a process with unstable requirements.
- Skipping stakeholder review.
- Hiding evidence gaps.
- Treating readiness as a formality rather than a gate.
Frequently asked questions
Does readiness mean the final supplier is selected?
No. It means the sourcing packet is ready for the next process.
Can the checklist stop a sourcing event?
Yes. A useful readiness gate should identify when work is not ready to proceed.
Related playbooks and examples
Next step
Use the starter kit, then request the full sourcing playbook overview.
The free kit shows the workflow. The full package discussion can cover team use, advisory use, category-specific adaptations, and implementation support.