A Periodic Benefit-Risk Evaluation Report (PBRER) is a harmonized aggregate safety document mandated by the ICH E2C(R2) guideline, submitted by the Marketing Authorization Holder (MAH) to global regulators at defined intervals. Its core function is to present a cumulative, critical analysis of all new and existing safety information for a medicinal product, integrated with an evaluation of its therapeutic benefits within approved indications.
Glossary
Periodic Benefit-Risk Evaluation Report (PBRER)

What is a Periodic Benefit-Risk Evaluation Report (PBRER)?
A comprehensive, standardized aggregate safety report submitted by marketing authorization holders to regulators, providing an evaluation of new and cumulative safety data alongside a critical benefit-risk analysis of the product.
The PBRER replaces the older Periodic Safety Update Report (PSUR) format, shifting the focus from a purely safety-centric summary to a holistic benefit-risk assessment. It requires the MAH to integrate data from multiple sources—including Individual Case Safety Reports (ICSRs), clinical trials, and published literature—to determine if the favorable benefit-risk profile remains unchanged or if regulatory action is necessary to protect public health.
Key Characteristics of the PBRER
The Periodic Benefit-Risk Evaluation Report is a structured, cumulative safety document mandated by ICH E2C(R2). It moves beyond simple line listings to provide a critical, integrated analysis of new safety information within the context of therapeutic benefit.
Cumulative Safety Analysis
Unlike interval reports, the PBRER analyzes the cumulative safety experience of a product since its international birth date. This longitudinal view is critical for detecting slow-onset signals or changes in adverse event patterns that are invisible in short-term snapshots. The analysis integrates data from clinical trials, spontaneous reports like ICSRs, and published literature to provide a holistic safety profile.
Integrated Benefit-Risk Assessment
The defining feature of the PBRER is the mandatory, explicit evaluation of benefit versus risk. This section requires the Marketing Authorization Holder to critically weigh the product's therapeutic efficacy against its updated safety profile for each approved indication. The analysis must consider the seriousness of the adverse events, the severity of the treated condition, and the availability of alternative therapies.
Reference Information Compliance
The report relies on strict adherence to Reference Safety Information (RSI) , typically the company core safety data sheet. The determination of an adverse event's expectedness against the RSI is a fundamental regulatory act. Events that are both unexpected and serious require expedited reporting, while the PBRER contextualizes their cumulative impact on the product's overall safety specification.
Signal and Risk Evaluation
A dedicated module summarizes all safety signals, both closed and under evaluation, since the last report. It details the results of disproportionality analyses from databases like FAERS and EudraVigilance, and describes the validation process. The report must clearly state whether new signals constitute identified risks, potential risks, or missing information, directly updating the product's Risk Management Plan.
Structured Global Format
The PBRER follows a rigid, internationally harmonized format defined by the ICH E2C(R2) guideline. Key sections include:
- Worldwide Marketing Authorization Status: A global regulatory overview.
- Actions Taken for Safety Reasons: A log of label changes or market withdrawals.
- Cumulative Exposure Data: Quantifying patient use from clinical trials and post-marketing settings.
- Data in Summary Tabulations: Structured presentations of cumulative serious adverse events from clinical trials.
Periodicity and Submission Triggers
The submission frequency is determined by the product's regulatory lifecycle and local requirements, often every 6 or 12 months. A PBRER is also triggered by ad-hoc requests from regulators. The Development International Birth Date (DIBD) anchors the clock for all periodic reports, ensuring synchronized data lock points across global submissions to prevent fragmented safety evaluations.
Frequently Asked Questions
Clear, technical answers to the most common questions about the structure, regulatory requirements, and strategic purpose of the Periodic Benefit-Risk Evaluation Report.
A Periodic Benefit-Risk Evaluation Report (PBRER) is a comprehensive, standardized aggregate safety report submitted by marketing authorization holders (MAHs) to global regulators. It provides a critical evaluation of new and cumulative safety data alongside a formal benefit-risk analysis of the product. The PBRER is the direct successor to the Periodic Safety Update Report (PSUR), as defined by the ICH E2C(R2) guideline.
The key distinction is scope: the legacy PSUR focused almost exclusively on a summary of new safety information. The PBRER expands this mandate to include a structured, critical benefit-risk assessment. This requires the MAH to integrate efficacy and effectiveness data alongside safety signals, explicitly weighing the product's therapeutic value against its cumulative risk profile. The PBRER also places greater emphasis on cumulative data, not just the reporting interval, and requires a detailed evaluation of signal management activities and risk minimization effectiveness.
PBRER vs. Other Aggregate Safety Reports
Key distinctions between the PBRER and other mandatory periodic safety reports submitted to global regulators.
| Feature | PBRER | DSUR | PSUR |
|---|---|---|---|
Primary Focus | Benefit-risk evaluation | Safety of investigational drug | Safety of marketed drug |
Scope of Data | Cumulative and interval | Annual cumulative | Interval (usually 6-12 months) |
Benefit Assessment Required | |||
Applicable Product Stage | Marketed (post-authorization) | Clinical development (investigational) | Marketed (legacy format) |
Reference Safety Information | Company Core Data Sheet (CCDS) | Investigator's Brochure (IB) | Company Core Data Sheet (CCDS) |
Regulatory Guideline | ICH E2C(R2) | ICH E2F | ICH E2C(R1) (superseded) |
Submission Frequency | Every 6-12 months or upon request | Annually | Every 6-12 months |
Integrated Risk Characterization |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
The PBRER is a cornerstone of aggregate safety reporting. Mastery of these interconnected concepts is essential for constructing a compliant and scientifically rigorous benefit-risk evaluation.
Development Safety Update Report (DSUR)
The annual aggregate safety report submitted during the clinical trial phase, distinct from the post-market PBRER. The DSUR focuses on safety signals emerging from ongoing interventional trials, providing an annual analysis of new safety information and the status of the clinical development program. It serves as the investigational counterpart to the periodic post-marketing report.
Reference Safety Information (RSI)
The definitive list of expected adverse reactions against which seriousness and expectedness are judged during PBRER compilation. For post-market products, this is typically the Company Core Data Sheet (CCDS) . Determining whether an event is 'listed' or 'unlisted' in the RSI is the critical first step in identifying a potential new safety signal requiring expedited or aggregate analysis.
Cumulative Summary Tabulation
A mandatory PBRER appendix presenting a line listing of all serious adverse events reported since the drug's global development inception. This tabulation is not merely a data dump; it requires rigorous deduplication against the company safety database to ensure each case is counted only once, providing the reviewer with a transparent, unaggregated view of the cumulative safety data underpinning the report's analysis.
Benefit-Risk Characterization
The culminating section of the PBRER where the marketing authorization holder provides a critical, integrated evaluation of the product's benefits versus its risks. This is not a simple ratio but a qualitative and quantitative argument that weighs efficacy in the target population against the severity, frequency, and reversibility of identified and potential risks, often structured around the BRAT (Benefit-Risk Action Team) framework.
Signal Evaluation in PBRER
The PBRER is a primary vehicle for presenting the results of signal validation and evaluation. For each new or changing safety signal detected since the last report, the PBRER must summarize the signal, present the cumulative data, and provide a preliminary assessment. This transforms the report from a static data compilation into a dynamic risk management tool that informs regulatory decision-making.
Post-Market Exposure Data
An essential component of the PBRER's global marketing authorization status module. This section quantifies patient exposure using robust metrics like patient-years of exposure derived from sales data, prescription audits, and patient registries. Accurate exposure estimation is critical for contextualizing the incidence of reported adverse events and calculating meaningful reporting rates.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us