Sign inJoin Free
DashboardSign out
Free Lesson Preview
Module 1: Lesson 1

Examines how multiple regulatory frameworks generate overlapping and sometimes conflicting obligations at the site level, and how the RC reconciles them
A sponsor sends a monitoring visit letter requesting an updated delegation log. The log must reflect the format in the sponsor's study-specific procedure: a proprietary template with 14 columns, electronic signatures, and a revision history footer. Straightforward enough. But the site's IRB requires its own delegation log format for continuing review submissions -- eight columns, wet-ink signatures, and a certification statement at the bottom that the sponsor's template does not include. And then the site's institutional policy, driven by the compliance office's interpretation of 21 CFR 312.62, mandates a third format: one that captures FTE percentages and links each delegated task to the staff member's documented training.
Three regulatory sources. Three versions of what is, conceptually, the same document. None of them is wrong. All of them are binding on the site -- through contract, through institutional policy, through federal regulation. And the person who must reconcile them, maintain them, and produce the correct version for the correct audience at the correct time is sitting at the regulatory coordinator's desk.
The previous two lessons established what the site's regulatory obligations are and why they demand systems-level infrastructure at portfolio scale. This lesson asks a question that those lessons deferred: whose requirements, exactly, is the site fulfilling? Because the answer is not singular. It is layered, sometimes harmonious, occasionally contradictory, and always converging on the same desk.
By the end of this lesson, you will be able to:
Regulatory Coordinator
Full course · The Regulatory Coordinator: Role, Scope & Professional Identity
Free Lesson Preview
Module 1: Lesson 1

Examines how multiple regulatory frameworks generate overlapping and sometimes conflicting obligations at the site level, and how the RC reconciles them
A sponsor sends a monitoring visit letter requesting an updated delegation log. The log must reflect the format in the sponsor's study-specific procedure: a proprietary template with 14 columns, electronic signatures, and a revision history footer. Straightforward enough. But the site's IRB requires its own delegation log format for continuing review submissions -- eight columns, wet-ink signatures, and a certification statement at the bottom that the sponsor's template does not include. And then the site's institutional policy, driven by the compliance office's interpretation of 21 CFR 312.62, mandates a third format: one that captures FTE percentages and links each delegated task to the staff member's documented training.
Three regulatory sources. Three versions of what is, conceptually, the same document. None of them is wrong. All of them are binding on the site -- through contract, through institutional policy, through federal regulation. And the person who must reconcile them, maintain them, and produce the correct version for the correct audience at the correct time is sitting at the regulatory coordinator's desk.
The previous two lessons established what the site's regulatory obligations are and why they demand systems-level infrastructure at portfolio scale. This lesson asks a question that those lessons deferred: whose requirements, exactly, is the site fulfilling? Because the answer is not singular. It is layered, sometimes harmonious, occasionally contradictory, and always converging on the same desk.
By the end of this lesson, you will be able to:
Regulatory Coordinator
Full course · The Regulatory Coordinator: Role, Scope & Professional Identity
Continue with the Regulatory Coordinator track
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full courseContinue with the Regulatory Coordinator track
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full course