What happens after the coordinator clicks "submit"

A participant in a Phase III oncology trial develops grade 3 hepatotoxicity on a Tuesday afternoon. The clinical research coordinator documents the event. The investigator assesses causality. Within 24 hours, the sponsor receives an initial serious adverse event report. Within 15 calendar days -- sometimes sooner, depending on the regulatory framework -- the sponsor determines whether this event qualifies as a suspected unexpected serious adverse reaction and, if so, transmits an expedited report to the relevant regulatory authority. Meanwhile, the study site must ensure the IRB receives notification if required by the protocol or the IRB's own reporting policies.

That sequence, from bedside observation to regulatory authority desk, is the safety reporting pipeline. And somewhere in that pipeline -- at the junction where information flows outward from the site to multiple destinations simultaneously -- sits the regulatory coordinator.

This lesson maps that pipeline end to end. Not the clinical judgments within it (those belong to the investigator) and not the per-event documentation that feeds it (that belongs to the CRC). What we are mapping here is the system -- the architecture of information flow that the RC must understand, manage, and protect from failure. Because when this pipeline breaks, the consequences range from regulatory findings to compromised participant safety. Often both.

Tracing a serious adverse event from bedside to regulatory authority

Before we dissect the pipeline into its component parts, I want you to hold a single event in your mind and follow it through the entire system. This is the mental model that will anchor everything else in the course.

A participant enrolled in a multi-site clinical trial experiences a serious adverse event -- an unexpected hospitalization. Here is what happens, step by step, at the investigator site:

Step 1. The clinical research coordinator becomes aware of the event (through direct observation, participant contact, or medical record review) and documents it according to the protocol's safety reporting requirements. The CRC captures the clinical details: onset date, description, severity, outcome, and any concomitant medications or relevant medical history.

Step 2. The investigator reviews the CRC's documentation and makes the medical assessments that only a physician-investigator can make: Is this event serious? Is it expected based on the Reference Safety Information in the Investigator's Brochure? Is there a reasonable possibility of a causal relationship to the investigational product? Per ICH E6(R3) Annex 1, Section 2.7.2(b), the investigator should include an assessment of causality, and per Section 2.7.2(d), the investigator retains overall responsibility for participant safety even when delegating safety reporting activities. These medical assessments require physician qualifications and should not be performed by non-physician site staff.

Step 3. The serious adverse event report -- now containing both the CRC's documentation and the investigator's medical assessment -- must be transmitted to the sponsor according to the reporting requirements and timelines specified in the protocol. Per Section 2.7.2(b), all SAEs should be reported immediately to the sponsor, with an assessment of causality.

Step 4. The sponsor receives the report and integrates it into the aggregate safety database. Per Section 3.13.1, the sponsor reviews this information alongside all other safety data to determine whether it represents new safety information that changes the product's risk-benefit profile.

Step 5. If the sponsor determines the event qualifies as a Suspected Unexpected Serious Adverse Reaction, the sponsor expedites reporting to the regulatory authority per Section 3.13.2(b) and notifies all investigators and IRBs per Section 3.13.2(d).

Step 6. The IRB receives safety information -- either directly from the site (for events at that site) or from the sponsor (for aggregate safety updates) -- and uses it in its ongoing risk-benefit assessment of the trial.

That is the pipeline. Six stakeholders, multiple information flows, strict timelines, and no room for ambiguity about who does what.

The six stakeholders: what each one generates, processes, and receives

The pipeline has six stakeholders, and each one occupies a distinct role. I have found that the most common source of confusion among new regulatory coordinators is treating this pipeline as a linear chain when it is, in fact, a network with branching paths. The information does not simply pass from one person to the next in sequence. It branches. It sometimes loops back. And at the RC's position, it must be routed to multiple destinations simultaneously.

Let me be precise about what each stakeholder does within the pipeline.

Information flows: what travels between stakeholders

Understanding the stakeholders is necessary but not sufficient. The RC must also understand what information moves along each connection in the pipeline. This is not academic -- when a monitor asks "Can you show me documentation that the PI received and reviewed this safety letter?", the RC who understands the information flows can produce that documentation immediately.

