Writing the Executive Summary in a PBRER

Explains what the PBRER executive summary should communicate, why it is usually drafted after the main scientific sections, how to select proportionate content and how to maintain consistency with risk, benefit-risk and conclusions sections.

Take test

Writing the Executive Summary in a PBRER

The Executive Summary gives the assessor a compact view of the completed PBRER. Although it appears near the beginning of the report, it should reflect the final scientific position reached after the detailed evidence, risk evaluation, benefit evaluation and integrated benefit-risk analysis have been completed.

Purpose and Regulatory Framework

The PBRER format is defined by ICH E2C(R2) and implemented in the EU PSUR framework through Commission Implementing Regulation (EU) No 520/2012 and GVP Module VII — Periodic safety update report (Rev. 1).

The Executive Summary is not an independent assessment. It is a concise synopsis of the report's most important context, findings and conclusions. Every important statement in it should be supportable from the detailed sections that follow.

Why the Executive Summary Is Usually Written Last

Writing it too early creates a predictable problem: the summary begins to drive the report rather than reflect it.

The preferred authoring sequence is generally:

complete the scientific sections → finalise risk and benefit evaluation → agree integrated benefit-risk conclusion → draft or revise the Executive Summary.

This reduces inconsistency and prevents preliminary interpretations from remaining in the summary after the detailed assessment has changed.

What the Executive Summary Should Help the Reader Understand

After reading the Executive Summary, an assessor should be able to understand:

The section should not attempt to list everything that appears in the PBRER.

Selection Is a Scientific Task

The difficult part is deciding what deserves space.

A useful inclusion test is whether omitting an item would materially change the reader's understanding of the reporting interval or the final benefit-risk conclusion.

Items often deserving emphasis include:

Routine operational activity, minor label editing, ordinary case volume and low-impact findings generally do not belong unless they are necessary to explain a major conclusion.

Executive Summary Versus Introduction

The Introduction defines the report context. The Executive Summary states what matters about the completed evaluation.

The two should therefore not duplicate one another. Product identity, reporting interval and high-level scope can be stated briefly, but the Executive Summary should quickly move to the scientific developments and conclusions that distinguish this reporting interval from the previous one.

Building the Scientific Narrative

A useful Executive Summary follows the logic of the report rather than the order of every section. A practical sequence is:

  1. brief reporting and product context;
  2. major interval safety developments;
  3. important risk or signal conclusions;
  4. important benefit developments where relevant;
  5. material regulatory or risk-management action; and
  6. the overall benefit-risk conclusion and principal next steps.

This sequence is recommended authoring practice, not a mandatory regulatory template.

Maintaining Balance

Balance does not mean giving equal space to benefits and risks. It means giving each issue weight proportionate to its importance to the overall assessment.

A rare but life-threatening newly identified risk may deserve more attention than several routine positive effectiveness findings. Conversely, important evidence of sustained benefit may need to be included when it materially affects interpretation of an evolving risk.

The summary should neither minimise important harm nor exaggerate uncertain observations.

Calibrating Certainty

Language should match the strength of evidence.

Use wording that distinguishes:

Avoid statements such as “the drug causes” when the detailed report supports only a potential association. Equally, do not describe an established and well-characterised risk as merely “possible” if that understates the evidence.

Numerical Detail

The Executive Summary should use numbers selectively. Include quantitative results when they are essential to understanding a major conclusion, not because the underlying section contains many tables.

For example, a new controlled study showing a clinically important increase in a serious risk may warrant a concise quantitative statement. Long lists of case counts, exposure estimates or study outputs usually belong in the detailed sections.

Signals and Risks

A signal should be included when its status or conclusion matters to the reporting interval.

The summary should make the status clear. Examples include:

The Executive Summary should not turn into a signal tracker.

Regulatory Actions

Significant safety-related actions should be summarised with correct status.

Distinguish between:

This prevents the summary from overstating the regulatory outcome.

Benefit Information

Benefit information deserves inclusion when it changes or materially supports the current benefit-risk evaluation. Routine repetition of historical efficacy results generally adds little value.

Relevant examples may include:

The Benefit-Risk Statement

The final benefit-risk statement should be explicit but not formulaic.

A weak conclusion is:

The benefit-risk balance remains positive.

