Process change implemented without QA approval during changeover – regulatory impact assessment case study







Published on 05/01/2026

Further reading: Manufacturing Deviation Case Studies

Case Study: Unauthorized Process Change During Changeover and Its Regulatory Implications

In the dynamic landscape of pharmaceutical manufacturing, adherence to established protocols is paramount. This case study highlights a scenario where a process change was implemented without proper QA approval during a changeover, leading to significant quality and regulatory implications. By the end of this article, you will be equipped with actionable insights to manage similar situations effectively and ensure compliance with regulatory expectations.

If you want a complete overview with practical prevention steps, see this Manufacturing Deviation Case Studies.

This case study walks through the step-by-step approach taken for detection, containment, investigation, and implementation of Corrective and Preventive Actions (CAPA). It offers valuable lessons learned to prevent recurrence and ensure inspection readiness.

Symptoms/Signals on the Floor or in the Lab

During routine production monitoring, operators

reported an unexpected increase in out-of-specification (OOS) results for a particular batch. Key symptoms included:

  • Deviation from established process parameters.
  • Increased scrap rates due to product defects.
  • Unusual operator feedback regarding equipment performance.

These symptoms emerged shortly after a changeover to a new formulation. The correlation between these OOS results and the recent change indicated a potential lapse in adherence to procedural requirements, sparking immediate concern among the QA and production teams.

Likely Causes (by category)

The preliminary investigation categorized likely causes of the deviation under six headings: Materials, Method, Machine, Man, Measurement, and Environment.

Category Potential Causes
Materials Use of non-approved raw materials.
Method Changes in the formulation without proper validation.
Machine Equipment calibrated incorrectly or not suited to new formulation.
Man Lack of training for operators on new processes.
Measurement Inadequate monitoring practices leading to unnoticed failures.
Environment Changes in environmental conditions post-changeover.

Immediate Containment Actions (first 60 minutes)

Upon identifying the OOS results, the following containment actions were initiated within the first hour:

  • Immediate halt of production for the affected batch.
  • Isolation and quarantine of all product batches produced post-changeover.
  • Notification of the QA team and initiation of a deviation report.
  • Sampling of affected batches for thorough testing.
  • Review of the changeover process and documentation for compliance verification.
Pharma Tip:  Unapproved process parameter change during tech transfer – FDA inspection observation breakdown

Compiling this information quickly contributed to a clear understanding of the potential extent of the problem and initiated cross-functional engagement to manage the situation.

Investigation Workflow (data to collect + how to interpret)

The investigation workflow developed encompassed several components, ensuring comprehensive data collection and appropriate analysis:

  1. Gather Documentation: Included change control records, training logs, equipment calibration certifications, and batch records.
  2. Interview Personnel: Key stakeholders involved in the changeover (operators, supervisors, quality personnel) were interviewed to understand their perspectives and adherence to protocols.
  3. Data Analysis: Statistical analysis of OOS results, including trends over time, to identify whether this was a one-off or systemic issue.
  4. Cross-Functional Meeting: Regular meetings involving all relevant departments (QA, Manufacturing, Engineering) to iterate findings and share insights.

This structured workflow helped delineate clear connections between operator actions, equipment performance, and the resultant product quality issues.

Root Cause Tools (5-Why, Fishbone, Fault Tree) and when to use which

Identifying root causes required employing multiple analytical tools:

  • 5-Why Analysis: This method helped drill down through successive layers of “why” to reach core issues. For example, “Why was the process changed?” led to the realization that the change had not been communicated adequately.
  • Fishbone Diagram: A collaborative tool used during workshops to visually categorize potential causes into physical and human factors, aiding in systematic problem exploration.
  • Fault Tree Analysis: Appropriate for complex issues where multiple factors intersect, allowing for a structured examination of potential failures and their interrelationships.

Employing a combination of these tools not only illuminated the root cause but also facilitated discussion between departments, driving a team-based learning culture.

CAPA Strategy (correction, corrective action, preventive action)

The establishment of a robust CAPA strategy was critical following the identification of the root causes:

  • Correction: Immediate rectification of the non-conforming product via disposal and documentation.
  • Corrective Action: Enhanced training on change control processes for all production and QA personnel, ensuring everyone understands the importance of approval and documentation.
  • Preventive Action: Revision of the Change Control SOP to include additional checkpoints and formal sign-offs from QA during changeovers, preventing similar issues in the future.
