Sponsor and CRA communication: approval notifications, document routing, and the regulatory timeline as a shared accountability
Designs standardized notification workflows per ICH E6(R3) Sections 3.8.2 and 3.11.4, applies proactive delay communication, and analyzes the three tiers of information flow — regulatory-required, contractual, and relationship-building.
The approval letter that sat in a drawer for three weeks
Here is a scenario I have encountered more times than I care to count. An IRB approves an amendment. The approval letter arrives — by email, by portal notification, by whatever mechanism the IRB uses. The coordinator who processes the incoming correspondence files the approval letter in the regulatory binder. And then nothing happens. The sponsor is not notified. The CRA does not receive the approved documents. The amendment — which may authorize a new dosing schedule, a revised consent form, or an expanded eligibility criterion — is not implemented at the site because no one closed the loop.
Three weeks later, the CRA contacts the site asking about the amendment status. The RC (or the CRC, depending on how the site is structured) discovers that the approval was received, filed, and forgotten. The amendment implementation is now three weeks behind. The sponsor is frustrated. The CRA notes it in the monitoring report. And the site's reputation — that intangible but profoundly consequential currency in the sponsor-site relationship — takes a hit.
This is not a knowledge failure. Everyone involved knew that sponsor notification was required. It is an infrastructure failure. The site lacked a systematic process for ensuring that every IRB action generates the appropriate outbound communication to every affected stakeholder. And at the portfolio level — where the RC is processing IRB communications for 15 or 20 studies simultaneously — these gaps are not exceptional. They are inevitable, unless the infrastructure prevents them.
Course 1 established the sponsor as a key stakeholder in the RC's professional ecosystem. This lesson operationalizes that relationship for the communication demands of the submission process: what must be communicated, to whom, when, and through what mechanism — across every study in the portfolio, every time.
What you will learn
By the end of this lesson, you will be able to: