Pharmacovigilance Inspections

Introduction

Pharmacovigilance systems exist to protect patients.

Marketing Authorisation Holders are expected to establish systems capable of:

• Collecting safety information
• Evaluating safety concerns
• Monitoring benefit–risk balance
• Meeting regulatory obligations
• Supporting public health

Regulators cannot directly observe these systems on a daily basis.

Instead, they periodically evaluate them through inspections.

Pharmacovigilance inspections are one of the most important regulatory oversight mechanisms within the pharmaceutical industry. For many organisations, inspections are viewed as high-pressure regulatory events. Mature organisations view inspections differently: as opportunities to demonstrate system effectiveness, governance maturity, compliance culture and patient-safety commitment.

Understanding inspections and implementing inspection-ready systems is essential for every QPPV, pharmacovigilance manager and compliance professional.

What Is a Pharmacovigilance Inspection?

A pharmacovigilance inspection is a regulatory assessment conducted by a competent authority to determine whether a pharmacovigilance system complies with applicable requirements.

Inspectors evaluate whether:

• Regulatory obligations are fulfilled.
• Processes operate effectively.
• Responsibilities are understood.
• Risks are managed appropriately.
• Patient safety remains protected.

Inspections are evidence-based activities. Inspectors seek objective evidence rather than assurances. A useful definition is:

A pharmacovigilance inspection is a regulatory assessment of whether an organisation can demonstrate effective control of its pharmacovigilance system.

Why Regulators Conduct Inspections

The primary purpose of pharmacovigilance regulation is patient protection. Regulators therefore need confidence that organisations:

• Identify safety concerns.
• Escalate safety concerns.
• Communicate safety information.
• Meet reporting obligations.
• Maintain effective oversight.

Inspections provide an independent mechanism for assessing these expectations and for validating that documented processes operate in practice.

The Regulatory Perspective

Although inspections examine documentation, procedures and records, inspectors are generally attempting to answer a broader question:

Can this organisation demonstrate effective control of its pharmacovigilance system?

Inspectors often focus on visibility, accountability, governance, oversight and risk management rather than isolated operational details. Inspectors will also evaluate whether the organisation understands and applies the regional regulatory framework that governs pharmacovigilance (for example, statutory QPPV responsibilities, PSMF maintenance, expedited reporting obligations, and record retention requirements). Regulatory differences may apply by jurisdiction; inspectors will evaluate compliance against the applicable law and guidance for the relevant market(s).

Inspections Versus Audits

Inspections and audits are closely related but fundamentally different.

Pharmacovigilance Audit

• Conducted by or on behalf of the organisation.
• Primary purpose: provide assurance and support improvement.

Pharmacovigilance Inspection

• Conducted by regulatory authorities.
• Primary purpose: assess regulatory compliance.

A useful comparison:

Strong audit programmes improve inspection readiness; however, audits should not exist solely for inspection preparation.

What Inspectors Are Trying To Determine

Inspection programmes vary across authorities. Nevertheless, most inspections seek evidence regarding several core questions.

• Is the pharmacovigilance system effective?
• Are regulatory requirements being met?
• Is oversight effective?
• Are significant risks managed appropriately?
• Is patient safety protected?

These questions shape the inspection process and the documentary evidence inspectors will request.

Types of Pharmacovigilance Inspections

• Routine Inspections: planned inspections as part of ongoing oversight.
• For-Cause Inspections: triggered by specific concerns (e.g., serious compliance issues, safety signals).
• Triggered Inspections: due to events such as acquisitions or major organisational changes.
• Pre-Authorisation Inspections: before marketing decisions.
• Post-Authorisation Inspections: after products enter the market.

Each inspection type implies different scope, depth and expected evidence.

The Inspection Lifecycle

Although inspection approaches vary, most follow a broadly similar lifecycle.

Notification
      ↓
Preparation
      ↓
Inspection (on-site or remote)
      ↓
Observations (findings)
      ↓
