What the 1572 actually commits the investigator to

Let me be direct about something that is frequently misunderstood: the 1572 is not an administrative form. It is a personal commitment by the investigator to the FDA. Per 21 CFR 312.53(c), the investigator agrees -- by signature -- to conduct the study in accordance with the protocol, to protect the rights, safety, and welfare of participants, to comply with all applicable regulatory requirements, and to ensure that an IRB meeting the requirements of 21 CFR Part 56 will review the research. The investigator further commits that the information on the form is accurate.

That last commitment -- accuracy -- is what creates the RC's operational obligation. Every piece of information on the 1572 is a representation to the FDA. When that information changes and the form is not updated, the investigator's representation to the FDA is no longer true.

ICH E6(R3) reinforces this through multiple sections. Section 2.1 establishes the investigator's qualification requirements, while Section 2.3.1 establishes that the investigator retains ultimate responsibility for delegated trial activities. Section 2.2 addresses adequate resources and qualified staff, while Section 2.3 governs delegation of trial-related activities and investigator oversight. Section 2.4 covers communication with the IRB/IEC. The 1572 is the mechanism through which the investigator certifies these commitments to the FDA for IND studies.

And here is the portfolio-level reality: if the investigator holds active 1572s for six IND studies, a single personnel change may require updating six forms. A laboratory change may affect four. The RC who tracks these obligations study-by-study will inevitably miss one.

The seven trigger events that require 1572 revision

Not every change at the site triggers a 1572 update. The RC needs to know precisely which events do, because a tracking system that alerts on irrelevant changes is a tracking system that gets ignored. Based on the information collected on FDA Form 1572 and the requirements of 21 CFR 312.53, I identify seven categories of trigger events.

Analyzing the high-risk triggers

Three of these seven triggers deserve closer analysis because they create the most significant portfolio-level risk.

Sub-investigator changes are, in my experience, the most frequently missed 1572 update. Sub-investigators leave institutions. New fellows rotate through. Visiting faculty join for a study season and depart. Each of these personnel changes should trigger a 1572 review for every IND study on which that individual was listed -- or should be listed. The challenge is that personnel changes often happen without formal notification to the regulatory team. The department announces a departure. The new fellow starts. Nobody thinks to tell the RC until the next monitoring visit, when the CRA asks why the study is being conducted by someone not on the 1572.

The RC's prevention system must include a mechanism for learning about personnel changes proactively, not reactively. This means establishing notification agreements with the department, the principal investigator's administrative team, and -- critically -- the human resources or credentialing office. When a person with sub-investigator privileges leaves the institution, the RC needs to know within days, not months.

Laboratory changes present a different challenge. A site may add a clinical laboratory to its repertoire gradually -- specimens are sent to the new lab for one study, then another, then another. By the time the RC realizes the laboratory is processing specimens for four IND studies, the 1572s for those studies still list only the original lab. The gap is not dramatic -- no alarm bell rings. But the gap is real, and auditors find it.

IRB transitions are, ironically, the least likely to be missed -- because IRB changes are high-visibility events that typically involve the RC directly. But I include them here because the 1572 update during an IRB transition is sometimes deprioritized in the larger operational complexity of the transition itself. Module 4 covered mid-study IRB transitions; the 1572 update should be an explicit step in the transition checklist.

Designing the portfolio-level 1572 tracking system

A 1572 tracking system is not merely a list of forms. It is a cross-referenced matrix that connects three dimensions: studies (which IND studies have active 1572s at the site), personnel (which individuals are listed on which 1572s), and facilities/laboratories (which resources are listed on which forms). When any element in any dimension changes, the system must identify every 1572 affected.

The minimum data architecture for a 1572 tracking matrix includes the following fields for each active 1572: study identifier and IND number, principal investigator name, date of most recent signed 1572, all listed sub-investigators (with dates added), all listed laboratories (with dates added), all listed facilities, IRB of record, and the sponsor contact for 1572 revisions. The matrix should also capture the date of the last currency review -- the date on which someone verified that all information on the 1572 remains accurate.

