Blogs
Technical Deviation Control in International Sourcing
A practical deviation register for making engineering, test, warranty, schedule and cost consequences visible before award.
International sourcing becomes risky when technical deviations are discovered after the order. A lower-cost offer is not equivalent when its exclusions, tolerances or evidence requirements differ from the specification.
Why this matters
Technical and commercial teams often review different documents. Unless departures are consolidated, an engineering exception can remain hidden inside a quotation note until production or acceptance.
ISO 21502:2020 provides guidance for project governance, planning, control and change. Applied to sourcing, it supports a simple principle: deviations should be visible, owned and approved before they become field problems.
Controls that should be defined
- Record every departure from the specification in one register.
- Describe the engineering, operational and lifecycle consequence.
- Assign a responsible reviewer and decision date.
- Define the test and acceptance evidence required for approval.
- Capture warranty, schedule and cost consequences.
- Control changes introduced after contract signature.
A practical workflow
- Issue a clear baseline specification and response format.
- Extract supplier qualifications and exclusions into the deviation register.
- Obtain engineering, quality, commercial and operational review.
- Close, reject or conditionally accept each deviation before award.
- Carry approved deviations into the contract, test plan and acceptance records.
Evidence to retain
Retain the baseline specification, supplier response, deviation register, technical disposition, approval authority, commercial consequence and verification evidence.
Conclusion
A deviation register is not paperwork added after the decision. It is the decision record that protects equivalence, accountability and acceptance across borders.