Regulatory Jobs

Six-Monthly Deadlines, No Extensions: Inside Pharmacovigilance Aggregate Reporting

What it takes to write a PBRER or DSUR: the data sources, the fixed reporting clock, and the career path behind pharmacovigilance aggregate reporting work.

Connor Griggs

Connor GriggsMSRACQA

Founder & Editor-in-Chief

8 min read

Introduction

Every approved drug carries an invisible paperwork obligation that never expires: somebody has to keep proving, on a fixed schedule, that its benefit-risk balance still holds up. That obligation is called aggregate safety reporting, and it is one of the more deadline-driven corners of pharmacovigilance work. Unlike the case-by-case triage that happens when a single adverse event report comes in, aggregate reporting asks a different question: looked at across six months, a year, or several years of real-world use, does this product's safety profile still look the way the label says it does?

The people who answer that question — periodic report writers, aggregate report scientists, safety physicians, sometimes titled PV medical writers — sit at a point where clinical judgment, data wrangling and hard regulatory deadlines all converge. It is a less visible job than clinical research or regulatory submissions work, but it is one almost every marketed drug depends on, and it draws people from clinical, regulatory, biostatistics and medical writing backgrounds who want work that is equal parts analysis and argument.

What Counts as an Aggregate Report

Individual case safety reports — the single adverse event narratives that get triaged, coded and entered into a safety database — are the raw material. Aggregate reports are the finished product: a periodic synthesis across all of that raw material for a given product, over a given interval. The two main formats a working PV professional will meet are the Periodic Benefit-Risk Evaluation Report (PBRER), harmonized internationally under ICH E2C(R2) and still often called a PSUR out of habit in parts of the industry, and the Development Safety Update Report (DSUR) under ICH E2F, which covers investigational products still in clinical trials rather than marketed ones.

A PBRER is not a list of adverse events with totals attached. It is a structured argument: here is the cumulative safety experience, here is what has changed since the last report, here is our evaluation of any emerging signals, and here is our conclusion about whether the benefit-risk balance remains favorable. A DSUR does the same work for a product still under development, anchored to the investigational new drug application rather than a marketing authorization.

The Reporting Clock That Never Stops

Every product has an international birth date — the date of its first marketing authorization anywhere in the world — and that date anchors the reporting cycle. Newly approved products typically report every six months for the first couple of years, then annually, then on a longer cycle such as every three years once the safety profile is considered well characterized; regulators can also set a different cadence through an agreed risk management plan. DSURs for investigational products run annually from the development international birth date, independent of what happens with the marketing application.

None of these dates move for convenience. Each report has a data lock point — the cutoff after which no further safety data is included in that cycle's report — and a fixed number of days to prepare, review, approve and submit the finished document afterward. Missing that window is not a paperwork inconvenience; it is the kind of compliance gap that shows up in inspection findings and, repeated, in regulatory correspondence. The job runs on that clock in a way few other PV roles do.

Where the Data Actually Comes From

Writing the report is the visible part of the job. Assembling what goes into it is the larger share of the actual work. A report author pulls cumulative case counts and seriousness classifications from the company's safety database, literature search results covering the reporting interval, data from ongoing and completed clinical trials, and — depending on the product — manufacturing and quality complaint data where a complaint turned out to be linked to a safety event. None of these sources live in one system, and reconciling them against each other, so the numbers in the report actually match what is in the underlying systems, is where a surprising amount of the timeline gets spent.

That reconciliation work also means the role is cross-functional by necessity. A report author routinely pulls information from biostatistics for trial-derived safety data, from regulatory affairs for the current status of approvals and label language in each market, from clinical teams for study-level context, and sometimes from quality for complaint-linked events. Getting those handoffs to happen on schedule, repeatedly, across every market a product is approved in, is as much a part of the job as the writing itself.

Writing the Benefit-Risk Narrative

The section of an aggregate report that actually gets read closely by regulators is the signal evaluation and benefit-risk conclusion — the part where counting adverse events stops and clinical reasoning starts. Did the rate of a particular event change meaningfully against what would be expected from the underlying patient population? Does a cluster of cases in the literature, taken together with company data, suggest something worth investigating further as a safety signal? If a new risk was identified during the period, what is being done about it — a label update, additional risk minimization measures, a dedicated study?

