Sign inJoin Free
DashboardSign out
Regulatory Coordinator1 of 6
Free Lesson Preview
Module 1: Lesson 1
The regulatory function defined: what investigator sites must do, and who is responsible
Maps the complete regulatory obligation set under ICH E6(R3) that falls on an investigator site, categorizes obligations by function, traces cascading dependencies, and identifies where the RC's domain begins.
Before you build, you survey
Consider what happens at a site running 18 active studies when the institutional review board approval for one protocol lapses by a single day. The investigator cannot enroll the next participant who was scheduled for screening that morning. But the cascade does not stop there. The coordinator who was preparing informed consent materials for that participant now has nothing to consent to. The data manager expecting screening data has a gap. The sponsor's enrollment timeline slips. And the investigator -- who signed the FDA Form 1572 attesting to IRB oversight -- is now technically in noncompliance with 21 CFR 56.103, regardless of whether anyone at the site noticed the lapse.
One missed renewal date. Six downstream failures. This is not a hypothetical constructed to alarm you -- it is an unremarkable Tuesday at a busy research site that lacks a regulatory system.
If you are stepping into a regulatory coordinator role, your instinct will be to start doing things: filing submissions, organizing binders, tracking deadlines. That instinct is understandable, and it is premature. Before you can build an effective regulatory operation, you must first understand what the operation is for -- the complete set of regulatory obligations that falls on an investigator site, how those obligations depend on one another, and where the boundary sits between what the investigator must do personally and what can be operationally delegated. That is the work of this lesson.
What you will learn
By the end of this lesson, you will be able to:
The obligation landscape: six functional categories
ICH E6(R3) Annex 1, Sections 2.1 through 2.13, enumerates the investigator's responsibilities across more than 60 discrete requirements. If you read them in order -- qualification, resources, responsibilities, communication, compliance, termination, safety, consent, records, reports -- the sheer volume can feel arbitrary, as though each section were an isolated rule dropped onto the site from a great height.
But these are not isolated rules. They are the components of a regulatory system. And the first step toward operating that system intelligently is to reorganize these obligations by function -- by what they actually require the site to do -- rather than by the section numbers that happen to contain them.
I find it useful to think of the site's regulatory obligations as falling into six functional categories. This is not the only way to organize them, and ICH did not design these sections with this taxonomy in mind. But in over three decades of teaching investigators and site staff, this categorization reflects how obligations actually generate work at the site level -- which is ultimately what matters when you are the person responsible for making sure the work gets done.
Reference Table
Six functional categories of investigator site regulatory obligations
Functional category | What it requires | Key E6(R3) sections |
|---|---|---|
Qualification | The investigator and all delegated staff must be qualified by education, training, and experience. The site must demonstrate adequate resources, facilities, and recruitment potential. | Sections 2.1.1, 2.1.2, 2.2.1, 2.2.2, 2.3.2 |
Oversight & delegation | The investigator retains ultimate responsibility for trial conduct and must maintain proportionate oversight of all delegated activities. Delegation must be documented. | Sections 2.3.1, 2.3.3, 2.3.4, 2.3.5; Principle 10 (10.1--10.3) |
IRB/IEC communication | The site must obtain and maintain IRB/IEC approval, submit updates and safety information, report protocol deviations, and notify the IRB/IEC of changes affecting conduct or risk. | Sections 2.4.1--2.4.6, 2.5.3--2.5.5, 2.13 |
Records & data integrity | The investigator must ensure data integrity, maintain source records per Section 2.12.2 attributes, protect confidentiality, manage computerized systems, and retain essential records. | Sections 2.12.1--2.12.14 |
Safety & medical care | A qualified physician must be responsible for medical decisions. The site must report adverse events per protocol timelines, report SAEs immediately, and ensure participant care during and after the trial. | Sections 2.7.1(a)--(d), 2.7.2(a)--(d) |
Informed consent | The investigator must obtain and document voluntary, informed consent before enrollment, maintain the consent process throughout participation, and manage re-consent when new information emerges. | Sections 2.8.1--2.8.13 |
What the categories reveal
The table above is worth studying carefully, because the categorization tells you something that reading the sections sequentially does not: the regulatory function is not primarily about paperwork. It is about maintaining six interconnected operational capacities simultaneously, across every active study, for the entire duration of each trial.
Qualification is not a one-time checkbox. Section 2.2.2 requires sufficient qualified staff for the foreseen duration of the trial. When a sub-investigator leaves the site mid-study, the qualification obligation re-activates: the delegation log must be updated, the replacement must be trained, and the IRB/IEC must be notified if required by local policy. A regulatory coordinator who thinks of qualification as "something we handled at study start-up" will miss this entirely.
Oversight and delegation is, in my view, the most underappreciated category. Section 2.3.1 establishes a principle that shapes everything else the site does: the investigator may delegate activities, but retains ultimate responsibility and must maintain appropriate oversight proportionate to the importance of the data and the risks to participant safety. This is not bureaucratic language. It means that every delegated task -- every consent discussion conducted by a coordinator, every adverse event assessed by a sub-investigator, every regulatory submission prepared by an RC -- exists within an accountability structure that traces back to one person. Understanding this structure is essential to understanding what the RC role is and what it is not.
IRB/IEC communication generates more recurring operational work than any other category. Sections 2.4.1 through 2.4.6 create a continuous dialogue between the site and its reviewing body: initial approval, continuing review, amendments, safety notifications, status reports, and prompt communication of anything that changes conduct or increases risk. For a site running 18 studies, each with its own review cycle, amendment schedule, and safety reporting obligations, this single category can consume the majority of a regulatory coordinator's working hours.
Cascading dependencies: why the system metaphor matters
The six categories are not independent departments that happen to coexist at the same site. They are operationally dependent on one another in ways that create cascading failure chains. When one domain fails, it does not simply create a problem in that domain -- it forces stops or degradations in others.
This is the single most important insight for a regulatory coordinator to internalize. The regulatory function is a system, and systems fail in systemic ways.
Figure 1: Cascading dependencies between regulatory obligation domains -- a single failure propagates across the system
Three dependency chains illustrate this principle with particular clarity.
IRB/IEC approval is the master dependency. Per Section 2.4.2, the site must have documented IRB/IEC approval before initiating a trial. But this is not merely a start-up requirement. The approval must remain current throughout the trial's duration. If continuing review approval lapses -- even by a single day -- the site cannot enroll new participants, cannot obtain new consents, and under many institutional policies, cannot administer investigational product to already-enrolled participants. The consent domain, the safety domain, and the records domain all depend on the IRB/IEC communication domain being current. One missed renewal date halts an entire study.
Qualification failures propagate through delegation. If a sub-investigator's medical license expires, or if a coordinator's required GCP training lapses, the delegation under Section 2.3.1 becomes unsupported. That person can no longer perform delegated trial activities until the qualification gap is resolved. If that person was the only staff member trained to obtain informed consent for a particular study, the consent process stops. If that person was responsible for assessing adverse events, the safety reporting chain weakens. The qualification domain feeds the oversight domain, which feeds every operational activity at the site.
Protocol compliance depends on consent integrity. Section 2.5.2 requires the investigator to comply with the protocol. But many protocol procedures -- blood draws, imaging, administering questionnaires -- require a participant who has provided valid informed consent. If the consent process was deficient (Section 2.8), the data generated from those procedures may be unreliable or unusable. The consent domain does not merely protect the participant's rights. It underwrites the integrity of every data point the site collects.
The nondelegable boundary: where the investigator's personal responsibility ends and the RC's operational domain begins
Section 2.3.1 is one of the most consequential passages in all of E6(R3) for understanding the regulatory coordinator role. It establishes two principles simultaneously: the investigator may delegate trial-related activities, and the investigator retains ultimate responsibility regardless of delegation. These principles are not in tension. They define a boundary.
On one side of that boundary sits a set of responsibilities that the investigator must fulfill personally -- responsibilities that cannot be delegated because they require the investigator's professional judgment, medical expertise, or personal attestation. On the other side sits the vast operational infrastructure required to enable those responsibilities: the tracking, the filing, the monitoring, the coordinating, the system-building that makes the investigator's personal responsibilities possible to discharge across a portfolio of concurrent studies.
The RC lives on the operational side of that boundary. But to work effectively there, you must understand precisely where the line falls.
Nondelegable investigator responsibilities versus delegable operations
The investigator must personally sign the protocol or alternative agreement with the sponsor, confirming willingness to comply. The investigator must personally comply with the protocol, GCP, and applicable regulatory requirements. The RC cannot sign the protocol on the investigator's behalf, and the RC cannot make clinical decisions about protocol compliance. However, the RC can prepare the protocol package for the investigator's review, track protocol deviations across the portfolio (Section 2.5.3), and ensure the investigator is aware of deviations that require their assessment.
A qualified physician or dentist who is an investigator or sub-investigator must have responsibility for trial-related medical care and decisions. The RC cannot make medical judgments about participant care. However, the RC can build and maintain the systems that ensure safety reports reach the investigator promptly, that reporting timelines are tracked, and that the documentation of the investigator's medical assessments is complete and timely.
All serious adverse events must be reported immediately to the sponsor, and the investigator must include an assessment of causality. This clinical judgment -- whether the SAE is related to the investigational product -- is a medical determination that cannot be delegated to non-physician staff. The RC's role is to ensure the reporting infrastructure works: that SAE forms are accessible, that reporting timelines are tracked, that follow-up information is submitted, and that the IRB/IEC receives required notifications.
The investigator must review and endorse data accuracy, completeness, and timeliness at milestones agreed upon with the sponsor (for example, before interim analyses or database lock). This endorsement is a personal attestation that cannot be performed by proxy. The RC can schedule the data review, ensure the investigator receives the data package requiring review, and document the endorsement -- but cannot endorse data on the investigator's behalf.
While the investigator or institution submits to the IRB/IEC, the operational work of preparing submissions, tracking approval timelines, compiling required documents, and managing the continuing review calendar can be delegated to qualified site staff. This is core RC territory -- the systematic management of the IRB/IEC dialogue across every study in the portfolio.
The investigator must ensure delegation records are maintained and that delegated staff are qualified and trained. The operational work of maintaining the record of delegation -- the document E6(R3) Section 2.3.3 requires, commonly called the 'delegation log' in industry practice -- tracking training completion dates, ensuring training is protocol-specific per Section 2.3.2, and documenting agreements with service providers can be assigned to the RC. The investigator oversees; the RC operates.
Maintaining essential records per Appendix C, ensuring retention compliance, managing access for monitors and auditors, and informing the sponsor of changes to the responsible records custodian -- all of this operational infrastructure is delegable. The RC typically owns this domain entirely, with the investigator providing oversight proportionate to the data's importance.
E6(R3) Section 2.7.2(d) explicitly states that the investigator 'may delegate activities for safety reporting to qualified investigator site staff but retains the overall responsibility for safety of participants.' The RC can manage the reporting workflow -- ensuring forms are completed, timelines are met, follow-ups are tracked -- while the investigator retains responsibility for the clinical assessments within those reports.
The nondelegable/delegable boundary is not a limitation on the RC's role. It is the definition of the RC's role. Everything on the delegable side of that boundary -- the submission tracking, the document management, the training oversight, the reporting infrastructure, the deadline monitoring, the inspection readiness -- is operational work that the investigator cannot realistically perform personally across a portfolio of studies. Someone must build and maintain the systems that make the investigator's nondelegable responsibilities possible to fulfill. That someone is the regulatory coordinator.
And this framing matters for another reason that I think is often overlooked: it protects both parties. The investigator cannot later claim that regulatory failures were "the RC's responsibility" -- because Section 2.3.1 makes clear that the investigator retains ultimate responsibility regardless of delegation. And the RC cannot be placed in the position of making medical or clinical judgments that exceed their qualification -- because the nondelegable boundary reserves those decisions for the investigator. The line is protective in both directions.
The obligation landscape as a system
Step back now and consider the full picture. An investigator site conducting clinical trials under ICH E6(R3) must simultaneously maintain:
- Qualified, trained personnel with documented delegations for every active study
- Active IRB/IEC approval with continuous communication across initial review, continuing review, amendments, safety reports, and status updates
- Protocol compliance with documented deviations and immediate hazard procedures
- A functioning safety reporting infrastructure with immediate SAE notification and investigator causality assessment
- Valid informed consent for every enrolled participant, with re-consent processes for emerging safety information
- Source records meeting Section 2.12.2 integrity attributes, protected data systems, essential record retention, and inspection-ready files
These six capacities are interdependent. They must be maintained concurrently across every study in the portfolio. And they must be current -- not completed at some point in the past, but operational right now, today, for every active protocol.
This is the regulatory function. Not a set of tasks to complete. Not a binder to fill. A living operational system that requires continuous management and that fails in cascading, interconnected ways when that management breaks down.
The next lesson will build directly on this obligation map. It examines how the same requirements you have just studied change character when you shift from thinking about them study-by-study to thinking about them across an entire portfolio -- and why that shift from task execution to systems management is the defining characteristic of what makes a regulatory coordinator's work fundamentally different from a coordinator's regulatory tasks.
Test your understanding
An investigator site has 12 active studies. A coordinator who obtains informed consent for three of those studies allows their GCP training to lapse without notifying anyone. Which obligation domains are directly affected?
Key takeaways
The investigator site's regulatory obligations under ICH E6(R3) are not a collection of independent requirements. They form an interconnected system organized around six functional capacities: qualification, oversight and delegation, IRB/IEC communication, records and data integrity, safety and medical care, and informed consent. These capacities depend on one another -- a failure in one domain cascades into enforced stops in others.
The investigator retains ultimate responsibility for all trial conduct under Section 2.3.1, but may delegate operational activities to qualified staff with proportionate oversight. The regulatory coordinator works on the delegable side of this boundary, building and maintaining the operational infrastructure that makes it possible for the investigator to fulfill nondelegable responsibilities across a multi-study portfolio.
Understanding this complete obligation landscape -- as a system, not a checklist -- is the prerequisite for everything that follows in this course.
Enjoyed this preview?
Enroll to access all courses in the Regulatory Coordinator track.
Unlock the full course