Quality leadership: from supplier policing to supplier development.
ISO Cloud Consulting editorial teamSupplier policing (approve, inspect, reject, raise a corrective action request) protects you from bad deliveries, but it rarely makes a supplier better. Supplier development reduces bad deliveries in the first place: pick the high-risk suppliers you depend on, agree a joint plan, share data both ways and measure the result every quarter.
Why is supplier policing not enough?
Most supplier quality programs are built around policing. Approve, inspect, reject, issue a corrective action request, repeat. It is necessary, but it rarely makes a supplier better. This episode explains how to move from policing to development, for the suppliers who matter most.
What is the difference between policing and development?
Policing protects you from bad deliveries. Development reduces the number of bad deliveries in the first place. Policing is a cost you carry forever. Development is an investment that pays back in lower inspection, fewer disruptions and better prices over time.
Which suppliers should you develop?
You cannot develop every supplier. Use your supplier segmentation: risk to your product on one side, spend on the other. The best candidates are high-risk suppliers that you depend on, that are hard to replace, and that are willing to improve. A small supplier with good people and weak systems is often the best investment you can make.
How do you build a joint improvement plan?
Sit down with the supplier's leadership, not just their quality person. Share the data you have about their performance, honestly. Agree two or three improvement priorities, each with an owner on both sides and a timescale.
Typical priorities include process capability on a critical characteristic, packaging that prevents damage, or change notification that actually happens. Offer something in return: forecasts, a longer agreement, technical support, or access to your engineers.
What data should you share with the supplier?
Share data both ways. Give the supplier your rejection data, your incoming inspection results and your complaints that trace to their parts. Ask for their process data, their first-off results and their capability studies. When both sides see the same numbers, conversations change from blame to problem solving.
Agree in advance how disputed rejections will be settled, for example by a joint measurement on a reference gauge, so disagreements are resolved by data rather than by who shouts loudest.
How do you measure the result?
Use a simple scorecard reviewed quarterly with the supplier: quality, delivery, responsiveness and progress on the joint plan. As performance improves, reduce incoming inspection, and tell the supplier why. That reward matters.
When should you exit a supplier?
Development needs willingness on both sides. If a supplier will not engage after a fair attempt, the program has still done its job. You now have the evidence to make a change, and a clear picture of what you need from a replacement.
How does this help with ISO 9001:2026 and ISO 13485?
Supplier development also gives you excellent evidence for the opportunities and supplier control expectations of ISO 9001:2026, and for the risk-based supplier control expected under ISO 13485.
Can you get help with supplier development?
Supply chain optimization and supplier development are part of the industrial engineering services we offer. The consulting page explains how. For the records, see the ISO 9001:2026 Complete QMS Documentation Kit, the ISO 13485 Supplier Control Kit and the ISO 9001:2026 templates collection.
