The required structure
The template should begin with a defined decision scope and approval owner. It should then connect five control layers:
- Decision configuration
- Supplier qualification
- Commercial and risk calculation
- Weighted comparison and negotiation
- Award recommendation and approval
Using separate sheets is not a problem when the sheets are connected. The risk arises when each sheet uses different supplier names, assumptions, currencies or version controls.
Separate mandatory gates from weighted scores
A mandatory requirement answers a binary question: may this supplier remain eligible? A weighted criterion answers a comparative question: among eligible suppliers, which performs better?
Combining the two can create a misleading result. A supplier may compensate for failed compliance with a strong price score, even though the requirement was intended to be non-negotiable.
Design criteria that can be evidenced
Each criterion should have a definition, measurement scale, evidence source, weight and owner. Avoid vague criteria such as “overall fit” unless the scale and evidence are explicit. Check for double counting: quality certification and compliance evidence may overlap; lead time and delivery performance may measure different things and should be distinguished.
Weights should total 100% and reflect the decision context. Use the weighting sanity checker as a basic control, then review whether the model behaves as intended in realistic scenarios.
Preserve evidence and the decision trail
The evaluation should record the source and status of each material input. At a minimum, include evidence references, clarification status, calculation assumptions, unresolved issues, owners, dates and version. The purpose is not to create unnecessary administration; it is to make the recommendation reproducible.
Outputs a management reviewer needs
- Recommended supplier
- Decision rationale
- Cost comparison
- Weighted score
- Residual risk
- Mandatory failures
- Unresolved issues
- Award conditions
- Owners
- Approval fields
- Decision date
- Version reference
A detailed matrix can support the analysis, but the management summary should explain the decision in plain language. The preferred supplier, reasons, risks and conditions should be visible without searching through the workbook.
Common template design mistakes
- Too many criteria with weak definitions
- Weights designed after offers are received
- Price compared without landed-cost adjustments
- Risk shown in a separate register but omitted from ranking
- Missing critical-failure control
- No negotiation or award-condition tracker
- No final recommendation or approval fields