Which Study Visits Actually Work Remotely, and Which Don't

Remote visits stopped being an emergency workaround several years ago. They are now written into protocols from the first draft, and sites are expected to run them well. The problem is that most sites inherited telehealth habits formed under pressure in 2020 and never rebuilt the workflow around how these visits actually behave.

Which visits actually work remotely

Not every visit converts. The ones that do tend to share three features: no specimen collection, no device calibration, and assessments that depend on conversation rather than physical examination.

Strong candidates:

• Pre-screening and eligibility conversations. Often better remotely, because candidates will talk longer from their kitchen than from an exam room.
• Consent discussions. The conversation can be remote even when signature logistics are not.
• Symptom diaries, PRO review, adherence check-ins.
• Safety follow-up calls after a dose change or adverse event.

Weak candidates, regardless of what the protocol says:

• Any visit with a lab draw that then requires a same-day in-person stop anyway. You have created two visits out of one.
• Cognitive or functional assessments that were validated in person. Raters often disagree on scores across video.
• First visits for participants who have never met the team. Trust is built faster face to face, and retention reflects it.

The hidden cost nobody budgets for

Remote visits are cheaper for the participant and often more expensive for the site. A video visit requires the same coordinator hour, plus tech troubleshooting, plus a higher no-show rate because the visit feels less consequential than driving across town.

Sites commonly find that remote visit no-shows run noticeably higher than in-clinic no-shows unless the team adds a same-day confirmation touch. Build that into the workflow rather than treating it as extra effort:

1. Reminder 48 hours out with the link.
2. Reminder the morning of, with the link again — never "see previous email."
3. A phone call if the participant has not joined within five minutes. Most joins happen on that call.

Fix the technology floor before the protocol starts

The single most common cause of a failed remote visit is not bandwidth. It is a participant who has the link but cannot work the platform. Address this at the baseline in-person visit, while you have them in the room:

• Install and open the platform on their device, not a site tablet.
• Do a 60-second test call with a coordinator down the hall.
• Write the login steps on paper and hand it to them.
• Record which device they will use in the participant record, so the next coordinator is not guessing.

Five minutes at baseline prevents a cascade of missed windows later.

Document it like a visit, not a phone call

Remote visits draw monitoring attention. Make sure your notes answer, without the monitor asking: who was present, how identity was verified, which modality was used, whether the participant consented to the remote modality, and why the visit was conducted remotely if the protocol allowed either option. A short standardized note template beats free-text every time.

Treat modality as a retention lever

The practical win is not "all remote" or "all in person." It is offering a genuine choice at the point where participants typically disengage — usually the long middle stretch of follow-up. Ask at enrollment which visits they expect to struggle to attend, and flag those early for remote conversion where the protocol permits. Participants who feel the schedule bends to their lives stay enrolled longer, and the decision costs the site nothing but a conversation.