Expedited Safety Reporting in Clinical Trials: The Four-Gate Clock for SAEs, SUSARs, and IND Safety Reports

At a glance

• Run expedited reporting as four sequential gates: discovery, seriousness, causality + expectedness, then the clock. Most inspection findings are not about unknown definitions; they are blown clocks and mis-classified events.
• A serious adverse event (SAE) is not a SUSAR. A SUSAR requires three things at once: serious, a reasonable suspected causal relationship, and unexpected against the reference safety information (RSI) in the Investigator’s Brochure.
• The reporting clock starts at sponsor awareness, not investigator discovery. ICH E2A times the 7- and 15-day clocks from “first knowledge by the sponsor,” and FDA 21 CFR 312.32 times them from sponsor receipt/determination, not from the site visit where the event surfaced.
• Two distinct legs: the investigator reports SAEs immediately to the sponsor with a causality assessment; the sponsor then expedites qualifying cases to the regulatory authority, IRB/IEC, and other investigators.
• FDA diverges from ICH/EU single-case SUSAR logic with a “reasonable possibility” standard and an aggregate-analysis trigger: some serious unexpected events are reportable only when they occur more often in the drug arm than in a control group.
• This is a compliance explainer. Regulations define what you must report and by when; meeting the deadline is the sponsor’s responsibility, and no SOP or system “makes you compliant” on its own.

This guide is written for clinical-ops, PV/drug-safety associates, CRAs, and study-startup leads who own the safety-reporting SOP and need to know whether their day-zero definition and SUSAR classification would survive a BIMO or GCP inspection. It is the operational decision flow, not a glossary. For the upstream and downstream pieces, see the sibling guides on adverse event classification, protocol deviations, and IND/sponsor obligations.

The four gates: discovery, seriousness, causality + expectedness, timeline

Every potentially expeditable event passes through four gates in order. An event that fails a gate stops there; it does not advance to the clock.

1. Discovery — an adverse event is observed and reported to the sponsor.
2. Seriousness — does it meet a seriousness criterion? If no, it is not expeditable.
3. Causality + expectedness — is there a reasonable suspected causal relationship, and is it unexpected against the RSI? Both must be yes for the SUSAR/IND-safety gate to open.
4. Timeline — once the gate opens, the clock runs from sponsor awareness on a 7- or 15-calendar-day deadline.

Event	Gate outcome	Who reports	Deadline
Non-serious AE, related or not	Stops at Gate 2	Investigator to sponsor per protocol	Per protocol, not expedited
Serious, but expected (listed in IB/RSI)	Stops at Gate 3	Investigator (immediate) to sponsor	Not expedited as a single case
Serious, unexpected, not causally related	Stops at Gate 3	Investigator (immediate) to sponsor	Not expedited as a single case
SUSAR: serious + unexpected + reasonable causality, fatal/life-threatening	Passes all gates	Sponsor to authority + IRB/EC + investigators	7 calendar days (ICH/FDA)
SUSAR: serious + unexpected + reasonable causality, not fatal/life-threatening	Passes all gates	Sponsor to authority + IRB/EC + investigators	15 calendar days (ICH/FDA)
Anticipated serious event, frequency imbalance in drug arm (FDA)	Passes via aggregate trigger	Sponsor to FDA + investigators	15 calendar days

Gates 1 and 2: serious adverse event vs adverse event

Gate 1 is pure observation. An adverse event is any untoward medical occurrence in a participant administered the product, whether or not considered related to it; ICH E2A and FDA 21 CFR 312.32(a) both define the adverse event without implying any judgment about causality. Collection of routine non-serious AEs runs on the protocol’s schedule and is out of scope here.

Gate 2 is the seriousness test, and it is an outcome test, not a severity test. Under ICH E2A, a serious adverse event is any untoward medical occurrence that results in death, is life-threatening, requires inpatient hospitalisation or prolongation of existing hospitalisation, results in persistent or significant disability/incapacity, or is a congenital anomaly/birth defect. ICH E2A is explicit that “serious” and “severe” are not synonymous: severity describes intensity, while seriousness is based on patient/event outcome and is what defines regulatory reporting obligations. A severe headache is not serious; a non-severe event meeting an outcome criterion is.

