Regulatory Coordinator

Full course · Regulatory Submissions & Stakeholder Management

Post-approval IRB correspondence: managing stipulations, modifications required, and conditional approvals — Regulatory Submissions & Stakeholder Management

Post-approval IRB correspondence: managing stipulations, modifications required, and conditional approvals

Teaches the RC to manage post-approval IRB correspondence as a portfolio-level workflow, with tracking systems, routing protocols, escalation paths, and pattern analysis for systemic improvement.

23 min

Approval is not the end of the conversation

There is a persistent misconception -- one I encounter even among experienced research professionals -- that IRB approval is a binary event. You submit. The IRB approves. You move on. But anyone who has managed regulatory submissions at scale knows that IRB approval is frequently the beginning of a new stream of work, not the end of the old one.

An IRB approves a continuing review but stipulates that the consent form must be revised to include updated risk information from the investigator's brochure. Another approves an amendment with modifications required -- the consent language about data sharing must be clarified before the new version can be implemented. A third issues conditional approval: the site may continue enrolling, but must submit a revised protocol deviation management plan within 30 days.

Each of these outcomes creates a follow-up obligation. And in a portfolio of 18 studies, with continuing reviews, amendments, and safety reports flowing through multiple IRBs throughout the year, these follow-up obligations accumulate. They accumulate silently, because they are attached to approvals -- and approvals feel like victories, not like the beginning of new tasks.

This lesson is about building the systems that prevent post-approval obligations from falling through the cracks. Not how to respond to a single stipulation -- your CRC training covers that. This lesson teaches you to manage post-approval correspondence as a portfolio-level workflow: tracking every requirement to closure, routing each item to the responsible party, and analyzing patterns that reveal systemic gaps your site can fix.

What you will learn3 objectives

By the end of this lesson, you will be able to:

Design a stipulation and modification tracking system that captures every post-approval IRB requirement, assigns responsibility, sets deadlines, and monitors completion to closure, referencing ICH E6(R3) Annex 1, Section 1.4.9
Analyze recurring stipulation patterns across the portfolio to identify systemic process gaps that drive IRB concerns
Implement a communication routing workflow with escalation paths for items not resolved within defined timelines

Progress saves itself — finish reading and this lesson completes

Continue with the Regulatory Coordinator track

Approval is not the end of the conversation