Getting that section right takes more than summarizing a spreadsheet. It takes the ability to read a stack of individual case narratives, decide which details actually matter clinically, and write a conclusion that a regulator, a company safety committee and, eventually, a prescriber relying on the label can all trust was reasoned through rather than just tabulated.

Who Does This Work, and How They Get There

People land in aggregate reporting from several directions. Some come up through case processing and signal management within pharmacovigilance and move into report writing once they know the safety database and the company's products well. Others arrive from clinical research or clinical data backgrounds, drawn by work that still involves patient-level reasoning but runs on a steadier internal schedule than a trial site. A smaller number come from medical writing, bringing the structured-document discipline and comfortable with ICH-format templates, and build the safety-specific clinical judgment on the job. Safety physicians — MDs who specialize in pharmacovigilance — typically lead the medical evaluation and sign off on the benefit-risk conclusion, with PV scientists and dedicated aggregate report writers doing much of the drafting and data assembly underneath them.

This is a distinct discipline from regulatory affairs, even though the two teams work closely together — regulatory affairs manages where and how the report gets filed and what it means for a product's approval status, while pharmacovigilance owns the safety content and the clinical argument inside it.

The Tools of the Trade

Most companies run their case data through a dedicated safety database — Oracle Argus Safety and ArisGlobal LifeSphere are the two most widely used platforms in the industry — and an aggregate report author needs to be comfortable pulling and interpreting line listings and summary tabulations out of whichever system their company runs. Beyond the database, the job leans on the ICH E2C(R2) and E2F templates themselves, company-specific standard operating procedures for report content, and a working familiarity with the product's current reference safety information, since one of the report's jobs is comparing observed events against what the label already says is expected.

Skills That Set People Apart

Technical pharmacovigilance knowledge gets someone in the door, but what distinguishes a strong aggregate report author is the ability to hold a large, messy dataset in their head long enough to find the pattern worth writing about, then explain that pattern clearly enough that a reviewer who was not in the data all along can follow the reasoning. Cross-functional coordination matters just as much: chasing down a biostatistics output or a complaint record on a fixed deadline, repeatedly, across every product in a portfolio, is a real and underrated skill. And because the format is internationally standardized but regulators still read the content closely, precision with the ICH templates — what goes in which section, what level of detail a benefit-risk conclusion needs — separates people who produce reports regulators accept without query from people whose reports keep coming back with questions.

Career Path and Where It Leads

Aggregate reporting tends to be a few years' specialization rather than a permanent destination, though plenty of people build long careers in it as reports become more senior and portfolios grow. From here, the common next moves are into signal management and broader safety surveillance leadership, into a Qualified Person for Pharmacovigilance (QPPV) track in companies with European operations, or sideways into regulatory affairs roles that benefit from someone who already understands how safety data and submission timelines interact. The deadline discipline and cross-functional fluency the role builds transfer well in any of those directions.

Conclusion

Aggregate safety reporting rarely gets the visibility of a first-in-human trial or a new drug approval, but the obligation it fulfills — proving, on a schedule that does not bend, that a marketed product's risk profile still matches what regulators and patients were told — is one of the quieter load-bearing functions in the industry. For someone who wants pharmacovigilance work that combines real clinical reasoning with a steady, predictable rhythm rather than the unpredictability of case intake, it is worth a closer look, and it is a role companies are consistently trying to fill well.

Regulatory & Quality. REWIRED.

New roles. Real pay. Your next move.

  • Hand-picked roles, every week.
  • The newest company pages.
  • One article worth your time.
Get the Weekly

Free. Thursday mornings. One-click unsubscribe.

Connor GriggsConnor Griggs

About the author

Connor GriggsMSRA, CQA

Founder & Editor-in-Chief

Connor began his career as a regulatory analyst at the FDA and has spent 13 years in medical device regulatory affairs and quality.

Find your next regulatory or quality role

Every role on Regulatory Jobs is in regulatory, quality or clinical, in pharma, biotech or medical devices. Set an alert and the next one reaches you the day it posts.

Next in Role ProfilesBefore the Inspector Walks In: Running a Site's Internal GMP Audit Program