Engineering change notification clause obligations

A supplier changes a plating process. Nobody tells you until a qualification test fails eight months later.

What is an engineering change notification clause?

An engineering change notification clause requires a supplier to notify the buyer before making a change to a part, material, process, sub-tier source or manufacturing location. It typically sets a minimum notice period, defines which change categories require buyer approval rather than notification alone, and grants the buyer rights such as last-time-buy, requalification support or rejection. The clause exists because a change invisible in the part number can still invalidate a qualification.

Last updated: September 18, 2026 · Reviewed by the Aavenir Manufacturing practice

Key takeaways

  • ✓Notification and approval are different obligations, and clauses that blur them leave the buyer with notice but no veto.
  • ✓Process and sub-tier changes are the highest-risk category and the one most often excluded from the notification scope.
  • ✓Notice periods are only useful if they exceed the time needed to requalify, which means the period should be set from qualification lead time.
  • ✓Last-time-buy rights create a buyer-side deadline that has to be tracked, or the right expires unexercised.

A supplier switches a plating chemistry at one of its plants. The part number does not change. The drawing does not change. The incoming inspection passes because inspection was never designed to detect that variable. Eight months later a qualification retest fails, a field return pattern emerges, or a customer audit asks when the process was last validated, and the investigation discovers a change nobody was told about.

The contractual answer to this is the change notification clause, and most supplier agreements contain one. The reason the scenario above still happens regularly is that the clause is usually written to cover changes the supplier makes to the part, not changes it makes to the process, and almost never requires the supplier to pass the obligation down to its own sources. It also tends to require notification without requiring approval, which leaves the buyer informed and powerless.

This article covers how to scope a change notification clause so it catches the changes that actually matter, why notice periods should be derived from qualification lead time, the buyer-side deadlines that notification creates, and how to track all of it rather than relying on a quality engineer noticing an email. It is written for procurement, supplier quality and the contract teams supporting them.

What the clause has to cover

Scope is where most notification clauses fail, because they were drafted around design change and the risk sits in process change. The categories below are the ones worth naming explicitly rather than leaving to a general obligation to notify material changes.

  • Part and specification change, any change to dimensions, materials, finish or the bill of materials, including changes the supplier considers equivalent or non-functional.
  • Process and method change, changes to manufacturing process, tooling, plating or coating chemistry, heat treatment, test methods and inspection sampling plans.
  • Location change, relocation of manufacturing, assembly, test or packaging operations to a different site, including movement between the supplier own plants.
  • Sub-tier source change, changes to the suppliers of critical materials and components, with flowdown language obliging the supplier to impose equivalent duties on its own sources.
  • End of life and discontinuation, notice of planned discontinuation with a defined last-time-buy window and continuity support obligations during transition.

Naming the categories is only half the work. Each category needs an assigned treatment, meaning notification alone or notification plus written buyer approval before implementation. A clause that applies the same treatment to a packaging artwork change and a plating chemistry change will be applied inconsistently by suppliers, because the effort of seeking approval for trivial changes trains everyone to route them informally.

Set the notice period from qualification lead time

A notice period shorter than the time needed to requalify provides no protection. Work backwards from the qualification path for each part family, add time to build bridge stock, and negotiate the notice period from that figure. For parts with extended life testing or regulatory requalification, periods of six to twelve months are common in the approval categories, and a standard ninety-day clause across all parts is simply a mismatch.

Where notification obligations break

The patterns below are consistent, and each one is a contract design issue rather than a supplier performance issue. Suppliers generally comply with what the agreement asks for, which is why the asking has to be precise.

  • Process change is out of scope. Clauses drafted around part and specification change do not oblige notification of a process change, which is where qualification risk concentrates.
  • There is no flowdown requirement. Without an obligation to impose equivalent duties on critical sub-tiers, a tier two change is invisible to the direct supplier contractually and to the buyer entirely.
  • Notification arrives without a decision path. A notice received in a procurement mailbox with no routing, category assessment or approval gate is filed rather than acted on, which is the most common failure.
  • Last-time-buy windows expire. The right is treated as information rather than as a buyer deadline, and the window closes without an order, leaving no continuity position during requalification.
  • Change history is not retained against the part. When a field failure investigation begins, the question is what changed and when, and answers scattered across email are not usable as tracked evidence.

Putting the controls in place

Step 1, Audit clause scope across the supply base

Pull the change notification clause from every agreement covering a critical or regulated part and record which categories it covers, which require approval, what notice period applies and whether flowdown is required. The output is usually a wide spread of coverage across a supply base built over many years, and the gaps are the renewal agenda.

Step 2, Set notice periods from qualification paths

Map qualification lead time by part family, then set the required notice period for approval-category changes from that figure plus bridge stock build time. Agreements with a single notice period applied across all parts need differentiation, because the same period cannot serve a commodity fastener and a life-tested component.

Step 3, Build the intake and routing path

Give supplier notifications a single intake point, a mandatory category assessment and automatic routing to supplier quality and design engineering. Notifications arriving into individual mailboxes are the root cause of unassessed change, and the fix is a defined queue with an owner rather than better email discipline.

Step 4, Track the buyer-side deadlines

Create an obligation when a notification is received, with the approval decision deadline and the last-time-buy window as tracked dates. This is the step most programs miss, because the clause is understood as a supplier duty and the deadlines it generates on the buyer side are not recorded anywhere.

