Glossary
Change Management
Definition
Change management in food manufacturing is the documented process for identifying, evaluating, approving, implementing, and recording modifications to food production processes, ingredients, suppliers, equipment, facilities, or procedures while keeping food safety and regulatory compliance intact throughout.
Every operational change carries the potential to introduce a new hazard or increase an existing one.Under 21 CFR Part 117, FDA expects you to assess changes before they take effect, have a qualified individual review them, and update your food safety plan where necessary.
In practice: if it changes how food is made, received, or handled, there should be a record showing the change was evaluated for safety risk, approved by the right person, implemented correctly, and verified. No record means no defense when an investigator walks in.
Where It Fits
Change management sits at the intersection of your food safety plan, your preventive controls program, and your supplier qualification process. It's not a standalone procedure. It's what keeps every other program current when operations shift.
Relevant frameworks and where change management appears:
- FSMA / 21 CFR Part 117: Reanalysis requirements under § 117.170 are the primary regulatory driver. Preventive control management under § 117.140 requires that monitoring, corrective actions, and verification remain effective when changes occur.
- GFSI-recognized schemes (SQF, BRCGS, FSSC 22000): All three evaluate food safety culture as an audit dimension, including whether your organization identifies and responds to changes without compromising food safety. See our GFSI schemes overview for scheme-specific requirements.
- Supply chain programs (21 CFR Part 117, Subpart G): Changes upstream, at a supplier's facility, can trigger reassessment of your verification activities under §§ 117.410 and 117.435.
- FSMA 204 traceability: Changes to ingredient sourcing or supply chain routing intersect with Critical Tracking Events and Key Data Elements. Architecture decisions made now will affect your compliance posture when the rule's requirements take full effect.
Real-World Use Cases
A procurement team swaps to a lower-cost flour supplier mid-quarter without flagging the change to quality. The new supplier's facility processes tree nuts on shared lines. The allergen profile of the incoming ingredient has changed, but the food safety plan hasn't. A quality director at a bakery operation catches this during an internal audit, but only after two weeks of production. The reanalysis, allergen control update, and CAPA process that follow are significantly more expensive than a 20-minute change review would have been.
A mid-size beverage manufacturer's primary juice supplier relocates their processing facility across state lines. The account manager gets an email, it sits in a shared inbox, and no one routes it to the supplier qualification team. Under 21 CFR § 117.410, the receiving facility's supplier quality management obligations don't disappear when a supplier moves, they shift to a new facility that hasn't been evaluated. By the time the annual supplier review surfaces the gap, the receiving facility has a year of unvalidated supply.
A private equity-backed food group acquires a three-plant regional processor. During due diligence, they confirm the target has food safety plans, but post-close, the integration team discovers that two of the three facilities list the same individual as PCQI, and that person left the company eight months earlier. Every change approved in that period lacks compliant PCQI sign-off. The documentation gap is now a board-level conversation about inherited compliance debt.
After a CAPA finding, a plant's sanitation team adjusts the dwell time on a key chemical step. The change is implemented on the floor immediately, but the written procedure isn't updated for six weeks. When a third-party auditor asks to verify that sanitation procedures match current practice, the facility can't demonstrate it. The finding is minor on its own; combined with two other documentation inconsistencies from the same audit cycle, it contributes to a conditional certification.
FAQs
The regulatory standard under 21 CFR § 117.170(d) focuses on whether a change creates a reasonable potential for a new hazard or a significant increase in a previously identified hazard. That determination requires professional judgment by a PCQI. What matters most: the judgment call, whether it concludes a full reanalysis is needed or not, must be documented. "We looked at it and decided no revision was needed" is a defensible position, but "we didn't look at it" is not.
A PCQI must perform or oversee reanalysis under 21 CFR § 117.170(e). Operational approval typically involves Quality, Operations, and relevant subject matter experts depending on the change's scope. The PCQI requirement isn't a formality. It's the compliance anchor, one role, one sign-off, and without it the review doesn't count. Our PCQI responsibilities guide covers what that role owns in practice.
No. Supplier changes, regulatory updates, new FDA guidance, and GFSI scheme revisions can all trigger reanalysis obligations even if nothing in your own facility has changed. Changes upstream don't stay upstream: when a supplier modifies their process or facility, your food safety plan may need to reflect that change.
A change is a planned or intentional modification to a process, ingredient, supplier, or procedure. A deviation is an unintended departure from an established parameter or step. Both require documentation, but they follow different response workflows. Deviations typically route to CAPA; changes route to hazard analysis and reanalysis. The practical risk: a "temporary" deviation that becomes standard practice without going through the change management process is a compliance gap waiting to be found.
Start with an inventory of changes made in the last 12 months and check whether each has a documented hazard evaluation and PCQI review on record. Gaps there tell you exactly where your exposure sits. From that baseline, build a formal change identification step at the point of initiation, not retrospectively. The key components of food safety compliance guide covers how to structure the broader program.
Yes, with a caveat. The current compliance deadline for full FSMA 204 implementation is July 2028, though organizations making architecture decisions now should monitor FDA guidance given the rule's history of adjustment. Changes to ingredient sourcing, supplier locations, or supply chain routes intersect with Critical Tracking Events and Key Data Elements under the traceability rule. Building change management processes in isolation from your traceability program creates rework when requirements take hold. See our FSMA 204 traceability resource for current guidance.
Compliance Requirements
- 21 CFR § 117.170(d): The core mandate. You must revise your written food safety plan if a significant change creates a reasonable potential for a new hazard or a significant increase in a previously identified hazard, or document why no revision was needed. This applies every time a significant operational change occurs. All initial compliance deadlines have passed.
- 21 CFR § 117.170(e): A Preventive Controls Qualified Individual (PCQI) must perform or oversee the reanalysis. This is not a step you can delegate to someone without that qualification.
- 21 CFR § 117.170(f): FDA can require reanalysis when new hazards or developments in scientific understanding warrant it, independent of any change you've initiated.
- 21 CFR § 117.140: Preventive control management components, including monitoring, corrective actions, and verification, must remain effective when changes occur. A process modification that affects a critical control point without a corresponding monitoring update creates a gap that auditors will find.
- 21 CFR §§ 117.410 and 117.435: Supplier verification obligations don't pause when a supplier makes changes. When a supplier modifies their process, relocates a facility, or changes control measures, that should prompt reassessment of your verification activities. Depending on the risk profile of the change, that reassessment may include an onsite audit under § 117.435.
Non-compliance consequences: FDA warning letters regularly cite preventive control failures, HACCP plan deficiencies, and recordkeeping gaps, and in many cases, those findings trace back to operational changes implemented without corresponding documentation updates. At multi-site scale, a single undocumented change at one facility is rarely treated as an isolated finding. Your organization's program maturity across the entire portfolio is what regulators are assessing.
Ready to See SafetyChain in Action?
Book a Demo