CAPAs and RCA
      ↓
Follow-up / Re-inspection

Timely, traceable documentation at each stage is essential.

Notification and Initial Requests

Inspections often begin with formal notification and document requests. Typical initial requests include:

• PSMF and index
• Organisation charts with contact details
• QPPV contact and qualification details
• Core SOPs and their revision histories
• List of products and active safety cases
• Vendor list and contracts for outsourced PV services
• Recent audit reports, CAPA logs and metrics/dashboards
• Training records for PV staff

The quality and completeness of the initial response frequently influence inspection efficiency and scope creep.

Inspection Preparation

Preparation should be continuous. Inspection-ready organisations maintain:

• Current, accurate documentation (PSMF, SOPs, DP lists)
• Clear governance and accountability (QPPV visibility, delegations)
• Rapid evidence retrieval capability
• Up-to-date CAPA management and verification evidence
• Periodic mock-inspections and staff interview practice

A useful principle is: inspection readiness should be a permanent state rather than a temporary project.

Inspection Teams and Scope

Inspection teams may include inspectors with expertise in pharmacovigilance, quality systems, regulatory affairs and data management. Scope may cover:

• Entire pharmacovigilance systems (governance, PSMF)
• Specific operations (ICSR processing, signal management)
• Vendors and outsourced activities
• Product- or portfolio-specific safety management
• Data integrity and information-system controls

Inspection scope determines which documentary evidence and personnel are requested.

What Inspectors Review: Evidence and Demonstration

Inspectors evaluate documentary evidence and supporting operational demonstration. Common documentary categories and examples of inspection-relevant evidence are described in the sections below and in the Evidence Matrix.

Important principle: documentation alone is insufficient — inspectors will cross-check documentation against records, system audit trails and interviews.

Inspection Findings and Classifications

Findings identify deficiencies, weaknesses or compliance concerns and are typically classified (terminology varies):

• Critical Findings: significant risk to patient safety or public health.
• Major Findings: important weaknesses requiring remediation.
• Minor Findings: lower-risk deficiencies.

Regulatory response, escalation, and CAPA expectations depend on classification.

CAPAs, Root Cause Analysis and Regulatory Expectations

Following inspection completion, organisations must address findings through CAPAs. Authorities expect CAPAs to be:

• Timely and risk-based.
• Supported by robust root cause analysis (RCA).
• Sustainable and verifiable with measurable outcomes.
• Appropriately resourced and subject to management oversight.

Regulators commonly focus on the quality and effectiveness of remediation rather than mere closure.

Inspection-Readiness Checklists and Practical Implementation

This section provides practical, inspection-focused checklists that transform high-level guidance into concrete, inspectable evidence. Use these checklists as a minimum baseline and adapt to organisational size, complexity and regulatory jurisdictions.

Continuous (Operational) Readiness — Daily / Weekly Activities

• Ensure the PSMF index and PSMF contact details are current (monthly review).
• Verify the PV master contact list (QPPV, deputies, safety database contacts) is accurate.
• Monitor and close high-priority CAPAs to target dates; escalate delays.
• Review open audit findings and track verification evidence.
• Confirm ICSR processing queue is within SLA and reconciled to EV submissions.
• Ensure training completion rates for PV staff meet defined thresholds; evidence stored.
• Validate vendor KPI reports have been received and logged; follow up on breaches.
• Ensure safety signal evaluations and risk-minimisation activities have up-to-date minutes and action trackers.

Practical evidence: daily/weekly dashboards, validated extracts from safety database audit trails, CAPA status reports with documented verification evidence.

Tactical Readiness — 90 / 60 / 30 / 7 Days Pre-Notification

90 days - Complete a rapid PSMF health check: index, section ownerships, version control. - Verify QPPV CV and delegation letters, plus contactability procedures. - Run a fresh reconciliation of ICSR processing volumes vs. EV receipts for each product. - Ensure most recent audit reports and CAPA verifications are compiled and accessible.

