Common Pharmacovigilance Inspection Failures

Introduction

Many pharmacovigilance professionals assume inspection findings arise from isolated mistakes. In reality, inspectors often identify findings because they uncover broader weaknesses within the pharmacovigilance system.

Examples include:

• Weak governance
• Poor oversight
• Inadequate escalation
• Ineffective CAPAs
• Lack of organisational learning

A useful principle is:

Inspectors rarely focus only on what went wrong. They focus on why it was allowed to go wrong.

Understanding recurring inspection failures helps organisations strengthen readiness and reduce regulatory risk.

Failure Themes (summary)

• PSMF maintenance and accuracy
• QPPV oversight and visibility
• Vendor oversight and contract alignment
• Documentation vs. operational reality gaps
• Weak audit programmes and follow-up
• Inadequate CAPA design and effectiveness verification
• Governance and escalation failures
• Risk management weaknesses
• Data integrity and record-keeping problems
• Training and competence gaps
• Reactive inspection readiness rather than continuous readiness
• Absence of organisational learning and improvement

Inspectors assess these themes against regulatory expectations (notably EMA GVP modules I–IV, Annex I/Directive 2001/83/EC, and national equivalents) and against internationally recognised quality system principles (ICH Q9, ICH Q10, PIC/S guidance).

Inspection-Ready Implementation Materials

The remainder of this article converts the high-level guidance above into practical, inspection-ready implementation materials. These materials are intended to be used by pharmacovigilance functions to implement concrete controls, compile demonstrable evidence for inspections, and maintain continuous readiness. They include checklists, sample templates (PSMF index, QPPV oversight report, CAPA effectiveness verification), and a mock-inspection playbook with evidence examples. Regulatory context and inspection relevance are included for each item, plus governance considerations.

Note: These templates are illustrative. Organisations should adapt content to product portfolio, corporate structure, and applicable regulations.

Regulatory context and inspection relevance

Regulatory expectations underpin every checklist and template below:

• EMA GVP Module II (PSMF) specifies content, maintenance and availability for inspectors.
• EMA GVP Module I addresses pharmacovigilance systems, quality systems and QPPV responsibilities.
• EMA GVP Module III outlines expectations for inspections and the role of evidence.
• EMA GVP Module IV describes audit requirements.
• Regulation (EC) No 726/2004 and Directive 2001/83/EC set legal responsibilities, including QPPV accountability.
• ICH Q9 and Q10 provide quality risk management and pharmaceutical quality system frameworks relevant to CAPA and governance.
• PIC/S guidance and national inspectorates provide additional procedural expectations for inspection conduct and evidence presentation.

Inspection relevance: Inspectors will map documentary artefacts (PSMF, SOPs, contracts), records (audit reports, CAPA evidence, training logs), and live demonstrations (system screenshots, process walkthroughs) to assess visibility, accountability, control, oversight and improvement. The materials below are structured to support that mapping.

Checklists

Each checklist is designed to be used during routine self-inspection, internal audit, or in the week prior to an announced inspection. Use evidence mapping (file names, locations, versions, owners) to convert checklist items into hyperlinked evidence bundles.

Note on governance: Assign a named owner for each checklist (e.g., Head of PV Quality, QPPV, Vendor Governance Lead) and ensure items are reviewed at least quarterly by PV governance committees.

1. PSMF Readiness Checklist (inspection-focused)

Regulatory basis: GVP Module II.

• PSMF latest review date documented; next review scheduled.
• Master PSMF index present and current (see sample template below).
• Organisation chart(s) current with titles, reporting lines and location.
• QPPV contact information correct and available in PSMF front page.
• Product list (MA numbers, authorised markets, MAHs) current and reconciled with regulatory affairs.
• PV system description (process flows, systems, databases) accurate and matches operational evidence.
• Sourcing and outsourcing inventory (vendors, subcontractors, essential PV services) complete and cross-referenced to contracts and SDEAs.
• Annexes present and complete: SIAs, SOP index, audit reports summary, safety signals, RMP status, periodic reporting timelines.
• Evidence of PSMF updates following major changes (change log) included.
• Electronic and paper versions located and accessible; access controls documented.
• PSMF owner and version control process defined and recorded.

