The Visit-Type-Aware Clinical Trial Monitoring Visit Checklist: SQV, SIV, IMV, COV, and Inspection Prep, Mapped to GCP

At a glance

• There is no single “monitoring visit.” There are at least five distinct events (Site Qualification, Site Initiation, Interim Monitoring, Close-Out, and audit/inspection prep), and each asks a different question, so a flat document-pull list will fail at least four of them.
• ICH E6(R3) §3.11.4 frames every monitoring activity around two ends: participant rights, safety, and well-being, and the reliability of trial results. Tag each line of your checklist to the purpose it serves (subject safety, data integrity, or protocol compliance) and a junior CRA can tell a critical finding from a note.
• ICH E6(R3) §3.11.4.1 ties monitoring frequency and extent to identified risks, and the FDA Risk-Based Monitoring guidance pushes scope toward the most critical data and processes. Risk-based monitoring changes how much you verify, not what GCP requires.
• The follow-up letter is not optional courtesy correspondence. ICH E6(R3) §3.11.4.6 requires monitoring reports that summarise what was reviewed, describe significant findings, and state the actions required to resolve them, including escalation. The letter is the report’s site-facing deliverable.
• FDA BIMO inspection prep is a different drill from a sponsor IMV. An FDA investigator works to compliance program 7348.811 and issues a Form FDA 483 when they observe deviations from the regulations, so inspection prep means reconciling consent versions, source records, and investigational product accountability to a regulatory standard, not a sponsor preference.

Most monitoring checklists circulating as ACRP PDFs and site SOPs share three defects: they blur the visit types into one generic “monitoring visit,” they never tell you why GCP requires a given check, and they stop at the visit and ignore the follow-up letter as a timed deliverable. This reference fixes all three. Every checklist below is keyed to one visit type and every line is tagged to the GCP purpose it serves, so the list produces findings and drives the follow-up-letter timeline instead of being a box-ticking walkthrough.

A note on language before the checklists: monitoring enables compliance, it does not certify it. Running a clean IMV does not make a sponsor “compliant.” Under ICH E6(R3), oversight of the trial remains the sponsor’s responsibility and the conduct of the trial at the site remains the investigator’s. The checklist is a tool for surfacing where that responsibility is or is not being met.

The five monitoring visit types and why one checklist won’t fit all

Visit	Purpose (the question it answers)	When	Who calls it	Core checklist focus	Typical findings
SQV (Site Qualification)	Can this site run this protocol safely and properly?	Pre-selection, before contracting	Sponsor / CRA	Investigator qualifications, resources, facilities, staff	Inadequate staffing, no access to required population, equipment gaps
SIV (Site Initiation)	Is the site ready to enrol the first subject?	After approvals, before first enrolment	Sponsor / CRA	Training, IRB approval, IP receipt, source-record plan	Untrained staff, IP not on site, consent version not finalised
IMV (Interim Monitoring)	Is the site running the trial correctly right now?	Periodically during enrolment/conduct	Sponsor / CRA	Consent, eligibility, SDV, IP accountability, deviations, safety	Consent timing errors, source-to-data discrepancies, late SAE reporting
COV (Close-Out)	Is everything resolved, reconciled, and retained?	After last subject/last visit	Sponsor / CRA	Final IP accountability, records retention, open-query resolution	Unreconciled IP, missing essential records, unresolved deviations
Audit / BIMO prep	Will the site withstand a regulatory inspection?	Before or in response to an inspection	Sponsor QA or FDA	Consent version control, source/case histories, IP reconciliation	Form FDA 483 observations: consent, records, accountability

The reason one checklist cannot serve all five is that the underlying GCP question changes. The SQV asks a selection question that ICH E6(R3) §3.7.1 assigns to the sponsor: each investigator should be qualified by education, training, and experience and demonstrate adequate resources and facilities to properly conduct the trial. The IMV asks a conduct question. The COV asks a reconciliation-and-retention question. Collapsing them hides the moment a finding actually matters.

The interim monitoring visit (IMV): what the CRA verifies and why GCP requires it