60 days - Conduct a focused mock inspection covering product(s) likely to be targeted. - Collect the latest vendor contracts, SDEAs and most recent vendor audit reports. - Confirm training records for staff who will be interviewed and prepare training briefs.

30 days - Assemble the inspection evidence pack (see Evidence Pack checklist) and create an index. - Validate that SOPs cited in the PSMF are current and that revision pages are captured. - Perform a final reconciliation of outstanding CAPAs and closure evidence.

7 days - Conduct interview rehearsals with the QPPV and key contacts. - Ensure document retrieval processes are tested (share sample requests and verify retrieval within agreed times). - Prepare a daily inspection coordination plan and designate a single point of contact for the inspector team.

Pre-Inspection Evidence Pack (Suggested Minimum)

Create a logical, paginated evidence pack (electronic and searchable). Include: - PSMF with cover sheet and index (including version and sign-off dates) - Org chart and responsibilities matrix (QPPV, deputies, PV headcount) - QPPV CV and delegation of authority - Core PV SOPs with revision history - Safety database validation summary and audit trail extracts - ICSR processing SOP, SOP-controlled work instructions, and representative ICSR files (redacted) - Recent audits and management meeting minutes (safety governance) - CAPA register with evidence of verification/closure - Vendor master list, contracts, SDEAs, KPI reports and recent vendor audit reports - Signal management minutes and current risk-management activities - Periodic-safety-update reports (PSUR/PBRER) and submission receipts - Training matrix and certificate evidence - Metrics dashboards and escalation records - Any external communications with regulators relevant to the inspection scope

Packaging: include a short executive summary for inspectors summarising the system, major risk mitigations and recent improvements.

Evidence Matrix: What to Provide and Why

Inspectors request documentation to demonstrate capabilities. The matrix below links typical inspection questions to specific documentary evidence and concrete examples of what inspectors expect to see.

• Question: Is the PSMF accurate and maintained?
• Evidence: Current PSMF with signature page; PSMF version-control log; evidence of PSMF updates following organisational changes (email sign-offs, minutes).

• Example: PSMF v3.2 signed by Head of PV and QPPV on 2026-03-01; change log showing updates to section II (vendor oversight) on 2026-04-15 with email approval.

• Question: Who is responsible for oversight?

• Evidence: Organisational chart, roles and responsibilities matrix, QPPV CV, delegation of tasks.

• Example: Org chart PDF with hierarchical reporting, a responsibility matrix (RACI) showing QPPV as accountable for aggregate reporting.

• Question: Are ICSRs processed and reported on time?

• Evidence: ICSR flowchart, SOPs, representative ICSR files (redacted), database audit trail extracts, EV gateway receipts.

• Example: Representative ICSR for Product X showing date received, triage, case processing times, submission receipt from EV dated within regulatory timeframe.

• Question: Is vendor oversight effective?

• Evidence: Contracts, SDEAs, vendor audit reports, KPI trend reports, issue tracking and escalation emails.

• Example: Contract with Vendor A includes specific KPIs; KPI report shows a 98% on-time processing rate; minutes of a vendor governance meeting showing escalation of a missed EV submission.

• Question: Are CAPAs substantive and effective?

• Evidence: CAPA register entries with root-cause analysis, action plans, implementation evidence and verification metrics.

• Example: CAPA ID 2025-045 addressing delayed EV submissions describing root cause, corrective actions and follow-up monitoring showing sustained improvement.

• Question: Is signal management robust?

• Evidence: Signal assessment SOP, signal review minutes, data sources used, analysis outputs, decision records for risk-minimisation measures.

• Example: Signal review minutes showing cross-functional membership, data considered (EV dataset), and decision to update safety communications with documented timelines.

• Question: Is the PV quality system effective?

• Evidence: Audit schedule, results, management review minutes, quality KPIs and trend analyses.
• Example: Management quality review minutes showing PV KPIs, recent audits, and decisions on resource allocation for remediation.

