The short version
What teams need to understand
- Pharmacovigilance documents must undergo structured review and formal approval before use.
- Review must confirm accuracy, completeness, and alignment with regulatory and operational requirements.
- Approval must be performed by authorised roles with defined responsibility.
- Documents must have a clearly defined effective date before implementation.
- Only approved and current documents must be made available for use.
- Inspection-ready evidence must demonstrate controlled review, approval, and release processes.
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.
- Documents must be reviewed and approved before use.
- Approval must be performed by authorised roles.
- Documents must have a defined effective date.
- Only approved documents must be accessible to users.
- Document approval processes must be traceable.
Why it matters
What this means in practice
Inspectors assess whether pharmacovigilance documents are reviewed, approved, and released through controlled processes. They review approval workflows, approver authority, effective dates, and evidence that only approved documents are in use across the PV system.
Questions this page answers
Inspection evidence
Evidence teams should be able to show
Document Review Workflow
- Defined review stages before approval
- Reviewer roles and responsibilities
- Evidence of document accuracy and completeness checks
- Review comments and resolution tracking
Approval Records and Sign-Off
- Formal approval signatures or electronic approvals
- Authorised approver roles (e.g. PV, QA)
- Approval date and version confirmation
- Evidence of approval authority
Document Review and Approval Tracker
- Tracking of documents under review
- Approval status and progress
- Reviewer and approver assignment
- Completion of review and approval cycle
Effective Date and Release Controls
- Defined effective date on approved documents
- Controlled release of documents to users
- Alignment between approval and effective date
- Evidence that documents are not used before approval
Document Distribution Controls
- Access to approved documents only
- Removal or restriction of draft versions
- User notification of new or updated documents
- Audit trail of document access and release
Regulatory Basis (Primary Sources)
- GVP Module I - requirement for controlled documentation within the PV quality system
- GVP Module II - documentation requirements supporting the PV system master file
- ICH E2D - requirement for controlled and compliant safety documentation processes
- MHRA GPvP guidance - expectations for document approval and control
- FDA 21 CFR Part 11 - requirements for electronic records and approval workflows
Typical Inspection Questions (What Inspectors Ask)
- Who reviewed and approved this document?
- How do you ensure documents are approved before use?
- What is the effective date of this document?
- How do you track document approval status?
- How do you prevent use of draft or unapproved documents?
Common failure patterns
What good looks like
- Defined and structured document review workflow.
- Formal approval by authorised roles.
- Clear effective dates for all documents.
- Controlled release ensuring only approved documents are used.
- Traceable review and approval records.
How teams operationalise it
- Define document review and approval workflows within SOPs.
- Assign authorised reviewers and approvers.
- Track document status through review and approval stages.
- Define effective dates before document release.
- Restrict access to draft and unapproved documents.
- Ensure audit trails for review and approval activities.
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
How are pharmacovigilance documents approved?
Documents are approved through a structured workflow involving review by subject matter experts and formal sign-off by authorised roles such as PV and QA.
What is an effective date in document control?
The effective date is the date when an approved document becomes valid and can be used within the pharmacovigilance system.
Who approves pharmacovigilance documents?
Documents are typically approved by authorised roles such as PV leadership and Quality Assurance, depending on organisational structure.
Do inspectors review document approval processes?
Yes. Inspectors review approval workflows, authorisation, and evidence that only approved documents are in use.
How do you ensure only approved documents are used?
By controlling access, removing draft versions, and ensuring only approved documents are available within the document management system.
What happens if documents are used without approval?
Use of unapproved documents can result in inspection findings due to lack of control and potential compliance risk.
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