In a start-up, pharmacovigilance is sometimes treated as an operational service that can be added once the clinical programme becomes larger. Instead, the safety operating model should be designed before the first participant is exposed. A young company does not need to recreate the infrastructure of a multinational pharmaceutical organisation. It does need clear accountability, reliable case-handling processes, fit-for-purpose technology, trained people, documented oversight and a route for escalating clinically important information. ICH E6(R3) is explicit that activities may be transferred to service providers, but ultimate responsibility for sponsor activities remains with the sponsor and important outsourced activities require appropriate oversight.1
What should exist before first-in-human dosing?
Before the first participant is dosed, one would expect the sponsor to be able to answer a small number of basic questions without hesitation: where will safety information arrive, who will assess it, how will expedited cases be submitted, who makes the medical decisions to identify new safety issues and mitigate them, how will important safety findings be escalated, and how will the company demonstrate control over outsourced work?
Named safety accountability
A medically and operationally credible safety lead, with defined decision rights, escalation routes and back-up arrangements.
Regulatory reporting map
Country- and study-specific responsibilities for SAE intake, SUSAR/IND safety reporting, investigator notifications and annual safety reporting.
Case-handling process
A continuously available route for receipt of serious safety information, medical review, follow-up, expectedness/causality assessment, reporting and reconciliation.
Fit-for-purpose technology
A validated sponsor or vendor safety system that supports coding, audit trails, reporting, reconciliation and the electronic formats required for the programme.
Core quality documents
A proportionate SOP set, training records, safety management plans and agreements that define hand-offs with CROs, vendors and development partners.
Safety governance
A defined review cadence for clinically important cases, emerging risks, AESIs, aggregate trends, protocol/IB implications and escalation to senior governance.
ICH E2A remains the core international reference for definitions and expedited reporting principles during clinical development, while ICH E2F provides the common structure for the Development Safety Update Report (DSUR).23 In the United States, 21 CFR 312.32 requires sponsors to promptly review safety information and report qualifying serious risks, including serious and unexpected suspected adverse reactions and certain important findings from other studies, analyses, animal or in-vitro testing.4 In the EU, the Clinical Trials Regulation sets out sponsor obligations for SUSAR reporting and annual safety reporting.7
Important US systems update for 2026
For applicable commercial INDs, from 1 April 2026 FDA requires electronic submission of IND safety reports for serious and unexpected suspected adverse reactions under 21 CFR 312.32(c)(1)(i) to the FDA Adverse Event Monitoring System (AEMS), using E2B(R3) via the supported submission routes. This should be factored into safety-database and vendor decisions early, not treated as a late technical project.56
A phase-appropriate PV roadmap
The capability should expand because the safety questions become more complex—not because a particular headcount milestone has been reached. The practical roadmap below is therefore based on what the sponsor must be able to decide and demonstrate at each stage.
Regulatory mapping, safety lead, vendor/database strategy, core SOPs, reporting pathways, safety agreements, medical review conventions, training and governance.
Reliable SAE intake and follow-up, expedited reporting, QC, investigator communication, reconciliation, issue escalation, vendor metrics and regular sponsor review.
DSUR ownership, structured aggregate review, AESI surveillance, laboratory and exposure trends, DMC/IDMC inputs where applicable, stronger data interfaces and a more mature QMS.
Scale case volume, medical review capacity, partner oversight, signal evaluation, aggregate reporting, audit/inspection readiness and submission-oriented safety analyses.
CTD Module 2.7.4, integrated safety analyses/ISS where applicable, benefit–risk evaluation, proposed labelling, RMP planning for the EU and readiness for regulatory questions.
Market intake routes, literature, medical information interfaces, product-quality complaints, local responsibilities, postmarketing case submission, signal management, periodic reporting and regulatory commitments.
Outsource execution, not accountability
For most small companies, outsourcing is entirely sensible. Case processing, literature surveillance, database hosting, regulatory submission, aggregate-report production and even elements of signal analytics can all be performed by capable external providers. The mistake is to treat the contract as the control system.
What may be outsourced
- Case receipt and processing
- Database operations and submissions
- Literature screening
- Medical review support
- Aggregate report production
- Signal analytics and data preparation
What the sponsor must still control
- Safety strategy and risk tolerance
- Important medical judgements
- Escalation and governance
- Vendor qualification and oversight
- Cross-functional safety decisions
- Evidence that issues were recognised and acted upon
ICH E6(R3) now states this in particularly clear terms: the sponsor retains ultimate responsibility, should have access to information such as relevant SOPs and performance metrics, and should ensure appropriate oversight of important activities transferred to service providers, including further subcontracting.1 For a start-up, that means the oversight model needs to be visible in practice—through metrics, reconciliations, issue logs, meeting minutes, deviation/CAPA follow-up and documented safety decisions—not simply described in an SDEA or scope of work.
Case processing is necessary, but it is not safety surveillance
A company can process every SAE on time and still have a weak pharmacovigilance system. Individual case compliance answers one question: did we handle the report correctly? Safety surveillance asks a different question: what do these cases, together with the rest of the evidence, mean for participants and for the development programme?
As exposure grows, review should become increasingly integrated. Case narratives need to be considered alongside laboratory patterns, AESIs, dose and exposure, protocol deviations, non-clinical findings, class effects, literature, external databases where appropriate, DMC/IDMC outputs and emerging efficacy information. The output should not merely be a list of events; it should support decisions about the protocol, Investigator's Brochure, informed consent, risk minimisation, monitoring, dose selection and the overall benefit–risk assessment.
Launch readiness should begin during Phase 3, not after approval
The commercial pharmacovigilance system is not a new system that appears on the day of authorisation. It is the development safety system expanded to cope with marketed-product reality: spontaneous reports, literature, patient-support programmes, medical information, digital channels, product-quality complaints, partners, local affiliates, periodic reporting, signal management, risk minimisation and regulatory commitments.
The EU makes this pre-authorisation expectation especially tangible. A marketing-authorisation application includes a summary of the applicant's pharmacovigilance system in Module 1.8.1, including evidence that a QPPV is available and a reference to the PSMF location; the applicant is expected to describe the system that will be in place and functioning at the time the marketing authorisation is granted and the product is placed on the market.10 EMA's GVP framework and the current EU implementing regulation provide the operational architecture for the post-authorisation system.89
In the United States, the regulatory architecture is different: there is no directly equivalent pre-approval QPPV/PSMF submission requirement. Nevertheless, the company must be operationally ready for postmarketing reporting obligations once approval is granted; 21 CFR 314.80 sets out the core adverse-drug-experience reporting requirements for approved drugs.11
A pragmatic PV start up plan
If a company has a clinical programme underway but only a skeletal safety structure, one should prioritise control before complexity. The first steps should be to create evidence that the sponsor understands its obligations, can receive and assess safety information, can report on time and can oversee the parties acting on its behalf.
Step 1: assess and design
- Map studies, countries, products and reporting obligations.
- Confirm sponsor/Vendor/CRO responsibilities and escalation.
- Gap-assess the database, intake routes and existing SOPs.
- Identify immediate compliance or participant-safety risks.
Step 2: implement and train
- Activate reliable intake, review and reporting workflows.
- Finalise critical SOPs, plans and safety agreements.
- Train internal teams, sites and providers on hand-offs.
- Start formal reconciliation, QC and governance meetings.
Step 3: demonstrate control
- Run the first full oversight and metrics cycle.
- Test escalation, deviations and CAPA follow-through.
- Check that inspection evidence is retrievable.
- Set the next-stage PV roadmap, resources and budget.
Warning signs that the PV model is too immature
“The CRO owns safety.”
A provider may perform the work. The sponsor still needs the information, expertise and governance required to oversee it.
“We will build the QMS before Phase 3.”
Core procedures, training, deviations and document control are needed while the early programme is running, not retrospectively.
“Signal detection starts after launch.”
Structured safety surveillance begins during development; the methods should become more systematic as exposure and data complexity increase.
“The database can wait.”
The technology can be outsourced, but the company still needs a validated, auditable and reportable system appropriate for its jurisdictions and submissions.
“Submission is a regulatory-writing exercise.”
The safety sections of an application are the culmination of years of surveillance, case evaluation, aggregate analysis and documented risk decisions.
“Commercial PV begins at approval.”
EU PV-system information is already part of the marketing-authorisation application, and global launch processes need time to qualify, test and train.
The practical endpoint
For a start-up, the right PV model is not defined by the number of employees or the number of SOPs. It is defined by whether the company can make the right safety decision at the right time, meet its reporting obligations, explain who was accountable, and produce the evidence that shows how the decision was reached.
Build the system in layers. Keep it proportionate. But build the parts that protect participants and preserve sponsor control before you need them.
Regulatory references and further reading
The links below point to primary regulatory or ICH sources. They are useful anchors, but they are not an exhaustive list of country- or product-specific requirements.
- ICH E6(R3): Good Clinical Practice — sponsor responsibility, service-provider agreements, oversight and quality management.
- ICH E2A: Clinical Safety Data Management — Definitions and Standards for Expedited Reporting.
- ICH E2F: Development Safety Update Report.
- 21 CFR 312.32 — IND safety reporting.
- FDA: IND Application Reporting — IND Safety Reports.
- FDA: Providing Regulatory Submissions in Electronic Format — IND Safety Reports.
- Regulation (EU) No 536/2014 on clinical trials — see in particular Articles 41–43 on safety reporting.
- EMA: Good Pharmacovigilance Practices (GVP) — including Modules I, II, V, VI, VII and IX.
- Commission Implementing Regulation (EU) No 520/2012 — current consolidated text on the performance of pharmacovigilance activities.
- EMA: Pre-authorisation guidance — pharmacovigilance system requirements, including the Module 1.8.1 pharmacovigilance-system summary, QPPV and PSMF information.
- 21 CFR 314.80 — Postmarketing reporting of adverse drug experiences.