How to Prepare for a Monitoring Visit: The Complete CRC Guide

The monitoring visit is one of the most visible measures of your site's compliance and data quality. For most Clinical Research Coordinators, it is also one of the most reliably stressful events in the site operations calendar, but it doesn't need to be. Monitoring visits contain no surprises for a site that maintains its records continuously and understands what monitors are looking for and why. This guide covers the complete preparation workflow, from the two-week countdown through the monitoring report response process, grounded in the current regulatory framework.

What Monitoring Is — and What It Isn't

Clinical trial monitoring is a quality control function. Per the FDA's risk-based monitoring guidance, monitoring is a tool for determining whether investigation activities are being carried out as planned, for verifying that participant rights and safety are protected, that data are complete and accurate, and that the trial is being conducted in compliance with the protocol, GCP, and applicable regulations.

The Clinical Research Associate (CRA) conducting the monitoring visit works on behalf of the sponsor. Their job is to ensure data integrity and participant protection — the same goals the site team is working toward. Understanding this shared purpose matters practically: a monitor who finds a data discrepancy is giving the site an opportunity to correct it before the data package goes to FDA. A monitor who identifies an ISF gap is catching something a BIMO inspector would also catch, but in a context where correction is still possible. Approach monitoring visits as a quality assurance partnership, not an adversarial review.

Risk-Based Monitoring: What It Means for Your Site

The FDA's 2013 guidance on risk-based monitoring and its 2023 Questions and Answers update formalized a shift in how sponsors approach monitoring — and ICH E6(R3), finalized January 2025, embedded that shift into the international GCP standard. Risk-based monitoring (RBM) means that monitoring resources are directed proportionately to the risks identified for a specific trial, rather than applied uniformly regardless of risk level.

In practice, this affects what monitors focus on when they visit your site. Under RBM, sponsors identify Critical to Quality (CtQ) factors for each trial, the data elements and processes that are essential to participant safety and primary endpoint integrity. Monitoring activities, including on-site source data verification (SDV), are concentrated on those CtQ elements. This means monitors at your site are likely to focus their time on primary efficacy endpoint data, consent documentation, eligibility criteria, and SAE reporting rather than conducting comprehensive line-by-line SDV of every data point.

For CRCs, the implication is that data quality on CtQ elements matters more than ever under RBM. Centralized monitoring — statistical review of data patterns across sites, performed remotely by the sponsor's data management team — runs continuously in many modern trials and may identify site-level risk signals before a monitor ever visits. By the time a monitor arrives for an on-site visit, the sponsor often already has a preliminary view of which data areas warrant focused attention at your site.

Types of Monitoring Visits

Not all monitoring visits have the same scope or purpose. Understanding which type of visit is scheduled shapes how you prepare.

Site Qualification Visit (SQV) / Site Selection Visit (SSV): Conducted before the study begins. The sponsor assesses whether your site has the staff, facilities, patient population, and infrastructure to conduct the trial. Your ISF is not yet established, but your PI's CV, staff qualifications, enrollment potential, and facility capabilities will be reviewed. The focus is on whether the site should be selected.

Site Initiation Visit (SIV): Conducted after the site has been selected but before the first participant is enrolled. The monitor trains your team on the protocol, EDC system, IP handling, and sponsor SOPs. Your ISF should be substantially complete by the SIV. The monitor will verify that required essential documents are in place before authorizing the site to begin enrollment.

Interim Monitoring Visit (IMV): Conducted at regular intervals during active enrollment. This is the core ongoing monitoring activity — reviewing source documents for enrolled participants, verifying CRF data, resolving queries, reviewing the ISF for currency, and assessing IP accountability. Most CRC monitoring visit preparation focuses on IMVs.

Close-out Visit (COV): Conducted after the last participant completes the study or after the site is closed. The monitor reconciles final IP accountability, confirms essential document completeness for archival, and documents that all open findings have been resolved. The COV is the site's final formal quality review before the study enters the retention period.

Remote Monitoring vs. On-Site Monitoring Under E6(R3)

ICH E6(R3) explicitly recognizes remote and centralized monitoring as equally valid approaches to on-site monitoring — a significant formalization of what had been evolving practice since the COVID-19 pandemic. Under E6(R3)'s proportionality principle, the monitoring approach should be tailored to the trial's specific risk profile, not defaulted to on-site simply because it has historically been the norm.

For CRCs, remote monitoring visits have their own preparation requirements. Instead of ensuring a physical workspace and record access on-site, you are typically responsible for: ensuring the monitor has remote access credentials to your EDC system and any electronic source systems before the scheduled visit; preparing and transmitting certified copies of paper source documents to the monitor in advance; and being available by video or phone during the scheduled review period to answer questions in real time. The checklist items are similar — ISF currency, source documentation completeness, query resolution, but the logistics of providing access differ significantly from in-person visits.

