Verifying design change approval records is a critical quality and compliance activity, ensuring changes are properly assessed, authorized, and implemented. Here’s a structured approach to thorough verification:

1. Completeness: All required information is present.
2. Compliance: Process aligns with internal procedures and external regulations.
3. Traceability: Clear links between the change request, approval, implementation, and verification.
4. Effectiveness: Change was implemented correctly and achieves intended results.

Step-by-Step Verification Process

Preparation & Scope Definition

• Identify Relevant Records: Gather all documentation for the specific design change:
  • Design Change Request (DCR) / Engineering Change Notice (ECN)
  • Impact Assessment (Design, Manufacturing, Quality, Supply Chain, Regulatory, Safety)
  • Risk Analysis (FMEA, HARA, etc.)
  • Verification & Validation Plan/Results
  • Approval Signatures (Engineering, Manufacturing, Quality, Regulatory, etc.)
  • Implementation Records (Work Orders, Revision Updates, Training Records)
  • Verification Records (Inspection Reports, Test Results)
  • Customer/Regulatory Communication Records (if applicable)
• Define Verification Criteria: Based on:
  • Internal Quality Management System (QMS) procedures (e.g., ISO 9001, AS9100, ISO 13485).
  • Industry-specific regulations (e.g., FDA 21 CFR Part 820, EMDR).
  • Customer requirements.
  • Company engineering standards.
• Assemble Resources: Trained auditors/verifiers, checklists, access to systems (PLM, ERP, QMS).

Record Review & Completeness Check

• Review the DCR/ECN: Ensure it clearly defines:
  • What is being changed (part number, drawing/specification number, revision level).
  • Reason for change (customer request, defect correction, cost reduction, improvement).
  • Detailed description of the change.
  • Proposed effective date.
• Verify Impact Assessment: Confirm it comprehensively addresses:
  • Design Impact: Compatibility, functionality, performance, safety.
  • Manufacturing Impact: Process changes, tooling, capacity, training.
  • Quality Impact: Inspection methods, testing requirements, defect potential.
  • Supply Chain Impact: Sourcing, lead times, supplier changes.
  • Regulatory/Safety Impact: Compliance implications, risk mitigation.
• Check Risk Analysis: Verify it was performed and documented, identifying potential failures and controls.
• Confirm Approval Signatures: Ensure all required/approved signatures are present and legible. Verify signatories have authority (check job titles/roles in procedure).
• Verify Implementation Records: Check evidence the change was physically implemented:
  • Drawing/specification revisions are updated with correct revision levels and dates.
  • Work orders/production orders reflect the change.
  • Tooling/fixtures were modified/replaced.
  • Training records for affected personnel.
• Review Verification & Validation Results: Confirm evidence that:
  • The implemented change meets design requirements.
  • Production processes using the change are validated.
  • Performance/safety testing was completed and passed.
  • Inspection/test reports are complete and acceptable.

Compliance & Process Adherence Verification

• Against Internal Procedures: Check if the change followed the defined workflow:
  • Was the DCR/ECR initiated correctly?
  • Was the assessment period adhered to?
  • Were all required stakeholders consulted and approved?
  • Was verification performed before full implementation?
  • Was configuration management (revision control) followed?
• Against Regulations/Standards: Verify compliance with specific requirements:
  • Traceability to design history files (21 CFR 820.30(j)).
  • Change control procedures documented and followed.
  • Risk management activities (ISO 14971, IEC 62304).
  • Post-market change reporting requirements (if applicable).
• Against Customer Requirements: Ensure any specific customer approval processes or documentation were met.

Traceability & Linkage Check

• Trace Forward: Follow the change from approval to implementation and verification.

  DCR/ECR -> Approved Design -> Updated Drawings/Specs -> Production Implementation -> Verification Reports.

• Trace Backward: Ensure the change is linked to its origin.

  DCR/ECR -> Root Cause (e.g., customer complaint, internal audit finding, test failure).

• Cross-Reference: Verify links between related documents:
  • Impact assessment references the correct DCR/ECR.
  • Risk analysis references the impact assessment.
  • Verification plan references the change description.
  • Test reports reference the verification plan and acceptance criteria.

Effectiveness & Follow-Up Verification

• Review Verification Results: Confirm the change achieved its intended purpose without introducing new problems.
• Check Corrective Actions: If verification identified issues, verify root cause analysis and corrective actions were implemented and verified.
• Monitor Post-Implementation: (Especially for high-risk changes)
  • Review early production/inspection data for unexpected issues.
  • Check customer feedback for related problems.
  • Ensure configuration management remains accurate.

Documentation & Reporting

• Document Findings: Record verification results, including:
  • Records reviewed.
  • Criteria applied.
  • Evidence of compliance/non-compliance.
  • Identified gaps or deficiencies.
  • Recommendations for corrective action.
• Report: Prepare a formal verification report summarizing findings and conclusions.
• Track Corrective Actions: Monitor the resolution of any identified deficiencies.

Key Considerations & Best Practices

• Independence: The verifier should be independent of the change implementation team whenever possible.
• Risk-Based Approach: Focus more rigorously on high-risk changes (safety, critical functions, regulatory impact).
• Version Control: Ensure all referenced documents are the correct, latest versions.
• Digital vs. Paper: If using electronic systems (PLM, QMS), verify system controls (audit trails, electronic signatures, access permissions) are functioning.
• Training: Ensure verifiers understand the procedures, regulations, and products involved.
• Continuous Improvement: Use verification findings to improve the design change process itself.
• Common Pitfalls to Watch For:
  • Missing approvals or signatures.
  • Incomplete impact/risk assessments.
  • Verification performed after full implementation.
  • Lack of traceability between change and origin.
  • Failure to update all affected documentation (e.g., BOMs, work instructions).
  • Inadequate configuration management.

By following this systematic approach, you can confidently verify that design change approval records are accurate, complete, compliant, and provide a reliable history of the product's evolution.