Clinical Trial Monitoring: Visit Types, Source Data Verification & the Monitoring Plan

Clinical trial monitoring is the ongoing oversight process by which a sponsor confirms that a trial is being conducted, recorded, and reported in accordance with the protocol, the sponsor’s Standard Operating Procedures (SOPs), Good Clinical Practice (GCP), and applicable regulatory requirements. It is distinct from an audit (a periodic, independent, systematic examination) and from an inspection (a regulatory authority’s official review) — monitoring is the sponsor’s own continuous quality-oversight function, carried out throughout the life of the trial rather than as a one-time check. This guide covers monitoring as a process: the visit types a Clinical Research Associate (CRA) performs, what monitors actually check at a site, how the monitoring plan document scopes that work, and how risk-based monitoring and Clinical Trial Management System (CTMS) software have reshaped how monitoring is practiced today. “Clinical research monitoring” and “clinical trial monitoring” refer to the same function and are used interchangeably in this guide.

What Is Clinical Trial Monitoring?

ICH E6(R2) Good Clinical Practice, Section 1.38, defines monitoring as “the act of overseeing the progress of a clinical trial, and of ensuring that it is conducted, recorded, and reported in accordance with the protocol, Standard Operating Procedures (SOPs), Good Clinical Practice (GCP), and the applicable regulatory requirement(s).” The industry job title Clinical Research Associate (CRA) is the common name for the person who performs this function — ICH E6 itself does not use the title “CRA,” only the functional term “monitor.” A CRA is typically employed by the trial sponsor or by a Contract Research Organization (CRO) acting on the sponsor’s behalf, and is responsible for confirming that one or more investigator sites are running the trial as designed, protecting participants, and generating data that regulators can trust.

Why Monitoring Matters

Monitoring exists to protect two things simultaneously: participant safety and data integrity. A monitor confirms that participants gave valid informed consent before any study procedure, that the protocol is being followed as written, that adverse events are being identified and reported on the required timeline, and that the data submitted to the sponsor traces back to genuine source documentation at the site. Because sponsors ultimately bear responsibility for trial data quality even when duties are delegated to a CRO, monitoring is the sponsor’s primary mechanism for maintaining oversight of work happening at sites it does not directly control.

Types of Monitoring Visits

While ICH E6 does not itself name specific visit types, the industry has converged on a broadly consistent sequence of monitoring visits across a trial’s lifecycle:

• Pre-study / site selection visit: conducted before a site is activated, to assess whether the site has the facilities, staff, patient population, and regulatory infrastructure to conduct the trial.
• Site initiation visit (SIV): conducted once a site is selected and before enrollment begins. The monitor trains site staff on the protocol, confirms regulatory and ethics-committee approvals are in place, and verifies the site’s essential document files are complete before the first participant can be enrolled.
• Routine / interim monitoring visits: conducted at intervals throughout active enrollment and follow-up. Frequency and depth are set by the trial’s monitoring plan rather than a fixed industry standard, and increasingly vary by site risk rather than following an identical schedule across all sites.
• Close-out visit (COV): conducted once a site’s participation ends (enrollment target reached, trial terminated, or the site withdraws). The monitor reconciles outstanding queries, confirms investigational product accountability and destruction/return, and verifies the site’s essential documents are complete and archived per the retention requirements in the trial agreement and applicable regulation.

On-Site, Remote, and Centralized Monitoring

ICH E6(R2) Section 5.18.3 explicitly recognizes centralized monitoring as “a remote evaluation of accumulating data, performed in a timely manner, supported by appropriately qualified and trained persons (e.g., data managers, biostatisticians).” Sponsors may choose an on-site-only approach, a combination of on-site and centralized monitoring, or, where justified and documented, a centralized-only approach for lower-risk aspects of a trial. This flexibility is a deliberate departure from the older assumption that monitoring meant a CRA physically present at the site for every visit:

• On-site monitoring — the CRA visits the site in person, reviews source documents directly, and interacts face-to-face with investigators and coordinators.
• Remote monitoring — the CRA reviews site data, documents, or systems (including via remote/virtual access) without a physical visit, often used for lower-risk interim checks between on-site visits.
• Centralized monitoring — statisticians and data managers analyze accumulating data across all sites in a trial (not one site at a time) to detect patterns, outliers, or data anomalies that a single site visit would never surface, such as one site’s enrollment rate, query rate, or adverse-event pattern diverging from the rest of the trial.

Sponsors document their chosen approach and rationale in the trial’s monitoring plan, and increasingly combine all three depending on a site’s or trial parameter’s assessed risk level — the core logic behind risk-based monitoring (RBM), covered in more depth below.

What Monitors Actually Check

A monitoring visit is not a single checklist item but a review across several domains:

• Protocol compliance — confirming procedures, visit windows, dosing, and eligibility criteria were followed as specified in the clinical trial protocol, and that any deviations were identified and reported per the sponsor’s deviation-handling procedures.
• Informed consent documentation — verifying that every enrolled participant’s consent was obtained using the currently approved consent form version, before any study-specific procedure took place, and that the signed and dated documentation is complete and correctly filed.
• Source data verification (SDV) — cross-checking data recorded on the Case Report Form (CRF) against the site’s original source documents (clinic notes, lab reports, imaging, participant diaries) to confirm the CRF accurately reflects what actually happened at the site.
• Investigational product accountability — confirming receipt, storage, dispensing, and return/destruction of investigational product are documented and reconciled against what was actually administered.
• Adverse event reporting — confirming adverse events were identified, assessed for causality and seriousness, and reported within the required timelines.
• Essential documents and the regulatory binder — confirming the site’s essential-document file (the documents that, individually and collectively, permit evaluation of trial conduct and data quality, per ICH E6(R2) Section 8) is current and complete.

Source Data Verification: What It Is and What It Isn’t

Source data verification (SDV) is the process of comparing data on the CRF against the original source document it was transcribed from, to confirm accuracy and completeness. A common misconception is that regulation requires checking 100% of data points against source documents this way. Neither ICH E6 nor FDA guidance has ever mandated 100% SDV — FDA’s 2013 guidance Oversight of Clinical Investigations: A Risk-Based Approach to Monitoring explicitly encourages sponsors to focus monitoring resources on the data and processes most critical to trial quality and participant protection, rather than exhaustive verification of every field. Full SDV of every data point became a de facto industry default that went beyond what regulators actually required, and a 2024 scoping review of the published literature found no settled evidence base establishing that 100% SDV produces meaningfully more accurate data than a well-designed risk-based, reduced-SDV approach. This evidence gap is a major reason the industry has shifted toward risk-based monitoring rather than blanket verification.

The Monitoring Plan

The monitoring plan is the document that scopes and governs how a specific trial will be monitored. ICH E6(R2) Section 5.18.1 establishes that monitors should be appropriately trained and qualified, and that the sponsor should develop a monitoring plan tailored to the specific human subject protection and data integrity risks of the trial, rather than applying a generic template. A monitoring plan typically specifies:

• Which monitoring approach(es) will be used (on-site, remote, centralized, or a combination) and the rationale for that choice.
• The frequency and depth of monitoring visits, including whether frequency varies by site based on assessed risk.
• The scope of source data verification — which data fields or forms will be verified against source, and at what proportion, if reduced or targeted SDV is used.
• Quality tolerance limits (QTLs) — predefined, trial-critical parameters (introduced under ICH E6(R2) Section 5.0.4) with thresholds that, if breached, trigger a documented root-cause investigation.
• Roles, responsibilities, and escalation pathways for issues identified during monitoring.
• How monitoring findings are documented and communicated back to the site and sponsor.

Monitoring Visit Reports

ICH E6(R2) Section 1.39 defines a monitoring report as a written report from the monitor to the sponsor, produced after each site visit and/or other trial-related communication, in accordance with the sponsor’s SOPs. These reports document what was reviewed, findings and observations (including any protocol deviations or data discrepancies identified), actions agreed with the site, and any follow-up required before the next visit. Monitoring reports are themselves part of the trial’s essential documentation and are subject to review during sponsor audits and regulatory inspections.