Whether a visit is remote or on-site, the FDA's monitoring guidance establishes that monitoring reports must document: the participants in the activity; a summary of the data or activities reviewed; a description of any findings, deviations, or outstanding issues; and the follow-up actions agreed between the monitor and the site. This documentation requirement applies regardless of visit modality.

Two Weeks Out: The Preparation Window That Matters Most

Two weeks is the right lead time for systematic visit preparation. It provides enough time to identify and correct gaps — obtain a missing PI signature, chase down an updated CV, resolve open queries with additional documentation, without the scramble of last-minute preparation that characterizes poorly-maintained sites. The goal is to arrive at the day before the monitoring visit with nothing left to do except confirm logistics.

When a monitoring visit is confirmed, immediately do four things: confirm the date, expected duration, and which participants are on the review list; ask the monitor whether they have an agenda or a list of specific source documents or queries they plan to focus on; confirm logistical requirements (workspace, computer access, EMR credentials, printer); and block your calendar for the preparation period as well as the visit itself.

ISF Audit: Walk It Like a Monitor

The Investigator Site File is typically the first thing a monitor reviews on arrival. Its completeness and currency set the tone for the entire visit. Two weeks before any monitoring visit, conduct a systematic self-audit of every ISF section against your protocol's required document list and ICH E6(R3) Appendix C.

Any gap you find during this self-audit becomes a prioritized action item. A missing document you identify two weeks out can be obtained. The same gap identified by a monitor on the day of their visit becomes a written finding in the monitoring report, and generates a corrective action obligation with a deadline.

Source Document Pre-Review: Check Before the Monitor Does

Source data verification (SDV), comparing CRF entries against source records, is the core activity of most interim monitoring visits. The most effective preparation you can do is perform your own pre-visit SDV pass on the charts the monitor will review. You will find the same discrepancies they will find, and you can resolve many of them before they become monitoring findings.

For each participant on the review list, pull the source records and check:

Consent documentation: Is the correct version of the ICF signed and dated? Is the participant's signature preceded by the person obtaining consent's signature? Critically — is the date of consent before or on the same day as the first study-specific procedure? A consent date after a screening procedure is a major deviation by definition. No other documentation error generates as much concern during a monitoring visit.

Eligibility documentation: Does the source record contain dated, documented evidence of every inclusion and exclusion criterion? Is there an eligibility worksheet or PI note confirming the participant qualifies? For laboratory-based eligibility criteria, use the CrCl Calculator to verify calculated values match what was recorded. Missing or undated eligibility documentation is among the most common IMV findings.

Visit notes and procedure documentation: Does a dated, signed visit note exist for every study visit? Does it document all protocol-required assessments? If a procedure was not performed, is the reason documented contemporaneously? A visit with a CRF entry for a procedure but no source documentation for it is an SDV discrepancy that will generate a query at minimum.

Adverse event concordance: Check this in both directions. Every AE in the CRF should have corresponding documentation in the source. And every AE documented in the source should have been entered in the CRF. Monitors specifically look for AEs present in the medical record that were not reported in the CRF, this is one of the most significant data integrity findings in clinical research.

CRF-to-source consistency: For the data elements most likely to be SDV'd (primary endpoint assessments, eligibility-related labs, AE descriptions, SAE narratives), confirm that what is in the CRF matches what is in the source — same values, same dates, same clinical descriptions. Transcription errors that have been in the CRF for months will generate queries that could have been resolved before the visit.

CRF Query Cleanup: Resolve Before the Visit

Open data queries represent an opportunity to demonstrate data quality — or, if left unaddressed, a signal of poor site responsiveness. Run a full query report from your EDC system two weeks before the monitoring visit and work through every open item systematically.

Queries older than 30 days with no response are a specific red flag. The FDA's monitoring guidance notes that monitoring reports should document outstanding issues and agreed follow-up actions — chronic query backlogs indicate systemic site responsiveness problems that will be documented in the report and potentially escalated to the sponsor's clinical operations team.

For queries you can resolve by finding the supporting source documentation, resolve them and provide the response directly in the EDC. For queries requiring clarification from an external source (a laboratory reference, a treating physician note, a pharmacy record), document your communication and leave a status note so the monitor understands the item is in progress and not simply ignored. For queries that reveal a genuine data error requiring a source document correction, follow the ALCOA+ correction process, single line, initials, date, reason, before the monitoring visit rather than after.

IP Accountability: The Zero-Gap Standard

Drug accountability is consistently among the areas that generate monitoring findings, including at sites that otherwise maintain strong documentation. The accountability log must provide a complete chain of custody — every unit received, stored at the correct temperature, dispensed to the correct participant in the correct dose, and either returned or destroyed, with no unexplained gaps at any point.

