The biopsy that disappeared

Amendment 6 to an oncology study arrives on a Thursday morning. The sponsor's summary of changes is brief: the third of three scheduled tumor biopsy timepoints has been eliminated based on an interim analysis showing that the Week 36 specimen adds no meaningful pharmacodynamic data beyond what the Week 12 and Week 24 specimens provide. The amendment also updates the schedule of assessments, removes the associated pathology processing requirements, and revises the study budget.

Forty-three participants are currently enrolled. A coordinator reviews the amendment and brings a question to the regulatory coordinator: "This amendment reduces what we ask of participants. We are taking something away, not adding something. Do we need to reconsent everyone?"

It is, I have found, one of the most instructive questions in amendment management -- because the instinct to say "no" feels entirely reasonable. The amendment makes the study less burdensome. Participants are getting what most would consider good news. Why would you need to pull 43 people back to the site, or extend 43 upcoming visits, to tell them they no longer have to undergo a painful procedure?

And yet the answer is not that simple. The regulatory framework does not limit the reconsent obligation to changes that increase risk or burden. The standard is broader than that, and an RC who manages reconsent determination across a portfolio of 15 or 20 studies needs a decision framework that goes beyond instinct. This lesson builds that framework.

The regulatory threshold: Section 2.8.2

The reconsent obligation originates from a single, deliberately broad provision in ICH E6(R3). Section 2.8.2 states:

The participant or the participant's legally acceptable representative should be informed in a timely manner if new information becomes available that may be relevant to the participant's willingness to continue trial participation. The communication of this information and confirmation of the willingness to continue trial participation should be documented.

Three elements of this provision demand careful attention from the RC building a determination framework for the site.

First, the trigger is "new information," not "increased risk." The provision does not say "if new information increases risk to the participant." It says "if new information becomes available that may be relevant to the participant's willingness to continue." This is a critical distinction. A burden-reducing amendment is new information. A change in the risk-benefit profile based on emerging efficacy data is new information. A shift in the study's competitive landscape that changes the likelihood of the investigational product reaching market -- that, too, could be new information relevant to a participant's decision to continue.

Second, the standard is "may be relevant," not "is relevant." The provision uses deliberately permissive language. The question is not whether the information will change the participant's mind. It is whether the information might be relevant to the participant's ongoing decision about participation. This tilts the framework toward disclosure, not away from it.

Third, communication must be documented. Section 2.8.2 does not merely require that participants be informed -- it requires that the communication and the participant's confirmation of willingness to continue be documented. For the RC coordinating reconsent across a portfolio, this means every determination (reconsent required or not required) must be defensible and every reconsent conversation must produce a record.

The consent form requirement: Section 2.8.10(q)

Section 2.8.2 establishes the substantive obligation. Section 2.8.10(q) establishes the prospective promise. It requires that the informed consent materials explain to participants "that the participant or the participant's legally acceptable representative will be informed in a timely manner if information becomes available that may be relevant to the participant's willingness to continue trial participation."

This matters at the systems level for a specific reason: the consent form itself promises the participant that they will be told about relevant new information. When an amendment generates information that meets the Section 2.8.2 threshold, failing to communicate that information does not merely violate a regulatory requirement -- it breaks a promise the site made to the participant during the original consent process. And Section 2.8.10(q) means the IRB has already reviewed and approved that promise as part of the initial consent.

For the RC, the practical implication is that the reconsent determination is not discretionary in the way that some operational decisions are. The regulatory threshold is set by the guideline. The promise is embedded in the consent form. The site's obligation is to apply the threshold consistently, not to decide whether to apply it at all.

Applying the enrolled versus future participant distinction

In Module 1, Lesson 2, you learned to distinguish between amendment changes that affect currently enrolled participants and changes that affect only future participants. That distinction is the first branch point in the reconsent determination framework.

The logic is straightforward in its principle, though it requires careful application:

