GCP · Blog
Back to journal

The Clinical Monitoring Plan: A Risk-Based Blueprint, Not a Visit Schedule

The instinct is to treat the monitoring plan as a schedule: visit every site every six weeks, check everything. ICH E6(R3) describes something different. The aim of monitoring is to ensure the participants' rights, safety, and well-being and the reliability of trial results (ICH E6(R3) §3.11.4), and crucially the sponsor should determine the appropriate extent and nature of monitoring based on identified risks (ICH E6(R3) §3.11.4). "Extent and nature, based on risk" is the whole brief. A plan that applies the same intensity everywhere is not following that instruction; it is avoiding the work of prioritising.

GCP 7 min read
A

Aileen

Aileen writes practical guidance for clinical trial teams at GCP Blog.

On this page · 8 sections
  1. 01 At a glance
  2. 02 What a monitoring plan actually is
  3. 03 The foundation is critical-to-quality, set at design
  4. 04 What goes in the plan: the methods and the mix
  5. 05 The plan binds the people doing the work
  6. 06 What the plan tells the monitor to actually do
  7. 07 Where teams get it wrong
  8. 08 Sources

At a glance

  • A monitoring plan is not a calendar of site visits. It is the document that decides what to oversee, how closely, and by which methods, based on the trial’s specific risks.
  • Its starting point is upstream: the critical-to-quality factors identified when the trial was designed. You monitor what matters to participant safety and result reliability, in proportion to risk.
  • It defines a mix, not a single tactic: on-site monitoring, centralized monitoring of accumulated data, and the balance between them.
  • The plan is binding on the people doing the work. Monitors follow the plan and its procedures; the plan is not advisory.
  • Done well, the plan concentrates effort on the data and processes that can hurt participants or the results, and deliberately spends less on the rest.

What a monitoring plan actually is

The instinct is to treat the monitoring plan as a schedule: visit every site every six weeks, check everything. ICH E6(R3) describes something different. The aim of monitoring is to ensure the participants’ rights, safety, and well-being and the reliability of trial results (ICH E6(R3) §3.11.4), and crucially the sponsor should determine the appropriate extent and nature of monitoring based on identified risks (ICH E6(R3) §3.11.4). “Extent and nature, based on risk” is the whole brief. A plan that applies the same intensity everywhere is not following that instruction; it is avoiding the work of prioritising.

The plan itself is required to be risk-tailored by design. The sponsor should develop a monitoring plan that is tailored to the identified potential safety risks, the risks to data quality, and other risks to the reliability of the trial results, with particular attention given to procedures relevant to participant safety and to trial endpoints (ICH E6(R3) §3.11.4.3). That sentence sets the plan’s organising principle: it is built around this trial’s risks, not lifted from a template.

The foundation is critical-to-quality, set at design

A monitoring plan that starts at “how often do we visit” has started in the wrong place. The upstream question is what is critical to this trial’s quality, and ICH E8(R1) answers it. The quality-by-design approach focuses on critical-to-quality factors to ensure the protection of participants’ rights, safety, and wellbeing, the generation of reliable and meaningful results, and the management of risks to those factors using a risk-proportionate approach (ICH E8(R1), designing quality into clinical studies). Those factors are not soft: critical-to-quality factors are attributes of a study whose integrity is fundamental to the protection of study participants and to the reliability and interpretability of the results, and the sponsor and other parties designing the study should identify them (ICH E8(R1), critical-to-quality factors).

So the chain runs E8 to E6: identify what is critical to quality at design, then build the monitoring plan to protect exactly those things. A plan that monitors everything equally has effectively decided nothing is critical, which is the opposite of risk-based.

What goes in the plan: the methods and the mix

The plan is not single-tactic. ICH E6(R3) and FDA’s risk-based monitoring guidance both describe a blend.

On-site monitoring happens at the investigator site, and the plan sets its frequency by risk rather than by default cadence. Centralized monitoring is the complement: an evaluation of accumulated data, performed in a timely manner, by the sponsor’s qualified and trained persons such as a medical monitor, data scientist or data manager, and biostatistician (ICH E6(R3) §3.11.4.2). Centralized review can flag the sites and signals that then earn an on-site visit, which is more efficient than visiting everyone on a fixed schedule.