Watch one cross-regulation wrinkle here. ICH E2A treats important medical events as serious when they may jeopardise the patient or may require intervention to prevent a listed outcome. FDA’s definition at 21 CFR 312.32(a) phrases the same clause with “and” (may jeopardise the patient and may require medical or surgical intervention). FDA states it will accept application of either the FDA “and” criteria or the ICH E2A “or” criteria when determining seriousness. State this tension in your SOP rather than smoothing it over: the two texts read differently, and FDA explicitly permits both readings.

Gate 3: the SUSAR test (causality AND unexpectedness against the RSI)

A SUSAR is the convergence of three conditions. ICH E6(R3) defines a Suspected Unexpected Serious Adverse Reaction as an adverse reaction that is suspected, unexpected, and serious. Miss any one and it is not a SUSAR.

Causality. ICH E2A requires a causality assessment for clinical-investigation cases, and any case judged by either the reporting health-care professional or the sponsor to have a reasonable suspected causal relationship qualifies as an ADR. The phrase “reasonable causal relationship” means there are facts or arguments to suggest causation, not certainty.

Expectedness. ICH E2A defines an unexpected adverse reaction as one whose nature or severity is not consistent with the applicable product information, and names the Investigator’s Brochure as the source document for an unapproved product. ICH E6(R3) Appendix A.1.2 makes the operational point: the reference safety information (RSI) in the IB is the reference point for expedited SUSAR reporting, and that list is used to determine expectedness and therefore whether reporting must be expedited. This is where teams quietly go wrong: “expected” means listed in the RSI/IB for this product, not “anticipated for this disease or population.” A stroke in an elderly cohort can be clinically anticipated yet still be “unexpected” for reporting purposes if it is not in the IB.

Dimension	SAE	SUSAR
Seriousness	Yes (meets an outcome criterion)	Yes
Causality	Not required for the SAE label	Reasonable suspected causal relationship required
Expectedness	Not assessed	Must be unexpected against the RSI/IB
Expedited single-case reporting	No (by itself)	Yes, on the 7/15-day clock

Gate 4: when the clock actually starts

The deadlines are well known; the day-zero rule is what teams get wrong. ICH E2A times both clocks from “first knowledge by the sponsor.” Fatal or life-threatening unexpected ADRs must be reported as soon as possible but no later than 7 calendar days after first knowledge by the sponsor that a case qualifies, followed by as complete a report as possible within 8 additional calendar days. All other serious, unexpected ADRs must be filed no later than 15 calendar days after first knowledge by the sponsor that the case meets the minimum criteria for expedited reporting.

FDA frames day zero similarly but bipartitely. Under 21 CFR 312.32, the 15-day clock runs from when the sponsor determines that the suspected adverse reaction or other information qualifies for reporting, while the 7-day clock for an unexpected fatal or life-threatening suspected adverse reaction runs from the sponsor’s initial receipt of the information. FDA also notes that if the report submitted within 7 calendar days is complete, an additional submission within 15 days from day zero is not required.

Clock-start and reset callout. Day zero is sponsor awareness, not the Friday site visit. Picture a non-fatal SUSAR a CRA spots on Friday but that reaches the sponsor’s safety mailbox Monday: the 15-day clock the inspector counts starts Monday. ICH E2A also makes initial reports submittable on minimum criteria (an identifiable patient, a suspect product, an identifiable reporting source, and a serious, unexpected event with a reasonable suspected causal relationship); follow-up information must be actively sought and submitted as it becomes available, so follow-up does not pause the original deadline. Log when the qualifying determination was made and by whom; that timestamp is the record the inspection turns on.

Two legs of the obligation: investigator to sponsor, sponsor to authority/IRB

Expedited reporting is two distinct hand-offs, and conflating them creates gaps.

Leg 1, investigator to sponsor (immediate). ICH E6(R3) section 4.2.7.2 requires that all serious adverse events be reported immediately to the sponsor after the investigator reasonably becomes aware of the event, and that the investigator also include an assessment of causality. Under FDA 21 CFR 312.64(b), except for study endpoints, the investigator must immediately report to the sponsor all serious adverse events regardless of whether the investigator believes they are drug related. Note who does what: FDA states the investigator is not required to determine whether an event is “unexpected”; that is a sponsor responsibility.

