How to Write a Clinical Monitoring Plan
Define how a trial will be monitored — risk-based, not 100% source data verification.
What a how-to is not
A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.
A clinical monitoring plan defines how a sponsor will oversee the conduct of a clinical trial to protect participants and data integrity. Modern practice (ICH E6(R3)) is risk-based: focus monitoring on what matters to participant safety and data reliability, rather than defaulting to 100% source data verification at every site.
- 1
Identify the critical data and processes
Identify the data and processes critical to participant safety and to the reliability of the results, and let that list drive everything the plan then says. Monitoring designed to cover the protocol uniformly spends the same effort on a secondary endpoint as on informed consent; monitoring designed around criticality spends it where an error would change something.
- 2
Assess risks
Assess the risks to those critical items by site, by process and by system, taking account of site experience, complexity, enrolment rate and the systems in use. The assessment should produce different monitoring for different sites, because that is its purpose — a plan that reaches the same intensity everywhere has performed the assessment and then ignored it.
- 3
Define the monitoring approach
Define the monitoring approach: what is monitored centrally through data review, what requires an on-site visit, what will be verified against source and to what extent, and how the three interact. State the rationale, since a reviewer will want to know why source data verification was limited, and "risk-based" is a label rather than a reason.
- 4
Set triggers and thresholds
Set the triggers and thresholds that will change the monitoring intensity, in advance and in numbers. A trigger defined after a site starts to look problematic is a judgement being documented; defined beforehand it is a commitment that removes the argument about whether the site is bad enough yet.
- 5
Define follow-up and escalation
Define what happens when a trigger fires or a significant finding arises: who is notified, in what time, what additional monitoring follows, and when an issue is escalated to the sponsor’s quality function or becomes a serious breach. Follow-up defined vaguely converts a detected problem into a discussed one.
- !Defaulting to 100% source data verification instead of a risk-based approach.
- !Monitoring uniformly across all data rather than concentrating on critical data.
- !No defined triggers, so monitoring intensity never adapts to emerging risk.
- !Findings recorded but not followed up or escalated.
How to Write a Clinical Monitoring Plan: frequently asked questions
Common questions on write a clinical monitoring plan.
What is risk-based monitoring?
An approach that focuses trial monitoring effort on the data and processes most critical to participant safety and result reliability, using a mix of centralised, remote, and targeted on-site monitoring — rather than uniform 100% source data verification. ICH E6(R3) expects this risk-based model.
Does a monitoring plan require 100% SDV?
No — and modern guidance discourages it as a default. Source data verification should be proportionate to risk; 100% SDV across all data is resource-intensive and often adds little assurance for low-risk data. The plan defines SDV extent by risk.
What triggers increased monitoring at a site?
Signals such as breaches of quality tolerance limits, key risk indicators, protocol-deviation rates, or data anomalies detected through centralised monitoring. The plan defines these triggers so monitoring intensity adapts to the site’s actual risk.