Inspection Interviews in Pharmacovigilance

Inspection interviews are one of the principal ways inspectors test whether the pharmacovigilance system described in procedures, records and the pharmacovigilance system master file (PSMF) is actually understood and operated by the people responsible for it.

An interview is therefore not primarily a memory test. Inspectors use questions to examine responsibility, understanding, decision-making, escalation, oversight and consistency with evidence. A technically correct answer that contradicts the documented process can create more concern than an answer that appropriately pauses for verification.

Regulatory Context and Purpose

EU pharmacovigilance inspections are conducted under the legal framework established by Directive 2001/83/EC, Regulation (EC) No 726/2004 and related implementing legislation. GVP Module III — Pharmacovigilance inspections describes inspection conduct and recognises interviews with relevant staff as part of the evidence available to inspectors.

GVP Module I is particularly relevant because it establishes expectations for the pharmacovigilance quality system and the QPPV's system-level oversight. GVP Module II is relevant where interview statements are compared with the PSMF description of responsibilities, processes, outsourced activities and system organisation.

Interviews therefore sit within a wider evidence model:

documented requirement → stated process → interview explanation → operational evidence → inspector conclusion.

The interview does not stand alone. Inspectors can compare what an individual says with SOPs, PSMF content, case records, metrics, contracts, audit trails, meeting minutes and system demonstrations.

Why Inspectors Interview People

Documents show what an organisation says should happen. Interviews help inspectors determine whether people understand what actually happens.

Interviews can test whether:

• responsibilities are clearly understood;
• tasks and accountabilities are aligned with documented roles;
• escalation pathways work in practice;
• significant risks are visible to the appropriate level of management;
• outsourced activities remain under control;
• individuals understand the controls they rely on;
• deviations and failures are recognised and managed; and
• operational practice matches the PSMF and procedures.

This is why interview questions often begin broadly and then become more specific. An inspector may first ask how a process works, then request an example, then ask for the underlying record.

Who May Be Interviewed

The interview population depends on inspection scope. It may include:

• the QPPV and deputy arrangements;
• pharmacovigilance operations staff;
• safety physicians or scientists;
• signal-management personnel;
• aggregate-report authors or reviewers;
• quality and audit personnel;
• vendor-management staff;
• regulatory affairs;
• medical information or product-quality interfaces;
• local affiliate personnel; and
• IT or system specialists where relevant.

No fixed list applies to every inspection. Inspectors select individuals according to the activities, risks and evidence they need to examine.

The QPPV Interview

The QPPV interview has a distinct purpose because GVP Module I assigns the QPPV responsibility for maintaining oversight of the functioning of the pharmacovigilance system and identifies the QPPV as a contact point for pharmacovigilance inspections.

Inspectors may therefore explore whether the QPPV can explain:

• the overall pharmacovigilance system and major changes;
• how significant safety and compliance issues reach the QPPV;
• major outsourced activities and their oversight;
• important audit findings and CAPAs;
• significant system or database changes;
• important risk-management obligations;
• how quality and compliance performance are monitored; and
• what authority and access the QPPV has when action is needed.

The QPPV is not expected to reproduce every operational SOP from memory. The central question is whether system-level oversight is genuine, informed and effective.

Oversight versus operational knowledge

A QPPV should understand enough about critical processes to assess whether the system is functioning, but that does not require performing every process or knowing every transaction-level detail.

For example, the QPPV should be able to explain how ICSR reporting compliance is monitored, how significant delays are escalated and what happens when performance deteriorates. The QPPV does not necessarily need to describe every database field used by a case processor.

This distinction is important because over-preparation can push QPPVs toward memorising operational detail at the expense of demonstrating actual oversight.

Subject-Matter Expert Interviews

SME interviews usually go deeper into process execution.

An inspector may ask an SME to explain:

1. what triggers the process;
2. who performs each step;
3. what controls prevent or detect error;
4. what records are created;
5. how deviations are handled;
6. how performance is monitored; and
7. how changes are implemented.

