Regulatory Coordinator

Full course · The Regulatory Coordinator: Role, Scope & Professional Identity

Working with CRCs: delegation, oversight, and the handoff boundaries that matter — The Regulatory Coordinator: Role, Scope & Professional Identity

Working with CRCs: delegation, oversight, and the handoff boundaries that matter

Examines the RC-CRC working relationship from the RC's perspective: delegation design, handoff documentation, and proportionate oversight

20 min

The delegation you design

The previous lesson addressed the relationship that sits above you in the accountability chain: the principal investigator whose authority you support but do not assume. This lesson addresses the relationship that sits below: the clinical research coordinators whose execution you direct but do not micromanage. And if you think the word "below" implies this relationship is simpler than the PI partnership, you have not yet managed a regulatory handoff that failed at 4:47 p.m. on the Friday before a monitoring visit.

The RC-CRC boundary is, in my experience, where more regulatory errors originate than at any other handoff point in the site's operation. Not because CRCs are careless -- they are, as a group, among the most conscientious professionals in clinical research. And not because RCs fail to communicate -- most communicate constantly. The errors originate because the boundary itself is poorly designed. Tasks are divided by custom rather than by analysis. Handoffs rely on assumptions rather than documentation. Oversight is either absent or suffocating, rarely calibrated.

Here is the core principle: the delegation framework between the RC and the CRC is something you design. It is not inherited from the previous RC. It is not dictated by "how we have always done it." It is not improvised study by study. Under ICH E6(R3) Annex 1, Section 2.3.2, the investigator must ensure that individuals to whom tasks are delegated are qualified by education, training, and experience. Under Section 2.3.3, the investigator must maintain a record of delegation documenting persons to whom trial-related activities have been delegated, proportionate to the significance of those activities. As the person who operationalizes these requirements at portfolio scale, the RC is the architect of how regulatory work flows between roles -- what gets delegated, what gets retained, what gets checked, and what documentation travels with each handoff.

What you will learn3 objectives

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

Design a delegation framework for regulatory tasks between RC and CRC roles, specifying which are appropriate for CRC execution, which require RC oversight, and which the RC must retain, per E6(R3) Sections 2.3.1-2.3.3
Create handoff documentation standards for the RC-CRC boundary, defining what information must transfer to prevent gaps where responsibilities fall between roles
Evaluate RC oversight mechanisms for CRC regulatory work, distinguishing constructive oversight from surveillance that undermines CRC autonomy, per Principle 7

Progress saves itself — finish reading and this lesson completes

Continue with the Regulatory Coordinator track

The delegation you design