The Clinical Research Coordinator as a GCP-Accountability Map: Which CRC Duties Carry Regulatory Weight Under ICH E6(R3) and 21 CFR 312

At a glance

• The clinical research coordinator (CRC) is not an independent regulatory role. The CRC executes trial-related activities under the investigator’s delegated authority, and the investigator keeps ultimate responsibility for everything the coordinator touches.
• Almost every core CRC task (consent administration, source data, adverse event capture, essential-document upkeep) maps to a specific ICH E6(R3) investigator obligation or a 21 CFR Part 312 commitment the PI signed on the Form FDA-1572.
• A few duties can be delegated to the coordinator but never assumed by them: the PI’s protective duty for subjects, the PI’s signed 1572 commitments, and obtaining valid informed consent all stay with the investigator even when the CRC runs the visit.
• FDA’s BIMO clinical-investigator inspection program (7348.811) reads the delegation-of-authority log, the informed consent documentation, and the source-to-CRF data trail. These are exactly where coordinators show up in findings.
• The CRC, the clinical trial coordinator, and the clinical research associate (the monitor) are three different jobs: the CRC and CTC run the site under the PI; the CRA oversees the site on behalf of the sponsor.
• “Senior” or “CRC-II” is a scope-and-judgment ladder, not a separate regulatory status. The regulations care about whether a task was properly delegated and properly supervised, not about a title.

If you are an early-career coordinator, you have read a dozen pages that list what a CRC does. This one does something different. It treats each duty as a line item in a GCP-accountability map: the task you perform, the regulation that makes it mandatory, and the part of that obligation the principal investigator can never hand off. Read this way, your job stops being a list of chores and becomes a map of where your accountability ends and the PI’s begins.

The CRC is the PI’s delegated hands

Start with the structural fact that every job-description page skips. The coordinator has no freestanding authority in the regulations. You act because the investigator delegated activities to you, and that delegation is bounded.

ICH E6(R3) §2.6 (Investigator Responsibilities) states that the investigator may delegate trial-related activities to other persons or parties, but retains the ultimate responsibility and should maintain appropriate oversight of the persons to whom activities are delegated to ensure participant rights, safety and well-being and the reliability of data. The level of that oversight should be proportionate to the importance of the data and the risk to participants. In plain terms: the more safety-critical or data-critical your task, the more closely the PI is expected to watch it.

The same section requires that the investigator ensure delegated staff are appropriately qualified and adequately informed about the protocol, the investigational product, and their assigned activities, with training corresponding to what is necessary to fulfil activities that go beyond their usual training. It also requires that a record be maintained of the persons to whom activities have been delegated, with documentation proportionate to the significance of those activities. That record is your delegation log, and it is the document an inspector will reach for first.

On the FDA side, 21 CFR §312.53 requires the sponsor to obtain a signed investigator statement (Form FDA-1572) before the investigator begins, in which the investigator commits to personally conduct or supervise the investigation and to ensure that all associates, colleagues, and employees assisting in the study are informed about their obligations. That clause is the legal hook that puts you inside the PI’s accountability. You are one of those associates, and the PI’s signature is a promise to supervise you.

The duty-to-regulation map

This is the centerpiece. Each row is a duty that typically lands on the coordinator’s desk, the regulatory obligation it discharges, the residual that stays with the PI, and where it tends to surface in an FDA inspection.

CRC duty	What it discharges	Governing reg + citation	Non-delegable PI residual	Common inspection finding
Run the informed consent visit; collect signatures	The site’s consent obligation	ICH E6(R3) §2.8.5 (process conducted by investigator or delegated site staff); 21 CFR §312.60 (investigator shall obtain informed consent per part 50)	The PI’s duty to obtain valid consent and to protect subject rights, safety and welfare	Wrong/expired consent version used; procedures started before signature
Maintain source records and enter data into the eCRF	Accurate, reliable trial data	ICH E6(R3) §2.12 (source records ALCOA: attributable, legible, contemporaneous, original, accurate, complete); 21 CFR §312.62 (adequate and accurate case histories)	The PI’s responsibility for the reliability of data and for case histories	Source-to-CRF discrepancies; data not consistent with source
Recognize and document adverse events; flag SAEs	Timely safety signal to the sponsor	ICH E6(R3) §2.7.2 (AEs/SAEs reported to sponsor; SAEs immediately; investigator delegates but retains responsibility); 21 CFR §312.64	The PI’s responsibility for safety reporting and causality assessment	Late or missed SAE reporting; AEs not captured in records
Keep essential documents and the delegation log current	An auditable trial record	ICH E6(R3) §2.12 / Guideline 66 (essential documents); §2.6 (delegation records)	The PI’s oversight that delegated staff are qualified and the record is maintained	Delegation log gaps; staff performing tasks not on the log
Route protocol changes and unanticipated problems to the PI/IRB	IRB-review assurance	21 CFR §312.66 (investigator assures IRB review; promptly reports changes and unanticipated problems; no changes without IRB approval)	The investigator’s assurance to the IRB; this commitment is the PI’s	Changes made without IRB approval; unanticipated problems not reported