Inspection relevance: Inspectors typically begin with the PSMF. A coherent, indexed PSMF speeds inspection navigation and reduces follow-up questions.

2. QPPV Oversight Checklist

Regulatory basis: Directive 2001/83/EC; GVP Module I.

• QPPV maintains documented oversight plan covering MAHs and key vendors (with frequency of reviews).
• QPPV receives and reviews KPI dashboard and risk indicators at defined cadence.
• QPPV signs off on key governance meeting minutes and CAPA approvals where required.
• Evidence of QPPV involvement in signal management, aggregate reporting and safety communications.
• QPPV accessibility: documented delegation log for availability during inspections.
• QPPV receives vendor audit summaries and corrective action status reports.
• QPPV review of PSMF updates documented.
• QPPV participates in management review and periodic strategic risk review.
• QPPV has a maintained contact list for immediate queries (Regulatory/Legal/Clinical).

Inspection relevance: Inspectors will ask how the QPPV maintains oversight, and whether evidence aligns with claims of oversight.

3. Vendor Oversight & Contract Checklist

Regulatory basis: GVP Module I; contractual obligations in EU law.

• Comprehensive vendor inventory with risk classification (critical/major/minor) and function.
• SDEA/SHA/SLA availability for each vendor; date of last review.
• Contract clauses: responsibilities for AE/SAE reporting, urgent notifications, audit rights, data access and transfer.
• Audit schedule and most recent audit report for each critical vendor.
• CAPA log for vendor-related findings and evidence of effectiveness verification.
• Vendor performance KPIs (timeliness, completeness, quality metrics) tracked.
• Evidence of subscription to vendor change management notifications and reconciliation with PSMF and SDEAs.

Inspection relevance: Inspectors verify that MAH retains ultimate responsibility; evidence should show active oversight and contract enforceability.

4. CAPA & Effectiveness Verification Checklist

Regulatory basis: ICH Q9, GVP Module IV (audits).

• Root cause analysis documented for each CAPA (5 Whys, fishbone, or other method).
• Action owner, target date and completion date recorded.
• Evidence of implementation for each action (training records, SOP updates, database changes).
• Effectiveness criteria defined at CAPA creation (specific, measurable).
• Evidence collected to demonstrate effectiveness (metrics before/after, sample records, observations).
• CAPA re-audit or verification completed; results documented.
• Repeat findings trend analysis performed and presented to governance.
• Governance approval and closure sign-off documented.

Inspection relevance: Inspectors often focus on repeat findings; robust effectiveness verification prevents recurrence and demonstrates control.

5. Data Integrity Checklist

Regulatory basis: EMA guidance, PIC/S, applicable national guidance.

• Audit trails enabled and retained for critical safety systems (ICS databases, ARGUS, safety databases).
• System validation documentation current and traceable to releases/changes.
• Access control matrices and user privilege reviews up-to-date.
• Back-up and restore procedures tested and results available.
• Data retention policies implemented and evidenced.
• Data migration/change logs available for major system changes.
• Examples of reconciliations between source systems and safety databases with date-stamps.

Inspection relevance: Inspectors expect demonstrable integrity across the data lifecycle for safety information.

6. Training & Competence Checklist

Regulatory basis: GVP Module I, ICH Q10.

• Training matrix aligned to roles and responsibilities (including vendor personnel if applicable).
• Records link training to competence assessments and periodic refresh training.
• Evidence of training on any SOP or process changes.
• Training completion rates and overdue action reports.
• Onboarding records for PV personnel with documented job-specific training.
• Demonstrable training effectiveness assessment (post-training quizzes, observed competence).

Inspection relevance: Training gaps often correlate with SOP non-compliance; evidence should show competence and currency.

7. Inspection Readiness Checklist (Operational)

• Inspection team nominated and trained (documented roles: lead, QPPV supporter, evidence custodian).
• Document retrieval list prioritised and accessible (electronic and physical).
• Evidence bundles prepared (indexed, hyperlinked where possible).
• Mock Q&A prepared for common inspection questions (QPPV, audit, CAPA, vendor).
• Quiet rooms and IT access arranged for inspectors (if on-site).
• Communication plan for staff during inspection (escalation, media/legal).
• Post-inspection action plan template prepared for rapid turnaround.