Pharma Tip:  Critical IPC skipped during scale-up – regulatory impact assessment case study

This systematic approach not only aimed to remedy the immediate problem but also sought to prevent recurrence through embedding quality-driven decisions within the organization.

Control Strategy & Monitoring (SPC/trending, sampling, alarms, verification)

Following the CAPA implementation, an updated Control Strategy and Monitoring framework was established:

  • Statistical Process Control (SPC): Introduced for real-time monitoring of critical process parameters to ensure consistency.
  • Trending Analysis: Regular assessments of production data to identify patterns indicative of deviations before they become significant issues.
  • Sampling Plans: Adjusted sampling frequencies and expanded the scope for testing of batches following changeovers.
  • Alarm Systems: Implemented to alert operators immediately when deviations occur, ensuring a rapid response.
  • Verification Steps: Conducted periodic audits of systems and procedures to ensure compliance and functionality.

Embedding these strategies created a deeper layer of proactive oversight and flexibility to respond to emerging risks promptly.

Related Reads

Validation / Re-qualification / Change Control impact (when needed)

Post-CAPA implementation, it was essential to reassess validation and qualification protocols:

  • Re-validation Needs: Any process that had undergone a change without requisite QA approval necessitated a full validation review.
  • Qualification Procedures: Equipment used in the affected batch was subjected to requalification prior to resuming normal production.
  • Change Control Updates: A new framework was introduced for monitoring change proposals, requiring greater detail and justification before approvals.

This ensured that all changes were scrutinized at multiple levels, safeguarding product integrity and regulatory compliance.

Inspection Readiness: what evidence to show (records, logs, batch docs, deviations)

To reinforce inspection readiness, a thorough collection of evidence was assembled:

  • Complete documentation of the deviation report, including the initial detection, containment actions, and CAPA implementation.
  • Records of all training completed by personnel, emphasizing the importance of adherence to protocols.
  • Batch production records following the implementation of the revised control strategy.
  • Logs documenting regular statistical process control checks and any subsequent corrective actions.
Pharma Tip:  Deviation closed without effectiveness check during changeover – FDA inspection observation breakdown

Compiling and maintaining comprehensive records facilitated not only immediate responses but also long-term compliance during regulatory audits.

FAQs

What steps should be taken if a deviation is detected?

Immediate containment measures should be implemented, followed by thorough documentation and a structured investigation to determine root causes.

How can I ensure all process changes receive correct approvals?

Implement a robust Change Control system that requires multi-level sign-off from QA and operational stakeholders with clear documentation.

What are the implications of unauthorized changes?

Unauthorized changes can lead to product quality issues, regulatory non-compliance, and potential market withdrawal announcements.

Which root cause analysis tool is most effective?

The choice of tool, such as 5-Why or Fishbone, should align with the complexity of the problem and the depth of analysis needed.

How often should re-validation occur?

Re-validation should occur any time a significant change in process, equipment, or raw materials is made, or when non-conformance issues are identified.

What does an effective CAPA system consist of?

An effective CAPA system includes correction, corrective actions, and preventive actions, all documented thoroughly for compliance purposes.

How can data integrity be maintained during investigations?

Data integrity can be maintained through strict adherence to protocols, regular audits, and training, ensuring a culture of quality.

What does inspection readiness entail?

Inspection readiness includes maintenance of accurate records, adherence to SOPs, training documentation, and having CAPA actions properly implemented and documented.

What role does risk management play in change control?

Risk management allows for the identification of potential impacts of changes, guiding the need for additional controls or justification of process modifications.

How should staff be trained to handle deviations?

Staff should receive regular training on SOPs, deviation reporting, corrective actions, and the importance of compliance with QA protocols.

What are the regulatory implications of documented deviations?

Documented deviations provide crucial evidence of compliance but also require thorough investigation and CAPA to prevent recurrence and maintain quality standards.

How can continuous improvement be fostered within the organization?

Establish a culture of continuous improvement through regular training, employee engagement in quality discussions, and encouraging feedback for all operational processes.