What Is an Adverse Event (AE) vs. a Serious Adverse Event (SAE)?

There are a lot of safety considerations and reporting requirements in clinical research. One such is recognizing and reporting adverse events (AEs) vs serious adverse events (SAEs). These terms are very similar but mean different things and trigger different reporting requirements. Understanding the distinction between the two is important for reporting and ensuring study participant safety and oversight. 

Here we break down both terms in plain language, provide guidance on classification decisions, and explain what happens after an event is identified.

What Is an Adverse Event (AE)?

An adverse event is any unfavorable and unintended sign, symptom, or medical condition that occurs in a study participant after they've started receiving a study treatment or intervention. Regardless of whether the AEs is believed to be related to the treatment it is still associated with the trial and must be documented and reported according to clinical trail best practices such as following ALCOA-C. 

That last part comes as a surprise to those new to clinical research. It is important to understand that an AE does not have to be caused by the study investigational product (IP). A headache, a rash, elevated blood pressure, or even a minor injury sustained through other activities outside the trials that occurred during the study period must be documented as an AE. This provides for proper steps to evaluate it for relatedness as opposed to simply dismissing it outright. 

Common examples of AEs you may encounter include:

• Mild to moderate nausea or fatigue

• A new or worsening headache

• Minor injection-site reactions

• Laboratory abnormalities that meet protocol-defined thresholds

• Worsening of a pre-existing condition, if the worsening itself is unexpected in nature or severity

There are expectations for AEs to emerge though they are usually manageable and won;t require more than routine monitoring and documentation in a Case Report Form (CRF). The important requirement to remember is that every AE has to be assessed for severity, causality, and expectedness. This assessment helps determine if this remains an AE or if it should be escalated. 

What Is a Serious Adverse Event (SAE)?

A serious adverse effect is determined against a defined checklist of regulatory requirements. It is not as simple as an AE that feels seriously bad. An SAE is not based on severity or mildness, but is based on meeting one of the following criteria:

• Results in death

• Is life-threatening (the participant was at immediate risk of death at the time of the event, not merely a hypothetical risk if it worsened)

• Requires inpatient hospitalization or prolongs an existing hospitalization

• Results in persistent or significant disability/incapacity

• Results in a congenital anomaly or birth defect

• Is another medically important event that, based on clinical judgment, may jeopardize the participant or require intervention to prevent one of the outcomes above

The last category is a catch-all category requiring judgment calls. An event may not set the other criteria and still qualify as “medically important” requiring SAE handling. This can lead to confusion on whether to escalate an event or not. When in doubt, it is best to escalate the event opposed to  assuming it doesn’t qualify. 

It is also important to note that severity and seriousness are two different assessments. An event can be serious without being severe or can be sever without being serious. Avoid conflating the two to ensure to avoid classification errors. 

Adverse Event (AE) vs. Serious Adverse Event (SAE): The Core Difference at a Glance

	Adverse Event (AE)	Serious Adverse Event (SAE)
Definition	Any unfavorable, unintended medical occurrence	Meets one or more specific regulatory seriousness criteria
Severity vs. seriousness	Can range from mild to severe	Defined by outcome/criteria, not symptom intensity
Reporting timeline	Routine, per protocol/CRF schedule	Expedited — typically within 24 hours of site awareness
Who gets notified	Documented in source and CRF	Sponsor, IRB, and potentially regulatory authorities
Follow-up requirements	Standard monitoring	Often requires follow-up reports until resolution or stabilization

How Sites Typically Handle Reporting

There are specific SAE reporting requirements protocol to protocol, but most SAE reporting follows similar workflows:

1. Immediate internal notification. 

   As soon as site staff become aware of a potential SAE, the principal investigator (PI) should be notified without delay, even before all details are confirmed.

2. Initial expedited report to the sponsor. 

   Most protocols require sponsor notification within 24 hours of the site becoming aware of the event, even if information is still incomplete. A follow-up report with additional detail typically comes later.

3. IRB notification. 

   Depending on the event and the IRB's specific reporting policy, the IRB may need to be notified on a defined timeline separate from the sponsor notification.

4. Causality and expectedness assessment. 

   The PI (not a delegate) is typically responsible for assessing whether the event is related to the study intervention and whether it was expected based on the current investigator's brochure or product labeling.

5. Follow-up until resolution. 

   SAEs generally need to be followed and reported on until they resolve, stabilize, or the participant is lost to follow-up, this isn't a one-time report and done.

Research staff often underestimate how important timeliness and an appropriate documentation trail is to SAE management. A complicated report submitted on time not only follow Good Clinical Practice (GCP), it could potentially hold less risk than a straightforward report created late. 

Common Mistakes Sites Make

A few patterns show up repeatedly during monitoring visits and audits:

• Treating "serious" as a judgment call about how sick the participant looked, rather than checking it against the actual criteria list.

• Delaying the report while waiting for "complete" information. Expedited timelines start at awareness of the event, not once all the facts are gathered.

• Under-documenting the PI's causality assessment, leaving it unclear whether the PI actually made the relatedness determination.

• Forgetting hospitalizations that don't feel "dramatic," like a planned overnight stay for observation, which can still meet the SAE hospitalization criterion.

• 
  

Making some of these mistakes in bot about bad intent, but about recognizing the events with training and repetition. this can be helped with structured boarding and related trainings 

The Bottom Line

Any suspected AEs must be documented and assessed to identify those that will be treated as SAEs. Escalating to SAE is not about how alarming an event seems, but based on assessing it against regulatory criteria. By building the habits for appropriate reporting of AE and SAE, a site’s patient safety oversight and regulatory compliance improves. 

Getting this distinction set early on is important for the success of new sites. This ensures they follow Good Clinical Practice (GCP) documentation and can continue serving their community by providing clinical trials.

Note: This article is intended as an educational overview. Site-specific reporting timelines and definitions should always be confirmed against the current protocol, IRB requirements, and applicable regulatory guidance.