I recommend two complementary tracking mechanisms. First, an event-driven alert system: when a trigger event occurs (sub-investigator departure, new lab, IRB change), the system generates a task to review and update every affected 1572. Second, a calendar-driven review cycle: a quarterly audit of all active 1572s against current site information, catching any changes that slipped past the event-driven system. The quarterly review is the safety net. The event-driven system is the primary control.

Evaluating the regulatory risk of outdated information

Not all 1572 deficiencies carry equal risk. The RC must be able to triage -- to distinguish between a deficiency that requires immediate correction and one that can be addressed during the next routine update cycle.

The risk evaluation hinges on two questions. First, does the outdated information affect participant safety or data integrity? A sub-investigator who has departed but is still listed on the 1572 is an inaccuracy, but it does not create a safety risk unless study activities are being attributed to that person. A new laboratory processing specimens that is not listed on the 1572, by contrast, breaks the data integrity chain -- the FDA's records do not reflect where specimens are being analyzed.

Second, does the outdated information create a discrepancy that an auditor or inspector would flag as a significant finding? FDA inspectors reviewing 1572 accuracy will assess whether the inaccuracy reflects a systemic failure of oversight or an isolated administrative delay. A single 1572 updated three weeks late looks like a process improvement opportunity. Five 1572s updated seven months late looks like a site that does not maintain its regulatory commitments.

I categorize 1572 deficiencies into three risk tiers. Tier 1 -- critical: the deficiency affects participant safety, data integrity, or involves an individual conducting study activities who is not authorized on the 1572. These require immediate correction, same business day. Tier 2 -- significant: the deficiency represents an inaccuracy that an auditor would flag as a finding, but does not currently affect safety or data integrity. These require correction within two weeks. Tier 3 -- administrative: the deficiency is a minor inaccuracy (address change, updated CV) that should be corrected at the next scheduled update cycle or quarterly review.

The quarterly currency review -- your safety net

Event-driven alerts catch the changes you know about. The quarterly currency review catches the ones you missed.

The process is straightforward. Once per quarter, the RC pulls the current 1572 for every active IND study and compares it, line by line, against current site information. Is the investigator's address current? Are all active sub-investigators listed and all departed sub-investigators removed? Are all current laboratories and facilities listed? Does the IRB information match the current IRB of record?

This review takes time -- in a portfolio of 15 IND studies, it can consume a full day. But the alternative is discovering 1572 deficiencies during a sponsor audit or FDA inspection, when the finding is documented formally and the site's credibility takes a hit that no amount of retroactive correction fully repairs.

The quarterly review also generates useful portfolio intelligence. If the same type of deficiency appears repeatedly -- sub-investigators consistently added late, for instance -- it signals a systemic gap in the notification chain. The review is not merely a correction exercise. It is a diagnostic tool.

When the system fails -- and how to recover

A portfolio-level tracking system is the prevention. But what happens when the RC discovers -- during an audit, a monitoring visit, or the quarterly review -- that multiple 1572s are out of date? The response requires a structured approach: assess the scope of the deficiency, determine the risk tier for each affected form, sequence the corrections by urgency, notify the appropriate sponsors, and implement the systemic fix that prevents recurrence.

The following case study illustrates exactly this scenario.

Key takeaways

FDA Form 1572 is not a one-time filing -- it is a living commitment by the investigator to the FDA that must reflect current reality across every IND study in the portfolio. The RC manages this currency through two complementary systems: an event-driven alert mechanism that captures trigger events (personnel changes, laboratory additions, IRB transitions, facility changes) as they occur, and a quarterly currency review that catches any changes the event-driven system missed.

Seven categories of trigger events require 1572 revision, but three dominate the RC's operational attention: sub-investigator changes, laboratory changes, and IRB transitions. Of these, sub-investigator departures are the most frequently missed because they often occur without formal notification to the regulatory team.

Not all 1572 deficiencies carry equal risk. The three-tier framework -- critical (same-day correction when an unlisted individual is conducting study activities or an unlisted facility is generating data), significant (correction within two weeks for inaccuracies that do not currently affect safety or integrity), and administrative (next scheduled review for minor factual updates) -- enables the RC to triage deficiencies and allocate correction effort proportionately across a multi-study portfolio.

