A participant tells a site coordinator that getting to an upcoming study visit is going to be difficult. The study offers travel support. The service has been set up, and the participant is eligible. But the coordinator’s never needed to use it before. Maybe they remember seeing something about travel during study startup, or they know who to contact but not what happens next. Either way, the participant’s immediate problem still has to be solved.
Participant support can be fully available without being fully adopted. While setting up a service creates the possibility of support, the effect on participants depends on what happens when a site actually needs to use it.
Availability’s relatively easy to establish. Has travel support been included in the study? Can participants receive reimbursement? Is a support service ready for sites to access?
Adoption asks what happens after those decisions have been made. Can site staff comfortably use the service when a need arises? Do they know what support is available under the study? Can participants still get help months after the initial study training?
Low use doesn’t always signal a problem; some studies may just have fewer participants who need travel assistance or reimbursement. But availability alone can’t tell us whether a support program is working as intended. As Scout Chief Innovation Officer Matt Sowards put it at the April 2026 Clinical Leader Digital Expo, “Support only works when it’s actually getting used.”
One reason adoption can vary is simple: research sites don’t all work the same way. The differences become especially obvious in global studies. Some sites may prefer a digital process. Others may rely on paper for certain reimbursement workflows. A site may want to call and arrange transportation rather than ask a participant to complete another online process.
Study requirements still have to be met. But forcing every site into an identical interaction model can create friction before the support ever reaches the participant. Understanding how sites already work makes it easier to figure out how the service can fit into the study without creating unnecessary work for the people expected to use it.
Sowards put it plainly at the expo: “You got to talk to the actual sites and the actual patients and find out what they want, how they want it to work.” That variability makes site adoption an implementation question, instead of something that can just be assumed once a service goes live.
Study startup receives a lot of attention for good reason. Processes are introduced, teams are trained, expectations established. Then the study continues, and a coordinator may go months without needing to arrange participant travel. A participant who had no difficulty reaching study visits at enrollment might experience a change in work, transportation, caregiving responsibilities, or finances later.
Access still has to be clear when a need emerges months after the service was introduced. And the answer might not even be “more communication.” Some experienced sites may prefer very little contact once a process is established, while another may benefit from occasional outreach or a clear reminder of where to go when questions arise. The appropriate level of engagement depends on the people using the service. What matters is that the path back to support remains clear when the need appears.
Utilization data can tell study teams that a service is being used. Interpreting low use does require more care. Sometimes the explanation is straightforward: participants didn’t need much assistance. But other cases may warrant a closer look. Are sites comfortable with the process? Do staff remember what support is available under the study? Does the way the service is accessed fit reasonably well with how those sites operate? Those questions turn utilization into something more useful than a simple score.
A support program with modest usage may be functioning exactly as expected. A program with unexpectedly low usage may reveal an opportunity to understand what is happening between availability and use. Participant needs can’t be inferred from program setup alone.
Sponsors can make meaningful support available to participants long before anyone knows exactly when it will be needed. That uncertainty is part of the point. A participant-support program has to remain usable through the ordinary life of the study, including the months when a site does not need it and the moment when a participant suddenly does.
Planning for adoption means considering how sites will work with the service, how participants will reach support when circumstances change, and what utilization may be telling the study team over time.