Supplier change notification requirements

TL;DR

• Control supplier changes as documented operational decisions, consistent with the controlled-operation and documented-information framework in the ISO 9001:2026 public overview.
• Preserve the current baseline, proposed baseline, impact, evidence, approvers, effectivity, first changed lot, and post-change result under one notice ID and revision.
• Hold implementation for missing child rows, Unknown impacts, unaccepted evidence, missing approvals, invalid deviations, uncertain cutover identity, or prior implementation.
• Use formula readiness only to request a bounded buyer decision; implementation, product release, corrective action, and closure always remain separate manual decisions.

Define the change before reviewing it

A supplier change notice must compare one current approved baseline with one proposed baseline for a named supplier, site, part, and revision. “Equivalent source” or “process improvement” is not a reviewable scope.

1. Freeze the join key. Use one notice ID and notice revision across every impact, evidence, approval, gate, and validation row.
2. State current and proposed conditions. Name the material, process, tool, equipment, site, subtier, software, inspection, packaging, or ownership record on both sides.
3. Bound effectivity. Identify the proposed date, first changed lot, affected open orders, old inventory, work in process, and rollback plan.
4. Name the next decision. Review, sample, implementation, shipment, production release, and closure are different decisions.

Set notice triggers from the actual requirement

Use categories to prompt questions, not to invent universal rules. The contract, quality agreement, drawing, specification, risk control, sector rule, and customer requirement define what needs notice or approval.

The official ISO pages identify ISO 9001:2026 as the current requirements edition and ISO 9000:2026 as the fundamentals and vocabulary reference. Their public pages do not create a universal supplier notice calendar, approval form, PPAP level, or capability threshold.

Label sector and customer examples honestly

JPL QAC01c names facility, product, process, QMS, company, and supplier changes within its customer-specific scope. Its ten-business-day term applies only where that clause controls. FDA's medical-device site-change guidance uses product- and risk-specific submission paths. Automotive buyers must check the current OEM documents listed by the IATF customer-specific requirements index. None is a general default for every industrial buyer.

Run one linked workflow from notice to closure

Separate intake, analysis, evidence, approval, implementation, and validation so that a complete-looking form cannot hide a missing decision.

Keep Unknown different from Not applicable

An Unknown can be neutral evidence about uncertainty, but it cannot be treated as a favorable answer. A Not applicable decision needs a scoped rationale. Evidence acceptance confirms an artifact's use for one decision; it does not approve the change.

Copy the six-sheet supplier change workbook

Create tabs with these exact names and paste each block into cell A1. Preserve the formulas. Keep the notice ID, notice revision, buyer program, supplier entity and site, part, and current and proposed revisions identical across linked rows.

Preserve the controlled values

• Impact applicability: Applicable, Not applicable, or Unknown.
• Decision stage: exactly Pre-implementation or Post-change.
• Evidence state: Accepted, N/A, or another explicit state that remains on Hold.
• Approval decision: Approved, N/A, Hold, Rejected, or Not reviewed.
• Keep every date column as a spreadsheet date value; a blank, invalid, or text-formatted date remains on Hold.
• Formula outputs: only HOLD, READY FOR BUYER DECISION, or READY FOR BUYER DECISION/CLOSURE.
• Manual decisions, owners, dates, and evidence references stay separate from every formula.

Fail closed at implementation and closure

The formulas test record completeness and controlled states. They do not judge technical adequacy, approve the change, release product, or close corrective action.

Each used row validates its own ID, parent identity, controlled vocabulary, required fields, and chronology. Current evidence needs a valid expiry through the relevant decision date. Evidence marked Not time-limited needs an explicit policy or basis. A typo, duplicate, orphan, expired record, or date after the cutover fails closed.

Restrict the buyer-verified implementation-status fields to buyer editors. A supplier's unchecked “Not implemented” statement is not enough: the fixture requires a buyer verifier, verification date, and evidence reference, and it holds any already implemented change with a linked SCAR.

Scope every deviation to the same cutover identity

The fixture accepts either no deviation or an approved deviation whose scope exactly joins notice, revision, part, site, and first changed lot. An expired or broader deviation remains on Hold. A deviation does not approve a permanent baseline.

Make post-change validation a new decision

