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.

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.

The preparation framework

Let me walk through each phase.

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.

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.

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.

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.

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.

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.

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.

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.

The preparation framework

Let me walk through each phase.

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.

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.

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.

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.

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.

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.