Making Remote Visits Work Without Creating a Second Workflow
Remote visits are now standard in protocol design, but most sites run them as an undocumented second workflow. A practical guide to classifying visits, screening for connectivity, and documenting remote encounters so monitors never have to ask.
By Trialflow Team
Remote visits stopped being an emergency workaround years ago. They are now written into protocols from the first draft, and sites that handle them well win enrollment in geographies they could never have covered before. Sites that handle them badly end up with a second, parallel workflow that nobody owns and that quietly generates deviations.
Here is what actually makes remote visits work at site level.
Decide which visits belong remote before the study opens
Do not let this be decided visit by visit by whichever coordinator is on the schedule. Walk the schedule of events during startup and classify every visit into three buckets:
- Must be in person — anything with a procedure, lab draw, IP dispensing requiring chain of custody, or physical exam feeding a primary endpoint.
- Can be either — symptom diaries reviewed, concomitant medication checks, adverse event interviews, most follow-up calls.
- Better remote — short safety check-ins, window-sensitive touchpoints where travel is the main dropout risk.
Then put that classification somewhere the whole team sees it, ideally in the visit template itself rather than a separate memo. The most common source of remote-visit deviations in site datasets is not technology failure; it is a coordinator conducting a visit remotely that the protocol required on site, or vice versa.
Treat the technology check as a screening step
A participant who cannot reliably join a video call is a retention problem you can detect at consent. Build a two-minute connectivity check into the screening visit while the participant is still in your building: have them install the platform on their own device, log in, and confirm camera and audio work. You will find a meaningful share of participants who are using a family member's device, have no home broadband, or cannot navigate a login.
That is not a reason to exclude them. It is a reason to assign them to the in-person arm of your scheduling, or to plan phone-only contacts where the protocol allows.
Source documentation needs to be stricter, not looser
Remote visits produce thinner documentation by default because nobody is standing at a workstation. Counter this deliberately:
- Record how the visit was conducted — video, telephone, or in person — as a discrete field on every visit note, not buried in narrative text.
- Document that the participant was in a private setting and confirmed their identity, using whatever method your protocol specifies.
- Note any assessment that could not be completed remotely and why, at the time, rather than reconstructing it during monitoring prep.
- Capture participant location if the protocol has any licensure or jurisdictional constraint.
Monitors will ask about all four. Answering from a structured field takes seconds; answering from narrative takes an afternoon.
Build the no-show protocol differently
Remote visits have a higher no-show rate than clinic visits in most site experience, partly because the participant has invested nothing in travel. Compensate with a tighter reminder cadence — a reminder the day before and a second one roughly fifteen minutes before, with a one-tap join link — and with an explicit rule about how long the coordinator waits and what happens next. Without that rule, coordinators burn fifteen-minute blocks all day.
Protect the clinical relationship
The real risk of remote-heavy designs is that participants never build a relationship with a human at your site, which makes them easier to lose. Use the in-person visits you do have for relationship work: same coordinator where possible, a few minutes of unstructured conversation, a clear explanation of what happens next. Remote visits are efficient. They are not where loyalty gets built.
Enrolling studies shouldn't be this hard
Trialflow gives research sites one platform for lead management, AI trial matching, and recruitment analytics.
Request a Demo