The CRC-CRA relationship: collaboration, not adversary
Understand the monitor's role and regulatory obligations, learn to prepare effectively for monitoring visits, and build a collaborative relationship that benefits both site performance and participant safety.
Two perspectives on the same morning
The monitor arrives at the site at 8:45 a.m., 15 minutes before the scheduled monitoring visit. She spent Sunday evening reviewing the site's data in the electronic data capture system, flagging 14 open queries, two consent form discrepancies, and an adverse event that was reported three days past the protocol-required timeline. She has a monitoring plan from the sponsor that specifies exactly which records she must verify, which processes she must confirm, and which deficiencies she must document in her report. Her job--per ICH E6(R3) Section 3.11.4--is to ensure that participant rights, safety, and well-being are protected and that the trial data are reliable. She is not here to judge. She is here to verify.
The coordinator sees the same morning differently. The regulatory binder is not quite where it should be because the IRB approval letter from the last amendment arrived Friday at 4:47 p.m. and has not been filed yet. Two of the three participants the monitor will review had complicated visits: one involved a dosing hold the investigator ordered verbally, and the coordinator is not entirely sure the documentation captures the conversation accurately. The coordinator knows the visit will surface findings. The question is whether those findings become a collaborative problem-solving exercise or a tense interrogation.
This is the CRC-CRA relationship in its essential form. Two professionals, employed by different organizations, with different reporting lines and different pressures, sitting in the same conference room trying to accomplish the same fundamental goal: a well-conducted trial that protects participants and produces reliable data. When the relationship works, monitoring visits are productive, findings are resolved efficiently, and both parties leave the room better informed. When it does not work--when defensiveness meets rigidity, or when silence meets suspicion--the trial suffers and so do the participants.
I have watched this relationship go wrong more times than I care to count, and almost always for the same reason: a failure of perspective. The coordinator who sees the monitor as an adversary will hide problems. The monitor who sees the coordinator as an obstacle will document findings without context. Both reactions are human. Both are professionally destructive. And both are avoidable, once you understand what the person across the table is actually required to do.
What you will learn
By the end of this lesson, you will be able to:
1
Explain the CRA's regulatory obligations per ICH E6(R3) Section 3.11.4 and how understanding these improves your collaboration as a CRC
2
Describe what constitutes effective monitoring visit preparation from the CRC perspective, including document readiness and scheduling
3
Identify common sources of CRC-CRA friction and apply strategies to build collaborative rather than adversarial relationships
4
Demonstrate how to respond professionally to monitoring findings without defensiveness
Understanding the CRA's regulatory obligations
Here is something that transformed my understanding of the CRC-CRA dynamic, and I think it will transform yours: the monitor is not choosing to scrutinize your work. The monitor is required to scrutinize your work. The distinction matters enormously.
ICH E6(R3) Section 3.11.4 establishes monitoring as "one of the principal quality control activities" in clinical trials. The aim of monitoring, per that section, is "to ensure the participants' rights, safety and well-being and the reliability of trial results as the trial progresses." That is not a suggestion. It is a mandate. And it flows downward from the sponsor's responsibility under Section 3.9 to maintain oversight of every aspect of trial conduct.
The monitor who arrives at your site is executing a monitoring plan designed by the sponsor. That plan specifies--often in granular detail--exactly what the monitor must review, verify, and document during each visit. The monitor does not get to decide that your site looks good and skip the source document verification. The monitor does not get to overlook an unsigned consent form because you seem like a careful coordinator. Per Section 3.11.4.4, "Persons performing monitoring should follow the sponsor's monitoring plan and applicable monitoring procedures."
What the monitor must do at your site
Section 3.11.4.5 of ICH E6(R3) lays out the monitoring activities that sponsors must ensure are performed. Understanding these obligations is not academic trivia--it is the key to preparing effectively and interpreting findings accurately.
CRA monitoring obligations under ICH E6(R3) Section 3.11.4.5
The monitor must maintain communication between the sponsor and the site, inform the investigator of deviations from the protocol or GCP, and confirm that corrections to source records are properly documented. When the monitor flags a deviation during a visit, this is not personal criticism -- it is a specific obligation under Section 3.11.4.5.1(b). The monitor is required to inform the investigator of relevant deviations and take 'appropriate action designed to prevent recurrence.' Notably, E6(R3) specifies that 'important deviations should be highlighted and should be the focus of remediation efforts.' The monitor is distinguishing between minor issues and significant ones -- and your response should reflect that distinction.
The monitor must confirm that investigator site staff have adequate qualifications and resources, that the team is following the current approved protocol, that essential records are maintained, that informed consent was obtained before participation, that adverse events are reported within required timeframes, and that source record requirements are met. When the monitor asks to see the delegation log, the training records, or the IRB approval correspondence, these are not discretionary requests. Each one traces directly to a specific sub-paragraph of Section 3.11.4.5.2.
The monitor must verify proper storage conditions, adequate supplies within shelf life, correct dosing per protocol, and appropriate drug accountability documentation. The monitor who opens the temperature log for the study drug refrigerator is not being pedantic -- temperature excursion documentation is explicitly required under Section 3.11.4.5.3(a)(i). Similarly, the monitor who reconciles drug accountability records is fulfilling an obligation under Section 3.11.4.5.3(a)(v).
The monitor must verify that only eligible participants are enrolled, check accuracy and completeness of reported data against source records, and identify missing data, inconsistencies, and protocol deviations. Source data verification -- comparing what was entered in the EDC against what the source record shows -- is the single most time-consuming monitoring activity, and it is explicitly mandated under Section 3.11.4.5.4(b). The monitor is checking your data entry not because they doubt your competence but because Section 3.11.4.5.4(c) requires them to identify 'significant errors in data collection and reporting.'
Key Takeaway: The monitor's scrutiny is not discretionary
Every document review, every source data verification, every question about a consent form date -- these trace to specific paragraphs in ICH E6(R3) Section 3.11.4.5. The monitor who does not check these items is the one failing to do their job. Understanding this reframes the entire relationship: the monitor is not looking for your mistakes. The monitor is fulfilling a regulatory obligation that ultimately protects participants and preserves data integrity. Your preparation should make it easy for them to fulfill that obligation.
How E6(R3) changed monitoring
If you have worked with monitors who trained under earlier versions of GCP, you may notice a difference in approach between those who monitor by rote and those who apply the risk-based principles of E6(R3). This is not accidental. The original ICH E6(R1) guideline leaned heavily toward 100% source data verification -- every data point, every visit, every participant. E6(R2), adopted in 2016, introduced the concept of risk-based monitoring, and E6(R3) expanded and refined that proportionality principle: monitoring extent and frequency should be "based on identified risks" (Section 3.11.4).
In practice, this means the modern risk-based monitor may verify 100% of informed consent documents but only sample source data verification for routine visit assessments. The monitor may spend more time on participants with protocol deviations and less on participants with clean records. The monitor may use centralised monitoring -- data analytics performed remotely (Section 3.11.4.2) -- to identify sites and processes that need closer on-site review.
For coordinators, this shift has a practical consequence: the findings you receive from a risk-based monitor tend to be more targeted and more significant. When a monitor trained in E6(R3) flags something, it is usually because the issue falls within a domain the sponsor has identified as critical to quality. Pay attention to those findings accordingly.
Preparing for monitoring visits: the CRC checklist
I have a view on monitoring visit preparation that surprises some coordinators: the preparation should be continuous, not episodic. If you are scrambling to organize files the week before a monitoring visit, you have already lost. The best-prepared sites are the ones where daily documentation habits make monitoring visits unremarkable events rather than fire drills.
But I am a realist. Even well-organized sites benefit from systematic pre-visit preparation. What follows is a framework, not a rigid checklist, because your specific preparation will vary by protocol, sponsor, and what happened since the last visit.
The two-week timeline
Effective monitoring visit preparation begins roughly two weeks before the scheduled visit. Not because the work takes two weeks, but because you need that lead time to identify and resolve problems before the monitor arrives. A consent form signature missing since the last visit is a finding when the monitor discovers it. It is a correction when you discover it first and document the late signature with an appropriate note.
Two weeks out: resolve what you can. Run a query report from the EDC system. Every open query that you can resolve before the monitor arrives is one fewer finding in the monitoring report. Check the regulatory binder: is the current IRB approval letter filed? Has the most recent protocol amendment been added? Are all delegation log entries current, with appropriate training documented for each delegate? If something is missing, you still have time to obtain it.
One week out: pull and verify. Ask the monitor--or check the visit confirmation letter--which participants will be reviewed. Pull the source documents for those participants. Do your own source data verification: compare the EDC entries against the source for the key data points (eligibility criteria, primary endpoint data, adverse events, concomitant medications). Flag discrepancies and correct them now. Verify that every consent form is complete: all required signatures present, correct version used, dated appropriately, no blank fields. Check drug accountability records for accuracy.
Two to three days out: finalize and brief. Organize the documents the monitor will need in a logical order. Brief the investigator on any unresolved issues the monitor is likely to raise -- a pending protocol deviation report, an adverse event with borderline seriousness criteria, an enrollment shortfall the sponsor has flagged. Confirm the logistics: a conference room or workspace for the monitor, computer access to the EDC, printer access if needed, parking instructions if the monitor is visiting from out of town.
Communicate proactively with the monitor before the visit
The best CRC
CRA relationships involve pre-visit communication. Send the monitor a brief email a week before the visit: "We have resolved 11 of the 14 open queries. Three remain pending investigator review and should be resolved by Wednesday. The regulatory binder is current. We had one protocol deviation since your last visit -- a missed visit window for Participant 007 -- and the deviation report has been submitted. Is there anything specific you would like me to prepare?" This message takes three minutes to write. It tells the monitor that you are organized, that you are transparent about problems, and that you respect their time. It also sets a collaborative tone before the visit begins.
Checklist
CRC monitoring visit preparation checklist
Progress: 0 of 7 completed0%
Run a query report and address every query that can be resolved without investigator input. Route medical queries to the PI with the relevant source data.
Confirm the binder contains the current IRB/IEC approval, all protocol amendments, current Investigator's Brochure, delegation log with signatures and dates, site staff CVs and medical licenses, laboratory certifications, and normal ranges.
Identify which participants the monitor will review. Pull their charts, source worksheets, consent forms, and any supporting documentation. Organize them in participant order.
For each monitored participant, verify: correct consent form version, all required signatures and dates present, consent obtained before any study procedures, re-consent documented for amendments when required.
Reconcile drug accountability logs: shipment received, dispensed to participants, returned or destroyed, current inventory. Verify temperature monitoring logs are complete and within range.
Inform the investigator of any unresolved findings from the previous visit, pending protocol deviations, or issues the monitor is likely to raise. Confirm the PI's availability if the monitor needs to discuss medical decisions.
Ensure the monitor has a dedicated workspace, access to the EDC system, printer access if needed, and clear directions to the site. Confirm the visit date and expected duration.
Building the collaborative relationship
Preparation is necessary but not sufficient. The relationship between the coordinator and the monitor is built through repeated interactions, and the quality of those interactions depends on behaviors that both parties control. Since you can only control your side of the equation, let me focus on what coordinators can do.
Transparency is your most powerful tool
I have said this to every CRC I have mentored, and I will say it to you: the single most effective thing you can do for the CRC-CRA relationship is to be transparent about problems. Not after the monitor discovers them. Before.
When you walk into the monitoring visit and say, "Before we start, I want to flag two issues I found during my pre-visit review. First, Participant 012's Cycle 4 visit was three days outside the window because the participant had a scheduling conflict. The deviation report was submitted last Thursday. Second, I noticed that the investigator's verbal order for the dosing hold on Participant 008 was not documented in real time -- I wrote the note the following morning. I have corrected the documentation habit going forward" -- when you say that, you have accomplished several things at once.
You have demonstrated that you review your own work critically. You have shown that you understand what constitutes a finding. You have deprived the finding of its sting by presenting it yourself. And you have signaled that you are a professional who takes accountability seriously. Every competent monitor I have known responds to that kind of transparency with respect, not with harsher scrutiny.
The opposite approach--hoping the monitor does not notice, deflecting when they do, explaining why the problem was not really your fault--destroys the relationship. Monitors talk to each other and to their managers. A site that hides problems becomes a site that gets more intensive monitoring, not less.
Understand the monitor's constraints
The monitor is under pressure you may not see. The sponsor expects a monitoring report within a defined timeframe after the visit--often five business days. That report must document everything the monitor reviewed, every finding, every action item, and every resolution. If the monitor asks you a question that seems obvious, it may be because the report requires a specific confirmation that cannot be left to assumption.
The monitor is also managing a portfolio of sites. A field-based monitor may be responsible for 12 to 18 investigator sites, each with different protocols, different investigators, and different coordinators. The monitor may have visited a site in Philadelphia yesterday, flown to your site today, and be driving to another site tomorrow. When the monitor seems rushed or preoccupied, it is usually not disrespect. It is the reality of a role that demands constant travel and rapid context-switching.
Understanding these constraints does not mean excusing poor behavior from a monitor. But it does mean extending the same professional grace you would want extended to you on a day when three studies demanded your attention simultaneously.
The CRA was often a CRC first
A significant percentage of clinical research associates began their careers as coordinators. The monitor in this lesson's case study is a former coordinator -- and this is not unusual. The Association of Clinical Research Professionals (ACRP) has reported that monitoring is one of the most common career transitions for experienced coordinators. When you work with a monitor who seems to understand site operations unusually well, there is a good chance they sat in your chair not long ago. This shared background, when acknowledged, can be a foundation for mutual respect and practical collaboration.
Common friction points and how to defuse them
Even in the best CRC-CRA relationships, specific situations generate tension. Knowing what these are -- and having strategies ready -- prevents reactive responses that damage the relationship.
Reference Table
Common CRC-CRA friction points and collaborative responses
Friction point
Why it happens
Collaborative response
The monitor raises the same finding repeatedly
Previous corrective actions were not sustained, or the root cause was not addressed. The monitor is required under Section 3.11.4.5.1(b) to follow up on prior deviations and confirm they have not recurred.
Acknowledge the pattern directly: 'You are right that this has come up before. The correction I implemented last time did not hold because [specific reason]. Here is what I am changing systemically.' Then follow through.
The monitor requests documents the coordinator considers excessive
The monitoring plan may require verification of items the coordinator views as low-risk. The monitor cannot deviate from the plan without sponsor approval.
Ask the monitor to explain which section of the monitoring plan drives the request. This is not confrontational -- it helps you understand priorities and prepare better next time. If the request genuinely exceeds the plan, the monitor can confirm with their manager.
The monitor's tone feels condescending or adversarial
Some monitors have not developed effective communication skills. Others are under pressure from sponsors to document findings aggressively. Occasionally, a monitor's directness is misread as hostility.
Address behavior, not intent: 'I want to make sure we are working through these findings productively. Can we go through them one at a time so I can understand each one and give you the context you need?' If the behavior persists across multiple visits, raise it with your site leadership.
The coordinator feels ambushed by findings not previously discussed
Some findings emerge only during on-site review of source documents. Others reflect issues the monitor identified through centralised monitoring but did not communicate in advance.
After the visit, send a professional email requesting that significant concerns identified before the visit be communicated in advance when possible: 'This helps me prepare the relevant documentation and ensures we can resolve issues efficiently during the visit.'
Disagreement on whether something constitutes a finding
The coordinator and monitor may interpret protocol language or GCP requirements differently. Neither may be definitively right.
State your interpretation clearly and provide supporting documentation (protocol section, sponsor clarification, SOP). If the disagreement persists, ask the monitor to escalate to the sponsor for a definitive ruling. Do not argue the point repeatedly -- escalation is the appropriate resolution mechanism.
Responding to findings: professional versus defensive
This is where the CRC-CRA relationship is won or lost. Not during the pleasant small talk at the beginning of the visit or the logistics coordination beforehand, but in the moment when the monitor says, "I found a discrepancy in Participant 015's source documentation."
The human instinct in that moment is defensiveness. The coordinator's internal monologue says: "I worked on that chart for an hour. I know it is correct. The monitor is being unreasonable." And the external response--the tone of voice, the body language, the first words out of the coordinator's mouth--either reinforces or overrides that instinct.
The defensive response and its cost
A defensive response sounds like this: "That is not a discrepancy--the participant told us a different date during the visit, and we updated it." Or: "We were incredibly busy that week and short-staffed." Or: "The last monitor did not flag that." Or worst of all: silence and visible frustration.
Every one of these responses damages the relationship. The first challenges the monitor's competence. The second offers an excuse instead of a correction. The third implies the current monitor is being unreasonable. The fourth signals that the coordinator views monitoring as a personal attack.
And here is the practical cost that goes beyond the interpersonal: the monitoring report. The monitor is required to document findings and the site's response. A defensive response--or a non-response--will be recorded. That report goes to the sponsor. A pattern of defensive responses across multiple visits can trigger escalated monitoring, site audits, or in extreme cases, discussions about the site's continued participation in the trial. Defensiveness does not make findings go away. It makes them more consequential.
The professional response framework
A professional response to a monitoring finding has four components, and it takes practice to deliver them naturally.
Reference Table
The four-part professional response to monitoring findings
Step
What to say
Why it works
1. Acknowledge
'Thank you for catching that' or 'I see the discrepancy you are identifying'
Signals that you take the finding seriously and are not going to argue about whether it exists
2. Understand
'Can you walk me through exactly what you are seeing so I can pull the right documents?'
Ensures you and the monitor are looking at the same issue before you respond, and gives you time to gather relevant context
3. Explain or correct
'Here is what happened: [factual account]. I will correct the entry and add a note explaining the change' or 'I will need to check with the investigator on this and follow up with you'
Provides context without making excuses, and commits to a specific corrective action or follow-up timeline
4. Prevent
'To prevent this from happening again, I am going to [specific process change]'
Demonstrates that you think systemically, not just about the individual error -- this is the response that separates experienced coordinators from beginners
Putting the framework into practice
Consider the difference between these two responses to the same finding.
The finding: The monitor identifies that a participant's adverse event start date in the EDC is recorded as March 3, but the source document shows the participant first reported the symptom on February 28.
Defensive response: "The participant was not clear about when the symptoms started. They kept changing the date during the visit. I entered what I thought was correct based on our conversation."
Professional response: "I see the discrepancy -- the EDC shows March 3 and the source shows February 28. Looking at my visit notes, the participant initially reported March 3 during the interview, but when I reviewed the prior visit notes, the symptom was actually first mentioned on February 28. I should have used the earlier date as the onset. I will correct the EDC entry now, and going forward I will cross-reference the prior visit notes before entering adverse event dates to catch situations where a participant's self-report does not match the documented history."
The second response takes 20 seconds longer to deliver. It acknowledges the error, explains the root cause without deflecting blame, commits to an immediate correction, and describes a preventive measure. And critically, it gives the monitor something meaningful to write in the monitoring report: the site acknowledged the finding, corrected it, and implemented a process improvement. That is the kind of response that builds trust over time.
A finding is not a failure -- it is the system working
I want to be direct about this because I have seen too many coordinators internalize monitoring findings as personal failures. They are not. The monitoring system exists precisely because human beings make errors, and those errors must be caught and corrected before they affect participant safety or data integrity. A monitoring visit that produces zero findings is not necessarily a sign of a flawless site -- it may be a sign of inadequate monitoring. A visit that produces findings accompanied by prompt corrections and thoughtful prevention is a sign of a site that takes quality seriously. The best investigators and the best sponsors understand this distinction.
Case Study
"The consent form discrepancy"
Clinical ResearchIntermediate10-15 minutes
Scenario
Marcus Williams is the coordinator on the HORIZON cardiovascular trial at Riverside Medical Center. Jennifer Rodriguez, a CRA from Pacific Coast Research Institute, arrives for a routine monitoring visit covering five participants enrolled in the past two months.
During her review, Jennifer identifies a discrepancy in the informed consent documentation for Participant 019. The participant signed the consent form on January 14. However, the screening bloodwork in the source document is dated January 13 -- one day before the consent was signed. Per ICH E6(R3) Section 2.8 and the HORIZON protocol, all study-specific procedures must occur after the participant has provided written informed consent.
Jennifer brings this to Marcus's attention. "Marcus, I am seeing that Participant 019's screening labs were drawn on January 13, but the consent form is dated January 14. Can you help me understand the sequence here?"
Marcus's initial reaction is a sinking feeling. He remembers that day: the participant came in for a routine clinic appointment on January 13 and had standard-of-care bloodwork drawn. Marcus had planned to consent the participant on January 14 and use the January 13 labs for screening, since the protocol permits the use of standard-of-care labs obtained within 72 hours of consent. But looking at the lab requisition form, he realizes the order was placed under the study account, not the clinical account. The labs were billed as study-specific procedures.
The challenge:
Marcus must respond to this finding in a way that is honest, professional, and constructive. The finding has regulatory significance: if study-specific procedures were performed before informed consent, this is a protocol deviation that may require IRB notification.
Analysis
Acknowledge the discrepancy immediately. Marcus should not argue about whether the labs were standard of care. The documentation shows study-billed labs drawn before consent. The finding is valid. "You are right. The lab order was placed under the study account, and the draw date precedes the consent date. That is a discrepancy I should have caught."
Investigate honestly. Marcus should review the clinical chart to determine whether identical labs were also ordered under the participant's clinical care. If the participant had a clinical appointment that day with overlapping lab panels, the situation may be that standard-of-care labs were inadvertently duplicated under the study account -- a billing error rather than a consent violation. But Marcus must present the facts, not the most favorable interpretation. "Let me pull the clinical chart to check whether these labs were also ordered under clinical care. If so, we may have a duplicate order situation. If not, this is a protocol deviation."
Involve the investigator. Regardless of the root cause, the principal investigator needs to be informed. The investigator must determine whether this constitutes a protocol deviation, whether it requires IRB notification, and whether the participant's eligibility is affected. "I will brief the investigator today and have a determination by tomorrow on whether we need to file a deviation report."
Implement a preventive measure. Marcus should propose a specific process change: "Going forward, I will verify the consent date against all lab and procedure dates before entering screening data into the EDC. I am also going to add a verification step to my screening checklist: confirm consent is signed before placing any study-specific orders."
Follow up in writing. After the visit, Marcus should send Jennifer a written summary of the corrective actions taken, including the investigator's determination, the deviation report status, and the process change. This documentation demonstrates accountability and closes the loop for the monitoring report.
Check your understanding
1 of 3
A monitor requests access to temperature monitoring logs for the study drug refrigerator during a routine monitoring visit. The coordinator considers this unnecessary because there have been no temperature excursions. What is the most accurate explanation for the monitor's request?
What to carry forward
The CRC-CRA relationship is, at its core, an exercise in professional empathy. Not the soft, sentimental kind, but the rigorous kind: the ability to understand what the person across the table is required to do, what pressures they face, and how your behavior either enables or obstructs their work.
Three principles should guide your practice.
Prepare as if you are monitoring yourself. The coordinators who handle monitoring visits with composure are the ones who have already found most of what the monitor will find. Do your own source data verification. Check your own consent forms. Review your own regulatory binder. When you find a problem, fix it and document the correction. When the monitor arrives, you are not hoping for the best. You are presenting work you have already reviewed.
Be transparent about problems, not defensive about findings. Every finding the monitor identifies is an opportunity to demonstrate professionalism. Acknowledge the issue. Explain the root cause. Commit to a correction and a prevention strategy. Then follow through. The coordinators who earn monitor trust are not the ones with perfect records. They are the ones who own their imperfections and fix them reliably.
Invest in the relationship between visits. The monitoring visit is a snapshot. The relationship is continuous. Respond to follow-up requests promptly. Resolve action items within the committed timeline. Send the monitor a brief update when you resolve a significant issue. And when the monitor does something that helps the site--clarifies a protocol question, provides useful guidance from other sites, flags an issue early enough for you to address it--say thank you. Monitors, like coordinators, do better work when they feel their effort is valued.
In the next lesson, we shift to a different set of relationships: communicating with sponsors, IRBs, and regulatory authorities. Where the CRC-CRA relationship is built on shared operational space, those relationships operate through formal channels with distinct protocols. The communication skills you developed here will serve you well there, but the rules of engagement are different.
The professional standard
The monitor is not your adversary. The monitor is not your friend. The monitor is a professional with a regulatory mandate, working under constraints you may not see, toward a goal you share: a well-conducted trial that protects participants and produces data the world can trust. Treat the relationship accordingly.
Full Preview
Free Lesson Preview
Module 1: Lesson 1
The CRC-CRA relationship: collaboration, not adversary
Understand the monitor's role and regulatory obligations, learn to prepare effectively for monitoring visits, and build a collaborative relationship that benefits both site performance and participant safety.
Two perspectives on the same morning
The monitor arrives at the site at 8:45 a.m., 15 minutes before the scheduled monitoring visit. She spent Sunday evening reviewing the site's data in the electronic data capture system, flagging 14 open queries, two consent form discrepancies, and an adverse event that was reported three days past the protocol-required timeline. She has a monitoring plan from the sponsor that specifies exactly which records she must verify, which processes she must confirm, and which deficiencies she must document in her report. Her job--per ICH E6(R3) Section 3.11.4--is to ensure that participant rights, safety, and well-being are protected and that the trial data are reliable. She is not here to judge. She is here to verify.
The coordinator sees the same morning differently. The regulatory binder is not quite where it should be because the IRB approval letter from the last amendment arrived Friday at 4:47 p.m. and has not been filed yet. Two of the three participants the monitor will review had complicated visits: one involved a dosing hold the investigator ordered verbally, and the coordinator is not entirely sure the documentation captures the conversation accurately. The coordinator knows the visit will surface findings. The question is whether those findings become a collaborative problem-solving exercise or a tense interrogation.
This is the CRC-CRA relationship in its essential form. Two professionals, employed by different organizations, with different reporting lines and different pressures, sitting in the same conference room trying to accomplish the same fundamental goal: a well-conducted trial that protects participants and produces reliable data. When the relationship works, monitoring visits are productive, findings are resolved efficiently, and both parties leave the room better informed. When it does not work--when defensiveness meets rigidity, or when silence meets suspicion--the trial suffers and so do the participants.
I have watched this relationship go wrong more times than I care to count, and almost always for the same reason: a failure of perspective. The coordinator who sees the monitor as an adversary will hide problems. The monitor who sees the coordinator as an obstacle will document findings without context. Both reactions are human. Both are professionally destructive. And both are avoidable, once you understand what the person across the table is actually required to do.
What you will learn
By the end of this lesson, you will be able to:
1
Explain the CRA's regulatory obligations per ICH E6(R3) Section 3.11.4 and how understanding these improves your collaboration as a CRC
2
Describe what constitutes effective monitoring visit preparation from the CRC perspective, including document readiness and scheduling
3
Identify common sources of CRC-CRA friction and apply strategies to build collaborative rather than adversarial relationships
4
Demonstrate how to respond professionally to monitoring findings without defensiveness
Understanding the CRA's regulatory obligations
Here is something that transformed my understanding of the CRC-CRA dynamic, and I think it will transform yours: the monitor is not choosing to scrutinize your work. The monitor is required to scrutinize your work. The distinction matters enormously.
ICH E6(R3) Section 3.11.4 establishes monitoring as "one of the principal quality control activities" in clinical trials. The aim of monitoring, per that section, is "to ensure the participants' rights, safety and well-being and the reliability of trial results as the trial progresses." That is not a suggestion. It is a mandate. And it flows downward from the sponsor's responsibility under Section 3.9 to maintain oversight of every aspect of trial conduct.
The monitor who arrives at your site is executing a monitoring plan designed by the sponsor. That plan specifies--often in granular detail--exactly what the monitor must review, verify, and document during each visit. The monitor does not get to decide that your site looks good and skip the source document verification. The monitor does not get to overlook an unsigned consent form because you seem like a careful coordinator. Per Section 3.11.4.4, "Persons performing monitoring should follow the sponsor's monitoring plan and applicable monitoring procedures."
What the monitor must do at your site
Section 3.11.4.5 of ICH E6(R3) lays out the monitoring activities that sponsors must ensure are performed. Understanding these obligations is not academic trivia--it is the key to preparing effectively and interpreting findings accurately.
CRA monitoring obligations under ICH E6(R3) Section 3.11.4.5
The monitor must maintain communication between the sponsor and the site, inform the investigator of deviations from the protocol or GCP, and confirm that corrections to source records are properly documented. When the monitor flags a deviation during a visit, this is not personal criticism -- it is a specific obligation under Section 3.11.4.5.1(b). The monitor is required to inform the investigator of relevant deviations and take 'appropriate action designed to prevent recurrence.' Notably, E6(R3) specifies that 'important deviations should be highlighted and should be the focus of remediation efforts.' The monitor is distinguishing between minor issues and significant ones -- and your response should reflect that distinction.
The monitor must confirm that investigator site staff have adequate qualifications and resources, that the team is following the current approved protocol, that essential records are maintained, that informed consent was obtained before participation, that adverse events are reported within required timeframes, and that source record requirements are met. When the monitor asks to see the delegation log, the training records, or the IRB approval correspondence, these are not discretionary requests. Each one traces directly to a specific sub-paragraph of Section 3.11.4.5.2.
The monitor must verify proper storage conditions, adequate supplies within shelf life, correct dosing per protocol, and appropriate drug accountability documentation. The monitor who opens the temperature log for the study drug refrigerator is not being pedantic -- temperature excursion documentation is explicitly required under Section 3.11.4.5.3(a)(i). Similarly, the monitor who reconciles drug accountability records is fulfilling an obligation under Section 3.11.4.5.3(a)(v).
The monitor must verify that only eligible participants are enrolled, check accuracy and completeness of reported data against source records, and identify missing data, inconsistencies, and protocol deviations. Source data verification -- comparing what was entered in the EDC against what the source record shows -- is the single most time-consuming monitoring activity, and it is explicitly mandated under Section 3.11.4.5.4(b). The monitor is checking your data entry not because they doubt your competence but because Section 3.11.4.5.4(c) requires them to identify 'significant errors in data collection and reporting.'
Key Takeaway: The monitor's scrutiny is not discretionary
Every document review, every source data verification, every question about a consent form date -- these trace to specific paragraphs in ICH E6(R3) Section 3.11.4.5. The monitor who does not check these items is the one failing to do their job. Understanding this reframes the entire relationship: the monitor is not looking for your mistakes. The monitor is fulfilling a regulatory obligation that ultimately protects participants and preserves data integrity. Your preparation should make it easy for them to fulfill that obligation.
How E6(R3) changed monitoring
If you have worked with monitors who trained under earlier versions of GCP, you may notice a difference in approach between those who monitor by rote and those who apply the risk-based principles of E6(R3). This is not accidental. The original ICH E6(R1) guideline leaned heavily toward 100% source data verification -- every data point, every visit, every participant. E6(R2), adopted in 2016, introduced the concept of risk-based monitoring, and E6(R3) expanded and refined that proportionality principle: monitoring extent and frequency should be "based on identified risks" (Section 3.11.4).
In practice, this means the modern risk-based monitor may verify 100% of informed consent documents but only sample source data verification for routine visit assessments. The monitor may spend more time on participants with protocol deviations and less on participants with clean records. The monitor may use centralised monitoring -- data analytics performed remotely (Section 3.11.4.2) -- to identify sites and processes that need closer on-site review.
For coordinators, this shift has a practical consequence: the findings you receive from a risk-based monitor tend to be more targeted and more significant. When a monitor trained in E6(R3) flags something, it is usually because the issue falls within a domain the sponsor has identified as critical to quality. Pay attention to those findings accordingly.
Preparing for monitoring visits: the CRC checklist
I have a view on monitoring visit preparation that surprises some coordinators: the preparation should be continuous, not episodic. If you are scrambling to organize files the week before a monitoring visit, you have already lost. The best-prepared sites are the ones where daily documentation habits make monitoring visits unremarkable events rather than fire drills.
But I am a realist. Even well-organized sites benefit from systematic pre-visit preparation. What follows is a framework, not a rigid checklist, because your specific preparation will vary by protocol, sponsor, and what happened since the last visit.
The two-week timeline
Effective monitoring visit preparation begins roughly two weeks before the scheduled visit. Not because the work takes two weeks, but because you need that lead time to identify and resolve problems before the monitor arrives. A consent form signature missing since the last visit is a finding when the monitor discovers it. It is a correction when you discover it first and document the late signature with an appropriate note.
Two weeks out: resolve what you can. Run a query report from the EDC system. Every open query that you can resolve before the monitor arrives is one fewer finding in the monitoring report. Check the regulatory binder: is the current IRB approval letter filed? Has the most recent protocol amendment been added? Are all delegation log entries current, with appropriate training documented for each delegate? If something is missing, you still have time to obtain it.
One week out: pull and verify. Ask the monitor--or check the visit confirmation letter--which participants will be reviewed. Pull the source documents for those participants. Do your own source data verification: compare the EDC entries against the source for the key data points (eligibility criteria, primary endpoint data, adverse events, concomitant medications). Flag discrepancies and correct them now. Verify that every consent form is complete: all required signatures present, correct version used, dated appropriately, no blank fields. Check drug accountability records for accuracy.
Two to three days out: finalize and brief. Organize the documents the monitor will need in a logical order. Brief the investigator on any unresolved issues the monitor is likely to raise -- a pending protocol deviation report, an adverse event with borderline seriousness criteria, an enrollment shortfall the sponsor has flagged. Confirm the logistics: a conference room or workspace for the monitor, computer access to the EDC, printer access if needed, parking instructions if the monitor is visiting from out of town.
Communicate proactively with the monitor before the visit
The best CRC
CRA relationships involve pre-visit communication. Send the monitor a brief email a week before the visit: "We have resolved 11 of the 14 open queries. Three remain pending investigator review and should be resolved by Wednesday. The regulatory binder is current. We had one protocol deviation since your last visit -- a missed visit window for Participant 007 -- and the deviation report has been submitted. Is there anything specific you would like me to prepare?" This message takes three minutes to write. It tells the monitor that you are organized, that you are transparent about problems, and that you respect their time. It also sets a collaborative tone before the visit begins.
Checklist
CRC monitoring visit preparation checklist
Progress: 0 of 7 completed0%
Run a query report and address every query that can be resolved without investigator input. Route medical queries to the PI with the relevant source data.
Confirm the binder contains the current IRB/IEC approval, all protocol amendments, current Investigator's Brochure, delegation log with signatures and dates, site staff CVs and medical licenses, laboratory certifications, and normal ranges.
Identify which participants the monitor will review. Pull their charts, source worksheets, consent forms, and any supporting documentation. Organize them in participant order.
For each monitored participant, verify: correct consent form version, all required signatures and dates present, consent obtained before any study procedures, re-consent documented for amendments when required.
Reconcile drug accountability logs: shipment received, dispensed to participants, returned or destroyed, current inventory. Verify temperature monitoring logs are complete and within range.
Inform the investigator of any unresolved findings from the previous visit, pending protocol deviations, or issues the monitor is likely to raise. Confirm the PI's availability if the monitor needs to discuss medical decisions.
Ensure the monitor has a dedicated workspace, access to the EDC system, printer access if needed, and clear directions to the site. Confirm the visit date and expected duration.
Building the collaborative relationship
Preparation is necessary but not sufficient. The relationship between the coordinator and the monitor is built through repeated interactions, and the quality of those interactions depends on behaviors that both parties control. Since you can only control your side of the equation, let me focus on what coordinators can do.
Transparency is your most powerful tool
I have said this to every CRC I have mentored, and I will say it to you: the single most effective thing you can do for the CRC-CRA relationship is to be transparent about problems. Not after the monitor discovers them. Before.
When you walk into the monitoring visit and say, "Before we start, I want to flag two issues I found during my pre-visit review. First, Participant 012's Cycle 4 visit was three days outside the window because the participant had a scheduling conflict. The deviation report was submitted last Thursday. Second, I noticed that the investigator's verbal order for the dosing hold on Participant 008 was not documented in real time -- I wrote the note the following morning. I have corrected the documentation habit going forward" -- when you say that, you have accomplished several things at once.
You have demonstrated that you review your own work critically. You have shown that you understand what constitutes a finding. You have deprived the finding of its sting by presenting it yourself. And you have signaled that you are a professional who takes accountability seriously. Every competent monitor I have known responds to that kind of transparency with respect, not with harsher scrutiny.
The opposite approach--hoping the monitor does not notice, deflecting when they do, explaining why the problem was not really your fault--destroys the relationship. Monitors talk to each other and to their managers. A site that hides problems becomes a site that gets more intensive monitoring, not less.
Understand the monitor's constraints
The monitor is under pressure you may not see. The sponsor expects a monitoring report within a defined timeframe after the visit--often five business days. That report must document everything the monitor reviewed, every finding, every action item, and every resolution. If the monitor asks you a question that seems obvious, it may be because the report requires a specific confirmation that cannot be left to assumption.
The monitor is also managing a portfolio of sites. A field-based monitor may be responsible for 12 to 18 investigator sites, each with different protocols, different investigators, and different coordinators. The monitor may have visited a site in Philadelphia yesterday, flown to your site today, and be driving to another site tomorrow. When the monitor seems rushed or preoccupied, it is usually not disrespect. It is the reality of a role that demands constant travel and rapid context-switching.
Understanding these constraints does not mean excusing poor behavior from a monitor. But it does mean extending the same professional grace you would want extended to you on a day when three studies demanded your attention simultaneously.
The CRA was often a CRC first
A significant percentage of clinical research associates began their careers as coordinators. The monitor in this lesson's case study is a former coordinator -- and this is not unusual. The Association of Clinical Research Professionals (ACRP) has reported that monitoring is one of the most common career transitions for experienced coordinators. When you work with a monitor who seems to understand site operations unusually well, there is a good chance they sat in your chair not long ago. This shared background, when acknowledged, can be a foundation for mutual respect and practical collaboration.
Common friction points and how to defuse them
Even in the best CRC-CRA relationships, specific situations generate tension. Knowing what these are -- and having strategies ready -- prevents reactive responses that damage the relationship.
Reference Table
Common CRC-CRA friction points and collaborative responses
Friction point
Why it happens
Collaborative response
The monitor raises the same finding repeatedly
Previous corrective actions were not sustained, or the root cause was not addressed. The monitor is required under Section 3.11.4.5.1(b) to follow up on prior deviations and confirm they have not recurred.
Acknowledge the pattern directly: 'You are right that this has come up before. The correction I implemented last time did not hold because [specific reason]. Here is what I am changing systemically.' Then follow through.
The monitor requests documents the coordinator considers excessive
The monitoring plan may require verification of items the coordinator views as low-risk. The monitor cannot deviate from the plan without sponsor approval.
Ask the monitor to explain which section of the monitoring plan drives the request. This is not confrontational -- it helps you understand priorities and prepare better next time. If the request genuinely exceeds the plan, the monitor can confirm with their manager.
The monitor's tone feels condescending or adversarial
Some monitors have not developed effective communication skills. Others are under pressure from sponsors to document findings aggressively. Occasionally, a monitor's directness is misread as hostility.
Address behavior, not intent: 'I want to make sure we are working through these findings productively. Can we go through them one at a time so I can understand each one and give you the context you need?' If the behavior persists across multiple visits, raise it with your site leadership.
The coordinator feels ambushed by findings not previously discussed
Some findings emerge only during on-site review of source documents. Others reflect issues the monitor identified through centralised monitoring but did not communicate in advance.
After the visit, send a professional email requesting that significant concerns identified before the visit be communicated in advance when possible: 'This helps me prepare the relevant documentation and ensures we can resolve issues efficiently during the visit.'
Disagreement on whether something constitutes a finding
The coordinator and monitor may interpret protocol language or GCP requirements differently. Neither may be definitively right.
State your interpretation clearly and provide supporting documentation (protocol section, sponsor clarification, SOP). If the disagreement persists, ask the monitor to escalate to the sponsor for a definitive ruling. Do not argue the point repeatedly -- escalation is the appropriate resolution mechanism.
Responding to findings: professional versus defensive
This is where the CRC-CRA relationship is won or lost. Not during the pleasant small talk at the beginning of the visit or the logistics coordination beforehand, but in the moment when the monitor says, "I found a discrepancy in Participant 015's source documentation."
The human instinct in that moment is defensiveness. The coordinator's internal monologue says: "I worked on that chart for an hour. I know it is correct. The monitor is being unreasonable." And the external response--the tone of voice, the body language, the first words out of the coordinator's mouth--either reinforces or overrides that instinct.
The defensive response and its cost
A defensive response sounds like this: "That is not a discrepancy--the participant told us a different date during the visit, and we updated it." Or: "We were incredibly busy that week and short-staffed." Or: "The last monitor did not flag that." Or worst of all: silence and visible frustration.
Every one of these responses damages the relationship. The first challenges the monitor's competence. The second offers an excuse instead of a correction. The third implies the current monitor is being unreasonable. The fourth signals that the coordinator views monitoring as a personal attack.
And here is the practical cost that goes beyond the interpersonal: the monitoring report. The monitor is required to document findings and the site's response. A defensive response--or a non-response--will be recorded. That report goes to the sponsor. A pattern of defensive responses across multiple visits can trigger escalated monitoring, site audits, or in extreme cases, discussions about the site's continued participation in the trial. Defensiveness does not make findings go away. It makes them more consequential.
The professional response framework
A professional response to a monitoring finding has four components, and it takes practice to deliver them naturally.
Reference Table
The four-part professional response to monitoring findings
Step
What to say
Why it works
1. Acknowledge
'Thank you for catching that' or 'I see the discrepancy you are identifying'
Signals that you take the finding seriously and are not going to argue about whether it exists
2. Understand
'Can you walk me through exactly what you are seeing so I can pull the right documents?'
Ensures you and the monitor are looking at the same issue before you respond, and gives you time to gather relevant context
3. Explain or correct
'Here is what happened: [factual account]. I will correct the entry and add a note explaining the change' or 'I will need to check with the investigator on this and follow up with you'
Provides context without making excuses, and commits to a specific corrective action or follow-up timeline
4. Prevent
'To prevent this from happening again, I am going to [specific process change]'
Demonstrates that you think systemically, not just about the individual error -- this is the response that separates experienced coordinators from beginners
Putting the framework into practice
Consider the difference between these two responses to the same finding.
The finding: The monitor identifies that a participant's adverse event start date in the EDC is recorded as March 3, but the source document shows the participant first reported the symptom on February 28.
Defensive response: "The participant was not clear about when the symptoms started. They kept changing the date during the visit. I entered what I thought was correct based on our conversation."
Professional response: "I see the discrepancy -- the EDC shows March 3 and the source shows February 28. Looking at my visit notes, the participant initially reported March 3 during the interview, but when I reviewed the prior visit notes, the symptom was actually first mentioned on February 28. I should have used the earlier date as the onset. I will correct the EDC entry now, and going forward I will cross-reference the prior visit notes before entering adverse event dates to catch situations where a participant's self-report does not match the documented history."
The second response takes 20 seconds longer to deliver. It acknowledges the error, explains the root cause without deflecting blame, commits to an immediate correction, and describes a preventive measure. And critically, it gives the monitor something meaningful to write in the monitoring report: the site acknowledged the finding, corrected it, and implemented a process improvement. That is the kind of response that builds trust over time.
A finding is not a failure -- it is the system working
I want to be direct about this because I have seen too many coordinators internalize monitoring findings as personal failures. They are not. The monitoring system exists precisely because human beings make errors, and those errors must be caught and corrected before they affect participant safety or data integrity. A monitoring visit that produces zero findings is not necessarily a sign of a flawless site -- it may be a sign of inadequate monitoring. A visit that produces findings accompanied by prompt corrections and thoughtful prevention is a sign of a site that takes quality seriously. The best investigators and the best sponsors understand this distinction.
Case Study
"The consent form discrepancy"
Clinical ResearchIntermediate10-15 minutes
Scenario
Marcus Williams is the coordinator on the HORIZON cardiovascular trial at Riverside Medical Center. Jennifer Rodriguez, a CRA from Pacific Coast Research Institute, arrives for a routine monitoring visit covering five participants enrolled in the past two months.
During her review, Jennifer identifies a discrepancy in the informed consent documentation for Participant 019. The participant signed the consent form on January 14. However, the screening bloodwork in the source document is dated January 13 -- one day before the consent was signed. Per ICH E6(R3) Section 2.8 and the HORIZON protocol, all study-specific procedures must occur after the participant has provided written informed consent.
Jennifer brings this to Marcus's attention. "Marcus, I am seeing that Participant 019's screening labs were drawn on January 13, but the consent form is dated January 14. Can you help me understand the sequence here?"
Marcus's initial reaction is a sinking feeling. He remembers that day: the participant came in for a routine clinic appointment on January 13 and had standard-of-care bloodwork drawn. Marcus had planned to consent the participant on January 14 and use the January 13 labs for screening, since the protocol permits the use of standard-of-care labs obtained within 72 hours of consent. But looking at the lab requisition form, he realizes the order was placed under the study account, not the clinical account. The labs were billed as study-specific procedures.
The challenge:
Marcus must respond to this finding in a way that is honest, professional, and constructive. The finding has regulatory significance: if study-specific procedures were performed before informed consent, this is a protocol deviation that may require IRB notification.
Analysis
Acknowledge the discrepancy immediately. Marcus should not argue about whether the labs were standard of care. The documentation shows study-billed labs drawn before consent. The finding is valid. "You are right. The lab order was placed under the study account, and the draw date precedes the consent date. That is a discrepancy I should have caught."
Investigate honestly. Marcus should review the clinical chart to determine whether identical labs were also ordered under the participant's clinical care. If the participant had a clinical appointment that day with overlapping lab panels, the situation may be that standard-of-care labs were inadvertently duplicated under the study account -- a billing error rather than a consent violation. But Marcus must present the facts, not the most favorable interpretation. "Let me pull the clinical chart to check whether these labs were also ordered under clinical care. If so, we may have a duplicate order situation. If not, this is a protocol deviation."
Involve the investigator. Regardless of the root cause, the principal investigator needs to be informed. The investigator must determine whether this constitutes a protocol deviation, whether it requires IRB notification, and whether the participant's eligibility is affected. "I will brief the investigator today and have a determination by tomorrow on whether we need to file a deviation report."
Implement a preventive measure. Marcus should propose a specific process change: "Going forward, I will verify the consent date against all lab and procedure dates before entering screening data into the EDC. I am also going to add a verification step to my screening checklist: confirm consent is signed before placing any study-specific orders."
Follow up in writing. After the visit, Marcus should send Jennifer a written summary of the corrective actions taken, including the investigator's determination, the deviation report status, and the process change. This documentation demonstrates accountability and closes the loop for the monitoring report.
Check your understanding
1 of 3
A monitor requests access to temperature monitoring logs for the study drug refrigerator during a routine monitoring visit. The coordinator considers this unnecessary because there have been no temperature excursions. What is the most accurate explanation for the monitor's request?
What to carry forward
The CRC-CRA relationship is, at its core, an exercise in professional empathy. Not the soft, sentimental kind, but the rigorous kind: the ability to understand what the person across the table is required to do, what pressures they face, and how your behavior either enables or obstructs their work.
Three principles should guide your practice.
Prepare as if you are monitoring yourself. The coordinators who handle monitoring visits with composure are the ones who have already found most of what the monitor will find. Do your own source data verification. Check your own consent forms. Review your own regulatory binder. When you find a problem, fix it and document the correction. When the monitor arrives, you are not hoping for the best. You are presenting work you have already reviewed.
Be transparent about problems, not defensive about findings. Every finding the monitor identifies is an opportunity to demonstrate professionalism. Acknowledge the issue. Explain the root cause. Commit to a correction and a prevention strategy. Then follow through. The coordinators who earn monitor trust are not the ones with perfect records. They are the ones who own their imperfections and fix them reliably.
Invest in the relationship between visits. The monitoring visit is a snapshot. The relationship is continuous. Respond to follow-up requests promptly. Resolve action items within the committed timeline. Send the monitor a brief update when you resolve a significant issue. And when the monitor does something that helps the site--clarifies a protocol question, provides useful guidance from other sites, flags an issue early enough for you to address it--say thank you. Monitors, like coordinators, do better work when they feel their effort is valued.
In the next lesson, we shift to a different set of relationships: communicating with sponsors, IRBs, and regulatory authorities. Where the CRC-CRA relationship is built on shared operational space, those relationships operate through formal channels with distinct protocols. The communication skills you developed here will serve you well there, but the rules of engagement are different.
The professional standard
The monitor is not your adversary. The monitor is not your friend. The monitor is a professional with a regulatory mandate, working under constraints you may not see, toward a goal you share: a well-conducted trial that protects participants and produces data the world can trust. Treat the relationship accordingly.
Enjoyed this preview?
The full CRC track covers 8 courses from study start-up to close-out — the skills sponsors actually look for.