Amendments that change only the conditions of entry -- revised inclusion or exclusion criteria, modified screening procedures, new recruitment requirements -- typically affect future participants only. Currently enrolled participants have already passed through the gate these criteria guard. They were screened under the prior criteria. They were eligible under the prior criteria. Changing the gate does not change the experience of people already inside.

Amendments that change the study experience -- new safety monitoring procedures, additional study visits, modified dosing schedules, elimination of procedures, changes to the investigational product formulation, revised risk disclosures based on new safety data -- affect currently enrolled participants. These participants are living inside the study every day. Changes to what the study asks of them, or what the study exposes them to, or what the study now knows about the investigational product, are precisely the kind of information Section 2.8.2 contemplates.

But the boundary between these categories is not always clean. Consider an amendment that tightens an exclusion criterion to exclude participants with a resting heart rate below 50 beats per minute. For future participants, this is simply a new screening criterion. But what about currently enrolled participants whose resting heart rate has fallen below 50 bpm since enrollment? They were eligible at screening, but they now meet a criterion that the sponsor has determined makes study participation inappropriate. This is not a future-only change. It is new information about the safety profile that may be relevant to currently enrolled participants -- and possibly to their physicians.

The portfolio-level reconsent determination framework

The RC cannot afford to make ad-hoc reconsent determinations for each amendment in each study. When six amendments arrive in a month across four studies, the determination process must be standardized -- not because judgment is eliminated, but because the framework ensures the right questions are asked every time.

The framework operates through four sequential questions. Each question narrows the determination until the answer is clear.

Question 1: Does the amendment change anything for currently enrolled participants? If the amendment modifies only screening criteria, recruitment procedures, or other conditions that apply exclusively to participants not yet enrolled, the answer is no. Update the consent form for future participants per the version control system you built in Module 2 (Lesson 3), and move on. No reconsent of enrolled participants is needed.

If the amendment changes any aspect of the study experience for currently enrolled participants -- procedures, visit schedules, safety monitoring, risk disclosures, study duration, data collection requirements, or the investigational product itself -- proceed to Question 2.

Question 2: Does the change introduce new information that may be relevant to a participant's willingness to continue? Apply the Section 2.8.2 threshold. "May be relevant" is broad. A new safety monitoring procedure is relevant because it implies the sponsor has identified a safety signal requiring additional oversight. An additional study visit is relevant because it increases the time commitment the participant agreed to. A change in the investigational product formulation is relevant because the participant consented to receive a specific formulation. Even the elimination of a procedure is relevant -- participants may want to know that a decision was made about the scientific value of something they were asked to undergo.

If the answer is yes -- and for amendments that change the enrolled participant's experience, it usually is -- proceed to Question 3.

Question 3: Does the IRB require reconsent for this amendment? The IRB's approval letter for the amendment may specify whether reconsent is required. Some IRBs make this determination explicitly. Others approve the amended consent form and leave the reconsent determination to the site. When the IRB specifies a requirement, that requirement governs -- the site implements accordingly. When the IRB is silent, the site must apply its own determination using the Section 2.8.2 standard.

Regardless of the IRB's position, if the site determines that reconsent is warranted under Section 2.8.2, the site should proceed with reconsent even if the IRB has not explicitly required it. The investigator's obligation under Section 2.8.2 exists independently of the IRB's direction.

Question 4: What documentation supports the determination? Whether the determination is "reconsent required" or "reconsent not required," document the rationale. For a portfolio operating at scale, this means the amendment impact assessment (from Module 1, Lesson 4) should include a reconsent determination field with a brief written rationale. An auditor or monitor should be able to review the determination and understand why the site reached the conclusion it did.

Edge cases and the reasonable person standard

The four-question framework resolves most amendments cleanly. But a subset of amendments fall into territory where the answer is genuinely uncertain. These are the edge cases that separate a mechanical process from a thoughtful one, and they are where the "would a reasonable person want to know" standard becomes essential.