The IMV is where most monitoring time is spent, and it is the visit junior CRAs most often reduce to a document pull. ICH E6(R3) §3.11.4 states that the aim of monitoring is to ensure participants’ rights, safety, and well-being and the reliability of trial results as the trial progresses, and it is explicit that monitoring should be performed by persons not involved in the clinical conduct of the trial at the site being monitored. That independence is structural, not stylistic: the monitor is the sponsor’s check on the site, so a coordinator cannot self-monitor.

What the IMV verifies, per ICH E6(R3) §3.11.4.5.4, is not “every field.” Monitoring should verify that the data required by the protocol and identified as data of higher criticality in the monitoring plan are consistent with the source, identify missing or inconsistent data and protocol deviations, and surface significant errors, potential data manipulation, and data-integrity problems. This is the line that separates a modern IMV from a 100%-SDV walkthrough: the protocol- and plan-defined critical data come first.

Start-up answers “can this site begin?” The IMV answers “is this site conducting the trial correctly, and is the data it is generating reliable?” They are not the same checklist with a different date.

Checklist: Site Qualification Visit (SQV) — can this site run this protocol

Purpose tags: [SAFETY] subject safety, [DATA] data integrity, [PROTOCOL] protocol compliance.

• Confirm the investigator is qualified by education, training, and experience to assume responsibility for the trial. [PROTOCOL] ICH E6(R3) §2.1.1 requires this and requires evidence of those qualifications.
• Confirm the site has adequate resources, facilities, staff, equipment, and laboratory access to conduct the trial safely and properly. [SAFETY] This is the sponsor’s selection duty under ICH E6(R3) §3.7.1.
• Confirm access to the target population and realistic recruitment capacity. [PROTOCOL]
• Assess whether the site can define and maintain source records, and where source data will live. [DATA] ICH E6(R3) §2.12.2 requires the investigator to define what counts as a source record, the methods of capture, and their location before the trial starts.
• Evaluate the site’s capacity to manage and account for investigational product. [SAFETY]
• Document the qualification decision and the rationale; this is selection evidence, not a formality.

Checklist: Study Start-Up / Site Initiation (SIV) — the ready-to-enrol gate

• Confirm IRB/IEC approval of the protocol and the current consent materials is in hand before any enrolment. [SAFETY] ICH E6(R3) §2.8.1 requires the investigator to have documented IRB approval of the informed consent materials and process before consenting and enrolling participants.
• Confirm all site staff are trained on the current approved protocol, the current Investigator’s Brochure, and their delegated tasks. [PROTOCOL] ICH E6(R3) §3.11.4.5.2(b) makes confirming that site staff are adequately informed and follow the current approved protocol a monitoring activity.
• Confirm investigational product has been received, stored under protocol-specified conditions, and accountability records are open. [SAFETY] ICH E6(R3) §2.10.1 places IP accountability, handling, and dispensing responsibility on the investigator/institution.
• Confirm the source-record definition and location are finalised and the data acquisition tools are ready. [DATA]
• Confirm safety-reporting timelines and contacts are understood by the site. [SAFETY]
• Lock the consent version control: the IRB-approved version that will be used on day one is identified and no superseded version is in circulation. [SAFETY]

The SIV is a gate, not a visit you can pass conditionally and fix later. If the consent version or IP is not ready, the site is not ready.

Checklist: Interim Monitoring Visit (IMV) — SDV, consent, IP accountability, deviations, safety

This is the core artifact. Each line is tagged and traceable to ICH E6(R3) §3.11.4.5.

