Making Hybrid Visit Schedules Work at the Site Level

Hybrid protocols are no longer unusual. Most sponsors now write at least some visits as "remote or telehealth permitted," and sites that handle those visits well see better retention and fewer protocol deviations. Sites that treat remote visits as a lighter version of an in-person visit tend to see the opposite.

The difference is almost entirely operational.

Decide which visits actually belong remote

When a protocol allows flexibility, don't default to remote for everything permitted. Work through the visit schedule and sort each timepoint into three buckets:

• Must be in person. Anything requiring phlebotomy, imaging, infusion, physical exam findings that drive dosing, or device calibration.
• Better remote. Symptom diaries review, concomitant medication reconciliation, adverse event follow-up, dosing compliance checks, most questionnaires.
• Could go either way. Consent discussions, early screening conversations, end-of-study wrap-up.

That third bucket is where judgment matters. A remote screening conversation saves a candidate a trip before you know they qualify, which is a real retention win. But a remote visit immediately after a dose escalation may not give your investigator enough signal.

Build a remote visit workflow, not an exception process

The most common failure mode is treating each remote visit as a one-off. The coordinator scrambles for the video link, realizes the participant never got the questionnaire, and the visit runs long or gets rescheduled.

What works better:

1. Pre-visit packet sent 48 hours out. Link, what to have ready (medication bottles, diary, blood pressure cuff readings), and expected duration.
2. A confirmation touch the day before. Short, specific, and answerable with one tap.
3. A tech check offer for first-time remote participants. Five minutes with a coordinator prevents a lost visit window.
4. Source documentation template built for remote. It should prompt the coordinator to record the modality, who was present, how identity was confirmed, and any procedures deferred to the next in-person visit.

That last item is where monitors find problems. If your source note for a remote visit looks identical to an in-person note, you have a documentation gap.

Watch for the participants remote visits fail

Remote flexibility is often framed as universally better for access. In practice, sites commonly see that it helps some participants and quietly disadvantages others — those with limited bandwidth, shared devices, no private space to discuss symptoms, or low comfort with video platforms.

Screen for this early. A simple question during consent — "Would video visits work well for you, or would you rather come in?" — lets you plan the schedule around the person instead of forcing a modality they will eventually no-show.

Also keep a phone-only fallback. For many visit types, a structured phone call documented properly is fully acceptable and dramatically more reliable than troubleshooting video.

Negotiate the budget for it

Remote visits are not free for the site. Someone still prepares, conducts, documents, and reconciles. Shorter clock time does not mean less coordinator labor, and tech support time is real.

When reviewing budgets, ask explicitly how remote visits are reimbursed. If they are priced at a fraction of in-person visits without a corresponding reduction in site work, say so during negotiation. Sponsors generally understand this argument when it is made with a specific accounting of tasks rather than a general objection.

The practical test

After a few months of hybrid conduct, pull your deviation log and your no-show log, and tag each entry by visit modality. If remote visits are overrepresented in either, the problem is usually workflow design, not the protocol. Fix the preparation steps before concluding that remote visits don't work for your population.