Risk-Based Monitoring and How Modern Practice Has Shifted

Risk-based monitoring (RBM) is the current dominant monitoring paradigm, formally incorporated into ICH E6(R2)’s 2016 addendum and given further emphasis under ICH E6(R3). Rather than applying identical monitoring intensity to every site and every data point regardless of risk, RBM directs monitoring resources toward the risks most likely to affect participant safety or data quality — using centralized statistical monitoring to flag outlier sites or patterns, key risk indicators (KRIs) to track site performance between visits, and adaptive on-site visit frequency based on what that ongoing analysis shows. TransCelerate BioPharma’s 2013 RBM methodology position paper was an influential industry framework that helped popularize this approach alongside FDA’s own 2013 risk-based monitoring guidance. In practice, most trials today run a blended model: centralized monitoring continuously across all sites, supplemented by on-site visits at a frequency and depth calibrated to each site’s assessed risk rather than a fixed universal schedule.

How CTMS Fits Into Monitoring

A Clinical Trial Management System (CTMS) is the operational software layer that supports monitoring logistics rather than replacing the monitoring function itself. Monitors and study teams typically use a CTMS to schedule and track monitoring visits across every site in a trial, log visit findings and follow-up action items, monitor site-level metrics that feed into a risk-based monitoring approach (such as query rates, enrollment pace, or protocol deviation counts), and maintain a trial-wide record of monitoring history that supports both ongoing oversight and eventual audit or inspection readiness. CTMS and centralized statistical monitoring tools often work together: the CTMS tracks operational visit activity while dedicated centralized-monitoring or data-surveillance tools analyze the underlying clinical data for the anomalies that inform where on-site attention should go next.

Frequently Asked Questions

What is the difference between clinical trial monitoring and an audit?

Monitoring is the sponsor’s own ongoing oversight of trial conduct, typically performed by a CRA at intervals throughout the trial. An audit is a more formal, periodic, and independent evaluation — often conducted by a sponsor’s quality assurance function rather than the monitoring team itself — assessing whether trial conduct and processes complied with the protocol, SOPs, GCP, and regulation. A regulatory inspection is a further step removed: it is carried out by a government regulatory authority (such as FDA), not the sponsor.

Who performs clinical trial monitoring?

The role is most commonly performed by a Clinical Research Associate (CRA), employed either directly by the trial sponsor or by a Contract Research Organization (CRO) the sponsor has contracted to conduct monitoring on its behalf. ICH E6 uses only the functional term “monitor” and does not itself require a specific job title or credential, though many CRAs hold a certification such as ACRP’s CCRA or SOCRA’s CCRP.

How often are monitoring visits conducted?

There is no single mandated frequency. Visit frequency is set out in the trial’s monitoring plan and, under a risk-based monitoring approach, is often calibrated per site based on factors such as enrollment volume, site experience, data quality trends, and protocol complexity, rather than applying an identical schedule to every site in the trial.

Is 100% source data verification required by regulation?

No. Neither ICH E6 nor FDA guidance has ever required checking every data point against source documents. Full (100%) SDV became a common industry practice beyond what regulators required, and current guidance explicitly encourages a risk-based, targeted approach to verification instead.

What’s the difference between on-site, remote, and centralized monitoring?

On-site monitoring involves a CRA physically visiting the site and reviewing source documents in person. Remote monitoring involves reviewing site data or documents without a physical visit, often for lower-risk interim checks. Centralized monitoring is a distinct, cross-site function performed by data managers or biostatisticians who statistically analyze accumulating data across all sites in a trial to detect patterns or anomalies a single-site visit would not reveal. Most modern trials combine all three.

Related CASRAI Resources

• Risk-Based Monitoring (RBM) — the strategy that determines how monitoring intensity is allocated.
• Clinical Trial Management System (CTMS) — the software layer supporting monitoring operations.
• Case Report Form (CRF) — the document set monitors verify against source data.
• Clinical Research Associate (CRA) — the role that performs the ICH-defined “monitor” function.
• Clinical Trial Protocol — the document monitors verify site conduct against.