• Verify the investigator enrolled only eligible participants. [PROTOCOL] ICH E6(R3) §3.11.4.5.4(a) makes eligibility verification a monitoring activity.
• Verify informed consent was obtained before participation for the subjects reviewed, using the correct IRB-approved version. [SAFETY] ICH E6(R3) §3.11.4.5.2(d) requires confirming consent was obtained before participation; §2.8.1 requires the version to be IRB-approved.
• Source-data verification of critical data: check accuracy, completeness, consistency, and timeliness of reported data against source records, prioritising the higher-criticality data defined in the monitoring plan. [DATA] ICH E6(R3) §3.11.4.5.4(b) sets this expectation and explicitly allows sampling supported by data analytics.
• Reconcile investigational product: storage conditions acceptable, supplies within shelf life, correct IP supplied only to eligible participants at the protocol-specified dose, and receipt/use/return documented. [SAFETY] ICH E6(R3) §3.11.4.5.3(a) lists these IP-monitoring confirmations; §2.10.4 requires the underlying accountability records of delivery, inventory, per-participant use, and return/destruction.
• Review protocol deviations: confirm they are documented and that important deviations are highlighted and remediated. [PROTOCOL] ICH E6(R3) §3.11.4.5.1(b) requires the monitor to inform the site of relevant deviations and, where necessary, take action to prevent recurrence, with important deviations the focus of remediation.
• Verify adverse events, and serious adverse events in particular, were reported within the protocol- and regulation-required time periods. [SAFETY] ICH E6(R3) §3.11.4.5.2(e) makes determining timely AE reporting a monitoring activity.
• Confirm essential records are maintained and current. [DATA] ICH E6(R3) §3.11.4.5.2(c) requires confirming the investigator is maintaining essential records.
• Note entry errors or omissions in source records or data tools and ensure corrections are made, dated, and explained. [DATA] ICH E6(R3) §3.11.4.5.1(c) makes this an explicit monitoring activity, and §2.12.2 requires source records to be attributable, legible, contemporaneous, original, accurate, and complete.

How findings escalate: a consent obtained after a study procedure, an unreported SAE, or IP dispensed to an ineligible subject is a critical finding, because each maps directly to subject safety or to the reliability of the trial. A single mis-dated query response is a minor note. The tag tells you which bucket you are in.

Checklist: Close-Out Visit (COV)

• Confirm final investigational product accountability: receipt, use, and return or destruction are reconciled and documented. [SAFETY] ICH E6(R3) §3.11.4.5.2(j) makes confirming the final accountability of IP and its return/destruction a close-out monitoring activity.
• Confirm arrangements for retention of essential records are in place. [DATA] Same provision, §3.11.4.5.2(j), covers retention arrangements.
• Confirm all open queries, deviations, and prior monitoring findings are resolved or have a documented resolution plan. [PROTOCOL]
• Confirm safety reporting is complete and final reports/notifications have been provided. [SAFETY]
• Confirm the site understands its ongoing record-retention obligations after the visit.

The monitoring visit follow-up letter: what it contains and the timeline it commits to

The follow-up letter is the site-facing face of the monitoring report, and ICH E6(R3) §3.11.4.6 defines what that report must contain: a summary of what was reviewed, a description of significant findings, the conclusions, and the actions required to resolve them, including follow-up on resolution of findings not closed in previous reports. The same section requires that, when needed, the report describe findings requiring escalation for action and resolution, with the sponsor deciding on the action and the decisions and resolutions recorded.

Follow-up-letter contents checklist, built from those requirements:

• A summary of what was reviewed at the visit (scope, subjects, data sampled).
• A clear description of significant findings, separated from minor notes.
• The required corrective actions, each with an owner.
• Items carried forward from prior visits that remain open.
• Any finding escalated to the sponsor and the action taken.
• A response or resolution due date for the site.

On timeline: ICH E6(R3) §3.11.4.6(b) requires monitoring reports to be provided to the appropriate sponsor staff in a timely manner for review and follow-up, and §3.11.4.6 states that the specific requirements for monitoring reports, including their content and frequency, are defined in the sponsor’s own procedures. In practice this means the precise turnaround (often expressed as a number of business days) is set by your monitoring plan and SOPs, not by the guideline itself. Anchor your letter timeline to the sponsor procedure, and treat “timely” as the GCP floor that procedure must satisfy.

Audit and FDA BIMO inspection prep: how it differs from a sponsor IMV

A sponsor IMV checks the site against the protocol and the monitoring plan. An FDA Bioresearch Monitoring (BIMO) inspection checks the clinical investigator against the regulations, and the consequence is a different document: the BIMO compliance program 7348.811 directs the FDA investigator to issue a Form FDA 483 at the conclusion of the inspection when deviations from applicable regulations are observed. That is the practical line. An IMV finding becomes a follow-up-letter action item; a BIMO finding can become a 483 observation.

