1
Configure
Set criteria, weights, thresholds and assumptions before supplier data influences the result.
Use case
Keep lead time, MOQ and implementation exposure inside the supplier choice.
A decision view that prevents logistics, quality and implementation consequences from disappearing behind a unit-price comparison.
The recurring problem
Why this role needs a connected decision trail.
- Freight, duty and handling are added after the preferred supplier is already selected.
- MOQ and lead-time consequences are visible but not weighted consistently.
- Operational risks are described in notes without owners or residual-risk status.
- The award decision and onboarding handoff are not connected.
Relevant outputs
What the system is designed to produce.
- Landed unit cost by supplier
- Total lead time and MOQ comparison
- Residual-risk profile with controls and owners
- Pre-award implementation conditions
- Onboarding and performance follow-up
Practical use
An operations lead can compare the apparent commercial advantage with the actual supply and implementation exposure before approving a preferred supplier.
The decision still requires professional judgement, supplier evidence and the appropriate legal, tax, technical and regulatory review.
Suggested workflow
Use the same five stages without changing their meaning.
2
Qualify
Record mandatory evidence, critical failures and supplier readiness before commercial ranking.
3
Calculate
Compare quoted price with landed cost, total lead time, MOQ and other commercial drivers.
4
Rank and negotiate
Apply weighted scoring, keep residual risk inside the decision and track negotiated conditions.
5
Approve and govern
Create a management-ready recommendation, document approval conditions and monitor the supplier after award.
Next step
See whether the sample output fits your use case.
Download the fictional decision summary and compare it with the approval output you currently use.