Clinical Research Coordinator Responsibilities: A Delegation-Mapped Guide to Staying In Scope for an FDA Inspection

At a glance

• A clinical research coordinator (CRC) does not “own” a fixed list of tasks. Every task a CRC performs is a slice of the investigator’s responsibility that has been delegated, documented, and matched to evidence the CRC was qualified to perform it.
• The investigator may delegate trial-related activities, but ICH E6(R3) §2.3.1 says the investigator retains ultimate responsibility and oversight. The delegation log and the Form FDA 1572 are where that chain is written down.
• Some duties cannot be handed to a CRC at all: trial-related medical care and medical decisions rest with a qualified physician investigator or sub-investigator (ICH E6(R3) §2.7.1).
• The tasks that get sites cited in an FDA Bioresearch Monitoring (BIMO) inspection are usually the ones a coordinator performed without proper delegation, training evidence, or oversight, not exotic edge cases.
• This guide maps the core CRC responsibility areas to their regulatory basis, contrasts what a PI may and may not delegate, names the BIMO 483 hot spots, and closes with an “am I operating in scope?” self-check you can run at your own site.

The CRC role in one sentence

A clinical research coordinator operationalizes the investigator’s delegated duties; the role is not a standalone job defined by a generic task list. Under 21 CFR 312.60, the investigator is responsible for ensuring the investigation is conducted according to the signed investigator statement, the investigational plan, and applicable regulations, for protecting subjects, and for controlling the investigational drug. When you, as a CRC, perform a study task, you are executing part of that responsibility on the investigator’s behalf. That framing changes everything: your job description is not the source of your authority. The delegation record is.

The accountability chain: sponsor to investigator to CRC

The chain has three links, and each one is documented.

The sponsor selects the investigator. 21 CFR 312.53(c) requires the sponsor, before letting an investigator begin, to obtain a signed investigator statement (Form FDA 1572) in which the investigator commits to conduct the study per the protocol, 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 last commitment is the regulatory hook for the entire site staff, including the CRC.

The investigator then delegates specific activities to site staff. ICH E6(R3) §2.3.1 states that the investigator may delegate trial-related activities but retains the ultimate responsibility and should maintain appropriate oversight proportionate to the importance of the data and the risk to participants. ICH E6(R3) §2.3.3 requires that a record be maintained of the persons and parties to whom activities were delegated. In practice this is the delegation of authority log.

A monitor or FDA inspector reads that chain backward: from a task that was performed, to the person who performed it, to the log entry that authorized it, to the training and qualification evidence behind it. The FDA BIMO compliance program 7348.811 instructs inspectors, where there are concerns about appropriate delegation, to obtain the curriculum vitae, license, and delegation of authority log to evaluate the qualifications and training of the person who performed the delegated task and the investigator’s oversight. If any link is missing, the chain breaks at your site.

What the PI may delegate to a CRC

ICH E6(R3) §2.3.1 establishes that delegation is allowed. The constraint is not whether a task can be delegated but whether the delegation was properly recorded and the delegate properly prepared. Two companion provisions set the bar:

• ICH E6(R3) §2.3.2 requires the investigator to ensure that delegated persons are appropriately qualified and adequately informed about the protocol, the investigational product, and their assigned activities, with training that corresponds to what is necessary for activities going beyond their usual training and experience.
• ICH E6(R3) §2.3.3 requires that the delegation record exist and that its detail be proportionate to the significance of the activity.

Typical delegable CRC responsibility areas, each tied to a regulatory basis:

• Supporting the informed consent process. ICH E6(R3) §2.8.5 allows the informed consent process to be conducted by the investigator or by investigator site staff delegated by the investigator. A CRC may run the consent discussion if delegated and qualified; the act is not reserved to the PI by ICH E6(R3), but it must be on the log.
• Source documentation and data entry. ICH E6(R3) §2.12.2 requires adequate source records that are attributable, legible, contemporaneous, original, accurate, and complete, with traceable changes. CRC-entered data sits squarely here.
• Investigational product accountability tasks. ICH E6(R3) §2.10.2 permits the investigator to delegate some or all IP-management activities to a pharmacist or another individual under the investigator’s oversight, and ICH E6(R3) §2.10.4 specifies the delivery, inventory, per-participant use, and return records that must be kept.
• Adverse event capture and onward reporting to the sponsor. ICH E6(R3) §2.7.2(a) requires adverse events and abnormal results needed for safety evaluation to be reported to the sponsor per the protocol’s requirements and timelines.
• Essential records and protocol-deviation documentation. ICH E6(R3) §2.5.3 requires the investigator to document all protocol deviations; a CRC commonly maintains that documentation under delegation.

What the PI may not delegate

This is where coordinators most often drift out of scope without realizing it.

Medical care and medical decisions are not delegable to a non-clinician. ICH E6(R3) §2.7.1(a) states that a qualified physician (or, where appropriate, a qualified dentist or other qualified healthcare professional per local requirements) who is an investigator or sub-investigator should be responsible for trial-related medical care and decisions. Eligibility judgments that turn on clinical assessment, causality assessment of an adverse event, and treatment decisions fall on that clinician, not on the CRC.

Ultimate accountability is non-transferable. ICH E6(R3) §2.3.1 is explicit that the investigator retains ultimate responsibility even for delegated activities. The Form FDA 1572 reinforces this at the US level: 21 CFR 312.53(c) records the investigator’s personal commitment to conduct or supervise the study. Note a genuine tension here worth stating plainly rather than smoothing over. ICH E6(R3) §2.3.3 says delegation documentation should be proportionate and that, where activities are performed as part of clinical practice, delegation documentation may not be required. The US frame is less forgiving: 21 CFR 312.61 requires that the investigational drug be administered only to subjects under the investigator’s personal supervision or the supervision of a subinvestigator responsible to the investigator, and 21 CFR 312.53(c) extracts a personal supervision commitment on the 1572. For a study under a US IND, do not lean on the ICH “may not be required” clause to skip a log entry; the 1572 supervision commitment and BIMO’s delegation-log expectation set the practical floor.

Assurance of independent ethical review stays with the investigator. 21 CFR 312.66 requires the investigator to assure that an IRB will conduct initial and continuing review and that the investigator will not change the research without IRB approval except to eliminate immediate hazards. A CRC may handle IRB submissions operationally, but the assurance is the investigator’s.

Core responsibilities mapped to regulation

Responsibility	Regulatory basis	Delegable to CRC?	Required record
Conduct of study per protocol and plan	21 CFR 312.60; ICH E6(R3) §2.5.2	No (investigator accountability); execution support yes	Signed 1572; delegation log
Informed consent process	ICH E6(R3) §2.8.5	Yes, if delegated and qualified	Delegation log entry; signed/dated consent (ICH E6(R3) §2.8.7)
Trial-related medical care and decisions	ICH E6(R3) §2.7.1(a)	No (qualified physician/sub-I)	Investigator/sub-I on delegation log; CV; license
Source records and data accuracy	ICH E6(R3) §2.12.2, §2.12.5	Yes	Source documents; data acquisition tool entries
IP accountability	ICH E6(R3) §2.10.2, §2.10.4	Yes, under oversight	IP delivery, inventory, per-subject use, return records
AE/SAE capture to sponsor	ICH E6(R3) §2.7.2(a); 21 CFR 312.64(b)	Yes (capture); SAE assessment needs clinician	AE log; SAE reports per protocol timeline
Onward IND safety reporting to FDA	21 CFR 312.32	No (sponsor obligation)	Sponsor IND safety reports
Protocol deviation documentation	ICH E6(R3) §2.5.3	Yes	Deviation log
IRB assurance	21 CFR 312.66	No (investigator)	IRB approvals; continuing review records

Where coordinators get cited: the BIMO 483 hot spots

FDA’s BIMO program 7348.811 exists to protect subjects’ rights, safety, and welfare and to verify the accuracy and reliability of clinical study data submitted to FDA. Its inspection procedures point straight at the places a CRC’s work can generate a Form 483 observation.