What a BIMO inspector actually pulls, per compliance program 7348.811, and therefore what inspection prep must reconcile to a regulatory standard:

• All approved versions of the informed consent documents, and confirmation that the correct IRB-approved version was used for each subject before any study-related procedures. The program directs the investigator to review all consent versions and verify the version used per subject.
• Source records and case histories (progress notes, medical charts, laboratory reports, nursing notes), and subject eligibility for enrolment, which the program directs the investigator to examine.
• Documentation of adverse events, including severity, relationship to the investigational product, and any resulting changes to the subject’s participation, which the program lists as a safety-monitoring review item.
• Investigational product accountability: the program directs the inspector to review records of shipment, receipt, disposition, return, and destruction and to compare the amount of investigational product shipped, received, dispensed, used, and returned or destroyed.

The inspection-prep delta over a routine IMV: where an IMV samples critical data, inspection prep reconciles the full chain end to end against the regulations, with consent version control and IP reconciliation the two areas where 483 observations most often land. Run the IMV checklist above, then add a regulatory-standard reconciliation pass on consent versions and IP accountability, and confirm there is a clean, retrievable trail for every subject reviewed.

One tension worth stating plainly rather than smoothing over. ICH E6(R3) §3.11.4.5.4(b) explicitly endorses sampling of data supported by analytics: monitoring need not verify every record, and the FDA Risk-Based Monitoring guidance reinforces that a monitoring plan should ordinarily focus on the critical data and processes identified by the risk assessment. The BIMO program, by contrast, directs the FDA investigator to review all approved consent versions and to perform a complete shipped-to-returned reconciliation of investigational product. These are not contradictory commands to the same actor, the sponsor monitor samples while the FDA inspector reconciles fully, but they do mean a risk-based IMV is not a dress rehearsal for an inspection. The areas you reasonably sampled during routine monitoring are the same areas an inspector will examine exhaustively, so inspection prep must close that gap deliberately. Cite both standards, and do not assume risk-based sampling will satisfy an inspector.

Where risk-based monitoring changes what you check (and what you don’t)

Risk-based monitoring changes the extent, frequency, and method of your checks, not the GCP obligations underneath them. ICH E6(R3) §3.11.4.1 ties the frequency of monitoring activities to identified risks and says those activities and their frequency should be modified using knowledge gained. ICH E6(R3) §3.11.4.3 requires a monitoring plan tailored to the identified safety and data-reliability risks, with particular attention to participant safety and trial endpoints, focused on what is critical to quality.

The FDA Risk-Based Monitoring guidance points the same direction: it describes a risk-based approach that focuses on critical study parameters and relies on a combination of monitoring activities, and it states that the monitoring plan ordinarily should focus on the critical data and processes identified by the risk assessment, with centralised monitoring of accumulated data able to complement and reduce the extent or frequency of on-site visits.

Here the two in-scope sources align rather than conflict, and it is worth saying so. Both ICH E6(R3) and the FDA guidance endorse risk-proportionate, centralised-plus-on-site monitoring focused on critical data; ICH E6(R3) §3.11.4.2 describes centralised monitoring as an evaluation of accumulated data that can complement and reduce site monitoring or be used on its own. What neither source does is let you stop verifying eligibility, consent timing, IP accountability, or safety reporting. Those remain on the IMV checklist regardless of how risk-based your plan is, because they are the items where a failure is a subject-safety or data-reliability failure. Risk-based monitoring lets you sample the merely important; it does not let you skip the critical.

Sources

• ICH E6(R3) Good Clinical Practice (ICH), version r3 — https://www.ich.org/page/efficacy-guidelines
• FDA Guidance: Oversight of Clinical Investigations — A Risk-Based Approach to Monitoring (FDA), version 2013
• FDA Compliance Program 7348.811 — Bioresearch Monitoring: Clinical Investigators and Sponsor-Investigators (FDA), version 2020 — https://www.fda.gov/media/75927/download