Leg 2, sponsor to authority, IRB/IEC, and investigators (expedited). ICH E6(R3) section 3.13.2 directs the sponsor to expedite reporting to the regulatory authority of all SUSARs, in accordance with applicable requirements and ICH E2A, and to assess expectedness against the RSI in the IB. The sponsor must also onward-report SUSARs to investigators/institutions and to the IRB/IEC in a manner reflecting the urgency of action required. ICH E2A’s section on informing investigators and ethics committees points to the same duty: the sponsor keeps the IB’s safety information current so investigators and IRBs/IECs learn of new safety information. Missing the IRB/investigator leg is a common finding even when the authority submission was on time.

FDA divergence: IND safety reports, “reasonable possibility,” and aggregate analysis

FDA’s IND safety reporting under 21 CFR 312.32 starts from the same SAE/SUSAR scaffolding but diverges on two operational points that matter for US INDs.

First, the causality judge. FDA defines a suspected adverse reaction as any adverse event for which there is a reasonable possibility that the drug caused it, where “reasonable possibility” means there is evidence to suggest a causal relationship. FDA assigns the causality determination for IND safety reporting to the sponsor: the sponsor considers the investigator’s causality assessment but submits an IND safety report only for events where the sponsor itself finds a reasonable possibility, regardless of the investigator’s assessment. ICH E2A, by contrast, lets either the reporting health-care professional or the sponsor establish the reasonable suspected causal relationship. State this divergence plainly; do not reconcile it. FDA itself flags that the difference is about who makes the causality judgment.

Second, the aggregate trigger. Beyond single cases, 21 CFR 312.32(c)(1)(i)(C) requires an IND safety report when an aggregate analysis of specific events observed in a clinical trial indicates those events occur more frequently in the drug treatment group than in a concurrent or historical control group. This is the structural difference from EU/ICH single-case SUSAR logic: certain serious, unexpected, anticipated events are not reportable as individual cases because a single case cannot establish reasonable possibility; they become reportable only on the imbalance. (EU single-case SUSAR submission specifics under the EU Clinical Trials Regulation are outside this corpus, so this comparison stays on the FDA-vs-ICH axis rather than asserting EU mechanics.)

Point	ICH E2A / ICH E6(R3)	FDA 21 CFR 312.32
Who judges causality	Reporting HCP or sponsor	Sponsor (considers investigator’s view)
Core single-case trigger	Serious + unexpected + reasonable suspected causality (SUSAR)	Serious + unexpected + reasonable possibility
Fatal/life-threatening deadline	7 calendar days from sponsor’s first knowledge	7 calendar days from sponsor’s initial receipt
Other serious/unexpected deadline	15 calendar days from sponsor’s first knowledge	15 calendar days from sponsor’s determination it qualifies
Aggregate-imbalance trigger	Not a single-case mechanism	Required under 312.32(c)(1)(i)(C)

Where teams get cited

• Blown day-zero clocks. Counting from the investigator’s discovery instead of sponsor awareness. ICH E2A times the clock from first sponsor knowledge and FDA from sponsor receipt/determination; the gap between site discovery and sponsor intake is where deadlines quietly slip.
• Mis-coded non-SUSARs. Treating “serious” as sufficient, or treating “anticipated for the population” as “expected.” Expectedness is judged against the RSI/IB, and under FDA’s aggregate logic some anticipated serious events are not single-case reportable at all.
• Missing the IRB/investigator leg. Submitting to the authority on time but not onward-reporting SUSARs to the IRB/IEC and participating investigators, which ICH E6(R3) section 3.13.2 requires.
• Letting follow-up pause the clock. ICH E2A wants the initial report on minimum criteria within the deadline, with follow-up sought actively afterward; waiting for a “complete” case is a finding.

None of this is about software certifying compliance. A reporting system can enforce a timestamp and route a case, but the sponsor remains responsible for the qualifying determination and the deadline. Treat the four gates as your audit trail: record what was decided at each gate, by whom, and when.

Sources

• ICH E2A — Clinical Safety Data Management: Definitions and Standards for Expedited Reporting (Step 4, 27 October 1994) — https://database.ich.org/sites/default/files/E2A_Guideline.pdf
• ICH E6(R3) — Good Clinical Practice (2025) — https://www.ich.org/page/efficacy-guidelines
• FDA Guidance for Industry and Investigators — Safety Reporting Requirements for INDs and BA/BE Studies (December 2012; 21 CFR 312.32) — https://www.fda.gov/regulatory-information/search-fda-guidance-documents/safety-reporting-requirements-inds-and-babe-studies