• Undelegated or improperly delegated tasks. FDA BIMO 7348.811 directs inspectors to determine whether the authority for the conduct of the study was delegated properly so that the clinical investigator retained control and knowledge, and to pull the delegation of authority log, CVs, and licenses when delegation is in question. A task you performed that is not on the log, or that is on the log without training evidence behind it, is the classic finding.
• Consent process and timing. FDA BIMO 7348.811 instructs inspectors to verify that the subject or the subject’s legally authorized representative signed the IRB-approved informed consent document prior to initiation of any study-related procedures. ICH E6(R3) §2.8.7 requires the consent form to be signed and dated before participation by the person who conducted the discussion. A screening procedure done before a valid signature is a high-frequency citation.
• Source-data discrepancies. FDA BIMO 7348.811 has inspectors compare source documents with case report forms to find the source of any error. ICH E6(R3) §2.12.6 requires reported data to be consistent with source records or the discrepancies explained, with traceable, non-obscuring changes. Sloppy transcription and unexplained corrections surface here.
• Untimely or broken safety reporting. The investigator must immediately report serious adverse events to the sponsor under 21 CFR 312.64(b), and the sponsor carries the onward IND safety reporting duty to FDA under 21 CFR 312.32. A CRC who captures an SAE but lets it sit, or routes it incorrectly, can break a chain that ends in a regulatory finding.

The proof-of-qualification trail

A delegation log entry is necessary but not sufficient. ICH E6(R3) §2.3.2 requires that delegated staff be appropriately qualified and adequately informed, with training corresponding to what their assigned activities require. ICH E6(R3) §2.1.1 sets the parallel expectation for the investigator: qualified by education, training, and experience, with evidence of those qualifications. The records that prove your qualification trail include a current CV, study-specific and protocol-specific training documentation, GCP currency, and a delegation log that shows the date you were authorized for each task and the investigator’s oversight. When a monitor cross-checks tasks performed against tasks delegated, this is the file they open. FDA BIMO 7348.811 makes the same documents the inspector’s evidence base for evaluating qualifications, training, and oversight.

The “am I operating in scope?” self-check

Run this for each task you routinely perform. If any answer is no, raise it with your PI or site manager before the next monitoring visit, not after the 483.

1. Is the task written on the current delegation of authority log next to my name, with an effective date on or before the first time I performed it? (ICH E6(R3) §2.3.3)
2. Is there training documentation showing I was prepared for this specific task, beyond my general experience? (ICH E6(R3) §2.3.2)
3. If the task involves a medical judgment, eligibility-determining clinical assessment, or causality assessment, is it actually assigned to a qualified physician investigator or sub-investigator rather than to me? (ICH E6(R3) §2.7.1(a))
4. For consent, did the subject sign the current IRB-approved form before any study-related procedure, and was the discussion conducted by a delegated, qualified person? (ICH E6(R3) §2.8.5, §2.8.7; verified at inspection per FDA BIMO 7348.811)
5. Can my source-to-CRF trail withstand a line-by-line comparison, with every change traceable and explained? (ICH E6(R3) §2.12.6)
6. For a US IND study, does my supervision and oversight reflect the investigator’s personal supervision commitment, rather than relying on the ICH “documentation may not be required” clause? (21 CFR 312.61; 21 CFR 312.53(c))

A clean answer to all six does not certify your site as compliant, and no document or checklist can: the sponsor and investigator remain responsible for conduct under 21 CFR 312.60. What these questions do is surface the scope and delegation gaps that a BIMO inspector would otherwise find for you. For deeper treatment of adjacent topics, see our companion guidance on the delegation of authority log, the informed consent process, protocol deviation handling, and SAE and expedited safety reporting.

Sources

• ICH E6(R3) Good Clinical Practice, version r3 — ICH — https://www.ich.org/page/efficacy-guidelines
• 21 CFR Part 312 Investigational New Drug Application, version 2026-04 — FDA
• FDA Compliance Program 7348.811, Bioresearch Monitoring: Clinical Investigators and Sponsor-Investigators, version 2020 — FDA — https://www.fda.gov/media/75927/download