Before every monitoring visit, physically count your current IP inventory and reconcile it against the log. Use the IP Compliance Calculator to confirm your compliance percentage falls within protocol-specified limits for each participant. If you identify a discrepancy between the physical count and the log, even a single unit — investigate and document the investigation before the monitor arrives. A discrepancy that exists when the monitor arrives but has no documented investigation looks far worse than the same discrepancy with a documented root cause analysis, even if the root cause has not yet been fully resolved.

Also verify: temperature storage logs are complete and uninterrupted; any temperature excursions have been documented along with the sponsor notification and quarantine actions taken; lot numbers and expiration dates were verified at each dispensation; and dispensation amounts match the protocol-specified doses for each participant's visit.

Briefing Your Team

A monitoring visit that surprises sub-investigators, study nurses, or research assistants who performed study procedures creates problems that preparation could have prevented. Staff who are not expecting the visit tend to give vague answers or redirect questions to the CRC, which can create the impression of poor site communication. Worse, uninformed staff may speculate about procedures they performed rather than referring to the source record, generating apparent discrepancies that then require additional explanation.

Brief every staff member on the delegation log at least 48 hours before the visit: the monitor is visiting, these are the studies under review, if the CRA asks you about a specific procedure refer them to me or to the source documentation rather than answering from memory. This is not coaching staff on what to say: it is ensuring that the site presents as a functioning, coordinated team rather than a group of individuals who happen to share a physical space.

Ensure your PI knows the monitoring visit is occurring and is either present for the visit or reachable by phone for any questions that require investigator-level responses. Some monitoring findings — eligibility determination questions, SAE causality assessments, protocol deviation classifications — require PI input that the CRC cannot provide independently.

Day-of Best Practices

On the day of the visit, have the ISF, source documents for review participants, and IP accountability records staged and accessible before the monitor arrives. Provide the monitor with a private workspace where they can review materials independently — monitors generally work more efficiently when they are not being watched and can come to you with questions at natural breakpoints.

Be available but not hovering. Checking in periodically to confirm the monitor has everything they need is appropriate; standing over their shoulder while they review source documents is not. When the monitor comes to you with a question, answer it directly and accurately. If you do not know the answer, say so and find out — guessing or speculating generates more problems than acknowledging uncertainty. If you need to consult the PI or check a document, tell the monitor you will follow up and do so promptly.

Take your own notes throughout the day on every finding, discrepancy, or question the monitor raises verbally. Do not wait for the written monitoring report to understand what was found. By the time the formal report arrives, typically 10 to 21 days after the visit. You want a corrective action plan already drafted, not a fresh start.

The Monitoring Report: What It Is and What It Means

The monitoring report is the formal written record of the monitoring visit. Per the FDA's risk-based monitoring guidance, monitoring reports must document who participated, what data and activities were reviewed, what findings or deviations were identified, and what follow-up actions are expected of both the monitor and the site, with agreed timelines.

Monitoring reports typically classify findings by severity. Common classification tiers include: observations (items noted for awareness, no action required), recommendations (suggested improvements that do not rise to formal findings), findings or deviations (items requiring documented corrective action), and critical findings (issues requiring immediate action, potential participant safety implications, or possible data integrity compromise). Know your sponsor's classification system and respond to each tier appropriately.

The monitoring report is a permanent document that lives in your ISF and in the sponsor's trial master file. Its findings become part of the evidentiary record of your site's conduct of the trial. A site with consistently clean monitoring reports, few findings, prompt resolutions, documented CAPAs, demonstrates the kind of quality culture that reflects well in regulatory submissions and BIMO inspections.

The Monitoring Report Response Process

Most sponsor monitoring report formats require a formal site response within a specified timeframe — commonly 10 to 14 business days from receipt of the report. The response should address every finding documented in the report, with three components for each: what correction was made (corrective action), what process change was implemented to prevent recurrence (preventive action), and the date both were completed or are expected to be completed.

Respond to findings in order of severity. Critical findings requiring immediate action should be addressed before the formal response is submitted, if a finding has participant safety implications, the participant's situation must be assessed and any necessary action taken immediately, not after the 14-day response window closes. Document that immediate action was taken and reference it in the formal response.

File the monitoring letter and your written response together in the ISF's monitoring correspondence section. The response is part of the regulatory record, an unanswered monitoring letter in the ISF is a visible compliance gap. At the next monitoring visit, the monitor will confirm that every finding from the previous visit has been resolved. A resolution documented in writing, before the next visit, closes the loop. An unresolved finding from a previous visit that is still open at the next visit suggests the site's corrective action process is ineffective.