A strong SME can connect procedure to practice. The explanation should be specific enough that the inspector can trace the process into evidence.

For instance, a vendor manager should not stop at “we monitor vendors through KPIs.” The inspector may reasonably ask which KPIs, how exceptions are identified, who reviews them, what escalation occurs, and to see an example where poor performance led to action.

How Inspectors Develop Questions

Inspection questions are often evidence-driven rather than drawn from a fixed questionnaire.

A document, metric or earlier interview may create the next question. Examples include:

• a PSMF states that a governance committee reviews compliance monthly, so the inspector asks how that committee works and requests recent minutes;
• a metric shows improved reporting timeliness, so the inspector asks what changed and how the metric population is defined;
• a vendor agreement assigns literature screening to a third party, so the inspector asks how completeness is reconciled and monitored;
• an audit identified a recurring weakness, so the inspector asks how CAPA effectiveness was established.

Understanding this dynamic is more useful than memorising a generic “top 50 inspection questions” list.

Preparing for an Interview

Preparation should improve understanding and evidence awareness, not create scripted testimony.

An interviewee should review:

• their current responsibilities;
• the procedures and records relevant to those responsibilities;
• important recent changes;
• significant deviations, CAPAs or audit findings in their area;
• relevant metrics and trends;
• interfaces with vendors or other functions;
• escalation pathways; and
• the evidence that demonstrates the process works.

For the QPPV, preparation should additionally include the current system risk picture and significant matters requiring oversight.

Preparation should be risk-based

Not every document needs to be memorised. Preparation should concentrate on areas within inspection scope, recent changes, known weaknesses and issues likely to require explanation.

A mock interview can be useful when it tests genuine understanding and evidence retrieval. It becomes counterproductive when it rewards memorised phrases or teaches interviewees to avoid acknowledging real problems.

Conducting the Interview

The most reliable interview technique is straightforward: listen carefully, answer the question asked, distinguish fact from assumption, and support important statements with evidence where needed.

Answer directly before adding context

Long answers can create ambiguity. A useful sequence is:

1. answer the question directly;
2. explain the relevant control or reasoning;
3. give a concrete example if useful; and
4. identify documentary evidence if the inspector wants verification.

This keeps the interview focused while still allowing the inspector to follow the evidence trail.

Do not guess

When an interviewee is uncertain about a detail, it is better to verify it than to speculate. A suitable response may explain what is known and state that the exact figure, date or document reference will be confirmed through the inspection request process.

Accuracy is more important than speed.

Distinguish personal knowledge from organisational evidence

An individual may know how a process generally works but not the exact status of a particular case, CAPA or system record. The interviewee should avoid converting general knowledge into an unsupported statement about a specific record.

For example, “our standard process requires reconciliation” is not the same as “this reconciliation was completed on 3 September.” The second statement should be based on the actual record.

Consistency Between Interview and Evidence

Inspectors often triangulate several evidence sources.

A discrepancy does not automatically mean misconduct or a finding. Processes can change, documents can lag, and individuals can misunderstand. But an unexplained inconsistency can prompt deeper inspection.

The appropriate response is to understand and reconcile the difference rather than force all sources into artificial agreement.

Handling Difficult Questions

Difficult questions often concern known failures, overdue CAPAs, vendor problems, historical non-compliance or areas where the organisation's controls did not work as intended.

A credible answer usually contains four elements:

1. acknowledgement — what happened;
2. scope — what is known about the extent and impact;
3. action — what was done to contain and correct the issue; and
4. current state — what evidence shows about the situation now.

The goal is not to present the organisation as flawless. A mature pharmacovigilance quality system should be able to identify weaknesses, investigate them and improve.

Avoid defensive language

Blaming an individual, affiliate or vendor rarely explains system control. Even where a third party made an error, the inspector may still ask how responsibilities were defined, how performance was monitored and why the MAH's controls did not detect the problem earlier.

