The short version
What teams need to understand
- Pharmacovigilance documents must be created using defined templates and structured formats.
- Document numbering systems must ensure traceability, version control, and identification.
- Authorship and ownership must be clearly assigned during document creation.
- Templates must standardise content, structure, and formatting across all PV documents.
- Document creation must align with regulatory requirements and operational processes.
- Inspection-ready evidence must demonstrate that document creation is controlled, consistent, and traceable from the outset.
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 created using controlled templates.
- Document numbering must ensure traceability and identification.
- Authorship and ownership must be clearly defined.
- Templates must ensure consistency across documentation.
- Document creation must align with PV processes and regulatory expectations.
Why it matters
What this means in practice
Inspectors assess whether pharmacovigilance documents are created using controlled templates, structured numbering systems, and defined authorship. They review document consistency, traceability, and whether templates ensure standardised and compliant documentation across the PV system.
Questions this page answers
Inspection evidence
Evidence teams should be able to show
Controlled Document Templates
- Standard SOP template with predefined structure
- Work instruction templates for operational processes
- Consistent section headings, formatting, and document layout
- Defined document headers including version, ID, and approval fields
Document Numbering System
- Unique document identifiers
- Standardised naming conventions
- Link between document number, type, and function
- Traceability across versions and document lifecycle
Document Creation and Authorship Records
- Document author identification
- Defined document owner responsibilities
- Draft creation records
- Evidence of initial document development process
Template Governance and Standardisation
- Controlled templates maintained within document system
- Consistency across SOPs, work instructions, and forms
- Defined formatting and structure requirements
- Template version control
Initial Document Review Preparation
- Prepared draft documents ready for review
- Alignment with PV processes and regulatory expectations
- Document completeness before formal approval
- Evidence of structured content development
Regulatory Basis (Primary Sources)
- GVP Module I - requirement for structured quality system documentation
- GVP Module II - pharmacovigilance system documentation requirements
- ICH E2D - requirement for consistent and controlled documentation processes
- MHRA GPvP guidance - expectations for structured documentation
- FDA 21 CFR Part 11 - requirements for controlled electronic documentation
Typical Inspection Questions (What Inspectors Ask)
- How are pharmacovigilance documents created?
- What templates do you use for SOPs and work instructions?
- How are documents numbered and identified?
- How do you ensure consistency across documents?
- Who is responsible for creating and owning documents?
Common failure patterns
What good looks like
- Use of standardised templates for all PV documents.
- Clear and consistent document numbering system.
- Defined authorship and ownership for each document.
- Consistent structure and formatting across documentation.
- Controlled template management supporting document consistency.
How teams operationalise it
- Define standard templates for SOPs, work instructions, and forms.
- Implement a structured document numbering system.
- Assign document owners and authors during creation.
- Ensure all documents follow consistent formatting and structure.
- Maintain control of templates within the document management system.
- Align document creation with PV processes and regulatory requirements.
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 created?
Pharmacovigilance documents are created using controlled templates, defined authorship, and structured processes to ensure consistency, traceability, and compliance.
What is document numbering in pharmacovigilance?
Document numbering is a structured system that assigns unique identifiers to each document to ensure traceability, version control, and easy identification.
What templates are used in pharmacovigilance documentation?
Templates typically include SOP templates, work instruction templates, forms, and controlled document formats that standardise structure and content.
What is a document template in pharmacovigilance?
A document template is a predefined format used to create consistent and compliant documents, ensuring that all required sections, structure, and metadata are included.
Why is standardisation important in document creation?
Standardisation ensures consistency, reduces errors, supports compliance, and makes documents easier to review, audit, and maintain.
What do inspectors check for document creation?
Inspectors check whether documents are created using controlled templates, numbered correctly, owned by defined roles, and consistent across the pharmacovigilance system.
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