A Pharmacovigilance System Master File is one of the most important documents within any safety system. It reflects how well your organisation manages drug safety activities, maintains compliance, monitors patient risks and ensures overall control of its pharmacovigilance processes. However, many companies still struggle to keep their PSMF updated and inspection ready throughout the year. Even small inconsistencies can raise significant concerns during inspections and may lead to findings that could have been avoided with better planning and documentation. This makes it critical to understand the common gaps that place organisations at risk and to implement strong governance practices that ensure the PSMF stays accurate, current and aligned with day to day operations.
Before looking at how Q&V can support you, it is important to first understand why many PSMFs fail inspections and the areas auditors commonly focus on.
Also Read: How to Prepare for an MHRA Inspection: Expert Tips from Quality and Vigilance
Why These Issues Cannot Be Ignored
PSMF issues cannot be ignored because they often reveal deeper weaknesses within the entire pharmacovigilance system. Even small gaps in the file can signal a lack of control, poor coordination and outdated practices, which immediately concerns inspectors.
These issues matter because they often indicate
• Incomplete or unreliable safety documentation
• Lack of ownership and unclear responsibilities
• Weak internal communication across PV and quality teams
• Processes that do not match what is written in the PSMF
• Limited oversight of vendors or outsourced activities
Inspectors view the PSMF as the clearest reflection of how well your organisation manages patient safety. Any inconsistencies or missing information suggest that the system is not fully controlled. This is why organisations must maintain continuous oversight, frequent reviews and consistent documentation. Ignoring these issues increases the risk of inspection findings and undermines overall compliance.
Common Reasons Why Your PSMF Could Fail an Inspection
1. Outdated or Inaccurate Information
One of the most common reasons for PSMF non compliance is outdated content. Information within the PSMF must align with the organisation’s current PV activities, personnel, processes and overall safety operations. However, many companies update only a portion of the file and forget to revise other interlinked sections, which creates inconsistencies that inspectors notice quickly.
Key areas that become outdated include
- PV personnel names, roles and CVs
- Safety vendor lists and contracts
- Updated pharmacovigilance agreements
- System descriptions and process changes
- Volume nine requirements and updated internal SOPs
Inspectors closely compare the PSMF with the organisation’s most recent activities. Even a single outdated section can suggest that the company does not routinely monitor or maintain the file. This raises the possibility of other gaps within the system.
2. Incomplete Documentation and Missing Evidence
Another major challenge organisations face is the lack of complete supporting evidence. The PSMF must not only describe the system but also be backed by real evidence. Often, companies mention a process but fail to attach or reference supporting documents. This creates a disconnect between written descriptions and actual operations.
Common examples include
- Missing training records for safety staff
- No documented evidence of QPPV oversight
- Incomplete or outdated organisational charts
- Missing reconciliation reports
- Absence of vendor oversight documentation
Inspectors assess whether every statement in the PSMF can be proven through documentation. If evidence is missing or unclear, it becomes a strong inspection finding.
3. Poor Integration Between the PSMF and Daily PV Activities
An effective PSMF must reflect the system exactly as it operates. Many organisations create a well written PSMF but fail to ensure that daily practices align with what is documented. This creates inconsistencies that inspectors immediately flag.
Examples of poor integration include
- Describing a process in the PSMF that is not followed in real practice
- Using outdated SOPs that conflict with operational steps
- Mentioning tools or systems that are no longer in use
- Inaccurate escalation procedures or communication pathways
- Incorrect information about case processing or signal activities
These inconsistencies indicate that the organisation does not have strong oversight of its safety system, which is a critical expectation during inspections.
4. Insufficient QPPV Oversight Documentation
Although many companies have a QPPV in place, the documentation that demonstrates their oversight is often incomplete. Inspectors expect clear evidence that the QPPV is fully aware of and actively involved in the pharmacovigilance system.
Frequent gaps include
- No documented QPPV approval for key safety procedures
- Missing QPPV involvement in audits or reviews
- Lack of traceable communication regarding safety decisions
- No evidence that the QPPV has access to the safety database
- Unclear backup arrangements for deputy QPPV responsibilities
Inspectors consider QPPV oversight a high priority. Any ambiguity in this area becomes a direct and significant finding.
5. Weak Vendor Management and Incomplete Oversight Activities
Many organisations work with multiple vendors for safety operations which makes oversight essential. However, these relationships and responsibilities are often not fully reflected in the PSMF.
Typical gaps include
- Missing descriptions of vendor responsibilities
- No documented oversight activities
- Incomplete partner lists
- Outdated agreements
- Missing audit records for third party vendors
If inspectors cannot verify how a company oversees vendors, it raises concern about compliance control across outsourced activities.
6. Lack of Regular Review Cycles and Version Control
A PSMF must always remain current and accurately version controlled. Many companies update it only before an inspection which leads to rushed changes, errors and missing information.
Common failures include
- Absence of fixed review timelines
- No version history with explanations
- Missing record of changes
- Unauthorised or undocumented edits
- No sign off trail for updates
Without structured review cycles, the PSMF loses credibility and does not represent a controlled document.
How Quality and Vigilance Ltd Supports You in Strengthening Your PSMF
Quality and Vigilance Ltd helps organisations improve control, accuracy and consistency across their pharmacovigilance systems. The focus is to ensure your PSMF stays clear, up to date and fully aligned with real operations.
Q&V supports you with
• Targeted PSMF reviews to spot gaps
• Alignment of documentation with actual practices
• Strong quality oversight and traceability
• Improved documentation structure and evidence trails
• Vendor oversight documentation reviews
• Clear ownership and responsibility mapping
• Routine review cycles and document control
• Strengthened QPPV oversight records
• Ensuring the PSMF reflects current processes and systems
By improving these areas, Q&V helps you maintain a reliable and inspection ready PSMF.