Management
of Change in Quality Systems: When Every Modification Becomes a
Controlled Event — Not a Surprise That Derails Your Production
You’ve seen it happen a hundred times. Someone swaps a material
supplier to save three cents per unit. A maintenance technician replaces
a worn sensor with a “compatible” alternative from a different
manufacturer. An engineer adjusts a temperature profile by two degrees
because the new batch of resin feels different. Six weeks later, your
customer sends you a container of parts that failed in the field — and
the investigation trail leads back to a change nobody documented, nobody
assessed, and nobody approved.
Welcome to the most underestimated killer of quality in
manufacturing today.
The Invisible Assassin of
Quality
Let me be direct with you. Most quality failures in mature
manufacturing systems don’t come from bad design, poor training, or
incompetent operators. They come from uncontrolled
change. A process that was validated, proven, and stable is
subtly altered — and the alteration creates a cascade of effects that
nobody anticipated.
I learned this lesson the hard way. We had a production line running
at a Cpk of 1.67 — textbook capability, beautiful control charts,
everything humming. Then the purchasing department switched our adhesive
supplier. Same specification on paper. Same technical data sheet
numbers. The engineering team wasn’t even notified. Three months later,
we had field failures in a safety-critical application. The root cause?
The new adhesive had identical bulk properties but different surface
energy characteristics that affected bonding on our specific substrate
geometry.
The cost of that “cost-saving” switch? Fourteen times the annual
savings projected by purchasing. Plus a customer audit. Plus a line
shutdown. Plus the kind of meeting where your name appears on a
PowerPoint slide in red font.
That day, I became a believer in Management of Change — not as a
bureaucratic exercise, but as the single most important quality gate
your organization can build.
What Is Management of Change?
Management of Change (MOC) is a systematic process for evaluating and
controlling modifications to processes, equipment, materials, personnel,
and organizational structures that could affect product quality, safety,
or regulatory compliance.
It’s not a form. It’s not a checklist. It’s a disciplined
decision-making framework that forces your organization to
answer four questions before any change takes effect:
- What exactly is changing? — Not the intent, not the
hoped-for outcome. The precise technical modification. - What could go wrong as a result? — A honest,
structured risk assessment by people who understand the process
deeply. - What do we need to do to make this change safely? —
Actions, validations, notifications, training, approvals. - How will we verify the change worked as intended? —
Post-change monitoring, confirmation runs, data review.
If you can’t answer all four, the change doesn’t happen. Period.
The Anatomy of an
Effective MOC System
Change Identification and
Initiation
Every MOC begins with someone saying, “We need to modify something.”
The trick is capturing all the changes, not just the
ones people remember to flag.
Changes that must go through MOC include the obvious ones: new
equipment, process parameter modifications, material substitutions,
facility modifications. But the list also includes the subtle ones:
software updates on PLCs, replacement of gauge types, changes to
inspection frequencies, reassignment of key personnel, new suppliers for
indirect materials, modifications to utility systems.
I recommend maintaining a trigger list — a living
document that catalogs every category of change that requires MOC
review. This list should be developed by a cross-functional team and
reviewed quarterly, because your operation will evolve and new
categories of change will emerge.
The initiation should include: – Change description
— Technical specificity, not management summary – Reason for
change — The problem being solved or opportunity being pursued
– Proposed implementation date — Which drives the
timeline for assessment – Change owner — The single
person responsible for shepherding the change through the process
Risk Assessment: The Heart of
MOC
This is where most MOC systems either earn their keep or become
rubber stamps. A proper MOC risk assessment is not a quick conversation
in a hallway. It’s a structured evaluation using the tools your
organization already knows — FMEA logic, hazard analysis, impact
matrices — applied specifically to the proposed change.
The assessment must consider:
Product quality impact. Could this change affect
critical-to-quality dimensions, material properties, functional
performance, or appearance characteristics? How? Under what
conditions?
Process stability impact. Could this change shift
the process mean, increase variation, alter the shape of the
distribution, or create new failure modes?
Supply chain impact. Does this change affect
downstream processes, customer specifications, regulatory submissions,
or supplier quality agreements?
Validation status impact. Does this change
invalidate any existing validation protocols, process capability
studies, or qualification reports?
Personnel and training impact. Do operators,
inspectors, or maintenance staff need new training, updated work
instructions, or revised qualification records?
The risk assessment team should include process engineers, quality
engineers, production supervisors, and — critically — experienced
operators. The people who run the process every day see things that no
risk matrix can capture.
Approval: The Gate That Must
Hold
An effective MOC system has defined approval levels based on risk
severity. Low-risk changes might require a quality engineer’s sign-off.
Medium-risk changes require the quality manager and the process owner.
High-risk changes — anything affecting safety-critical characteristics,
validated processes, or regulatory commitments — require plant
management approval.
The key principle: the approver must be independent of the
change request. The person who proposed the change cannot be
the person who approves it. This isn’t distrust — it’s basic engineering
discipline. You wouldn’t let the person who designed a bridge also be
the sole inspector of its structural integrity.
Implementation: Controlled
Execution
Once approved, the change is implemented according to a documented
plan. This plan includes:
- Pre-change baseline data collection
- Specific implementation steps with responsible parties
- Updated documentation: work instructions, control plans, FMEAs, flow
diagrams - Training completion records for all affected personnel
- Communication to internal stakeholders and, when required, to
customers - Supplier notifications if the change affects supplier quality
requirements
Every step has a completion date and a verification method. The
change owner tracks progress and resolves obstacles.
Post-Change
Verification: Proving It Worked
This is the step most organizations skip — and it’s the one that
catches them.
After implementation, you must verify that the change produced the
intended result without introducing unintended consequences. This
means:
- Monitoring key process indicators for a defined
period — typically 30 to 90 days depending on risk level - Comparing post-change data to pre-change baselines
using statistical methods, not visual inspection of charts - Conducting confirmation runs for process-critical
changes - Reviewing first-article inspection results after
changes to tooling, materials, or process parameters - Auditing updated documentation to confirm it
matches actual practice
If the verification reveals problems, the MOC system must have a
clear escalation path — including the authority to reverse the change if
necessary.
The MOC FMEA Connection
One of the most powerful applications of MOC is linking it directly
to your FMEA process. Every time a change is proposed, the corresponding
FMEA should be reviewed and updated. This creates a living risk
management system where your FMEAs actually reflect current process
conditions rather than becoming dusty documents filed after the initial
process launch.
Here’s the framework: When a change is initiated, the MOC review team
pulls the relevant FMEA and evaluates whether the change introduces new
failure modes, increases the severity or occurrence ratings of existing
failure modes, or reduces the effectiveness of current controls. The
FMEA gets updated in real-time, the control plan gets adjusted
accordingly, and the entire quality planning system stays synchronized
with reality.
This connection transforms FMEA from a one-time compliance exercise
into a continuous risk management tool — which is what it was always
meant to be.
Common Failure Modes of MOC
Systems
After implementing MOC systems in organizations ranging from
fifty-person automotive suppliers to multinational pharma manufacturers,
I’ve seen the same failure patterns repeat. Let me save you from
them.
Failure Mode 1: The Rubber
Stamp
The MOC form exists, but nobody takes the risk assessment seriously.
Every change is classified as “low risk” to avoid the burden of thorough
evaluation. The approval signature becomes a formality rather than a
genuine decision point.
The fix: Audit your MOC system. Randomly select ten
completed MOCs and read the risk assessments. If they all say “no impact
expected” or use identical boilerplate language, your system is broken.
Train the reviewers. Enforce meaningful assessment. Make the quality of
MOC reviews a measurable expectation.
Failure Mode 2:
The Change That Wasn’t a Change
People don’t intentionally circumvent MOC — they genuinely don’t
recognize that what they’re doing constitutes a change. A maintenance
technician replaces a motor with a “same” motor from a different
manufacturer. A procurement specialist buys a cleaning solvent from a
new vendor because the old one is out of stock. A production supervisor
adjusts cycle time to meet a shipment deadline.
The fix: Training, yes — but more importantly, make
the trigger list visible, accessible, and part of daily routine. Post it
in maintenance shops. Include it in purchasing procedures. Embed MOC
triggers into your change control software so that certain actions
automatically flag a review requirement.
Failure Mode 3: The
Emergency Bypass
Emergencies happen. Equipment fails mid-production. A safety issue
requires immediate action. The temptation to implement the fix now and
document the MOC later is enormous — and sometimes justified. But
“later” often becomes “never,” and the emergency change becomes
permanent without assessment.
The fix: Build an emergency change procedure into
your MOC system. Allow immediate implementation for genuine emergencies,
but require that a retrospective MOC be completed within a defined
timeframe — typically 72 hours. No exceptions. The emergency procedure
should require notification of the quality manager before
implementation, not after.
Failure Mode 4: The Silo
Effect
Engineering initiates a change, evaluates the impact, implements it,
and tells quality about it afterward. Or purchasing switches a supplier
and informs production when the new material arrives at the dock. The
MOC system exists, but it operates within departmental boundaries rather
than across them.
The fix: MOC is inherently cross-functional. The
review team must include representatives from every function that could
be affected. Make cross-functional participation a non-negotiable
requirement, not an optional invitation.
MOC in Regulated Industries
If you’re in aerospace, automotive, pharmaceutical, or medical device
manufacturing, MOC isn’t optional — it’s a regulatory requirement. But
the way you implement it determines whether it’s a burden or a
competitive advantage.
In aerospace, AS9100 and NADCAP require documented change control for
special processes. In automotive, IATF 16949 Section 8.5.6 explicitly
requires control of changes to production processes. In pharma, FDA 21
CFR Part 820 requires design changes to be documented, verified, and
validated before implementation.
The regulatory requirement gives you the mandate. The MOC system
gives you the method. Use both to build something that protects your
customers and your organization.
Measuring MOC Effectiveness
You can’t manage what you don’t measure. Here are the metrics that
tell you whether your MOC system is actually working:
-
MOC cycle time — Average time from initiation to
closure. Track trends. If cycle time is growing, your system is becoming
a bottleneck. If it’s shrinking, check whether rigor is being sacrificed
for speed. -
Post-change quality incidents — How many quality
events in the past year trace back to a change that went through MOC? If
the number is significant, your risk assessment process needs
strengthening. -
Uncontrolled change rate — How many changes are
discovered during audits that bypassed the MOC system? This is your most
important metric. It measures the gap between your documented process
and actual practice. -
MOC completion rate for emergency changes — What
percentage of emergency changes receive retrospective MOC review within
the required timeframe? This metric exposes the “fix it now, document it
never” problem. -
Customer notification timeliness — For changes
requiring customer notification, how consistently are notifications sent
before implementation?
The Digital MOC Advantage
Modern quality management systems are moving MOC from paper forms to
digital workflows. This isn’t just about convenience — it’s about
capability.
A digital MOC system can automatically route change requests to the
right reviewers based on the type and risk level of the change. It can
link directly to your FMEA database, control plans, and process
validation records. It can trigger post-change verification tasks
automatically. It can generate dashboards showing the status of every
active change and flag overdue items.
But here’s what technology cannot replace: judgment.
The best MOC system in the world is worthless if the people using it
don’t have the knowledge, experience, and authority to ask hard
questions and demand honest answers. Technology accelerates the process.
People make it meaningful.
Building Your MOC Culture
Systems without culture are just paperwork. The most technically
perfect MOC procedure will fail in an organization where people view
change control as bureaucracy, where supervisors encourage operators to
“just make it work,” and where the response to a proposed MOC review is
“we don’t have time for that.”
Building a MOC culture means:
Leadership commitment. When plant management treats
MOC approvals with the same seriousness as safety incident
investigations, the organization follows. When leaders bypass the system
“just this once,” everyone learns that the system is optional.
Transparency about failures. When an uncontrolled
change causes a quality escape, make it a learning event — not a blame
event. Show the organization how MOC would have prevented it. Let people
see the cost of skipping the process.
Recognition of good MOC practice. When an engineer
identifies a subtle risk during MOC review that prevents a major quality
issue, celebrate it. Make it visible. Show that thorough change
management is valued behavior.
Continuous improvement of the MOC system itself.
Audit your MOC process. Measure its effectiveness. Ask the people who
use it what’s working and what isn’t. The MOC system should be subject
to the same PDCA discipline it helps enforce.
The Bottom Line
Every manufacturing process is a balance — a carefully tuned system
of materials, methods, machines, measurements, environment, and people.
That balance was achieved through design, validation, and continuous
refinement. Uncontrolled change disrupts that balance in ways that are
often invisible until the consequences become impossible to ignore.
Management of Change is your organization’s immune system against
disruption. It doesn’t prevent change — it ensures that change is
intentional, assessed, controlled, and verified. It transforms “we
didn’t see that coming” into “we evaluated that possibility and here’s
what we decided.”
The next time someone on your team proposes a modification — any
modification — ask the four questions. What’s changing? What could go
wrong? What do we need to do? How will we verify? Those four questions,
asked consistently and answered honestly, will save you from the most
preventable quality failures in manufacturing.
Not because change is dangerous. But because uncontrolled change
is.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming manufacturing organizations across
automotive, aerospace, and industrial sectors. He specializes in
building quality management systems that don’t just comply with
standards — they create competitive advantages. His approach combines
deep technical knowledge with practical shop-floor experience, helping
organizations move from reactive firefighting to proactive quality
leadership.
