The short version
What teams need to understand
- Pharmacovigilance documents must be updated through controlled change management processes.
- All changes must be documented, reviewed, and approved before implementation.
- Version control must ensure full traceability of document revisions.
- Periodic review must confirm that documents remain current and compliant.
- Changes must reflect regulatory updates, operational changes, or identified issues.
- Inspection-ready evidence must demonstrate controlled updates, traceable version history, and regular document review.
Regulatory expectation
What regulators expect
Each expectation should be supported by controlled documentation, traceable records, clear ownership, and evidence that the process works in practice.
- All document changes must be controlled and approved.
- Version history must be traceable.
- Documents must be reviewed periodically.
- Changes must reflect regulatory and operational updates.
- Obsolete versions must be removed from use.
Why it matters
What this means in practice
Inspectors assess whether pharmacovigilance documents are updated through controlled change processes. They review version history, change request documentation, periodic review cycles, and evidence that documents are kept current and compliant.
Questions this page answers
Inspection evidence
Evidence teams should be able to show
Document Change Request Records
- Formal change request forms
- Description of proposed changes
- Justification for document updates
- Approval of change requests
Version Control and Revision History
- Version numbering system
- Revision history logs within documents
- Summary of changes between versions
- Traceability from previous to current versions
Periodic Review Records
- Scheduled review cycles (e.g. annually)
- Review completion records
- Assessment of document relevance and accuracy
- Approval of continued use or update
Change Implementation Evidence
- Updated documents reflecting approved changes
- Communication of document updates to users
- Alignment between change request and final document
- Removal of superseded versions
Regulatory and Operational Change Triggers
- Updates following regulatory changes
- Changes due to process improvements
- Updates triggered by audit findings or CAPA
- Adjustments based on system or organisational changes
Regulatory Basis (Primary Sources)
- GVP Module I - requirement for document control and quality system updates
- GVP Module II - requirement for maintaining current PV system documentation
- ICH E2D - requirement for maintaining compliant and current documentation
- MHRA GPvP guidance - expectations for document review and control
- FDA 21 CFR Part 11 - requirements for audit trails and document version control
Typical Inspection Questions (What Inspectors Ask)
- How are document changes managed?
- Show me the version history of this document.
- How often are documents reviewed?
- What triggered the last update to this SOP?
- How do you ensure outdated documents are not used?
Common failure patterns
What good looks like
- Controlled change request process for all updates.
- Clear and traceable version history.
- Defined periodic review schedule.
- Prompt updates following regulatory or process changes.
- Removal of obsolete documents from use.
How teams operationalise it
- Implement a formal document change request process.
- Maintain version control with clear numbering and history.
- Schedule periodic document reviews.
- Update documents based on regulatory or operational changes.
- Remove obsolete versions from circulation.
- Maintain audit trails for all document changes.
From expectation to working control
Find the documentation that supports this work
Review the related toolkit to understand its purpose, included files, and how it supports this regulatory expectation.
Frequently asked questions
What is change control in pharmacovigilance?
Change control is the process of managing updates to documents through formal request, review, approval, and implementation to ensure compliance and traceability.
What is document version control?
Version control is a system that tracks document revisions, ensuring that all changes are recorded and traceable across versions.
How often should pharmacovigilance documents be reviewed?
Documents are typically reviewed periodically, often annually or based on risk, to ensure they remain current and compliant.
What triggers document updates?
Updates are triggered by regulatory changes, process improvements, audit findings, CAPA, or organisational changes.
Do inspectors review document change control?
Yes. Inspectors review change control processes, version history, and evidence that documents are kept current.
How do you ensure outdated documents are not used?
Outdated documents are controlled through versioning, removal from circulation, access restrictions, and clear identification as obsolete.
Source boundary
Regulatory sources
These primary sources inform this structured interpretation. Always confirm current requirements against the original source and the requirements applicable to your organisation, product, and jurisdiction.
European Medicines Agency (EMA)
Guideline on good pharmacovigilance practices (GVP) - Module I
View sourceGuideline on good pharmacovigilance practices (GVP) - Module II
View source
FDA
21 CFR Part 11 - Electronic Records
View source
ICH
Post-Approval Safety Data Management (E2D)
View source
MHRA
Good Pharmacovigilance Practice (GPvP)
View source