GMP Risks When SOPs Are Not Implemented Uniformly Across Shifts

Introduction to the Audit Finding

1. Problem Overview

GMP audit findings revealed that approved and signed SOPs were only partially implemented. While day shift personnel adhered to the updated procedures, night and weekend shifts continued following outdated or unofficial practices.

2. Why It’s a Concern

• Leads to inconsistent operations across the facility
• Results in critical deviations in cleaning, manufacturing, and documentation practices
• Compromises batch integrity and reproducibility

3. Real-World Impact

For example, during a cleaning validation review, night shift records showed different disinfectant contact times than what was approved in the latest SOP.

Regulatory Expectations and Inspection Observations

1. 21 CFR 211.25(c)

Personnel must be trained and perform functions according to the written SOPs applicable to their duties — regardless of shift or schedule.

2. EU GMP Chapter 2.9

All personnel involved in the manufacture of medicinal products must be trained and comply with SOPs, including during off-hours and weekends.

3. WHO TRS 986

Training and procedure implementation must be verified across all operating shifts.

4. Regulatory Findings

• FDA 483: “Night shift operators were not aware of the updated SOP for cleaning operations.”
• MHRA: “Weekend production followed obsolete instructions, resulting in undocumented deviations.”

Root Causes of Incomplete SOP Implementation

1. Shift Handover Gaps

Critical updates not communicated effectively during shift handover meetings or through formal logs.

2. Training Schedule Constraints

Training sessions often conducted during day shifts, with no rescheduled sessions for off-shift personnel.

3. Document Distribution Failure

QA does not verify SOP availability at all workstations for all shifts.

4. Absence of Verification Mechanism

No structured system to confirm SOP implementation across all shifts — leading to gaps in application and monitoring.

Prevention of Shift-Based SOP Implementation Gaps

1. Shift-Specific SOP Rollout Plans

Design and enforce shift-wise training schedules, including weekends and nights, with electronic tracking of attendance and completion.

2. QA Verification Logs

• QA to maintain SOP implementation verification records for all three shifts
• Spot checks across operations to confirm SOP in-use version matches master copy

3. Mandatory Acknowledgement Sheets

All staff must sign SOP update acknowledgment forms — no exceptions based on shift.

4. Real-Time Tracking

Use software tools or training dashboards to track shift-wise implementation metrics and flag gaps.

5. Integration with Stability and Validation Teams

Ensure procedural consistency across shifts especially in activities related to Stability Studies and cleaning validation.

Corrective and Preventive Actions (CAPA)

1. Corrective Measures

• Conduct audit of SOP compliance logs by shift
• Immediately retrain all staff on SOPs not acknowledged across all shifts
• Withdraw and replace any outdated hardcopies in night or weekend areas

2. Preventive Systems

Update SOP on Document Control and SOP Training to include provisions for multi-shift implementation verification and training rescheduling.

3. KPI Monitoring

Track implementation gaps across shifts using compliance KPIs — escalate any deviation through QA governance framework.

4. Regulatory Alignment

Align shift-wise SOP rollouts with expectations of agencies like MHRA and USFDA.

Cleaning Deviations in Batch Records Without Deviation Logging: A Recipe for GMP Trouble

Introduction to the Audit Finding

1. Discrepancies in Batch Records

Cleaning steps recorded in batch records differ from those described in the approved SOPs.

2. Missing Deviation Reports

No deviations were raised to justify or investigate these differences.

3. Critical Audit Observation

This type of mismatch is commonly flagged during GMP inspections as a serious data integrity risk.

4. Non-Conformance Signals

Unlogged deviations suggest systemic gaps in procedural enforcement and documentation culture.

5. Misleading Product Release Decisions

Products may be released based on records that deviate from validated cleaning practices.

6. QA Oversight Breakdown

QA fails to detect or question the inconsistency, highlighting flaws in batch review.

7. Regulatory Risk

Such unreported deviations constitute a breach of GMP principles and may result in 483s or warning letters.

8. Operator Training Deficiency

Operators may not understand when a deviation must be logged or reported.

Regulatory Expectations and Inspection Observations

1. 21 CFR 211.100(b)

Mandates that any deviation from written procedures must be recorded and justified.

2. EU GMP Chapter 5

Requires documentation of all deviations from standard procedures, especially those related to cleaning.

3. WHO GMP Guidelines

State that all discrepancies must be documented and investigated promptly.

4. FDA 483 Example

Cleaning solution concentration used in practice differed from the SOP without documented deviation.

5. MHRA Audit Finding

Operators deviated from hold time limits during equipment cleaning, with no deviation record.

6. TGA Non-Compliance

Batch record noted skipped rinse step; deviation not initiated and batch released.

7. EMA Warning Letter

Disinfection step performed using a different agent not listed in SOP; not reported as deviation.

8. Risk to Stability testing

Improper or undocumented cleaning can introduce unknown variables affecting product shelf-life.

Root Causes of Cleaning Procedure Deviations

1. Informal Practice Drift

Operators follow habitual steps learned over time, not those documented in SOPs.

2. Inadequate SOP Access

SOPs may be inaccessible or outdated, leading staff to rely on memory or informal instructions.

3. Poor Awareness of Deviation Criteria

Staff are unclear on what constitutes a reportable deviation.

4. Absence of Real-Time QA Oversight

No on-floor presence to verify cleaning steps as they occur.

5. Rush to Close Batch Records

Time pressure leads to bypassing documentation steps or “fitting” records to expectations.

6. SOP Lacks Detail

Overly generic cleaning SOPs may leave room for misinterpretation or procedural drift.

7. Poor Training Programs

Training doesn’t include sufficient emphasis on deviation identification and reporting.

8. Weak QA Batch Review

Reviewers may overlook mismatches between batch entries and SOP steps.

Prevention of Unlogged Cleaning Deviations

1. SOP Accessibility

Ensure real-time access to current SOPs at points of use.

2. Training on Deviation Reporting

Explain clearly what constitutes a deviation and how to report it.

3. Visual Aids for Cleaning Steps

Use pictorial flowcharts or laminated checklists to standardize and visualize key steps.

4. Supervisor Walkthroughs

Implement cleaning activity verification by supervisors or QA.

5. Real-Time Logbook Review

Review cleaning log entries on the same day to catch inconsistencies.

6. Include Hold Time and Agent Details in SOP

Specify cleaning parameters such as contact time and agent concentration explicitly.

7. Encourage Deviation Initiation

Foster a non-punitive culture for reporting procedural variances.

8. Reconcile Records vs SOP Periodically

QA should perform periodic checks comparing batch records with SOP content.

Corrective and Preventive Actions (CAPA)

1. Conduct Impact Assessment

Evaluate all batches associated with unlogged deviations for potential contamination or data risk.

2. SOP Revision

Update cleaning SOPs to ensure they reflect practical steps and include deviation triggers.

3. QA Review Protocol Update

Train QA reviewers to verify batch record entries against SOPs during every review cycle.

4. Operator Retraining

Reinforce deviation awareness and proper documentation through immediate training sessions.

5. Implement Cleaning Checklists

Introduce QA-approved checklists to support adherence and documentation consistency.

6. Strengthen Documentation Controls

Use electronic batch recording systems with deviation prompts or alerts.

7. Audit Logs for Cleaning Actions

Introduce time-stamped logs or barcoded steps for traceability.

8. CAPA Monitoring by QA

Track implementation of corrective measures using KPI dashboards to ensure sustainable compliance.