What the 1572 actually commits the investigator to

Let me be direct about something that is frequently misunderstood: the 1572 is not an administrative form. It is a personal commitment by the investigator to the FDA. Per 21 CFR 312.53(c), the investigator agrees -- by signature -- to conduct the study in accordance with the protocol, to protect the rights, safety, and welfare of participants, to comply with all applicable regulatory requirements, and to ensure that an IRB meeting the requirements of 21 CFR Part 56 will review the research. The investigator further commits that the information on the form is accurate.

That last commitment -- accuracy -- is what creates the RC's operational obligation. Every piece of information on the 1572 is a representation to the FDA. When that information changes and the form is not updated, the investigator's representation to the FDA is no longer true.

ICH E6(R3) reinforces this through multiple sections. Section 2.1 establishes the investigator's qualification requirements, while Section 2.3.1 establishes that the investigator retains ultimate responsibility for delegated trial activities. Section 2.2 addresses adequate resources and qualified staff, while Section 2.3 governs delegation of trial-related activities and investigator oversight. Section 2.4 covers communication with the IRB/IEC. The 1572 is the mechanism through which the investigator certifies these commitments to the FDA for IND studies.

And here is the portfolio-level reality: if the investigator holds active 1572s for six IND studies, a single personnel change may require updating six forms. A laboratory change may affect four. The RC who tracks these obligations study-by-study will inevitably miss one.

The seven trigger events that require 1572 revision

Not every change at the site triggers a 1572 update. The RC needs to know precisely which events do, because a tracking system that alerts on irrelevant changes is a tracking system that gets ignored. Based on the information collected on FDA Form 1572 and the requirements of 21 CFR 312.53, I identify seven categories of trigger events.

Analyzing the high-risk triggers

Three of these seven triggers deserve closer analysis because they create the most significant portfolio-level risk.

Sub-investigator changes are, in my experience, the most frequently missed 1572 update. Sub-investigators leave institutions. New fellows rotate through. Visiting faculty join for a study season and depart. Each of these personnel changes should trigger a 1572 review for every IND study on which that individual was listed -- or should be listed. The challenge is that personnel changes often happen without formal notification to the regulatory team. The department announces a departure. The new fellow starts. Nobody thinks to tell the RC until the next monitoring visit, when the CRA asks why the study is being conducted by someone not on the 1572.

The RC's prevention system must include a mechanism for learning about personnel changes proactively, not reactively. This means establishing notification agreements with the department, the principal investigator's administrative team, and -- critically -- the human resources or credentialing office. When a person with sub-investigator privileges leaves the institution, the RC needs to know within days, not months.

Laboratory changes present a different challenge. A site may add a clinical laboratory to its repertoire gradually -- specimens are sent to the new lab for one study, then another, then another. By the time the RC realizes the laboratory is processing specimens for four IND studies, the 1572s for those studies still list only the original lab. The gap is not dramatic -- no alarm bell rings. But the gap is real, and auditors find it.

IRB transitions are, ironically, the least likely to be missed -- because IRB changes are high-visibility events that typically involve the RC directly. But I include them here because the 1572 update during an IRB transition is sometimes deprioritized in the larger operational complexity of the transition itself. Module 4 covered mid-study IRB transitions; the 1572 update should be an explicit step in the transition checklist.

Designing the portfolio-level 1572 tracking system

A 1572 tracking system is not merely a list of forms. It is a cross-referenced matrix that connects three dimensions: studies (which IND studies have active 1572s at the site), personnel (which individuals are listed on which 1572s), and facilities/laboratories (which resources are listed on which forms). When any element in any dimension changes, the system must identify every 1572 affected.

The minimum data architecture for a 1572 tracking matrix includes the following fields for each active 1572: study identifier and IND number, principal investigator name, date of most recent signed 1572, all listed sub-investigators (with dates added), all listed laboratories (with dates added), all listed facilities, IRB of record, and the sponsor contact for 1572 revisions. The matrix should also capture the date of the last currency review -- the date on which someone verified that all information on the 1572 remains accurate.