Edge case 1: Amendments that reduce participant burden. Return to the biopsy scenario from the opening. Amendment 6 eliminates the Week 36 tumor biopsy. The amendment reduces what the study asks of participants. It does not increase risk. It does not add procedures. It removes a painful, invasive procedure.

Should the RC determine that reconsent is required?

Apply the standard: would a reasonable person want to know that a painful procedure they consented to undergo has been eliminated from their study? I would argue -- and most IRBs agree -- that the answer is yes. A reasonable person wants to know that the study they are participating in has changed, even when the change is favorable. The information is relevant to their understanding of the study, and their consent was based on a description that included three biopsies, not two. But there is a practical nuance: the method of communication may differ. Some IRBs will require formal reconsent with a revised consent form. Others will accept documented communication -- a conversation during the next visit, noted in the source record -- without requiring a new signature on a revised consent. The RC must check with the IRB of record.

Edge case 2: Amendments that change the risk-benefit profile based on new efficacy data. An interim analysis reveals that the investigational product is performing significantly better than expected -- the treatment arm is showing a response rate of 62% against a historical control of 25%. The Data Safety Monitoring Board recommends continuing the study but reducing the sample size. The protocol amendment reflects this change.

Would a reasonable person want to know that the investigational product they are receiving appears to be working far better than anticipated? Yes -- and for complex reasons. The participant may feel reassured. The participant may also want to reassess whether they are willing to remain in a study where they might be receiving placebo (if the study is blinded and controlled). The participant may want to discuss the new data with their personal physician. New efficacy information changes the risk-benefit calculus the participant used when deciding to enroll.

Edge case 3: Amendments that change the nature of the study without changing the risk profile. A phase III oncology study amends the protocol to change the primary endpoint from overall survival to progression-free survival. The study procedures do not change. The safety monitoring does not change. What changes is what the sponsor is trying to prove, and by extension, the scientific context in which the participant's data will be used.

This is, in my view, the most difficult edge case. The participant's daily experience in the study does not change. But would a reasonable person want to know that the goal of the study they volunteered for has shifted? I believe the answer is yes, though I recognize that reasonable professionals disagree. A participant who enrolled because they wanted to contribute to evidence about whether the drug extends life may feel differently about contributing to evidence about whether the drug delays tumor progression. The information is relevant to their autonomy -- their right to decide, based on full information, whether to continue.

The practical resolution for the RC is to apply the reasonable person standard conservatively: when in doubt, disclose. The regulatory and ethical cost of unnecessary disclosure is low -- it requires time and documentation but causes no harm. The cost of failing to disclose when disclosure was warranted is significantly higher: it undermines participant autonomy, violates the promise embedded in the consent form per Section 2.8.10(q), and creates a compliance finding that is difficult to remediate after the fact.

Applying the framework at portfolio scale

A decision framework that works for one study is useful. A decision framework that works across 20 studies, applied consistently by three different coordinators, is essential. The portfolio-level application of the reconsent determination framework requires two additional considerations that single-study thinking does not address.

Consistency across coordinators. At a site with multiple coordinators, each coordinator may apply the Section 2.8.2 standard differently. One coordinator may default to reconsent for every amendment. Another may require reconsent only when the IRB explicitly mandates it. Neither approach is correct if applied mechanically. The framework standardizes the analysis: every coordinator asks the same four questions, in the same order, and documents the rationale. The RC reviews the determinations for consistency -- not to override the coordinator's judgment, but to ensure the framework was applied.

Batch determination during amendment surges. When three amendments arrive in a single week, the temptation is to process them quickly. The reconsent determination is the step most likely to be shortcut under time pressure, because it requires judgment rather than paperwork. The portfolio-level system treats the reconsent determination as a mandatory field in the amendment impact assessment -- it cannot be left blank, and the amendment cannot advance to the planning stage (which you will build in the next lesson) until the determination is documented.

