When Process Validation SOPs Diverge from Practice: Closing the GMP Gap

Introduction to the Audit Finding

1. Defining the Issue

Process validation SOPs are often detailed, but their execution in actual operations may not fully align. This disconnect signals non-compliance and poor oversight.

2. How the Gap Appears

• SOP outlines three validation batches, but only two are executed
• Environmental monitoring during validation is skipped despite SOP requirements
• Data logging steps stated in SOP are bypassed during practical runs

3. Compliance Risks

Deviating from the process validation SOP introduces unapproved variations, invalidates study outcomes, and poses a data integrity threat — all serious GMP audit checklist violations.

4. Regulatory Lens

Agencies like USFDA consider these inconsistencies as systemic failures in validation governance, often classifying them as major or critical deviations.

Regulatory Expectations and Inspection Observations

1. 21 CFR 211.100 and 211.110

Mandate that written production procedures must be followed and that process controls must be validated and reproducible.

2. EU GMP Annex 15 – Validation and Qualification

Emphasizes that actual practices must reflect approved validation protocols and SOPs. Any deviation must be documented and justified.

3. WHO TRS 1019 (Annex 6)

Calls for strict alignment between protocol execution and documented procedures, especially during process validation.

4. Sample Audit Observations

• FDA: “Process validation was conducted with batch size larger than that specified in the SOP.”
• MHRA: “Protocol acceptance criteria were altered without revision of the SOP or documented justification.”
• EMA: “Validation run skipped hold time step mentioned in approved SOP.”

Root Causes of Discrepancies

1. SOPs Not Updated

Changes in equipment or process conditions may occur, but corresponding SOPs remain outdated, causing mismatch during execution.

2. Informal Workarounds

Operators may perform steps based on past experience or verbal instruction rather than written SOPs.

3. Insufficient Training

Staff executing validation may not fully understand protocol requirements or how to interpret ambiguous SOP language.

4. Weak QA Oversight

Quality Assurance fails to detect or prevent divergence during review of validation execution and summary reports.

5. No Verification Checks

Execution teams lack real-time verification or use of checklists to ensure full SOP compliance during each validation run.

Prevention of SOP-Practice Gaps

1. SOP-Proofing During Protocol Drafting

Cross-verify protocol steps with existing SOPs. Every protocol line item must trace back to an SOP reference.

2. Validation Execution Checklists

Create process-specific checklists derived from SOPs to use during real-time validation execution.

3. Training on SOP-Practice Consistency

Conduct sessions demonstrating how small deviations from SOP can compromise validation credibility and product safety.

4. Joint Review Meetings

Schedule QA, validation, and operations review of every protocol before execution to identify and resolve inconsistencies.

5. Digital Execution Systems

Use of Manufacturing Execution Systems (MES) or e-validation tools that enforce SOP-defined steps reduces risk of deviation, as seen in stability testing platforms.

Corrective and Preventive Actions (CAPA)

1. Gap Mapping of Past Validations

Review completed validation records against SOPs to detect deviations. Document and assess impact retrospectively.

2. CAPA Implementation Example

• Root Cause: SOP lacked hold time validation steps
• Corrective Action: Update SOP and re-train operators
• Preventive Action: Implement SOP-protocol alignment review form before any validation

3. Re-training QA and Validation Teams

Use examples from regulatory citations and internal audits to train teams on validation-SOP alignment best practices.

4. Incorporate into Internal Audit Checklist

Every QA audit should include “SOP vs Execution” as a scored compliance metric.

5. Link Validation Execution to Document Control

Use document control systems to block validation protocol release unless linked SOP is current and approved.