The vendor's proposal is vague about deliverables. What should be clarified?
Ambiguous supplier scopeDefine outputs, responsibilities, acceptance evidence, dependencies, and exclusions before commitment. Use examples to expose different interpretations while changes are still inexpensive.
What to do now
- List the promised deliverables
- Define acceptance and client obligations
- Clarify exclusions and assumptions
- Obtain an agreed commercial scope
When to escalate
Escalate when
A material commitment would be made without a usable scope definition.
Who decides
The authorized procurement or commercial owner
Example
Implementation is clarified to include specific integrations, training, and handover evidence.
Mistake to avoid
Assuming a polished proposal contains an executable delivery agreement.
Prevent a repeat
Compare supplier evidence with agreed obligations; refer contract interpretation and remedies to qualified owners.
Suggested ApprovedFlow setup
- Vendors
- Documents
- Tasks
- Approvals
Keep supplier commitments and evidence linked to the project, assign follow-up work, and route commercial decisions to authorized owners. See the platform
Related cases
- The vendor says knowledge transfer is not included. How do we respond?Missing supplier transition scope
- The vendor refuses to share progress evidence. What should we do?Unverifiable supplier delivery
- Our scope statement lists activities but no deliverables. What should change?Activity-focused scope
- Our project plan and backlog disagree about scope. Which is authoritative?Competing scope representations