Determining whether an event requires prompt institutional review board (IRB) reporting is an important part of protecting research participants, supporting effective IRB oversight, and maintaining regulatory compliance. But not every adverse event, deviation, or new piece of safety information requires an immediate submission.
A consistent approach to identifying IRB reportable events can help research teams focus attention on information that meaningfully affects participant rights, safety, welfare, or the study’s risk profile while reducing unnecessary reports.
The checkpoints below provide a practical framework for evaluating common reportable event categories and avoiding frequent reporting mistakes. Organizational policies, the approved protocol, and IRB-specific reporting requirements should always be consulted when making a final determination.
What are IRB reportable events?
IRB reportable events are events or information that meet the reviewing IRB’s criteria for reporting, often because they affect participant safety or welfare, alter the known risks of the research, involve significant deviations or noncompliance, or otherwise require IRB review.
Several related terms may arise when evaluating reportability, including “unanticipated problem” (UP), “serious adverse event” (SAE), and “unanticipated adverse device effect” (UADE). An IRB reportable event is the umbrella determination—the outcome of the reportability analysis itself—while UP, SAE, and UADE are the specific classifications that can lead to that determination. UP is the general standard applied across research types; SAE and UADE are event-type-specific categories—tied to drug/biologic and device studies, respectively—that still have to clear the same unexpectedness, relatedness, and increased-risk criteria before they become reportable. These categories can overlap, but they aren’t interchangeable.
Most importantly, not every safety report or protocol deviation requires IRB submission. Many minor deviations that don’t affect participant safety, or reports that don’t meet the UP or UADE threshold, are submitted unnecessarily. Understanding what not to report to an IRB can be just as important as recognizing what does require prompt submission.
Final reporting decision checklist
Before submitting—or deciding not to submit—a report, research teams can use the following checklist to support a consistent determination:
- Confirm the event category and applicable definition. Determine whether the event is a UP, SAE, UADE, protocol deviation, noncompliance, or another reportable event. Applying the correct definition is the foundation for making a consistent reporting decision.
- Review the protocol, consent form, investigator brochure or device information, and IRB reporting policy. Compare the event against the study’s approved documents and your institution’s reporting requirements. This helps determine whether the event is expected, already known, or meets the criteria for prompt reporting.
- Determine whether the event is unexpected, related or possibly related, and indicative of greater risk. These three questions form the core of most IRB reporting decisions. If the event is unexpected, reasonably related to the research, and suggests participants are at greater risk than previously recognized, it’ll often require prompt IRB review.
- Identify the required reporting timeframe and recipients. Once an event is determined to be reportable, verify applicable submission deadlines and who must receive the report, such as the reviewing IRB, sponsor, U.S. Food and Drug Administration (FDA), or other oversight bodies. Reporting timelines may differ depending on the event type and study.
- Submit a concise description of the event, its impact, and any immediate protective actions. Provide enough information for the IRB to understand what happened, how participants may have been affected, and what actions have already been taken to mitigate risk. Clear, objective reporting helps facilitate timely review.
- Document the rationale when the event is determined not to be promptly reportable. Not every event requires immediate IRB reporting, but the decision-making process should still be documented. Maintaining this rationale supports consistency, transparency, and inspection readiness.
- Track required follow-up, including amendments, reconsent, corrective actions, and additional reports. Reporting an event is often only the first step. Monitor any required follow-up activities—such as protocol or consent updates, CAPAs, participant reconsent, or additional safety reports—to ensure the issue is fully addressed and documented.
A consistent approach to IRB reportable events
IRB reporting should focus on events and information that meaningfully affect participant rights, safety, welfare, or the study’s risk profile. Applying a standardized checklist can help research teams reduce both under-reporting and unnecessary submissions while supporting consistent oversight and documentation.
No checklist replaces study-specific requirements. Research organizations should align their processes with the reviewing IRB’s policies, the approved protocol, and applicable institutional and regulatory requirements, and maintain clear documentation supporting every reportability decision.
