Procurement needs a replacement supplier to protect production; quality refuses approval because process capability and inspection evidence are incomplete. If neither function has clear decision rights, the disagreement tends to travel through increasingly urgent emails until a senior executive asks someone to “be practical.” That outcome is risky because commercial pressure can quietly override the original product requirement.
The objective is not to guarantee that quality always wins or that procurement always has the last word. It is to distinguish facts from preferences, establish non-waivable criteria and provide a documented route for acceptable conditional decisions. Some risks cannot legitimately be waived by either function.
1State the point of disagreement precisely
Begin with a single contested decision: supplier eligibility, initial technical qualification, specific material release, temporary deviation or contract award. Approval of a legal entity does not automatically authorize every part, site or process. Disagreements become harder to solve when one team argues about the general supplier relationship while the other is assessing a particular unverified process.
List the criterion, available evidence and consequence if it is not met. Use a short joint issue record rather than parallel scorecards. Label items as legal or contractual obligation, technical acceptance criterion, security condition, commercial preference or discretionary risk treatment. This classification often reveals that some points need clarification rather than compromise.
A concise dispute record can prevent people from arguing different versions of the question. State the supplier’s legal entity, manufacturing location, part or service family, proposed start date and precise gate that is blocked. Then list the evidence quality concern and the business consequence of delay. Avoid shorthand such as “Quality rejected supplier X” when the real issue is that one particular coating process has not been demonstrated. The distinction preserves legitimate purchasing alternatives while protecting the affected technical characteristic.
2Separate risk ownership from approval authority
Procurement owns sourcing strategy, supplier engagement, cost and continuity planning. Quality or engineering has competence to assess whether the defined product or service characteristics are met. Legal, regulatory or information-security functions may possess additional authority in particular contexts. No one function should silently absorb the other’s accountability.
A decision-rights matrix should say who may approve a deviation, who must be consulted and who is authorized to accept the remaining exposure. Escalation to leadership does not make an unsafe or unlawful purchase acceptable. For nonwaivable requirements, the legitimate options may be containment, redesign, customer authorization or an alternative supplier.
Authority is especially important when regulations and customer specifications are involved. A manager may accept commercial exposure to a delayed delivery but cannot authorize disregard of an applicable mandatory safety rule. The team should identify which conditions are organizational policy and which arise externally. If a customer concession is possible, define the party authorized to seek and grant it and the specific products it covers. A senior signature alone does not transform missing conformity evidence into an acceptable technical result.
Standards context. ISO 9001:2026 establishes quality-management-system requirements, while the exact supplier acceptance boundary is defined by the applicable product requirements, customer arrangements and laws. Read the official ISO publication information.
3Ask for evidence that can resolve the dispute
Quality may request supplier capability studies, first-article inspection, qualification reports, traceability records or proof of an effective corrective action. Procurement may present alternative lead-time scenarios, single-source dependence and production shutdown consequences. Both need to test evidence quality, not rely on assertions such as “the supplier has always been good” or “we cannot wait.”
Define which additional evidence would change each function’s conclusion. A targeted witnessed trial can sometimes resolve uncertainty more quickly than a broad supplier audit. Conversely, an apparent documentary gap may mask a real capability issue that demands substantive verification. Do not confuse incomplete files with insignificant risk.
Evidence requests should be proportionate and falsifiable. If the doubt concerns process stability, define representative production-run data and the target characteristic. If it concerns an unapproved sub-tier operation, map who actually performs the process and whether incoming inspection can detect variation. Procurement can contribute alternative supply options and the operational cost of waiting, while quality can explain the possible harm from a defect. The discussion becomes productive when both teams expose the assumptions that would make their preferred choice inappropriate.
4Use controlled temporary approval where defensible
Conditional approval can be appropriate for bounded quantities, defined applications and clearly identified lots or work orders. Conditions may include increased incoming inspection, restricted end use, technical witnessing and an expiry date. Assign an individual who can stop receipt or production if the conditions fail.
Record the business case and the residual risks in terms the decision maker understands. A conditional release is not the same as declaring the supplier fully qualified. If customer approval or legal authorization is required, obtain it explicitly before use. Changes to controls or conditions require renewed approval, not informal acceptance by production.
Temporary permission needs operational control, not just a footnote. Receiving and production staff should know the permitted quantity, destination, identification, sampling plan and withdrawal trigger. Purchasing should prevent new orders beyond the concession scope. A time-limited approval should automatically be reviewed before expiry; it must not become permanent because systems keep accepting orders. For high-consequence cases, hold supplier stock until an identified technical authority checks the agreed test evidence. Traceability must be sufficient to isolate any affected output later.
5Resolve escalation without eroding trust
Run a short structured review with procurement, quality, engineering, operations and the accountable executive when needed. Give each side space to state the evidence and the failure mode it fears. The chair should ask what the organization can legitimately authorize, what is still unknown and what it will do if the supplier fails.
Document dissent when material. A dissenting technical view should not vanish from the minutes merely because leadership approves a limited risk treatment. Equally, quality should not use “more data needed” as an indefinite veto without specifying decision-relevant evidence. Clarity reduces future confrontation.
A chair who does not understand the technical issue should ask for a written consequence statement, not improvise an engineering verdict. Record alternatives rejected for reasons such as insufficient validation, unacceptable schedule or prohibited customer deviation. If a technical function raises dissent about residual safety exposure, preserve that view with the leadership decision and follow-up responsibilities. This safeguards professional accountability while allowing legitimate business trade-offs. Avoid repeating the dispute through different channels once a formally authorized decision has been reached.
6Learn from the cause of recurring disagreements
After closure, review whether sourcing was initiated late, the supplier requirements were vague, approval criteria changed during evaluation or governance roles were unclear. Repeated conflict can indicate that procurement and quality operate against incompatible metrics, rather than a personality problem between managers.
Improve supplier selection gates, technical specification handoffs and early capacity planning. Confirm whether temporary exceptions were closed on time and whether a newly approved supplier actually performed to the agreed conditions. The quality of the governance process is visible in subsequent decisions, not in the absence of recorded disagreement.
Investigating recurring approval conflict can reveal structural incentives. Procurement may be rewarded solely for unit price and on-time award, while quality bears the cost of escapes. A better shared plan includes early technical qualification, supplier development and a review of projected demand. Examine whether sourcing gates require adequate lead time and whether specifications reach bidders in an unambiguous state. Strengthening those upstream practices reduces the need for rushed concessions and improves trust between functions.
How an approval panel should record its resolution
A short decision paper may be more useful than a long meeting minute. It identifies supplier scope, contested criteria, supplier and buyer evidence, alternative options, mandatory conditions, residual risk, approved restrictions, accountable reviewer and next checkpoint. Where a customer specification requires prior consent, document the customer decision separately from internal approval. Do not use a generic waiver form that lacks the characteristics on which the final acceptance depends.
If leaders approve a conditional path, deploy the decision to purchasing, receiving, production and the supplier. A concession known only to the meeting participants cannot control actual goods. Schedule a reassessment before the concession expires and define what would cause immediate suspension. That operational translation of a difficult decision is the point at which the governance process either becomes effective or remains an impressive document.
Operational decision checklist
- Identify the exact supplier, product, location and approval scope
- Classify disputed criteria as mandatory or discretionary
- Define evidence needed to reverse or confirm the technical decision
- Record residual risk, conditions, authority and follow-up verification
Closing perspective
A good resolution process does not suppress disagreement. It transforms opposing concerns into an explicit classification of requirements, evidence and legitimate decision authority. When the risk boundary is visible, commercial speed and product protection can be managed together.
Successful escalation preserves the technical acceptance boundary while making legitimate trade-offs explicit. Record the authorized outcome and communicate its conditions to everyone who can order, receive or use the supplied output.