Two reading notes. First, the right-hand columns matter more than the left. Anyone can list CRC tasks; the value is knowing the residual the PI keeps. Second, the citations are deliberately specific. If a page tells you the CRC “handles informed consent” without telling you that §2.8.5 lets the PI delegate the process while §312.60 still requires the investigator to obtain consent, it has shown you the task and hidden the accountability.

Informed consent: the duty the CRC runs but the PI still owns

This is the duty most coordinators run hands-on and the one most often misread as theirs.

ICH E6(R3) §2.8.5 is explicit that the informed consent process should be conducted by the investigator or other investigator site staff delegated by the investigator. So yes, you can run the consent discussion. But §2.8.7 says that by signing the consent form, the investigator or delegated site staff attests that consent was freely given and the information was accurately explained to and apparently understood by the participant. That attestation is a regulatory act, not a clerical one.

The non-delegable residual sits in 21 CFR §312.60, which states flatly that an investigator shall obtain the informed consent of each human subject to whom the drug is administered, in accordance with part 50. The FDA frames the obligation as the investigator’s even when a coordinator performs the discussion. The practical reading: you can conduct the conversation and collect the signature, but you cannot make the PI’s obligation disappear, and you cannot certify a process the PI is responsible for if the PI has not actually supervised it.

On the inspection side, FDA’s BIMO compliance program 7348.811 instructs investigators to review who explained the study and the consent document to subjects (clinical investigator, nurse, study coordinator, or other personnel) and whether the person obtaining consent was delegated this task by the clinical investigator. The inspector is checking your delegation against the consent record. If you consented a subject but the delegation log does not authorize you to, that gap is the finding.

Source data, eCRF entry, and the ALCOA expectations on the coordinator

The coordinator usually owns the keyboard, and that is where data integrity is won or lost.

ICH E6(R3) §2.12 requires the investigator/institution to maintain adequate source records and states that source records should be attributable, legible, contemporaneous, original, accurate and complete, with changes traceable, not obscuring the original entry, and explained via an audit trail. That is the ALCOA expectation expressed as a site obligation. The same section requires that data reported to the sponsor be consistent with the source records or that discrepancies be explained.

FDA’s 21 CFR §312.62 requires the investigator to prepare and maintain adequate and accurate case histories that record all observations and other data pertinent to the investigation on each individual, and defines case histories to include case report forms and supporting data such as signed and dated consent forms and medical records. Your eCRF entries are case histories under this rule, which is why a sloppy transcription is not a documentation nuisance but a regulatory gap.

Where teams get it wrong: treating the eCRF as the record and the chart as a formality. The regulation runs the other way. The source record is primary; the eCRF must reconcile to it. BIMO inspectors compare source records against the data line listings and CRFs for completeness and accuracy, and they treat unexplained source-to-CRF discrepancies as a possible signal of systemic data-management problems. The coordinator who fixes a value in the eCRF without an audit-trail-supported correction in the source has manufactured exactly that discrepancy.

AE/SAE recognition and the handoff to the PI’s reporting clock

This is the duty where a coordinator’s attentiveness has the highest stakes, and where the boundary with the PI is sharpest.

ICH E6(R3) §2.7.2 requires that adverse events and abnormal test results required for safety evaluations be reported to the sponsor per the protocol, and that all serious adverse events be reported immediately to the sponsor after the investigator reasonably becomes aware, with the investigator also providing an assessment of causality. Critically, §2.7.2(d) says the investigator may delegate safety-reporting activities to qualified site staff but retains the overall responsibility for participant safety and for compliance with the reporting requirements.

Read that boundary carefully. You can be delegated the mechanics of safety reporting. You cannot own the causality call or the responsibility for the reporting clock. The coordinator’s job is recognition and an immediate, clean handoff: you find the event at the visit, you document it, and you escalate it to the PI without delay so the investigator’s assessment and the sponsor-reporting timeline can run. 21 CFR §312.64 governs the investigator’s reports to the sponsor, and the 1572 commitment under §312.53 already binds the investigator to report adverse experiences in accordance with §312.64. Your value is making sure nothing the PI must report gets lost between the exam room and that clock.

BIMO 7348.811 reflects this at inspection: investigators review the documentation of adverse events, the assessment of severity and relationship to the investigational product, and whether reports were submitted to the sponsor in accordance with the protocol and applicable regulations. A coordinator who buries an AE in a progress note, or who lets an SAE sit over a weekend, is creating the finding the inspector is trained to look for.

Essential-document and TMF-facing housekeeping