Concrete documentary examples to prepare: database validation summary, audit-trail extracts for specific records (with redaction where required), scanned signed SOPs with revision history, printed dashboards with date/time stamps and filter criteria saved, signed meeting minutes, and electronic mail chains demonstrating escalation and decision-making.

Sample CAPA and Root Cause Analysis (RCA) Templates

Below are practical, inspector-focused templates. Use these templates in quality systems, ensure they are controlled documents and include versioning and sign-off. Inspectors expect CAPAs to demonstrate clear linkages between the finding, root cause, corrective/preventive actions and verification evidence.

Sample CAPA Template

Implementation notes: - Always attach supporting documents: signed SOW, mail trail, screenshots of system logs. - Record the date and person implementing each action. - Verification should be time-bound and measured (e.g., 3 months of KPIs).

Sample RCA Template

1. Problem statement
2. Concise description of the non-compliance observed (who, what, when, where).
3. Data and evidence collected
4. List of records reviewed (ICSRs, logs, SOPs, emails, audit trails), including document IDs and dates.
5. Contributing factors
6. Organisational, process, system and people factors (bullet list).
7. Analysis (tools)
8. Use of techniques such as 5 Whys, fishbone diagram, fault tree; include outputs.
9. Root cause(s)
10. Clear statement(s) of the root cause(s) with evidence.
11. Corrective and preventive actions
12. Linked to cause(s), with owners and target dates.
13. Verification plan
14. Specific metrics, data sources, and timeframes to demonstrate effectiveness.
15. Management approval
16. Sign-off by PV Head or nominated governance representative with date.

Sample (condensed): - Problem: 6 ICSRs for Product B had delayed EV submission (more than 7 days) between Jan–Mar 2026. - Data: Electronic case processing logs, vendor emails, SOP 12 (case processing) revision history. - Contributing factors: SOP not aligned to current vendor process; handover steps unclear; IT alerts not configured. - Root cause: SOW and SOP mismatch caused the vendor to assume MAH responsibility for final submission; no reconciliations in place. - Actions: Amend SOW and SOP; implement reconciliation; configure IT alerts; training for vendor; monitor KPIs for 3 months. - Verification: KPI extracts monthly showing <1% delay; reviewed by QPPV and QA; closure approved on evidence.

Inspectors expect RCA outputs to be logical, evidence-based and traceable from finding to verification.

Concrete Examples of Documentary Evidence (Inspection-Ready Samples)

Inspectors frequently request representative documents. Below are concrete examples and how they should be prepared for inspection — including redaction, indexing and cross-referencing.

1. PSMF
2. Evidence: PDF with cover page, organisational chart embedded, index hyperlinked to sections, signature page signed by QPPV and Head of PV with dates.

3. Inspection relevance: Shows ownership, system description and current status.

4. QPPV Documentation

5. Evidence: QPPV CV, professional registration, delegation letter, contactability plan (24/7 if applicable), record of QPPV involvement in governance meetings.

6. Inspection relevance: Demonstrates accountability and access to current safety information.

7. SOPs and Work Instructions

8. Evidence: Controlled SOPs with revision history, revision change control forms, training registers showing attendees and dates.

9. Inspection relevance: Demonstrates documented processes and staff competence.

10. Representative ICSR Files

11. Evidence: Full case file (redacted to protect personal data) including source, medical narrative, causality decision, expedited reporting determination, EV submission receipt and internal QC record.

12. Inspection relevance: Demonstrates end-to-end ICSR handling and reporting compliance.

13. Database Audit Trails

14. Evidence: Audit trail extracts showing creation, edits, user IDs, timestamps and reason codes for changes.

15. Inspection relevance: Demonstrates data integrity and traceability.

16. EudraVigilance / Global Gateway Receipts

17. Evidence: Submission receipts with unique identifiers and timestamps; reconciliation logs showing receipt vs. processing status.

18. Inspection relevance: Demonstrates timely reporting and system performance.