The biopsy that disappeared

Amendment 6 to an oncology study arrives on a Thursday morning. The sponsor's summary of changes is brief: the third of three scheduled tumor biopsy timepoints has been eliminated based on an interim analysis showing that the Week 36 specimen adds no meaningful pharmacodynamic data beyond what the Week 12 and Week 24 specimens provide. The amendment also updates the schedule of assessments, removes the associated pathology processing requirements, and revises the study budget.

Forty-three participants are currently enrolled. A coordinator reviews the amendment and brings a question to the regulatory coordinator: "This amendment reduces what we ask of participants. We are taking something away, not adding something. Do we need to reconsent everyone?"

It is, I have found, one of the most instructive questions in amendment management -- because the instinct to say "no" feels entirely reasonable. The amendment makes the study less burdensome. Participants are getting what most would consider good news. Why would you need to pull 43 people back to the site, or extend 43 upcoming visits, to tell them they no longer have to undergo a painful procedure?

And yet the answer is not that simple. The regulatory framework does not limit the reconsent obligation to changes that increase risk or burden. The standard is broader than that, and an RC who manages reconsent determination across a portfolio of 15 or 20 studies needs a decision framework that goes beyond instinct. This lesson builds that framework.

The regulatory threshold: Section 2.8.2

The reconsent obligation originates from a single, deliberately broad provision in ICH E6(R3). Section 2.8.2 states:

The participant or the participant's legally acceptable representative should be informed in a timely manner if new information becomes available that may be relevant to the participant's willingness to continue trial participation. The communication of this information and confirmation of the willingness to continue trial participation should be documented.

Three elements of this provision demand careful attention from the RC building a determination framework for the site.

First, the trigger is "new information," not "increased risk." The provision does not say "if new information increases risk to the participant." It says "if new information becomes available that may be relevant to the participant's willingness to continue." This is a critical distinction. A burden-reducing amendment is new information. A change in the risk-benefit profile based on emerging efficacy data is new information. A shift in the study's competitive landscape that changes the likelihood of the investigational product reaching market -- that, too, could be new information relevant to a participant's decision to continue.

Second, the standard is "may be relevant," not "is relevant." The provision uses deliberately permissive language. The question is not whether the information will change the participant's mind. It is whether the information might be relevant to the participant's ongoing decision about participation. This tilts the framework toward disclosure, not away from it.

Third, communication must be documented. Section 2.8.2 does not merely require that participants be informed -- it requires that the communication and the participant's confirmation of willingness to continue be documented. For the RC coordinating reconsent across a portfolio, this means every determination (reconsent required or not required) must be defensible and every reconsent conversation must produce a record.

The consent form requirement: Section 2.8.10(q)

Section 2.8.2 establishes the substantive obligation. Section 2.8.10(q) establishes the prospective promise. It requires that the informed consent materials explain to participants "that the participant or the participant's legally acceptable representative will be informed in a timely manner if information becomes available that may be relevant to the participant's willingness to continue trial participation."

This matters at the systems level for a specific reason: the consent form itself promises the participant that they will be told about relevant new information. When an amendment generates information that meets the Section 2.8.2 threshold, failing to communicate that information does not merely violate a regulatory requirement -- it breaks a promise the site made to the participant during the original consent process. And Section 2.8.10(q) means the IRB has already reviewed and approved that promise as part of the initial consent.

For the RC, the practical implication is that the reconsent determination is not discretionary in the way that some operational decisions are. The regulatory threshold is set by the guideline. The promise is embedded in the consent form. The site's obligation is to apply the threshold consistently, not to decide whether to apply it at all.

Applying the enrolled versus future participant distinction

In Module 1, Lesson 2, you learned to distinguish between amendment changes that affect currently enrolled participants and changes that affect only future participants. That distinction is the first branch point in the reconsent determination framework.

The logic is straightforward in its principle, though it requires careful application:

