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.

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.