Field notes · 18 February 2026
When a quality incident belongs on the scorecard
Deciding which quality events change a vendor’s ranking and which belong in a separate operational log.
Not every rejected carton should move a vendor down the ranking. Some events are one-off handling mistakes; others repeat across months and categories. Procurement leads need a rule that feels fair to suppliers and credible to operations.
We recommend counting incidents that meet a written threshold: safety risk, production stoppage, or a formal non-conformance already logged by your quality contact. Minor packing notes can stay in the operational log without entering the scorecard until they accumulate past an agreed count.
Weight repeat offenders more heavily than first-time events. A vendor with three similar incidents in one quarter is a different risk than a vendor with one isolated miss after two clean years. State the weighting on the scorecard so the supplier can see how the rank was formed.
Share the draft incident list with your quality counterpart before the briefing. Their confirmation prevents a ranking argument based on an incomplete log. The packs we deliver for Thai procurement teams always include that check as a fixed step before final scores are locked.