19. Vendor Contracts and SDEAs

20. Evidence: Contract clauses delineating responsibilities, SDEA with specific data exchange frequency and format, escalation paths and audit rights.

21. Inspection relevance: Demonstrates clarity of roles in outsourced processes.

22. Vendor Oversight Records

23. Evidence: KPI trend reports, vendor audit reports, governance meeting minutes, evidence of corrective actions and verification.

24. Inspection relevance: Demonstrates control over outsourced activities.

25. Audit Reports and CAPA Files

26. Evidence: Audit report PDF, executive summary, non-conformances, RCA(s), CAPA plans, evidence of implementation and verification.

27. Inspection relevance: Demonstrates independent assurance and remediation effectiveness.

28. Signal Management and Safety Communication Records

    • Evidence: Signal detection reports, signal review committee minutes, decision records for RMMs, dissemination records for safety communications.
    • Inspection relevance: Demonstrates proactive safety surveillance and management.

29. Training Records

    • Evidence: Training matrix, attendance logs, competency assessments for staff whose duties are PV-critical.
    • Inspection relevance: Demonstrates staff qualification and preparedness.

30. Management Oversight

    • Evidence: PV governance committee minutes, PV performance dashboards, risk registers, management review action items.
    • Inspection relevance: Demonstrates senior management visibility and escalation.

Presentation tips for inspectors: - Provide documented indexes and hyperlinks for electronic packs. - Redact personal data but preserve medical and regulatory-relevant content. - Include a short cover note for each document explaining why the document is relevant and how it maps to the PSMF or inspection question. - Provide chain-of-custody or version-control evidence when relevant (change control forms, signatures, timestamps).

Governance, Accountability and Practical Controls

Governance is central to inspection success. Inspectors expect clear, implemented governance structures with documented responsibilities, appropriate segregation of duties (SoD), and effective escalation.

QPPV and Senior Oversight

• The QPPV is expected to have authority to access all pharmacovigilance data and to advise senior management on PV matters.
• Maintain QPPV accessibility evidence (delegation letters, contactability procedures).
• Document QPPV participation in periodic safety reporting and major decisions.

Roles and Responsibilities (Practical Implementation)

• Maintain a RACI matrix linking PV activities (ICSR intake, PSUR submission, signal management, safety communication) to named roles and deputies.
• Ensure delegations are documented with scope and competency requirements.
• Implement annual role reviews and update the PSMF accordingly.

Management Review and Escalation

• Schedule periodic PV governance meetings with defined agendas capturing KPIs, open CAPAs, signals and audit findings.
• Produce concise management review minutes with actions and owners documented.
• Implement an escalation matrix for safety concerns that specifies criteria for escalation (e.g., number of serious ICSRs, signal thresholds, product-specific triggers).

Vendor Governance

• Maintain centralised vendor master data with SDEAs, contracts and oversight history.
• Implement periodic vendor performance reviews (monthly/quarterly) and record minutes.
• Ensure adequate audit rights and schedule vendor audits as part of the PV audit programme.

Segregation of Duties and Data Controls

• Map critical PV processes and apply SoD where necessary to prevent conflicts (e.g., case entry vs. case quality control).
• Implement role-based access controls in safety databases and maintain user access review logs.
• Preserve audit trails and perform periodic data integrity checks.

Records Retention and Archiving

• Implement retention policies aligned with regulatory requirements and company policy; evidence retention periods in the PSMF.
• Ensure electronic and paper archives are searchable and that transfer procedures to long-term archives are documented and tested.

Inspection relevance: inspectors will probe whether governance described in the PSMF is actually implemented — expect requests for meeting minutes, delegation letters, KPI trends and audit trails.

Vendor Oversight: Practical Checklist

