Inspection Hosting for QPPVs

Introduction

For many Qualified Persons Responsible for Pharmacovigilance (QPPVs), hosting a pharmacovigilance inspection is one of the most important and high‑visibility responsibilities. Inspectors typically review years of activity in a short time window and use interviews and documentary evidence to assess whether the pharmacovigilance system is functioning effectively and whether the QPPV exercises appropriate oversight.

Inspectors commonly view the QPPV as:

• A source of system knowledge
• A guardian of governance
• A signatory to system-level responsibility

A guiding principle:

Inspectors are assessing whether the QPPV maintains demonstrable, effective oversight; they are not expecting operational ownership of every detail.

This article synthesises preparatory activities, hosting practices and inspection‑ready artifacts — including inspection checklists and actionable document templates — to support QPPVs to reach and demonstrate inspection readiness.

Regulatory context and inspection relevance

Key regulatory expectations that inform inspection hosting and artifacts include:

• EMA GVP Module II (Pharmacovigilance System Master File): requires an up‑to‑date PSMF that documents the system and its supporting processes, roles and responsibilities.
• EMA GVP Module I and Module III: describe quality systems and inspection frameworks.
• GxP principles (ICH Q9, ICH Q10): require risk‑based controls, documented governance and records demonstrating implementation and effectiveness.
• National and regional pharmacovigilance legislation (e.g., Regulation (EC) No 726/2004, Directive 2001/83/EC, Implementing Regulation (EU) No 520/2012): underpin inspection scope and obligations.

Inspectors expect traceability, contemporaneous records, auditable evidence of decisions and remediation, and accessible documentation indexed and cross‑referenced. The templates and checklists below are designed to produce artefacts that meet these expectations and can be directly presented to inspectors.

Core hosting responsibilities of the QPPV

The QPPV’s inspection responsibilities fall into three domains:

• Strategic oversight: explain system structure, risk profile, governance and major decisions.
• Governance and assurance: demonstrate maintenance of the PSMF, audit programme, CAPA effectiveness and vendor oversight.
• Inspection management: designate roles, ensure accurate and timely document handling, and coordinate interviews.

Assigning clear operational roles (inspection lead, document coordinator, scribe, subject matter experts) reduces risk of inconsistent responses or documentation lapses.

Inspection‑Ready Checklists

The following checklists are inspection‑ready: designed for practical use and to be incorporated into the inspection plan and evidence repository.

Pre-notification / Continuous readiness checklist (always maintained)

• PSMF: current, versioned, signed and indexed.
• PSMF index: identifies physical/digital locations and custodians (see PSMF index template).
• Core SOPs: current versions, approved and accessible.
• Organisation chart: shows QPPV, deputies, heads of safety, vendors.
• Critical vendor list: contracts, vendor descriptions, oversight evidence.
• Audit log: completed audits, scheduled audits, remedial actions.
• CAPA register: open and closed CAPAs with evidence of effectiveness.
• Training records: QPPV and PV team training, delegation logs.
• Document control: DMS access, version history, change control.
• Mock inspection outputs: findings and remedial status.
• Document request templates: standard responses pre‑prepared (see Document Request Tracker).
• Interview question bank: updated and practised (see Interview Question Bank).
• Secure file sharing process: validated for remote inspections, redaction controls in place.

Day‑0 to Day‑2 (immediate tasks after notification)

• Confirm inspection scope and dates; obtain list of initial document requests.
• Establish inspection governance: inspection lead, document coordinator, scribe, QPPV role.
• Open document request tracker and log all incoming requests.
• Confirm secure room(s) or virtual meeting links and IT access.
• Confirm time slots for QPPV and SME interviews; circulate interview preparation pack.
• Prepare ‘inspection pack’ summary for inspectors: PSMF snapshot, critical vendors, recent audits, open CAPAs.
• Schedule daily debriefs and evidence review sessions.

Document handling and submission checklist

• Use Document Request Tracker to log and version all submissions.
• Quality‑check every document before submission (header/footer, version, signatory).
• Maintain an auditable trail of who prepared, reviewed and submitted each document.
• Note any redactions and the reason; document redaction approval.
• For remote inspections, apply watermarking and file naming conventions that preserve version history.
• After submission, capture inspector receipt confirmation and time‑stamp.

Interview and communication checklist

• Provide the QPPV with concise briefing notes and document cross‑references.
• Prepare SME contact list and escalation pathways.
• Maintain a scribe to capture questions and responses (including commitments).
• Do not guess: agree a process to follow up where the answer must be verified.
• Capture any new document requests from interviews in the tracker immediately.

Close‑out checklist