The three critical handoff points

A pipeline is only as strong as its weakest joint. In safety reporting, the joints are the handoff points -- the moments where information must transition from one person's responsibility to another's. Each handoff requires documentation that proves the information was transferred, received, and acted upon.

I want to be direct about this: in my experience reviewing inspection findings across hundreds of investigator sites, the single most common category of safety reporting deficiency is not the clinical content of the report. It is the handoff. Information was generated but not transmitted. Information was transmitted but not documented. Information was received but not acted upon. The pipeline leaked at the joints.

There are three handoff points that the RC must understand -- and, in many cases, directly manage.

Handoff 1: CRC to investigator

The CRC documents the event. The investigator must review that documentation and add the medical assessment. This handoff requires:

What must transfer: Complete event documentation -- clinical description, onset date, severity, outcome, relevant medical history, and concomitant medications. The investigator cannot assess causality without this information.

Documentation requirement: Evidence that the investigator received the CRC's documentation, reviewed it, and rendered a medical judgment. This typically takes the form of a signed and dated SAE report form that includes both the CRC's clinical narrative and the investigator's causality assessment.

Where it fails: When the CRC completes the event documentation but the investigator does not review it promptly. Per Section 2.7.2(b), SAEs should be reported to the sponsor "immediately (after the investigator reasonably becomes aware of the event)." A delay at this handoff directly delays sponsor reporting and, consequently, delays the entire downstream pipeline.

The RC's role: The RC does not typically manage this handoff for individual events -- that is a per-event CRC function. But the RC is responsible for ensuring the system works: that there are clear procedures for CRC-to-investigator handoff, that these procedures include escalation when the investigator is unavailable, and that the documentation trail is auditable.

Handoff 2: Investigator to sponsor (via RC coordination)

Once the investigator has completed the medical assessment, the completed SAE report must reach the sponsor. This is where the RC's coordination role becomes most visible.

What must transfer: The complete SAE report with the investigator's causality assessment, formatted according to the sponsor's requirements and submitted via the sponsor's designated reporting mechanism (electronic portal, fax, or email per the study's safety reporting plan).

Documentation requirement: Evidence of transmission -- date and time of submission, confirmation of receipt by the sponsor, and a copy of what was submitted. Per Section 2.7.2(b), subsequent follow-up information should be submitted as necessary.

Where it fails: When the report sits completed on the investigator's desk but is not transmitted to the sponsor within the protocol-specified timeline. Or when it is transmitted but the site has no documentation proving it was sent. Or when initial reports are sent but follow-up reports with additional information (autopsy reports, hospital discharge summaries) are not submitted.

The RC's role: For many sites, the RC coordinates the actual transmission of SAE reports to the sponsor, tracks confirmation of receipt, and monitors follow-up report obligations. The RC also manages the parallel reporting to the IRB for events that meet IRB reporting thresholds.

Handoff 3: Site to IRB

Safety information must also flow from the site to the IRB. This handoff is governed by Section 1.4.8(c)-(d) and by the specific requirements of each IRB overseeing the site's studies.

What must transfer: The specific safety information the IRB requires, which varies by IRB. Some IRBs require notification of all SAEs. Others require notification only of unanticipated problems involving risks to subjects. Still others use hybrid criteria. The RC must know each IRB's requirements for each study.

Documentation requirement: Evidence of submission to the IRB, the IRB's acknowledgment of receipt, and any IRB response or follow-up request. This documentation becomes part of the essential records for the trial.

Where it fails: When a site does not submit a required safety report to the IRB, or submits it late, or submits it to the wrong IRB (a real risk for sites working with multiple IRBs). Also when a site fails to submit follow-up reports after the initial notification.

The RC's role: At most sites, the RC is directly responsible for preparing and submitting safety reports to the IRB. This is one of the RC's core functions in the safety reporting pipeline.

When the pipeline breaks: three failure scenarios

Understanding the pipeline is one thing. Understanding what happens when it breaks is another. Not all failures carry the same consequences. Some create regulatory findings. Some compromise participant safety. And some -- the most serious -- do both. The RC who can distinguish between these failure types is better equipped to build systems that prevent the most consequential ones.

