The Participant Is on Time. Why Isn’t the Visit?

Imagine a participant arriving at 8:55 for a nine o’clock research visit. They checked the instructions, brought what was requested, and planned their morning around the time the site gave them.

At 9:35, they’re still waiting. Nobody has explained what happens next.

This is a hypothetical morning, not a story about a particular site. But it raises a question worth asking before we send another appointment reminder: how carefully have we planned our side of the appointment?

If we ask participants to protect time for research, we should protect that time too.

The appointment is a promise with missing details

“Your visit is at nine” sounds precise. It doesn’t explain whether nine means check-in, the first procedure, or the start of a queue.

A visit estimate can be equally misleading if it counts only hands-on procedures. The participant experiences the whole stretch from arrival to departure, including the gaps between people, rooms, and decisions.

The NIH’s participant information encourages people to ask how research will affect daily life and explains that participation can require substantial time. My operational takeaway is simple: we should be prepared to answer those questions with more than the shortest possible version of a visit.

An honest estimate might be a range, with an explanation of what could extend it. That is more useful than a confident finish time built around everything going perfectly.

Some waiting belongs in the visit

There is a fair objection here. Research appointments aren’t restaurant reservations.

A safety concern may need immediate attention. A procedure may require a defined interval. An investigator may need more time with someone than the calendar anticipated. Sponsors need consistent procedures and usable data; sites cannot rearrange every step for convenience.

I wouldn’t want a team rushing an assessment to protect an on-time metric.

The distinction I would make is between time the study needs and time our process loses. Required observation is different from discovering, after arrival, that the room is double-booked or the person needed for the next step wasn’t scheduled.

Both can feel like waiting to a participant. They require different responses from us.

A necessary wait deserves an explanation. An avoidable wait deserves a change.

That explanation must also protect other people’s privacy. “The clinician is handling an unexpected clinical issue” can provide context without sharing someone else’s situation.

Plan the gaps, not just the procedures

I’d start with one visit type and walk through it with the people who actually deliver it.

Where does the participant go after each step? Who needs to be available? Which activities have fixed timing? What happens if the previous appointment runs long?

In software, a task can be quick while the handoff around it is slow. I find that a useful way to examine a visit: completing each individual step efficiently doesn’t guarantee that the whole experience runs well.

Three changes seem worth trying.

• Build the estimate from arrival to departure. Include required intervals and realistic handoffs. Check a small sample of actual visits against the estimate, using the site’s approved records and privacy practices. Separate necessary study time from avoidable delay.
• Match bookings to shared capacity. Before filling a slot, check the rooms, qualified staff, equipment, and investigator availability it depends on. Where the protocol allows flexibility, stagger appointments around the constrained resource instead of giving everyone the same start time.
• Assign the delay update. Decide who tells the participant what is happening, when they’ll hear again, and which options the study team can safely offer. An uncertain finish time is a reason to communicate uncertainty, not disappear.

A CRO monitor or sponsor team can help by clarifying procedural dependencies that sites are interpreting differently. Where the same bottleneck appears across sites, it deserves a study-level conversation. A local scheduling fix cannot solve every design constraint.

Don’t make the coordinator absorb the whole problem

It would be easy to turn this into another instruction to the front desk: keep everyone happy while the schedule falls apart.

That misses the point. The person explaining a delay needs a reliable update and a realistic plan from the team. Courtesy cannot substitute for capacity.

I’d review repeated overruns without turning the discussion into a ranking of who works fastest. Look for the step that keeps starting late. Ask whether the estimate was credible in the first place.

We can’t promise a research visit will always finish exactly on time. We can promise to plan honestly, explain changes, and investigate delays that keep repeating.

Which part of your visit most often runs later than promised, and what would you change before booking the next one?

Enmanuel Corvo | The Site Perspective

Enmanuel CorvoEngineer. Site leader. Always learning.

I write about the practical work behind clinical research and what sites, sponsors, and CROs can learn from each other.

Share your perspectiveAll perspectives