Amendments that change only the conditions of entry -- revised inclusion or exclusion criteria, modified screening procedures, new recruitment requirements -- typically affect future participants only. Currently enrolled participants have already passed through the gate these criteria guard. They were screened under the prior criteria. They were eligible under the prior criteria. Changing the gate does not change the experience of people already inside.

Amendments that change the study experience -- new safety monitoring procedures, additional study visits, modified dosing schedules, elimination of procedures, changes to the investigational product formulation, revised risk disclosures based on new safety data -- affect currently enrolled participants. These participants are living inside the study every day. Changes to what the study asks of them, or what the study exposes them to, or what the study now knows about the investigational product, are precisely the kind of information Section 2.8.2 contemplates.

But the boundary between these categories is not always clean. Consider an amendment that tightens an exclusion criterion to exclude participants with a resting heart rate below 50 beats per minute. For future participants, this is simply a new screening criterion. But what about currently enrolled participants whose resting heart rate has fallen below 50 bpm since enrollment? They were eligible at screening, but they now meet a criterion that the sponsor has determined makes study participation inappropriate. This is not a future-only change. It is new information about the safety profile that may be relevant to currently enrolled participants -- and possibly to their physicians.

The portfolio-level reconsent determination framework

The RC cannot afford to make ad-hoc reconsent determinations for each amendment in each study. When six amendments arrive in a month across four studies, the determination process must be standardized -- not because judgment is eliminated, but because the framework ensures the right questions are asked every time.

The framework operates through four sequential questions. Each question narrows the determination until the answer is clear.

Question 1: Does the amendment change anything for currently enrolled participants? If the amendment modifies only screening criteria, recruitment procedures, or other conditions that apply exclusively to participants not yet enrolled, the answer is no. Update the consent form for future participants per the version control system you built in Module 2 (Lesson 3), and move on. No reconsent of enrolled participants is needed.

If the amendment changes any aspect of the study experience for currently enrolled participants -- procedures, visit schedules, safety monitoring, risk disclosures, study duration, data collection requirements, or the investigational product itself -- proceed to Question 2.

Question 2: Does the change introduce new information that may be relevant to a participant's willingness to continue? Apply the Section 2.8.2 threshold. "May be relevant" is broad. A new safety monitoring procedure is relevant because it implies the sponsor has identified a safety signal requiring additional oversight. An additional study visit is relevant because it increases the time commitment the participant agreed to. A change in the investigational product formulation is relevant because the participant consented to receive a specific formulation. Even the elimination of a procedure is relevant -- participants may want to know that a decision was made about the scientific value of something they were asked to undergo.

If the answer is yes -- and for amendments that change the enrolled participant's experience, it usually is -- proceed to Question 3.

Question 3: Does the IRB require reconsent for this amendment? The IRB's approval letter for the amendment may specify whether reconsent is required. Some IRBs make this determination explicitly. Others approve the amended consent form and leave the reconsent determination to the site. When the IRB specifies a requirement, that requirement governs -- the site implements accordingly. When the IRB is silent, the site must apply its own determination using the Section 2.8.2 standard.

Regardless of the IRB's position, if the site determines that reconsent is warranted under Section 2.8.2, the site should proceed with reconsent even if the IRB has not explicitly required it. The investigator's obligation under Section 2.8.2 exists independently of the IRB's direction.

Question 4: What documentation supports the determination? Whether the determination is "reconsent required" or "reconsent not required," document the rationale. For a portfolio operating at scale, this means the amendment impact assessment (from Module 1, Lesson 4) should include a reconsent determination field with a brief written rationale. An auditor or monitor should be able to review the determination and understand why the site reached the conclusion it did.

Edge cases and the reasonable person standard

The four-question framework resolves most amendments cleanly. But a subset of amendments fall into territory where the answer is genuinely uncertain. These are the edge cases that separate a mechanical process from a thoughtful one, and they are where the "would a reasonable person want to know" standard becomes essential.