Failure 1: Delayed follow-up report to the sponsor (regulatory finding)

An initial SAE report is submitted to the sponsor within 24 hours. But the hospital discharge summary, which contains important outcome information, arrives at the site three weeks later and is filed in the medical record without being forwarded to the sponsor as a follow-up report.

What broke: Handoff 2. The follow-up information was available at the site but not transmitted to the sponsor.

Regulatory consequence: This is a documentation and reporting deficiency. Per Section 2.7.2(b), subsequent information should be submitted as follow-up reports "as necessary." A monitor or auditor reviewing the site's safety records would identify this gap. It would likely appear as a finding on a monitoring visit report and, in an inspection, could appear as a Form 483 observation.

Participant safety impact: In most cases, minimal. The initial report was timely, so the sponsor was aware of the event. The delayed follow-up affects the completeness of the sponsor's safety database but does not, by itself, compromise participant safety at the reporting site.

The distinction matters: This failure is serious because it represents a systemic process gap, but it is not the same category of failure as one that leaves participants unprotected.

Failure 2: Sponsor safety letter not reaching the investigator (safety compromise)

The sponsor sends a safety letter to the site notifying the investigator of a newly identified drug-drug interaction that affects participants on a common concomitant medication. The letter arrives at the site but is filed without being routed to the investigator for review. The investigator never becomes aware of the new safety information. Participants on the affected concomitant medication continue in the trial without being counseled about the newly identified risk.

What broke: The inbound pipeline -- the link between sponsor communication and investigator awareness. Per Section 3.13.2(d), SUSAR reporting to investigators should reflect "the urgency of action required." A safety letter about a drug interaction affecting currently enrolled participants requires prompt investigator attention.

Participant safety impact: Direct. Participants are exposed to a risk that the investigator could mitigate if informed. The investigator cannot exercise medical judgment about information they have not received.

Regulatory consequence: This would also generate a regulatory finding -- the site failed to process a safety communication and failed to ensure investigator awareness. But the primary concern here is not the regulatory finding. It is the participants.

Failure 3: SUSAR notification not submitted to the IRB (both)

The sponsor notifies the site of a SUSAR -- a suspected unexpected serious adverse reaction at another site in the multi-site trial. Per the IRB's reporting policy, this SUSAR notification must be forwarded to the IRB within five business days. The regulatory coordinator does not submit it. The IRB never receives the information and therefore cannot incorporate it into its ongoing risk-benefit assessment. Meanwhile, participants continue to be enrolled and treated under an IRB approval that is based on incomplete safety information.

What broke: Handoff 3. The information reached the site but was not transmitted to the IRB.

Participant safety impact: The IRB exists to protect participants. When the IRB lacks current safety information, its oversight function is impaired. In this scenario, the IRB may have continued to approve the study or approved re-consent materials without knowing about the SUSAR. This is a direct compromise of the oversight system designed to protect participants.

Regulatory consequence: Severe. Failure to report to the IRB per Section 1.4.8(c) is one of the most serious compliance deficiencies a site can commit. This finding would likely trigger increased regulatory scrutiny of the site and could affect the site's ability to conduct future research.

The RC's position in the pipeline

By now you can see where the RC sits: at the coordination junction. The RC does not generate the safety data (the CRC does that) and does not make the medical assessments (the investigator does that). The RC ensures that once safety information exists and has been medically assessed, it reaches every destination it needs to reach, on time, with documentation proving it got there.

This is, in my view, one of the most underappreciated roles in clinical research. The RC's contribution is invisible when the pipeline works and catastrophic when it does not. A well-functioning safety reporting pipeline is evidence that an RC is doing their job. You will never see a headline reading "Regulatory coordinator ensures timely IRB notification of SUSAR." But you will see FDA warning letters citing failure to do exactly that.

In the next lesson, we will draw the precise boundaries between the RC's responsibilities, the CRC's responsibilities, and the investigator's responsibilities in this pipeline. Before you can build the infrastructure to manage safety reporting across a portfolio, you need to know -- with precision -- which parts of the pipeline are yours.