Step 5, Connect to downstream arrangements

Where a change affects parts under a vendor managed inventory or consignment arrangement, trigger the contractual wind-down and liability allocation in that agreement rather than handling it by phone. The two clauses are meant to interact and usually do not, which is where stranded stock arguments begin.

Review your notification clauses

A working session on scope, notice periods and flowdown across a sample of agreements.

Book a demo

Why flowdown is the highest-value fix

Of all the gaps in change notification, the absence of sub-tier flowdown is the one that produces the largest surprises for the least drafting effort. A direct supplier may be entirely compliant with its notification obligations while a tier two source changes a resin grade, a wire supplier, a foundry or a test house. The direct supplier may not know, because its own agreements impose no such duty, and even where it does know it has no contractual obligation to pass the information on unless the clause says so. Closing this requires two sentences. The supplier must impose equivalent notification obligations on its critical sub-tiers, and must notify the buyer of any change of which it receives notice regardless of origin. Adding a requirement to identify critical sub-tiers for named parts makes the obligation enforceable rather than aspirational. This is the same flowdown discipline applied elsewhere in supplier agreements, and it belongs on the same clause standardization agenda described in the supplier contract automation guide.

Treatment by change category

The table below shows a workable default treatment for each category. The point is not the specific periods, which should be derived from your own qualification paths, but that the categories carry different treatments rather than one blanket rule.

Change categoryTreatmentBuyer-side deadline createdOwner
Cosmetic or packaging artworkNotification onlyNoneProcurement
Specification or dimensionalApproval requiredApproval decisionDesign engineering
Process, plating, heat treatmentApproval requiredApproval plus requalification planSupplier quality
Manufacturing site relocationApproval requiredApproval plus site auditSupplier quality
Sub-tier source for critical itemApproval requiredApproval plus qualificationSupplier quality

Change notification is one of the few supplier clauses where the buyer bears most of the operational burden despite the obligation sitting with the supplier. The notice has to be received by someone who can categorize it, routed to people who can assess it, decided within a window, and acted on before a last-time-buy right expires. Getting value from the clause means scoping it to include process and sub-tier change, setting notice periods from qualification lead time, and treating every notification as the start of a tracked obligation rather than as an email to file.

For related guidance, see IATF 16949 supplier quality agreements, a control guide, Supplier quality agreement and PPAP commitment tracking and Last time buy notices and end of life duties.

FAQ

Change notification questions teams ask

What is the difference between an ECN and a PCN? +
An engineering change notice generally describes a change to the design, specification or bill of materials of a part, and it is most often issued by the buyer to the supplier. A process change notification describes a change to how a part is made, including materials, tooling, plating, test methods, manufacturing location or sub-tier sources, and it is issued by the supplier to the buyer. The distinction matters contractually because process change is where the risk to qualification sits and where notification clauses most often have gaps in scope.
Which change categories should require approval rather than notification? +
A workable split puts changes that could affect form, fit, function, reliability, regulatory status or qualification into the approval category, and administrative or cosmetic changes into the notification category. In practice that means material substitutions, process changes affecting metallurgy or chemistry, manufacturing site relocation, sub-tier source changes for critical components, test method changes and any change to a part used in a safety or regulated application should require written buyer approval before implementation.
How long should the notice period be? +
Long enough to complete requalification and build a bridge stock position, which means the period should be derived from qualification lead time rather than chosen as a round number. For a part requiring extended life testing, a ninety-day notice period is not protection, it is a courtesy. Buyers with regulated or long-qualification parts commonly negotiate notice periods of six to twelve months for the approval categories, with shorter periods acceptable for changes that do not touch qualification.
What is a last-time-buy right and why does it need tracking? +
A last-time-buy right lets the buyer place a final order at agreed pricing for the pre-change configuration, usually within a defined window after notification. It is the practical remedy when a change cannot be avoided but the buyer needs continuity while requalifying. It also creates a buyer-side deadline. If the window closes without an order being placed, the right expires, and buyers who treat notification as purely informational routinely discover this after the fact. The window should be tracked as an obligation on the buyer, not just as a right on paper.
How do sub-tier changes escape notification clauses? +
Because the clause often binds the direct supplier to notify changes it makes, without requiring the supplier to flow the obligation down to its own suppliers. A tier two source change is then invisible to the direct supplier contractually and to the buyer entirely. Closing this requires explicit flowdown language obliging the supplier to impose equivalent notification duties on its critical sub-tiers, and to notify the buyer of any change it receives notice of, whether or not it originated the change.
What evidence should be retained for change notifications? +
The notification itself with its receipt date, the change category assessment, the qualification or requalification records generated in response, the approval or rejection decision with its date and approver, and any last-time-buy order placed. Retention matters because change history is the first thing examined when a field failure investigation begins, and the question asked is usually whether the change was notified, assessed and approved through the contractual process or whether it arrived without anyone deciding.

Make change notification a tracked duty

See how Aavenir holds supplier notification scope, notice periods, approval gates and last-time-buy windows as monitored obligations against each agreement.

  • ✓Notification scope and flowdown terms extracted per supplier
  • ✓Buyer-side approval and last-time-buy deadlines with escalation
  • ✓Standalone or native on ServiceNow