Common Pharmacovigilance Inspection Failures

Introduction

Inspection observations often reveal system weaknesses rather than isolated mistakes. The relevant question is not whether an organisation can produce a policy, but whether it can demonstrate a controlled process, credible oversight, reliable records and effective learning.

The patterns below are potential failure modes and preparation prompts. They are not presented as universal findings or as a substitute for the competent authority’s current inspection guidance.

Systemic failure patterns

Governance without evidence

A governance chart is not evidence that decisions, escalation and review occurred. Retain minutes, decisions, action tracking, QPPV involvement and links to safety outputs.

QPPV visibility too late

If the QPPV learns of major findings, overdue actions, significant vendor issues or important signals only at the end of a process, the system cannot demonstrate timely oversight. Define escalation criteria and preserve the decision trail.

PSMF disconnected from practice

The PSMF should describe the operating system accurately, including responsibilities, interfaces, delegated activities, performance indicators and significant changes. A document that conflicts with actual workflows creates an avoidable inspection question.

Weak case-processing evidence

Metrics without traceable denominators, exception handling or sample records do not show that cases were processed correctly. Be ready to connect intake, medical review, quality control, submission, follow-up and reconciliation.

Vendor oversight by contract alone

A quality agreement is necessary but does not prove performance. Combine contractual controls with qualification, oversight, metrics, audit or equivalent assurance, issue escalation and CAPA follow-up.

Data-integrity gaps

Inspectors may ask who entered, changed, reviewed, approved or transmitted safety data and whether the audit trail is reliable. Define access, reconciliation, change control, backup, retention and investigation of discrepancies.

CAPA without effectiveness

A completed action is not necessarily an effective action. Show the finding, cause, scope, containment, permanent change, check and closure rationale.

Training as a proxy for competence

Training completion does not prove understanding or reliable performance. Use role-based content, qualification, observation, quality checks or other evidence appropriate to the task.

Evidence and response

Build an evidence chain

For a selected process, connect requirement, procedure, record, exception, review, escalation, CAPA and effectiveness evidence. This chain is more persuasive than a folder of disconnected documents.

Answer questions precisely

If a record cannot be found, say so and explain the controlled retrieval route. Do not speculate, backfill or create retrospective records without preserving the original context. Inspection responses should distinguish fact, interpretation, corrective action and commitment.

Manage mock inspections carefully

A mock inspection can test retrieval, interview readiness, room logistics and escalation. It should not generate fictional regulatory findings or encourage rehearsed answers that hide uncertainty. Capture lessons and improve the system.

Readiness checklist

• current PSMF and linked annexes;
• QPPV contact and delegation evidence;
• current quality and procedural documents;
• case, signal, aggregate and risk-management samples;
• vendor and affiliate oversight evidence;
• training and competence evidence;
• audit, finding and CAPA lifecycle;
• data-integrity and system-validation records;
• regulatory correspondence and commitments;
• controlled retrieval and secure access.

References

• EMA, GVP Module III: Pharmacovigilance inspections
• EMA, GVP Module II: Pharmacovigilance system master file
• EMA, GVP Module I: PV systems and quality systems
• EMA, GVP overview

Regulatory Note

Inspection scope, process and evidence expectations vary by authority, product and jurisdiction. These prompts support readiness but do not predict an inspection outcome or create a universal checklist.