The interview should therefore focus on the system and the evidence.

Common Interview Themes

Inspection questions vary with scope, but several themes recur because they test core aspects of system effectiveness.

Roles and responsibilities

Questions may explore what the interviewee is responsible for, where authority begins and ends, how tasks are delegated and how coverage is maintained.

Escalation and governance

Inspectors may ask how significant safety, compliance or quality issues are identified and escalated, who receives them and what happens next.

Vendor oversight

Questions may test which activities are outsourced, how responsibilities are documented, how performance is monitored, how deviations are handled and whether subcontracting is understood.

Audit and CAPA

Inspectors may ask how audit priorities are set, how findings are managed, how root causes are established and how CAPA effectiveness is verified.

PSMF maintenance

Questions may explore who maintains the PSMF, how significant changes are captured and whether its contents match current system reality.

Metrics and performance

Inspectors may ask which metrics are used, what population they measure, how exceptions are investigated and how trends influence management decisions.

Computerised systems

Where relevant, interviewees may be asked how system changes are controlled, what users can access, how significant failures are managed and what the QPPV knows about important pharmacovigilance-system changes.

Example QPPV Questions and What They Test

The following examples are illustrative and are not a regulator-issued question bank.

These questions are useful for preparation only if the answers are based on the organisation's real system.

Example SME Questions and What They Test

The strongest interviewees can move naturally between process explanation and evidence without reciting a procedure verbatim.

Remote Interviews

GVP Module III recognises remote inspections, including remote interviews and document or system review where feasible.

Remote interviews create additional practical considerations:

• stable communication and screen-sharing arrangements;
• clear identification of participants;
• avoidance of off-screen coaching or uncontrolled communications;
• orderly document retrieval through the agreed inspection channel; and
• awareness of time-zone and technology constraints.

The inspection authority's arrangements should govern how the remote interview is conducted. Internal preparation should not interfere with the independence or integrity of the interview.

Use of Scribes and Support Personnel

Some organisations use a scribe or inspection coordinator during interviews, where permitted by the inspectorate. Their role may be to record questions, follow-up commitments and document requests.

They should not answer for the interviewee or coach responses during the interview. The presence and role of support personnel should be transparent and consistent with the inspector's expectations.

Potential Failure Modes

The following are illustrative failure modes, not published inspection findings.

How an Inspector May Evaluate an Interview

An inspector may consider whether the interviewee:

• understands their actual responsibilities;
• can describe how the process operates in practice;
• knows how significant problems are escalated;
• can identify the controls that prevent or detect failure;
• understands important recent changes and known weaknesses;
• gives answers consistent with documentary and operational evidence;
• distinguishes known facts from matters requiring verification; and
• demonstrates appropriate ownership without overstating authority.

For the QPPV, additional attention may be given to whether the person has sufficient access, authority and awareness to maintain effective system oversight.

Practical Interview Preparation Checklist

This checklist is recommended operational practice, not an EU regulatory template.

For all interviewees

1. Can I explain my responsibilities in plain operational terms?
2. Do I understand the processes within my scope, including important interfaces?
3. Do I know the key controls and what happens when they fail?
4. Am I aware of significant current deviations, CAPAs or changes in my area?
5. Can I identify where supporting evidence is held?
6. Do I know my escalation pathways?
7. Can I distinguish what I know personally from what must be verified from a record?

Additional questions for the QPPV

1. Can I explain the current structure of the pharmacovigilance system?
2. What are the most significant current safety, compliance and quality risks?
3. What major changes have occurred recently?
4. Which important audits, CAPAs or vendor issues require my awareness?
5. How do significant issues reach me, and what authority do I have to act?
6. Can I explain how I maintain oversight without implying that I perform every operational task?

Immediately before the interview