The least glamorous duty is the one inspectors can read fastest.

ICH E6(R3) §2.12 and its essential-records guidance treat the documents that substantiate the existence of trial participants and the integrity of the data, and that document the recruitment, screening and consenting process, as essential. The delegation record itself is part of this set: §2.6 requires the investigator to maintain a record of who was delegated which activities. When you keep the delegation log, the regulatory binder, and the consent tracker current, you are maintaining the evidence that the trial was conducted under proper authority.

Where teams get it wrong: letting the delegation log lag reality. Staff rotate, a new coordinator starts running visits, and the log is updated weeks later. BIMO 7348.811 instructs investigators, when there are concerns about delegation, to obtain the delegation-of-authority log and information about the qualifications and training of the person who performed the delegated task, and to confirm that the clinical investigator retained control and knowledge of the study. A task performed by someone not yet on the log is, in inspection terms, a task performed without authority.

CRC vs CTC vs CRA: who does what, who oversees whom

These three get blurred constantly, and the regulations draw a clean line.

The clinical research coordinator (CRC) and the clinical trial coordinator (CTC) are essentially the same site-side role under different house styles. Both run the day-to-day conduct of the trial at the site under the investigator’s delegated authority: consent, visits, source data, AE capture, document upkeep. Under ICH E6(R3) §2.6 and the §312.53 1572 commitments, they are “investigator site staff” assisting the investigator.

The clinical research associate (CRA) is the monitor, and the monitor works for the sponsor, not the site. ICH E6(R3) §3.11.4 (Monitoring) describes monitoring activities including verification of investigator and site-staff qualifications, source data review, and source data verification, performed on the sponsor’s behalf to confirm that reported data are accurate, complete and verifiable from source. So when the CRA reviews your eCRF against source and raises a query, that is the sponsor’s oversight function checking the site’s work. The relationship is structural: the CRC produces the record, the CRA verifies it. They are not peers doing the same job from two desks.

The CRC-I / CRC-II / lead-coordinator scope ladder

Titles like CRC-I, CRC-II, senior, or lead coordinator describe scope, autonomy, and judgment. They are an employer’s ladder, not a regulatory tier.

The regulations are title-agnostic. ICH E6(R3) §2.6 cares about two things regardless of seniority: whether the person is appropriately qualified and adequately trained for the assigned activity, and whether that activity is recorded in the delegation log under proportionate oversight. A CRC-II is typically delegated broader or higher-risk activities (running complex consent, owning AE workflows, mentoring), which under the proportionality principle of §2.6 implies the PI should exercise correspondingly attentive oversight. But the regulatory test is the same one applied to a CRC-I: qualified, trained, delegated, supervised. Seniority changes what you may be delegated; it does not change the accountability map or move any of the PI’s residual obligations onto your desk.

Where BIMO inspections cite the coordinator

A short, blunt list of where coordinators actually show up in FDA clinical-investigator inspections, drawn from the 7348.811 program’s instructions to inspectors:

• Delegation gaps. The inspector pulls the delegation-of-authority log and checks whether the person who performed a task was authorized and whether the PI retained control and knowledge of the study. Tasks performed off-log are findings.
• Consent execution. The inspector reviews who obtained consent, whether they were delegated the task, whether the correct IRB-approved version was used, and whether the subject signed before any study-related procedures. Wrong-version and timing errors are classic coordinator-adjacent citations.
• Source-to-CRF data integrity. The inspector compares source records with CRFs and data line listings for completeness and accuracy, and treats unexplained discrepancies as a possible systemic signal.
• Adverse event documentation and reporting. The inspector reviews AE documentation, severity and relationship assessments, and whether events reached the sponsor per the protocol.

None of these “make you compliant” in the inverse sense either. Doing them well does not certify the trial; it removes the most common reasons the site gets cited. The investigator stays responsible for the conduct of the study throughout. Your job is to make sure that when the inspector reads the delegation log, the consent file, and the source-to-CRF trail back to you, the record holds.

A final framing for the new coordinator: the regulations never ask whether you are competent in the abstract. They ask whether each task you performed was properly delegated, properly supervised, and properly documented, and whether the PI’s non-delegable residual stayed with the PI. Keep that map in your head and the job stops being a list of duties and becomes a clear picture of where your accountability lives.

Sources

• ICH E6(R3) Good Clinical Practice, version r3 (ICH, effective 6 January 2025) — https://www.ich.org/page/efficacy-guidelines
• 21 CFR Part 312 Investigational New Drug Application, version 2026-04 (FDA, eCFR up to date as of 14 April 2026)
• FDA Compliance Program 7348.811, Bioresearch Monitoring: Clinical Investigators and Sponsor-Investigators, version 2020 (FDA, issued 22 July 2020) — https://www.fda.gov/media/75927/download