Inspection relevance: Smooth logistics and well-prepared evidence bundles reduce inspection duration and limit adverse findings.

Sample Templates

Below are sample templates to be adapted and populated. Each template includes inspection relevance notes and governance fields.

1. PSMF Index (sample)

Regulatory basis: GVP Module II.

Use this table as the front-of-file index in the PSMF. Ensure each entry includes evidence locations (server path, document ID) and owner.

Inspection relevance: The index should enable an inspector to quickly locate evidence. Keep the PSMF concise; longer documents should be annexed and cross-referenced.

Governance: PSMF owner (PV QA) should report PSMF status quarterly to the PV Governance Committee with the index attached.

2. QPPV Oversight Report (template)

Regulatory basis: Directive 2001/83/EC; GVP Module I.

Produce a periodic QPPV oversight report (recommended monthly summary with quarterly deep-dive) to map oversight activities to regulatory expectations. This is a primary governance artifact for QPPV visibility.

QPPV Oversight Report – [Period: YYYY-MM]

• Report prepared by: [Name], QPPV (or delegated)
• Date of report: [Date]

• Distribution: PV Governance Committee, CEO (if required), MAH Responsible Persons

• Executive summary

• Snapshot of PV system status (Green/Amber/Red)
• New safety signals, serious concerns, urgent actions

• Statement of QPPV availability and any recent delegations

• Key metrics (period to date)

• ICS: Number of ICSs received / completed / overdue (target 0% overdue)
• Timeliness: % of serious expedited reports submitted within regulatory timelines
• PBRER submissions: On-time / late statuses
• Audit findings: New / open / closed (by severity)
• CAPA status: Open CAPAs, overdue CAPAs, number of CAPAs with verified effectiveness

• Vendor KPIs: Critical vendor SLA compliance %, audit overdue %

• Significant activities and decisions

• Major safety signal assessments, decisions and actions
• Regulatory interactions related to safety matters (notifications, submissions)

• Changes to PV system (new vendors, system migrations, new products)

• QPPV oversight actions performed

• List of meetings attended (audit committee, vendor review, management review)
• Documents personally reviewed/signed by QPPV (audit reports, PSMF update)

• Direct vendor engagements and follow-up actions

• Risk assessment update

• Top PV risks (ranked) and mitigation status

• Emerging risks requiring immediate governance attention

• CAPA governance summary

• Summary of CAPAs initiated in period (root cause, action status)
• CAPA effectiveness verification results (see CAPA template)

• Recommendations for additional oversight or escalation

• Regulatory compliance exceptions and investigations

• Open investigations and status

• Corrective actions and expected completion dates

• Evidence index (attachment list) — hyperlinked

• Attach audit reports, CAPA evidence, sample ICS records, vendor reports, training matrix extracts

• QPPV declaration

• "Based on the information available to me, the pharmacovigilance system is operating within my expectations for [period]." — QPPV signature and date

Inspection relevance: Inspectors will expect to see evidence that the QPPV receives and acts on key documents and that oversight covers all critical aspects. Having a dated, signed QPPV oversight report with linked evidence demonstrates active and documented oversight.

Governance: Oversight reports should be routine agenda items at PV Governance Committee meetings with closed action tracking.

3. CAPA Effectiveness Verification Template

Regulatory basis: GVP Module IV, ICH Q9.

Use this template when closing CAPAs to demonstrate measurable verification.

CAPA ID: CAPA-YYYY-NNN

• CAPA title:
• Originating audit/issue:
• Root cause summary (documented method and findings):
• Action(s) taken (description, owner, start/completion dates):
• Effectiveness criteria (SMART — specific, measurable, achievable, relevant, time-bound):
• Example: "Reduce ICS processing time to 7 days for 95% of cases within 3 months"
• Evidence of implementation (attach or reference):
• Training records (names, dates, content)
• SOP revisions (document IDs, approval dates)
• System configuration change logs (change ticket IDs)
• Communication logs (emails, minutes)
• Data supporting effectiveness (metrics and comparison pre/post):
• Baseline metric (dates and values)
• Post-implementation metric (dates and values)
• Statistical or trend analysis (if applicable)
• Verification method:
• Re-audit (auditor, date, findings)
• Sample record review (sample size, selection method, results)
• KPI trend review (report run dates)
• Verification result:
• Effective / Partially effective / Not effective
• Evidence summary (attach re-audit report or sample findings)
• Closure recommendation:
• Close / Keep open for further actions
• Governance sign-off:
• PV QA (name/date)
• QPPV (name/date)
• Management review (name/date)

