- What Counts as a Serious Adverse Event
- The Sponsor's Core Obligations
- SAE Reporting Timelines at a Glance
- What a Well-Structured SAE Report Contains
- Common Mistakes Sponsors Make
- SAE Reporting in First-in-Human Trials: Specific Considerations
- Building an SAE Reporting Plan Before Your Trial Starts
- FAQs
Serious adverse events are a reality of clinical research. How your team responds in the hours and days after one occurs can determine whether your trial stays on schedule, whether your regulatory submission holds up, and whether your relationship with the FDA remains intact.
For startup sponsors running first-in-human studies, the stakes are especially high. You may not have a dedicated safety pharmacovigilance team. Your CRO may be managing the reporting workflow on your behalf. Either way, the sponsor remains legally accountable for every SAE report that goes to the FDA, the ethics committee, and the host country authority.
This article covers what an SAE is, what triggers reporting obligations, what the timelines look like, and what a well-run SAE process actually requires.
What Counts as a Serious Adverse Event
An adverse event is any untoward medical occurrence in a trial participant. An SAE is a specific subset, defined by outcome criteria. Under FDA definitions and ICH-GCP standards, an adverse event qualifies as serious if it results in any of the following:
- Death
- A life-threatening condition
- Inpatient hospitalization or prolongation of existing hospitalization
- Persistent or significant disability or incapacity
- A congenital anomaly or birth defect
- A medically important event that may not meet the above criteria but could jeopardize the participant and require medical or surgical intervention to prevent one of the above outcomes
That last category — "medically important events" — is where sponsor judgment gets tested. It requires real clinical and regulatory expertise to assess correctly, and errors in either direction create problems. Under-reporting exposes you to regulatory action; over-reporting can signal poor protocol design or weak site management.
The Sponsor’s Core Obligations
Sponsors bear primary responsibility for SAE reporting, even when a CRO is handling day-to-day trial operations. FDA regulations under 21 CFR Part 812 (for devices) and 21 CFR Part 312 (for drugs and biologics) make this unambiguous.
Sponsor obligations generally fall into four categories.
1. Receiving and Acknowledging Reports from Sites
Investigators are required to report SAEs to the sponsor promptly — typically within 24 hours of becoming aware of the event. Your trial protocol should define the exact reporting pathway: who the investigator contacts, what form or system they use, and what information must be included in the initial report.
A missing or delayed investigator report does not relieve the sponsor of its own reporting obligations. You are expected to have systems in place to capture SAEs regardless of whether sites report on time.
2. Assessing Causality and Expectedness
Once you receive an SAE report, your medical monitor or safety team must assess two things: whether the event is reasonably related to the investigational product or device, and whether it was anticipated based on the current risk profile documented in your Investigator's Brochure or device description.
An unexpected serious adverse device effect (SADE) in a medical device trial, or an unexpected serious adverse reaction (USAR) in a drug trial, triggers expedited reporting requirements. Expected SAEs still require documentation and submission — just on a different timeline.
3. Reporting to the FDA
For investigational device exemption (IDE) trials, sponsors must report unanticipated adverse device effects (UADEs) to the FDA and all reviewing IRBs within 10 working days of first receiving notice of the effect.
For IND-covered drug and biologic trials, unexpected fatal or life-threatening suspected unexpected serious adverse reactions (SUSARs) must be reported within 7 calendar days. All other unexpected SUSARs go to the FDA within 15 calendar days.
These are not soft targets. Missing a reporting window is a protocol deviation that must itself be documented and may trigger an FDA inquiry.
4. Reporting to Ethics Committees and Local Authorities
Beyond FDA reporting, you must notify the IRB or ethics committee that approved the study. Local requirements in the country where the trial is being conducted also apply.
For trials running in Latin American jurisdictions, this means notifying the relevant national authority alongside the ethics committee. In Panama, that involves MINSA/CNBI. In Chile, ISP/MINSAL. In El Salvador, SRS/CNEIS. Each authority has its own SAE reporting format and timeline requirements — all of which need to be built into your safety management plan before the trial starts.
SAE Reporting Timelines at a Glance
| Event Type | Reporting Deadline |
|---|---|
| UADE (IDE trial, device) | 10 working days to FDA and reviewing IRBs |
| Unexpected fatal/life-threatening SUSAR (IND) | 7 calendar days to FDA |
| All other unexpected SUSARs (IND) | 15 calendar days to FDA |
| Expected SAEs | Per protocol and annual report |
| IRB/ethics committee notification | Per local requirements, typically within 7–15 days |
These timelines run from the date the sponsor first becomes aware of the event — not from when the investigator first observed it. The clock starts the moment information reaches your organization.
What a Well-Structured SAE Report Contains
An incomplete SAE report is nearly as problematic as a late one. The FDA and ethics committees expect the following elements in an expedited report:
- Patient identifiers (coded, not personally identifiable)
- Event description: onset date, duration, severity, and outcome
- Causality assessment: the sponsor's determination of whether the event is related to the investigational product
- Expectedness assessment: whether the event was anticipated based on current risk documentation
- Action taken: whether the protocol was modified, the participant discontinued, or the device retrieved
- Investigator's narrative: the site-level account of what happened
- Sponsor's narrative: the sponsor-level analysis, including any signal implications for the broader study population
For device trials following ISO 14155 architecture, the report structure also needs to align with risk management documentation. An SAE that reveals a failure mode not previously identified in your risk analysis requires a formal update to that analysis — not just a safety report.
Common Mistakes Sponsors Make
Most SAE reporting failures follow a small number of patterns.
Delayed internal escalation. Sites report to the CRO, but internal routing takes two days before the sponsor's medical monitor sees the event. By then, the reporting window is already compressed.
Causality assessed too narrowly. Sponsors sometimes default to "unrelated" assessments to avoid expedited reporting obligations. Regulatory reviewers are experienced at identifying patterns across a trial population, and a string of "unrelated" SAEs that share a mechanism will draw scrutiny.
Inadequate follow-up reporting. An initial expedited report is not the end of the obligation. Follow-up reports must be submitted as new information becomes available, until the event resolves or the outcome is confirmed. Sponsors who file an initial report and then go quiet on a case create audit flags.
Inconsistent definitions across sites. If your protocol does not define SAE criteria precisely, different investigators will apply different thresholds — and you end up with inconsistent safety data that complicates your eventual submission.
No pre-defined escalation path for ambiguous events. Medical monitors need a documented decision tree for events that sit at the boundary of the SAE definition. Without one, each ambiguous case becomes an ad hoc discussion, which slows reporting and introduces inconsistency.
SAE Reporting in First-in-Human Trials: Specific Considerations
First-in-human studies carry a higher baseline uncertainty than later-phase trials. The safety profile of the device or compound is, by definition, not yet established in humans — which means your SAE reporting infrastructure needs to be especially robust from day one.
A few things matter more at the FIH stage than they do later.
Your Investigator's Brochure or device description must be current. Expectedness assessments depend on what your IB documents as known or anticipated risks. An out-of-date IB means you may misclassify expected events as unexpected, or miss the significance of something that should have been flagged.
Your DSMB or Safety Review Committee needs clear SAE triggers. Define in advance what event types or frequencies will prompt an unscheduled safety review or a protocol hold recommendation. Leaving this to judgment in the moment creates delays and inconsistency.
Your evidence package must capture SAE data in a submission-ready format. If your goal is an IDE, 510(k), or PMA submission, the safety data from your FIH study needs to be organized so that FDA reviewers can evaluate it efficiently. An SAE narrative that reads well in a site file but isn't structured for regulatory review will slow your submission.
For sponsors running trials in Latin American jurisdictions, the SAE data also needs to meet FDA's requirements for foreign clinical data under 21 CFR 812.28. That means the safety reporting process must be designed with FDA acceptance in mind from the start — not retrofitted after the trial closes.
bioaccess® structures all FIH-12™ program safety workflows around this requirement. The nine-workstream engagement includes data management and final evidence package delivery specifically designed to produce a submission-ready safety record for the sponsor's next FDA regulatory step — whether that is an IDE, 510(k), De Novo, or PMA. You can learn more at bioaccess®.
Building an SAE Reporting Plan Before Your Trial Starts
The time to design your SAE reporting process is during protocol development — not after your first event occurs. A functional SAE reporting plan addresses the following:
- Definitions: Exact criteria for what constitutes an SAE in your specific trial, including the "medically important events" category
- Reporting pathways: How investigators report to the sponsor, what system or form they use, and what the acknowledgment process looks like
- Internal routing: Who in the sponsor organization receives the report, who performs the causality assessment, and who signs the expedited report to FDA
- Timeline tracking: A system that logs the date the sponsor first became aware of each event and tracks the reporting deadline automatically
- Local authority requirements: Country-specific reporting formats and timelines for each jurisdiction where the trial is running
- Follow-up procedures: Who is responsible for obtaining outcome information and filing follow-up reports
- Annual safety reporting: How individual SAE data rolls up into the annual progress report or Development Safety Update Report (DSUR)
Getting this infrastructure in place before enrollment starts is not a bureaucratic exercise. It protects your participants, protects your data, and protects your regulatory pathway.
FAQs
What is the difference between an adverse event and a serious adverse event?
An adverse event is any untoward medical occurrence in a trial participant, regardless of severity. A serious adverse event meets at least one of a defined set of outcome criteria: death, life-threatening condition, hospitalization, significant disability, congenital anomaly, or a medically important event requiring intervention to prevent a serious outcome. Not all adverse events require expedited reporting; SAEs do.
Who is responsible for SAE reporting in a sponsored clinical trial?
The sponsor holds primary legal responsibility for SAE reporting to the FDA and ethics committees, even when a CRO manages day-to-day operations. The investigator is responsible for reporting SAEs to the sponsor promptly — typically within 24 hours. The sponsor then assesses the event and files the required regulatory reports within the applicable deadlines.
What is the FDA reporting deadline for an unanticipated adverse device effect in an IDE trial?
Sponsors must report unanticipated adverse device effects (UADEs) to the FDA and all reviewing IRBs within 10 working days of first receiving notice of the effect.
Does SAE reporting work the same way in Latin American trial jurisdictions as it does in the US?
The FDA reporting obligations remain the same regardless of where the trial is conducted. In addition, sponsors must comply with the SAE reporting requirements of each host country's national authority. In Panama, Chile, and El Salvador, separate notifications to MINSA/CNBI, ISP/MINSAL, and SRS/CNEIS respectively are required. A well-designed safety management plan accounts for both sets of obligations simultaneously.
Can foreign clinical trial SAE data be used in a US regulatory submission?
Yes, provided the data is collected and documented in accordance with FDA's requirements for foreign clinical data. For device trials, 21 CFR 812.28 governs the acceptance of foreign data. The safety record must be structured to meet FDA review standards — which requires intentional design from the start of the trial, not after the fact.
What happens if a sponsor misses an SAE reporting deadline?
Missing a reporting deadline is a protocol deviation that must be documented and reported. Depending on the severity of the event and the length of the delay, the FDA may issue a clinical hold, request a corrective action plan, or flag the deviation during a pre-submission review. Repeated reporting failures can jeopardize the entire trial program.
How should sponsors handle SAEs that are ambiguous about whether they meet the "serious" threshold?
Your protocol should include a pre-defined decision process for ambiguous events, including escalation to a medical monitor or safety officer. When in doubt, the default should be to treat the event as serious and report it. Over-reporting a borderline event is a far smaller regulatory risk than under-reporting one that later proves significant.
SAE reporting is not a back-office compliance task. It is a core part of how you demonstrate that your trial is being conducted with scientific rigor and participant safety as the priority. Build the infrastructure before your first patient is enrolled, train your sites on the process, and make sure your CRO's safety workflows are designed to produce data that will hold up in a regulatory submission.
If you are planning a first-in-human study and want to understand how SAE reporting fits into a structured trial program, bioaccess® manages the full safety workflow as part of the FIH-12™ engagement.
Leave a Reply