The closure gate verifies that the implementation decision exists, the first changed lot matches, post-change evidence is accepted, every used post-change approval remains valid through validation and closure, validation passes, and deviations or corrective actions are resolved. The result stops at readiness. An authorized buyer records the exact closure separately.

Worked example: one late change stays on Hold, one controlled change closes

Supplier Alpha changed a coating subtier before notice and cannot yet bound affected lots. Supplier Beta proposes a controlled inspection-software update with an exact cutover lot. The same formulas produce different readiness results from the linked evidence.

Exact closure for the controlled change

The formula returns READY FOR BUYER DECISION/CLOSURE. It does not close the record. The buyer manually records: “Close CN-FX-CLOSE/R1 for PN-FX-510 Rev G at Site-MX-02 beginning LOT-FX-2026-104; evidence VAL-RPT-FX-C1 and TRACE-FX-C1 accepted.”

That closure does not approve another site, part, software version, lot, or future change. It also does not replace normal production-release and supplier-performance controls. Use the sample validation, FAI, and PPAP guide when the approved change requires a separate product or process evidence gate.

Common pitfalls and their operational consequences

Submitting a reason without current and proposed baselines

“Improve coating capacity” does not identify what changes. In a fictional case, reviewers return 2 files, the supplier loses 3 business days, and the planned validation window is missed.

Copying one customer's notice period into every agreement

A buyer treats a customer-specific 10-day term as universal. In a fictional case, regulatory and test work needs 35 days, so $4,500 of booked freight is cancelled and rescheduled.

Treating Unknown impact as no impact

The buyer leaves traceability unresolved but lets production continue. In a fictional case, 1,800 finished parts and 900 work-in-process parts enter containment because changed lots cannot be bounded.

Letting a summary row hide missing child reviews

The notice says “all functions reviewed” without packaging or logistics rows. In a fictional case, 240 cartons need new labels and shipment moves by 3 business days.

Using an approval email without exact scope

A supplier applies one engineer's “looks good” reply to 2 parts and 3 sites. In a fictional case, 600 units from the unreviewed site move to Hold for document reconstruction.

Accepting an expired or overbroad deviation

A deviation for one lot is reused after expiry. In a fictional case, 900 units are produced outside scope and wait 7 business days for material review.

Leaving the first changed lot ambiguous

The effectivity date is recorded but the physical cutover is not. In a fictional case, 1,100 old and changed units require a 2-day sort before shipment.

Approving a change after it was already implemented

The planned form is used to sanitize an escape. In a fictional case, 3,200 parts enter containment, a SCAR opens, and the line loses 6 production days.

Closing on one sample without a defined validation plan

One sample passes but the required evidence population was never set. In a fictional case, lot 5 rejects 160 parts and the closure record must be reopened.

Closing the change while corrective action remains open

A linked SCAR has no effectiveness evidence, but the change record closes. In a fictional case, 2 repeat escapes place another 400 units on Hold and trigger a second review.

Glossary

Supplier change notice

A controlled proposal to alter an approved supplier, product, process, or delivery baseline.

Current approved baseline

The identified material, process, tool, site, document, software, or other state currently authorized for the scope.

Proposed baseline

The identified state requested to replace or supplement the current approved baseline.

Effectivity

The controlled point at which an approved change is intended to begin.

First changed lot

The first uniquely identified production lot made under the proposed baseline.

Impact assessment

A domain-by-domain evaluation of what the proposed change may affect and what decision is needed.

Unknown

A controlled state showing that an effect or evidence has not been resolved. It is not a favorable result.

Not applicable

A scoped buyer conclusion, supported by a rationale, that a domain or requirement does not apply.

Evidence acceptance

A named reviewer's decision that an artifact supports its stated scope. It does not approve implementation.

Approval routing

The controlled list of functions, authorities, decisions, dates, scope, and evidence required for the change.

Deviation

A bounded authorization to depart from a requirement for a defined scope and period.

Cutover identity

The effectivity, site, part, revision, and first lot that separate old and changed production.

Post-change validation

Evidence and review performed after implementation on the identified changed output.

SCAR

A supplier corrective action request used for a detected failure or control breakdown, not as planned-change approval.

Frequently asked questions

Practical answers for buyers controlling supplier-originated manufacturing changes.