Safety Reporting in Clinical Research: Managing Volume and Enabling Meaningful Review

Effective regulatory oversight in clinical research depends on systems that are both compliant and operationally feasible. One area that is especially challenging for research sites is managing safety reporting. While essential to participant protection and study integrity, the volume of reporting has increased significantly in the last decade and the implementation and management varies widely across sponsor organizations.

A recent League Regulatory Working Group discussion explored how different institutions approach this topic, highlighting both common challenges and emerging strategies.

Regulatory Context: Roles and Responsibilities

The FDA guidance documents on Safety Reporting [1, 2] provide important context for safety reporting and notification processes and stakeholder responsibilities. At the same time, FDA regulations do not prescribe specific workflows for the safety reporting process. Instead, the emphasis is on ensuring that safety information is appropriately reviewed and documented by both sites and sponsors.

Figure 1 provides a general overview of the safety reporting workflow across all stakeholders.

Figure 1: This workflow diagram illustrates the end-to-end process for identifying, assessing, reporting, and communicating safety events in a clinical trial. Abbreviations used: Principal Investigator (PI), Serious Adverse Event (SAE), Electronic Data Capture (EDC), Contract Research Organization (CRO), Suspected Unexpected Serious Adverse Reaction (SUSAR), U.S. Food and Drug Administration (FDA), Electronic Submission Gateway (ESG), European Medicines Agency (EMA), Investigator Brochure (IB), Acknowledge (Ack), Institutional Review Board (IRB). Regulatory submissions may be prepared using Council for International Organizations of Medical Sciences (CIOMS) I forms, FDA MedWatch Form 3500A, or International Council for Harmonisation (ICH) E2B electronic reporting standards, depending on jurisdiction and reporting requirements.

Investigator/Site Responsibilities: Adverse Event Reporting and Safety Report Review and Acknowledgement

At the site level, investigators are responsible for timely reporting of adverse events (AEs) and serious adverse events (SAEs) to sponsors, Institutional Review Boards (IRBs) and regulatory authorities, when required. Sites must also review and acknowledge safety notification reports distributed by sponsors and CROs to assess the impact to their ongoing studies and participants, and take any necessary action required. These reporting and review obligations are defined by study protocols, sponsor requirements, IRB requirements, and applicable regulations, and are central to participant safety and ongoing risk assessment. Sites must maintain accurate documentation, adhere to reporting and review timelines, and define and follow escalation pathways for events that may impact participant safety or study conduct. Ensuring consistency in how events are assessed, documented, and reported remains a foundational component of regulatory compliance. However, the volume of AE and SAE reports and safety notifications, especially in complex therapeutic areas, such as oncology, can create significant operational burden.

Variability in Site Processes

The Working Group members described a range of approaches to managing safety notification reports at sites. Some sites require individual principal investigator (PI) signatures for each report, while others implement monthly bulk review and acknowledgment processes. Some organizations track safety reports manually in spreadsheets while others use centralized systems, such as internal databases or electronic investigator site files (eISFs), to track and organize reports.

These differences reflect institutional preferences and interpretations of regulatory expectations, but they also underscore the lack of standardization across sites. Ensuring that safety reports are not only acknowledged but also meaningfully reviewed is a recurring concern. Some sites address this through individual signatures, while others rely on summary documentation or attestations confirming that reports have been reviewed. 

Sponsor Responsibilities: Evaluation and Distribution of Safety Information

Sponsors are responsible for the ongoing evaluation of safety data across all clinical trials involving an investigational product, including the identification of emerging safety signals. This responsibility extends beyond individual adverse event assessment to the identification of patterns that may indicate new or evolving safety risks. Based on this evaluation, sponsors determine whether adverse events meet criteria for expedited reporting to regulatory authorities, including those that qualify as Suspected Unexpected Serious Adverse Reactions (SUSARs) or require submission as IND safety reports in accordance with regulatory requirements.

In addition to regulatory reporting, sponsors are responsible for translating safety findings into broader risk communication. This includes timely distribution of safety reports and safety letters, as well as making updates to the Investigator Brochure (IB) to ensure that new safety information is incorporated and disseminated to all participating investigators. These communications are intended to support site-level awareness, assessment and, where necessary, action for patient safety.

Variability in Sponsor Processes

Members of the Regulatory Working Group reported that there is variability in how sponsors operationalize these safety reporting requirements. There are differences in how sponsors perform signal evaluation, interpret reportable events, and communicate the context and priority of safety information to sites. There is also variability in how sponsors manage and communicate follow-up information, such as the frequency, level of detail, and prioritization information provided in each report. This is particularly notable given that safety reporting is a highly regulated process. 

While safety reporting is highly regulated, these differences in sponsor operational processes can make it difficult for sites participating in multiple studies to establish consistent review practices. Greater consistency in how safety information is communicated could help sites more efficiently assess relevance and determine appropriate next steps.

Challenges with Safety Notification Reporting

Managing the volume and prioritization of safety notification reports was a central topic of discussion. Sites often receive large numbers of reports without clear differentiation between those requiring immediate review or action and those that are primarily informational. Working group members noted that clearer guidance from sponsors, such as indicating report priority, whether acknowledgment is required, and what specific actions are expected, would help support more efficient site-level review.

Participants provided an example in which a single event generated an initial safety report followed by multiple follow-up updates distributed until the case was fully resolved. Each update required review and acknowledgment, contributing to administrative burden without always providing new actionable information. Members noted that clearer prioritization and more consolidated reporting, where feasible, could help sites focus attention on the information most relevant to participant safety.

The group also noted that differences in regulatory requirements and reporting expectations across jurisdictions can add complexity to safety review processes, reinforcing the need for clear communication and alignment between sponsors and sites.

Emerging Best Practices

Despite these challenges, working group members identified several practices that can help sites manage safety reporting more efficiently while maintaining appropriate oversight. These include centralized tracking systems to organize safety reports by study or investigational product, periodic bulk review processes to reduce administrative burden, defined standard operating procedures that clarify responsibilities and timelines, and documentation approaches such as summary logs that demonstrate meaningful review.

Participants also highlighted opportunities for sponsors to improve the effectiveness of safety communications. Clearer prioritization of reports, differentiation between new and follow-up notifications, and explicit guidance regarding required actions and review timelines could help sites focus attention on the information most relevant to participant safety.

Looking ahead, members noted that AI and automation may offer opportunities to support the triage, organization, and review of safety reports, provided that these tools are implemented in a manner that preserves investigator oversight and regulatory accountability. More broadly, the group emphasized the importance of designing safety reporting processes that support meaningful risk assessment and participant protection while enabling sites to focus their attention on the information most relevant to participant safety.

References

1. Investigator Responsibilities — Safety Reporting for Investigational Drugs and Devices. FDA, December 2025.
2. Sponsor Responsibilities — Safety Reporting Requirements and Safety Assessment for IND and Bioavailability/Bioequivalence Studies. FDA, December 2025.