I recommend two complementary tracking mechanisms. First, an event-driven alert system: when a trigger event occurs (sub-investigator departure, new lab, IRB change), the system generates a task to review and update every affected 1572. Second, a calendar-driven review cycle: a quarterly audit of all active 1572s against current site information, catching any changes that slipped past the event-driven system. The quarterly review is the safety net. The event-driven system is the primary control.

Evaluating the regulatory risk of outdated information

Not all 1572 deficiencies carry equal risk. The RC must be able to triage -- to distinguish between a deficiency that requires immediate correction and one that can be addressed during the next routine update cycle.

The risk evaluation hinges on two questions. First, does the outdated information affect participant safety or data integrity? A sub-investigator who has departed but is still listed on the 1572 is an inaccuracy, but it does not create a safety risk unless study activities are being attributed to that person. A new laboratory processing specimens that is not listed on the 1572, by contrast, breaks the data integrity chain -- the FDA's records do not reflect where specimens are being analyzed.

Second, does the outdated information create a discrepancy that an auditor or inspector would flag as a significant finding? FDA inspectors reviewing 1572 accuracy will assess whether the inaccuracy reflects a systemic failure of oversight or an isolated administrative delay. A single 1572 updated three weeks late looks like a process improvement opportunity. Five 1572s updated seven months late looks like a site that does not maintain its regulatory commitments.

I categorize 1572 deficiencies into three risk tiers. Tier 1 -- critical: the deficiency affects participant safety, data integrity, or involves an individual conducting study activities who is not authorized on the 1572. These require immediate correction, same business day. Tier 2 -- significant: the deficiency represents an inaccuracy that an auditor would flag as a finding, but does not currently affect safety or data integrity. These require correction within two weeks. Tier 3 -- administrative: the deficiency is a minor inaccuracy (address change, updated CV) that should be corrected at the next scheduled update cycle or quarterly review.

The quarterly currency review -- your safety net

Event-driven alerts catch the changes you know about. The quarterly currency review catches the ones you missed.

The process is straightforward. Once per quarter, the RC pulls the current 1572 for every active IND study and compares it, line by line, against current site information. Is the investigator's address current? Are all active sub-investigators listed and all departed sub-investigators removed? Are all current laboratories and facilities listed? Does the IRB information match the current IRB of record?

This review takes time -- in a portfolio of 15 IND studies, it can consume a full day. But the alternative is discovering 1572 deficiencies during a sponsor audit or FDA inspection, when the finding is documented formally and the site's credibility takes a hit that no amount of retroactive correction fully repairs.

The quarterly review also generates useful portfolio intelligence. If the same type of deficiency appears repeatedly -- sub-investigators consistently added late, for instance -- it signals a systemic gap in the notification chain. The review is not merely a correction exercise. It is a diagnostic tool.

When the system fails -- and how to recover

A portfolio-level tracking system is the prevention. But what happens when the RC discovers -- during an audit, a monitoring visit, or the quarterly review -- that multiple 1572s are out of date? The response requires a structured approach: assess the scope of the deficiency, determine the risk tier for each affected form, sequence the corrections by urgency, notify the appropriate sponsors, and implement the systemic fix that prevents recurrence.

The following case study illustrates exactly this scenario.

Key takeaways

FDA Form 1572 is not a one-time filing -- it is a living commitment by the investigator to the FDA that must reflect current reality across every IND study in the portfolio. The RC manages this currency through two complementary systems: an event-driven alert mechanism that captures trigger events (personnel changes, laboratory additions, IRB transitions, facility changes) as they occur, and a quarterly currency review that catches any changes the event-driven system missed.

Seven categories of trigger events require 1572 revision, but three dominate the RC's operational attention: sub-investigator changes, laboratory changes, and IRB transitions. Of these, sub-investigator departures are the most frequently missed because they often occur without formal notification to the regulatory team.

Not all 1572 deficiencies carry equal risk. The three-tier framework -- critical (same-day correction when an unlisted individual is conducting study activities or an unlisted facility is generating data), significant (correction within two weeks for inaccuracies that do not currently affect safety or integrity), and administrative (next scheduled review for minor factual updates) -- enables the RC to triage deficiencies and allocate correction effort proportionately across a multi-study portfolio.