What happens after the coordinator clicks "submit"

A participant in a Phase III oncology trial develops grade 3 hepatotoxicity on a Tuesday afternoon. The clinical research coordinator documents the event. The investigator assesses causality. Within 24 hours, the sponsor receives an initial serious adverse event report. Within 15 calendar days -- sometimes sooner, depending on the regulatory framework -- the sponsor determines whether this event qualifies as a suspected unexpected serious adverse reaction and, if so, transmits an expedited report to the relevant regulatory authority. Meanwhile, the study site must ensure the IRB receives notification if required by the protocol or the IRB's own reporting policies.

That sequence, from bedside observation to regulatory authority desk, is the safety reporting pipeline. And somewhere in that pipeline -- at the junction where information flows outward from the site to multiple destinations simultaneously -- sits the regulatory coordinator.

This lesson maps that pipeline end to end. Not the clinical judgments within it (those belong to the investigator) and not the per-event documentation that feeds it (that belongs to the CRC). What we are mapping here is the system -- the architecture of information flow that the RC must understand, manage, and protect from failure. Because when this pipeline breaks, the consequences range from regulatory findings to compromised participant safety. Often both.

Tracing a serious adverse event from bedside to regulatory authority

Before we dissect the pipeline into its component parts, I want you to hold a single event in your mind and follow it through the entire system. This is the mental model that will anchor everything else in the course.

A participant enrolled in a multi-site clinical trial experiences a serious adverse event -- an unexpected hospitalization. Here is what happens, step by step, at the investigator site:

Step 1. The clinical research coordinator becomes aware of the event (through direct observation, participant contact, or medical record review) and documents it according to the protocol's safety reporting requirements. The CRC captures the clinical details: onset date, description, severity, outcome, and any concomitant medications or relevant medical history.

Step 2. The investigator reviews the CRC's documentation and makes the medical assessments that only a physician-investigator can make: Is this event serious? Is it expected based on the Reference Safety Information in the Investigator's Brochure? Is there a reasonable possibility of a causal relationship to the investigational product? Per ICH E6(R3) Annex 1, Section 2.7.2(b), the investigator should include an assessment of causality, and per Section 2.7.2(d), the investigator retains overall responsibility for participant safety even when delegating safety reporting activities. These medical assessments require physician qualifications and should not be performed by non-physician site staff.

Step 3. The serious adverse event report -- now containing both the CRC's documentation and the investigator's medical assessment -- must be transmitted to the sponsor according to the reporting requirements and timelines specified in the protocol. Per Section 2.7.2(b), all SAEs should be reported immediately to the sponsor, with an assessment of causality.

Step 4. The sponsor receives the report and integrates it into the aggregate safety database. Per Section 3.13.1, the sponsor reviews this information alongside all other safety data to determine whether it represents new safety information that changes the product's risk-benefit profile.

Step 5. If the sponsor determines the event qualifies as a Suspected Unexpected Serious Adverse Reaction, the sponsor expedites reporting to the regulatory authority per Section 3.13.2(b) and notifies all investigators and IRBs per Section 3.13.2(d).

Step 6. The IRB receives safety information -- either directly from the site (for events at that site) or from the sponsor (for aggregate safety updates) -- and uses it in its ongoing risk-benefit assessment of the trial.

That is the pipeline. Six stakeholders, multiple information flows, strict timelines, and no room for ambiguity about who does what.

The six stakeholders: what each one generates, processes, and receives

The pipeline has six stakeholders, and each one occupies a distinct role. I have found that the most common source of confusion among new regulatory coordinators is treating this pipeline as a linear chain when it is, in fact, a network with branching paths. The information does not simply pass from one person to the next in sequence. It branches. It sometimes loops back. And at the RC's position, it must be routed to multiple destinations simultaneously.

Let me be precise about what each stakeholder does within the pipeline.

Information flows: what travels between stakeholders

Understanding the stakeholders is necessary but not sufficient. The RC must also understand what information moves along each connection in the pipeline. This is not academic -- when a monitor asks "Can you show me documentation that the PI received and reviewed this safety letter?", the RC who understands the information flows can produce that documentation immediately.