FDA’s guidance is explicit that this mix is the modern expectation. A modern, risk-based approach focuses on critical study parameters and relies on a combination of monitoring activities, including greater use of centralized monitoring methods where appropriate (FDA Risk-Based Monitoring guidance, introduction), and there is a growing consensus that focusing on the most critical data elements is more likely to ensure subject protection and overall study quality, and lets sponsors monitor more effectively than routine visits to all clinical sites with 100% data verification (FDA Risk-Based Monitoring guidance, rationale). The plan is where you write down which methods you will use, on what data, and how they trigger one another.

A workable monitoring plan therefore specifies at least:

  • The critical-to-quality factors and the risks the plan is built to control.
  • What is monitored centrally, what on-site, and how central findings escalate to site visits.
  • The criteria and frequency for on-site visits, including risk-triggered and for-cause visits.
  • The data and processes given particular focus, especially primary and key secondary endpoints and the processes that protect participant safety.
  • How issues are reported, escalated, and resolved.

The plan binds the people doing the work

A monitoring plan is not a strategy slide. It governs execution. Persons performing monitoring should follow the sponsor’s monitoring plan and applicable monitoring procedures (ICH E6(R3) §3.11.4.4). That makes the plan the operative instruction for every monitor on the trial, which is also why a vague plan is dangerous: monitors will do what it says, so what it says has to be specific enough to act on and tied to the actual risks.

What the plan tells the monitor to actually do

A plan that names methods but not activities leaves the monitor guessing. ICH E6(R3) lists the activities monitoring should generally include, and the plan is where you select and target them. Among them, monitoring should verify that the investigator is enrolling only eligible trial participants, and should check the accuracy, completeness, and consistency of the reported trial data against source records and other trial-related records (ICH E6(R3) §3.11.4.5.4). Those two, eligibility and source-to-data fidelity, are the load-bearing checks, which is why a risk-based plan concentrates them on the critical data rather than spreading them evenly.

On-site work has its own anchor. Investigator site monitoring may be performed in relation to the clinical trial activities at the investigator sites, including their pharmacies and local laboratories as appropriate (ICH E6(R3) §3.11.4.1), and the plan sets how often and on what trigger those visits happen. The modern pattern is that centralized review does the broad, continuous watching and flags the sites and signals that then earn an on-site visit. A good plan writes that linkage down explicitly: what the central function watches, what threshold or finding escalates to a site visit, and what a for-cause visit looks for when it is triggered.

The plan also has to say what happens after a visit. Monitoring produces findings, findings produce actions, and actions need to close. A plan that schedules visits but is silent on how issues are reported, escalated, and resolved has described surveillance without consequence. The whole point of the activity, ensuring participants’ rights, safety, and well-being and the reliability of the results (ICH E6(R3) §3.11.4), depends on findings actually changing something, so the plan’s reporting-and-follow-up mechanics are not an appendix; they are where monitoring earns its keep.

Where teams get it wrong

  • Writing a visit schedule and calling it a plan. Frequency is an output of risk, not the plan’s organising idea. Start from critical-to-quality, not from the calendar.
  • Skipping the E8 step. If the critical-to-quality factors were never identified, the monitoring plan has nothing principled to prioritise around.
  • All on-site, no centralized. Centralized monitoring is part of the expected mix and is how you target on-site effort. Omitting it is the old model.
  • Uniform intensity. Monitoring everything equally is the failure E6(R3) and FDA both warn against. Proportionate means more where the risk is, less where it is not.
  • A plan too vague to follow. Monitors are bound to the plan. If it does not say what to do, it will not be done consistently.
  • No path from finding to resolution. A plan that schedules visits but never says how a finding is reported, escalated, and closed produces observation without correction, which protects no one and fixes nothing.
  • Static SDV masquerading as risk-based. Verifying a fixed percentage of every field is a smaller census, not a risk-based plan. Concentrate verification on the eligibility and critical-data checks E6(R3) names, and let the sample adapt to what monitoring finds.

A good monitoring plan reads like a set of decisions: these are the risks, this is what we watch and how closely, this is the blend of methods, and this is how findings move. It is the trial’s oversight blueprint, and like any blueprint its value is in the choices it makes, not the pages it fills. A useful test before a plan is finalised is to hand it to a monitor who was not in the room when it was written and ask what they would do on day one. If they can name the sites and data they would watch most closely, the threshold that would pull them on-site, and who they would escalate a finding to, the plan is doing its job. If they would have to ask, the plan has documented intentions rather than instructions, and intentions are not what protects a participant or survives an inspection.

Sources

A

Written by

Aileen

Aileen writes practical guidance for clinical trial teams at GCP Blog.