IRB Reportable Events

An IRB reportable event is any occurrence, finding, or piece of new information arising during an already-approved, ongoing human subjects study that federal regulation or an institution’s Human Research Protection Program (HRPP) policy requires the study team to report to the IRB outside the routine continuing-review cycle. Reportable events are about the conduct of an already-approved study — they are a distinct workstream from the initial IRB application and approval process, and they are not the same as a planned protocol amendment: an amendment is a prospective change submitted for approval before it is implemented, while a reportable event describes something that has already happened.

What has to be reported

Reportable events are an umbrella category, not a single regulatory term. In practice, IRBs and HRPP offices group several kinds of occurrences under it:

• Unanticipated problems involving risks to subjects or others (UPIRSOs) — the core federal category under 45 CFR 46 and 21 CFR 56.108(b); see UPIRSO for the three-part test IRBs use to decide whether something qualifies.
• Protocol deviations, particularly those that affect subject safety, subject rights, or data integrity — see Protocol Deviation.
• Adverse events and serious adverse events occurring in the course of the study — see Adverse Event (AE).
• Subject complaints about the conduct of the research or the informed consent process.
• Breaches of confidentiality or data security incidents involving identifiable subject information.
• Non-compliance with the IRB-approved protocol, applicable federal regulations, or institutional policy — whether by the study team or, in a multi-site study, another site.

Typical reporting timelines

Federal regulation sets the reporting duty but generally does not itself impose a fixed day-count. 21 CFR 56.108(b) requires that an IRB have written procedures for prompt reporting to the IRB, appropriate institutional officials, and (where applicable) FDA of unanticipated problems involving risk to subjects or others; 21 CFR 312.66 similarly requires investigators to promptly report unanticipated problems and changes in research activity to the IRB. Neither regulation itself specifies a fixed number of days for that subsequent report (contrast this with an emergency change made under 21 CFR 312.30(b)(2)(ii) to eliminate an apparent immediate hazard, which can be implemented before IRB approval but still requires prompt subsequent notification).

Because the federal text says “promptly” rather than naming a deadline, individual institutions’ HRPP/IRB policies fill in the specific clock — commonly (though this varies by institution and should always be confirmed against the specific IRB’s written policy, not assumed):

• Events posing an immediate risk to subject safety: reported immediately, often by phone or email within 24-48 hours, followed by the formal written report.
• UPIRSOs and reportable non-compliance that do not pose an immediate risk: commonly reported within 5 to 10 business days of the study team becoming aware of the event.
• Reportable protocol deviations that do not rise to the level of a UPIRSO: often logged and reported at the next continuing review, per the specific IRB’s deviation-reporting policy, unless the deviation itself carries a safety implication that triggers the shorter clock.

These day-counts are institutional HRPP policy implementing the federal “prompt reporting” standard, not a uniform number set by 45 CFR 46 or 21 CFR 56 themselves — always check the specific timeline in the reviewing IRB’s own reportable-events policy or reliance agreement (see Central IRB / Single IRB (sIRB) for how reporting responsibilities are allocated when a single IRB of record covers multiple sites).

Who has to report, and to whom

The reporting duty sits with the principal investigator and study team in the first instance. Depending on the event type and the study’s regulatory context, the same event may also need to go to the funding sponsor, FDA (for an IND/IDE-regulated study), the institution’s research integrity or compliance office, and — for multi-site studies under a single IRB of record — the other participating sites, so that the IRB of record can assess whether the event has implications beyond the site where it originated.

Related terms

See also UPIRSO, Protocol Deviation, Adverse Event (AE), Continuing Review (IRB), IRB (Institutional Review Board), and the IRB/REC Approval Process guide for how this fits alongside initial study approval.