How Conflicting Site and Central SOPs Threaten GMP Compliance

Introduction to the Audit Finding

1. What Was Observed

During a recent audit, multiple site-level SOPs were found to contradict corporate or central SOPs on the same process — such as deviation handling and data review timelines.

2. Why It’s a Critical Gap

• Leads to confusion among operators and QA reviewers
• Compromises traceability and consistent GMP practices across sites
• Increases the risk of audit findings and data integrity violations

3. Practical Consequences

For example, a corporate SOP required data review within 5 days, while the site SOP extended it to 10 — leading to missed review deadlines and GMP audit checklist observations.

Regulatory Expectations and Inspection Observations

1. 21 CFR 211.22(d)

Requires written procedures to be followed uniformly across all operations under a firm’s quality control unit.

2. EU GMP Chapter 4.3

States that procedures should be clear, concise, and avoid duplication or contradiction with other quality system elements.

3. WHO TRS 986 Annex 2

Encourages harmonization of procedures and avoidance of parallel conflicting systems.

4. Regulatory Observations

• FDA 483: “Local site SOP for deviation management contradicts central QA policy, leading to variable review timelines.”
• EMA: “Site procedures on OOS testing were found to be inconsistent with the corporate procedure resulting in re-testing without justification.”

Root Causes of SOP Misalignment

1. Lack of Global Governance

No oversight framework to manage central-to-site SOP flow and harmonization.

2. Legacy SOPs Still in Use

Older site SOPs remain active even after corporate SOP rollout.

3. Local Customization Without QA Approval

Site teams modify corporate SOPs for perceived practicality without following change control.

4. Poor Document Control Systems

Multiple versions circulate without status visibility, especially in multinational environments.

Prevention of SOP Conflicts Between Site and Central Procedures

1. SOP Governance Policy

Define in the Quality Manual how central and site SOPs should coexist — when to harmonize, when to localize, and how to document deviations.

2. Tiered SOP Structure

• Level 1: Corporate (Global SOP)
• Level 2: Site (Local SOP with reference to Global SOP)
• Level 3: Work Instructions (specific tasks)

3. Cross-Functional Review Committees

Ensure SOPs are reviewed by both site and central QA before approval, using collaborative platforms.

4. Unified Document Control Systems

Use a centralized electronic Document Management System (eDMS) with version control and audit trail access for both site and global teams.

5. Periodic SOP Reconciliation Audits

Conduct audits comparing site SOPs against corresponding corporate versions to identify discrepancies.

Corrective and Preventive Actions (CAPA)

1. Corrective Measures

• Immediate suspension of conflicting SOPs
• Communication of global SOP as the governing document
• Training and retraining of impacted staff at site

2. Preventive Strategies

Update the SOP on SOP Management to include mandatory alignment checks between site and central procedures prior to approval or revision.

3. Change Control Enforcement

All site SOP customizations must go through formal change control reviewed by central QA.

4. QA Ownership Realignment

Appoint global QA leads responsible for specific SOP clusters to ensure harmonization across regions.

5. Global Training Initiatives

Initiate pharma validation training modules aligned with corporate SOPs to minimize the need for localized variation.

6. Regulatory Best Practice Alignment

Align global and site SOP structures with recommendations from EMA and CDSCO.