Inspection relevance: Provide inspectors with a direct line from problem to root cause, to action, to measurable outcome. Inspectors focus on the quality of root cause analysis and the objectivity and sufficiency of effectiveness verification.

Governance: CAPA closure should require multidisciplinary sign-off (PV QA, QPPV, process owner). Present a CAPA summary table at management review meetings.

Mock-Inspection Playbook (step-by-step)

A playbook converts the organisation's policies into an operational script during an inspection. It reduces ambiguity, ensures consistent responses, and demonstrates preparedness. The playbook below describes typical pre-inspection, during-inspection and post-inspection activities and lists evidence examples an inspector commonly requests. Each element includes the inspection relevance and governance action.

Note: Train staff on the playbook in mock inspections and table-top exercises.

Pre-Inspection (Days to Weeks before)

1. Notification acknowledgement
2. Immediate acknowledgement by regulatory affairs or corporate legal.

3. Assign Inspection Lead (PV Inspection Lead) and Incident Manager.

4. Assemble Inspection Team

5. Roles: Inspection Lead, QPPV point, Evidence Custodian, IT Support, Legal/Regulatory liaison, Subject Matter Experts (SOP owners, vendor lead, audit lead).

6. Document team structure and contact list.

7. Evidence Triage and Bundling (72 hours recommended)

8. Use the PSMF index to locate prioritized evidence.
9. Prepare evidence bundles by inspection area: PSMF, ICS case examples, audit and CAPA, vendor contracts, QPPV oversight, training records, system validation.

10. Create an evidence register: Item ID, description, file path, custodian, version/date, confidentiality notes.

11. Q&A Preparation

12. Prepare a list of anticipated questions and standardised answers.
13. Run a QPPV briefing with examples of recent decisions and evidence references.

14. Prepare "walkthrough scripts" for processes (signal handling, ICS processing).

15. Logistics

16. Book appropriate rooms and equipment (screens, projector, secure Wi-Fi).
17. Arrange for controlled access to systems and offline copies of key reports if needed.

Governance: Inform PV Governance Committee and senior management of inspection dates and potential escalations. Ensure legal is briefed on communications and confidentiality.

During Inspection (Day 0 to Day X)

1. Opening meeting
2. Provide PSMF front page, PSMF index, and QPPV availability statement.

3. Present an inspection agenda and expected document locations.

4. Evidence presentation

5. Use evidence bundles and the PSMF index to direct inspectors; do not overwhelm with unnecessary files.

6. When presenting documents, provide a one-page context summary for each (what the document is, what it proves, key dates).

7. Live Demonstrations

8. System walkthroughs: open a small set of sample ICS entries, show audit trails, demonstrate user access and change history.

9. Vendor oversight: show vendor register, recent KPI reports, audit reports and CAPA status.

10. Interviews

11. QPPV interview: document the questions and answers and record any requests for follow-up evidence.
12. Staff interviews: ensure staff have practiced consistent, factual, short answers; do not speculate.

13. Legal/Regulatory: be prepared to discuss notifications and regulatory interactions.

14. CAPA and Audit evidence

15. Provide CAPA folders with root cause, action evidence, and effectiveness verification documents.

16. Show recent audit reports and follow-up tracking logs.

17. Document control during inspection

18. Record every document provided (copy file name, date, custodian).
19. If inspectors request additional evidence later, document the request, owner, due date, and evidence delivered.

Inspection relevance: Inspectors map documentary claims to live evidence; inconsistencies are common sources of findings.

Post-Inspection (within 48 hours and 30 days)

