Unapproved Temporary SOP Changes: A Risky Shortcut in GMP Environments

Introduction to the Audit Finding

1. Unrecorded Emergency Changes Violate GMP

Temporary alterations to SOPs during emergencies must be documented under formal change control. Failure to do so constitutes a serious compliance gap.

2. Common Scenario: “Just This Once” Deviations

Personnel may bypass SOP instructions during an equipment breakdown or batch urgency — often without prior QA approval or documented justification.

3. Real-World Implications

These undocumented changes can lead to inconsistent practices, deviations, and untraceable product impact assessments.

4. Risk to Product Quality

Non-standard execution without evaluation introduces uncontrolled variables that may compromise product safety or efficacy.

5. Why It’s a Regulatory Red Flag

This practice demonstrates poor procedural discipline, lack of control culture, and systemic failure to manage change under GMP frameworks.

6. Auditors Look for This Gap

Inspectors often identify undocumented temporary practices during batch record reviews, operator interviews, or deviation logs.

7. Disconnect Between Operations and QA

Lack of QA oversight in emergency actions indicates ineffective cross-functional communication and control.

8. Undermines QMS Integrity

If temporary changes are executed without formal mechanisms, the credibility of the entire quality system is at risk.

Regulatory Expectations and Inspection Observations

1. 21 CFR 211.100 (a)

Requires written procedures to be followed, and deviations must be justified and recorded.

2. EU GMP Part I, Chapter 1.4

Demands that quality systems maintain a state of control and that changes are authorized and documented.

3. WHO TRS 986

States that temporary changes should follow the same control and review process as permanent ones.

4. FDA 483 Observations

Commonly cite “lack of change control documentation” where firms made emergency adjustments to procedures or equipment use without traceable records.

5. MHRA Citations

Have flagged firms for allowing unapproved temporary SOP modifications during deviation events without CAPA linkage.

6. USFDA Warning Letters

Often emphasize that any procedural modification, even temporary, requires full documentation and approval.

7. Example: Sterile Manufacturing

In one case, an operator used a different disinfection process due to unavailable material — not documented until found in audit interview.

8. Highlighted by GMP audit checklist

Emergency procedures are a specific section assessed during GMP audit readiness checks.

Root Causes of Undocumented Emergency SOP Changes

1. Pressure to Maintain Production Flow

Operators or supervisors may opt for workarounds under pressure to meet timelines or avoid batch rejections.

2. Absence of Emergency Change SOP

Some companies do not have a formal SOP covering urgent procedural changes, leaving ambiguity in expectations.

3. Inadequate Training

Personnel are often unaware that any deviation, regardless of intent or urgency, must be logged and evaluated.

4. Lack of QA Accessibility

If QA representatives are not available in real-time, teams may proceed with changes to avoid downtime.

5. Weak Change Control Culture

Organizational mindset may trivialize temporary deviations, assuming no harm done means no documentation needed.

6. Missing Audit Trail Capabilities

Electronic or manual systems may not be designed to capture and alert QA on process deviations in real time.

7. Ineffective Internal Audits

Recurring emergency changes may go unnoticed if audit programs don’t examine informal practices.

8. Clinical trial protocol Disconnects

In cross-functional studies, emergency changes made by clinical teams are not always integrated into QMS workflows.

Prevention of SOP Deviations During Emergency Changes

1. Develop a Dedicated Emergency Change SOP

Define what constitutes an emergency, and outline steps for controlled execution, documentation, and post-review.

2. Empower QA to Review in Real-Time

Provide tools and access for QA personnel to evaluate and approve emergency changes without delay.

3. Add Triggers to Deviation Reporting Systems

Configure deviation forms to include a checkbox for emergency SOP modifications.

4. Include Emergency Change Modules in Training

Ensure all relevant personnel know how to handle urgent process variations compliantly.

5. Pre-Define Acceptable Emergency Scenarios

List known critical risk points and potential emergency adaptations, with predefined evaluation checklists.

6. Automate Notification Alerts

Link MES/LIMS or manual logs to notify QA and supervisors when deviations are recorded.

7. Audit Emergency Scenarios Quarterly

Include mock emergency drills to test SOP adherence and documentation discipline.

8. Benchmark Against Stability testing protocols

Use controlled conditions from stability protocols to simulate and plan for temporary operational changes.

Corrective and Preventive Actions (CAPA)

1. Immediate Correction

Identify all past emergency changes not logged under change control. Document them as retrospective deviations.

2. Root Cause Analysis

Perform cause analysis for each undocumented change — process pressure, knowledge gap, or system failure.

3. Revise or Create Emergency Change SOP

Clearly define procedure for initiating, approving, executing, and closing emergency SOP changes.

4. Change Control System Enhancement

Update the change control SOP to include emergency event criteria and handling procedures.

5. Training Rollout

Conduct targeted training sessions for production, QA, and maintenance staff on emergency change compliance.

6. Implement Emergency Review Board

Create a task force that reviews and approves emergency changes rapidly while ensuring compliance.

7. Link Emergency Events with CAPA

Every emergency procedural change must trigger a CAPA review to assess system gaps.

8. Continuous Monitoring

Set monthly review cycles to identify recurrence or trends in emergency deviations.