A stronger conclusion briefly explains why, for example by stating that the newly characterised risk is rare, clinically manageable under revised monitoring, and does not materially alter the established therapeutic benefit in the authorised population.

The detail belongs later in the report, but the logic should still be visible in the summary.

Cross-Section Reconciliation

The Executive Summary should be reconciled against the completed report after substantive medical review. At minimum, compare it with:

A material conclusion should not appear only in the Executive Summary, and a major conclusion elsewhere should not disappear from the summary without a reason.

Illustrative Example

Suppose a PBRER concludes that a previously potential risk of severe pancreatitis is now sufficiently supported to be treated as an identified risk, leading to strengthened warnings, while therapeutic benefit remains unchanged.

A weak Executive Summary might say:

Pancreatitis was reviewed and the benefit-risk balance remains positive.

A stronger summary would state that cumulative case and study evidence supported reclassification of severe pancreatitis as an identified risk; product information was strengthened accordingly; no material change in treatment benefit was identified; and the overall benefit-risk balance remains favourable under the updated conditions of use.

The detailed evidence still belongs in the risk and benefit-risk sections.

Potential Writing Failure Modes

The following are illustrative writing failures, not inspection findings.

Failure mode Why it matters
summary is drafted once at project start preliminary conclusions may survive after the report changes
every PBRER section receives one sentence scientific prioritisation is lost
new evidence appears only in the summary the conclusion is unsupported by the body of the report
important risk change is absent assessor receives an incomplete overview
company proposal is described as regulator-approved regulatory status is misstated
“benefit-risk remains positive” appears without reasoning conclusion becomes formulaic
summary uses stronger causal language than the risk section evidentiary certainty is inconsistent
excessive numbers obscure the major messages summary stops functioning as synthesis

Practical Executive Summary Checklist

  1. Was the summary revised after the scientific sections were finalised?
  2. Does it identify the major interval developments rather than list every section?
  3. Are important signal and risk conclusions represented accurately?
  4. Is benefit information included when relevant to the overall balance?
  5. Are significant regulatory actions described with correct status?
  6. Does language match the strength of evidence?
  7. Are numbers included only when they materially improve understanding?
  8. Does the benefit-risk statement explain the conclusion briefly?
  9. Can each material statement be traced to a detailed section?
  10. Is the summary consistent with Conclusions and Actions?

Relationship With Other QPPV.com PBRER Articles

For the overall structure see [[understanding-the-structure-of-a-pbrer]]. For the regulatory framework see [[pbrer-guide]]. For detailed report authoring see [[how-to-write-a-pbrer]]. The scientific conclusion is developed in [[writing-the-integrated-benefit-risk-evaluation-section-in-a-pbrer]] and translated into action in [[writing-the-overall-conclusion-section-in-a-pbrer]].

Key Takeaways

The Executive Summary is a scientific synopsis of the completed PBRER, not an abbreviated table of contents.

It is usually best drafted or finalised after the detailed risk, benefit and integrated benefit-risk sections are complete.

Selection, balance and calibration of certainty matter more than exhaustive coverage.

The summary should make the most important interval developments and the overall benefit-risk conclusion understandable without introducing evidence or conclusions that are absent from the body of the report.

References

  1. International Council for Harmonisation. ICH E2C(R2): Periodic Benefit-Risk Evaluation Report (PBRER). Step 4, 15 November 2012.
  2. International Council for Harmonisation. ICH E2C(R2) Questions and Answers. Last update 31 March 2014.
  3. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module VII — Periodic safety update report (Rev. 1). EMA/816292/2011 Rev. 1.
  4. European Medicines Agency. Periodic safety update reports (PSURs). Current procedural guidance.
  5. European Union. Commission Implementing Regulation (EU) No 520/2012, as amended.
  6. European Union. Directive 2001/83/EC, as amended.
  7. European Union. Regulation (EC) No 726/2004, as amended.

Regulatory Note

This article explains authoring of the PBRER/PSUR Executive Summary and distinguishes regulatory content expectations from organisation-specific drafting workflows. As of 9 September 2026, GVP Module VII Rev. 1 remains the published EMA module; current procedural guidance should be checked for live submissions.

Revision History

Last reviewed: 2026-09-09

QPPV.com