How to Prepare for a Pharmacovigilance Inspection
Make the system demonstrable, not merely compliant, before the inspector arrives.
What a how-to is not
A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.
A pharmacovigilance inspection tests whether the system described on paper is the system in operation. Preparation is therefore not document assembly — it is closing the distance between the two. The most damaging findings are rarely about a single late case; they are about a system that cannot show how it works.
- 1
Reconcile the master file against reality
Walk the master file section by section and confirm each statement is still true: named roles, sites, delegated activities, systems, procedures. Every divergence found now is a finding avoided, and the change logbook should show the correction.
- 2
Rehearse the case-processing walkthrough
Take a sample of cases and follow each from the intake record to the transmission acknowledgement. If the chain cannot be reconstructed quickly for a case you chose, it will not be reconstructable for one the inspector chooses.
- 3
Check compliance metrics and be ready to explain them
Assemble on-time submission rates, follow-up completion, and reconciliation results for the period under review. Adverse metrics with a documented cause and corrective action are far safer than metrics presented as uniformly excellent.
- 4
Confirm oversight of delegated activities is evidenced
For every partner performing pharmacovigilance work, produce the contract, the agreed responsibilities, and the evidence of oversight — audits, metrics, escalations. Delegation without evidenced oversight is one of the most frequently cited weaknesses.
- 5
Verify training and procedure currency
Confirm that procedures reflect current practice and that the people performing each activity are trained on the current version. A procedure superseded in practice but not in the system is a documented mismatch waiting to be found.
- 6
Brief the people who will answer questions
Prepare staff to describe what they actually do and to say plainly when something is outside their knowledge. A confident wrong answer creates a thread; an honest handover to the right person does not.
- !Preparing documents rather than closing the gap between the described system and the operating one.
- !Metrics presented as uniformly excellent, with no evidence of self-detected problems being corrected.
- !Oversight of delegated activities asserted in a contract but never evidenced in practice.
- !Staff coached to answer beyond their knowledge rather than to hand over to the right person.
How to Prepare for a Pharmacovigilance Inspection: frequently asked questions
Common questions on prepare for a pharmacovigilance inspection.
What does an inspector actually test?
Whether the system in operation matches the system described, and whether it produces the outcomes it claims. That is why walkthroughs of real cases and evidence of oversight matter more than the tidiness of the document set.
Are imperfect compliance metrics a problem?
Less than you might fear, provided the organisation found them itself, understood the cause, and acted. What raises concern is a system reporting perfection, because it suggests the monitoring is not sensitive enough to detect its own failures.
How should staff handle a question they cannot answer?
By saying so and directing the inspector to whoever owns that activity. Speculation creates inconsistencies across interviews, and inconsistency is what turns a single question into a line of enquiry.