• Up-to-date list of PV vendors, including contact persons and delegated activities.
• Signed contracts and SDEAs for each vendor.
• Evidence of supplier qualification and due diligence (assessment reports).
• Vendor KPI definitions and recent KPI trend reports.
• Recent vendor audit reports and CAPA follow-up status.
• Records of governance meetings and escalations.
• Evidence of training or onboarding for vendor staff where relevant.
• Evidence of control of subcontracting if vendor subcontracts activities.

Example evidence presentation: a single PDF per vendor containing contract, SDEA, most recent audit, KPI dashboard and minutes from the last two governance meetings.

Practical Implementation: Tools, Metrics and Mock Inspections

Tools and Systems

• Safety Database: validated, with accessible audit trails and exportable reports.
• Document Management System (DMS): controlled versions for SOPs, PSMF and training records; ability to provide version history and signatures.
• Incident/CAPA Tracking Tool: searchable CAPA register with attachments and closure evidence.
• Dashboarding Tools: up-to-date metrics for KPIs, accessible screenshots with filter settings saved as evidence.

Practical tips: - Regularly test data exports and system reporting to ensure inspectors can be shown the data as presented. - Implement a designated inspection electronic folder with required documents indexed and accessible to the inspection team.

KPIs and Metrics (Inspection-Relevant)

Examples of KPIs inspectors find useful: - ICSR processing timeliness (% within SLA). - EV submission timeliness and reconciliation success rate. - Number of open CAPAs and % overdue. - Vendor KPI adherence (%). - Training completion rates for PV-critical staff. - Audit closure rate and average time to close findings.

Ensure dashboards include source data and filters, and exportable reports with time stamps.

Mock Inspections and Interview Preparation

• Conduct mock inspections at least annually or after major organisational change.
• Use inspector-style questioning for interviews (QPPV, deputies, PV head, vendor leads, QA).
• Prepare scenario-based walkthroughs: representative ICSR walk-throughs, signal detection case, CAPA management example.
• Record mock interview outcomes and remedial training actions; treat mock inspections as audit activities feeding CAPAs.

Inspection relevance: inspectors often ask for examples during interviews. Being able to walk an inspector through representative cases and the supporting documents demonstrates operational control.

Inspection Conduct and Interview Best Practice

• Nominate a single inspection coordinator and communicate a clear inspection plan.
• During interviews, ensure the interviewees understand their role, have access to key documents and answer consistently with documentation.
• Avoid speculation; if a question requires checking, state that the answer will be confirmed and provide written follow-up.
• Demonstrate traceability: when referring to a document (e.g., SOP), show the relevant section and its revision date.

Documentation for interviews: - Annotated SOPs or quick reference job aids for interviewees. - A one-page QPPV briefing summarising recent PV activities, open risks and CAPAs. - Access to representative case files and dashboards on request.

Inspection Follow-up: CAPA Execution and Verification Evidence

After receiving inspection findings, follow an organised, documented path:

1. Acknowledge findings and propose an initial timetable for CAPA submission as soon as practicable.
2. Conduct RCA and produce CAPAs using the templates above.
3. Implement corrective/preventive actions with documented evidence (documents changed, training logs, system configurations).
4. Verify effectiveness with objective metrics and maintain evidence demonstrating the metric definition, data source and trend.
5. Maintain a CAPA closure folder that includes the finding, RCA, action evidence, verification evidence and management sign-off.

Concrete examples of verification evidence: - Updated SOP with redline and approval signature. - Training attendance sheet with assessment results. - Database audit trail showing configuration change. - KPI trend charts exported from the dashboard showing improvement. - Minutes of governance meeting confirming closure and acceptance.

Inspection relevance: regulators will review CAPAs for adequacy and may request follow-up evidence or re-inspection if CAPAs are insufficient.

Regulatory Context and Inspection Relevance

Regulatory frameworks require that marketing authorisation holders implement effective pharmacovigilance systems and maintain evidence of compliance. Key expectations include:

• A nominated competent person for pharmacovigilance (QPPV) with documented responsibilities.
• Maintenance of a Pharmacovigilance System Master File (PSMF) describing system elements, responsibilities and oversight.
• Systems and processes for detecting, assessing, reporting and preventing adverse reactions in line with applicable regional requirements.
• Evidence of vendor control when activities are delegated, including SDEAs and auditability.

Regulators such as the EMA, MHRA, FDA and other competent authorities structure inspections according to their legal frameworks and guidance (e.g., EMA GVP Modules, PIC/S guidance). Although specifics vary by jurisdiction, the inspection fundamentals are consistent: inspectors will seek evidence that systems are designed, operated and controlled to ensure patient safety and regulatory compliance.

Note: Reporting timelines and specific legal obligations vary by jurisdiction. Ensure your inspection-ready documentation references the correct regional requirements and that personnel understand which laws apply to the products and markets under inspection.

Inspection Scenarios: Examples and Evidence Walkthroughs

Example 1 — For-cause inspection triggered by suspected delayed reporting: - Inspector requests representative ICSRs, EV submissions, reconciliation logs and CAPAs for recent delays. - Inspection evidence: representative redacted case files, EV receipt screenshots, reconciliation logs showing exception handling, vendor meeting minutes and CAPA with RCA and verification data.

Example 2 — Routine post-authorisation inspection focused on vendor oversight: - Inspector requests contracts, SDEAs, recent vendor audit reports, KPI trends and governance meeting minutes. - Inspection evidence: signed contract pages, SDEA specifying roles, vendor audit report with non-conformances and CAPA, KPI dashboards, governance meeting minutes showing escalation.

Example 3 — Pre-authorisation PV inspection: - Inspector may focus on PSMF, PV system description for upcoming product, SOPs for expedited reporting, QPPV availability. - Inspection evidence: PSMF, QPPV CV and delegation letter, SOPs, training records for clinical safety staff.

In all scenarios, inspectors will cross-reference documents with system audit trails and interviews; prepare to demonstrate the chain of evidence.

Appendices

Appendix A — Mock Inspection Agenda (Sample)

• Day 0: Document submission and evidence pack index
• Day 1: Opening meeting; QPPV overview; PSMF walk-through; Organisation and governance
• Day 2: ICSR processing (triage, coding, quality control) and database review
• Day 3: Signal management; periodic safety reporting; risk-minimisation activities
• Day 4: Vendor oversight; audit programme; CAPA and RCA review
• Day 5: Closing meeting; preliminary observations and next steps

Appendix B — Example Document Request Template (Inspector-style)

1. Current PSMF and index
2. Organisational chart and PV responsibilities matrix
3. QPPV CV and delegation letter
4. SOPs: case processing, signal management, PSUR/PAER submission, vendor oversight
5. Representative ICSRs and EV receipts (redacted) — 5 normal, 5 expedited
6. Recent audit reports and CAPA files (last 24 months)
7. Vendor contracts and SDEAs for PV activities
8. Metrics dashboard exports for last 12 months
9. Management review and governance meeting minutes (last 2 years)
10. Training records for PV personnel (last 3 years)

Appendix C — Quick Reference: Evidence Packaging Checklist

• Index (hyperlinked for electronic packs)
• Cover letter summarising the pack contents and owner contact
• PSMF and core SOPs up-front
• Representative operational files (ICSRs, audit trails)
• CAPA register and supporting evidence
• Vendor file (contract + audit + KPIs)
• Governance minutes and management review
• Exported KPI and system report evidence (with date/time stamps)

Key Takeaways (Practical)

• Inspection readiness is continuous; operational routines and evidence management are critical.
• Prepare inspection packs that are indexed and hyperlinked; provide clear traceability between findings and evidence.
• CAPAs must demonstrate root-cause understanding, measurable verification and sustainable preventive measures.
• Governance, QPPV visibility and vendor oversight are inspection focal points.
• Invest in system controls, data integrity and demonstrable metrics to support inspection assertions.
• Mock inspections, rehearsals and scenario walk-throughs materially improve inspection performance.

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.