The three critical handoff points

A pipeline is only as strong as its weakest joint. In safety reporting, the joints are the handoff points -- the moments where information must transition from one person's responsibility to another's. Each handoff requires documentation that proves the information was transferred, received, and acted upon.

I want to be direct about this: in my experience reviewing inspection findings across hundreds of investigator sites, the single most common category of safety reporting deficiency is not the clinical content of the report. It is the handoff. Information was generated but not transmitted. Information was transmitted but not documented. Information was received but not acted upon. The pipeline leaked at the joints.

There are three handoff points that the RC must understand -- and, in many cases, directly manage.

Handoff 1: CRC to investigator

The CRC documents the event. The investigator must review that documentation and add the medical assessment. This handoff requires:

What must transfer: Complete event documentation -- clinical description, onset date, severity, outcome, relevant medical history, and concomitant medications. The investigator cannot assess causality without this information.

Documentation requirement: Evidence that the investigator received the CRC's documentation, reviewed it, and rendered a medical judgment. This typically takes the form of a signed and dated SAE report form that includes both the CRC's clinical narrative and the investigator's causality assessment.

Where it fails: When the CRC completes the event documentation but the investigator does not review it promptly. Per Section 2.7.2(b), SAEs should be reported to the sponsor "immediately (after the investigator reasonably becomes aware of the event)." A delay at this handoff directly delays sponsor reporting and, consequently, delays the entire downstream pipeline.

The RC's role: The RC does not typically manage this handoff for individual events -- that is a per-event CRC function. But the RC is responsible for ensuring the system works: that there are clear procedures for CRC-to-investigator handoff, that these procedures include escalation when the investigator is unavailable, and that the documentation trail is auditable.

Handoff 2: Investigator to sponsor (via RC coordination)

Once the investigator has completed the medical assessment, the completed SAE report must reach the sponsor. This is where the RC's coordination role becomes most visible.

What must transfer: The complete SAE report with the investigator's causality assessment, formatted according to the sponsor's requirements and submitted via the sponsor's designated reporting mechanism (electronic portal, fax, or email per the study's safety reporting plan).

Documentation requirement: Evidence of transmission -- date and time of submission, confirmation of receipt by the sponsor, and a copy of what was submitted. Per Section 2.7.2(b), subsequent follow-up information should be submitted as necessary.

Where it fails: When the report sits completed on the investigator's desk but is not transmitted to the sponsor within the protocol-specified timeline. Or when it is transmitted but the site has no documentation proving it was sent. Or when initial reports are sent but follow-up reports with additional information (autopsy reports, hospital discharge summaries) are not submitted.

The RC's role: For many sites, the RC coordinates the actual transmission of SAE reports to the sponsor, tracks confirmation of receipt, and monitors follow-up report obligations. The RC also manages the parallel reporting to the IRB for events that meet IRB reporting thresholds.

Handoff 3: Site to IRB

Safety information must also flow from the site to the IRB. This handoff is governed by Section 1.4.8(c)-(d) and by the specific requirements of each IRB overseeing the site's studies.

What must transfer: The specific safety information the IRB requires, which varies by IRB. Some IRBs require notification of all SAEs. Others require notification only of unanticipated problems involving risks to subjects. Still others use hybrid criteria. The RC must know each IRB's requirements for each study.

Documentation requirement: Evidence of submission to the IRB, the IRB's acknowledgment of receipt, and any IRB response or follow-up request. This documentation becomes part of the essential records for the trial.

Where it fails: When a site does not submit a required safety report to the IRB, or submits it late, or submits it to the wrong IRB (a real risk for sites working with multiple IRBs). Also when a site fails to submit follow-up reports after the initial notification.

The RC's role: At most sites, the RC is directly responsible for preparing and submitting safety reports to the IRB. This is one of the RC's core functions in the safety reporting pipeline.

When the pipeline breaks: three failure scenarios

Understanding the pipeline is one thing. Understanding what happens when it breaks is another. Not all failures carry the same consequences. Some create regulatory findings. Some compromise participant safety. And some -- the most serious -- do both. The RC who can distinguish between these failure types is better equipped to build systems that prevent the most consequential ones.