• Capture exit meeting statements and immediate findings.
• Collate all inspector requests, confirm timeframe for responses if provided.
• Open CAPAs linked to inspection findings and populate CAPA evidence template.
• Update PSMF and artefacts as required and execute change control.
• Prepare regulatory reply package if formal findings are issued.

Templated artefacts (inspection‑ready) — practical templates with examples

The templates below are intentionally concise, with example rows that illustrate the expected content and governance details. Each template should be hosted in the controlled Document Management System (DMS), assigned a document owner, and version controlled.

1. Document Request Tracker (template and example)

Purpose: central log for incoming document requests, status and evidence of submission. Inspectors expect to see traceability from request to submitted file.

Template (CSV/Excel style):

Request ID | Date Requested | Requested By (Inspector) | Document Title | Doc ID | Version | Custodian | Priority | Planned Submission Date | Actual Submission Date | Submission Medium | Submitted By | Submitted To (inspector) | File Name (in DMS) | Status | Comments

Example entries:

REQ-2026-001 | 2026-06-08 | Inspector A (EMA) | PSMF Summary | PSMF-SUM | v3.0 | PV Quality Lead | High | 2026-06-09 10:00 | 2026-06-09 09:45 | Secure SharePoint link | Emma Brown | Inspector A | PSMF_SUM_v3.0_20260609.pdf | Submitted | Signed by QPPV on 2026-06-08
REQ-2026-002 | 2026-06-08 | Inspector B | Vendor audit report - Vendor X | AUD-XYZ-2024 | v1.2 | Vendor Oversight Mgr | Medium | 2026-06-10 | 2026-06-10 14:30 | Encrypted email | John Smith | Inspector B | AUD_XYZ_2024_v1.2.pdf | Submitted | Redacted commercial pricing per Legal

Practical implementation notes: - Use unique Request IDs with a date or sequential number for traceability. - Link each entry to the authoritative file in the DMS, not local copies. - Record reasons for redaction and retain unredacted master in a secure location. - Capture confirmation of receipt from inspectors (email or system trace).

Inspection relevance: - Inspectors will review the tracker to verify timeliness and completeness; inconsistencies between tracker and submitted files raise concerns.

Governance: - The Document Coordinator owns the tracker. Changes to statuses require evidence (timestamped submission, reviewer sign-off).

2. PSMF Index (template and example)

Purpose: a structured, signed index that maps PSMF sections to underlying documents and custodians, consistent with GVP Module II requirements.

Template (table):

PSMF Section | Section Title | Primary Document(s) | Doc ID(s) | Version | Custodian | Location (DMS path / physical) | Last Updated | Cross‑references / Evidence

Example entries:

1 | PV System Overview | PSMF v3.0 (full) | PSMF-FULL | v3.0 | QPPV | /DMS/PSMF/PSMF_v3.0.pdf | 2026-05-30 | Org chart (ORG-2026-01_v1.1), Risk register (RISK-PV-v2.3)
3 | Organisation and Staffing | Org chart, Roles & Responsibilities matrix | ORG-2026-01, R&R-2025 | v1.1, v2.0 | HR / PV Ops | /DMS/ORG/ORG-2026-01.pdf | 2026-05-20 | Delegation log (DELEG-2025)
5 | PV Processes | SOPs: Adverse Event Reporting, Signal Management | SOP-PV-001, SOP-PV-005 | v4.2, v3.0 | PV Quality | /DMS/SOPs/SOP-PV-001_v4.2.pdf | 2026-04-12 | Training records (TRN-PV-2026)

Practical implementation notes: - Keep the PSMF index concise and current; ensure cross‑references are hyperlinked to DMS. - Include custodians and contact details to enable quick retrieval during inspection. - Make the PSMF index the inspector’s navigation map — show where evidence lives.

Inspection relevance: - Inspectors use the index to verify that documents exist and to request supporting evidence; an outdated index undermines credibility.

Governance: - The QPPV signs off the PSMF and PSMF index at approved intervals (e.g., annually or with major changes). Changes should be logged through formal change control and versioned.

3. Interview Question Bank (template and examples)

Purpose: standardised bank of likely inspection questions mapped to expected evidence and owner; used for mock interviews and briefing.

Template columns:

Topic | Question | Rationale | Suggested key points to cover | Primary evidence | SME / Owner | Practice status

Example entries:

Pharmacovigilance System | "Describe the structure of your PV system and how responsibility is delegated." | Verify system understanding and oversight | Outline central PV organisation, deputy arrangements, vendor responsibilities, escalation routes | PSMF section 1, Org chart, Delegation log | QPPV / PV Ops Lead | Practised 2026-06-05
Vendor Oversight | "How do you determine which vendors are critical and how are they managed?" | Assess control of outsourced activities | Describe criticality assessment, contractual obligations, KPI monitoring, audit frequency | Vendor list, contracts, KPI reports, audit reports | Vendor Oversight Mgr | Practised 2026-06-04
CAPA Management | "Show an example of a CAPA that closed and how you assessed effectiveness." | Expect evidence of root cause and verification | Describe finding, root cause analysis, actions taken, evidence of implementation, metrics for effectiveness | CAPA record, training records, process change memo | Quality Head | Not yet practised
PSMF Maintenance | "How is the PSMF maintained and who is responsible for version control?" | Check governance of critical document | State periodic review intervals, triggers for updates, QPPV sign‑off, and DMS procedures | PSMF index, change control log | QPPV / PV Quality | Practised 2026-06-06

Practical implementation notes: - Use the bank for structured mock interviews: schedule QPPV and SME practice sessions with a scribe/observer to capture gaps. - Map each question to a specific document and file path to reduce retrieval time during inspection. - Update the bank after every inspection and mock exercise.

Inspection relevance: - Inspectors will test consistency between oral answers and documentary evidence; the bank helps ensure consistent messaging.

Governance: - The QPPV should review and approve the interview bank annually; training and practice records should be retained.

Sample QPPV answer format (for practice, brief and evidence‑oriented): - One-sentence summary (system definition) - Key control points (delegation, escalation, monitoring) - Reference to evidence (PSMF section and file path) - If needed, offer to provide a specific document and the expected timing

Example: - Question: "How do you review the PV system for ongoing suitability?" - Model response: "We maintain a risk‑based PV quality plan with quarterly metrics reviews and an annual system review documented in the PSMF (PSMF v3.0, sec 7). The QPPV chairs quarterly governance meetings where KPIs and audit findings are discussed; minutes and KPI reports are in /DMS/PV/Reports. I will provide the latest KPI pack (KPI-PV-Q2-2026.pdf) now."

4. CAPA Evidence Template (template and example)

Purpose: provide inspectors with clear, auditable evidence that CAPAs were implemented and their effectiveness assessed.

Template (structured CAPA record with evidence fields):

CAPA ID | Finding Reference | Date Opened | Root Cause Summary | CAPA Title | Corrective Action(s) | Responsible Owner | Planned Completion Date | Actual Completion Date | Evidence of Implementation (file names / locations) | Evidence of Effectiveness (metrics, monitoring period, files) | Quality Review / Closure Date | Reviewer

Example entry:

CAPA-2025-015 | Audit-Find-2025-07 | 2025-09-10 | Incomplete vendor oversight procedures for Vendor X | Strengthen Vendor Oversight Process | 1) Update SOP-PV-Vendor-001; 2) Implement quarterly KPI reporting; 3) Additional audit of Vendor X | Vendor Oversight Mgr | 2026-02-28 | 2026-02-21 | SOP-PV-Vendor-001_v2.0_20260221.pdf; KPI_VendorX_Q1-2026.xlsx; AuditReport_VendorX_2026-02.pdf | KPI trend shows 95% timeliness vs baseline 78% over 3 months (KPIs and monitoring report in /DMS/CAPA/CAPA-2025-015_EFF.pdf) | 2026-05-01 | Head of Quality

Practical implementation notes: - Evidence types: revised SOPs, training records, communications, system reports (timestamped), audit reports, meeting minutes, signed declarations. - File naming: include CAPA ID and descriptive title for quick reference (e.g., CAPA-2025-015_SOP_Update.pdf). - Include links to metrics and monitoring dashboards; provide exported snapshots with dates.

Inspection relevance: - Inspectors will expect to see not only that actions were completed but that their effectiveness was assessed over a sufficient period with measurable outcomes.

Governance: - CAPA closure requires documented verification and quality review; QPPV must be able to reference review dates and reviewers.

Practical implementation: systems, version control and evidence management

• Centralised repository: store all inspection artifacts in a controlled DMS with role‑based access and audit trail. Ensure the PSMF index points to DMS locations.
• Version control and signatures: every PSMF or SOP change must be versioned, with approvals and effective dates recorded. Signed PDFs or DMS signature logs satisfy inspector expectations for traceability.
• File naming conventions: use a consistent convention incorporating date, version and document ID to prevent ambiguity (e.g., PSMF_v3.0_20260530_QPPVsig.pdf).
• Change control: maintain a change control register for all PSMF, SOP and process updates; link change controls to CAPAs where relevant.
• Retention and archival: retain source files and unredacted originals in a secure area with documented reasons for any redactions provided to inspectors. Follow local regulatory retention requirements.
• Remote inspection readiness: for remote inspections, validate secure sharing platforms before inspection, ensure remote access for inspectors to DMS or controlled packages, and maintain communication logs.

