What Inspectors Expect From a PV Training Program

Pharmacovigilance training is one of the easiest parts of a PV system to under-resource and one of the first things an inspector checks. The reason is simple: training records are documentary evidence of whether the rest of your PV system can actually function. If the people running ICSR processing, signal management, or QPPV oversight cannot be shown to be trained and current, the inspector has no basis to trust the processes they operate.

What inspectors expect, in one line: a documented, role-specific, regularly refreshed training program — covering everyone who can touch safety data — backed by training records that prove it actually happened.

This guide explains what a GVP-compliant PV training program must contain, the findings inspectors raise most often, and a readiness checklist.

Why Training Is a Regulatory Requirement, Not an HR Nicety

GVP Module I sets the expectation explicitly: the MAH must ensure all personnel involved in pharmacovigilance activities receive initial and continued training, and that training is documented. The QPPV is responsible for ensuring this happens.

The principle behind it: a PV system is only as reliable as the people executing it. A perfectly written SOP is worthless if the person following it was never trained on the current version. Inspectors treat training records as the link between your documented system and your operating system.

This requirement is not limited to the PV department. It reaches anyone whose role means they could receive or handle a safety report — which is broader than most biotech teams assume.

Who Must Be Trained — Wider Than the PV Team

The most common gap: a biotech trains its PV department thoroughly and forgets that a sales representative or a medical information line operator can also receive an adverse event — and must know to forward it within 24 hours.

The Elements of an Inspection-Ready Training Program

1. A training plan / matrix

A documented matrix mapping roles to required training. It defines, for each role, which modules are mandatory, at what depth, and at what frequency. Without a matrix, you cannot demonstrate that the right people received the right training.

2. Role-specific content

Training must be proportionate to the role. A case processor needs deep ICSR training; a sales representative needs to recognise an adverse event and know the forwarding rule and timeline. One generic deck for everyone is a finding waiting to happen.

3. Initial (onboarding) training

Every new joiner in a PV-relevant role must be trained before they perform PV activities — and that timing must be documented.

4. Continued / refresher training

PV knowledge decays and regulations change. Refresher training on a defined cycle (commonly annual) keeps staff current, especially after GVP updates.

5. SOP and process training

When an SOP is created or revised, affected staff must be trained on the new version, and the record must tie the training to that SOP version.

6. Training records

The evidentiary core. Each record should show who was trained, on what (including document version), when, by whom, and ideally evidence of comprehension (assessment or sign-off). Records must be retrievable on request during an inspection.

7. Curriculum vitae and job descriptions

Inspectors cross-check that staff qualifications and job descriptions are consistent with the PV roles they hold and the training they received.

For the programme design itself, see our Safety Corner overview of role-based pharmacovigilance training and of the wider PV system it supports.

The Findings Inspectors Raise Most Often

• No training matrix. Training happens, but there is no documented link between roles and required training — so completeness cannot be demonstrated.
• Non-PV staff untrained. Sales, medical affairs, or medical information staff who can receive adverse events were never trained on adverse event recognition and forwarding.
• Training not tied to SOP versions. An SOP was revised, but there is no record that staff were trained on the current version.
• No refresher cycle. Initial training exists; there is no evidence of ongoing/continued training.
• Records incomplete or unretrievable. Training happened but cannot be evidenced — dates missing, no sign-off, or records that cannot be produced during the inspection.
• QPPV training not documented. The QPPV's own continued GVP training is not evidenced.
• Vendors not covered. A contracted partner handles safety data, but there is no evidence their staff are trained, and the contract does not require it.

A useful rule of thumb: in pharmacovigilance, if it is not documented, it did not happen. Training that occurred but was not recorded is, from an inspector's standpoint, training that did not occur.

How these findings are raised and graded in practice is covered in our overview of PV audits and inspections.

PV Training Program Readiness Checklist

• Documented training plan / matrix mapping roles to required training
• Role-specific content (not one generic deck for everyone)
• Adverse event awareness training for all staff who could receive a safety report
• Initial training completed before staff perform PV activities
• Defined refresher / continued training cycle
• SOP training tied to specific document versions
• Complete, retrievable training records (who / what / version / when / sign-off)
• QPPV and deputy continued-training records
• CVs and job descriptions consistent with PV roles
• Vendor / partner training covered contractually and evidenced
• Training program owned and periodically reviewed (typically by the QPPV)

If the QPPV oversight side of this is still open, our EU and local QPPV services cover the accountability layer that owns the training programme, and our PV services cover the operational layer it trains people to run.

Key Takeaways

• PV training is a GVP Module I requirement and one of the first things inspectors check.
• Training must reach everyone who could receive a safety report — not just the PV department.
• An inspection-ready program has a role-based training matrix, role-specific content, initial and refresher training, SOP-version-linked training, and complete, retrievable records.
• The most common findings are a missing matrix, untrained non-PV staff, and training that is not tied to current SOP versions.
• If training is not documented, an inspector treats it as not having happened.

Frequently Asked Questions

Who needs pharmacovigilance training in a biotech?

Everyone whose role could mean they receive or handle a safety report — which is wider than the PV department. It includes PV and safety staff, the QPPV and deputy, medical affairs and MSLs, sales and commercial staff, regulatory affairs, clinical operations, medical information / customer-facing staff, senior management, and any vendor handling safety data on the MAH's behalf. Training depth should be proportionate to the role.

How often is refresher PV training required?

GVP Module I requires both initial and continued training but does not fix a single mandatory interval. In practice, an annual refresher cycle is common and well-regarded by inspectors, with additional ad-hoc training triggered by GVP updates, SOP revisions, or significant process changes. The key is a defined, documented cycle rather than a specific number.

What training records do inspectors want to see?

For each training event: who was trained, on what (including the specific document or SOP version), when, by whom, and ideally evidence of comprehension such as an assessment or sign-off. Records must be complete and retrievable on request during the inspection. In pharmacovigilance, training that occurred but was not documented is treated as training that did not occur.

NextPV builds and runs training programmes as part of client PV systems — why teams work with us.