Edge case 1: Amendments that reduce participant burden. Return to the biopsy scenario from the opening. Amendment 6 eliminates the Week 36 tumor biopsy. The amendment reduces what the study asks of participants. It does not increase risk. It does not add procedures. It removes a painful, invasive procedure.

Should the RC determine that reconsent is required?

Apply the standard: would a reasonable person want to know that a painful procedure they consented to undergo has been eliminated from their study? I would argue -- and most IRBs agree -- that the answer is yes. A reasonable person wants to know that the study they are participating in has changed, even when the change is favorable. The information is relevant to their understanding of the study, and their consent was based on a description that included three biopsies, not two. But there is a practical nuance: the method of communication may differ. Some IRBs will require formal reconsent with a revised consent form. Others will accept documented communication -- a conversation during the next visit, noted in the source record -- without requiring a new signature on a revised consent. The RC must check with the IRB of record.

Edge case 2: Amendments that change the risk-benefit profile based on new efficacy data. An interim analysis reveals that the investigational product is performing significantly better than expected -- the treatment arm is showing a response rate of 62% against a historical control of 25%. The Data Safety Monitoring Board recommends continuing the study but reducing the sample size. The protocol amendment reflects this change.

Would a reasonable person want to know that the investigational product they are receiving appears to be working far better than anticipated? Yes -- and for complex reasons. The participant may feel reassured. The participant may also want to reassess whether they are willing to remain in a study where they might be receiving placebo (if the study is blinded and controlled). The participant may want to discuss the new data with their personal physician. New efficacy information changes the risk-benefit calculus the participant used when deciding to enroll.

Edge case 3: Amendments that change the nature of the study without changing the risk profile. A phase III oncology study amends the protocol to change the primary endpoint from overall survival to progression-free survival. The study procedures do not change. The safety monitoring does not change. What changes is what the sponsor is trying to prove, and by extension, the scientific context in which the participant's data will be used.

This is, in my view, the most difficult edge case. The participant's daily experience in the study does not change. But would a reasonable person want to know that the goal of the study they volunteered for has shifted? I believe the answer is yes, though I recognize that reasonable professionals disagree. A participant who enrolled because they wanted to contribute to evidence about whether the drug extends life may feel differently about contributing to evidence about whether the drug delays tumor progression. The information is relevant to their autonomy -- their right to decide, based on full information, whether to continue.

The practical resolution for the RC is to apply the reasonable person standard conservatively: when in doubt, disclose. The regulatory and ethical cost of unnecessary disclosure is low -- it requires time and documentation but causes no harm. The cost of failing to disclose when disclosure was warranted is significantly higher: it undermines participant autonomy, violates the promise embedded in the consent form per Section 2.8.10(q), and creates a compliance finding that is difficult to remediate after the fact.

Applying the framework at portfolio scale

A decision framework that works for one study is useful. A decision framework that works across 20 studies, applied consistently by three different coordinators, is essential. The portfolio-level application of the reconsent determination framework requires two additional considerations that single-study thinking does not address.

Consistency across coordinators. At a site with multiple coordinators, each coordinator may apply the Section 2.8.2 standard differently. One coordinator may default to reconsent for every amendment. Another may require reconsent only when the IRB explicitly mandates it. Neither approach is correct if applied mechanically. The framework standardizes the analysis: every coordinator asks the same four questions, in the same order, and documents the rationale. The RC reviews the determinations for consistency -- not to override the coordinator's judgment, but to ensure the framework was applied.

Batch determination during amendment surges. When three amendments arrive in a single week, the temptation is to process them quickly. The reconsent determination is the step most likely to be shortcut under time pressure, because it requires judgment rather than paperwork. The portfolio-level system treats the reconsent determination as a mandatory field in the amendment impact assessment -- it cannot be left blank, and the amendment cannot advance to the planning stage (which you will build in the next lesson) until the determination is documented.