The short version
What teams need to understand
- Pharmacovigilance systems must continuously monitor regulatory sources across global and local territories.
- Monitoring must include health authorities, regulatory agencies, guidance publications, and industry sources.
- Regulatory intelligence signals must be identified, screened, and validated for relevance.
- Monitoring responsibilities must be clearly assigned across global and local roles.
- Monitoring must be performed at defined frequencies to ensure timely identification of changes.
- Inspection-ready evidence must demonstrate that regulatory changes are systematically identified and not missed.
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.
- Regulatory sources must be continuously monitored.
- Monitoring must cover all relevant territories.
- Regulatory changes must be identified promptly.
- Monitoring responsibilities must be clearly assigned.
- The organisation must demonstrate that no critical regulatory updates are missed.
Why it matters
What this means in practice
Inspectors assess whether pharmacovigilance systems actively monitor and identify regulatory changes. They review source coverage, monitoring processes, responsibility assignment, and evidence that relevant regulatory updates are consistently captured and logged.
Questions this page answers
Inspection evidence
Evidence teams should be able to show
Regulatory Monitoring Process
- Defined monitoring procedures within SOP
- Assigned responsibility for monitoring sources
- Defined monitoring frequency (daily, weekly, monthly)
- Documentation of monitoring activities
Regulatory Sources and Coverage
- Global authorities such as FDA, EMA, MHRA, PMDA, Health Canada
- Local country-specific regulatory authorities
- ICH guidelines and international standards
- Industry publications and regulatory intelligence services
Territory Monitoring Framework
- Defined list of countries and regions monitored
- Assignment of local affiliate responsibility
- Coverage of key PV markets and emerging regions
- Documentation of source review by territory
Regulatory Intelligence Signal Identification
- Identification of new or updated regulations
- Capture of regulatory intelligence signals
- Initial classification of relevance
- Documentation of identified updates
Screening and Validation Records
- Filtering of relevant versus non-relevant updates
- Validation of regulatory information accuracy
- Escalation of uncertain or complex updates
- Documentation of screening decisions
Regulatory Basis (Primary Sources)
- GVP Module I - requirement for maintaining compliance with regulatory obligations
- GVP Module VI - requirement to align safety processes with regulatory requirements
- ICH E2E - proactive monitoring of regulatory expectations
- MHRA GPvP guidance - expectations for awareness of regulatory changes
- FDA pharmacovigilance guidance - requirement to comply with evolving regulatory requirements
Typical Inspection Questions (What Inspectors Ask)
- How do you monitor regulatory changes?
- What sources do you use to identify updates?
- How do you ensure global and local coverage?
- Who is responsible for monitoring regulatory intelligence?
- How do you confirm that no updates are missed?
Common failure patterns
What good looks like
- Defined and documented regulatory monitoring process.
- Comprehensive coverage of global and local sources.
- Clear assignment of monitoring responsibilities.
- Consistent identification and capture of regulatory updates.
- Evidence of timely detection of regulatory changes.
How teams operationalise it
- Define monitoring processes within regulatory intelligence SOP.
- Assign responsibility for monitoring global and local sources.
- Establish a list of key regulatory authorities and sources.
- Perform monitoring at defined frequencies.
- Capture regulatory intelligence signals as they are identified.
- Validate and escalate relevant updates for further assessment.
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 do companies monitor regulatory changes in pharmacovigilance?
Companies monitor regulatory changes by reviewing global and local authority websites, guidance publications, industry sources, and regulatory intelligence tools on a defined schedule.
What is a regulatory intelligence signal?
A regulatory intelligence signal is a newly identified or updated regulatory requirement that may impact pharmacovigilance processes and requires further assessment.
What sources should be monitored for regulatory intelligence?
Sources include health authorities such as FDA, EMA, MHRA, PMDA, local regulatory agencies, ICH guidelines, and industry publications.
Do inspectors review regulatory monitoring processes?
Yes. Inspectors assess whether monitoring processes are structured, consistent, and effective in identifying regulatory changes.
How often should regulatory monitoring be performed?
Monitoring frequency depends on the source, but key authorities are typically reviewed regularly (e.g., weekly or monthly) to ensure timely identification of updates.
How do you ensure regulatory changes are not missed?
By maintaining defined monitoring processes, assigning responsibilities, covering all relevant sources, and documenting monitoring activities.
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 VI
View source
FDA
FDA Postmarketing Safety Reporting
View source
ICH
ICH E2E Pharmacovigilance Planning
View source
MHRA
Good Pharmacovigilance Practice (GPvP)
View source