Clinical Research CoordinatorCourse 1 of 8

Clinical Research Coordinator

Full course · The CRC Role: Foundations and Career Path

Communicating with sponsors, IRBs, and regulatory authorities — The CRC Role: Foundations and Career Path

Communicating with sponsors, IRBs, and regulatory authorities

Master the communication protocols and documentation standards for interactions with sponsors, IRBs/IECs, and regulatory bodies, including when to escalate and what to put in writing.

22 min

The email that needed two different answers

A coordinator opens the inbox on a Tuesday morning to find two messages about the same protocol amendment. The first is from the sponsor's clinical operations team: "Please begin implementing Protocol Amendment 4 at your site immediately. The amendment removes the fasting requirement for Visit 6 bloodwork and adds a new patient-reported outcome measure at Visit 8. Updated case report forms are available in the EDC." The second is from the IRB, timestamped an hour later: "Our records indicate that your site has not yet submitted Protocol Amendment 4 for review. Please submit the amendment with tracked changes, updated consent form, and a summary of modifications before implementing any changes at your site."

The coordinator stares at both messages. The sponsor says implement now. The IRB says not so fast. And both of them are, within their respective frameworks, correct. The sponsor has approved the amendment at the global level and wants sites to adopt it without delay. The IRB has not yet reviewed the amendment at the local level and cannot authorize changes to participant-facing procedures until it does. The coordinator is caught in the middle -- not because anyone made an error, but because the sponsor and IRB operate on different timelines, with different authorities, and with different communication expectations.

This is not an unusual situation. It is, in fact, one of the defining challenges of the CRC role: sitting at the intersection of multiple authorities that do not always coordinate their instructions with each other. The sponsor directs. The IRB oversees. The regulatory authority governs. And the coordinator must communicate with all of them, in the right way, at the right time, through the right channels, with the right documentation. Get any of those wrong and you create confusion at best, compliance failures at worst.

In the previous lesson, we examined the CRC-CRA relationship -- a dynamic built on shared operational space and repeated face-to-face interactions. The relationships we turn to now are different. Communication with sponsors, IRBs, and regulatory authorities is largely formal, often asynchronous, and governed by protocols that leave less room for improvisation. The skills are different. The stakes, if anything, are higher.

What you will learn4 objectives

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

Distinguish the communication protocols appropriate for sponsor, CRO, and IRB/IEC interactions, including formality levels and documentation requirements
Identify which types of communications must be in writing versus those that may be handled verbally
Apply an escalation decision framework to determine when an issue requires sponsor notification, IRB reporting, or both
Describe the common regulatory submission types the CRC manages and the documentation standards for each

Progress saves itself — finish reading and this lesson completes

This is just the beginning

The email that needed two different answers