Sign inJoin Free
DashboardSign out
Regulatory Coordinator
Full course · Protocol Amendment Management
Regulatory Coordinator
Full course · Protocol Amendment Management
Free Lesson Preview
Module 1: Lesson 1

Teaches RCs to build portfolio-level reconsent tracking systems that monitor completion status across studies, generate escalation alerts for overdue reconsents, and create escalation procedures for participants who are difficult to reach.
The reconsent campaign for Amendment 4 is two weeks old. The tracking log shows 76 of 80 participants reconsented -- a 95% completion rate that, in most operational contexts, would qualify as a success. But in reconsent, 95% is not a completion metric. It is a problem statement. Those four remaining participants are not a rounding error. Each represents a regulatory obligation that has not been fulfilled, and every study activity conducted for those participants under the amended protocol without documented reconsent is an activity that may not withstand scrutiny during a monitoring visit or inspection.
There is a fifth participant, too -- one the team thought was reconsented until someone checked the verification log and discovered that the consent form in the binder was signed but bore the wrong version number. That signature is documentation of a conversation that used outdated materials. It does not count.
Five participants remain. Two have no upcoming visits for six weeks. One has not answered phone calls, voicemails, or letters for three weeks. Two declined the initial outreach call and have not been re-contacted. The reconsent plan from Lesson 2 identified these participants and assigned priority tiers. But the plan is a prospective document -- it says what the team intended to do. The question now is operational: how does the research coordinator know, across an entire portfolio of active reconsent campaigns, which participants are overdue, which escalation steps have been taken, and which require intervention today?
That question is answered by a tracking system. Not a tracking log -- the log records what happened. The tracking system monitors what has not happened yet.
By the end of this lesson, you will be able to:
Continue with the Regulatory Coordinator track
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full courseFree Lesson Preview
Module 1: Lesson 1

Teaches RCs to build portfolio-level reconsent tracking systems that monitor completion status across studies, generate escalation alerts for overdue reconsents, and create escalation procedures for participants who are difficult to reach.
The reconsent campaign for Amendment 4 is two weeks old. The tracking log shows 76 of 80 participants reconsented -- a 95% completion rate that, in most operational contexts, would qualify as a success. But in reconsent, 95% is not a completion metric. It is a problem statement. Those four remaining participants are not a rounding error. Each represents a regulatory obligation that has not been fulfilled, and every study activity conducted for those participants under the amended protocol without documented reconsent is an activity that may not withstand scrutiny during a monitoring visit or inspection.
There is a fifth participant, too -- one the team thought was reconsented until someone checked the verification log and discovered that the consent form in the binder was signed but bore the wrong version number. That signature is documentation of a conversation that used outdated materials. It does not count.
Five participants remain. Two have no upcoming visits for six weeks. One has not answered phone calls, voicemails, or letters for three weeks. Two declined the initial outreach call and have not been re-contacted. The reconsent plan from Lesson 2 identified these participants and assigned priority tiers. But the plan is a prospective document -- it says what the team intended to do. The question now is operational: how does the research coordinator know, across an entire portfolio of active reconsent campaigns, which participants are overdue, which escalation steps have been taken, and which require intervention today?
That question is answered by a tracking system. Not a tracking log -- the log records what happened. The tracking system monitors what has not happened yet.
By the end of this lesson, you will be able to:
Continue with the Regulatory Coordinator track
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full course