What approvals are required when a supplier proposes a process change?

There is no single universal approval path, but in regulated manufacturing the answer is usually: more than the supplier’s internal approval is required.

If a supplier proposes a process change, the required approvals typically depend on:

• contractual and customer flow-down requirements
• whether the part is critical, special-process related, or otherwise controlled
• whether the change could affect fit, form, function, reliability, performance, or traceability
• whether the process was previously qualified, validated, or tied to a first article, control plan, or approved source listing
• your own supplier change-control procedure and risk classification rules

In practice, approvals commonly involve some combination of the following before implementation:

• the supplier’s documented internal change review
• your purchasing or supplier quality review
• your quality approval
• your engineering or manufacturing engineering approval
• customer approval, if required by contract, drawing note, specification, or source-control requirement
• regulatory or delegated authority review where applicable to the program and product, though this is highly context-specific

What usually must be reviewed

The approval decision is rarely just a signature. It usually requires evidence showing what is changing, why, and what the impact could be. Common review items include:

• the exact process step, equipment, tooling, software, location, routing, material source, or sub-tier source being changed
• risk assessment for product quality, process capability, inspection method, and downstream effects
• whether existing qualification or validation remains valid
• whether inspection plans, control plans, work instructions, travelers, or approved methods need revision
• whether part approval, FAIR updates, capability studies, sample submissions, or equivalency data are required
• whether inventory made before and after the change can be segregated and traced

If the change affects a qualified or validated process, prior approvals are often stricter. A supplier cannot reasonably assume that a machine swap, software revision, parameter change, relocation, or sub-tier substitution is administratively minor. In many environments, those are material changes until reviewed and dispositioned.

When customer approval is likely required

Customer approval is often required when the proposed change could alter product realization in a way that was part of the original approval basis. Common triggers include:

• changes to special processes or approved processors
• changes in manufacturing location
• changes in tooling, fixtures, CNC programs, recipes, or critical parameters
• changes in raw material source or sub-tier supplier for controlled items
• changes that may require partial or full first article re-accomplishment
• changes called out explicitly in purchase order terms or supplier quality clauses

If the contract or customer requirements are silent, that does not automatically mean no customer approval is needed. It means your organization needs a documented interpretation and risk-based decision process.

What not to do

Do not let the supplier implement first and document later. That creates avoidable risk around nonconforming product, mixed inventory, broken traceability, and disputed acceptance status.

Also, do not assume an ERP note or email chain is enough. In brownfield environments, approvals often span QMS, ERP, MES, PLM, document control, and supplier portals. If those systems are not aligned, plants can end up with approved paperwork in one system and obsolete routings or work instructions in another. The approval itself is only part of the control problem. Synchronizing the effective date, revision state, and affected lots or serials matters just as much.

Practical rule

A safe general rule is this: if the supplier process change could affect product acceptance, process capability, validated state, or traceability, treat it as a formal change-control event requiring documented review and explicit approval at the appropriate levels before release.

The exact approvers and evidence package are site- and program-specific, and they should be defined in your supplier change procedure, quality clauses, and engineering governance.