Engineering Change vs Production Change: Two Change-Management Workflows That Cannot Be Swapped

Key takeaways

• Engineering change (EC) = change to the product design.
• Production change (PC) = change to how the product is made (process, equipment, parameters).
• Different governance, different stakeholders, different validation.
• Confusing them produces poor traceability and audit findings.
• Both need formal workflows: request, review, approval, validation, implementation, post-change verification.

Short answer: Engineering change alters the product design; production change alters how the product is made. They sound similar and overlap in some cases, but they have different governance, different validation needs, and different risk profiles. Confusing them produces poor traceability and audit findings. See also Production Monitoring vs OEE.

What engineering change covers

• Geometry changes.
• Material substitutions.
• Tolerance updates.
• BOM additions or removals.
• Specification revisions.
• Functional changes.

Owned by engineering. Affects all subsequent production.

What production change covers

• Process step modifications.
• Equipment substitution.
• Recipe parameter updates.
• Tooling changes.
• Material handling.
• Operator workflow.

Owned by manufacturing engineering or operations. Affects how the same designed product is produced.

Where they overlap

Some changes touch both:

• Material substitution may require both design approval and production validation.
• Geometry change may require new tooling (production change to implement EC).
• Tolerance change may require new measurement process.

These are linked changes — EC plus dependent PC. Workflow links them but each has its own approval path.

The engineering change workflow

1. EC request. From engineering, customer, regulatory.
2. Impact analysis. Drawings, BOM, downstream effects, customer notification.
3. Engineering review. Design integrity, performance, manufacturability.
4. Customer approval if applicable.
5. Implementation cutover. Date and lot identification.
6. Effectivity tracking. Which serial numbers / lots use the new design.
7. Documentation update. Drawings, specifications, manuals.

The production change workflow

1. PC request. From operations, maintenance, engineering.
2. Risk and quality assessment. Does the change affect product compliance?
3. Production review. Manufacturing engineering, quality, maintenance, operations.
4. Validation plan. How will the change be verified before full production.
5. Pilot implementation. Small batch under the new process.
6. Quality verification. Pilot results meet spec.
7. Full implementation. Documented procedures updated.
8. Post-change monitoring. First weeks under new process tracked.

Common confusions

1. Production change passed off as engineering change. Process change without engineering involvement. Risk if it affects product compliance.

2. Engineering change implemented without production change planning. New design issued; production not ready; first production batch produces defects.

3. Same workflow for both. Misses governance differences; audit finds.

The traceability requirement

Both ECs and PCs need traceability:

• What changed.
• When it took effect.
• Which products affected.
• Who approved.
• What validation was done.

ISO 9001 and IATF 16949 audits look for this.

The validation depth difference

EC validation: design integrity, functional performance, customer acceptance.

PC validation: process capability, quality consistency, equipment performance, operator workflow.

Different depth, different stakeholders.

Common mistakes

1. No formal change workflow at all. Changes happen informally; traceability is lost.

2. Single workflow for both. Different governance is lost.

3. Skipping post-change monitoring. Issues from the change appear weeks later without attribution.

4. No effectivity tracking. Cannot tell which serial numbers have the new design.

What changes with disciplined workflow

• Quality issues attributable to specific changes.
• Regression detection becomes possible.
• Audit-ready records.
• Cross-functional alignment.

How OEE relates

Production changes affect OEE — new process, new equipment, new parameters all impact Performance and Quality. Tracking PC implementation against OEE shows whether the change delivered.

How a modern OEE platform supports change tracking

A modern OEE platform tracks production parameters over time, surfaces OEE changes correlated with parameter changes, and supports post-change verification.

Fabrico's OEE module tracks production parameters and surfaces OEE changes correlated with parameter changes — supporting post-change verification for production changes.

See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.

Related reading

• Production Monitoring vs OEE

Frequently asked questions

Should I have one or two systems?

Logically separate workflows; physically can be one PLM or QMS system with two change types.

Who approves PCs?

Manufacturing engineering, quality, operations typically. May include external customer approval for certain changes.

What is a deviation vs PC?

Deviation is one-time exception; PC is permanent. Different workflows.

Do PCs always require customer approval?

In regulated industries often yes for any change that affects product spec or process. Document the requirement.

What is the biggest mistake?

No formal workflow at all. Informal changes happen; traceability lost.