1. Immediate actions (within 48 hours)
2. Provide any additional evidence requested during the inspection as per the agreed timeframe.

3. Draft an internal debrief report summarising inspection activities, potential observations, and immediate corrective actions.

4. Formal response and governance (within 30 days / regulated timeframes)

5. Prepare formal responses to inspector observations, with clear root cause, interim and long-term CAPAs, timelines, and responsible owners.
6. Ensure QPPV review and sign-off of responses where required.

7. Present response and CAPA plan to PV Governance Committee and secure required resources.

8. CAPA implementation and verification

9. Track CAPA progress using the CAPA template above.
10. Ensure effectiveness verification is scheduled and evidence collected for closure.

11. Revisit PSMF and update where changes were required during inspection.

12. Lessons learned and training

13. Conduct lessons learned workshop with involved staff.
14. Update training materials and run targeted training sessions on inspection findings.

Governance: Ensure PV Governance Committee monitors progress and signs off closure of inspection-related CAPAs. Escalate unresolved or resource-intensive actions to executive management.

Evidence Examples and File Naming Conventions

Inspections are expedited when evidence is organised and clearly named. Use a consistent file naming convention and an evidence registry with document IDs.

Recommended naming convention: [YYYYMMDD][DocumentType][Area][ShortDescription][Version]_[Owner].pdf

Examples: - 20260510_PSMF_FrontPage_PSMF_v3_PVQA.pdf - 20260601_QPPV_Rpt_2026-06_QPPVMonthly_JSmith.pdf - 20260415_Audit_CriticalVendor_AuditRpt_v1_PVQA.pdf - 20260520_CAPA_CAPA-2025-012_ClosureEvidence_v2_PVOPS.pdf

Inspection evidence examples by inspection area:

• PSMF: front page, index, org charts, system descriptions, annexes.
• QPPV: signed oversight report, QPPV CV, delegation log, minutes showing QPPV participation.
• ICS: redacted ICS entries (with demonstrable case narratives, line listings, case processing timestamps), SAE expedited reports (redacted as required).
• Audit & CAPA: audit report with rating, CAPA form with root cause analysis, CAPA evidence, re-audit report.
• Vendor: contract excerpt showing PV responsibilities, SDEA, audit report, KPI trend report.
• Data Integrity: system validation summary (IQ/OQ/PQ), audit trails, user access review logs, back-up test records.
• Training: training matrix, sample personnel training records, competence assessment evidence.
• Governance: management review minutes, risk register excerpts, escalation records.

Inspection relevance: Provide both a representative sample and full logs when requested. Redaction should preserve the integrity of the evidence (i.e., do not redact dates or process-critical fields).

Governance Considerations

Sustained inspection readiness requires governance controls that ensure the materials above are owned, reviewed and escalated appropriately.

Recommended governance arrangements:

• PV Governance Committee (monthly or quarterly) with defined terms of reference, attendees (QPPV, PV QA, Head of PV Ops, Regulatory Affairs, Legal), and clear escalation pathways to executive management.
• PSMF Owner (PV QA) with responsibility for maintenance, periodic reviews and ensuring evidence availability.
• QPPV Oversight Plan documented and reviewed by committee.
• CAPA Review Board to review high-impact CAPAs and verify effectiveness.
• Vendor Governance Forum to review critical vendor performance, audit outcomes and contractual compliance.
• Audit Committee reporting line to ensure independence of PV audit activities.

Inspection relevance: Inspectors evaluate not only documents but the governance arrangements that produce them. A robust, evidence-driven governance structure reduces the likelihood of systemic failures.

Practical Implementation Timelines and Responsibilities

A practical implementation plan to operationalise the above materials:

• Week 0–4: Assign PSMF owner, inspection lead; assemble evidence register and adopt file naming conventions; run gap analysis against PSMF index.
• Month 1–3: Prepare QPPV oversight report template and generate first monthly report; perform vendor inventory and classify vendors; schedule critical vendor audits.
• Month 3–6: Implement CAPA template across PV; conduct CAPA re-verification training; update SOPs for evidence bundling and inspection logistics.
• Month 6–12: Complete system validation review, data integrity controls and re-audit CAPAs; conduct at least one mock inspection using the playbook and checklists.
• Ongoing: Quarterly governance reviews, PSMF updates post-major changes, continuous monitoring of KPIs and CAPA effectiveness.