Governance: roles, responsibilities and decision rights

• QPPV: owns system-level oversight, approves the PSMF, signs off major governance deliverables, engages with regulators.
• Inspection Lead: operational coordination, point of contact for inspectors, manages logistics and trackers.
• Document Coordinator: maintains document request tracker, prepares and quality checks submissions.
• PV Quality Lead / Head of Quality: ensures CAPA governance, audit programme, and closure verification.
• SMEs (Safety Ops, Vendor Oversight, Medical Information, RA): prepare technical responses and supporting evidence.
• Legal / Data Protection: advise on redaction and confidentiality review for submitted documents.

Governance mechanisms: - Establish an inspection governance charter defining authorities for approvals, prioritisation of document requests and decision escalation. - Formalise roles and delegated authorities in a one‑page inspection organogram; include contact details and backup arrangements. - Use change control and quality review steps for all inspection artefacts prior to submission; record reviewer names and timestamps in the tracker.

Mock inspections and rehearsal protocol

• Conduct regular mock inspections using the Interview Question Bank and Document Request Tracker.
• Include cross‑functional participation and use realistic request simulations (e.g., ask for an older audit report, a corrected SOP, or CAPA evidence).
• Use the scribe to capture timing, retrieval speed of documents, accuracy of responses and any inconsistencies between oral answers and documents.
• Post-mortem: generate an action log and CAPA entries with evidence templates to confirm remediation.

Inspection day conduct and tactical considerations

• Maintain a single point of contact for inspector communications; log all interactions in the tracker.
• Provide the inspector with a PSMF snapshot and index at the outset to facilitate navigation.
• For interviews, supply the QPPV with a one‑page briefing (key facts, references to evidence, and recent significant events).
• Record all commitments and follow‑ups and assign an owner and deadline; enter these immediately into the tracker.
• Keep a running list of documents prepared “on demand” so that completeness can be shown at close‑out.

Practical examples: quick reference scenarios

Example 1 — Document request flow: - Inspector requests "recent signal review report" (REQ-2026-011). - Document Coordinator identifies Signal Lead as custodian, retrieves Report-SIGNAL-Q1-2026_v1.0, quality checks, records planned submission time, obtains QPPV approval for submission, uploads to secure share, records actual submission time and inspector receipt.

Example 2 — QPPV interview: - Inspector asks "How do you ensure vendor X meets reporting timelines?" - QPPV answers with summary: contractual reporting terms, KPI thresholds, recent KPI trend, reference to vendor audit date and vendor corrective actions, and offers to provide KPI report (link provided). The Document Coordinator immediately logs the requested KPI report and submits it via the tracker.

Example 3 — CAPA evidence presentation: - Inspector requests evidence that CAPA-2025-015 improved timeliness. - CAPA owner presents KPI charts (pre/post), training completion logs, revised SOP, and the CAPA evidence pack with signed verification and date of effectiveness review.

Common inspection pitfalls and how artefacts mitigate them

• Incomplete indexing: an outdated PSMF index forces inspectors to hunt for documents — maintain the PSMF index and link to DMS to avoid this.
• Missing evidence trail: CAPAs without demonstrable effectiveness lead to findings — use the CAPA Evidence Template to capture implementation and monitoring.
• Inconsistent responses: mismatches between interview answers and documents cause credibility loss — use the Interview Question Bank and mock interviews to align messaging.
• Poor document tracking: inconsistent submissions and unlogged redactions raise concerns — use the Document Request Tracker to provide an auditable trail.

After the inspection: documentation, CAPA and regulatory engagement

• Consolidate inspector comments, extract formal observations and open CAPAs where required using the CAPA Evidence Template.
• Update the PSMF, SOPs and the PSMF index in controlled fashion, citing inspection as the reason where changes are made.
• Prepare regulatory responses as required, supported by the document request tracker, CAPA evidence and audit trail.
• Conduct a governance review to update inspection readiness materials and the Interview Question Bank to reflect lessons learned.

Key takeaways

• Preparation, governance and traceability are the pillars of effective inspection hosting.
• Standardised, inspection‑ready artefacts (Document Request Tracker, PSMF Index, Interview Question Bank, CAPA Evidence Template) reduce risk and accelerate responses.
• Inspectors look for demonstrable oversight, auditable evidence and consistent messaging; the templates provided facilitate these expectations.
• Governance: assign clear roles, apply change control and retain evidence of review and effectiveness.
• Regular mock inspections and updates to templates maintain organisational readiness and resilience.

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.