1. Have I reviewed the actual inspection scope relevant to me?
2. Do I know which significant issues are likely to be discussed?
3. Am I clear about which documents or records may support my answers?
4. Have I avoided memorising scripts that could conflict with real evidence?

Illustrative Interview Scenario

The following scenario is hypothetical.

An inspector asks a QPPV: “How do you know your outsourced case-processing vendor is meeting reporting requirements?”

A weak answer might be: “The vendor is audited every two years and their KPI is above 98%.” This may be incomplete because it does not explain what the KPI measures, whether failures outside the measured population are visible, how exceptions are escalated or whether the audit frequency is risk-based.

A stronger answer would explain the actual oversight model: which reporting and quality metrics are reviewed, how the denominator is defined, how reconciliation identifies cases that may never have entered the vendor workflow, how significant deviations reach the QPPV or responsible governance body, how vendor CAPAs are monitored and what evidence shows the controls have operated recently.

The strength of the answer lies not in its length but in the connection between oversight claim and verifiable evidence.

After the Interview

Interview follow-up may include additional document requests, clarifications or data extraction. These should be captured through the agreed inspection request process so that the answer and evidence remain traceable.

If an interview reveals a genuine internal inconsistency or previously unknown deficiency, the organisation should not simply rehearse a better answer for later interviews. The discrepancy should be understood and, where appropriate, investigated and contained.

The interview is part of inspection evidence. It can therefore reveal both strengths and weaknesses in the pharmacovigilance system.

Relationship With Inspection Hosting and Findings

Interview management should be integrated with the wider inspection-hosting process described in [[inspection-hosting-for-qppvs]]. Requests and commitments arising from interviews should feed into the same controlled inspection workflow.

Where interview evidence contributes to a formal deficiency, subsequent remediation should follow the finding-management principles described in [[inspection-findings]]: understand the requirement, scope the issue, assess impact, determine root cause, implement proportionate CAPA and verify effectiveness.

Key Takeaways

Pharmacovigilance inspection interviews are evidence-generating activities used to test whether responsibilities, governance and operational controls are understood and functioning as described.

The QPPV interview focuses particularly on system-level oversight, risk awareness, access to information, escalation and authority. SME interviews generally examine deeper operational execution and control.

Strong preparation is based on current responsibilities, known risks, recent changes and evidence—not memorised answers. Interviewees should answer directly, avoid speculation and verify specific details when necessary.

Consistency matters because inspectors can compare interviews with the PSMF, procedures, metrics, records and system demonstrations. When sources disagree, the correct response is to understand and explain the discrepancy rather than force artificial consistency.

References

1. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module I — Pharmacovigilance systems and their quality systems. EMA/541760/2011. https://www.ema.europa.eu/en/documents/scientific-guideline/guideline-good-pharmacovigilance-practices-module-i-pharmacovigilance-systems-and-their-quality-systems_en.pdf
2. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module II — Pharmacovigilance system master file (Rev. 2). EMA/816573/2011 Rev. 2.
3. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module III — Pharmacovigilance inspections. EMA/119871/2012 Rev. 1. https://www.ema.europa.eu/en/documents/scientific-guideline/guideline-good-pharmacovigilance-practices-module-iii-pharmacovigilance-inspections_en.pdf
4. European Medicines Agency. Pharmacovigilance inspection procedures: human. Current Union procedures for preparation, conduct, reporting and follow-up of pharmacovigilance inspections.
5. European Union. Commission Implementing Regulation (EU) No 520/2012, consolidated version current at 12 February 2026.
6. European Union. Directive 2001/83/EC, as amended.
7. European Union. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article distinguishes binding EU requirements, GVP guidance, Union inspection procedures and recommended interview-preparation practices. As of 7 September 2026, EMA continues to list GVP Module I, Module II Rev. 2 and Module III Rev. 1 as the applicable published modules. EMA has announced future GVP revisions following Commission Implementing Regulation (EU) 2025/1466, so current versions should be checked before a live inspection.