Failure 1: Delayed follow-up report to the sponsor (regulatory finding)

An initial SAE report is submitted to the sponsor within 24 hours. But the hospital discharge summary, which contains important outcome information, arrives at the site three weeks later and is filed in the medical record without being forwarded to the sponsor as a follow-up report.

What broke: Handoff 2. The follow-up information was available at the site but not transmitted to the sponsor.

Regulatory consequence: This is a documentation and reporting deficiency. Per Section 2.7.2(b), subsequent information should be submitted as follow-up reports "as necessary." A monitor or auditor reviewing the site's safety records would identify this gap. It would likely appear as a finding on a monitoring visit report and, in an inspection, could appear as a Form 483 observation.

Participant safety impact: In most cases, minimal. The initial report was timely, so the sponsor was aware of the event. The delayed follow-up affects the completeness of the sponsor's safety database but does not, by itself, compromise participant safety at the reporting site.

The distinction matters: This failure is serious because it represents a systemic process gap, but it is not the same category of failure as one that leaves participants unprotected.

Failure 2: Sponsor safety letter not reaching the investigator (safety compromise)

The sponsor sends a safety letter to the site notifying the investigator of a newly identified drug-drug interaction that affects participants on a common concomitant medication. The letter arrives at the site but is filed without being routed to the investigator for review. The investigator never becomes aware of the new safety information. Participants on the affected concomitant medication continue in the trial without being counseled about the newly identified risk.

What broke: The inbound pipeline -- the link between sponsor communication and investigator awareness. Per Section 3.13.2(d), SUSAR reporting to investigators should reflect "the urgency of action required." A safety letter about a drug interaction affecting currently enrolled participants requires prompt investigator attention.

Participant safety impact: Direct. Participants are exposed to a risk that the investigator could mitigate if informed. The investigator cannot exercise medical judgment about information they have not received.

Regulatory consequence: This would also generate a regulatory finding -- the site failed to process a safety communication and failed to ensure investigator awareness. But the primary concern here is not the regulatory finding. It is the participants.

Failure 3: SUSAR notification not submitted to the IRB (both)

The sponsor notifies the site of a SUSAR -- a suspected unexpected serious adverse reaction at another site in the multi-site trial. Per the IRB's reporting policy, this SUSAR notification must be forwarded to the IRB within five business days. The regulatory coordinator does not submit it. The IRB never receives the information and therefore cannot incorporate it into its ongoing risk-benefit assessment. Meanwhile, participants continue to be enrolled and treated under an IRB approval that is based on incomplete safety information.

What broke: Handoff 3. The information reached the site but was not transmitted to the IRB.

Participant safety impact: The IRB exists to protect participants. When the IRB lacks current safety information, its oversight function is impaired. In this scenario, the IRB may have continued to approve the study or approved re-consent materials without knowing about the SUSAR. This is a direct compromise of the oversight system designed to protect participants.

Regulatory consequence: Severe. Failure to report to the IRB per Section 1.4.8(c) is one of the most serious compliance deficiencies a site can commit. This finding would likely trigger increased regulatory scrutiny of the site and could affect the site's ability to conduct future research.

The RC's position in the pipeline

By now you can see where the RC sits: at the coordination junction. The RC does not generate the safety data (the CRC does that) and does not make the medical assessments (the investigator does that). The RC ensures that once safety information exists and has been medically assessed, it reaches every destination it needs to reach, on time, with documentation proving it got there.

This is, in my view, one of the most underappreciated roles in clinical research. The RC's contribution is invisible when the pipeline works and catastrophic when it does not. A well-functioning safety reporting pipeline is evidence that an RC is doing their job. You will never see a headline reading "Regulatory coordinator ensures timely IRB notification of SUSAR." But you will see FDA warning letters citing failure to do exactly that.

In the next lesson, we will draw the precise boundaries between the RC's responsibilities, the CRC's responsibilities, and the investigator's responsibilities in this pipeline. Before you can build the infrastructure to manage safety reporting across a portfolio, you need to know -- with precision -- which parts of the pipeline are yours.