Reduced SDV: What Changes When You Stop Verifying Every Field

Reducing source data verification saves monitoring days, but it does not reduce risk. It moves risk into central review, edit check design and site qualification. A reduced plan is defensible when the rule was written before the first visit, tied to critical factors rather than to a percentage, and applied consistently enough that deviations from it are visible.
The regulatory position has been settled for over a decade. The FDA guidance on a risk-based approach to monitoring, first issued in 2013 and updated with questions and answers in 2019, is explicit that complete source data verification is not expected. ICH E6(R3) frames the same point as proportionality. Neither says anything about a percentage, which is where most plans go wrong.

Why It Is Not a Percentage
A plan that says thirty percent treats every field as equally worth checking, which is exactly the assumption risk-based monitoring exists to remove. The field that decides whether a participant belongs in the analysis and the field recording a routine vital sign carry different consequences, and a single sampling rate applies the same effort to both.
Tiering fixes this. A small set of fields is verified in full because a failure there is unrecoverable or changes the result. A larger set is sampled under a stated rule. A third set is not verified at all, because the source is electronic, or the value is derived, or the data is already under central statistical review. The third tier is the one teams leave implicit, and stating it is what makes the plan readable.
Which fields sit in the first tier is not a monitoring decision. It follows from the critical-to-quality factors named in the risk assessment, which is why that assessment has to exist before the monitoring plan can be written.
Where the Risk Moves To
Every hour removed from source checking reappears somewhere, and the plan should say where.

Central review is the main destination. It finds what no site visit can, because it works across all sites at once: distribution anomalies, an implausibly clean site, query aging clustered in one region. A reduced plan that adds no central component has not redistributed the effort, it has simply removed it.
Edit check design is the second destination, and it is upstream. Errors prevented at entry never need verifying, which makes the study build a monitoring decision as much as a data management one. The build sequence and the point at which checks are actually tested are covered in every step between final protocol and first patient in.
The third is site qualification. Fewer visits means the judgment that a site can run this protocol has to be made earlier and revisited on triggers, particularly staff turnover.
Writing a Sampling Rule That Holds
The rule is an inspection artifact. It has to answer what is sampled, how much, which participants, when it changes and what happens to the findings, and it has to answer them before the first monitoring visit rather than in a reconstruction afterwards.

The most common weakness is the fourth row. Sampling rates get adjusted informally as a study runs, usually for good operational reasons, and nobody records the change or the reasoning. At inspection the plan and the visit reports then disagree, and the disagreement is harder to explain than the original decision would have been.
The most useful habit is the fifth row. A sampling rule that never changes in response to what it finds is not risk-based, it is a fixed schedule with a smaller number. Findings at a site should be able to move that site's rate up, and a sustained clean record should be able to move it down.
Why the First Participants Are Different
Early source checking at each site is worth more than the same effort spread evenly, because it catches a misunderstanding while it affects two participants rather than twenty. A site reading an eligibility criterion differently from the protocol will keep reading it that way until someone looks.
This is also the cheapest form of site training. Verifying the first participants in full, then dropping to the sampled rate once the site has demonstrated it understands the protocol, uses monitoring effort where it changes behavior rather than where it documents it.
What Inspectors Tend to Ask
Three questions recur. What was your rationale, meaning the link from critical factors to the tier each field sits in. Did you follow your own plan, which is answered by the visit records rather than by the plan itself. And what did you do when you found something, which is where the feedback loop either exists or does not.
A team that can answer those three is in a stronger position than a team that verified everything without being able to explain why. Where oversight of the monitoring itself sits with a contract research organization, the split of responsibility becomes its own question, and it is set out in the wider risk-based quality management plan. The systems that carry the record are covered in Clinera EDC and in our work with contract research organizations.
References
The FDA guidance Oversight of Clinical Investigations, A Risk-Based Approach to Monitoring, issued August 2013, and A Risk-Based Approach to Monitoring of Clinical Investigations, Questions and Answers, issued April 2019. ICH E6(R3), Good Clinical Practice, Step 4 on 6 January 2025, for proportionate monitoring. The EMA reflection paper on risk-based quality management in clinical trials remains a useful companion for European studies. TransCelerate BioPharma has published methodology papers on reduced and targeted source data verification.
Current texts are at www.fda.gov, www.ich.org and www.ema.europa.eu.
Frequently Asked Questions
Is 100% source data verification required by regulators?
No. The FDA guidance on a risk-based approach to monitoring, issued in 2013 and supplemented with questions and answers in 2019, states that complete verification is not expected, and ICH E6(R3) frames monitoring as proportionate to risk. Neither prescribes a percentage. What is expected is a documented rationale for what is verified and what is not, and evidence that the plan was followed.
What percentage of SDV should we do?
The percentage is the wrong unit. A single rate applies equal effort to a field that decides the analysis population and a field recording a routine vital sign. A tiered plan verifies a small set in full because failure there is unrecoverable, samples a larger set under a stated rule, and names a third set as not verified because the source is electronic or the data is under central review.
Which data should always be verified in full?
The data that traces back to a critical-to-quality factor. In most studies that means the primary endpoint, the eligibility criteria that decide whether a participant belongs in the analysis, serious adverse events and their onset dates, and informed consent dates and versions. Consent is on almost every list because it is the category where essentially no failure can be corrected afterwards.
Does reducing SDV reduce data quality?
Not if the effort is redistributed rather than removed. Central review finds patterns across sites that no single visit can see, and edit checks prevent errors at entry rather than detecting them later. A reduced plan that adds no central monitoring component and no strengthening of the study build has cut cost rather than changed method, and that is the version that shows up as findings.
Can the sampling rate change during the study?
It should. A rate that never responds to what it finds is a fixed schedule with a smaller number, not a risk-based plan. Findings at a site should be able to raise that site's rate, and a sustained clean record should be able to lower it. What causes problems at inspection is not the change but the informal change: an adjustment made for sound operational reasons with no record of the reasoning.
Why verify the first participants at each site in full?
Because a site that has misread an eligibility criterion will keep misreading it until someone looks, and catching that at the second participant rather than the twentieth changes how much data is affected. Front-loading verification also functions as the cheapest form of site training, after which dropping to the sampled rate uses monitoring effort where it changes behavior rather than where it documents it.



