Free Lesson Preview
Continue with the Regulatory Coordinator track
View the Regulatory Coordinator track for current pricing and enrollment options.
View enrollment optionsAlready enrolled? Sign in
Regulatory Coordinator
Full course Β· Regulatory Submissions & Stakeholder Management
Free Lesson Preview
View the Regulatory Coordinator track for current pricing and enrollment options.
View enrollment optionsAlready enrolled? Sign in
Teaches the RC to design a multi-stage QC process for IRB submissions, apply risk-calibrated QC intensity, and create standardized checklists adaptable across IRBs and delegable to CRCs.
When an IRB returns a submission -- requesting a missing PI signature, noting an outdated CV, identifying an inconsistency between the protocol version and the consent form version -- the immediate cost is rework. Someone must obtain the signature, update the CV, reconcile the version discrepancy, and resubmit. That rework typically takes two to five days of elapsed time and one to three hours of labor.
But the real cost is not the rework. It is the downstream consequences. For a continuing review, a returned submission may push the resubmission past the approval expiration date, triggering a regulatory lapse that halts enrollment. For an initial submission, a returned package delays site activation by the entire resubmission cycle -- often three to six weeks. For an amendment, a returned submission means the site continues operating under the old protocol version while the corrected package is processed, creating a window of potential noncompliance.
And there is a cost that is harder to measure but, I would argue, equally consequential: reputation. IRBs notice which sites submit clean packages and which sites routinely submit incomplete ones. Monitors notice. Sponsors notice. Over time, a site with a high submission return rate develops a reputation for unreliable regulatory operations -- a reputation that affects everything from enrollment allocation decisions to the intensity of monitoring visits.
Quality control is not a luxury the RC adds when there is time. It is the system that prevents the most expensive kind of failure in the submission pipeline: the failure that reaches the IRB.
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