Responsibility matrix (example): - PSMF owner: PV QA - QPPV oversight report: QPPV - Vendor inventory: Vendor Governance Lead - CAPA governance and verification: PV QA / CAPA Board - Inspection readiness & playbook training: Inspection Lead / HR

Inspection relevance: Demonstrating a schedule with clear responsibilities shows inspectors that weaknesses are being managed proactively.

Practical Examples — Mock Evidence Packages

Below are condensed examples of the type of evidence an inspector may request and how to present them in a package.

1. Example: QPPV oversight on a safety signal
2. Evidence bundle:
   • QPPV oversight report (dated) with signal summary (attached)
   • Signal assessment minutes (date, attendees, decisions)
   • Sample ICS case related to the signal (redacted)
   • Notification to regulatory authority (if applicable)
   • PSMF annex update showing signal assessment recording

3. Presentation note: Lead with the QPPV signed oversight report and highlight where each attached document supports the narrative.

4. Example: CAPA effectiveness for delayed ICS closure

5. Evidence bundle:
   • Original audit report citing timeliness issue
   • CAPA record (root cause, actions, owners)
   • Training records (attendance lists and materials)
   • System configuration change ticket (to implement auto-workflow)
   • KPI trend report showing timeliness improvement pre/post implementation
   • Re-audit report confirming closure

6. Presentation note: Bind the bundle to the CAPA template and show the effectiveness criteria and data.

7. Example: Vendor oversight for outsourced case processing

8. Evidence bundle:
   • Contract excerpts (SLA clauses for timelines and reporting)
   • SDEA or subcontracting agreement
   • Audit report (recent) with open CAPAs
   • Vendor KPI reports (3-6 months)
   • Email trail showing escalation and mitigation actions
   • Evidence of vendor data access for QPPV or MAH (logs)
9. Presentation note: Show the vendor register entry and link items to PSMF vendor annex.

Inspection relevance: Packages that tell a coherent story (issue → action → evidence → verification) reduce the inspector's time to conclude and demonstrate control.

Maintaining the Materials in a Quality System

To ensure long-term utility, the checklists, templates and playbook should be maintained within the PV quality management system (QMS):

• Store master templates in the controlled document management system with version control.
• Define review cycles for each template (e.g., PSMF index quarterly, QPPV oversight monthly).
• Include the playbook as an SOP annex with training and mock inspection frequency defined.
• Ensure that audit programmes expressly verify adherence to these templates and the existence of evidence bundles.

Inspection relevance: A maintained QMS with controlled documents and audited adherence demonstrates organisational control and reduces inspection findings.

Key Takeaways (revised)

• Convert high-level guidance into executable, documented materials: checklists, templates and playbooks.
• The PSMF index, QPPV oversight report and CAPA effectiveness verification are primary inspection artefacts; produce and control them.
• Inspectors seek traceability: show how a statement in the PSMF maps to operational evidence.
• Governance must own and review these materials regularly; the QPPV and PV QA should be visible in governance artefacts.
• A mock-inspection playbook with prepared evidence bundles, staff scripts and a clear evidence registry materially improves inspection outcomes.
• Continuous maintenance (not ad-hoc preparation) of these materials demonstrates learning, control and reduces regulatory risk.

References

1. EMA Good Pharmacovigilance Practices (GVP) Module III – Pharmacovigilance Inspections.
2. EMA Good Pharmacovigilance Practices (GVP) Module I – Pharmacovigilance Systems and Their Quality Systems.
3. EMA Good Pharmacovigilance Practices (GVP) Module II – Pharmacovigilance System Master File.
4. EMA Good Pharmacovigilance Practices (GVP) Module IV – Pharmacovigilance Audits.
5. Regulation (EC) No 726/2004.
6. Directive 2001/83/EC.
7. Commission Implementing Regulation (EU) No 520/2012.
8. ICH Q9 Quality Risk Management.
9. ICH Q10 Pharmaceutical Quality System.
10. PIC/S Guidance on Pharmacovigilance Inspections.