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
Creates an institutional knowledge repository for each IRB the site works with, analyzing impact on portfolio planning and evaluating ethical boundaries of adapting to IRB-specific operational patterns.
Every site has one. The coordinator who has worked with the local IRB for 12 years and knows that Dr. Kessler on the committee always asks about the readability level of the consent form, that submitting on a Tuesday gives you three extra days before the committee reviews it because they meet on Friday, that the IRB administrator processes emails faster than portal messages before 10 a.m. but switches after lunch, and that the annual fee invoice comes in March but is not due until June even though the cover letter says 30 days.
This is institutional knowledge. It is not documented in any SOP. It is not available on the IRB's website. It was learned through years of interaction, accumulated observation, and occasional painful experience. And it is extraordinarily valuable -- because it is the difference between a submission that sails through review and one that gets returned with a request for revisions that a more experienced coordinator would have anticipated.
The problem, of course, is that this knowledge lives in one person's head. When that person leaves -- transfers to another department, takes a new position, retires -- the knowledge leaves with them. The next coordinator starts from zero, making the same mistakes, discovering the same patterns, rebuilding the same mental map. At a site managing 15 or more studies across multiple IRBs, the institutional knowledge about each IRB represents months of accumulated operational intelligence. Losing it is not merely inconvenient. It is operationally costly.
This lesson teaches you to make that knowledge explicit. To build a structured repository that captures what the formal procedures do not -- the operational patterns, the reviewer preferences, the timing insights, the unwritten rules -- and to maintain it as a living resource that survives personnel changes and strengthens the playbook system you built in Lesson 3.
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
