Regulatory Coordinator
Full course · Protocol Amendment Management
Free Lesson Preview
View the Regulatory Coordinator track for current pricing and enrollment options.
View enrollment optionsAlready enrolled? Sign in
Teaches RCs to read protocol amendments as operational analysts -- scanning for downstream consequences across five operational domains, categorizing urgency, and distinguishing impact on enrolled versus future participants.
The amendment arrives on a Tuesday morning. It is four pages long. The sponsor's cover letter summarizes the changes in two paragraphs: "Amendment 4 modifies the schedule of the primary endpoint assessment from Week 24 to Week 16 and revises Exclusion Criterion 7 to exclude participants with a resting heart rate below 50 bpm."
Two sentences. Clean, factual, complete -- in the sense that both changes are mentioned. But an RC who reads only those two sentences and moves to the IRB submission step has missed everything that matters. Because the schedule change means every enrolled participant's visit calendar must be rebuilt. The pharmacy must adjust drug supply projections. The laboratory must accommodate eight additional weeks of assessments compressed into the remaining study timeline. Source documents capturing the endpoint assessment at Week 24 are now wrong -- they reference a visit window that no longer exists. Case report forms that map to the old schedule need updating. And the exclusion criterion change means screening procedures must be revised, informed consent must be amended to reflect the new eligibility requirements, and every participant currently enrolled must be evaluated against a criterion that did not exist when they were screened.
Two paragraphs in the cover letter. Twelve operational consequences on the ground.
This is the gap that this lesson addresses. The sponsor writes amendments in regulatory language -- what changed in the protocol text. The site must translate that regulatory language into operational language -- what the change means for the people, processes, documents, and systems that execute the study every day. And I have found, across three decades of teaching this material, that the single most common source of implementation failure is not a missed amendment. It is an amendment that was received, submitted to the IRB, approved, and then incompletely implemented because nobody systematically identified everything the change required.
What you will learn3 objectives
By the end of this lesson, you will be able to:
Progress saves itself — finish reading and this lesson completes
