1. Document Control

2. Purpose

This specification establishes the mandatory Quality Control requirement for verification of effectiveness following implementation of any GMP-impacting change executed under QMS Change Control.

This requirement mitigates the risk that implemented changes fail to achieve their intended control objective, introduce unintended consequences, degrade validated state, or weaken established acceptance criteria governing identity, purity, strength, composition, safety, or data integrity.

21 CFR Part 111 requires control over manufacturing, packaging, labeling, holding, and quality operations. Failure to verify change effectiveness may result in adulteration, misbranding, data integrity failure, or loss of validated control state, exposing the firm to regulatory enforcement action.

3. Regulatory Basis

• 21 CFR 111.100 — Requirement to establish and follow written procedures for quality control operations.
• 21 CFR 111.140 — Requirement to establish a system of production and process controls.
• 21 CFR 111.180 — Requirement to maintain and follow a quality control system.

4. Scope

Applies To: All GMP-impacting changes implemented under QMS Change Control affecting processes, specifications, equipment, utilities, facilities, systems, software, training curricula, suppliers, materials, documentation, or control parameters.

Excludes: Administrative or non-GMP changes with no impact on product quality, data integrity, regulatory status, or validated state.

5. Definitions

Compliant State: Effectiveness verification completed, objective evidence demonstrates intended outcome achieved, no adverse impact detected, and QU authorization documented.

Nonconforming State: Effectiveness criteria not fully met or adverse impact identified requiring QMS workflow.

Invalid State: Change implemented without defined effectiveness criteria, missing required data, or missing required QU authorization.

Escalation Trigger: Objective condition requiring mandatory entry into Deviation, CAPA, Quality Defect, or Change Control reassessment workflow.

Stop-Execution Condition: Execution is prohibited when effectiveness verification identifies risk to product quality, data integrity, validated state, or regulatory compliance.

6. Acceptance Criteria

7. Decision Logic Matrix

8. Exception Handling

When effectiveness criteria are not met, Deviation entry is mandatory.

When systemic failure or repeated ineffective changes occur, CAPA entry is mandatory.

When product impact is identified, Quality Defect entry is mandatory.

When change scope or criteria require modification, Change Control reassessment is mandatory.

9. Required Records

Base Execution Record

• Approved Change Control Record
• Defined Effectiveness Criteria
• Post-Implementation Performance Data

Conditional Workflow Records

• Deviation Record (if triggered)
• CAPA Record (if triggered)
• Quality Defect Record (if triggered)

QU Authorization Record

• Formal QU approval of effectiveness closure

10. Authority Classification

E — Execution: Trained personnel may collect data and document results.

W — Workflow Entry: QA administers QMS workflow entries.

A — Authorization: QU authorizes final closure of change effectiveness.

Execution authority does not confer product disposition authority.

11. Control State Definitions

Compliant, Nonconforming, and Invalid states are defined in Section 5 and are mandatory across all domains.

12. Change Control

Change Control entry is required for any modification to this specification.

Independent QU approval is required.

No implementation is permitted without documented QU authorization.

13. References

• QC-REQ-IDX
• QMS Change Control SOP
• 21 CFR Part 111