What monitoring looks like without a site visit
Monitoring does not disappear in decentralised trials. It evolves. The binders go away. The rhythms change. But the underlying purpose, ensuring data is reliable, participants are protected, and sites are running the study as intended, remains exactly the same.
This isn't just a hopeful reframe. A literature review covering 22 publications on different monitoring approaches found little objective evidence that traditional 100% source data verification actually produces better data integrity than reduced SDV, centralised statistical monitoring, or remote approaches.
One hundred percent SDV is not a rational method of ensuring data integrity and subject safety based on the high cost, and this literature review indicates that reduced SDV is a viable monitoring method. Olsen et al., review of clinical trial monitoring approaches
Several of the reviewed studies did find that full on-site verification and centralised statistical monitoring each caught specific things the other missed, unreported adverse events in one case, atypical statistical trends in the other, which is a genuinely useful nuance: the answer isn't that remote monitoring is simply as good, it's that the two approaches tend to be good at catching different kinds of problems.
From spot checks to continuous oversight
Traditional monitoring was cyclical: visits every four to six weeks, followed by a round of query resolution. In a digital-first setup, the rhythm changes significantly:
- eCRF data can be reviewed daily or weekly rather than in batches
- Query turnaround is tracked in real time rather than at the next scheduled visit
- System alerts flag missing or conflicting entries as they happen, not weeks later
The result is less catch-up work and more continuous visibility. Issues surface earlier, which makes them easier to resolve, and it's a big part of why the literature review above found centralised statistical monitoring so good at spotting atypical trends: a monitor watching data accumulate continuously notices a drift in the pattern long before a monitor seeing the same data in one large batch every six weeks would.
Skills and tools that matter now
Remote monitoring requires a different set of competencies:
- Comfort with platforms. Navigating system logic, audit views, permission levels, and query workflows is core to the role now.
- Pattern recognition. The job is not just spotting errors but reading signals: slow form entry, repeated deviations from a single site, uploads that never quite complete.
- Clear written communication. Queries are now documents rather than hallway conversations. Tone, clarity, and specificity matter more when there is no accompanying verbal explanation.
- Cross-referencing without a folder. Comparing protocols, CRFs, and logs across systems takes practice.
What gets missed without a visit, and how to compensate
It is worth being honest about the trade-offs, because the evidence above doesn't say remote monitoring catches everything an on-site visit would.
| What's harder to see remotely | Why | How teams compensate |
|---|---|---|
| Paper source notes that don't align with expectations | No physical documents to cross-check against the system | Scheduled periodic visits at higher-risk sites, or photographed source documents |
| The working atmosphere at a site, whether coordinators are under pressure or stretched | Not visible in a dashboard, only inferable from patterns | Structured regular calls where a coordinator can raise concerns directly |
| Informal reassurance and relationship-building | Site visits build this naturally through in-person time | Deliberate video calls rather than relying on written messages alone |
This is why remote monitoring works best when paired with proactive communication: structured calls, shared dashboards, and transparent systems for raising and resolving issues, rather than assuming that data flowing into a system is the same thing as a relationship with the people generating it.
Rethinking what monitoring is for
Replacing site visits is not the goal. The goal is to maintain quality and oversight using whatever mix of tools and interactions the study actually needs, and the underlying literature increasingly backs a mixed approach rather than treating it as a stopgap.
Some trials still benefit from periodic visits. Others run well with entirely remote monitoring. Many use both depending on the phase and the site, matching the specific strength of each method (verification for one kind of problem, statistical monitoring for another) to where it's actually useful rather than defaulting to whichever approach is more familiar. What matters is that oversight remains timely, relevant, and genuinely engaged with what is happening on the ground.
None of that requires choosing a side in the debate between on-site and remote monitoring as though only one can be correct. The more useful question for any given study is which specific risks matter most at which sites, and then building a monitoring plan that answers that question directly rather than one inherited wholesale from however the last study happened to be run.