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.

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.